Differences between revisions 1 and 3 (spanning 2 versions)
Revision 1 as of 2008-10-02 14:46:32
Size: 528
Editor: abr
Comment:
Revision 3 as of 2010-03-17 13:09:23
Size: 548
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
== doms:ContentModel_AudioPreservationFile ==
Extends [:DataModel/ContentModel_File: doms:ContentModel_File]
== doms:ContentModel_VideoPreservationFile ==
Extends [[DataModel/ContentModel File| doms:ContentModel_File]]
Line 4: Line 4:
Objects of doms:!ContentModel_!AudioPreservationFile represent File objects for files that have been characterized and found to be of audio formats that we can preserve for the long term. At the moment this is the mpeg1 and mpeg2 formats. Objects of doms:!ContentModel_!VidePreservationFile represent File objects for files that have been characterized and found to be of video formats that we can preserve for the long term. At the moment this is the mpeg1 and mpeg2 formats.
Line 6: Line 6:
In the "PRONOMID" datastream, that all objects of doms:!ContentModel_File must have, the possible values are restricted to
In the "FORMAT_URI" attribute to the "CONTENTS" datastream, which all objects of doms:!ContentModel_File must have, the possible values are

doms:ContentModel_VideoPreservationFile

Extends doms:ContentModel_File

Objects of doms:ContentModel_VidePreservationFile represent File objects for files that have been characterized and found to be of video formats that we can preserve for the long term. At the moment this is the mpeg1 and mpeg2 formats.

In the "FORMAT_URI" attribute to the "CONTENTS" datastream, which all objects of doms:ContentModel_File must have, the possible values are

  • "x-fmt/385" (mpeg1)
  • "x-fmt/386" (mpeg2)

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