XML Schema : http://www.loc.gov/METS/
Schema Comments:
Imports namespace:http://www.w3.org/TR/xlink schemaLocation: xlink.xsd
Processing Instructions
Schema has:
12element definitions,  2 global attribute definitions,  87 element attribute definitions,  0 datatype definitions.
Possible root elements: mets,

Element list

Complex Type amdSecType
 
diagram
description amdSecType: Complex Type for Administrative Metadata. The administrative metadata section consists of four possible subsidiary sections: techMD (technical metadata for text/image/audio/video files), rightsMD (intellectual property rights metadata), sourceMD (analog/digital source metadata), and digiprovMD (digital provenance metadata, that is, the history of migrations/translations performed on a digital library object from it's original digital capture/encoding). amdSecType has a single attribute, ID (XML ID).
attributes ID  
defines locally techMD {mdSecType} * , rightsMD {mdSecType} * , sourceMD {mdSecType} * , digiprovMD {mdSecType} *
uses Does not reference other elements.
 
used by
content sequence
 
Attribute Datatype Use Values Default Comments
ID { xsd:ID } optional
 
source
- < xsd:complexType name =" amdSecType " >
- < xsd:annotation >
  < xsd:documentation > amdSecType: Complex Type for Administrative Metadata. The administrative metadata section consists of four possible subsidiary sections: techMD (technical metadata for text/image/audio/video files), rightsMD (intellectual property rights metadata), sourceMD (analog/digital source metadata), and digiprovMD (digital provenance metadata, that is, the history of migrations/translations performed on a digital library object from it's original digital capture/encoding). amdSecType has a single attribute, ID (XML ID). </ xsd:documentation >
  </ xsd:annotation >
- < xsd:sequence >
- < xsd:element name =" techMD " type =" mdSecType " minOccurs =" 0 " maxOccurs =" unbounded " >
- < xsd:annotation >
  < xsd:documentation > techMD: technical metadata. The techMD element provides a wrapper around a generic metadata section, which should contain technical metadata regarding a file or files. It has a single attribute, ID, which file/fileGrp elements can use to reference the technical metadata that applies to them. </ xsd:documentation >
  </ xsd:annotation >
  </ xsd:element >
- < xsd:element name =" rightsMD " type =" mdSecType " minOccurs =" 0 " maxOccurs =" unbounded " >
- < xsd:annotation >
  < xsd:documentation > rightsMD: intellectual property rights metadata. The rightsMD element provides a wrapper around a generic metadata section, which should contain IP rights metadata. It has a single attribute, ID, which other METS elements can use to reference IP Rights metadata that applies to them. </ xsd:documentation >
  </ xsd:annotation >
  </ xsd:element >
- < xsd:element name =" sourceMD " type =" mdSecType " minOccurs =" 0 " maxOccurs =" unbounded " >
- < xsd:annotation >
  < xsd:documentation > sourceMD: source metadata. The sourceMD element provides a wrapper around a generic metadata section which should contain information regarding the original source. It has a single attribute, ID, which file/fileGrp elements can use to reference the source metadata which applies to them. </ xsd:documentation >
  </ xsd:annotation >
  </ xsd:element >
- < xsd:element name =" digiprovMD " type =" mdSecType " minOccurs =" 0 " maxOccurs =" unbounded " >
- < xsd:annotation >
  < xsd:documentation > digiprovMD: digital provenance metadata. The digiprovMD element provides a wrapper around a generic metadata section, which should contain information regarding the ultimate origin of a digital object and the derivation of its current elements. This includes recording master/derivative relationships between various files which currently represent the object, as well recording any transformations or migrations undergone by files composing the digital object subsequent to the initial digitization of an item or, in the case of born digital materials, the files' creation. In short, digiprovMD should be used to record information to allow both archival/library staff and scholars to understand what modifications have been performed to a digital object during its life cycle in order to judge how those processes might have altered or corrupted the object's ability to accurately represent the original item. </ xsd:documentation >
  </ xsd:annotation >
  </ xsd:element >
  </ xsd:sequence >
  < xsd:attribute name =" ID " type =" xsd:ID " use =" optional " />
  </ xsd:complexType >

Complex Type areaType
 
diagram
description areaType: Complex Type for Area linking. The area element provides for more sophisticated linking between a div element and content files representing that div, be they text, image, audio, or video files. An area element can link a div to a point within a file, to a one-dimension segment of a file (e.g., text segment, image line, audio/video clip), or a two-dimensional section of a file (e.g, subsection of an image, or a subsection of the video display of a video file. The area element has no content, and the following attributes: 1. ID: an XML ID; 2. FILEID: an IDREF to the file element being pointed to by the div; 3. SHAPE: a text string defining the shape of a two-dimensional area being referenced in a link file; 4. COORDS: a text string representing a set of visual coordinates within an image (still image or video frame). The COORDS and SHAPE attributes should be used as in HTML 4; 5. BEGIN: a beginning location in a referenced file; 6. END: an ending location in a referenced file; 7. BETYPE: the syntax used in specifying the BEGIN and END attributes (byte offset, IDREF value, SMPTE time code, SMIL time value, MIDI time code, a simple time code of the form HH:MM:SS, or a TCF time code); 8. EXTENT: the duration of the segment; and 9. EXTTYPE: the syntax used in specifying the extent (byte length or SMPTE time value); 10. ADMID: IDREFs for administrative metadata regarding this area.
attributes ID   FILEID   SHAPE   COORDS   BEGIN   END   BETYPE   EXTENT   EXTTYPE   ADMID  
uses Does not reference other elements.
 
used by
substitution hierarchy areaType
content sequence (default)
 
Attribute Datatype Use Values Default Comments
ID { xsd:ID } optional
FILEID { xsd:IDREF } required
SHAPE { } {} optional possible values: RECT | CIRCLE | POLY
COORDS { xsd:string } optional
BEGIN { xsd:string } optional
END { xsd:string } optional
BETYPE { } {} optional possible values: BYTE | IDREF | SMIL | MIDI | SMPTE-25 | SMPTE-24 | SMPTE-DF30 | SMPTE-NDF30 | SMPTE-DF29.97 | SMPTE-NDF29.97 | TIME | TCF
EXTENT { xsd:string } optional
EXTTYPE { } {} optional possible values: BYTE | SMIL | MIDI | SMPTE-25 | SMPTE-24 | SMPTE-DF30 | SMPTE-NDF30 | SMPTE-DF29.97 | SMPTE-NDF29.97 | TIME | TCF
ADMID { xsd:IDREFS } optional
 
source
- < xsd:complexType name =" areaType " >
- < xsd:annotation >
  < xsd:documentation > areaType: Complex Type for Area linking. The area element provides for more sophisticated linking between a div element and content files representing that div, be they text, image, audio, or video files. An area element can link a div to a point within a file, to a one-dimension segment of a file (e.g., text segment, image line, audio/video clip), or a two-dimensional section of a file (e.g, subsection of an image, or a subsection of the video display of a video file. The area element has no content, and the following attributes: 1. ID: an XML ID; 2. FILEID: an IDREF to the file element being pointed to by the div; 3. SHAPE: a text string defining the shape of a two-dimensional area being referenced in a link file; 4. COORDS: a text string representing a set of visual coordinates within an image (still image or video frame). The COORDS and SHAPE attributes should be used as in HTML 4; 5. BEGIN: a beginning location in a referenced file; 6. END: an ending location in a referenced file; 7. BETYPE: the syntax used in specifying the BEGIN and END attributes (byte offset, IDREF value, SMPTE time code, SMIL time value, MIDI time code, a simple time code of the form HH:MM:SS, or a TCF time code); 8. EXTENT: the duration of the segment; and 9. EXTTYPE: the syntax used in specifying the extent (byte length or SMPTE time value); 10. ADMID: IDREFs for administrative metadata regarding this area. </ xsd:documentation >
  </ xsd:annotation >
  < xsd:attribute name =" ID " type =" xsd:ID " use =" optional " />
  < xsd:attribute name =" FILEID " type =" xsd:IDREF " use =" required " />
- < xsd:attribute name =" SHAPE " use =" optional " >
- < xsd:simpleType >
- < xsd:restriction base =" xsd:string " >
  < xsd:enumeration value =" RECT " />
  < xsd:enumeration value =" CIRCLE " />
  < xsd:enumeration value =" POLY " />
  </ xsd:restriction >
  </ xsd:simpleType >
  </ xsd:attribute >
  < xsd:attribute name =" COORDS " type =" xsd:string " use =" optional " />
  < xsd:attribute name =" BEGIN " type =" xsd:string " use =" optional " />
  < xsd:attribute name =" END " type =" xsd:string " use =" optional " />
- < xsd:attribute name =" BETYPE " use =" optional " >
- < xsd:simpleType >
- < xsd:restriction base =" xsd:string " >
  < xsd:enumeration value =" BYTE " />
  < xsd:enumeration value =" IDREF " />
  < xsd:enumeration value =" SMIL " />
  < xsd:enumeration value =" MIDI " />
  < xsd:enumeration value =" SMPTE-25 " />
  < xsd:enumeration value =" SMPTE-24 " />
  < xsd:enumeration value =" SMPTE-DF30 " />
  < xsd:enumeration value =" SMPTE-NDF30 " />
  < xsd:enumeration value =" SMPTE-DF29.97 " />
  < xsd:enumeration value =" SMPTE-NDF29.97 " />
  < xsd:enumeration value =" TIME " />
  < xsd:enumeration value =" TCF " />
  </ xsd:restriction >
  </ xsd:simpleType >
  </ xsd:attribute >
  < xsd:attribute name =" EXTENT " type =" xsd:string " use =" optional " />
- < xsd:attribute name =" EXTTYPE " use =" optional " >
- < xsd:simpleType >
- < xsd:restriction base =" xsd:string " >
  < xsd:enumeration value =" BYTE " />
  < xsd:enumeration value =" SMIL " />
  < xsd:enumeration value =" MIDI " />
  < xsd:enumeration value =" SMPTE-25 " />
  < xsd:enumeration value =" SMPTE-24 " />
  < xsd:enumeration value =" SMPTE-DF30 " />
  < xsd:enumeration value =" SMPTE-NDF30 " />
  < xsd:enumeration value =" SMPTE-DF29.97 " />
  < xsd:enumeration value =" SMPTE-NDF29.97 " />
  < xsd:enumeration value =" TIME " />
  < xsd:enumeration value =" TCF " />
  </ xsd:restriction >
  </ xsd:simpleType >
  </ xsd:attribute >
  < xsd:attribute name =" ADMID " type =" xsd:IDREFS " use =" optional " />
  </ xsd:complexType >

Complex Type behaviorSecType
 
diagram
description behaviorSecType: Complex Type for Behaviors. A behavior section can be used to associate executable behaviors with content in the METS object. A behavior section has an interface definition element that represents an abstract definition of the set of behaviors represented by a particular behavior section. A behavior section also has an behavior mechanism which is a module of executable code that implements and runs the behaviors defined abstractly by the interface definition. An behavior section may have the following attributes: 1. ID: an XML ID for the element 2. STRUCTID: IDREFS to structMap sections or divs within a structMap in the METS document. The content that the STRUCTID attribute points to is considered "input" to the behavior mechanism (executable) defined for the behaviorSec. 3. BTYPE: a behavior type identifier for a given set of related behaviors. 4. CREATED: date this behavior section of the METS object was created. 5. LABEL: a description of the type of behaviors this section represents. 6. GROUPID: an identifier that establishes a correspondence between this behavior section and other behavior sections. Typically, this will be used to facilitate versioning of behavior sections.
attributes ID   STRUCTID   BTYPE   CREATED   LABEL   GROUPID  
defines locally interfaceDef {objectType} ? , mechanism {objectType}
uses Does not reference other elements.
 
used by
content sequence
 
Attribute Datatype Use Values Default Comments
ID { xsd:ID } required
STRUCTID { xsd:IDREFS } required
BTYPE { xsd:string } optional
CREATED { xsd:dateTime } optional
LABEL { xsd:string } optional
GROUPID { xsd:string } optional
 
source
- < xsd:complexType name =" behaviorSecType " >
- < xsd:annotation >
  < xsd:documentation > behaviorSecType: Complex Type for Behaviors. A behavior section can be used to associate executable behaviors with content in the METS object. A behavior section has an interface definition element that represents an abstract definition of the set of behaviors represented by a particular behavior section. A behavior section also has an behavior mechanism which is a module of executable code that implements and runs the behaviors defined abstractly by the interface definition. An behavior section may have the following attributes: 1. ID: an XML ID for the element 2. STRUCTID: IDREFS to structMap sections or divs within a structMap in the METS document. The content that the STRUCTID attribute points to is considered "input" to the behavior mechanism (executable) defined for the behaviorSec. 3. BTYPE: a behavior type identifier for a given set of related behaviors. 4. CREATED: date this behavior section of the METS object was created. 5. LABEL: a description of the type of behaviors this section represents. 6. GROUPID: an identifier that establishes a correspondence between this behavior section and other behavior sections. Typically, this will be used to facilitate versioning of behavior sections. </ xsd:documentation >
  </ xsd:annotation >
- < xsd:sequence >
- < xsd:element name =" interfaceDef " type =" objectType " minOccurs =" 0 " >
- < xsd:annotation >
  < xsd:documentation > interfaceDef: interface definition object. The interface definition element contains a pointer an abstract definition of a set of related behaviors. These abstract behaviors can be associated with the content of a METS object. The interface definition element will be a pointer to another object (an interface definition object). An interface definition object could be another METS object, or some other entity (e.g., a WSDL file). Ideally, an interface definition object should contain metadata that describes a set of behaviors or methods. It may also contain files that describe the intended usage of the behaviors, and possibly files that represent different expressions of the interface definition. The interfaceDef element is optional to allow for cases where an interface definition can be obtained from a behavior mechanism object (see the mechanism element of the behaviorSec). </ xsd:documentation >
  </ xsd:annotation >
  </ xsd:element >
- < xsd:element name =" mechanism " type =" objectType " >
- < xsd:annotation >
  < xsd:documentation > mechanism: executable mechanism. A mechanism element contains a pointer to an executable code module that implements a set of behaviors defined by an interface definition. The mechanism element will be a pointer to another object (a mechanism object). A mechanism object could be another METS object, or some other entity (e.g., a WSDL file). A mechanism object should contain executable code, pointers to executable code, or specifications for binding to network services (e.g., web services). </ xsd:documentation >
  </ xsd:annotation >
  </ xsd:element >
  </ xsd:sequence >
  < xsd:attribute name =" ID " type =" xsd:ID " use =" required " />
  < xsd:attribute name =" STRUCTID " type =" xsd:IDREFS " use =" required " />
  < xsd:attribute name =" BTYPE " type =" xsd:string " use =" optional " />
  < xsd:attribute name =" CREATED " type =" xsd:dateTime " use =" optional " />
  < xsd:attribute name =" LABEL " type =" xsd:string " use =" optional " />
  < xsd:attribute name =" GROUPID " type =" xsd:string " use =" optional " />
  </ xsd:complexType >

Complex Type divType
 
diagram
description Div Complex Type The METS standard represents a document structurally as a series of nested div elements, that is, as a hierarchy (e.g., a book, which is composed of chapters, which are composed of subchapters, which are composed of text). Every div node in the structural map hierarchy may be connected (via subsidiary mptr or fptr elements) to content files which represent that div's portion of the whole document. The div element has the following attributes: 1. ID (an XML ID); 2. ORDER: an integer representation of this div's order among its siblings (e.g., its sequence); 3. ORDERLABEL: a string representation of this div's order among its siblings (e.g., "xii"), or a non-integer native numbering system. It is presumed that this value will still be machine-actionable (e.g., supports a page 'go to' function), and is not a replacement/ substitute for the LABEL attribute. 4. LABEL: a string label to describe this div to an end user viewing the document, as per a table of contents entry (NB: a div LABEL should be specific to its level in the structural map. In the case of a book with chapters, the book div LABEL should have the book title, and the chapter div LABELS should have the individual chapter titles, rather than having the chapter div LABELs combine both book title and chapter title). NB: to clarify the differences between ORDER, ORDERLABEL, and LABEL, imagine a text with 10 roman numbered pages followed by 10 arabic numbered pages. Page iii would have an ORDER of "3", an ORDERLABEL of "iii" and a LABEL of "Page iii", while page 3 would have an ORDER of "13", an ORDERLABEL of "3" and a LABEL of "Page 3". 5. DMDID: a set of IDREFs to descriptive metadata sections within this METS document applicable to this div. 6. ADMID: a set of IDREFS to administrative metadata sections within this METS document applicable to this div. 7. TYPE: a type of division (e.g., chapter, article, page, etc.).
attributes ID   LOCATION  xlink:simpleLink  ID   ID   FILEID   ID   ORDER   ORDERLABEL   LABEL   DMDID   ADMID   TYPE  
defines locally mptr * , fptr * , par ? , area {areaType} (0, unbounded) , seq {seqType} (0, unbounded) , seq {seqType} ? , area {areaType} ? , div {divType} *
uses Does not reference other elements.
 
used by
content sequence
 
Attribute Datatype Use Values Default Comments
ID { xsd:ID } optional
ID { xsd:ID } optional
ID { xsd:ID } optional
FILEID { xsd:IDREF } optional
ID { xsd:ID } optional
ORDER { xsd:integer } optional
ORDERLABEL { xsd:string } optional
LABEL { xsd:string } optional
DMDID { xsd:IDREFS } optional
ADMID { xsd:IDREFS } optional
TYPE { xsd:string } optional
 
source
- < xsd:complexType name =" divType " >
- < xsd:annotation >
  < xsd:documentation > Div Complex Type The METS standard represents a document structurally as a series of nested div elements, that is, as a hierarchy (e.g., a book, which is composed of chapters, which are composed of subchapters, which are composed of text). Every div node in the structural map hierarchy may be connected (via subsidiary mptr or fptr elements) to content files which represent that div's portion of the whole document. The div element has the following attributes: 1. ID (an XML ID); 2. ORDER: an integer representation of this div's order among its siblings (e.g., its sequence); 3. ORDERLABEL: a string representation of this div's order among its siblings (e.g., "xii"), or a non-integer native numbering system. It is presumed that this value will still be machine-actionable (e.g., supports a page 'go to' function), and is not a replacement/ substitute for the LABEL attribute. 4. LABEL: a string label to describe this div to an end user viewing the document, as per a table of contents entry (NB: a div LABEL should be specific to its level in the structural map. In the case of a book with chapters, the book div LABEL should have the book title, and the chapter div LABELS should have the individual chapter titles, rather than having the chapter div LABELs combine both book title and chapter title). NB: to clarify the differences between ORDER, ORDERLABEL, and LABEL, imagine a text with 10 roman numbered pages followed by 10 arabic numbered pages. Page iii would have an ORDER of "3", an ORDERLABEL of "iii" and a LABEL of "Page iii", while page 3 would have an ORDER of "13", an ORDERLABEL of "3" and a LABEL of "Page 3". 5. DMDID: a set of IDREFs to descriptive metadata sections within this METS document applicable to this div. 6. ADMID: a set of IDREFS to administrative metadata sections within this METS document applicable to this div. 7. TYPE: a type of division (e.g., chapter, article, page, etc.). </ xsd:documentation >
  </ xsd:annotation >
- < xsd:sequence >
- < xsd:element name =" mptr " minOccurs =" 0 " maxOccurs =" unbounded " >
- < xsd:annotation >
  < xsd:documentation > mptr: METS Pointer. The mptr element allows a div to be associated with a separate METS document containing the content corresponding with that div, rather than pointing to an internal file or file group. A typical instance of this would be the case of a METS document for a journal run, with a div elements for each individual journal issue. The div elements for the issues might point to separate METS documents for each issue, rather than having files and file groups for every issue encoded in one document. The mptr element may have the following attributes: 1. ID: an XML ID for this element; 2. LOCTYPE: the type of locator contained in the FLocat element; and 3. OTHERLOCTYPE: a string to indicate an alternative LOCTYPE if the LOCTYPE attribute itself has a value of "OTHER." 4. xlink:href: see XLink standard (http://www.w3.org/TR/xlink) 5. xlink:role: "" 6. xlink:arcrole: "" 7. xlink:title: "" 8. xlink:show: "" 9. xlink:actuate: "" NOTE: mptr is an empty element. The location of the resource pointed to MUST be stored in the xlink:href element. </ xsd:documentation >
  </ xsd:annotation >
- < xsd:complexType >
  < xsd:attribute name =" ID " type =" xsd:ID " use =" optional " />
  < xsd:attributeGroup ref =" LOCATION " />
  < xsd:attributeGroup ref =" xlink:simpleLink " />
  </ xsd:complexType >
  </ xsd:element >
- < xsd:element name =" fptr " minOccurs =" 0 " maxOccurs =" unbounded " >
- < xsd:annotation >
  < xsd:documentation > fptr: File Pointer. 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, par and seq elements. The fptr element can have the following attributes: 1. ID: an XML ID for this element; and 2. FILEID: an IDREF to a file element which corresponds with the div containing this ftpr. </ xsd:documentation >
  </ xsd:annotation >
- < xsd:complexType >
- < xsd:choice >
- < xsd:element name =" par " minOccurs =" 0 " >
- < xsd:annotation >
  < xsd:documentation > par: Parallel files. The par element should used to link a div to a set of content files when those files should be played/displayed in unison to deliver the content to the user. A par element has two possible subsidiary elements, which should be used in different cases. In cases where each bytestream to be played in parallel can fit in a single file, you should use subsidiary area elements within the par element to point to those files. However, in some cases, bytestreams which should be played in parallel are too large to fit in a single file (high quality multi-track audio, or video). In those cases, you should use subsidiary seq elements, where each seq contains the files comprising a particular bytestream in the order they should be played back. Par has the following attributes: 1. ID: an XML ID for this element. </ xsd:documentation >
  </ xsd:annotation >
- < xsd:complexType >
- < xsd:choice >
  < xsd:element name =" area " type =" areaType " maxOccurs =" unbounded " />
  < xsd:element name =" seq " type =" seqType " maxOccurs =" unbounded " />
  </ xsd:choice >
  < xsd:attribute name =" ID " type =" xsd:ID " use =" optional " />
  </ xsd:complexType >
  </ xsd:element >
  < xsd:element name =" seq " type =" seqType " minOccurs =" 0 " />
- < xsd:element name =" area " type =" areaType " minOccurs =" 0 " >
- < xsd:annotation >
  < xsd:documentation > The area element provides for more sophisticated linking between a div element and content files representing that div, be they text, image, audio, or video files. An area element can link a div to a point within a file, to a one-dimension segment of a file (e.g., text screen, image line, audio/video clip), or a two-dimensional section of a file (e.g, subsection of an image, or a subsection of the video display of a video file. See the areaType documentation for more details. </ xsd:documentation >
  </ xsd:annotation >
  </ xsd:element >
  </ xsd:choice >
  < xsd:attribute name =" ID " type =" xsd:ID " use =" optional " />
  < xsd:attribute name =" FILEID " type =" xsd:IDREF " use =" optional " />
  </ xsd:complexType >
  </ xsd:element >
  < xsd:element name =" div " type =" divType " minOccurs =" 0 " maxOccurs =" unbounded " />
  </ xsd:sequence >
  < xsd:attribute name =" ID " type =" xsd:ID " use =" optional " />
  < xsd:attribute name =" ORDER " type =" xsd:integer " use =" optional " />
  < xsd:attribute name =" ORDERLABEL " type =" xsd:string " use =" optional " />
  < xsd:attribute name =" LABEL " type =" xsd:string " use =" optional " />