Difference between revisions of "GCube Document Model"
m (moved Canonical gDoc Forms to GCube Document Model) |
|||
Line 1: | Line 1: | ||
− | The [[Content_Manager_(NEW)|Content Manager | + | The [[Content_Manager_(NEW)|Content Manager]] service adopts a generic model of content based on labelled trees, the [[Content_Manager_(NEW)#gDoc_Trees|<code>gDoc</code> trees]], under the assumption that content producers and content consumers will convene on concrete document models and exchange gDoc trees with an agreed shape. |
− | The agreement may be bilateral or involve any number of parties, and it may apply to the entire document or to distinguished parts of it (e.g. document metadata, annotations, raw content packaging, etc). For maximum decoupling between consumers and producers, the agreement may reflect system-wide conventions and result in ''canonical tree forms'' | + | The agreement may be bilateral or involve any number of parties, and it may apply to the entire document or to distinguished parts of it (e.g. document metadata, annotations, raw content packaging, etc). For maximum decoupling between consumers and producers, the agreement may reflect system-wide conventions and result in ''canonical tree forms''. |
− | + | A set of canonical forms for content metadata, annotations, parts, and alternative representations defines the ''gCube Document Model'', the concrete document model of the system. | |
− | = | + | {{UnderUpdate}} |
+ | |||
+ | = Documents = | ||
+ | |||
+ | == Canonical Form == | ||
+ | |||
+ | = Metadata = | ||
+ | |||
+ | |||
+ | == Canonical Form == | ||
+ | |||
+ | = Annotations = | ||
+ | |||
+ | |||
+ | == Canonical Form == | ||
+ | |||
+ | = Parts = | ||
+ | |||
+ | |||
+ | = Alternative Representations = | ||
+ | |||
+ | == Canonical Form == |
Revision as of 22:09, 5 October 2010
The Content Manager service adopts a generic model of content based on labelled trees, the gDoc
trees, under the assumption that content producers and content consumers will convene on concrete document models and exchange gDoc trees with an agreed shape.
The agreement may be bilateral or involve any number of parties, and it may apply to the entire document or to distinguished parts of it (e.g. document metadata, annotations, raw content packaging, etc). For maximum decoupling between consumers and producers, the agreement may reflect system-wide conventions and result in canonical tree forms.
A set of canonical forms for content metadata, annotations, parts, and alternative representations defines the gCube Document Model, the concrete document model of the system.
THIS SECTION OF GCUBE DOCUMENTATION IS CURRENTLY UNDER UPDATE.