A TEI Project

Documentation for METS Profile - Model Paged Text Object Profile | xml

Sample METS Profile Documenation with extended ODD

<structMap>

structMap The structural map is the heart of a METS document, defining the hierarchical arrangement of a primary source document which has been digitized. This hierarchy is encoded as a tree of 'div' elements. Any given 'div' can point to another METS document via the 'mptr' element, or to a single file, to a group of files, or to segments of individual files or groups of files through the 'fptr' and subsidiary elements.
Declaration 
   <sch:rule context="structMap" xmlns="http://www.ascc.net/xml/schematron">
      <sch:assert test="not(ancestor::par)">Par elements are not allowed in the structure map for this profile</sch:assert> 
   </sch:rule>
   <sch:rule context="structMap/@TYPE='physical' | structMap/@TYPE='mixed'">
        <sch:assert test="not(ancestor::par|ancestor::seq)"><structMap>'s with a TYPE of "mixed" or "physical" cannot have <par> or <seq> elements.>/sch:assert<
   </sch:rule>
Profile Requirements <structMap>s of "physical" and "mixed" TYPEs must not use either the <par> or <seq> elements.
Module metscore

<fptr>

fptr (fptr) The fptr element associates a div element with content files that represent that div. It can either point to a file directly itself, via the FILEID attribute, or it can do more complex links to content via the subsidiary area or seq elements.
Declaration 
element fptr
{
   attribute ID { odddata.name }?,
   attribute FILEID { odddata.namespace }?,
   attribute CONTENTIDS { odddata.namespace }?,
   { par* | seq* | area* }
}
Attributes
In addition to global attributes
ID an optional XML ID value.
Status: Optional
Datatype: data.name
Values: XML ID value
FILEID an IDREF to the file element which corresponds with the div containing this ftpr.
Status: Optional
ID Reference Requirment: this value must match the ID value for a <file> element [triggerd by the "references" attribute in the ODD]
Datatype: data.namespace
Values: XML IDREF Reference
CONTENTIDS Content IDs for this division (equivalent to DIDL DII)
Status: Optional
Datatype: data.namespace
Values: XML IDREF Reference
Profile Requirements A <fptr> element must either 1) directly point to a <file> element via its FILEID attribute; or 2) contain an <area> element that points to a <file> element; or 3) contain a <seq> element comprising multiple <area> elements that point to the relevant <file> elements. METS documents implementing this profile must not use the <par> element.
Relationship <fptr> isPartOf <div> [This piece of documentation generated because the "relationship" attribute has been used in the ODD source for the element.]
Module sMap