Difference between revisions of "Content Management"
(New page: {{UnderUpdate}}) |
Ali.boloori (Talk | contribs) |
||
Line 1: | Line 1: | ||
− | + | While other infrastructures for the manipulation of content in Grid-based environments, like gLite, provide basic file-system like functionality for content manipulation, the Information Organization services are aimed to provide more high-level functionality, built on top of gLite or other storage facilities. Content is stored and organized following a graph-based data model, the ''Information Object Model'', that allows finer control of content w.r.t. a file based view, by incorporating the possibility to annotate content with arbitrary properties and to relate different content unities via arbitrary relationships. | |
+ | Building on this basic data model, other services in the Information Organization family provide to other gCube services more sophisticated data models to manage ''complex documents, document collections, metadata'' and ''annotations''. |
Revision as of 16:52, 21 November 2008
While other infrastructures for the manipulation of content in Grid-based environments, like gLite, provide basic file-system like functionality for content manipulation, the Information Organization services are aimed to provide more high-level functionality, built on top of gLite or other storage facilities. Content is stored and organized following a graph-based data model, the Information Object Model, that allows finer control of content w.r.t. a file based view, by incorporating the possibility to annotate content with arbitrary properties and to relate different content unities via arbitrary relationships. Building on this basic data model, other services in the Information Organization family provide to other gCube services more sophisticated data models to manage complex documents, document collections, metadata and annotations.