Difference between revisions of "ESciDoc Content Models"

From MPDLMediaWiki
Jump to navigation Jump to search
Line 15: Line 15:
Following properties/attributes are specified within a CModel definition:
Following properties/attributes are specified within a CModel definition:


* properties: id, name, versioning-info{WOV, none}
* properties: id, name, description
**Each CModel is itself an object that has some general information that describes the e.g. usage and purpose of the model
**Note: in eSciDoc
 
* metadata-profiles: references to the metadata profiles
* metadata-profiles: references to the metadata profiles
* model-specific-object-properties: (property-name, property-type, multiplicity)*
**in this case still needs to be clarified if there are more than single metadata profile applicable to an e.g. item of a specific CModel
* 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
* component-types: types, multiplicity and format of files which can be associated with Items of particular CModel
* container-
* container-

Revision as of 12:05, 13 December 2007

UNDER CONSTRUCTION

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 at the moment 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.)
  • primary types may be further specialized by use of the content model i.e. CModel definition (at the moment in eSciDoc only Items and Containers are taken into consideration for CModel specialization)

ESciDoc_Data_Models explain more on primary types and the eSciDoc data models (note this page is not yet created :).

What cModel defines[edit]

Following properties/attributes are specified within a CModel definition:

  • properties: id, name, description
    • Each CModel is itself an object that has some general information that describes the e.g. usage and purpose of the model
    • Note: in eSciDoc
  • metadata-profiles: references to the metadata profiles
    • in this case still needs to be clarified if there are more than single metadata profile applicable to an e.g. item of a specific CModel
  • 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)