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 " />
  < xsd:attribute name =" DMDID " type =" xsd:IDREFS " use =" optional " />
  < xsd:attribute name =" ADMID " type =" xsd:IDREFS " use =" optional " />
  < xsd:attribute name =" TYPE " type =" xsd:string " use =" optional " />
  </ xsd:complexType >

Complex Type fileGrpType
 
diagram
description fileGrp: File Group. The file group is used to cluster all of the digital files composing a digital library object in a hierarchical arrangement (fileGrp is recursively defined to enable the creation of the hierarchy). Any file group may contain zero or more file elements. File elements in turn can contain one or more FLocat elements (a pointer to a file containing content for this object) and/or a FContent element (the contents of the file, in either XML or Base64 encoding). A fileGrp element may have the following attributes: 1. ID: an XML ID for the element 2. VERSDATE: date this version/fileGrp of the digital object was created. 3. ADMID: IDREFs to administrative metadata sections in the METS document that correspond with all files in this file group; 4. USE: a string to indicate the intended use of files within this file group (e.g., master, reference, thumbnails for image files).
attributes ID   LOCATION  USE   xlink:simpleLink  USE   ID   MIMETYPE   SEQ   SIZE   CREATED   CHECKSUM   OWNERID   ADMID   DMDID   GROUPID   USE   ID   VERSDATE   ADMID   USE  
defines locally fileGrp {fileGrpType} * , file * , FLocat * , FContent ? , binData {xsd:base64Binary} ? , xmlData ?
uses Does not reference other elements.
 
used by
metsType   fileSec     fileGrp    
content sequence
 
Attribute Datatype Use Values Default Comments
ID { xsd:ID } optional
USE { xsd:string } optional
USE { xsd:string } optional
ID { xsd:ID } required
MIMETYPE { xsd:string } optional
SEQ { xsd:int } optional
SIZE { xsd:long } optional
CREATED { xsd:dateTime } optional
CHECKSUM { xsd:string } optional
OWNERID { xsd:string } optional
ADMID { xsd:IDREFS } optional
DMDID { xsd:IDREFS } optional
GROUPID { xsd:string } optional
USE { xsd:string } optional
ID { xsd:ID } optional
VERSDATE { xsd:dateTime } optional
ADMID { xsd:IDREFS } optional
USE { xsd:string } optional
 
source
- < xsd:complexType name =" fileGrpType " >
- < xsd:annotation >
  < xsd:documentation > fileGrp: File Group. The file group is used to cluster all of the digital files composing a digital library object in a hierarchical arrangement (fileGrp is recursively defined to enable the creation of the hierarchy). Any file group may contain zero or more file elements. File elements in turn can contain one or more FLocat elements (a pointer to a file containing content for this object) and/or a FContent element (the contents of the file, in either XML or Base64 encoding). A fileGrp element may have the following attributes: 1. ID: an XML ID for the element 2. VERSDATE: date this version/fileGrp of the digital object was created. 3. ADMID: IDREFs to administrative metadata sections in the METS document that correspond with all files in this file group; 4. USE: a string to indicate the intended use of files within this file group (e.g., master, reference, thumbnails for image files). </ xsd:documentation >
  </ xsd:annotation >
- < xsd:choice >
  < xsd:element name =" fileGrp " type =" fileGrpType " minOccurs =" 0 " maxOccurs =" unbounded " />
- < xsd:element name =" file " minOccurs =" 0 " maxOccurs =" unbounded " >
- < xsd:annotation >
  < xsd:documentation > file: File element. The file element provides access to content files for a METS document. A file element may contain one or more FLocat elements, which provide pointers to a content file, and/or an FContent element, which wraps an encoded version of the file. Note that ALL FLocat and FContent elements underneath a singel file element should identify/contain identical copies of a single file. The file element has the following attributes: 1. ID: an XML ID for the element; 2. MIMETYPE: the MIME type for the file; 3. SEQ: an integer indicating the sequence of this file relative to the others in its file group; 4. SIZE: the size of the file in bytes; 5. CREATED: the date of creation for the file; 6. CHECKSUM: an MD5 digest value for the included file. 7. OWNERID: a primary identifier assigned to the file by its owner; 8. ADMID: IDREFS to administrative metadata sections in the METS document that correspond with this file; 9. DMDID: IDREFS to descriptive metadata sections in the METS document that correspond with this file; 10. GROUPID: an identifier that establishes a correspondence between this file and files in other file groups. Typically, this will be used to associate a master file in one file group with derivative files in other file groups; 11. USE: a string indicated the intended use of this file (e.g., master, reference, thumbnail for image files). </ xsd:documentation >
  </ xsd:annotation >
