Differences between revisions 1 and 11 (spanning 10 versions)
⇤ ← Revision 1 as of 2008-10-17 09:24:08 →
Size: 3590
Editor: abr
Comment:
← Revision 11 as of 2010-03-17 13:09:13 → ⇥
Size: 2163
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:

Doms come with some predefined objects. Most of these carry heavy semantic meaning in regards to the overall DataModel.

== Content Models in general ==

Fedora provides a repository for digital objects. All objects in the repository can, in principle, be unique, but Fedora provides a way of specifying that an object has a given type. Unfortunately, the type-definitions in Fedora, called Content Models, are rather simplistic by default. We use them as the basis of our type system, with certain enhancements.

For our purposes, there are two kinds of digital objects in Fedora
 * Data objects
 * Content Model objects

The Content Model object, as used in DOMS, describes the compulsary and legal content of an object of this type. It contains the information nessesary to verify if the given object is indeed of this type. For more detail on this, see FedoraOntology and FedoraTypeChecking

A data object can specify the Content Model describing its contents, via a fedora-model:hasModel relation, and in DOMS we require it to be present. A data object will be said to "subcribe" to a Content Model. Content Model inheritance, as specified in FedoraOntology, will be used.

The special Content Model object "doms:!ContentModel_DOMS" is the root object. All Content Models must have an "doms-relations:extendsModel" relation to this object, possibly through a number of other Content Models. The complete description of a data object is defined as the set of the descriptions in the Content Model specified with "fedora-model:hasModel" and all Content Models that can be reached from this, by following "doms-relations:extendsModel" relations.

A Content Model can "extend" more than one other Content Model. There is no overriding of Content Models, a subscribing object must be valid in regards to all the Content Models in the inheritance tree.


Content Models have two datastreams in particular that are interesting. These are the ONTOLOGY and DS-COMPOSITE. The Ontology defines the the allowed relations in subscribing objects, and the DS-COMPOSITE defines the required datastreams and any restrictions they must adhere to.		 Doms come with some predefined objects. Most of these carry heavy semantic meaning in regards to the overall DataModel.
Line 25: Line 5:
{{attachment:DOMSBaseCollection.png}}
Line 28: Line 9:

 * [:DataModel/ContentModel_DOMS: doms:ContentModel_DOMS]
 * [:DataModel/ContentModel_File: doms:ContentModel_File]
 * [:DataModel/ContentModel_AudioPreservationFile: doms:ContentModel_AudioPreservationFile]
 * [:DataModel/ContentModel_ImagePreservationFile: doms:ContentModel_ImagePreservationFile]
 * [:DataModel/ContentModel_VideoPreservationFile: doms:ContentModel_VideoPreservationFile]
 * [:DataModel/ContentModel_TextPreservationFile: doms:ContentModel_TextPreservationFile]
 * [:DataModel/ContentModel_Audio: doms:ContentModel_Audio]
 * [:DataModel/ContentModel_Image: doms:ContentModel_Image]
 * [:DataModel/ContentModel_Video: doms:ContentModel_Video]
 * [:DataModel/ContentModel_Text: doms:ContentModel_Text]
 * [:DataModel/ContentModel_License: doms:ContentModel_License]
 * [:DataModel/ContentModel_Schema: doms:ContentModel_Schema]
 * [:DataModel/ContentModel_Collection: doms:ContentModel_Collection]

 * [:DataModel/Root_Collection: doms:Root_Collection]
 * [:DataModel/DOMS_Base_Collection: doms:DOMS_Base_Collection]
 * [:DataModel/Open_License: doms:Open_License]
 * [:DataModel/View_Schema: doms:Schema_View]
 * [:DataModel/Schema_OAIDublinCore: doms:Schema_OAIDublinCore]		  * [[DataModel/ContentModel DOMS|doms:ContentModel_DOMS]] - The requirements for all objects in Doms
 * [[DataModel/ContentModel File|doms:ContentModel_File]] - The requirements for all objects that should reference files in Bitstorage. See DomsFileHandling
  * [[DataModel/ContentModel AudioPreservationFile|doms:ContentModel_AudioPreservationFile]] - Special content models for files that are of preservable formats
  * [[DataModel/ContentModel ImagePreservationFile|doms:ContentModel_ImagePreservationFile]] - See above
  * [[DataModel/ContentModel VideoPreservationFile|doms:ContentModel_VideoPreservationFile]] - See above
  * [[DataModel/ContentModel TextPreservationFile|doms:ContentModel_TextPreservationFile]] - See above
 * [[DataModel/ContentModel License|doms:ContentModel_License]] - The content model for objects containing the technical requirements of rights and licenses are described here. See FedoraLicensePolicies
  * [[DataModel/Open License|doms:Open_License]] - The license imposing no access restrictions
 * [[DataModel/ContentModel Schema|doms:ContentModel_Schema]] - The content model for objects objects describing the contents of datastreams in data objects. See FedoraTypeChecking
  * [[DataModel/View Schema|doms:Schema_View]] - The schema for the VIEW datastream
  * [[DataModel/Schema OAIDublinCore|doms:Schema_OAIDublinCore]] - The schema for the DC datastream
 * [[DataModel/ContentModel Collection|doms:ContentModel_Collection]] - The content model for objects representing the overall structure of the repository.
  * [[DataModel/Root Collection|doms:Root_Collection]] - The overall collection, representing the entire repository
  * [[DataModel/DOMS Base Collection|doms:DOMS_Base_Collection]] - The collection of the base objects ===

Doms Predefined Objects

Doms come with some predefined objects. Most of these carry heavy semantic meaning in regards to the overall DataModel.

DOMS Base Collection

DOMSBaseCollection.png

Doms come shipped with a base collection of objects, representing the base types. The objects in the base collection will be detailed in the following.

DomsPredefinedObjects (last edited 2010-03-17 13:09:13 by localhost)