Differences between revisions 1 and 5 (spanning 4 versions)
Revision 1 as of 2008-10-01 15:18:42
Size: 974
Editor: abr
Comment:
Revision 5 as of 2010-03-17 13:09:35
Size: 807
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
Extends [:DataModel/ContentModel_DOMS: doms:ContentModel_DOMS] Extends [[DataModel/ContentModel DOMS| doms:ContentModel_DOMS]]
Line 4: Line 4:
In DOMS, we have chosen to enforce a clear seperation between In DOMS, we have chosen to enforce a clear seperation between the metadata about the files, and the metadata about the intellectual content of the files. Objects of doms:ContentModel_Audio represents the second category, and holds metadata about the intellectual content. For more details on this concept see DomsFileHandling and [[DataModel/ContentModel File| doms:ContentModel_File]]
Line 6: Line 6:
Data objects of doms:!ContentModel_License must have the datastream "LICENSE". To understand the license system, see FedoraLicencePolicies. The "LICENSE" datastream contain the XACML code corresponding to the license this object represents. This content model represent the class of objects holding the descriptive metadata about a piece of Audio.
Line 8: Line 8:
The "DC" datastream in subscribing objects must contain information about the License. In particular:
 * dc:title must be the human readable title of the license
 * dc:description must contain the human readable legalese for the the license


=== ContentModel_Audio ===
Extends ContentModel_DOMS

The following variables are used:
 * $AudioFile: An object with the Content Model !ContentModel_AudioPreservationFile;


Requirements for objects described by !ContentModel_Audio
 * Datastreams
  * RELS-EXT:
   * doms:hasPreservationFile -> $AudioFile
Data objects of this content model must have one or more relations <doms-relations:hasPreservationFile> to objects of [[DataModel/ContentModel AudioPreservationFile| doms:ContentModel_AudioPreservationFile]]

doms:ContentModel_Audio

Extends doms:ContentModel_DOMS

In DOMS, we have chosen to enforce a clear seperation between the metadata about the files, and the metadata about the intellectual content of the files. Objects of doms:ContentModel_Audio represents the second category, and holds metadata about the intellectual content. For more details on this concept see DomsFileHandling and doms:ContentModel_File

This content model represent the class of objects holding the descriptive metadata about a piece of Audio.

Data objects of this content model must have one or more relations <doms-relations:hasPreservationFile> to objects of doms:ContentModel_AudioPreservationFile

DataModel/ContentModel Audio (last edited 2010-03-17 13:09:35 by localhost)