- < xsd:complexType >
- < xsd:sequence >
- < xsd:element name =" FLocat " minOccurs =" 0 " maxOccurs =" unbounded " >
- < xsd:annotation >
  < xsd:documentation > FLocat: File Location. The FLocat element provides a pointer to the location of a content file. It uses the XLink syntax to provide linking information indicating the actual location of the content file, along with a few additional attributes specifying additional linking information. The full attribute set for the FLocat element is as follows: 1. ID (an XML ID); 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. USE: a string indicating the intended use of the referenced file; 5. xlink:href: see XLink standard (http://www.w3.org/TR/xlink); 6. xlink:role: "" 7. xlink:arcrole: "" 8. xlink:title: "" 9. xlink:show: "" 10. xlink:actuate: "" NOTE: FLocat 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:attribute name =" USE " type =" xsd:string " use =" optional " />
  < xsd:attributeGroup ref =" xlink:simpleLink " />
  </ xsd:complexType >
  </ xsd:element >
- < xsd:element name =" FContent " minOccurs =" 0 " >
- < xsd:annotation >
  < xsd:documentation > FContent: file content. The FContent element is used to deliver a content file for a METS document within the METS file itself. The content file must be either Base 64 encoded, and contained within the subsidiary binData wrapper element, or consist of XML information and be contained within the subsidiary xmlData wrapper element. The FContent element has the following attribute: 1. ID (an XML ID) 2. USE: a string indicating the intended use of the embedded file. </ xsd:documentation >
  </ xsd:annotation >
- < xsd:complexType >
- < xsd:choice >
- < xsd:element name =" binData " type =" xsd:base64Binary " minOccurs =" 0 " >
- < xsd:annotation >
  < xsd:documentation > A wrapper to contain a Base64 encoded file. </ xsd:documentation >
  </ xsd:annotation >
  </ xsd:element >
- < xsd:element name =" xmlData " minOccurs =" 0 " >
- < xsd:annotation >
  < xsd:documentation > A wrapper to contain an XML encoded file. </ xsd:documentation >
  </ xsd:annotation >
- < xsd:complexType >
- < xsd:sequence >
  < xsd:any namespace =" ##any " maxOccurs =" unbounded " />
  </ xsd:sequence >
  </ xsd:complexType >
  </ xsd:element >
  </ xsd:choice >
  < xsd:attribute name =" USE " type =" xsd:string " use =" optional " />
  </ xsd:complexType >
  </ xsd:element >
  </ xsd:sequence >
  < xsd:attribute name =" ID " type =" xsd:ID " use =" required " />
  < xsd:attribute name =" MIMETYPE " type =" xsd:string " use =" optional " />
  < xsd:attribute name =" SEQ " type =" xsd:int " use =" optional " />
  < xsd:attribute name =" SIZE " type =" xsd:long " use =" optional " />
  < xsd:attribute name =" CREATED " type =" xsd:dateTime " use =" optional " />
  < xsd:attribute name =" CHECKSUM " type =" xsd:string " use =" optional " />
  < xsd:attribute name =" OWNERID " type =" xsd:string " use =" optional " />
  < xsd:attribute name =" ADMID " type =" xsd:IDREFS " use =" optional " />
  < xsd:attribute name =" DMDID " type =" xsd:IDREFS " use =" optional " />
  < xsd:attribute name =" GROUPID " type =" xsd:string " use =" optional " />
  < xsd:attribute name =" USE " type =" xsd:string " use =" optional " />
  </ xsd:complexType >
  </ xsd:element >
  </ xsd:choice >
  < xsd:attribute name =" ID " type =" xsd:ID " use =" optional " />
  < xsd:attribute name =" VERSDATE " type =" xsd:dateTime " use =" optional " />
  < xsd:attribute name =" ADMID " type =" xsd:IDREFS " use =" optional " />
  < xsd:attribute name =" USE " type =" xsd:string " use =" optional " />
  </ xsd:complexType >

Complex Type mdSecType
 
diagram
description mdSec (metadata section) Complex Type A generic framework for pointing to/including metadata within a METS document, a la Warwick Framework. An mdSec element may have the following attributes: 1. ID: an XML ID for this element; 2. GROUPID: an identifier that may be used to indicate that different metadata sections may be considered as part of a single group. Two metadata sections with the same GROUPID value are to be considered part of the same group. This facility might be used, for example, to group changed versions of the same metadata if previous versions are maintained in a file for tracking purposes; 3. ADMID: a set of IDREFS to administrative metadata elements which apply to the current descriptive or administrative metadata. Typically used to reference preservation metadata which applies to the current metadata; 4. CREATED: the date and time of creation for the metadata; and 5. STATUS: a string indicating the status of this metadata (e.g., superceded, current, etc.).
attributes ID   LOCATION  xlink:simpleLink  METADATA  MIMETYPE   LABEL   XPTR   ID   MIMETYPE   METADATA  LABEL   ID   GROUPID   ADMID   CREATED   STATUS  
defines locally mdRef ? , mdWrap ? , binData {xsd:base64Binary} ? , xmlData ?
uses Does not reference other elements.
 
used by
content sequence
 
Attribute Datatype Use Values Default Comments
ID { xsd:ID } optional
MIMETYPE { xsd:string } optional
LABEL { xsd:string } optional
XPTR { xsd:string } optional
ID { xsd:ID } optional
MIMETYPE { xsd:string } optional
LABEL { xsd:string } optional
ID { xsd:ID } required
GROUPID { xsd:string } optional
ADMID { xsd:IDREFS } optional
CREATED { xsd:dateTime } optional
STATUS { xsd:string } optional
 
source
- < xsd:complexType name =" mdSecType " >
- < xsd:annotation >
  < xsd:documentation > mdSec (metadata section) Complex Type A generic framework for pointing to/including metadata within a METS document, a la Warwick Framework. An mdSec element may have the following attributes: 1. ID: an XML ID for this element; 2. GROUPID: an identifier that may be used to indicate that different metadata sections may be considered as part of a single group. Two metadata sections with the same GROUPID value are to be considered part of the same group. This facility might be used, for example, to group changed versions of the same metadata if previous versions are maintained in a file for tracking purposes; 3. ADMID: a set of IDREFS to administrative metadata elements which apply to the current descriptive or administrative metadata. Typically used to reference preservation metadata which applies to the current metadata; 4. CREATED: the date and time of creation for the metadata; and 5. STATUS: a string indicating the status of this metadata (e.g., superceded, current, etc.). </ xsd:documentation >
  </ xsd:annotation >
- < xsd:all >
- < xsd:element name =" mdRef " minOccurs =" 0 " >
- < xsd:annotation >
  < xsd:documentation > mdRef: metadata reference. The mdRef element is a generic element used throughout the METS schema to provide a pointer to metadata which resides outside the METS document. It has the following attributes: 1. ID: an XML ID; 2. LOCTYPE: the type of locator contained in the body of the element; 3. OTHERLOCTYPE: a string indicating an alternative LOCTYPE when the LOCTYPE attribute value is set to "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: "" 10. MIMETYPE: the MIME type for the metadata being pointed at; 11. MDType: the type of metadata being pointed at (e.g., MARC, EAD, etc.); 12. OTHERMDTYPE: a string indicating an alternative MDTYPE when the MDTYPE attribute value is set to "OTHER."; 13. LABEL: a label to display to the viewer of the METS document identifying the metadata; and 14. XPTR: an xptr to a location within the file pointed to by the mdRef element, if applicable. NB: mdRef is an empty element. The location of the metadata must be recorded in the xlink:href attribute, supplemented by the XPTR attribute as needed. </ 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:attributeGroup ref =" METADATA " />
  < xsd:attribute name =" MIMETYPE " type =" xsd:string " use =" optional " />
  < xsd:attribute name =" LABEL " type =" xsd:string " use =" optional " />
  < xsd:attribute name =" XPTR " type =" xsd:string " use =" optional " />
  </ xsd:complexType >
  </ xsd:element >
- < xsd:element name =" mdWrap " minOccurs =" 0 " >
- < xsd:annotation >
  < xsd:documentation > mdWrap: metadata wrapper. The mdWrap element is a generic element used throughout the METS schema to allow the encoder to place arbitrary metadata conforming to other standards/schema within a METS document. The included metadata can either be encoded in XML, in which case it may be placed directly within the mdWrap element, or it can be Base64 encoded, and placed within a subsidiary binData element. The mdWrap element can have the following attributes: 1. ID: an XML ID for this element; 2. MIMETYPE: the MIME type for the metadata contained in the element; 3. MDType: the type of metadata contained (e.g., MARC, EAD, etc.); 4. OTHERMDTYPE: a string indicating an alternative MDTYPE when the MDTYPE attribute value is set to "OTHER."; 5. LABEL: a label to display to the viewer of the METS document identifying the metadata. </ xsd:documentation >
  </ xsd:annotation >
- < xsd:complexType >
- < xsd:choice >
- < xsd:element name =" binData " type =" xsd:base64Binary " minOccurs =" 0 " >
- < xsd:annotation >
  < xsd:documentation > A wrapper to contain Base64 encoded metadata. </ xsd:documentation >
  </ xsd:annotation >
  </ xsd:element >
- < xsd:element name =" xmlData " minOccurs =" 0 " >
- < xsd:complexType >
- < xsd:sequence >
  < xsd:any namespace =" ##any " maxOccurs =" unbounded " />
  </ xsd:sequence >
  </ xsd:complexType >
  </ xsd:element >
  </ xsd:choice >
  < xsd:attribute name =" ID " type =" xsd:ID " use =" optional " />
  < xsd:attribute name =" MIMETYPE " type =" xsd:string " use =" optional " />
  < xsd:attributeGroup ref =" METADATA " />
  < xsd:attribute name =" LABEL " type =" xsd:string " use =" optional " />
  </ xsd:complexType >
  </ xsd:element >
  </ xsd:all >
  < xsd:attribute name =" ID " type =" xsd:ID " use =" required " />
  < xsd:attribute name =" GROUPID " type =" xsd:string " use =" optional " />
  < xsd:attribute name =" ADMID " type =" xsd:IDREFS " use =" optional " />
  < xsd:attribute name =" CREATED " type =" xsd:dateTime " use =" optional " />
  < xsd:attribute name =" STATUS " type =" xsd:string " use =" optional " />
  </ xsd:complexType >

Element mets
 
diagram
description METS: Metadata Encoding and Transmission Standard. METS is intended to provide a standardized XML format for transmission of complex digital library objects between systems. As such, it can be seen as filling a role similar to that defined for the Submission Information Package (SIP), Archival Information Package (AIP) and Dissemination Information Package (DIP) in the Reference Model for an Open Archival Information System.
attributes
uses Does not reference other elements.
 
used by
substitution hierarchy metsType --> mets
content sequence (default)
 
source
- < xsd:element name =" mets " >
- < xsd:annotation >
  < xsd:documentation > METS: Metadata Encoding and Transmission Standard. METS is intended to provide a standardized XML format for transmission of complex digital library objects between systems. As such, it can be seen as filling a role similar to that defined for the Submission Information Package (SIP), Archival Information Package (AIP) and Dissemination Information Package (DIP) in the Reference Model for an Open Archival Information System. </ xsd:documentation >
  </ xsd:annotation >
- < xsd:complexType >
- < xsd:complexContent >
  < xsd:extension base =" metsType " />
  </ xsd:complexContent >
  </ xsd:complexType >
  </ xsd:element >

Complex Type metsType
 
diagram
description mets Complex Type. A METS document consists of seven possible subsidiary sections: metsHdr (METS document header), dmdSec (descriptive metadata section), amdSec (administrative metadata section), fileGrp (file inventory group), structLink (structural map linking), structMap (structural map) and behaviorSec (behaviors section). It also has five possible attributes: 1. ID (an XML ID); 2. OBJID: a primary identifier assigned to the original source document; 3. LABEL: a title/text string identifying the document for users; 4. TYPE: a type for the object, e.g., book, journal, stereograph, etc.; and 5. PROFILE: the registered profile to which this METS document conforms. METS registry information is available from the Library of Congress at http://www.loc.gov/mets.
attributes ID   ROLE   OTHERROLE   TYPE   OTHERTYPE   ID   TYPE   ID   CREATEDATE   LASTMODDATE   RECORDSTATUS   ID   ID   OBJID   LABEL   TYPE   PROFILE  
defines locally metsHdr ? , agent * , name {xsd:string} , note {xsd:string} * , altRecordID * , dmdSec {mdSecType} * , amdSec {amdSecType} * , fileSec ? , fileGrp (0, unbounded) , structMap {structMapType} (0, unbounded) , structLink {structLinkType} ? , behaviorSec {behaviorSecType} *
uses Does not reference other elements.
 
used by
substitution hierarchy metsType
mets    
content sequence
 
Attribute Datatype Use Values Default Comments
ID { xsd:ID } optional
ROLE { } {} required possible values: CREATOR | EDITOR | ARCHIVIST | PRESERVATION | DISSEMINATOR | CUSTODIAN | IPOWNER | OTHER
OTHERROLE { xsd:string } optional
TYPE { } {} optional possible values: INDIVIDUAL | ORGANIZATION | OTHER
OTHERTYPE { xsd:string } optional
ID { xsd:ID } optional
TYPE { xsd:string } optional
ID { xsd:ID } optional
CREATEDATE { xsd:dateTime } optional
LASTMODDATE { xsd:dateTime } optional
RECORDSTATUS { xsd:string } optional
ID { xsd:ID } optional
ID { xsd:ID } optional
OBJID { xsd:string } optional
LABEL { xsd:string } optional
TYPE { xsd:string } optional
PROFILE { xsd:string } optional
 
source
- < xsd:complexType name =" metsType " >
- < xsd:annotation >
  < xsd:documentation > mets Complex Type. A METS document consists of seven possible subsidiary sections: metsHdr (METS document header), dmdSec (descriptive metadata section), amdSec (administrative metadata section), fileGrp (file inventory group), structLink (structural map linking), structMap (structural map) and behaviorSec (behaviors section). It also has five possible attributes: 1. ID (an XML ID); 2. OBJID: a primary identifier assigned to the original source document; 3. LABEL: a title/text string identifying the document for users; 4. TYPE: a type for the object, e.g., book, journal, stereograph, etc.; and 5. PROFILE: the registered profile to which this METS document conforms. METS registry information is available from the Library of Congress at http://www.loc.gov/mets. </ xsd:documentation >
  </ xsd:annotation >
- < xsd:sequence >
- < xsd:element name =" metsHdr " minOccurs =" 0 " >
- < xsd:annotation >
  < xsd:documentation > metsHdr: METS Header. Like a TEI Header, the METS Header element records metadata about the METS document itself (not the digital library object that the METS document encodes). It has two possible subsidiary elements, agent (document agent) and altRecordID. (alternative Record ID). It also has the following four attributes: 1. ID (an XML ID); 2. CREATEDATE: the date/time the METS document was created; 3. LASTMODDATE: the date/time the METS document was last modified; 4. RECORDSTATUS: a string indicating the status of the METS document, to be used mainly for internal processing purposes. </ xsd:documentation >
  </ xsd:annotation >
- < xsd:complexType >
- < xsd:sequence >
- < xsd:element name =" agent " minOccurs =" 0 " maxOccurs =" unbounded " >
- < xsd:annotation >
  < xsd:documentation > agent: METS agent. The agent element allows for various parties and their roles with respect to the METS document to be recorded. It has five attributes: 1. ID (an XML ID); 2. ROLE: one of 7 set roles with respect to the document, CREATOR, EDITOR, ARCHIVIST, PRESERVATION, DISSEMINATOR, CUSTODIAN and IPOWNER or the value OTHER to indicate a non-set role; 3. OTHERROLE: a string to specify a non-set role if OTHER is indicated in the ROLE attribute; 4. TYPE: either the set values of INDIVIDUAL agent or ORGANIZATION, or the value OTHER to indicate a non-set value; and 5. OTHERTYPE: a string to indicate the type of agent if a value of OTHER is indicated in the TYPE attribute. </ xsd:documentation >
  </ xsd:annotation >
- < xsd:complexType >
- < xsd:sequence >
  < xsd:element name =" name " type =" xsd:string " />
  < xsd:element name =" note " type =" xsd:string " minOccurs =" 0 " maxOccurs =" unbounded " />
  </ xsd:sequence >
  < xsd:attribute name =" ID " type =" xsd:ID " use =" optional " />
- < xsd:attribute name =" ROLE " use =" required " >
- < xsd:simpleType >
- < xsd:restriction base =" xsd:string " >
  < xsd:enumeration value =" CREATOR " />
  < xsd:enumeration value =" EDITOR " />
  < xsd:enumeration value =" ARCHIVIST " />
  < xsd:enumeration value =" PRESERVATION " />
  < xsd:enumeration value =" DISSEMINATOR " />
  < xsd:enumeration value =" CUSTODIAN " />
  < xsd:enumeration value =" IPOWNER " />
  < xsd:enumeration value =" OTHER " />
  </ xsd:restriction >
  </ xsd:simpleType >
  </ xsd:attribute >
  < xsd:attribute name =" OTHERROLE " type =" xsd:string " use =" optional " />
- < xsd:attribute name =" TYPE " use =" optional " >
- < xsd:simpleType >
- < xsd:restriction base =" xsd:string " >
  < xsd:enumeration value =" INDIVIDUAL " />
  < xsd:enumeration value =" ORGANIZATION " />
  < xsd:enumeration value =" OTHER " />
  </ xsd:restriction >
  </ xsd:simpleType >
  </ xsd:attribute >
  < xsd:attribute name =" OTHERTYPE " type =" xsd:string " use =" optional " />
  </ xsd:complexType >
  </ xsd:element >
- < xsd:element name =" altRecordID " minOccurs =" 0 " maxOccurs =" unbounded " >
- < xsd:annotation >
  < xsd:documentation > altRecordID: Alternative Record ID. This element allows for documentation of alternative ID values for the METS document in addition to the primary ID stored in the OBJID attribute in the root METS element. It has two attributes: 1. ID: an XML ID, and 2. TYPE: a description of the identifier type (e.g., OCLC #, LCCN, etc.). </ xsd:documentation >
  </ xsd:annotation >
- < xsd:complexType >
- < xsd:simpleContent >
- < xsd:extension base =" xsd:string " >
  < xsd:attribute name =" ID " type =" xsd:ID " use =" optional " />
  < xsd:attribute name =" TYPE " type =" xsd:string " use =" optional " />
  </ xsd:extension >
  </ xsd:simpleContent >
  </ xsd:complexType >
  </ xsd:element >
  </ xsd:sequence >
  < xsd:attribute name =" ID " type =" xsd:ID " use =" optional " />
  < xsd:attribute name =" CREATEDATE " type =" xsd:dateTime " use =" optional " />
  < xsd:attribute name =" LASTMODDATE " type =" xsd:dateTime " use =" optional " />
  < xsd:attribute name =" RECORDSTATUS " type =" xsd:string " use =" optional " />
  </ xsd:complexType >
  </ xsd:element >
- < xsd:element name =" dmdSec " type =" mdSecType " minOccurs =" 0 " maxOccurs =" unbounded " >
- < xsd:annotation >
  < xsd:documentation > dmdSec: Description Metadata Section. This section records all of the descriptive metadata for all items in the METS object (including both structural map divs and descriptive metadata for data files). Metadata can be either included in the METS hub document (mdWrap) or referenced via an identifier/locator (mdRef), a la Warwick Framework. Multiple dmdSec elements are allowed so that descriptive metadata can be recorded for each separate item within the METS object. </ xsd:documentation >
  </ xsd:annotation >
  </ xsd:element >
- < xsd:element name =" amdSec " type =" amdSecType " minOccurs =" 0 " maxOccurs =" unbounded " >
- < xsd:annotation >
  < xsd:documentation > amdSec: Administrative Metadata Section. This section records all of the administrative metadata for all items in the METS object (including structural map divs, data files, descriptive metadata sections and adminstrative metadata sections themselves), and is divided into four subsections: techMD (technical metadata), rightsMD (intellectual property rights metadata), sourceMD (analog/digital source metadata), and digiprovMD (digital provenance metadata). Each of these subsections follows the mdSecType model, so that they can either include metadata within the METS hub document (mdWrap) or reference it via an identifier/locator (mdRef). Multiple techMD, rightsMD, sourceMD and digiprovMD elements are allowed so that administrative metadata can be recorded for each separate item within the METS object. </ xsd:documentation >
  </ xsd:annotation >
  </ xsd:element >
- < xsd:element name =" fileSec " minOccurs =" 0 " >
- < xsd:annotation >
  < xsd:documentation > fileSec: Content File Section. The content file section records information regarding all of the data files which comprise the digital library object. It has a single attribute, ID. </ xsd:documentation >
  </ xsd:annotation >
- < xsd:complexType >
- < xsd:sequence >
- < xsd:element name =" fileGrp " maxOccurs =" unbounded " >
- < xsd:complexType >
- < xsd:complexContent >
  < xsd:extension base =" fileGrpType " />
  </ xsd:complexContent >
  </ xsd:complexType >
  </ xsd:element >
  </ xsd:sequence >
  < xsd:attribute name =" ID " type =" xsd:ID " use =" optional " />
  </ xsd:complexType >
  </ xsd:element >
- < xsd:element name =" structMap " type =" structMapType " maxOccurs =" unbounded " >
- < xsd:annotation >
  < xsd:documentation > structMap: Structural Map. 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. </ xsd:documentation >
  </ xsd:annotation >
  </ xsd:element >
- < xsd:element name =" structLink " type =" structLinkType " minOccurs =" 0 " >
- < xsd:annotation >
  < xsd:documentation > structLink: Structural Map Linking. The Structural Map Linking section allows for the specification of hyperlinks between different components of a METS structure delineated in a structural map. </ xsd:documentation >
  </ xsd:annotation >
  </ xsd:element >
- < xsd:element name =" behaviorSec " type =" behaviorSecType " minOccurs =" 0 " maxOccurs =" unbounded " >
- < xsd:annotation >
  < xsd:documentation > behaviorSec: Behavior Section. This section records executable behaviors that are associated with content in the METS object. </ xsd:documentation >
  </ xsd:annotation >
  </ xsd:element >
  </ xsd:sequence >
  < xsd:attribute name =" ID " type =" xsd:ID " use =" optional " />
  < xsd:attribute name =" OBJID " type =" xsd:string " use =" optional " />
  < xsd:attribute name =" LABEL " type =" xsd:string " use =" optional " />
  < xsd:attribute name =" TYPE " type =" xsd:string " use =" optional " />
  < xsd:attribute name =" PROFILE " type =" xsd:string " use =" optional " />
  </ xsd:complexType >

Complex Type objectType
 
diagram
description objectType: An element of type objectType may have the following attributes: 1. ID: an XML ID for the element 2. LABEL: a description of the object that is being linked to. 3. LOCTYPE: the type of locator contained in the FLocat element; and 4. OTHERLOCTYPE: a string to indicate an alternative LOCTYPE if the LOCTYPE attribute itself has a value of "OTHER." 5. xlink:href: see XLink standard (http://www.w3.org/TR/xlink) 6. xlink:role: "" 7. xlink:arcrole: "" 8. xlink:title: "" 9. xlink:show: "" 10. xlink:actuate: "" NOTE: objectType is an empty element. The location of the resource pointed to MUST be stored in the xlink:href element.
attributes ID   LABEL   LOCATION  xlink:simpleLink 
uses Does not reference other elements.
 
used by
content sequence (default)
 
Attribute Datatype Use Values Default Comments
ID { xsd:ID } optional
LABEL { xsd:string } optional
 
source
- < xsd:complexType name =" objectType " >
- < xsd:annotation >
  < xsd:documentation > objectType: An element of type objectType may have the following attributes: 1. ID: an XML ID for the element 2. LABEL: a description of the object that is being linked to. 3. LOCTYPE: the type of locator contained in the FLocat element; and 4. OTHERLOCTYPE: a string to indicate an alternative LOCTYPE if the LOCTYPE attribute itself has a value of "OTHER." 5. xlink:href: see XLink standard (http://www.w3.org/TR/xlink) 6. xlink:role: "" 7. xlink:arcrole: "" 8. xlink:title: "" 9. xlink:show: "" 10. xlink:actuate: "" NOTE: objectType is an empty element. The location of the resource pointed to MUST be stored in the xlink:href element. </ xsd:documentation >
  </ xsd:annotation >
  < xsd:attribute name =" ID " type =" xsd:ID " use =" optional " />
  < xsd:attribute name =" LABEL " type =" xsd:string " use =" optional " />
  < xsd:attributeGroup ref =" LOCATION " />
  < xsd:attributeGroup ref =" xlink:simpleLink " />
  </ xsd:complexType >

Complex Type seqType
 
diagram
description seq: Sequence of files. The seq element should be used to link a div to a set of content files when those files should be played/displayed sequentially to deliver content to a user. Individual area subelements within the seq element provide the links to the files or portions thereof. Seq has the following attributes: 1. ID: an XML ID for this element.
attributes ID  
defines locally area {areaType} (0, unbounded)
uses Does not reference other elements.
 
used by
content sequence
 
Attribute Datatype Use Values Default Comments
ID { xsd:ID } optional
 
source
- < xsd:complexType name =" seqType " >
- < xsd:annotation >
  < xsd:documentation > seq: Sequence of files. The seq element should be used to link a div to a set of content files when those files should be played/displayed sequentially to deliver content to a user. Individual area subelements within the seq element provide the links to the files or portions thereof. Seq has the following attributes: 1. ID: an XML ID for this element. </ xsd:documentation >
  </ xsd:annotation >
- < xsd:sequence >
  < xsd:element name =" area " type =" areaType " maxOccurs =" unbounded " />
  </ xsd:sequence >
  < xsd:attribute name =" ID " type =" xsd:ID " use =" optional " />
  </ xsd:complexType >

Complex Type structLinkType
 
diagram
description structLink: Structural Map Linking. The Structural Map Linking section allows for the specification of hyperlinks between different components of a METS structure delineated in a structural map. structLink contains a single, repeatable element, smLink. Each smLink element indicates a hyperlink between two nodes in the structMap. The nodes in smLink are identified using their XML ID attributes.
attributes         to   from  
defines locally smLink (0, unbounded)
uses Does not reference other elements.
 
used by
content sequence
 
Attribute Datatype Use Values Default Comments
{ } optional
{ } optional
{ } optional
{ } optional
to { xsd:IDREF } optional (default)
from { xsd:IDREF } optional (default)
 
source
- < xsd:complexType name =" structLinkType " >
- < xsd:annotation >
  < xsd:documentation > structLink: Structural Map Linking. The Structural Map Linking section allows for the specification of hyperlinks between different components of a METS structure delineated in a structural map. structLink contains a single, repeatable element, smLink. Each smLink element indicates a hyperlink between two nodes in the structMap. The nodes in smLink are identified using their XML ID attributes. </ xsd:documentation >
  </ xsd:annotation >
- < xsd:sequence >
- < xsd:element name =" smLink " maxOccurs =" unbounded " >
- < xsd:annotation >
  < xsd:documentation > smLink: structural map Link An element linking two elements in the structural map, used to indicate that a hyperlink exists between the two METS components represented by the two structural map nodes. You would use smLink, for example, to record the existence of hypertext links between web pages, if you wish to record those links' existence inside of METS. The smLink element uses six attributes: 1. xlink:arcrole - the role of the link, as per the xlink specification; 2. xlink:title - a title for the link (if needed); 3. xlink:show - see the xlink specification; 4. xlink:actuate - see the xlink specification; 5. to: the XML ID attribute for the element in the structMap you are linking to; and 6. from: the XML id attribute for the element in the structMap you are linking from. Note that while we use the xlink 'to' and 'from' notions, we are not using the actual xlink schema definitions, as we wish to make these XML IDREF attributes, and not simple strings. </ xsd:documentation >
  </ xsd:annotation >
- < xsd:complexType >
  < xsd:attribute ref =" xlink:arcrole " use =" optional " />
  < xsd:attribute ref =" xlink:title " use =" optional " />
  < xsd:attribute ref =" xlink:show " use =" optional " />
  < xsd:attribute ref =" xlink:actuate " use =" optional " />
  < xsd:attribute name =" to " type =" xsd:IDREF " />
  < xsd:attribute name =" from " type =" xsd:IDREF " />
  </ xsd:complexType >
  </ xsd:element >
  </ xsd:sequence >
  </ xsd:complexType >

Complex Type structMapType
 
diagram
description structMap Complex Type The structural map (structMap) outlines a hierarchical structure for the original object being encoded, using a series of nested div elements. The structMap element has the following attributes: 1. ID: an XML ID for the element; 2. TYPE: the type of structural map provided. Typical values will be "PHYSICAL" for a map which describes the physical composition of the original work (a series with individual monographs with pages) and "LOGICAL" for one which describes the intellectual structure of the work (a monograph with TOC, forward, chapters, index., etc.); 3. LABEL: a string to describe the structMap to users. This is primarily useful where more than one structMap is provided for a single object (e.g., both logical and physical structMap).
attributes ID   TYPE   LABEL  
defines locally div {divType}
uses Does not reference other elements.
 
used by
content sequence
 
Attribute Datatype Use Values Default Comments
ID { xsd:ID } optional
TYPE { xsd:string } optional
LABEL { xsd:string } optional
 
source
- < xsd:complexType name =" structMapType " >
- < xsd:annotation >
  < xsd:documentation > structMap Complex Type The structural map (structMap) outlines a hierarchical structure for the original object being encoded, using a series of nested div elements. The structMap element has the following attributes: 1. ID: an XML ID for the element; 2. TYPE: the type of structural map provided. Typical values will be "PHYSICAL" for a map which describes the physical composition of the original work (a series with individual monographs with pages) and "LOGICAL" for one which describes the intellectual structure of the work (a monograph with TOC, forward, chapters, index., etc.); 3. LABEL: a string to describe the structMap to users. This is primarily useful where more than one structMap is provided for a single object (e.g., both logical and physical structMap). </ xsd:documentation >
  </ xsd:annotation >
- < xsd:sequence >
- < xsd:element name =" div " type =" divType " >
- < xsd:annotation >
  < xsd:documentation > div: Division. 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. </ xsd:documentation >
  </ xsd:annotation >
  </ xsd:element >
  </ xsd:sequence >
  < xsd:attribute name =" ID " type =" xsd:ID " use =" optional " />
  < xsd:attribute name =" TYPE " type =" xsd:string " use =" optional " />
  < xsd:attribute name =" LABEL " type =" xsd:string " use =" optional " />
  </ xsd:complexType >

Global Attributes

 
Attribute Datatype Use Values Default Comments
LOCTYPE { } {} required possible values: URN | URL | PURL | HANDLE | DOI | OTHER
OTHERLOCTYPE { xsd:string } optional
LOCTYPE { } {} required possible values: URN | URL | PURL | HANDLE | DOI | OTHER
OTHERLOCTYPE { xsd:string } optional

 
Attribute Datatype Use Values Default Comments
MDTYPE { } {} required possible values: MARC | EAD | DC | NISOIMG | LC-AV | VRA | TEIHDR | DDI | FGDC | OTHER
OTHERMDTYPE { xsd:string } optional
MDTYPE { } {} required possible values: MARC | EAD | DC | NISOIMG | LC-AV | VRA | TEIHDR | DDI | FGDC | OTHER
OTHERMDTYPE { xsd:string } optional

DataType definitions

http://www.loc.gov/METS/ Original Schema Source

<!--
 edited with XML Spy v4.2 U (http://www.xmlspy.com) by Jerome McDonough (private) 
  -->
<!--
 METS: Metadata Encoding and Transmission Standard 
  -->
<!--
 Copyright © 2001, 2002, 2003 Digital Library Federation 
  -->
<!--
 Prepared for the Digital Library Federation by Jerome McDonough, New York University,
with the assistance of Rick Beaubien (University of California), Morgan Cundiff (Library of 
Congress), Susan Dahl (University of Alberta), Richard Gartner (Bodleian Library at Oxford),
Nancy Hoebelheirich (Stanford University), Mark Kornbluh (Michigan State University),
Cecilia Preston (Preston & Lynch), Merrilee Proffitt (Research Libraries Group),
Richard Rinehart (Berkeley Art Museum/Pacific Film Archive), Mackenzie Smith (Massachusetts
Institute of Technology), Taylor Surface (OCLC), Brian Tingle (California Digital Library) and
Robin Wendler (Harvard University).
  -->
<!--
 Dec. 27, 2002 
  -->
<!--
 Version 1.2 
  -->
<!--
 Change History 
  -->
<!--
 April 23, 2001: Alpha Draft completed 
  -->
<!--
 June 7, 2001: Beta completed 
  -->
<!--
 6/7/2001 Beta Changes: 
	1. add 'Time' as a possible time code value, as well as TCF.
	2. Make dmdSec ID attribute required; make ID attribute optional on MDRef/MDWrap.
	3. Add 'Label' attribute to StructMap, along with 'Type'.
	4. Add DDI and FGDC as potential metadata schemes to enumeration.
	5. Enable an "otherMDtype" attribute for MDWrap/MDRef and any other element where
	    there's an 'other' in the enumerated possibilities.
	6. Add a "profile" attribute to METS element.
	7. Revised mptr declaration so that it's like FLocat/MDRef (and not like XLink)
	8. Extend internal documentation of <area> attributes.
	9. Add "other" to the possible set of LOCTYPEs.
	10. Change ADMIDS to ADMID on FileGrp.
	11. Change "N" to "Order" on <div> element.
	12. Change "Number" to "order label" on <div> element
	13. Add createdate and lastmoddate attributes to mets element.
	14. Allow <div> and <area> elements to link to administrative metadata sections.
	15. Normalize attribute pointing facilities for file element and mdRef.
	16. Provide a LOCTYPE of "other" and an "otherloctype" attribute for pointing to external files.
	17. Drop PDI from enumeration of LOCTYPES.
	18. Make MDTYPE required in mdRef and mdWrap.
	19. Rename preservationMD to digiprovMD.
	20. Add optional CHECKSUM attribute to FContent element.
	21. Modularize declarations of fileGrpType and mdSecType attributes and enumerations to
		simplify maintenance.
	22. Add TYPE attribute to structMap.
	23. Declare structMap element using structMapType rather than direct declaration.
	24. Add area element as possible subelement to <div>, along with par and seq.
	25. Change mdSec model to ALL, to enable differing order of mdRef/mdWrap elements.
	26. Extend documentation on <par> and <seq> elements.
 
  -->
<!--
 October 22, 2001: Gamma completed 
  -->
<!--
 10/22/2001 Gamma changes:
 	1. Added optional fileSec element beneath METS root element to contain fileGrps.
 	2. Created subsidiary schema file xlink.xsd for XLink attributes, restored XLink attributes
 	to mptr element, and added XLink support to mdRef and FLocat.
 	3. Created new element metsHdr to handle metadata regarding METS document
 	itself (analogous to TEI Header).  Moved CREATEDATE and LASTMODDATE attributes
 	to metsHdr, and added new RECORDSTATUS attribute.  Added new subsidiary elements
 	agent and altRecordID to metsHdr.
 	4. Made CREATEDATE and LASTMODDATE attributes type xsd:dateTime to allow more precise
 	recording of when work was done.
 	5. Changed all attributes using data type of xsd:binary to xsd:base64Binary to conform to final
 	W3C schema recommendations.
 	6. Cleaned up annotations/documentation.
 
  -->
<!--
 December 19, 2001: Epsilon and PROTOFINAL completed
  -->
<!--
 12/19/2001 Epsilon changes:
 	1. Changed sequence operator for StructMap so that only 1 root div element is permitted.
	2. Add new roles to agent element's role attribute and support for extensible 'other' role.
	3. Add support for extensible 'other' type attribute on agent element.
	4. Yet more documentation clean up.
	5. Relocate CHECKSUM attribute from FContent to File element.
	6. Change the file element's CREATED attribute and fileGroup's VERSDATE attribute to 
	a type of xsd:dateTime
	7. Change attribute name DMD for div element to DMDID for consistency's sake.
	8. Added new behaviorSec for support of referencing executable code from METS object
 
  -->
<!--
 February 8, 2002: Zeta bug fix to final 
  -->
<!--
 2/8/2002 Zeta changes:
 
 	1. Eliminated redundant VRA in metadata type enumeration.
 	2. Changed mdWrap content model, adding xmlData element to eliminate
 		ambiguous content model
 
  -->
<!--
 June 3, 2002: Version 1.1 
  -->
<!--
 6/3/2002 v1.1 changes:
 
  	1. Add new structLink section for recording hyperlinks between media represented by structMap nodes.
	2. Allow a <par> element to
	contain a <seq> 
  -->
<!--
 Dec. 27, 2002: Version 1.2 
  -->
<!--
 12/27/2002 v1.2 changes:
1. Add “USE� attribute to FileGrp, File, FLocat and FContent;
2. Make FLocat repeatable;
3. Have FContent mimic mdWrap in using separate binData/xmlData sections;
4. Copyright statement added;
5. Allow both FLocat and Fcontent in single file element;
6. Allow behaviorSec elements to group through GROUPID attribute;
7. allow descriptive and administrative metadata sections to be grouped through GROUPID attribute;
8. allow <file> element to point to descriptive metadata via DMDID attribute;
9. allow descriptive metadata and all forms of administrative metadata to point to administrative metadata via ADMID attribute;
10. CREATED and STATUS attributes added to all desc. and adm. metadata sections; and
11. clean up documentation in elements to reflect reality.
  -->
- < xsd:schema targetNamespace =" http://www.loc.gov/METS/ " elementFormDefault =" qualified " attributeFormDefault =" unqualified " >
  < xsd:import namespace =" http://www.w3.org/TR/xlink " schemaLocation =" xlink.xsd " />
- < xsd:element name =" mets " >
- < xsd:annotation >
  < xsd:documentation > METS: Metadata Encoding and Transmission Standard. METS is intended to provide a standardized XML format for transmission of complex digital library objects between systems. As such, it can be seen as filling a role similar to that defined for the Submission Information Package (SIP), Archival Information Package (AIP) and Dissemination Information Package (DIP) in the Reference Model for an Open Archival Information System. </ xsd:documentation >
  </ xsd:annotation >
- < xsd:complexType >
- < xsd:complexContent >
  < xsd:extension base =" metsType " />
  </ xsd:complexContent >
  </ xsd:complexType >
  </ xsd:element >
- < xsd:complexType name =" metsType " >
- < xsd:annotation >
  < xsd:documentation > mets Complex Type. A METS document consists of seven possible subsidiary sections: metsHdr (METS document header), dmdSec (descriptive metadata section), amdSec (administrative metadata section), fileGrp (file inventory group), structLink (structural map linking), structMap (structural map) and behaviorSec (behaviors section). It also has five possible attributes: 1. ID (an XML ID); 2. OBJID: a primary identifier assigned to the original source document; 3. LABEL: a title/text string identifying the document for users; 4. TYPE: a type for the object, e.g., book, journal, stereograph, etc.; and 5. PROFILE: the registered profile to which this METS document conforms. METS registry information is available from the Library of Congress at http://www.loc.gov/mets. </ xsd:documentation >
  </ xsd:annotation >
- < xsd:sequence >
- < xsd:element name =" metsHdr " minOccurs =" 0 " >
- < xsd:annotation >
  < xsd:documentation > metsHdr: METS Header. Like a TEI Header, the METS Header element records metadata about the METS document itself (not the digital library object that the METS document encodes). It has two possible subsidiary elements, agent (document agent) and altRecordID. (alternative Record ID). It also has the following four attributes: 1. ID (an XML ID); 2. CREATEDATE: the date/time the METS document was created; 3. LASTMODDATE: the date/time the METS document was last modified; 4. RECORDSTATUS: a string indicating the status of the METS document, to be used mainly for internal processing purposes. </ xsd:documentation >
  </ xsd:annotation >
- < xsd:complexType >
- < xsd:sequence >
- < xsd:element name =" agent " minOccurs =" 0 " maxOccurs =" unbounded " >
- < xsd:annotation >
  < xsd:documentation > agent: METS agent. The agent element allows for various parties and their roles with respect to the METS document to be recorded. It has five attributes: 1. ID (an XML ID); 2. ROLE: one of 7 set roles with respect to the document, CREATOR, EDITOR, ARCHIVIST, PRESERVATION, DISSEMINATOR, CUSTODIAN and IPOWNER or the value OTHER to indicate a non-set role; 3. OTHERROLE: a string to specify a non-set role if OTHER is indicated in the ROLE attribute; 4. TYPE: either the set values of INDIVIDUAL agent or ORGANIZATION, or the value OTHER to indicate a non-set value; and 5. OTHERTYPE: a string to indicate the type of agent if a value of OTHER is indicated in the TYPE attribute. </ xsd:documentation >
  </ xsd:annotation >
- < xsd:complexType >
- < xsd:sequence >
  < xsd:element name =" name " type =" xsd:string " />
  < xsd:element name =" note " type =" xsd:string " minOccurs =" 0 " maxOccurs =" unbounded " />
  </ xsd:sequence >
  < xsd:attribute name =" ID " type =" xsd:ID " use =" optional " />
- < xsd:attribute name =" ROLE " use =" required " >
- < xsd:simpleType >
- < xsd:restriction base =" xsd:string " >
  < xsd:enumeration value =" CREATOR " />
  < xsd:enumeration value =" EDITOR " />
  < xsd:enumeration value =" ARCHIVIST " />
  < xsd:enumeration value =" PRESERVATION " />
  < xsd:enumeration value =" DISSEMINATOR " />
  < xsd:enumeration value =" CUSTODIAN " />
  < xsd:enumeration value =" IPOWNER " />
  < xsd:enumeration value =" OTHER " />
  </ xsd:restriction >
  </ xsd:simpleType >
  </ xsd:attribute >
  < xsd:attribute name =" OTHERROLE " type =" xsd:string " use =" optional " />
- < xsd:attribute name =" TYPE " use =" optional " >
- < xsd:simpleType >
- < xsd:restriction base =" xsd:string " >
  < xsd:enumeration value =" INDIVIDUAL " />
  < xsd:enumeration value =" ORGANIZATION " />
  < xsd:enumeration value =" OTHER " />
  </ xsd:restriction >
  </ xsd:simpleType >
  </ xsd:attribute >
  < xsd:attribute name =" OTHERTYPE " type =" xsd:string " use =" optional " />
  </ xsd:complexType >
  </ xsd:element >
- < xsd:element name =" altRecordID " minOccurs =" 0 " maxOccurs =" unbounded " >
- < xsd:annotation >
  < xsd:documentation > altRecordID: Alternative Record ID. This element allows for documentation of alternative ID values for the METS document in addition to the primary ID stored in the OBJID attribute in the root METS element. It has two attributes: 1. ID: an XML ID, and 2. TYPE: a description of the identifier type (e.g., OCLC #, LCCN, etc.). </ xsd:documentation >
  </ xsd:annotation >
- < xsd:complexType >
- < xsd:simpleContent >
- < xsd:extension base =" xsd:string " >
  < xsd:attribute name =" ID " type =" xsd:ID " use =" optional " />
  < xsd:attribute name =" TYPE " type =" xsd:string " use =" optional " />
  </ xsd:extension >
  </ xsd:simpleContent >
  </ xsd:complexType >
  </ xsd:element >
  </ xsd:sequence >
  < xsd:attribute name =" ID " type =" xsd:ID " use =" optional " />
  < xsd:attribute name =" CREATEDATE " type =" xsd:dateTime " use =" optional " />
  < xsd:attribute name =" LASTMODDATE " type =" xsd:dateTime " use =" optional " />
  < xsd:attribute name =" RECORDSTATUS " type =" xsd:string " use =" optional " />
  </ xsd:complexType >
  </ xsd:element >
- < xsd:element name =" dmdSec " type =" mdSecType " minOccurs =" 0 " maxOccurs =" unbounded " >
- < xsd:annotation >
  < xsd:documentation > dmdSec: Description Metadata Section. This section records all of the descriptive metadata for all items in the METS object (including both structural map divs and descriptive metadata for data files). Metadata can be either included in the METS hub document (mdWrap) or referenced via an identifier/locator (mdRef), a la Warwick Framework. Multiple dmdSec elements are allowed so that descriptive metadata can be recorded for each separate item within the METS object. </ xsd:documentation >
  </ xsd:annotation >
  </ xsd:element >
- < xsd:element name =" amdSec " type =" amdSecType " minOccurs =" 0 " maxOccurs =" unbounded " >
- < xsd:annotation >
  < xsd:documentation > amdSec: Administrative Metadata Section. This section records all of the administrative metadata for all items in the METS object (including structural map divs, data files, descriptive metadata sections and adminstrative metadata sections themselves), and is divided into four subsections: techMD (technical metadata), rightsMD (intellectual property rights metadata), sourceMD (analog/digital source metadata), and digiprovMD (digital provenance metadata). Each of these subsections follows the mdSecType model, so that they can either include metadata within the METS hub document (mdWrap) or reference it via an identifier/locator (mdRef). Multiple techMD, rightsMD, sourceMD and digiprovMD elements are allowed so that administrative metadata can be recorded for each separate item within the METS object. </ xsd:documentation >
  </ xsd:annotation >
  </ xsd:element >
- < xsd:element name =" fileSec " minOccurs =" 0 " >
- < xsd:annotation >
  < xsd:documentation > fileSec: Content File Section. The content file section records information regarding all of the data files which comprise the digital library object. It has a single attribute, ID. </ xsd:documentation >
  </ xsd:annotation >
- < xsd:complexType >
- < xsd:sequence >
- < xsd:element name =" fileGrp " maxOccurs =" unbounded " >
- < xsd:complexType >
- < xsd:complexContent >
  < xsd:extension base =" fileGrpType " />
  </ xsd:complexContent >
  </ xsd:complexType >
  </ xsd:element >
  </ xsd:sequence >
  < xsd:attribute name =" ID " type =" xsd:ID " use =" optional " />
  </ xsd:complexType >
  </ xsd:element >
- < xsd:element name =" structMap " type =" structMapType " maxOccurs =" unbounded " >
- < xsd:annotation >
  < xsd:documentation > structMap: Structural Map. 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. </ xsd:documentation >
  </ xsd:annotation >
  </ xsd:element >
- < xsd:element name =" structLink " type =" structLinkType " minOccurs =" 0 " >
- < xsd:annotation >
  < xsd:documentation > structLink: Structural Map Linking. The Structural Map Linking section allows for the specification of hyperlinks between different components of a METS structure delineated in a structural map. </ xsd:documentation >
  </ xsd:annotation >
  </ xsd:element >
- < xsd:element name =" behaviorSec " type =" behaviorSecType " minOccurs =" 0 " maxOccurs =" unbounded " >
- < xsd:annotation >
  < xsd:documentation > behaviorSec: Behavior Section. This section records executable behaviors that are associated with content in the METS object. </ xsd:documentation >
  </ xsd:annotation >
  </ xsd:element >
  </ xsd:sequence >
  < xsd:attribute name =" ID " type =" xsd:ID " use =" optional " />
  < xsd:attribute name =" OBJID " type =" xsd:string " use =" optional " />
  < xsd:attribute name =" LABEL " type =" xsd:string " use =" optional " />
  < xsd:attribute name =" TYPE " type =" xsd:string " use =" optional " />
  < xsd:attribute name =" PROFILE " type =" xsd:string " use =" optional " />
  </ xsd:complexType >
- < 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 >
- < xsd:complexType name =" fileGrpType " >
- < xsd:annotation >
  < xsd:documentation > fileGrp: File Group. The file group is used to cluster all of the digital files composing a digital library object in a hierarchical arrangement (fileGrp is recursively defined to enable the creation of the hierarchy). Any file group may contain zero or more file elements. File elements in turn can contain one or more FLocat elements (a pointer to a file containing content for this object) and/or a FContent element (the contents of the file, in either XML or Base64 encoding). A fileGrp element may have the following attributes: 1. ID: an XML ID for the element 2. VERSDATE: date this version/fileGrp of the digital object was created. 3. ADMID: IDREFs to administrative metadata sections in the METS document that correspond with all files in this file group; 4. USE: a string to indicate the intended use of files within this file group (e.g., master, reference, thumbnails for image files). </ xsd:documentation >
  </ xsd:annotation >
- < xsd:choice >
  < xsd:element name =" fileGrp " type =" fileGrpType " minOccurs =" 0 " maxOccurs =" unbounded " />
- < xsd:element name =" file " minOccurs =" 0 " maxOccurs =" unbounded " >
- < xsd:annotation >
  < xsd:documentation > file: File element. The file element provides access to content files for a METS document. A file element may contain one or more FLocat elements, which provide pointers to a content file, and/or an FContent element, which wraps an encoded version of the file. Note that ALL FLocat and FContent elements underneath a singel file element should identify/contain identical copies of a single file. The file element has the following attributes: 1. ID: an XML ID for the element; 2. MIMETYPE: the MIME type for the file; 3. SEQ: an integer indicating the sequence of this file relative to the others in its file group; 4. SIZE: the size of the file in bytes; 5. CREATED: the date of creation for the file; 6. CHECKSUM: an MD5 digest value for the included file. 7. OWNERID: a primary identifier assigned to the file by its owner; 8. ADMID: IDREFS to administrative metadata sections in the METS document that correspond with this file; 9. DMDID: IDREFS to descriptive metadata sections in the METS document that correspond with this file; 10. GROUPID: an identifier that establishes a correspondence between this file and files in other file groups. Typically, this will be used to associate a master file in one file group with derivative files in other file groups; 11. USE: a string indicated the intended use of this file (e.g., master, reference, thumbnail for image files). </ xsd:documentation >
  </ xsd:annotation >
- < xsd:complexType >
- < xsd:sequence >
- < xsd:element name =" FLocat " minOccurs =" 0 " maxOccurs =" unbounded " >
- < xsd:annotation >
  < xsd:documentation > FLocat: File Location. The FLocat element provides a pointer to the location of a content file. It uses the XLink syntax to provide linking information indicating the actual location of the content file, along with a few additional attributes specifying additional linking information. The full attribute set for the FLocat element is as follows: 1. ID (an XML ID); 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. USE: a string indicating the intended use of the referenced file; 5. xlink:href: see XLink standard (http://www.w3.org/TR/xlink); 6. xlink:role: "" 7. xlink:arcrole: "" 8. xlink:title: "" 9. xlink:show: "" 10. xlink:actuate: "" NOTE: FLocat 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:attribute name =" USE " type =" xsd:string " use =" optional " />
  < xsd:attributeGroup ref =" xlink:simpleLink " />
  </ xsd:complexType >
  </ xsd:element >
- < xsd:element name =" FContent " minOccurs =" 0 " >
- < xsd:annotation >
  < xsd:documentation > FContent: file content. The FContent element is used to deliver a content file for a METS document within the METS file itself. The content file must be either Base 64 encoded, and contained within the subsidiary binData wrapper element, or consist of XML information and be contained within the subsidiary xmlData wrapper element. The FContent element has the following attribute: 1. ID (an XML ID) 2. USE: a string indicating the intended use of the embedded file. </ xsd:documentation >
  </ xsd:annotation >
- < xsd:complexType >
- < xsd:choice >
- < xsd:element name =" binData " type =" xsd:base64Binary " minOccurs =" 0 " >
- < xsd:annotation >
  < xsd:documentation > A wrapper to contain a Base64 encoded file. </ xsd:documentation >
  </ xsd:annotation >
  </ xsd:element >
- < xsd:element name =" xmlData " minOccurs =" 0 " >
- < xsd:annotation >
  < xsd:documentation > A wrapper to contain an XML encoded file. </ xsd:documentation >
  </ xsd:annotation >
- < xsd:complexType >
- < xsd:sequence >
  < xsd:any namespace =" ##any " maxOccurs =" unbounded " />
  </ xsd:sequence >
  </ xsd:complexType >
  </ xsd:element >
  </ xsd:choice >
  < xsd:attribute name =" USE " type =" xsd:string " use =" optional " />
  </ xsd:complexType >
  </ xsd:element >
  </ xsd:sequence >
  < xsd:attribute name =" ID " type =" xsd:ID " use =" required " />
  < xsd:attribute name =" MIMETYPE " type =" xsd:string " use =" optional " />
  < xsd:attribute name =" SEQ " type =" xsd:int " use =" optional " />
  < xsd:attribute name =" SIZE " type =" xsd:long " use =" optional " />
  < xsd:attribute name =" CREATED " type =" xsd:dateTime " use =" optional " />
  < xsd:attribute name =" CHECKSUM " type =" xsd:string " use =" optional " />
  < xsd:attribute name =" OWNERID " type =" xsd:string " use =" optional " />
  < xsd:attribute name =" ADMID " type =" xsd:IDREFS " use =" optional " />
  < xsd:attribute name =" DMDID " type =" xsd:IDREFS " use =" optional " />
  < xsd:attribute name =" GROUPID " type =" xsd:string " use =" optional " />
  < xsd:attribute name =" USE " type =" xsd:string " use =" optional " />
  </ xsd:complexType >
  </ xsd:element >
  </ xsd:choice >
  < xsd:attribute name =" ID " type =" xsd:ID " use =" optional " />
  < xsd:attribute name =" VERSDATE " type =" xsd:dateTime " use =" optional " />
  < xsd:attribute name =" ADMID " type =" xsd:IDREFS " use =" optional " />
  < xsd:attribute name =" USE " type =" xsd:string " use =" optional " />
  </ xsd:complexType >
- < xsd:complexType name =" structMapType " >
- < xsd:annotation >
  < xsd:documentation > structMap Complex Type The structural map (structMap) outlines a hierarchical structure for the original object being encoded, using a series of nested div elements. The structMap element has the following attributes: 1. ID: an XML ID for the element; 2. TYPE: the type of structural map provided. Typical values will be "PHYSICAL" for a map which describes the physical composition of the original work (a series with individual monographs with pages) and "LOGICAL" for one which describes the intellectual structure of the work (a monograph with TOC, forward, chapters, index., etc.); 3. LABEL: a string to describe the structMap to users. This is primarily useful where more than one structMap is provided for a single object (e.g., both logical and physical structMap). </ xsd:documentation >
  </ xsd:annotation >
- < xsd:sequence >
- < xsd:element name =" div " type =" divType " >
- < xsd:annotation >
  < xsd:documentation > div: Division. 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. </ xsd:documentation >
  </ xsd:annotation >
  </ xsd:element >
  </ xsd:sequence >
  < xsd:attribute name =" ID " type =" xsd:ID " use =" optional " />
  < xsd:attribute name =" TYPE " type =" xsd:string " use =" optional " />
  < xsd:attribute name =" LABEL " type =" xsd:string " use =" optional " />
  </ xsd:complexType >
- < 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 " />
  < xsd:attribute name =" DMDID " type =" xsd:IDREFS " use =" optional " />
  < xsd:attribute name =" ADMID " type =" xsd:IDREFS " use =" optional " />
  < xsd:attribute name =" TYPE " type =" xsd:string " use =" optional " />
  </ xsd:complexType >
- < xsd:complexType name =" seqType " >
- < xsd:annotation >
  < xsd:documentation > seq: Sequence of files. The seq element should be used to link a div to a set of content files when those files should be played/displayed sequentially to deliver content to a user. Individual area subelements within the seq element provide the links to the files or portions thereof. Seq has the following attributes: 1. ID: an XML ID for this element. </ xsd:documentation >
  </ xsd:annotation >
- < xsd:sequence >
  < xsd:element name =" area " type =" areaType " maxOccurs =" unbounded " />
  </ xsd:sequence >
  < xsd:attribute name =" ID " type =" xsd:ID " use =" optional " />
  </ xsd:complexType >
- < 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 >
- < xsd:complexType name =" structLinkType " >
- < xsd:annotation >
  < xsd:documentation > structLink: Structural Map Linking. The Structural Map Linking section allows for the specification of hyperlinks between different components of a METS structure delineated in a structural map. structLink contains a single, repeatable element, smLink. Each smLink element indicates a hyperlink between two nodes in the structMap. The nodes in smLink are identified using their XML ID attributes. </ xsd:documentation >
  </ xsd:annotation >
- < xsd:sequence >
- < xsd:element name =" smLink " maxOccurs =" unbounded " >
- < xsd:annotation >
  < xsd:documentation > smLink: structural map Link An element linking two elements in the structural map, used to indicate that a hyperlink exists between the two METS components represented by the two structural map nodes. You would use smLink, for example, to record the existence of hypertext links between web pages, if you wish to record those links' existence inside of METS. The smLink element uses six attributes: 1. xlink:arcrole - the role of the link, as per the xlink specification; 2. xlink:title - a title for the link (if needed); 3. xlink:show - see the xlink specification; 4. xlink:actuate - see the xlink specification; 5. to: the XML ID attribute for the element in the structMap you are linking to; and 6. from: the XML id attribute for the element in the structMap you are linking from. Note that while we use the xlink 'to' and 'from' notions, we are not using the actual xlink schema definitions, as we wish to make these XML IDREF attributes, and not simple strings. </ xsd:documentation >
  </ xsd:annotation >
- < xsd:complexType >
  < xsd:attribute ref =" xlink:arcrole " use =" optional " />
  < xsd:attribute ref =" xlink:title " use =" optional " />
  < xsd:attribute ref =" xlink:show " use =" optional " />
  < xsd:attribute ref =" xlink:actuate " use =" optional " />
  < xsd:attribute name =" to " type =" xsd:IDREF " />
  < xsd:attribute name =" from " type =" xsd:IDREF " />
  </ xsd:complexType >
  </ xsd:element >
  </ xsd:sequence >
  </ xsd:complexType >
- < 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 >
- < xsd:complexType name =" objectType " >
- < xsd:annotation >
  < xsd:documentation > objectType: An element of type objectType may have the following attributes: 1. ID: an XML ID for the element 2. LABEL: a description of the object that is being linked to. 3. LOCTYPE: the type of locator contained in the FLocat element; and 4. OTHERLOCTYPE: a string to indicate an alternative LOCTYPE if the LOCTYPE attribute itself has a value of "OTHER." 5. xlink:href: see XLink standard (http://www.w3.org/TR/xlink) 6. xlink:role: "" 7. xlink:arcrole: "" 8. xlink:title: "" 9. xlink:show: "" 10. xlink:actuate: "" NOTE: objectType is an empty element. The location of the resource pointed to MUST be stored in the xlink:href element. </ xsd:documentation >
  </ xsd:annotation >
  < xsd:attribute name =" ID " type =" xsd:ID " use =" optional " />
  < xsd:attribute name =" LABEL " type =" xsd:string " use =" optional " />
  < xsd:attributeGroup ref =" LOCATION " />
  < xsd:attributeGroup ref =" xlink:simpleLink " />
  </ xsd:complexType >
- < xsd:complexType name =" mdSecType " >
- < xsd:annotation >
  < xsd:documentation > mdSec (metadata section) Complex Type A generic framework for pointing to/including metadata within a METS document, a la Warwick Framework. An mdSec element may have the following attributes: 1. ID: an XML ID for this element; 2. GROUPID: an identifier that may be used to indicate that different metadata sections may be considered as part of a single group. Two metadata sections with the same GROUPID value are to be considered part of the same group. This facility might be used, for example, to group changed versions of the same metadata if previous versions are maintained in a file for tracking purposes; 3. ADMID: a set of IDREFS to administrative metadata elements which apply to the current descriptive or administrative metadata. Typically used to reference preservation metadata which applies to the current metadata; 4. CREATED: the date and time of creation for the metadata; and 5. STATUS: a string indicating the status of this metadata (e.g., superceded, current, etc.). </ xsd:documentation >
  </ xsd:annotation >
- < xsd:all >
- < xsd:element name =" mdRef " minOccurs =" 0 " >
- < xsd:annotation >
  < xsd:documentation > mdRef: metadata reference. The mdRef element is a generic element used throughout the METS schema to provide a pointer to metadata which resides outside the METS document. It has the following attributes: 1. ID: an XML ID; 2. LOCTYPE: the type of locator contained in the body of the element; 3. OTHERLOCTYPE: a string indicating an alternative LOCTYPE when the LOCTYPE attribute value is set to "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: "" 10. MIMETYPE: the MIME type for the metadata being pointed at; 11. MDType: the type of metadata being pointed at (e.g., MARC, EAD, etc.); 12. OTHERMDTYPE: a string indicating an alternative MDTYPE when the MDTYPE attribute value is set to "OTHER."; 13. LABEL: a label to display to the viewer of the METS document identifying the metadata; and 14. XPTR: an xptr to a location within the file pointed to by the mdRef element, if applicable. NB: mdRef is an empty element. The location of the metadata must be recorded in the xlink:href attribute, supplemented by the XPTR attribute as needed. </ 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:attributeGroup ref =" METADATA " />
  < xsd:attribute name =" MIMETYPE " type =" xsd:string " use =" optional " />
  < xsd:attribute name =" LABEL " type =" xsd:string " use =" optional " />
  < xsd:attribute name =" XPTR " type =" xsd:string " use =" optional " />
  </ xsd:complexType >
  </ xsd:element >
- < xsd:element name =" mdWrap " minOccurs =" 0 " >
- < xsd:annotation >
  < xsd:documentation > mdWrap: metadata wrapper. The mdWrap element is a generic element used throughout the METS schema to allow the encoder to place arbitrary metadata conforming to other standards/schema within a METS document. The included metadata can either be encoded in XML, in which case it may be placed directly within the mdWrap element, or it can be Base64 encoded, and placed within a subsidiary binData element. The mdWrap element can have the following attributes: 1. ID: an XML ID for this element; 2. MIMETYPE: the MIME type for the metadata contained in the element; 3. MDType: the type of metadata contained (e.g., MARC, EAD, etc.); 4. OTHERMDTYPE: a string indicating an alternative MDTYPE when the MDTYPE attribute value is set to "OTHER."; 5. LABEL: a label to display to the viewer of the METS document identifying the metadata. </ xsd:documentation >
  </ xsd:annotation >
- < xsd:complexType >
- < xsd:choice >
- < xsd:element name =" binData " type =" xsd:base64Binary " minOccurs =" 0 " >
- < xsd:annotation >
  < xsd:documentation > A wrapper to contain Base64 encoded metadata. </ xsd:documentation >
  </ xsd:annotation >
  </ xsd:element >
- < xsd:element name =" xmlData " minOccurs =" 0 " >
- < xsd:complexType >
- < xsd:sequence >
  < xsd:any namespace =" ##any " maxOccurs =" unbounded " />
  </ xsd:sequence >
  </ xsd:complexType >
  </ xsd:element >
  </ xsd:choice >
  < xsd:attribute name =" ID " type =" xsd:ID " use =" optional " />
  < xsd:attribute name =" MIMETYPE " type =" xsd:string " use =" optional " />
  < xsd:attributeGroup ref =" METADATA " />
  < xsd:attribute name =" LABEL " type =" xsd:string " use =" optional " />
  </ xsd:complexType >
  </ xsd:element >
  </ xsd:all >
  < xsd:attribute name =" ID " type =" xsd:ID " use =" required " />
  < xsd:attribute name =" GROUPID " type =" xsd:string " use =" optional " />
  < xsd:attribute name =" ADMID " type =" xsd:IDREFS " use =" optional " />
  < xsd:attribute name =" CREATED " type =" xsd:dateTime " use =" optional " />
  < xsd:attribute name =" STATUS " type =" xsd:string " use =" optional " />
  </ xsd:complexType >
- < xsd:attributeGroup name =" METADATA " >
- < xsd:attribute name =" MDTYPE " use =" required " >
- < xsd:simpleType >
- < xsd:restriction base =" xsd:string " >
  < xsd:enumeration value =" MARC " />
  < xsd:enumeration value =" EAD " />
  < xsd:enumeration value =" DC " />
  < xsd:enumeration value =" NISOIMG " />
  < xsd:enumeration value =" LC-AV " />
  < xsd:enumeration value =" VRA " />
  < xsd:enumeration value =" TEIHDR " />
  < xsd:enumeration value =" DDI " />
  < xsd:enumeration value =" FGDC " />
  < xsd:enumeration value =" OTHER " />
  </ xsd:restriction >
  </ xsd:simpleType >
  </ xsd:attribute >
  < xsd:attribute name =" OTHERMDTYPE " type =" xsd:string " use =" optional " />
  </ xsd:attributeGroup >
- < xsd:attributeGroup name =" LOCATION " >
- < xsd:attribute name =" LOCTYPE " use =" required " >
- < xsd:simpleType >
- < xsd:restriction base =" xsd:string " >
  < xsd:enumeration value =" URN " />
  < xsd:enumeration value =" URL " />
  < xsd:enumeration value =" PURL " />
  < xsd:enumeration value =" HANDLE " />
  < xsd:enumeration value =" DOI " />
  < xsd:enumeration value =" OTHER " />
  </ xsd:restriction >
  </ xsd:simpleType >
  </ xsd:attribute >
  < xsd:attribute name =" OTHERLOCTYPE " type =" xsd:string " use =" optional " />
  </ xsd:attributeGroup >
  </ xsd:schema >