Difference between revisions of "ESciDoc Content Models"
Jump to navigation
Jump to search
m |
m |
||
Line 1: | Line 1: | ||
== Definition and scope == | |||
* Content model (CModel) is a formal representation of set of structural, integrity, behavior rules associated with some content managed in an eSciDoc repository. | |||
** in eSciDoc content is categorized in several primary eSciDoc types: item, container, context, organizational unit etc. The primary types are subject to extension in eSciDoc. | |||
** in eSciDoc the CModel scope is limited to objects that are primary of type ''Item'' or ''Container''. | |||
==Primary types== | |||
* eSciDoc primary types are complex data structures that are used to describe objects of interest for the eSciDoc system. | |||
* primary types represent the highest level of generalizaton of eSciDoc objects (i.e. organizational units, contexts, items, containers, users, etc.) | |||
* Items and containers primary types may be further specialized by use of the content model i.e. CModel definition. | |||
[[ESciDoc_Data_Models]] you can find more on primary types and the eSciDoc data models. | |||
== What cModel defines== | |||
Following properties/attributes are specified within a CModel definition: | |||
* properties: id, name, versioning-info{WOV, none} | |||
* metadata-profiles: references to the metadata profiles | |||
* model-specific-object-properties: (property-name, property-type, multiplicity)* | |||
* component-types: types, multiplicity and format of files which can be associated with Items of particular CModel | |||
* container- | |||
Under consideration at present: | |||
* publishing-method: todo | |||
* pid-assignment-method: todo | |||
* withdrawal-method: todo | |||
* relations: todo (probably not necessary in content model definition) |
Revision as of 15:43, 15 November 2007
Definition and scope[edit]
- Content model (CModel) is a formal representation of set of structural, integrity, behavior rules associated with some content managed in an eSciDoc repository.
- in eSciDoc content is categorized in several primary eSciDoc types: item, container, context, organizational unit etc. The primary types are subject to extension in eSciDoc.
- in eSciDoc the CModel scope is limited to objects that are primary of type Item or Container.
Primary types[edit]
- eSciDoc primary types are complex data structures that are used to describe objects of interest for the eSciDoc system.
- primary types represent the highest level of generalizaton of eSciDoc objects (i.e. organizational units, contexts, items, containers, users, etc.)
- Items and containers primary types may be further specialized by use of the content model i.e. CModel definition.
ESciDoc_Data_Models you can find more on primary types and the eSciDoc data models.
What cModel defines[edit]
Following properties/attributes are specified within a CModel definition:
- properties: id, name, versioning-info{WOV, none}
- metadata-profiles: references to the metadata profiles
- model-specific-object-properties: (property-name, property-type, multiplicity)*
- component-types: types, multiplicity and format of files which can be associated with Items of particular CModel
- container-
Under consideration at present:
- publishing-method: todo
- pid-assignment-method: todo
- withdrawal-method: todo
- relations: todo (probably not necessary in content model definition)