Showing:

Annotations
Attributes
Diagrams
Instances
Model
Properties
Source
Used by
Main schema mets.xsd
Namespace http://www.loc.gov/METS/v2
Annotations
 
METS: Metadata Encoding and Transmission Standard, version 2

      This document is available under the Creative Commons CC0 1.0 Universal Public Domain Dedication (http://creativecommons.org/publicdomain/zero/1.0/).
      The METS Editorial Board, as creator of this document, has waived all rights to it worldwide under copyright law, including
      all related and neighboring rights, to the extent allowed by law. For the full text see http://creativecommons.org/publicdomain/zero/1.0/legalcode.

      Prepared by the METS Editorial Board

      Karin Bredenberg (Sydarkivera, Sweden)
      Bertrand Caron (Bibliothèque nationale de France)
      Aaron Elkiss (HathiTrust / University of Michigan)
      Inge Hofsink (KB National Library of the Netherlands)
      Juha Lehtonen (CSC – IT Center for Science, Finland)
      Andreas Nef (Docuteam GmbH, Baden, Switzerland)
      Tobias Steinke (German National Library)
      Robin Wendler (Harvard University)

      August, 2023
      Version 2.0 beta

      For version 1.x credits, change log, and documentation, see https://www.loc.gov/standards/mets/mets.xsd
 
This schema is a major revision of the METS schema. A white paper describing the new version and the rationale for the differences between the two is available: https://github.com/mets/METS-schema/blob/mets2/METS2.md.

      The latest draft of this schema is available at https://github.com/mets/METS-schema/blob/mets2/v2/mets.xsd.

      METS 2 will live alongside METS 1; METS 1 will continue to be supported and maintained.
 
Change Log

      2.0 alpha - August 17, 2022

      Initial public draft

      2.0 beta - Nov 15, 2022

      * Add links to recommended schema attributes
      * Remove transformfile references to behaviorSec; transformfile@TRANSFORMBEHAVIOR

      2.0 final - DATE TBD, 2024

      * Edit documentation elements to clarify usage and remove references to the METS 1 Primer
Properties
attribute form default unqualified
element form default qualified
Element mets
Namespace http://www.loc.gov/METS/v2
Annotations
 
METS: Metadata Encoding and Transmission Standard.
METS is intended to provide a standardized XML format for transmission of complex digital 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. The root element <mets> establishes the container for the information being stored and/or transmitted by the standard.
Diagram
Type extension of metsType
Type hierarchy
Properties
content complex
Model
Children fileSec, mdSec, metsHdr, structSec
Instance
 
<mets ID="" LABEL="" OBJID="" PROFILE="" TYPE="" xmlns="http://www.loc.gov/METS/v2">
  <metsHdr CREATEDATE="" ID="" LASTMODDATE="" MDID="" RECORDSTATUS="">{0,1}</metsHdr>
  <mdSec ID="">{0,1}</mdSec>
  <fileSec ID="">{0,1}</fileSec>
  <structSec ID="">{0,1}</structSec>
</mets>
Attributes
QName Type Use Annotation
ID xsd:ID optional 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
LABEL xsd:string optional 
LABEL (string/O): Is a simple title string used to identify the object/entity being described in the METS document for the user.
OBJID xsd:string optional 
OBJID (string/O): Is the primary identifier assigned to the METS object as a whole. Although this attribute is not required, it is strongly recommended. This identifier is used to tag the entire METS object to external systems, in contrast with the ID identifier.
PROFILE xsd:string optional 
PROFILE (string/O): Indicates the URI of the METS Profile this METS document conforms to.
TYPE xsd:string optional 
TYPE (string/O): Specifies the class or type of the object.

          Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#metstype
Wildcard: ANY attribute from ANY namespace OTHER than 'http://www.loc.gov/METS/v2'
Source
 
<xsd:element name="mets">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">METS: Metadata Encoding and Transmission Standard. METS is intended to provide a standardized XML format for transmission of complex digital 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. The root element <mets> establishes the container for the information being stored and/or transmitted by the standard.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:complexContent>
      <xsd:extension base="metsType"/>
    </xsd:complexContent>
  </xsd:complexType>
</xsd:element>
Element metsType / metsHdr
Namespace http://www.loc.gov/METS/v2
Annotations
 
The mets header element <metsHdr> captures metadata about the METS document itself, not the digital object the METS document encodes.
Diagram
Properties
content complex
minOccurs 0
Model
Children agent, altRecordID, metsDocumentID
Instance
 
<metsHdr CREATEDATE="" ID="" LASTMODDATE="" MDID="" RECORDSTATUS="" xmlns="http://www.loc.gov/METS/v2">
  <agent ID="" ROLE="" TYPE="">{0,unbounded}</agent>
  <altRecordID ID="" TYPE="">{0,unbounded}</altRecordID>
  <metsDocumentID ID="" TYPE="">{0,1}</metsDocumentID>
</metsHdr>
Attributes
QName Type Use Annotation
CREATEDATE xsd:dateTime optional 
CREATEDATE (dateTime/O): Records the date/time the METS document was created.
ID xsd:ID optional 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
LASTMODDATE xsd:dateTime optional 
LASTMODDATE (dateTime/O): Is used to indicate the date/time the METS document was last modified.
MDID xsd:IDREFS optional 
MDID (IDREFS/O): Contains the ID attribute values of the <md> elements within the <mdSec> of the METS document that contain metadata pertaining to the METS document itself.
RECORDSTATUS xsd:string optional 
RECORDSTATUS (string/O): Specifies the status of the METS document. It is used for internal processing purposes.
Wildcard: ANY attribute from ANY namespace OTHER than 'http://www.loc.gov/METS/v2'
Source
 
<xsd:element name="metsHdr" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The mets header element <metsHdr> captures metadata about the METS document itself, not the digital object the METS document encodes.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="agent" minOccurs="0" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">agent: The agent element <agent> provides for various parties and their roles with respect to the METS document to be documented.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element name="name" type="xsd:string">
              <xsd:annotation>
                <xsd:documentation xml:lang="en">The element <name> can be used to record the full name of the METS document agent.</xsd:documentation>
              </xsd:annotation>
            </xsd:element>
            <xsd:element name="note" minOccurs="0" maxOccurs="unbounded">
              <xsd:annotation>
                <xsd:documentation xml:lang="en">The <note> element can be used to record any additional information regarding the agent's activities with respect to the METS document.</xsd:documentation>
              </xsd:annotation>
              <xsd:complexType>
                <xsd:simpleContent>
                  <xsd:extension base="xsd:string">
                    <xsd:anyAttribute namespace="##other" processContents="lax"/>
                  </xsd:extension>
                </xsd:simpleContent>
              </xsd:complexType>
            </xsd:element>
          </xsd:sequence>
          <xsd:attribute name="ID" type="xsd:ID" use="optional">
            <xsd:annotation>
              <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
            </xsd:annotation>
          </xsd:attribute>
          <xsd:attribute name="ROLE" use="required" type="xsd:string">
            <xsd:annotation>
              <xsd:documentation xml:lang="en">ROLE (string/R): Specifies the function of the agent with respect to the METS document. Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#agentrole</xsd:documentation>
            </xsd:annotation>
          </xsd:attribute>
          <xsd:attribute name="TYPE" use="optional" type="xsd:string">
            <xsd:annotation>
              <xsd:documentation xml:lang="en">TYPE (string/O): is used to specify the type of AGENT. Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#agenttype</xsd:documentation>
            </xsd:annotation>
          </xsd:attribute>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="altRecordID" minOccurs="0" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">The alternative record identifier element <altRecordID> allows one to use alternative record identifier values for the digital object represented by the METS document; the primary record identifier is stored in the OBJID attribute in the root <mets> element.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:simpleContent>
            <xsd:extension base="xsd:string">
              <xsd:attribute name="ID" type="xsd:ID" use="optional">
                <xsd:annotation>
                  <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
                </xsd:annotation>
              </xsd:attribute>
              <xsd:attribute name="TYPE" type="xsd:string" use="optional">
                <xsd:annotation>
                  <xsd:documentation xml:lang="en">TYPE (string/O): A description of the identifier type. Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#altrecordidtype</xsd:documentation>
                </xsd:annotation>
              </xsd:attribute>
            </xsd:extension>
          </xsd:simpleContent>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="metsDocumentID" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">The metsDocument identifier element <metsDocumentID> allows a unique identifier to be assigned to the METS document itself. This may be different from the OBJID attribute value in the root <mets> element, which uniquely identifies the entire digital object represented by the METS document.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:simpleContent>
            <xsd:extension base="xsd:string">
              <xsd:attribute name="ID" type="xsd:ID" use="optional">
                <xsd:annotation>
                  <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
                </xsd:annotation>
              </xsd:attribute>
              <xsd:attribute name="TYPE" type="xsd:string" use="optional">
                <xsd:annotation>
                  <xsd:documentation xml:lang="en">TYPE (string/O): A description of the identifier type. Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#metsdocumentidtype</xsd:documentation>
                </xsd:annotation>
              </xsd:attribute>
            </xsd:extension>
          </xsd:simpleContent>
        </xsd:complexType>
      </xsd:element>
    </xsd:sequence>
    <xsd:attribute name="ID" type="xsd:ID" use="optional">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="MDID" type="xsd:IDREFS" use="optional">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">MDID (IDREFS/O): Contains the ID attribute values of the <md> elements within the <mdSec> of the METS document that contain metadata pertaining to the METS document itself.</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="CREATEDATE" type="xsd:dateTime" use="optional">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">CREATEDATE (dateTime/O): Records the date/time the METS document was created.</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="LASTMODDATE" type="xsd:dateTime" use="optional">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">LASTMODDATE (dateTime/O): Is used to indicate the date/time the METS document was last modified.</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="RECORDSTATUS" type="xsd:string" use="optional">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">RECORDSTATUS (string/O): Specifies the status of the METS document. It is used for internal processing purposes.</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:anyAttribute namespace="##other" processContents="lax"/>
  </xsd:complexType>
</xsd:element>
Element metsType / metsHdr / agent
Namespace http://www.loc.gov/METS/v2
Annotations
 
agent:
The agent element <agent> provides for various parties and their roles with respect to the METS document to be documented.
Diagram
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children name, note
Instance
 
<agent ID="" ROLE="" TYPE="" xmlns="http://www.loc.gov/METS/v2">
  <name>{1,1}</name>
  <note>{0,unbounded}</note>
</agent>
Attributes
QName Type Use Annotation
ID xsd:ID optional 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
ROLE xsd:string required 
ROLE (string/R): Specifies the function of the agent with respect to the METS document.
Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#agentrole
TYPE xsd:string optional 
TYPE (string/O): is used to specify the type of AGENT.
Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#agenttype
Source
 
<xsd:element name="agent" minOccurs="0" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">agent: The agent element <agent> provides for various parties and their roles with respect to the METS document to be documented.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="name" type="xsd:string">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">The element <name> can be used to record the full name of the METS document agent.</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="note" minOccurs="0" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">The <note> element can be used to record any additional information regarding the agent's activities with respect to the METS document.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:simpleContent>
            <xsd:extension base="xsd:string">
              <xsd:anyAttribute namespace="##other" processContents="lax"/>
            </xsd:extension>
          </xsd:simpleContent>
        </xsd:complexType>
      </xsd:element>
    </xsd:sequence>
    <xsd:attribute name="ID" type="xsd:ID" use="optional">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="ROLE" use="required" type="xsd:string">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">ROLE (string/R): Specifies the function of the agent with respect to the METS document. Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#agentrole</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="TYPE" use="optional" type="xsd:string">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">TYPE (string/O): is used to specify the type of AGENT. Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#agenttype</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
  </xsd:complexType>
</xsd:element>
Element metsType / metsHdr / agent / name
Namespace http://www.loc.gov/METS/v2
Annotations
 
The element <name> can be used to record the full name of the METS document agent.
Diagram
Type xsd:string
Properties
content simple
Source
 
<xsd:element name="name" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The element <name> can be used to record the full name of the METS document agent.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
Element metsType / metsHdr / agent / note
Namespace http://www.loc.gov/METS/v2
Annotations
 
The <note> element can be used to record any additional information regarding the agent's activities with respect to the METS document.
Diagram
Type extension of xsd:string
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
Wildcard: ANY attribute from ANY namespace OTHER than 'http://www.loc.gov/METS/v2'
Source
 
<xsd:element name="note" minOccurs="0" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The <note> element can be used to record any additional information regarding the agent's activities with respect to the METS document.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="xsd:string">
        <xsd:anyAttribute namespace="##other" processContents="lax"/>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
Element metsType / metsHdr / altRecordID
Namespace http://www.loc.gov/METS/v2
Annotations
 
The alternative record identifier element <altRecordID> allows one to use alternative record identifier values for the digital object represented by the METS document; the primary record identifier is stored in the OBJID attribute in the root <mets> element.
Diagram
Type extension of xsd:string
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
QName Type Use Annotation
ID xsd:ID optional 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
TYPE xsd:string optional 
TYPE (string/O): A description of the identifier type.
Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#altrecordidtype
Source
 
<xsd:element name="altRecordID" minOccurs="0" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The alternative record identifier element <altRecordID> allows one to use alternative record identifier values for the digital object represented by the METS document; the primary record identifier is stored in the OBJID attribute in the root <mets> element.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="xsd:string">
        <xsd:attribute name="ID" type="xsd:ID" use="optional">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
        <xsd:attribute name="TYPE" type="xsd:string" use="optional">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">TYPE (string/O): A description of the identifier type. Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#altrecordidtype</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
Element metsType / metsHdr / metsDocumentID
Namespace http://www.loc.gov/METS/v2
Annotations
 
The metsDocument identifier element <metsDocumentID> allows a unique identifier to be assigned to the METS document itself.  This may be different from the OBJID attribute value in the root <mets> element, which uniquely identifies the entire digital object represented by the METS document.
Diagram
Type extension of xsd:string
Properties
content complex
minOccurs 0
Attributes
QName Type Use Annotation
ID xsd:ID optional 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
TYPE xsd:string optional 
TYPE (string/O): A description of the identifier type.

                        Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#metsdocumentidtype
Source
 
<xsd:element name="metsDocumentID" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The metsDocument identifier element <metsDocumentID> allows a unique identifier to be assigned to the METS document itself. This may be different from the OBJID attribute value in the root <mets> element, which uniquely identifies the entire digital object represented by the METS document.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="xsd:string">
        <xsd:attribute name="ID" type="xsd:ID" use="optional">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
        <xsd:attribute name="TYPE" type="xsd:string" use="optional">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">TYPE (string/O): A description of the identifier type. Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#metsdocumentidtype</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
Element metsType / mdSec
Namespace http://www.loc.gov/METS/v2
Annotations
 
The metadata section <mdSec> contains the metadata pertaining to the digital object, its components and any original source material from which the digital object is derived. The <mdSec> is separated into sub-sections that accommodate any kind of metadata such as descriptive, technical, intellectual property rights, analog/digital source metadata, and digital provenance metadata. Each of these subsections can either wrap the metadata  (mdWrap) or reference it in an external location (mdRef) or both. Multiple instances of the <mdSec> element can occur within a METS document and multiple instances of its subsections can occur in one <mdSec> element. This allows considerable flexibility in the structuring of the metadata. METS does not define a vocabulary or syntax for encoding metadata. Metadata can be expressed within the mdSec sub-elements according to many current community defined standards or locally produced XML schemas.
Diagram
Type mdSecType
Properties
content complex
minOccurs 0
Model
Children md, mdGrp
Instance
 
<mdSec ID="" xmlns="http://www.loc.gov/METS/v2">
  <mdGrp ID="" STATUS="" USE="">{1,unbounded}</mdGrp>
  <md CREATED="" GROUPID="" ID="" MDID="" STATUS="" USE="">{1,unbounded}</md>
</mdSec>
Attributes
QName Type Use Annotation
ID xsd:ID optional 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
Wildcard: ANY attribute from ANY namespace OTHER than 'http://www.loc.gov/METS/v2'
Source
 
<xsd:element name="mdSec" type="mdSecType" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The metadata section <mdSec> contains the metadata pertaining to the digital object, its components and any original source material from which the digital object is derived. The <mdSec> is separated into sub-sections that accommodate any kind of metadata such as descriptive, technical, intellectual property rights, analog/digital source metadata, and digital provenance metadata. Each of these subsections can either wrap the metadata (mdWrap) or reference it in an external location (mdRef) or both. Multiple instances of the <mdSec> element can occur within a METS document and multiple instances of its subsections can occur in one <mdSec> element. This allows considerable flexibility in the structuring of the metadata. METS does not define a vocabulary or syntax for encoding metadata. Metadata can be expressed within the mdSec sub-elements according to many current community defined standards or locally produced XML schemas.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
Element mdSecType / mdGrp
Namespace http://www.loc.gov/METS/v2
Annotations
 
The <mdGrp> element allows grouping related kinds of metadata. This could be all metadata of a particular type, all metadata coming from a particular source, all metadata pertaining to a certain file or set of files, or any other relevant grouping.
Diagram
Properties
content complex
maxOccurs unbounded
Model
Children md
Instance
 
<mdGrp ID="" STATUS="" USE="" xmlns="http://www.loc.gov/METS/v2">
  <md CREATED="" GROUPID="" ID="" MDID="" STATUS="" USE="">{1,unbounded}</md>
</mdGrp>
Attributes
QName Type Use Annotation
ID xsd:ID optional 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
STATUS xsd:string optional 
STATUS (string/O): Indicates the status of this metadata
Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#status-md-mdgrp
USE xsd:string optional 
USE (string/O): Specifies the purpose of the metadata contained in this group.

              Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#mduse-mdgrpuse
Source
 
<xsd:element name="mdGrp" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation>The <mdGrp> element allows grouping related kinds of metadata. This could be all metadata of a particular type, all metadata coming from a particular source, all metadata pertaining to a certain file or set of files, or any other relevant grouping.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="md" type="mdType" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">A <md> element records any kind of metadata about the METS object or a component thereof. The <md> element can either wrap the metadata (mdWrap), reference it in an external location (<mdRef>), or both. METS allows multiple <md> elements; and metadata can be associated with any METS element that supports an MDID attribute. Metadata can be expressed according to many current technical description standards or a locally produced XML schema.</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
    </xsd:sequence>
    <xsd:attribute name="ID" type="xsd:ID" use="optional">
      <xsd:annotation>
        <xsd:documentation>ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="USE" type="xsd:string" use="optional">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">USE (string/O): Specifies the purpose of the metadata contained in this group. Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#mduse-mdgrpuse</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="STATUS" type="xsd:string" use="optional">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">STATUS (string/O): Indicates the status of this metadata Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#status-md-mdgrp</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
  </xsd:complexType>
</xsd:element>
Element mdSecType / mdGrp / md
Namespace http://www.loc.gov/METS/v2
Annotations
 
A <md> element records any kind of metadata about the METS object or a component thereof. The <md> element can either wrap the metadata (mdWrap), reference it in an external location (<mdRef>), or both. METS allows multiple <md> elements; and metadata can be associated with any METS element that supports an MDID attribute. Metadata can be expressed according to many current technical description standards or a locally produced XML schema.
Diagram
Type mdType
Properties
content complex
maxOccurs unbounded
Model
Children mdRef, mdWrap
Instance
 
<md CREATED="" GROUPID="" ID="" MDID="" STATUS="" USE="" xmlns="http://www.loc.gov/METS/v2">
  <mdRef CHECKSUM="" CHECKSUMTYPE="" CREATED="" ID="" LABEL="" LOCREF="" LOCTYPE="" MDTYPE="" MDTYPEVERSION="" MIMETYPE="" SIZE="">{0,1}</mdRef>
  <mdWrap CHECKSUM="" CHECKSUMTYPE="" CREATED="" ID="" LABEL="" MDTYPE="" MDTYPEVERSION="" MIMETYPE="" SIZE="">{0,1}</mdWrap>
</md>
Attributes
QName Type Use Annotation
CREATED xsd:dateTime optional 
CREATED (dateTime/O): Specifies the date and time of creation for the metadata.
GROUPID xsd:string optional 
GROUPID (string/O): This identifier is used to indicate that different metadata sections may be considered as part of a group. Two metadata sections with the same GROUPID value are to be considered part of the same group. For example this facility might be used to group changed versions of the same metadata if previous versions are maintained in a file for tracking purposes.
ID xsd:ID required 
ID (ID/R): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR. The ID attribute on the <md> element is required, and its value should be referenced from one or more MDID attributes that are associated with other elements in the METS document. The following elements support references to a <md> element via a MDID attribute: <file>, <fileGrp> <stream>, <div>, <metsHdr>, <md>.
MDID xsd:IDREFS optional 
MDID (IDREFS/O): Contains the ID attribute values of the <md> elements within the <mdSec> of the METS document that contain metadata pertaining to the current <md> element. Typically used in this context to reference preservation metadata (use="DIGIPROV") which applies to the current metadata.
STATUS xsd:string optional 
STATUS (string/O): Indicates the status of this metadata
Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#status-md-mdgrp
USE xsd:string optional 
USE: Specifies the purpose of metadata in this section.
Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#mduse-mdgrpuse
Wildcard: ANY attribute from ANY namespace OTHER than 'http://www.loc.gov/METS/v2'
Source
 
<xsd:element name="md" type="mdType" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">A <md> element records any kind of metadata about the METS object or a component thereof. The <md> element can either wrap the metadata (mdWrap), reference it in an external location (<mdRef>), or both. METS allows multiple <md> elements; and metadata can be associated with any METS element that supports an MDID attribute. Metadata can be expressed according to many current technical description standards or a locally produced XML schema.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
Element mdType / mdRef
Namespace http://www.loc.gov/METS/v2
Annotations
 
The metadata reference element <mdRef> element is a generic element used throughout the METS schema to provide a pointer to metadata which resides outside the METS document.  NB: <mdRef> is an empty element.
Diagram
Properties
content complex
minOccurs 0
Attributes
QName Type Use Annotation
CHECKSUM xsd:string optional 
CHECKSUM (string/O): Provides a checksum value for the associated file or wrapped content.
CHECKSUMTYPE xsd:string optional 
CHECKSUMTYPE (enumerated string/O): Specifies the checksum algorithm used to produce the value contained in the CHECKSUM attribute.
Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#checksumtype-file-mdref-mdwrap
CREATED xsd:dateTime optional 
CREATED (dateTime/O): Specifies the date and time of creation for the associated file or wrapped content.
ID xsd:ID optional 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
LABEL xsd:string optional 
LABEL (string/O): Provides a label to display to the viewer of the METS document that identifies the associated metadata.
LOCREF xsd:string required 
LOCREF (string/R): Specifies the location for resources. This may be a directly-resolvable URL (preferred for interoperability), or it may require the use of an external resolver or be system-specific. The LOCTYPE attribute identifies the type of location.
LOCTYPE xsd:string required 
LOCTYPE (string/R): Specifies the locator type used in the LOCREF attribute.
Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#loctype-mptr-mdref-flocat
MDTYPE xsd:string required 
MDTYPE (string/R): Is used to indicate the type of the associated metadata.
Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#mdtype-mdref-mdwrap
MDTYPEVERSION xsd:string optional 
MDTYPEVERSION(string/O): Provides a means for recording the version of the type of metadata (as recorded in the MDTYPE attribute) that is being used.  This may represent the version of the underlying data dictionary or metadata model rather than a schema version.
MIMETYPE xsd:string optional 
MIMETYPE (string/O): The IANA media type (formerly known as MIME type) for the associated file or wrapped content.

        Registered media/MIME types: https://www.iana.org/assignments/media-types/media-types.xhtml
SIZE xsd:long optional 
SIZE (long/O): Specifies the size in bytes of the associated file or wrapped content.
Source
 
<xsd:element name="mdRef" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The metadata reference element <mdRef> element is a generic element used throughout the METS schema to provide a pointer to metadata which resides outside the METS document. NB: <mdRef> is an empty element.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:attribute name="ID" type="xsd:ID" use="optional">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attributeGroup ref="LOCATION"/>
    <xsd:attributeGroup ref="METADATA"/>
    <xsd:attributeGroup ref="FILECORE"/>
    <xsd:attribute name="LABEL" type="xsd:string" use="optional">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">LABEL (string/O): Provides a label to display to the viewer of the METS document that identifies the associated metadata.</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
  </xsd:complexType>
</xsd:element>
Element mdType / mdWrap
Namespace http://www.loc.gov/METS/v2
Annotations
 
A metadata wrapper element <mdWrap> provides a wrapper around metadata embedded within a METS document. The element is repeatable. Such metadata can be in one of two forms: 1) XML-encoded metadata, with the XML-encoding identifying itself as belonging to a namespace other than the METS document namespace. 2) Any arbitrary binary or textual form, PROVIDED that the metadata is Base64 encoded and wrapped in a <binData> element within the internal metadata element.
Diagram
Properties
content complex
minOccurs 0
Model
Children binData, xmlData
Instance
 
<mdWrap CHECKSUM="" CHECKSUMTYPE="" CREATED="" ID="" LABEL="" MDTYPE="" MDTYPEVERSION="" MIMETYPE="" SIZE="" xmlns="http://www.loc.gov/METS/v2">
  <binData>{0,1}</binData>
  <xmlData>{0,1}</xmlData>
</mdWrap>
Attributes
QName Type Use Annotation
CHECKSUM xsd:string optional 
CHECKSUM (string/O): Provides a checksum value for the associated file or wrapped content.
CHECKSUMTYPE xsd:string optional 
CHECKSUMTYPE (enumerated string/O): Specifies the checksum algorithm used to produce the value contained in the CHECKSUM attribute.
Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#checksumtype-file-mdref-mdwrap
CREATED xsd:dateTime optional 
CREATED (dateTime/O): Specifies the date and time of creation for the associated file or wrapped content.
ID xsd:ID optional 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
LABEL xsd:string optional 
LABEL: an optional string attribute providing a label to display to the viewer of the METS document identifying the metadata.
MDTYPE xsd:string required 
MDTYPE (string/R): Is used to indicate the type of the associated metadata.
Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#mdtype-mdref-mdwrap
MDTYPEVERSION xsd:string optional 
MDTYPEVERSION(string/O): Provides a means for recording the version of the type of metadata (as recorded in the MDTYPE attribute) that is being used.  This may represent the version of the underlying data dictionary or metadata model rather than a schema version.
MIMETYPE xsd:string optional 
MIMETYPE (string/O): The IANA media type (formerly known as MIME type) for the associated file or wrapped content.

        Registered media/MIME types: https://www.iana.org/assignments/media-types/media-types.xhtml
SIZE xsd:long optional 
SIZE (long/O): Specifies the size in bytes of the associated file or wrapped content.
Source
 
<xsd:element name="mdWrap" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">A metadata wrapper element <mdWrap> provides a wrapper around metadata embedded within a METS document. The element is repeatable. Such metadata can be in one of two forms: 1) XML-encoded metadata, with the XML-encoding identifying itself as belonging to a namespace other than the METS document namespace. 2) Any arbitrary binary or textual form, PROVIDED that the metadata is Base64 encoded and wrapped in a <binData> element within the internal metadata element.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:choice>
      <xsd:element name="binData" type="xsd:base64Binary" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">The binary data wrapper element <binData> is used to contain Base64 encoded metadata.</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="xmlData" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">The xml data wrapper element <xmlData> is used to contain XML encoded metadata. The content of an <xmlData> element can be in any namespace or in no namespace. As permitted by the XML Schema Standard, the processContents attribute value for the metadata in an <xmlData> is set to “lax”. Therefore, if the source schema and its location are identified by means of an XML schemaLocation attribute, then an XML processor will validate the elements for which it can find declarations. If a source schema is not identified, or cannot be found at the specified schemaLocation, then an XML validator will check for well-formedness, but otherwise skip over the elements appearing in the <xmlData> element.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:sequence>
            <xsd:any namespace="##any" maxOccurs="unbounded" processContents="lax"/>
          </xsd:sequence>
        </xsd:complexType>
      </xsd:element>
    </xsd:choice>
    <xsd:attribute name="ID" type="xsd:ID" use="optional">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attributeGroup ref="METADATA"/>
    <xsd:attributeGroup ref="FILECORE"/>
    <xsd:attribute name="LABEL" type="xsd:string" use="optional">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">LABEL: an optional string attribute providing a label to display to the viewer of the METS document identifying the metadata.</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
  </xsd:complexType>
</xsd:element>
Element mdType / mdWrap / binData
Namespace http://www.loc.gov/METS/v2
Annotations
 
The binary data wrapper element <binData> is used to contain Base64 encoded metadata.
Diagram
Type xsd:base64Binary
Properties
content simple
minOccurs 0
Source
 
<xsd:element name="binData" type="xsd:base64Binary" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The binary data wrapper element <binData> is used to contain Base64 encoded metadata.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
Element mdType / mdWrap / xmlData
Namespace http://www.loc.gov/METS/v2
Annotations
 
The xml data wrapper element <xmlData> is used to contain XML encoded metadata. The content of an <xmlData> element can be in any namespace or in no namespace. As permitted by the XML Schema Standard, the processContents attribute value for the metadata in an <xmlData> is set to “lax”. Therefore, if the source schema and its location are identified by means of an XML schemaLocation attribute, then an XML processor will validate the elements for which it can find declarations. If a source schema is not identified, or cannot be found at the specified schemaLocation, then an XML validator will check for well-formedness, but otherwise skip over the elements appearing in the <xmlData> element.
Diagram
Properties
content complex
minOccurs 0
Model
ANY element from ANY namespace
Source
 
<xsd:element name="xmlData" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The xml data wrapper element <xmlData> is used to contain XML encoded metadata. The content of an <xmlData> element can be in any namespace or in no namespace. As permitted by the XML Schema Standard, the processContents attribute value for the metadata in an <xmlData> is set to “lax”. Therefore, if the source schema and its location are identified by means of an XML schemaLocation attribute, then an XML processor will validate the elements for which it can find declarations. If a source schema is not identified, or cannot be found at the specified schemaLocation, then an XML validator will check for well-formedness, but otherwise skip over the elements appearing in the <xmlData> element.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:any namespace="##any" maxOccurs="unbounded" processContents="lax"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
Element mdSecType / md
Namespace http://www.loc.gov/METS/v2
Annotations
 
A <md> element records any kind of metadata about the METS object or a component thereof. The <md> element can either wrap the metadata (mdWrap), reference it in an external location (<mdRef>), or both. METS allows multiple <md> elements; and metadata can be associated with any METS element that supports an MDID attribute. Metadata can be expressed according to many current technical description standards or a locally produced XML schema.
Diagram
Type mdType
Properties
content complex
maxOccurs unbounded
Model
Children mdRef, mdWrap
Instance
 
<md CREATED="" GROUPID="" ID="" MDID="" STATUS="" USE="" xmlns="http://www.loc.gov/METS/v2">
  <mdRef CHECKSUM="" CHECKSUMTYPE="" CREATED="" ID="" LABEL="" LOCREF="" LOCTYPE="" MDTYPE="" MDTYPEVERSION="" MIMETYPE="" SIZE="">{0,1}</mdRef>
  <mdWrap CHECKSUM="" CHECKSUMTYPE="" CREATED="" ID="" LABEL="" MDTYPE="" MDTYPEVERSION="" MIMETYPE="" SIZE="">{0,1}</mdWrap>
</md>
Attributes
QName Type Use Annotation
CREATED xsd:dateTime optional 
CREATED (dateTime/O): Specifies the date and time of creation for the metadata.
GROUPID xsd:string optional 
GROUPID (string/O): This identifier is used to indicate that different metadata sections may be considered as part of a group. Two metadata sections with the same GROUPID value are to be considered part of the same group. For example this facility might be used to group changed versions of the same metadata if previous versions are maintained in a file for tracking purposes.
ID xsd:ID required 
ID (ID/R): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR. The ID attribute on the <md> element is required, and its value should be referenced from one or more MDID attributes that are associated with other elements in the METS document. The following elements support references to a <md> element via a MDID attribute: <file>, <fileGrp> <stream>, <div>, <metsHdr>, <md>.
MDID xsd:IDREFS optional 
MDID (IDREFS/O): Contains the ID attribute values of the <md> elements within the <mdSec> of the METS document that contain metadata pertaining to the current <md> element. Typically used in this context to reference preservation metadata (use="DIGIPROV") which applies to the current metadata.
STATUS xsd:string optional 
STATUS (string/O): Indicates the status of this metadata
Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#status-md-mdgrp
USE xsd:string optional 
USE: Specifies the purpose of metadata in this section.
Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#mduse-mdgrpuse
Wildcard: ANY attribute from ANY namespace OTHER than 'http://www.loc.gov/METS/v2'
Source
 
<xsd:element name="md" type="mdType" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">A <md> element records any kind of metadata about the METS object or a component thereof. The <md> element can either wrap the metadata (mdWrap), reference it in an external location (<mdRef>), or both. METS allows multiple <md> elements; and metadata can be associated with any METS element that supports an MDID attribute. Metadata can be expressed according to many current technical description standards or a locally produced XML schema.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
Element metsType / fileSec
Namespace http://www.loc.gov/METS/v2
Annotations
 
The overall purpose of the content file section element <fileSec> is to provide an inventory of and the location for the content files that comprise the digital object being described in the METS document.
Diagram
Properties
content complex
minOccurs 0
Model
Children file, fileGrp
Instance
 
<fileSec ID="" xmlns="http://www.loc.gov/METS/v2">
  <fileGrp ID="" MDID="" USE="" VERSDATE="">{1,unbounded}</fileGrp>
  <file BEGIN="" BETYPE="" CHECKSUM="" CHECKSUMTYPE="" CREATED="" END="" GROUPID="" ID="" MDID="" MIMETYPE="" OWNERID="" SEQ="" SIZE="" USE="">{1,unbounded}</file>
</fileSec>
Attributes
QName Type Use Annotation
ID xsd:ID optional 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
Wildcard: ANY attribute from ANY namespace OTHER than 'http://www.loc.gov/METS/v2'
Source
 
<xsd:element name="fileSec" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The overall purpose of the content file section element <fileSec> is to provide an inventory of and the location for the content files that comprise the digital object being described in the METS document.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:choice>
      <xsd:element name="fileGrp" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">A sequence of file group elements <fileGrp> can be used to group the digital files comprising the content of a METS object. In the case where the content files are images of different formats and resolutions, for example, one could group the image content files by format and create a separate <fileGrp> for each image format/resolution such as: -- one <fileGrp> for the thumbnails of the images -- one <fileGrp> for the higher resolution JPEGs of the image -- one <fileGrp> for the master archival TIFFs of the images A <fileGrp> may contain zero or more <file> elements.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:complexContent>
            <xsd:extension base="fileGrpType"/>
          </xsd:complexContent>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="file" maxOccurs="unbounded" type="fileType">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">The file element <file> provides access to the content files for the digital object being described by the METS document. A <file> element may contain one or more <FLocat> elements which provide pointers to a content file and/or a <FContent> element which wraps an encoded version of the file. Embedding files using <FContent> can be a valuable feature for exchanging digital objects between repositories or for archiving versions of digital objects for off-site storage. All <FLocat> and <FContent> elements should identify and/or contain identical copies of a single file. The <file> element is recursive, thus allowing sub-files or component files of a larger file to be listed in the inventory. Alternatively, by using the <stream> element, a smaller component of a file or of a related file can be placed within a <file> element. Finally, by using the <transformFile> element, it is possible to include within a <file> element a different version of a file that has undergone a transformation for some reason, such as format migration.</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
    </xsd:choice>
    <xsd:attribute name="ID" type="xsd:ID" use="optional">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:anyAttribute namespace="##other" processContents="lax"/>
  </xsd:complexType>
</xsd:element>
Element metsType / fileSec / fileGrp
Namespace http://www.loc.gov/METS/v2
Annotations
 
A sequence of file group elements <fileGrp> can be used to group the digital files comprising the content of a METS object. In the case where the content files are images of different formats and resolutions, for example, one could group the image content files by format and create a separate <fileGrp> for each image format/resolution such as:
-- one <fileGrp> for the thumbnails of the images
-- one <fileGrp> for the higher resolution JPEGs of the image
-- one <fileGrp> for the master archival TIFFs of the images
A <fileGrp> may contain zero or more <file> elements.
Diagram
Type extension of fileGrpType
Type hierarchy
Properties
content complex
maxOccurs unbounded
Model
Children file
Instance
 
<fileGrp ID="" MDID="" USE="" VERSDATE="" xmlns="http://www.loc.gov/METS/v2">
  <file BEGIN="" BETYPE="" CHECKSUM="" CHECKSUMTYPE="" CREATED="" END="" GROUPID="" ID="" MDID="" MIMETYPE="" OWNERID="" SEQ="" SIZE="" USE="">{1,unbounded}</file>
</fileGrp>
Attributes
QName Type Use Annotation
ID xsd:ID optional 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
MDID xsd:IDREFS optional 
MDID (IDREF/O): Contains the ID attribute values of the <md> elements within the <mdSec> of the METS document applicable to all of the files in a particular file group.
USE xsd:string optional 
USE (string/O): A tagging attribute to indicate the intended use of files within this file group. A USE attribute can be expressed at the<fileGrp> level, the <file> level, the <FLocat> level and/or the <FContent> level.  A USE attribute value at the <fileGrp> level should pertain to all of the files in the <fileGrp>.  A USE attribute at the <file> level should pertain to all copies of the file as represented by subsidiary <FLocat> and/or <FContent> elements.  A USE attribute at the <FLocat> or <FContent> level pertains to the particular copy of the file that is either referenced (<FLocat>) or wrapped (<FContent>).

              Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#filegrpuse-fileuse
VERSDATE xsd:dateTime optional 
VERSDATE (dateTime/O): An optional dateTime attribute specifying the date this version/fileGrp of the digital object was created.
Wildcard: ANY attribute from ANY namespace OTHER than 'http://www.loc.gov/METS/v2'
Source
 
<xsd:element name="fileGrp" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">A sequence of file group elements <fileGrp> can be used to group the digital files comprising the content of a METS object. In the case where the content files are images of different formats and resolutions, for example, one could group the image content files by format and create a separate <fileGrp> for each image format/resolution such as: -- one <fileGrp> for the thumbnails of the images -- one <fileGrp> for the higher resolution JPEGs of the image -- one <fileGrp> for the master archival TIFFs of the images A <fileGrp> may contain zero or more <file> elements.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:complexContent>
      <xsd:extension base="fileGrpType"/>
    </xsd:complexContent>
  </xsd:complexType>
</xsd:element>
Element fileGrpType / file
Namespace http://www.loc.gov/METS/v2
Annotations
 
The file element <file> provides access to the content files for the digital object being described by the METS document. A <file> element may contain one or more <FLocat> elements which provide pointers to a content file and/or a <FContent> element which wraps an encoded version of the file. Embedding files using <FContent> can be a valuable feature for exchanging digital objects between repositories or for archiving versions of digital objects for off-site storage. All <FLocat> and <FContent> elements should identify and/or contain identical copies of a single file. The <file> element is recursive, thus allowing sub-files or component files of a larger file to be listed in the inventory. Alternatively, by using the <stream> element, a smaller component of a file or of a related file can be placed within a <file> element. Finally, by using the <transformFile> element, it is possible to include within a <file> element a different version of a file that has undergone a transformation for some reason, such as format migration.
Diagram
Type fileType
Properties
content complex
maxOccurs unbounded
Model
Children FContent, FLocat, file, stream, transformFile
Instance
 
<file BEGIN="" BETYPE="" CHECKSUM="" CHECKSUMTYPE="" CREATED="" END="" GROUPID="" ID="" MDID="" MIMETYPE="" OWNERID="" SEQ="" SIZE="" USE="" xmlns="http://www.loc.gov/METS/v2">
  <FLocat ID="" LOCREF="" LOCTYPE="" USE="">{0,unbounded}</FLocat>
  <FContent ID="" USE="">{0,1}</FContent>
  <stream BEGIN="" BETYPE="" END="" ID="" MDID="" OWNERID="" streamType="">{0,unbounded}</stream>
  <transformFile ID="" TRANSFORMALGORITHM="" TRANSFORMKEY="" TRANSFORMORDER="" TRANSFORMTYPE="">{0,unbounded}</transformFile>
  <file BEGIN="" BETYPE="" CHECKSUM="" CHECKSUMTYPE="" CREATED="" END="" GROUPID="" ID="" MDID="" MIMETYPE="" OWNERID="" SEQ="" SIZE="" USE="">{0,unbounded}</file>
</file>
Attributes
QName Type Use Annotation
BEGIN xsd:string optional 
BEGIN (string/O): An attribute that specifies the point in the parent <file> where the current <file> begins.  When used in conjunction with a <file> element, this attribute is only meaningful when this element is nested, and its parent <file> element represents a container file. It can be used in conjunction with the END attribute as a means of defining the location of the current file within its parent file. However, the BEGIN attribute can be used with or without a companion END attribute. When no END attribute is specified, the end of the parent file is assumed also to be the end point of the current file. The BEGIN and END attributes can only be interpreted meaningfully in conjunction with a BETYPE attribute, which specifies the kind of beginning/ending point values that are being used.
BETYPE xsd:string optional 
BETYPE: Begin/End Type.
BETYPE (string/O): An attribute that specifies the kind of BEGIN and/or END values that are being used.
     Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#filebetype-streambetype
CHECKSUM xsd:string optional 
CHECKSUM (string/O): Provides a checksum value for the associated file or wrapped content.
CHECKSUMTYPE xsd:string optional 
CHECKSUMTYPE (enumerated string/O): Specifies the checksum algorithm used to produce the value contained in the CHECKSUM attribute.
Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#checksumtype-file-mdref-mdwrap
CREATED xsd:dateTime optional 
CREATED (dateTime/O): Specifies the date and time of creation for the associated file or wrapped content.
END xsd:string optional 
END (string/O): An attribute that specifies the point in the parent <file> where the current, nested <file> ends. It can only be interpreted meaningfully in conjunction with the BETYPE, which specifies the kind of ending point values being used. Typically the END attribute would only appear in conjunction with a BEGIN attribute.
GROUPID xsd:string optional 
GROUPID (string/O): 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 the derivative files made from it in other file groups.
ID xsd:ID required 
ID (ID/R): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR. Typically, the ID attribute value on a <file> element would be referenced from one or more FILEID attributes (which are of type IDREF) on <fptr>and/or <area> elements within the <structMap>.  Such references establish links between  structural divisions (<div> elements) and the specific content files or parts of content files that manifest them.
MDID xsd:IDREFS optional 
MDID (IDREFS/O): Contains the ID attribute values of the <md> elements within the <mdSec> of the METS document that contain metadata pertaining to the file.
MIMETYPE xsd:string optional 
MIMETYPE (string/O): The IANA media type (formerly known as MIME type) for the associated file or wrapped content.

        Registered media/MIME types: https://www.iana.org/assignments/media-types/media-types.xhtml
OWNERID xsd:string optional 
OWNERID (string/O): A unique identifier assigned to the file by its owner.  This may be a URI which differs from the URI used to retrieve the file.
SEQ xsd:int optional 
SEQ (integer/O): Indicates the sequence of this <file> relative to the others in its <fileGrp>.
SIZE xsd:long optional 
SIZE (long/O): Specifies the size in bytes of the associated file or wrapped content.
USE xsd:string optional 
USE (string/O): A tagging attribute to indicate the intended use of all copies of the file aggregated by the <file> element. A USE attribute can be expressed at the<fileGrp> level, the <file> level, the <FLocat> level and/or the <FContent> level.  A USE attribute value at the <fileGrp> level should pertain to all of the files in the <fileGrp>.  A USE attribute at the <file> level should pertain to all copies of the file as represented by subsidiary <FLocat> and/or <FContent> elements.  A USE attribute at the <FLocat> or <FContent> level pertains to the particular copy of the file that is either referenced (<FLocat>) or wrapped (<FContent>).

              Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#filegrpuse-fileuse
Wildcard: ANY attribute from ANY namespace OTHER than 'http://www.loc.gov/METS/v2'
Source
 
<xsd:element name="file" maxOccurs="unbounded" type="fileType">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The file element <file> provides access to the content files for the digital object being described by the METS document. A <file> element may contain one or more <FLocat> elements which provide pointers to a content file and/or a <FContent> element which wraps an encoded version of the file. Embedding files using <FContent> can be a valuable feature for exchanging digital objects between repositories or for archiving versions of digital objects for off-site storage. All <FLocat> and <FContent> elements should identify and/or contain identical copies of a single file. The <file> element is recursive, thus allowing sub-files or component files of a larger file to be listed in the inventory. Alternatively, by using the <stream> element, a smaller component of a file or of a related file can be placed within a <file> element. Finally, by using the <transformFile> element, it is possible to include within a <file> element a different version of a file that has undergone a transformation for some reason, such as format migration.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
Element fileType / FLocat
Namespace http://www.loc.gov/METS/v2
Annotations
 
The file location element <FLocat> provides a pointer to the location of a content file. NOTE: <FLocat> is an empty element.
Diagram
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
QName Type Use Annotation
ID xsd:ID optional 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
LOCREF xsd:string required 
LOCREF (string/R): Specifies the location for resources. This may be a directly-resolvable URL (preferred for interoperability), or it may require the use of an external resolver or be system-specific. The LOCTYPE attribute identifies the type of location.
LOCTYPE xsd:string required 
LOCTYPE (string/R): Specifies the locator type used in the LOCREF attribute.
Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#loctype-mptr-mdref-flocat
USE xsd:string optional 
USE (string/O): A tagging attribute to indicate the intended use of the specific copy of the file  represented by the <FLocat> element. A USE attribute can be expressed at the<fileGrp> level, the <file> level, the <FLocat> level and/or the <FContent> level.  A USE attribute value at the <fileGrp> level should pertain to all of the files in the <fileGrp>.  A USE attribute at the <file> level should pertain to all copies of the file as represented by subsidiary <FLocat> and/or <FContent> elements.  A USE attribute at the <FLocat> or <FContent> level pertains to the particular copy of the file that is either referenced (<FLocat>) or wrapped (<FContent>).

              Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#flocatuse-fcontentuse
Source
 
<xsd:element name="FLocat" minOccurs="0" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The file location element <FLocat> provides a pointer to the location of a content file. NOTE: <FLocat> is an empty element.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:attribute name="ID" type="xsd:ID" use="optional">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="USE" type="xsd:string" use="optional">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">USE (string/O): A tagging attribute to indicate the intended use of the specific copy of the file represented by the <FLocat> element. A USE attribute can be expressed at the<fileGrp> level, the <file> level, the <FLocat> level and/or the <FContent> level. A USE attribute value at the <fileGrp> level should pertain to all of the files in the <fileGrp>. A USE attribute at the <file> level should pertain to all copies of the file as represented by subsidiary <FLocat> and/or <FContent> elements. A USE attribute at the <FLocat> or <FContent> level pertains to the particular copy of the file that is either referenced (<FLocat>) or wrapped (<FContent>). Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#flocatuse-fcontentuse</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attributeGroup ref="LOCATION"/>
  </xsd:complexType>
</xsd:element>
Element fileType / FContent
Namespace http://www.loc.gov/METS/v2
Annotations
 
The file content element <FContent> is used to identify a content file contained internally within a METS document. The content file must be either Base64 encoded and contained within the subsidiary <binData> wrapper element, or consist of XML information and be contained within the subsidiary <xmlData> wrapper element.
Diagram
Properties
content complex
minOccurs 0
Model
Children binData, xmlData
Instance
 
<FContent ID="" USE="" xmlns="http://www.loc.gov/METS/v2">
  <binData>{0,1}</binData>
  <xmlData>{0,1}</xmlData>
</FContent>
Attributes
QName Type Use Annotation
ID xsd:ID optional 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
USE xsd:string optional 
USE (string/O): A tagging attribute to indicate the intended use of the specific copy of the file represented by the <FContent> element. A USE attribute can be expressed at the<fileGrp> level, the <file> level, the <FLocat> level and/or the <FContent> level.  A USE attribute value at the <fileGrp> level should pertain to all of the files in the <fileGrp>.  A USE attribute at the <file> level should pertain to all copies of the file as represented by subsidiary <FLocat> and/or <FContent> elements.  A USE attribute at the <FLocat> or <FContent> level pertains to the particular copy of the file that is either referenced (<FLocat>) or wrapped (<FContent>).
 
             Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#flocatuse-fcontentuse
Source
 
<xsd:element name="FContent" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The file content element <FContent> is used to identify a content file contained internally within a METS document. The content file must be either Base64 encoded and contained within the subsidiary <binData> wrapper element, or consist of XML information and be contained within the subsidiary <xmlData> wrapper element.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:choice>
      <xsd:element name="binData" type="xsd:base64Binary" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">A binary data wrapper element <binData> is used to contain a Base64 encoded file.</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="xmlData" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">An xml data wrapper element <xmlData> is used to contain an XML encoded file. The content of an <xmlData> element can be in any namespace or in no namespace. As permitted by the XML Schema Standard, the processContents attribute value for the metadata in an <xmlData> element is set to “lax”. Therefore, if the source schema and its location are identified by means of an xsi:schemaLocation attribute, then an XML processor will validate the elements for which it can find declarations. If a source schema is not identified, or cannot be found at the specified schemaLocation, then an XML validator will check for well-formedness, but otherwise skip over the elements appearing in the <xmlData> element.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:sequence>
            <xsd:any namespace="##any" maxOccurs="unbounded" processContents="lax"/>
          </xsd:sequence>
        </xsd:complexType>
      </xsd:element>
    </xsd:choice>
    <xsd:attribute name="ID" type="xsd:ID" use="optional">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="USE" type="xsd:string" use="optional">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">USE (string/O): A tagging attribute to indicate the intended use of the specific copy of the file represented by the <FContent> element. A USE attribute can be expressed at the<fileGrp> level, the <file> level, the <FLocat> level and/or the <FContent> level. A USE attribute value at the <fileGrp> level should pertain to all of the files in the <fileGrp>. A USE attribute at the <file> level should pertain to all copies of the file as represented by subsidiary <FLocat> and/or <FContent> elements. A USE attribute at the <FLocat> or <FContent> level pertains to the particular copy of the file that is either referenced (<FLocat>) or wrapped (<FContent>). Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#flocatuse-fcontentuse</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
  </xsd:complexType>
</xsd:element>
Element fileType / FContent / binData
Namespace http://www.loc.gov/METS/v2
Annotations
 
A binary data wrapper element <binData> is used to contain a Base64 encoded file.
Diagram
Type xsd:base64Binary
Properties
content simple
minOccurs 0
Source
 
<xsd:element name="binData" type="xsd:base64Binary" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">A binary data wrapper element <binData> is used to contain a Base64 encoded file.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
Element fileType / FContent / xmlData
Namespace http://www.loc.gov/METS/v2
Annotations
 
An xml data wrapper element <xmlData> is used to contain  an XML encoded file. The content of an <xmlData> element can be in any namespace or in no namespace. As permitted by the XML Schema Standard, the processContents attribute value for the metadata in an <xmlData> element is set to “lax”. Therefore, if the source schema and its location are identified by means of an xsi:schemaLocation attribute, then an XML processor will validate the elements for which it can find declarations. If a source schema is not identified, or cannot be found at the specified schemaLocation, then an XML validator will check for well-formedness, but otherwise skip over the elements appearing in the <xmlData> element.
Diagram
Properties
content complex
minOccurs 0
Model
ANY element from ANY namespace
Source
 
<xsd:element name="xmlData" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">An xml data wrapper element <xmlData> is used to contain an XML encoded file. The content of an <xmlData> element can be in any namespace or in no namespace. As permitted by the XML Schema Standard, the processContents attribute value for the metadata in an <xmlData> element is set to “lax”. Therefore, if the source schema and its location are identified by means of an xsi:schemaLocation attribute, then an XML processor will validate the elements for which it can find declarations. If a source schema is not identified, or cannot be found at the specified schemaLocation, then an XML validator will check for well-formedness, but otherwise skip over the elements appearing in the <xmlData> element.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:any namespace="##any" maxOccurs="unbounded" processContents="lax"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
Element fileType / stream
Namespace http://www.loc.gov/METS/v2
Annotations
 
A component byte stream element <stream> may be composed of one or more subsidiary streams. An MPEG4 file, for example, might contain separate audio and video streams, each of which is associated with technical metadata. The repeatable <stream> element provides a mechanism to record the existence of separate data streams within a particular file, and the opportunity to <mdSec> elements with those subsidiary data streams if desired.
Diagram
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
QName Type Use Annotation
BEGIN xsd:string optional 
BEGIN (string/O): An attribute that specifies the point in the parent <file> where the current <stream> begins. It can be used in conjunction with the END attribute as a means of defining the location of the stream within its parent file. However, the BEGIN attribute can be used with or without a companion END attribute. When no END attribute is specified, the end of the parent file is assumed also to be the end point of the stream. The BEGIN and END attributes can only be interpreted meaningfully in conjunction with a BETYPE attribute, which specifies the kind of beginning/ending point values that are being used.
BETYPE xsd:string optional 
BETYPE: Begin/End Type.
                    BETYPE (string/O): An attribute that specifies the kind of BEGIN and/or END values that are being used.

                    Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#filebetype-streambetype
END xsd:string optional 
END (string/O): An attribute that specifies the point in the parent <file> where the <stream> ends. It can only be interpreted meaningfully in conjunction with the BETYPE, which specifies the kind of ending point values being used. Typically the END attribute would only appear in conjunction with a BEGIN attribute.
ID xsd:ID optional 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
MDID xsd:IDREFS optional 
MDID (IDREFS/O): Contains the ID attribute values of the <md> elements within the <mdSec> of the METS document that contain metadata pertaining to the bytestream.
OWNERID xsd:string optional 
OWNERID (string/O): Used to provide a unique identifier (which could include a URI) assigned to the file. This identifier may differ from the URI used to retrieve the file.
streamType xsd:string optional 
streamType (string/O): The IANA MIME media type for the bytestream.
Source
 
<xsd:element name="stream" minOccurs="0" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">A component byte stream element <stream> may be composed of one or more subsidiary streams. An MPEG4 file, for example, might contain separate audio and video streams, each of which is associated with technical metadata. The repeatable <stream> element provides a mechanism to record the existence of separate data streams within a particular file, and the opportunity to <mdSec> elements with those subsidiary data streams if desired.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:complexContent>
      <xsd:restriction base="xsd:anyType">
        <xsd:attribute name="ID" type="xsd:ID" use="optional">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
        <xsd:attribute name="streamType" type="xsd:string" use="optional">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">streamType (string/O): The IANA MIME media type for the bytestream.</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
        <xsd:attribute name="OWNERID" type="xsd:string" use="optional">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">OWNERID (string/O): Used to provide a unique identifier (which could include a URI) assigned to the file. This identifier may differ from the URI used to retrieve the file.</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
        <xsd:attribute name="MDID" type="xsd:IDREFS" use="optional">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">MDID (IDREFS/O): Contains the ID attribute values of the <md> elements within the <mdSec> of the METS document that contain metadata pertaining to the bytestream.</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
        <xsd:attribute name="BEGIN" type="xsd:string" use="optional">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">BEGIN (string/O): An attribute that specifies the point in the parent <file> where the current <stream> begins. It can be used in conjunction with the END attribute as a means of defining the location of the stream within its parent file. However, the BEGIN attribute can be used with or without a companion END attribute. When no END attribute is specified, the end of the parent file is assumed also to be the end point of the stream. The BEGIN and END attributes can only be interpreted meaningfully in conjunction with a BETYPE attribute, which specifies the kind of beginning/ending point values that are being used.</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
        <xsd:attribute name="END" type="xsd:string" use="optional">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">END (string/O): An attribute that specifies the point in the parent <file> where the <stream> ends. It can only be interpreted meaningfully in conjunction with the BETYPE, which specifies the kind of ending point values being used. Typically the END attribute would only appear in conjunction with a BEGIN attribute.</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
        <xsd:attribute name="BETYPE" use="optional" type="xsd:string">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">BETYPE: Begin/End Type. BETYPE (string/O): An attribute that specifies the kind of BEGIN and/or END values that are being used. Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#filebetype-streambetype</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
      </xsd:restriction>
    </xsd:complexContent>
  </xsd:complexType>
</xsd:element>
Element fileType / transformFile
Namespace http://www.loc.gov/METS/v2
Annotations
 
The transform file element <transformFile> provides a means to access any subsidiary files listed below a <file> element by indicating the steps required to "unpack" or transform the subsidiary files. This element is repeatable.
Diagram
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
QName Type Use Annotation
ID xsd:ID optional 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
TRANSFORMALGORITHM xsd:string required 
TRANSFORMALGORITHM (string/R): Specifies the decompression or decryption routine used to access the contents of the file. Algorithms for compression can be either loss-less or lossy.
TRANSFORMKEY xsd:string optional 
TRANSFORMKEY (string/O): A key to be used with the transform algorithm for accessing the file’s contents.
TRANSFORMORDER xsd:positiveInteger required 
TRANSFORMORDER (postive-integer/R): The order in which the instructions must be followed in order to unpack or transform the container file.
TRANSFORMTYPE xsd:string required 
TRANSFORMTYPE (string/R): Is used to indicate the type of transformation needed to render content of a file accessible. This may include unpacking a file into subsidiary files/streams.

                  Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#transformfiletransformtype
Source
 
<xsd:element name="transformFile" minOccurs="0" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The transform file element <transformFile> provides a means to access any subsidiary files listed below a <file> element by indicating the steps required to "unpack" or transform the subsidiary files. This element is repeatable.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:complexContent>
      <xsd:restriction base="xsd:anyType">
        <xsd:attribute name="ID" type="xsd:ID" use="optional">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
        <xsd:attribute name="TRANSFORMTYPE" use="required" type="xsd:string">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">TRANSFORMTYPE (string/R): Is used to indicate the type of transformation needed to render content of a file accessible. This may include unpacking a file into subsidiary files/streams. Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#transformfiletransformtype</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
        <xsd:attribute name="TRANSFORMALGORITHM" type="xsd:string" use="required">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">TRANSFORMALGORITHM (string/R): Specifies the decompression or decryption routine used to access the contents of the file. Algorithms for compression can be either loss-less or lossy.</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
        <xsd:attribute name="TRANSFORMKEY" type="xsd:string" use="optional">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">TRANSFORMKEY (string/O): A key to be used with the transform algorithm for accessing the file’s contents.</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
        <xsd:attribute name="TRANSFORMORDER" type="xsd:positiveInteger" use="required">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">TRANSFORMORDER (postive-integer/R): The order in which the instructions must be followed in order to unpack or transform the container file.</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
      </xsd:restriction>
    </xsd:complexContent>
  </xsd:complexType>
</xsd:element>
Element fileType / file
Namespace http://www.loc.gov/METS/v2
Diagram
Type fileType
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children FContent, FLocat, file, stream, transformFile
Instance
 
<file BEGIN="" BETYPE="" CHECKSUM="" CHECKSUMTYPE="" CREATED="" END="" GROUPID="" ID="" MDID="" MIMETYPE="" OWNERID="" SEQ="" SIZE="" USE="" xmlns="http://www.loc.gov/METS/v2">
  <FLocat ID="" LOCREF="" LOCTYPE="" USE="">{0,unbounded}</FLocat>
  <FContent ID="" USE="">{0,1}</FContent>
  <stream BEGIN="" BETYPE="" END="" ID="" MDID="" OWNERID="" streamType="">{0,unbounded}</stream>
  <transformFile ID="" TRANSFORMALGORITHM="" TRANSFORMKEY="" TRANSFORMORDER="" TRANSFORMTYPE="">{0,unbounded}</transformFile>
  <file BEGIN="" BETYPE="" CHECKSUM="" CHECKSUMTYPE="" CREATED="" END="" GROUPID="" ID="" MDID="" MIMETYPE="" OWNERID="" SEQ="" SIZE="" USE="">{0,unbounded}</file>
</file>
Attributes
QName Type Use Annotation
BEGIN xsd:string optional 
BEGIN (string/O): An attribute that specifies the point in the parent <file> where the current <file> begins.  When used in conjunction with a <file> element, this attribute is only meaningful when this element is nested, and its parent <file> element represents a container file. It can be used in conjunction with the END attribute as a means of defining the location of the current file within its parent file. However, the BEGIN attribute can be used with or without a companion END attribute. When no END attribute is specified, the end of the parent file is assumed also to be the end point of the current file. The BEGIN and END attributes can only be interpreted meaningfully in conjunction with a BETYPE attribute, which specifies the kind of beginning/ending point values that are being used.
BETYPE xsd:string optional 
BETYPE: Begin/End Type.
BETYPE (string/O): An attribute that specifies the kind of BEGIN and/or END values that are being used.
     Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#filebetype-streambetype
CHECKSUM xsd:string optional 
CHECKSUM (string/O): Provides a checksum value for the associated file or wrapped content.
CHECKSUMTYPE xsd:string optional 
CHECKSUMTYPE (enumerated string/O): Specifies the checksum algorithm used to produce the value contained in the CHECKSUM attribute.
Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#checksumtype-file-mdref-mdwrap
CREATED xsd:dateTime optional 
CREATED (dateTime/O): Specifies the date and time of creation for the associated file or wrapped content.
END xsd:string optional 
END (string/O): An attribute that specifies the point in the parent <file> where the current, nested <file> ends. It can only be interpreted meaningfully in conjunction with the BETYPE, which specifies the kind of ending point values being used. Typically the END attribute would only appear in conjunction with a BEGIN attribute.
GROUPID xsd:string optional 
GROUPID (string/O): 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 the derivative files made from it in other file groups.
ID xsd:ID required 
ID (ID/R): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR. Typically, the ID attribute value on a <file> element would be referenced from one or more FILEID attributes (which are of type IDREF) on <fptr>and/or <area> elements within the <structMap>.  Such references establish links between  structural divisions (<div> elements) and the specific content files or parts of content files that manifest them.
MDID xsd:IDREFS optional 
MDID (IDREFS/O): Contains the ID attribute values of the <md> elements within the <mdSec> of the METS document that contain metadata pertaining to the file.
MIMETYPE xsd:string optional 
MIMETYPE (string/O): The IANA media type (formerly known as MIME type) for the associated file or wrapped content.

        Registered media/MIME types: https://www.iana.org/assignments/media-types/media-types.xhtml
OWNERID xsd:string optional 
OWNERID (string/O): A unique identifier assigned to the file by its owner.  This may be a URI which differs from the URI used to retrieve the file.
SEQ xsd:int optional 
SEQ (integer/O): Indicates the sequence of this <file> relative to the others in its <fileGrp>.
SIZE xsd:long optional 
SIZE (long/O): Specifies the size in bytes of the associated file or wrapped content.
USE xsd:string optional 
USE (string/O): A tagging attribute to indicate the intended use of all copies of the file aggregated by the <file> element. A USE attribute can be expressed at the<fileGrp> level, the <file> level, the <FLocat> level and/or the <FContent> level.  A USE attribute value at the <fileGrp> level should pertain to all of the files in the <fileGrp>.  A USE attribute at the <file> level should pertain to all copies of the file as represented by subsidiary <FLocat> and/or <FContent> elements.  A USE attribute at the <FLocat> or <FContent> level pertains to the particular copy of the file that is either referenced (<FLocat>) or wrapped (<FContent>).

              Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#filegrpuse-fileuse
Wildcard: ANY attribute from ANY namespace OTHER than 'http://www.loc.gov/METS/v2'
Source
 
<xsd:element name="file" type="fileType" minOccurs="0" maxOccurs="unbounded"/>
Element metsType / fileSec / file
Namespace http://www.loc.gov/METS/v2
Annotations
 
The file element <file> provides access to the content files for the digital object being described by the METS document. A <file> element may contain one or more <FLocat> elements which provide pointers to a content file and/or a <FContent> element which wraps an encoded version of the file. Embedding files using <FContent> can be a valuable feature for exchanging digital objects between repositories or for archiving versions of digital objects for off-site storage. All <FLocat> and <FContent> elements should identify and/or contain identical copies of a single file. The <file> element is recursive, thus allowing sub-files or component files of a larger file to be listed in the inventory. Alternatively, by using the <stream> element, a smaller component of a file or of a related file can be placed within a <file> element. Finally, by using the <transformFile> element, it is possible to include within a <file> element a different version of a file that has undergone a transformation for some reason, such as format migration.
Diagram
Type fileType
Properties
content complex
maxOccurs unbounded
Model
Children FContent, FLocat, file, stream, transformFile
Instance
 
<file BEGIN="" BETYPE="" CHECKSUM="" CHECKSUMTYPE="" CREATED="" END="" GROUPID="" ID="" MDID="" MIMETYPE="" OWNERID="" SEQ="" SIZE="" USE="" xmlns="http://www.loc.gov/METS/v2">
  <FLocat ID="" LOCREF="" LOCTYPE="" USE="">{0,unbounded}</FLocat>
  <FContent ID="" USE="">{0,1}</FContent>
  <stream BEGIN="" BETYPE="" END="" ID="" MDID="" OWNERID="" streamType="">{0,unbounded}</stream>
  <transformFile ID="" TRANSFORMALGORITHM="" TRANSFORMKEY="" TRANSFORMORDER="" TRANSFORMTYPE="">{0,unbounded}</transformFile>
  <file BEGIN="" BETYPE="" CHECKSUM="" CHECKSUMTYPE="" CREATED="" END="" GROUPID="" ID="" MDID="" MIMETYPE="" OWNERID="" SEQ="" SIZE="" USE="">{0,unbounded}</file>
</file>
Attributes
QName Type Use Annotation
BEGIN xsd:string optional 
BEGIN (string/O): An attribute that specifies the point in the parent <file> where the current <file> begins.  When used in conjunction with a <file> element, this attribute is only meaningful when this element is nested, and its parent <file> element represents a container file. It can be used in conjunction with the END attribute as a means of defining the location of the current file within its parent file. However, the BEGIN attribute can be used with or without a companion END attribute. When no END attribute is specified, the end of the parent file is assumed also to be the end point of the current file. The BEGIN and END attributes can only be interpreted meaningfully in conjunction with a BETYPE attribute, which specifies the kind of beginning/ending point values that are being used.
BETYPE xsd:string optional 
BETYPE: Begin/End Type.
BETYPE (string/O): An attribute that specifies the kind of BEGIN and/or END values that are being used.
     Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#filebetype-streambetype
CHECKSUM xsd:string optional 
CHECKSUM (string/O): Provides a checksum value for the associated file or wrapped content.
CHECKSUMTYPE xsd:string optional 
CHECKSUMTYPE (enumerated string/O): Specifies the checksum algorithm used to produce the value contained in the CHECKSUM attribute.
Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#checksumtype-file-mdref-mdwrap
CREATED xsd:dateTime optional 
CREATED (dateTime/O): Specifies the date and time of creation for the associated file or wrapped content.
END xsd:string optional 
END (string/O): An attribute that specifies the point in the parent <file> where the current, nested <file> ends. It can only be interpreted meaningfully in conjunction with the BETYPE, which specifies the kind of ending point values being used. Typically the END attribute would only appear in conjunction with a BEGIN attribute.
GROUPID xsd:string optional 
GROUPID (string/O): 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 the derivative files made from it in other file groups.
ID xsd:ID required 
ID (ID/R): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR. Typically, the ID attribute value on a <file> element would be referenced from one or more FILEID attributes (which are of type IDREF) on <fptr>and/or <area> elements within the <structMap>.  Such references establish links between  structural divisions (<div> elements) and the specific content files or parts of content files that manifest them.
MDID xsd:IDREFS optional 
MDID (IDREFS/O): Contains the ID attribute values of the <md> elements within the <mdSec> of the METS document that contain metadata pertaining to the file.
MIMETYPE xsd:string optional 
MIMETYPE (string/O): The IANA media type (formerly known as MIME type) for the associated file or wrapped content.

        Registered media/MIME types: https://www.iana.org/assignments/media-types/media-types.xhtml
OWNERID xsd:string optional 
OWNERID (string/O): A unique identifier assigned to the file by its owner.  This may be a URI which differs from the URI used to retrieve the file.
SEQ xsd:int optional 
SEQ (integer/O): Indicates the sequence of this <file> relative to the others in its <fileGrp>.
SIZE xsd:long optional 
SIZE (long/O): Specifies the size in bytes of the associated file or wrapped content.
USE xsd:string optional 
USE (string/O): A tagging attribute to indicate the intended use of all copies of the file aggregated by the <file> element. A USE attribute can be expressed at the<fileGrp> level, the <file> level, the <FLocat> level and/or the <FContent> level.  A USE attribute value at the <fileGrp> level should pertain to all of the files in the <fileGrp>.  A USE attribute at the <file> level should pertain to all copies of the file as represented by subsidiary <FLocat> and/or <FContent> elements.  A USE attribute at the <FLocat> or <FContent> level pertains to the particular copy of the file that is either referenced (<FLocat>) or wrapped (<FContent>).

              Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#filegrpuse-fileuse
Wildcard: ANY attribute from ANY namespace OTHER than 'http://www.loc.gov/METS/v2'
Source
 
<xsd:element name="file" maxOccurs="unbounded" type="fileType">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The file element <file> provides access to the content files for the digital object being described by the METS document. A <file> element may contain one or more <FLocat> elements which provide pointers to a content file and/or a <FContent> element which wraps an encoded version of the file. Embedding files using <FContent> can be a valuable feature for exchanging digital objects between repositories or for archiving versions of digital objects for off-site storage. All <FLocat> and <FContent> elements should identify and/or contain identical copies of a single file. The <file> element is recursive, thus allowing sub-files or component files of a larger file to be listed in the inventory. Alternatively, by using the <stream> element, a smaller component of a file or of a related file can be placed within a <file> element. Finally, by using the <transformFile> element, it is possible to include within a <file> element a different version of a file that has undergone a transformation for some reason, such as format migration.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
Element metsType / structSec
Namespace http://www.loc.gov/METS/v2
Annotations
 
The <structSec> section contains the <structMap> elements that provide hierarchical organizations of the components of the digital object described by the METS document.
Diagram
Properties
content complex
minOccurs 0
Model
Children structMap
Instance
 
<structSec ID="" xmlns="http://www.loc.gov/METS/v2">
  <structMap ID="" LABEL="" TYPE="">{1,unbounded}</structMap>
</structSec>
Attributes
QName Type Use Annotation
ID xsd:ID optional 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
Source
 
<xsd:element name="structSec" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The <structSec> section contains the <structMap> elements that provide hierarchical organizations of the components of the digital object described by the METS document.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="structMap" type="structMapType" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">The structural map section <structMap> provides a means for organizing the digital content represented by the <file> elements in the <fileSec> of the METS document into a coherent hierarchical structure. Such a hierarchical structure can be presented to users to facilitate their comprehension and navigation of the digital content. It can further be applied to any purpose requiring an understanding of the structural relationship of the content files or parts of the content files. The organization may be specified to any level of granularity (intellectual and or physical) that is desired. Since the <structMap> element is repeatable, more than one organization can be applied to the digital content represented by the METS document. The hierarchical structure specified by a <structMap> is encoded as a tree of nested <div> elements. A <div> element may directly point to content via child file pointer <fptr> elements (if the content is represented in the <fileSec<) or child METS pointer <mptr> elements (if the content is represented by an external METS document). The <fptr> element may point to a single whole <file> element that manifests its parent <div<, or to part of a <file> that manifests its <div<. It can also point to multiple files or parts of files that must be played/displayed either in sequence or in parallel to reveal its structural division. In addition to providing a means for organizing content, the <structMap> provides a mechanism for linking content at any hierarchical level with relevant metadata.</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
    </xsd:sequence>
    <xsd:attribute name="ID" type="xsd:ID" use="optional">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
  </xsd:complexType>
</xsd:element>
Element metsType / structSec / structMap
Namespace http://www.loc.gov/METS/v2
Annotations
 
The structural map section <structMap> provides a means for organizing the digital content represented by the <file> elements in the <fileSec> of the METS document into a coherent hierarchical structure. Such a hierarchical structure can be presented to users to facilitate their comprehension and navigation of the digital content. It can further be applied to any purpose requiring an understanding of the structural relationship of the content files or parts of the content files. The organization may be specified to any level of granularity (intellectual and or physical) that is desired. Since the <structMap> element is repeatable, more than one organization can be applied to the digital content represented by the METS document.  The hierarchical structure specified by a <structMap> is encoded as a tree of nested <div> elements. A <div> element may directly point to content via child file pointer <fptr> elements (if the content is represented in the <fileSec<) or child METS pointer <mptr> elements (if the content is represented by an external METS document). The <fptr> element may point to a single whole <file> element that manifests its parent <div<, or to part of a <file> that manifests its <div<. It can also point to multiple files or parts of files that must be played/displayed either in sequence or in parallel to reveal its structural division. In addition to providing a means for organizing content, the <structMap> provides a mechanism for linking content at any hierarchical level with relevant metadata.
Diagram
Type structMapType
Properties
content complex
maxOccurs unbounded
Model
Children div
Instance
 
<structMap ID="" LABEL="" TYPE="" xmlns="http://www.loc.gov/METS/v2">
  <div CONTENTIDS="" ID="" LABEL="" MDID="" ORDER="" ORDERLABEL="" TYPE="">{1,1}</div>
</structMap>
Attributes
QName Type Use Annotation
ID xsd:ID optional 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
LABEL xsd:string optional 
LABEL (string/O): Describes the <structMap> to viewers of the METS document. This would be useful primarily where more than one <structMap> is provided for a single object. A descriptive LABEL value, in that case, could clarify to users the purpose of each of the available structMaps.
TYPE xsd:string optional 
TYPE (string/O): Identifies the type of structure represented by the <structMap>. For example, a <structMap> that represented a purely logical or intellectual structure could be assigned a TYPE value of “logical” whereas a <structMap> that represented a purely physical structure could be assigned a TYPE value of “physical”. However, the METS schema neither defines nor requires a common vocabulary for this attribute. A METS profile, however, may well constrain the values for the <structMap> TYPE.

        Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#structmaptype
Wildcard: ANY attribute from ANY namespace OTHER than 'http://www.loc.gov/METS/v2'
Source
 
<xsd:element name="structMap" type="structMapType" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The structural map section <structMap> provides a means for organizing the digital content represented by the <file> elements in the <fileSec> of the METS document into a coherent hierarchical structure. Such a hierarchical structure can be presented to users to facilitate their comprehension and navigation of the digital content. It can further be applied to any purpose requiring an understanding of the structural relationship of the content files or parts of the content files. The organization may be specified to any level of granularity (intellectual and or physical) that is desired. Since the <structMap> element is repeatable, more than one organization can be applied to the digital content represented by the METS document. The hierarchical structure specified by a <structMap> is encoded as a tree of nested <div> elements. A <div> element may directly point to content via child file pointer <fptr> elements (if the content is represented in the <fileSec<) or child METS pointer <mptr> elements (if the content is represented by an external METS document). The <fptr> element may point to a single whole <file> element that manifests its parent <div<, or to part of a <file> that manifests its <div<. It can also point to multiple files or parts of files that must be played/displayed either in sequence or in parallel to reveal its structural division. In addition to providing a means for organizing content, the <structMap> provides a mechanism for linking content at any hierarchical level with relevant metadata.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
Element structMapType / div
Namespace http://www.loc.gov/METS/v2
Annotations
 
The structural divisions of the hierarchical organization provided by a <structMap> are represented by division <div> elements, which can be nested to any depth. Each <div> element can represent either an intellectual (logical) division or a physical division. 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.
Diagram
Type divType
Properties
content complex
Model
Children div, fptr, mptr
Instance
 
<div CONTENTIDS="" ID="" LABEL="" MDID="" ORDER="" ORDERLABEL="" TYPE="" xmlns="http://www.loc.gov/METS/v2">
  <mptr CONTENTIDS="" ID="" LOCREF="" LOCTYPE="">{0,unbounded}</mptr>
  <fptr CONTENTIDS="" FILEID="" ID="">{0,unbounded}</fptr>
  <div CONTENTIDS="" ID="" LABEL="" MDID="" ORDER="" ORDERLABEL="" TYPE="">{0,unbounded}</div>
</div>
Attributes
QName Type Use Annotation
CONTENTIDS URIs optional 
CONTENTIDS (URI/O): Content IDs for the content represented by the <div> (equivalent to DIDL DII or Digital Item Identifier, a unique external ID).
ID xsd:ID optional 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
LABEL xsd:string optional 
LABEL (string/O): An attribute used, for example, to identify a <div> to an end user viewing the document. Thus a hierarchical arrangement of the <div> LABEL values could provide a table of contents to the digital content represented by a METS document and facilitate the users’ navigation of the digital object. Note that 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 . For further of the distinction between LABEL and ORDERLABEL see the description of the ORDERLABEL attribute.
MDID xsd:IDREFS optional 
MDID (IDREFS/O): Contains the ID attribute values identifying the <md> elements within the <mdSec> of the METS document that contain or link to metadata pertaining to the structural division represented by the <div> element.
ORDER xsd:integer optional 
ORDER (integer/O): A representation of the element's order among its siblings (e.g., its absolute, numeric sequence). For an example, and clarification of the distinction between ORDER and ORDERLABEL, see the description of the ORDERLABEL attribute.
ORDERLABEL xsd:string optional 
ORDERLABEL (string/O): A representation of the element's order among its siblings (e.g., “xii”), or of any non-integer native numbering system. It is presumed that this value will still be machine actionable (e.g., it would support ‘go to page ___’ function), and it should not be used as a replacement/substitute for the LABEL attribute. To understand 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”.
TYPE xsd:string optional 
TYPE (string/O): An attribute that specifies the type of structural division that the <div> element represents.

          Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#divtype
Source
 
<xsd:element name="div" type="divType">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The structural divisions of the hierarchical organization provided by a <structMap> are represented by division <div> elements, which can be nested to any depth. Each <div> element can represent either an intellectual (logical) division or a physical division. 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>
Element divType / mptr
Namespace http://www.loc.gov/METS/v2
Annotations
 
Like the <fptr> element, the METS pointer element <mptr> represents digital content that manifests its parent <div> element. Unlike the <fptr>, which either directly or indirectly points to content represented in the <fileSec> of the parent METS document, the <mptr> element points to content represented by an external METS document. Thus, this element allows multiple discrete and separate METS documents to be organized at a higher level by a separate METS document. For example, METS documents representing the individual issues in the series of a journal could be grouped together and organized by a higher level METS document that represents the entire journal series. Each of the <div> elements in the <structMap> of the METS document representing the journal series would point to a METS document representing an issue.  It would do so via a child <mptr> element. Thus the <mptr> element gives METS users considerable flexibility in managing the depth of the <structMap> hierarchy of individual METS documents. The <mptr> element points to an external METS document.
Diagram
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
QName Type Use Annotation
CONTENTIDS URIs optional 
CONTENTIDS (URI/O): Content IDs for the content represented by the <mptr> (equivalent to DIDL DII or Digital Item Identifier, a unique external ID).
ID xsd:ID optional 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
LOCREF xsd:string required 
LOCREF (string/R): Specifies the location for resources. This may be a directly-resolvable URL (preferred for interoperability), or it may require the use of an external resolver or be system-specific. The LOCTYPE attribute identifies the type of location.
LOCTYPE xsd:string required 
LOCTYPE (string/R): Specifies the locator type used in the LOCREF attribute.
Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#loctype-mptr-mdref-flocat
Source
 
<xsd:element name="mptr" minOccurs="0" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">Like the <fptr> element, the METS pointer element <mptr> represents digital content that manifests its parent <div> element. Unlike the <fptr>, which either directly or indirectly points to content represented in the <fileSec> of the parent METS document, the <mptr> element points to content represented by an external METS document. Thus, this element allows multiple discrete and separate METS documents to be organized at a higher level by a separate METS document. For example, METS documents representing the individual issues in the series of a journal could be grouped together and organized by a higher level METS document that represents the entire journal series. Each of the <div> elements in the <structMap> of the METS document representing the journal series would point to a METS document representing an issue. It would do so via a child <mptr> element. Thus the <mptr> element gives METS users considerable flexibility in managing the depth of the <structMap> hierarchy of individual METS documents. The <mptr> element points to an external METS document.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:attribute name="ID" type="xsd:ID" use="optional">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attributeGroup ref="LOCATION"/>
    <xsd:attribute name="CONTENTIDS" type="URIs" use="optional">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">CONTENTIDS (URI/O): Content IDs for the content represented by the <mptr> (equivalent to DIDL DII or Digital Item Identifier, a unique external ID).</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
  </xsd:complexType>
</xsd:element>
Element divType / fptr
Namespace http://www.loc.gov/METS/v2
Annotations
 
The <fptr> or file pointer element represents digital content that manifests its parent <div> element. The content represented by an <fptr> element must consist of integral files or parts of files that are represented by <file> elements in the <fileSec>. Via its FILEID attribute,  an <fptr> may point directly to a single integral <file> element that manifests a structural division. However, an <fptr> element may also govern an <area> element,  a <par>, or  a <seq>  which in turn would point to the relevant file or files. A child <area> element can point to part of a <file> that manifests a division, while the <par> and <seq> elements can point to multiple files or parts of files that together manifest a division. More than one <fptr> element can be associated with a <div> element. Typically sibling <fptr> elements represent alternative versions, or manifestations, of the same content
Diagram
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children area, par, seq
Instance
 
<fptr CONTENTIDS="" FILEID="" ID="" xmlns="http://www.loc.gov/METS/v2">
  <par ID="" LABEL="" ORDER="" ORDERLABEL="">{0,1}</par>
  <seq ID="" LABEL="" ORDER="" ORDERLABEL="">{0,1}</seq>
  <area BEGIN="" BETYPE="" CONTENTIDS="" COORDS="" END="" EXTENT="" EXTTYPE="" FILEID="" ID="" LABEL="" MDID="" ORDER="" ORDERLABEL="" SHAPE="">{0,1}</area>
</fptr>
Attributes
QName Type Use Annotation
CONTENTIDS URIs optional 
CONTENTIDS (URI/O): Content IDs for the content represented by the <fptr> (equivalent to DIDL DII or Digital Item Identifier, a unique external ID).
FILEID xsd:IDREF optional 
FILEID (IDREF/O): An optional attribute that provides the XML ID identifying the <file> element that links to and/or contains the digital content represented by the <fptr>. A <fptr> element should only have a FILEID attribute value if it does not have a child <area>, <par> or <seq> element. If it has a child element, then the responsibility for pointing to the relevant content falls to this child element or its descendants.
ID xsd:ID optional 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
Wildcard: ANY attribute from ANY namespace OTHER than 'http://www.loc.gov/METS/v2'
Source
 
<xsd:element name="fptr" minOccurs="0" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The <fptr> or file pointer element represents digital content that manifests its parent <div> element. The content represented by an <fptr> element must consist of integral files or parts of files that are represented by <file> elements in the <fileSec>. Via its FILEID attribute, an <fptr> may point directly to a single integral <file> element that manifests a structural division. However, an <fptr> element may also govern an <area> element, a <par>, or a <seq> which in turn would point to the relevant file or files. A child <area> element can point to part of a <file> that manifests a division, while the <par> and <seq> elements can point to multiple files or parts of files that together manifest a division. More than one <fptr> element can be associated with a <div> element. Typically sibling <fptr> elements represent alternative versions, or manifestations, of the same content</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:choice>
      <xsd:element name="par" type="parType" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">The <par> or parallel files element aggregates pointers to files, parts of files, and/or sequences of files or parts of files that must be played or displayed simultaneously to manifest a block of digital content represented by an <fptr> element. This might be the case, for example, with multi-media content, where a still image might have an accompanying audio track that comments on the still image. In this case, a <par> element would aggregate two <area> elements, one of which pointed to the image file and one of which pointed to the audio file that must be played in conjunction with the image. The <area> element associated with the image could be further qualified with SHAPE and COORDS attributes if only a portion of the image file was pertinent and the <area> element associated with the audio file could be further qualified with BETYPE, BEGIN, EXTTYPE, and EXTENT attributes if only a portion of the associated audio file should be played in conjunction with the image.</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="seq" type="seqType" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">The sequence of files element <seq> aggregates pointers to files, parts of files and/or parallel sets of files or parts of files that must be played or displayed sequentially to manifest a block of digital content. This might be the case, for example, if the parent <div> element represented a logical division, such as a diary entry, that spanned multiple pages of a diary and, hence, multiple page image files. In this case, a <seq> element would aggregate multiple, sequentially arranged <area> elements, each of which pointed to one of the image files that must be presented sequentially to manifest the entire diary entry. If the diary entry started in the middle of a page, then the first <area> element (representing the page on which the diary entry starts) might be further qualified, via its SHAPE and COORDS attributes, to specify the specific, pertinent area of the associated image file.</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="area" type="areaType" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">The area element <area> typically points to content consisting of just a portion or area of a file represented by a <file> element in the <fileSec>. In some contexts, however, the <area> element can also point to content represented by an integral file. A single <area> element would appear as the direct child of a <fptr> element when only a portion of a <file>, rather than an integral <file>, manifested the digital content represented by the <fptr>. Multiple <area> elements would appear as the direct children of a <par> element or a <seq> element when multiple files or parts of files manifested the digital content represented by an <fptr> element. When used in the context of a <par> or <seq> element an <area> element can point either to an integral file or to a segment of a file as necessary.</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
    </xsd:choice>
    <xsd:attribute name="ID" type="xsd:ID" use="optional">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="FILEID" type="xsd:IDREF" use="optional">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">FILEID (IDREF/O): An optional attribute that provides the XML ID identifying the <file> element that links to and/or contains the digital content represented by the <fptr>. A <fptr> element should only have a FILEID attribute value if it does not have a child <area>, <par> or <seq> element. If it has a child element, then the responsibility for pointing to the relevant content falls to this child element or its descendants.</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="CONTENTIDS" type="URIs" use="optional">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">CONTENTIDS (URI/O): Content IDs for the content represented by the <fptr> (equivalent to DIDL DII or Digital Item Identifier, a unique external ID).</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:anyAttribute namespace="##other" processContents="lax"/>
  </xsd:complexType>
</xsd:element>
Element divType / fptr / par
Namespace http://www.loc.gov/METS/v2
Annotations
 
The <par> or parallel files element aggregates pointers to files, parts of files, and/or sequences of files or parts of files that must be played or displayed simultaneously to manifest a block of digital content represented by an <fptr> element. This might be the case, for example, with multi-media content, where a still image might have an accompanying audio track that comments on the still image. In this case, a <par> element would aggregate two <area> elements, one of which pointed to the image file and one of which pointed to the audio file that must be played in conjunction with the image. The <area> element associated with the image could be further qualified with SHAPE and COORDS attributes if only a portion of the image file was pertinent and the <area> element associated with the audio file could be further qualified with BETYPE, BEGIN, EXTTYPE, and EXTENT attributes if only a portion of the associated audio file should be played in conjunction with the image.
Diagram
Type parType
Properties
content complex
minOccurs 0
Model
Children area, seq
Instance
 
<par ID="" LABEL="" ORDER="" ORDERLABEL="" xmlns="http://www.loc.gov/METS/v2">
  <area BEGIN="" BETYPE="" CONTENTIDS="" COORDS="" END="" EXTENT="" EXTTYPE="" FILEID="" ID="" LABEL="" MDID="" ORDER="" ORDERLABEL="" SHAPE="">{0,1}</area>
  <seq ID="" LABEL="" ORDER="" ORDERLABEL="">{0,1}</seq>
</par>
Attributes
QName Type Use Annotation
ID xsd:ID optional 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
LABEL xsd:string optional 
LABEL (string/O): An attribute used, for example, to identify a <div> to an end user viewing the document. Thus a hierarchical arrangement of the <div> LABEL values could provide a table of contents to the digital content represented by a METS document and facilitate the users’ navigation of the digital object. Note that 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 . For further of the distinction between LABEL and ORDERLABEL see the description of the ORDERLABEL attribute.
ORDER xsd:integer optional 
ORDER (integer/O): A representation of the element's order among its siblings (e.g., its absolute, numeric sequence). For an example, and clarification of the distinction between ORDER and ORDERLABEL, see the description of the ORDERLABEL attribute.
ORDERLABEL xsd:string optional 
ORDERLABEL (string/O): A representation of the element's order among its siblings (e.g., “xii”), or of any non-integer native numbering system. It is presumed that this value will still be machine actionable (e.g., it would support ‘go to page ___’ function), and it should not be used as a replacement/substitute for the LABEL attribute. To understand 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”.
Wildcard: ANY attribute from ANY namespace OTHER than 'http://www.loc.gov/METS/v2'
Source
 
<xsd:element name="par" type="parType" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The <par> or parallel files element aggregates pointers to files, parts of files, and/or sequences of files or parts of files that must be played or displayed simultaneously to manifest a block of digital content represented by an <fptr> element. This might be the case, for example, with multi-media content, where a still image might have an accompanying audio track that comments on the still image. In this case, a <par> element would aggregate two <area> elements, one of which pointed to the image file and one of which pointed to the audio file that must be played in conjunction with the image. The <area> element associated with the image could be further qualified with SHAPE and COORDS attributes if only a portion of the image file was pertinent and the <area> element associated with the audio file could be further qualified with BETYPE, BEGIN, EXTTYPE, and EXTENT attributes if only a portion of the associated audio file should be played in conjunction with the image.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
Element parType / area
Namespace http://www.loc.gov/METS/v2
Diagram
Type areaType
Properties
content complex
minOccurs 0
Attributes
QName Type Use Annotation
BEGIN xsd:string optional 
BEGIN (string/O): An attribute that specifies the point in the content file where the relevant section of content begins. It can be used in conjunction with either the END attribute or the EXTENT attribute as a means of defining the relevant portion of the referenced file precisely. It can only be interpreted meaningfully in conjunction with the BETYPE or EXTTYPE, which specify the kind of beginning/ending point values or beginning/extent values that are being used. The BEGIN attribute can be used with or without a companion END or EXTENT element. In this case, the end of the content file is assumed to be the end point.
BETYPE xsd:string optional 
BETYPE: Begin/End Type.
					BETYPE (string/O): An attribute that specifies the kind of BEGIN and/or END values that are being used. For example, if BYTE is specified, then the BEGIN and END point values represent the byte offsets into a file. If IDREF is specified, then the BEGIN element specifies the ID value that identifies the element in a structured text file where the relevant section of the file begins; and the END value (if present) would specify the ID value that identifies the element with which the relevant section of the file ends.

        Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#areabetype
CONTENTIDS URIs optional 
CONTENTIDS (URI/O): Content IDs for the content represented by the <area> (equivalent to DIDL DII or Digital Item Identifier, a unique external ID).
COORDS xsd:string optional 
COORDS (string/O): Specifies the coordinates in an image map for the shape of the pertinent area as specified in the SHAPE attribute. While technically optional, SHAPE and COORDS must both appear together to define the relevant area of image content. COORDS should be used in conjunction with SHAPE in the manner defined for the COORDs and SHAPE attributes on an HTML5 <area> element. COORDS must be a comma delimited string of integer value pairs representing coordinates (plus radius in the case of CIRCLE) within an image. Number of coordinates pairs depends on shape: RECT: x1, y1, x2, y2; CIRC: x1, y1; POLY: x1, y1, x2, y2, x3, y3 . . .
END xsd:string optional 
END (string/O): An attribute that specifies the point in the content file where the relevant section of content ends. It can only be interpreted meaningfully in conjunction with the BETYPE, which specifies the kind of ending point values being used. Typically the END attribute would only appear in conjunction with a BEGIN element.
EXTENT xsd:string optional 
EXTENT (string/O): An attribute that specifies the extent of the relevant section of the content file. Can only be interpreted meaningfully in conjunction with the EXTTYPE which specifies the kind of value that is being used. Typically the EXTENT attribute would only appear in conjunction with a BEGIN element and would not be used if the BEGIN point represents an IDREF.
EXTTYPE xsd:string optional 
EXTTYPE (string/O): An attribute that specifies the kind of EXTENT values that are being used. For example if BYTE is specified then EXTENT would represent a byte count. If TIME is specified the EXTENT would represent a duration of time.

        Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#areaexttype.
FILEID xsd:IDREF required 
FILEID (IDREF/R): An attribute which provides the XML ID value that identifies the <file> element in the <fileSec> that then points to and/or contains the digital content represented by the <area> element. It must contain an ID value represented in an ID attribute associated with a <file> element in the <fileSec> element in the same METS document.
ID xsd:ID optional 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
LABEL xsd:string optional 
LABEL (string/O): An attribute used, for example, to identify a <div> to an end user viewing the document. Thus a hierarchical arrangement of the <div> LABEL values could provide a table of contents to the digital content represented by a METS document and facilitate the users’ navigation of the digital object. Note that 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 . For further of the distinction between LABEL and ORDERLABEL see the description of the ORDERLABEL attribute.
MDID xsd:IDREFS optional 
MDID (IDREFS/O): Contains the ID attribute values identifying the <md> elements within the <mdSec> of the METS document that contain or link to metadata pertaining to the content represented by the <area> element.
ORDER xsd:integer optional 
ORDER (integer/O): A representation of the element's order among its siblings (e.g., its absolute, numeric sequence). For an example, and clarification of the distinction between ORDER and ORDERLABEL, see the description of the ORDERLABEL attribute.
ORDERLABEL xsd:string optional 
ORDERLABEL (string/O): A representation of the element's order among its siblings (e.g., “xii”), or of any non-integer native numbering system. It is presumed that this value will still be machine actionable (e.g., it would support ‘go to page ___’ function), and it should not be used as a replacement/substitute for the LABEL attribute. To understand 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”.
SHAPE xsd:string optional 
SHAPE (string/O): An attribute that can be used as in HTML to define the shape of the relevant area within the content file pointed to by the <area> element. Typically this would be used with image content (still image or video frame) when only a portion of an image pertains. If SHAPE is specified then COORDS must also be present. SHAPE should be used in conjunction with COORDS in the manner defined for the shape and coords attributes on an HTML5 <area> element. Recommended attribute values are those allowed by HTML5; see also https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#areashape
Wildcard: ANY attribute from ANY namespace OTHER than 'http://www.loc.gov/METS/v2'
Source
 
<xsd:element name="area" type="areaType" minOccurs="0"/>
Element parType / seq
Namespace http://www.loc.gov/METS/v2
Diagram
Type seqType
Properties
content complex
minOccurs 0
Model
Children area, par
Instance
 
<seq ID="" LABEL="" ORDER="" ORDERLABEL="" xmlns="http://www.loc.gov/METS/v2">
  <area BEGIN="" BETYPE="" CONTENTIDS="" COORDS="" END="" EXTENT="" EXTTYPE="" FILEID="" ID="" LABEL="" MDID="" ORDER="" ORDERLABEL="" SHAPE="">{0,1}</area>
  <par ID="" LABEL="" ORDER="" ORDERLABEL="">{0,1}</par>
</seq>
Attributes
QName Type Use Annotation
ID xsd:ID optional 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
LABEL xsd:string optional 
LABEL (string/O): An attribute used, for example, to identify a <div> to an end user viewing the document. Thus a hierarchical arrangement of the <div> LABEL values could provide a table of contents to the digital content represented by a METS document and facilitate the users’ navigation of the digital object. Note that 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 . For further of the distinction between LABEL and ORDERLABEL see the description of the ORDERLABEL attribute.
ORDER xsd:integer optional 
ORDER (integer/O): A representation of the element's order among its siblings (e.g., its absolute, numeric sequence). For an example, and clarification of the distinction between ORDER and ORDERLABEL, see the description of the ORDERLABEL attribute.
ORDERLABEL xsd:string optional 
ORDERLABEL (string/O): A representation of the element's order among its siblings (e.g., “xii”), or of any non-integer native numbering system. It is presumed that this value will still be machine actionable (e.g., it would support ‘go to page ___’ function), and it should not be used as a replacement/substitute for the LABEL attribute. To understand 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”.
Wildcard: ANY attribute from ANY namespace OTHER than 'http://www.loc.gov/METS/v2'
Source
 
<xsd:element name="seq" type="seqType" minOccurs="0"/>
Element seqType / area
Namespace http://www.loc.gov/METS/v2
Diagram
Type areaType
Properties
content complex
minOccurs 0
Attributes
QName Type Use Annotation
BEGIN xsd:string optional 
BEGIN (string/O): An attribute that specifies the point in the content file where the relevant section of content begins. It can be used in conjunction with either the END attribute or the EXTENT attribute as a means of defining the relevant portion of the referenced file precisely. It can only be interpreted meaningfully in conjunction with the BETYPE or EXTTYPE, which specify the kind of beginning/ending point values or beginning/extent values that are being used. The BEGIN attribute can be used with or without a companion END or EXTENT element. In this case, the end of the content file is assumed to be the end point.
BETYPE xsd:string optional 
BETYPE: Begin/End Type.
					BETYPE (string/O): An attribute that specifies the kind of BEGIN and/or END values that are being used. For example, if BYTE is specified, then the BEGIN and END point values represent the byte offsets into a file. If IDREF is specified, then the BEGIN element specifies the ID value that identifies the element in a structured text file where the relevant section of the file begins; and the END value (if present) would specify the ID value that identifies the element with which the relevant section of the file ends.

        Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#areabetype
CONTENTIDS URIs optional 
CONTENTIDS (URI/O): Content IDs for the content represented by the <area> (equivalent to DIDL DII or Digital Item Identifier, a unique external ID).
COORDS xsd:string optional 
COORDS (string/O): Specifies the coordinates in an image map for the shape of the pertinent area as specified in the SHAPE attribute. While technically optional, SHAPE and COORDS must both appear together to define the relevant area of image content. COORDS should be used in conjunction with SHAPE in the manner defined for the COORDs and SHAPE attributes on an HTML5 <area> element. COORDS must be a comma delimited string of integer value pairs representing coordinates (plus radius in the case of CIRCLE) within an image. Number of coordinates pairs depends on shape: RECT: x1, y1, x2, y2; CIRC: x1, y1; POLY: x1, y1, x2, y2, x3, y3 . . .
END xsd:string optional 
END (string/O): An attribute that specifies the point in the content file where the relevant section of content ends. It can only be interpreted meaningfully in conjunction with the BETYPE, which specifies the kind of ending point values being used. Typically the END attribute would only appear in conjunction with a BEGIN element.
EXTENT xsd:string optional 
EXTENT (string/O): An attribute that specifies the extent of the relevant section of the content file. Can only be interpreted meaningfully in conjunction with the EXTTYPE which specifies the kind of value that is being used. Typically the EXTENT attribute would only appear in conjunction with a BEGIN element and would not be used if the BEGIN point represents an IDREF.
EXTTYPE xsd:string optional 
EXTTYPE (string/O): An attribute that specifies the kind of EXTENT values that are being used. For example if BYTE is specified then EXTENT would represent a byte count. If TIME is specified the EXTENT would represent a duration of time.

        Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#areaexttype.
FILEID xsd:IDREF required 
FILEID (IDREF/R): An attribute which provides the XML ID value that identifies the <file> element in the <fileSec> that then points to and/or contains the digital content represented by the <area> element. It must contain an ID value represented in an ID attribute associated with a <file> element in the <fileSec> element in the same METS document.
ID xsd:ID optional 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
LABEL xsd:string optional 
LABEL (string/O): An attribute used, for example, to identify a <div> to an end user viewing the document. Thus a hierarchical arrangement of the <div> LABEL values could provide a table of contents to the digital content represented by a METS document and facilitate the users’ navigation of the digital object. Note that 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 . For further of the distinction between LABEL and ORDERLABEL see the description of the ORDERLABEL attribute.
MDID xsd:IDREFS optional 
MDID (IDREFS/O): Contains the ID attribute values identifying the <md> elements within the <mdSec> of the METS document that contain or link to metadata pertaining to the content represented by the <area> element.
ORDER xsd:integer optional 
ORDER (integer/O): A representation of the element's order among its siblings (e.g., its absolute, numeric sequence). For an example, and clarification of the distinction between ORDER and ORDERLABEL, see the description of the ORDERLABEL attribute.
ORDERLABEL xsd:string optional 
ORDERLABEL (string/O): A representation of the element's order among its siblings (e.g., “xii”), or of any non-integer native numbering system. It is presumed that this value will still be machine actionable (e.g., it would support ‘go to page ___’ function), and it should not be used as a replacement/substitute for the LABEL attribute. To understand 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”.
SHAPE xsd:string optional 
SHAPE (string/O): An attribute that can be used as in HTML to define the shape of the relevant area within the content file pointed to by the <area> element. Typically this would be used with image content (still image or video frame) when only a portion of an image pertains. If SHAPE is specified then COORDS must also be present. SHAPE should be used in conjunction with COORDS in the manner defined for the shape and coords attributes on an HTML5 <area> element. Recommended attribute values are those allowed by HTML5; see also https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#areashape
Wildcard: ANY attribute from ANY namespace OTHER than 'http://www.loc.gov/METS/v2'
Source
 
<xsd:element name="area" type="areaType" minOccurs="0"/>
Element seqType / par
Namespace http://www.loc.gov/METS/v2
Diagram
Type parType
Properties
content complex
minOccurs 0
Model
Children area, seq
Instance
 
<par ID="" LABEL="" ORDER="" ORDERLABEL="" xmlns="http://www.loc.gov/METS/v2">
  <area BEGIN="" BETYPE="" CONTENTIDS="" COORDS="" END="" EXTENT="" EXTTYPE="" FILEID="" ID="" LABEL="" MDID="" ORDER="" ORDERLABEL="" SHAPE="">{0,1}</area>
  <seq ID="" LABEL="" ORDER="" ORDERLABEL="">{0,1}</seq>
</par>
Attributes
QName Type Use Annotation
ID xsd:ID optional 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
LABEL xsd:string optional 
LABEL (string/O): An attribute used, for example, to identify a <div> to an end user viewing the document. Thus a hierarchical arrangement of the <div> LABEL values could provide a table of contents to the digital content represented by a METS document and facilitate the users’ navigation of the digital object. Note that 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 . For further of the distinction between LABEL and ORDERLABEL see the description of the ORDERLABEL attribute.
ORDER xsd:integer optional 
ORDER (integer/O): A representation of the element's order among its siblings (e.g., its absolute, numeric sequence). For an example, and clarification of the distinction between ORDER and ORDERLABEL, see the description of the ORDERLABEL attribute.
ORDERLABEL xsd:string optional 
ORDERLABEL (string/O): A representation of the element's order among its siblings (e.g., “xii”), or of any non-integer native numbering system. It is presumed that this value will still be machine actionable (e.g., it would support ‘go to page ___’ function), and it should not be used as a replacement/substitute for the LABEL attribute. To understand 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”.
Wildcard: ANY attribute from ANY namespace OTHER than 'http://www.loc.gov/METS/v2'
Source
 
<xsd:element name="par" type="parType" minOccurs="0"/>
Element divType / fptr / seq
Namespace http://www.loc.gov/METS/v2
Annotations
 
The sequence of files element <seq> aggregates pointers to files,  parts of files and/or parallel sets of files or parts of files  that must be played or displayed sequentially to manifest a block of digital content. This might be the case, for example, if the parent <div> element represented a logical division, such as a diary entry, that spanned multiple pages of a diary and, hence, multiple page image files. In this case, a <seq> element would aggregate multiple, sequentially arranged <area> elements, each of which pointed to one of the image files that must be presented sequentially to manifest the entire diary entry. If the diary entry started in the middle of a page, then the first <area> element (representing the page on which the diary entry starts) might be further qualified, via its SHAPE and COORDS attributes, to specify the specific, pertinent area of the associated image file.
Diagram
Type seqType
Properties
content complex
minOccurs 0
Model
Children area, par
Instance
 
<seq ID="" LABEL="" ORDER="" ORDERLABEL="" xmlns="http://www.loc.gov/METS/v2">
  <area BEGIN="" BETYPE="" CONTENTIDS="" COORDS="" END="" EXTENT="" EXTTYPE="" FILEID="" ID="" LABEL="" MDID="" ORDER="" ORDERLABEL="" SHAPE="">{0,1}</area>
  <par ID="" LABEL="" ORDER="" ORDERLABEL="">{0,1}</par>
</seq>
Attributes
QName Type Use Annotation
ID xsd:ID optional 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
LABEL xsd:string optional 
LABEL (string/O): An attribute used, for example, to identify a <div> to an end user viewing the document. Thus a hierarchical arrangement of the <div> LABEL values could provide a table of contents to the digital content represented by a METS document and facilitate the users’ navigation of the digital object. Note that 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 . For further of the distinction between LABEL and ORDERLABEL see the description of the ORDERLABEL attribute.
ORDER xsd:integer optional 
ORDER (integer/O): A representation of the element's order among its siblings (e.g., its absolute, numeric sequence). For an example, and clarification of the distinction between ORDER and ORDERLABEL, see the description of the ORDERLABEL attribute.
ORDERLABEL xsd:string optional 
ORDERLABEL (string/O): A representation of the element's order among its siblings (e.g., “xii”), or of any non-integer native numbering system. It is presumed that this value will still be machine actionable (e.g., it would support ‘go to page ___’ function), and it should not be used as a replacement/substitute for the LABEL attribute. To understand 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”.
Wildcard: ANY attribute from ANY namespace OTHER than 'http://www.loc.gov/METS/v2'
Source
 
<xsd:element name="seq" type="seqType" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The sequence of files element <seq> aggregates pointers to files, parts of files and/or parallel sets of files or parts of files that must be played or displayed sequentially to manifest a block of digital content. This might be the case, for example, if the parent <div> element represented a logical division, such as a diary entry, that spanned multiple pages of a diary and, hence, multiple page image files. In this case, a <seq> element would aggregate multiple, sequentially arranged <area> elements, each of which pointed to one of the image files that must be presented sequentially to manifest the entire diary entry. If the diary entry started in the middle of a page, then the first <area> element (representing the page on which the diary entry starts) might be further qualified, via its SHAPE and COORDS attributes, to specify the specific, pertinent area of the associated image file.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
Element divType / fptr / area
Namespace http://www.loc.gov/METS/v2
Annotations
 
The area element <area> typically points to content consisting of just a portion or area of a file represented by a <file> element in the <fileSec>. In some contexts, however, the <area> element can also point to content represented by an integral file. A single <area> element would appear as the direct child of a <fptr> element when only a portion of a <file>, rather than an integral <file>, manifested the digital content represented by the <fptr>. Multiple <area> elements would appear as the direct children of a <par> element or a <seq> element when multiple files or parts of files manifested the digital content represented by an <fptr> element. When used in the context of a <par> or <seq> element an <area> element can point either to an integral file or to a segment of a file as necessary.
Diagram
Type areaType
Properties
content complex
minOccurs 0
Attributes
QName Type Use Annotation
BEGIN xsd:string optional 
BEGIN (string/O): An attribute that specifies the point in the content file where the relevant section of content begins. It can be used in conjunction with either the END attribute or the EXTENT attribute as a means of defining the relevant portion of the referenced file precisely. It can only be interpreted meaningfully in conjunction with the BETYPE or EXTTYPE, which specify the kind of beginning/ending point values or beginning/extent values that are being used. The BEGIN attribute can be used with or without a companion END or EXTENT element. In this case, the end of the content file is assumed to be the end point.
BETYPE xsd:string optional 
BETYPE: Begin/End Type.
					BETYPE (string/O): An attribute that specifies the kind of BEGIN and/or END values that are being used. For example, if BYTE is specified, then the BEGIN and END point values represent the byte offsets into a file. If IDREF is specified, then the BEGIN element specifies the ID value that identifies the element in a structured text file where the relevant section of the file begins; and the END value (if present) would specify the ID value that identifies the element with which the relevant section of the file ends.

        Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#areabetype
CONTENTIDS URIs optional 
CONTENTIDS (URI/O): Content IDs for the content represented by the <area> (equivalent to DIDL DII or Digital Item Identifier, a unique external ID).
COORDS xsd:string optional 
COORDS (string/O): Specifies the coordinates in an image map for the shape of the pertinent area as specified in the SHAPE attribute. While technically optional, SHAPE and COORDS must both appear together to define the relevant area of image content. COORDS should be used in conjunction with SHAPE in the manner defined for the COORDs and SHAPE attributes on an HTML5 <area> element. COORDS must be a comma delimited string of integer value pairs representing coordinates (plus radius in the case of CIRCLE) within an image. Number of coordinates pairs depends on shape: RECT: x1, y1, x2, y2; CIRC: x1, y1; POLY: x1, y1, x2, y2, x3, y3 . . .
END xsd:string optional 
END (string/O): An attribute that specifies the point in the content file where the relevant section of content ends. It can only be interpreted meaningfully in conjunction with the BETYPE, which specifies the kind of ending point values being used. Typically the END attribute would only appear in conjunction with a BEGIN element.
EXTENT xsd:string optional 
EXTENT (string/O): An attribute that specifies the extent of the relevant section of the content file. Can only be interpreted meaningfully in conjunction with the EXTTYPE which specifies the kind of value that is being used. Typically the EXTENT attribute would only appear in conjunction with a BEGIN element and would not be used if the BEGIN point represents an IDREF.
EXTTYPE xsd:string optional 
EXTTYPE (string/O): An attribute that specifies the kind of EXTENT values that are being used. For example if BYTE is specified then EXTENT would represent a byte count. If TIME is specified the EXTENT would represent a duration of time.

        Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#areaexttype.
FILEID xsd:IDREF required 
FILEID (IDREF/R): An attribute which provides the XML ID value that identifies the <file> element in the <fileSec> that then points to and/or contains the digital content represented by the <area> element. It must contain an ID value represented in an ID attribute associated with a <file> element in the <fileSec> element in the same METS document.
ID xsd:ID optional 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
LABEL xsd:string optional 
LABEL (string/O): An attribute used, for example, to identify a <div> to an end user viewing the document. Thus a hierarchical arrangement of the <div> LABEL values could provide a table of contents to the digital content represented by a METS document and facilitate the users’ navigation of the digital object. Note that 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 . For further of the distinction between LABEL and ORDERLABEL see the description of the ORDERLABEL attribute.
MDID xsd:IDREFS optional 
MDID (IDREFS/O): Contains the ID attribute values identifying the <md> elements within the <mdSec> of the METS document that contain or link to metadata pertaining to the content represented by the <area> element.
ORDER xsd:integer optional 
ORDER (integer/O): A representation of the element's order among its siblings (e.g., its absolute, numeric sequence). For an example, and clarification of the distinction between ORDER and ORDERLABEL, see the description of the ORDERLABEL attribute.
ORDERLABEL xsd:string optional 
ORDERLABEL (string/O): A representation of the element's order among its siblings (e.g., “xii”), or of any non-integer native numbering system. It is presumed that this value will still be machine actionable (e.g., it would support ‘go to page ___’ function), and it should not be used as a replacement/substitute for the LABEL attribute. To understand 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”.
SHAPE xsd:string optional 
SHAPE (string/O): An attribute that can be used as in HTML to define the shape of the relevant area within the content file pointed to by the <area> element. Typically this would be used with image content (still image or video frame) when only a portion of an image pertains. If SHAPE is specified then COORDS must also be present. SHAPE should be used in conjunction with COORDS in the manner defined for the shape and coords attributes on an HTML5 <area> element. Recommended attribute values are those allowed by HTML5; see also https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#areashape
Wildcard: ANY attribute from ANY namespace OTHER than 'http://www.loc.gov/METS/v2'
Source
 
<xsd:element name="area" type="areaType" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The area element <area> typically points to content consisting of just a portion or area of a file represented by a <file> element in the <fileSec>. In some contexts, however, the <area> element can also point to content represented by an integral file. A single <area> element would appear as the direct child of a <fptr> element when only a portion of a <file>, rather than an integral <file>, manifested the digital content represented by the <fptr>. Multiple <area> elements would appear as the direct children of a <par> element or a <seq> element when multiple files or parts of files manifested the digital content represented by an <fptr> element. When used in the context of a <par> or <seq> element an <area> element can point either to an integral file or to a segment of a file as necessary.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
Element divType / div
Namespace http://www.loc.gov/METS/v2
Diagram
Type divType
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children div, fptr, mptr
Instance
 
<div CONTENTIDS="" ID="" LABEL="" MDID="" ORDER="" ORDERLABEL="" TYPE="" xmlns="http://www.loc.gov/METS/v2">
  <mptr CONTENTIDS="" ID="" LOCREF="" LOCTYPE="">{0,unbounded}</mptr>
  <fptr CONTENTIDS="" FILEID="" ID="">{0,unbounded}</fptr>
  <div CONTENTIDS="" ID="" LABEL="" MDID="" ORDER="" ORDERLABEL="" TYPE="">{0,unbounded}</div>
</div>
Attributes
QName Type Use Annotation
CONTENTIDS URIs optional 
CONTENTIDS (URI/O): Content IDs for the content represented by the <div> (equivalent to DIDL DII or Digital Item Identifier, a unique external ID).
ID xsd:ID optional 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
LABEL xsd:string optional 
LABEL (string/O): An attribute used, for example, to identify a <div> to an end user viewing the document. Thus a hierarchical arrangement of the <div> LABEL values could provide a table of contents to the digital content represented by a METS document and facilitate the users’ navigation of the digital object. Note that 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 . For further of the distinction between LABEL and ORDERLABEL see the description of the ORDERLABEL attribute.
MDID xsd:IDREFS optional 
MDID (IDREFS/O): Contains the ID attribute values identifying the <md> elements within the <mdSec> of the METS document that contain or link to metadata pertaining to the structural division represented by the <div> element.
ORDER xsd:integer optional 
ORDER (integer/O): A representation of the element's order among its siblings (e.g., its absolute, numeric sequence). For an example, and clarification of the distinction between ORDER and ORDERLABEL, see the description of the ORDERLABEL attribute.
ORDERLABEL xsd:string optional 
ORDERLABEL (string/O): A representation of the element's order among its siblings (e.g., “xii”), or of any non-integer native numbering system. It is presumed that this value will still be machine actionable (e.g., it would support ‘go to page ___’ function), and it should not be used as a replacement/substitute for the LABEL attribute. To understand 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”.
TYPE xsd:string optional 
TYPE (string/O): An attribute that specifies the type of structural division that the <div> element represents.

          Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#divtype
Source
 
<xsd:element name="div" type="divType" minOccurs="0" maxOccurs="unbounded"/>
Complex Type metsType
Namespace http://www.loc.gov/METS/v2
Annotations
 
metsType: Complex Type for METS Sections
A METS document consists of four possible subsidiary sections: metsHdr (METS document header), mdSec (metadata section), fileSec (file section) and structMap (structural map)
Diagram
Used by
Element mets
Model
Children fileSec, mdSec, metsHdr, structSec
Attributes
QName Type Use Annotation
ID xsd:ID optional 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
LABEL xsd:string optional 
LABEL (string/O): Is a simple title string used to identify the object/entity being described in the METS document for the user.
OBJID xsd:string optional 
OBJID (string/O): Is the primary identifier assigned to the METS object as a whole. Although this attribute is not required, it is strongly recommended. This identifier is used to tag the entire METS object to external systems, in contrast with the ID identifier.
PROFILE xsd:string optional 
PROFILE (string/O): Indicates the URI of the METS Profile this METS document conforms to.
TYPE xsd:string optional 
TYPE (string/O): Specifies the class or type of the object.

          Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#metstype
Wildcard: ANY attribute from ANY namespace OTHER than 'http://www.loc.gov/METS/v2'
Source
 
<xsd:complexType name="metsType">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">metsType: Complex Type for METS Sections A METS document consists of four possible subsidiary sections: metsHdr (METS document header), mdSec (metadata section), fileSec (file section) and structMap (structural map)</xsd:documentation>
  </xsd:annotation>
  <xsd:sequence>
    <xsd:element name="metsHdr" minOccurs="0">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">The mets header element <metsHdr> captures metadata about the METS document itself, not the digital object the METS document encodes.</xsd:documentation>
      </xsd:annotation>
      <xsd:complexType>
        <xsd:sequence>
          <xsd:element name="agent" minOccurs="0" maxOccurs="unbounded">
            <xsd:annotation>
              <xsd:documentation xml:lang="en">agent: The agent element <agent> provides for various parties and their roles with respect to the METS document to be documented.</xsd:documentation>
            </xsd:annotation>
            <xsd:complexType>
              <xsd:sequence>
                <xsd:element name="name" type="xsd:string">
                  <xsd:annotation>
                    <xsd:documentation xml:lang="en">The element <name> can be used to record the full name of the METS document agent.</xsd:documentation>
                  </xsd:annotation>
                </xsd:element>
                <xsd:element name="note" minOccurs="0" maxOccurs="unbounded">
                  <xsd:annotation>
                    <xsd:documentation xml:lang="en">The <note> element can be used to record any additional information regarding the agent's activities with respect to the METS document.</xsd:documentation>
                  </xsd:annotation>
                  <xsd:complexType>
                    <xsd:simpleContent>
                      <xsd:extension base="xsd:string">
                        <xsd:anyAttribute namespace="##other" processContents="lax"/>
                      </xsd:extension>
                    </xsd:simpleContent>
                  </xsd:complexType>
                </xsd:element>
              </xsd:sequence>
              <xsd:attribute name="ID" type="xsd:ID" use="optional">
                <xsd:annotation>
                  <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
                </xsd:annotation>
              </xsd:attribute>
              <xsd:attribute name="ROLE" use="required" type="xsd:string">
                <xsd:annotation>
                  <xsd:documentation xml:lang="en">ROLE (string/R): Specifies the function of the agent with respect to the METS document. Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#agentrole</xsd:documentation>
                </xsd:annotation>
              </xsd:attribute>
              <xsd:attribute name="TYPE" use="optional" type="xsd:string">
                <xsd:annotation>
                  <xsd:documentation xml:lang="en">TYPE (string/O): is used to specify the type of AGENT. Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#agenttype</xsd:documentation>
                </xsd:annotation>
              </xsd:attribute>
            </xsd:complexType>
          </xsd:element>
          <xsd:element name="altRecordID" minOccurs="0" maxOccurs="unbounded">
            <xsd:annotation>
              <xsd:documentation xml:lang="en">The alternative record identifier element <altRecordID> allows one to use alternative record identifier values for the digital object represented by the METS document; the primary record identifier is stored in the OBJID attribute in the root <mets> element.</xsd:documentation>
            </xsd:annotation>
            <xsd:complexType>
              <xsd:simpleContent>
                <xsd:extension base="xsd:string">
                  <xsd:attribute name="ID" type="xsd:ID" use="optional">
                    <xsd:annotation>
                      <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
                    </xsd:annotation>
                  </xsd:attribute>
                  <xsd:attribute name="TYPE" type="xsd:string" use="optional">
                    <xsd:annotation>
                      <xsd:documentation xml:lang="en">TYPE (string/O): A description of the identifier type. Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#altrecordidtype</xsd:documentation>
                    </xsd:annotation>
                  </xsd:attribute>
                </xsd:extension>
              </xsd:simpleContent>
            </xsd:complexType>
          </xsd:element>
          <xsd:element name="metsDocumentID" minOccurs="0">
            <xsd:annotation>
              <xsd:documentation xml:lang="en">The metsDocument identifier element <metsDocumentID> allows a unique identifier to be assigned to the METS document itself. This may be different from the OBJID attribute value in the root <mets> element, which uniquely identifies the entire digital object represented by the METS document.</xsd:documentation>
            </xsd:annotation>
            <xsd:complexType>
              <xsd:simpleContent>
                <xsd:extension base="xsd:string">
                  <xsd:attribute name="ID" type="xsd:ID" use="optional">
                    <xsd:annotation>
                      <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
                    </xsd:annotation>
                  </xsd:attribute>
                  <xsd:attribute name="TYPE" type="xsd:string" use="optional">
                    <xsd:annotation>
                      <xsd:documentation xml:lang="en">TYPE (string/O): A description of the identifier type. Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#metsdocumentidtype</xsd:documentation>
                    </xsd:annotation>
                  </xsd:attribute>
                </xsd:extension>
              </xsd:simpleContent>
            </xsd:complexType>
          </xsd:element>
        </xsd:sequence>
        <xsd:attribute name="ID" type="xsd:ID" use="optional">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
        <xsd:attribute name="MDID" type="xsd:IDREFS" use="optional">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">MDID (IDREFS/O): Contains the ID attribute values of the <md> elements within the <mdSec> of the METS document that contain metadata pertaining to the METS document itself.</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
        <xsd:attribute name="CREATEDATE" type="xsd:dateTime" use="optional">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">CREATEDATE (dateTime/O): Records the date/time the METS document was created.</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
        <xsd:attribute name="LASTMODDATE" type="xsd:dateTime" use="optional">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">LASTMODDATE (dateTime/O): Is used to indicate the date/time the METS document was last modified.</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
        <xsd:attribute name="RECORDSTATUS" type="xsd:string" use="optional">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">RECORDSTATUS (string/O): Specifies the status of the METS document. It is used for internal processing purposes.</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
        <xsd:anyAttribute namespace="##other" processContents="lax"/>
      </xsd:complexType>
    </xsd:element>
    <xsd:element name="mdSec" type="mdSecType" minOccurs="0">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">The metadata section <mdSec> contains the metadata pertaining to the digital object, its components and any original source material from which the digital object is derived. The <mdSec> is separated into sub-sections that accommodate any kind of metadata such as descriptive, technical, intellectual property rights, analog/digital source metadata, and digital provenance metadata. Each of these subsections can either wrap the metadata (mdWrap) or reference it in an external location (mdRef) or both. Multiple instances of the <mdSec> element can occur within a METS document and multiple instances of its subsections can occur in one <mdSec> element. This allows considerable flexibility in the structuring of the metadata. METS does not define a vocabulary or syntax for encoding metadata. Metadata can be expressed within the mdSec sub-elements according to many current community defined standards or locally produced XML schemas.</xsd:documentation>
      </xsd:annotation>
    </xsd:element>
    <xsd:element name="fileSec" minOccurs="0">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">The overall purpose of the content file section element <fileSec> is to provide an inventory of and the location for the content files that comprise the digital object being described in the METS document.</xsd:documentation>
      </xsd:annotation>
      <xsd:complexType>
        <xsd:choice>
          <xsd:element name="fileGrp" maxOccurs="unbounded">
            <xsd:annotation>
              <xsd:documentation xml:lang="en">A sequence of file group elements <fileGrp> can be used to group the digital files comprising the content of a METS object. In the case where the content files are images of different formats and resolutions, for example, one could group the image content files by format and create a separate <fileGrp> for each image format/resolution such as: -- one <fileGrp> for the thumbnails of the images -- one <fileGrp> for the higher resolution JPEGs of the image -- one <fileGrp> for the master archival TIFFs of the images A <fileGrp> may contain zero or more <file> elements.</xsd:documentation>
            </xsd:annotation>
            <xsd:complexType>
              <xsd:complexContent>
                <xsd:extension base="fileGrpType"/>
              </xsd:complexContent>
            </xsd:complexType>
          </xsd:element>
          <xsd:element name="file" maxOccurs="unbounded" type="fileType">
            <xsd:annotation>
              <xsd:documentation xml:lang="en">The file element <file> provides access to the content files for the digital object being described by the METS document. A <file> element may contain one or more <FLocat> elements which provide pointers to a content file and/or a <FContent> element which wraps an encoded version of the file. Embedding files using <FContent> can be a valuable feature for exchanging digital objects between repositories or for archiving versions of digital objects for off-site storage. All <FLocat> and <FContent> elements should identify and/or contain identical copies of a single file. The <file> element is recursive, thus allowing sub-files or component files of a larger file to be listed in the inventory. Alternatively, by using the <stream> element, a smaller component of a file or of a related file can be placed within a <file> element. Finally, by using the <transformFile> element, it is possible to include within a <file> element a different version of a file that has undergone a transformation for some reason, such as format migration.</xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:choice>
        <xsd:attribute name="ID" type="xsd:ID" use="optional">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
        <xsd:anyAttribute namespace="##other" processContents="lax"/>
      </xsd:complexType>
    </xsd:element>
    <xsd:element name="structSec" minOccurs="0">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">The <structSec> section contains the <structMap> elements that provide hierarchical organizations of the components of the digital object described by the METS document.</xsd:documentation>
      </xsd:annotation>
      <xsd:complexType>
        <xsd:sequence>
          <xsd:element name="structMap" type="structMapType" maxOccurs="unbounded">
            <xsd:annotation>
              <xsd:documentation xml:lang="en">The structural map section <structMap> provides a means for organizing the digital content represented by the <file> elements in the <fileSec> of the METS document into a coherent hierarchical structure. Such a hierarchical structure can be presented to users to facilitate their comprehension and navigation of the digital content. It can further be applied to any purpose requiring an understanding of the structural relationship of the content files or parts of the content files. The organization may be specified to any level of granularity (intellectual and or physical) that is desired. Since the <structMap> element is repeatable, more than one organization can be applied to the digital content represented by the METS document. The hierarchical structure specified by a <structMap> is encoded as a tree of nested <div> elements. A <div> element may directly point to content via child file pointer <fptr> elements (if the content is represented in the <fileSec<) or child METS pointer <mptr> elements (if the content is represented by an external METS document). The <fptr> element may point to a single whole <file> element that manifests its parent <div<, or to part of a <file> that manifests its <div<. It can also point to multiple files or parts of files that must be played/displayed either in sequence or in parallel to reveal its structural division. In addition to providing a means for organizing content, the <structMap> provides a mechanism for linking content at any hierarchical level with relevant metadata.</xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
        <xsd:attribute name="ID" type="xsd:ID" use="optional">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
      </xsd:complexType>
    </xsd:element>
  </xsd:sequence>
  <xsd:attribute name="ID" type="xsd:ID" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="OBJID" type="xsd:string" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">OBJID (string/O): Is the primary identifier assigned to the METS object as a whole. Although this attribute is not required, it is strongly recommended. This identifier is used to tag the entire METS object to external systems, in contrast with the ID identifier.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="LABEL" type="xsd:string" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">LABEL (string/O): Is a simple title string used to identify the object/entity being described in the METS document for the user.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="TYPE" type="xsd:string" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">TYPE (string/O): Specifies the class or type of the object. Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#metstype</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="PROFILE" type="xsd:string" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">PROFILE (string/O): Indicates the URI of the METS Profile this METS document conforms to.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:anyAttribute namespace="##other" processContents="lax"/>
</xsd:complexType>
Complex Type mdSecType
Namespace http://www.loc.gov/METS/v2
Annotations
 
mdSecType: Complex Type for Metadata Sections
The metadata section consists of elements that can contain any kind of metdata, included but not limited to technical metadata technical metadata for text/image/audio/video files, intellectual property rights metadata, analog/digital source metadata, and digital provenance metadata, that is, the history of migrations/translations performed on a digital library object from it's original digital capture/encoding.
Diagram
Used by
Element metsType/mdSec
Model
Children md, mdGrp
Attributes
QName Type Use Annotation
ID xsd:ID optional 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
Wildcard: ANY attribute from ANY namespace OTHER than 'http://www.loc.gov/METS/v2'
Source
 
<xsd:complexType name="mdSecType">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">mdSecType: Complex Type for Metadata Sections The metadata section consists of elements that can contain any kind of metdata, included but not limited to technical metadata technical metadata for text/image/audio/video files, intellectual property rights metadata, analog/digital source metadata, and digital provenance metadata, that is, the history of migrations/translations performed on a digital library object from it's original digital capture/encoding.</xsd:documentation>
  </xsd:annotation>
  <xsd:choice>
    <xsd:element name="mdGrp" maxOccurs="unbounded">
      <xsd:annotation>
        <xsd:documentation>The <mdGrp> element allows grouping related kinds of metadata. This could be all metadata of a particular type, all metadata coming from a particular source, all metadata pertaining to a certain file or set of files, or any other relevant grouping.</xsd:documentation>
      </xsd:annotation>
      <xsd:complexType>
        <xsd:sequence>
          <xsd:element name="md" type="mdType" maxOccurs="unbounded">
            <xsd:annotation>
              <xsd:documentation xml:lang="en">A <md> element records any kind of metadata about the METS object or a component thereof. The <md> element can either wrap the metadata (mdWrap), reference it in an external location (<mdRef>), or both. METS allows multiple <md> elements; and metadata can be associated with any METS element that supports an MDID attribute. Metadata can be expressed according to many current technical description standards or a locally produced XML schema.</xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
        <xsd:attribute name="ID" type="xsd:ID" use="optional">
          <xsd:annotation>
            <xsd:documentation>ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
        <xsd:attribute name="USE" type="xsd:string" use="optional">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">USE (string/O): Specifies the purpose of the metadata contained in this group. Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#mduse-mdgrpuse</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
        <xsd:attribute name="STATUS" type="xsd:string" use="optional">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">STATUS (string/O): Indicates the status of this metadata Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#status-md-mdgrp</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
      </xsd:complexType>
    </xsd:element>
    <xsd:element name="md" type="mdType" maxOccurs="unbounded">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">A <md> element records any kind of metadata about the METS object or a component thereof. The <md> element can either wrap the metadata (mdWrap), reference it in an external location (<mdRef>), or both. METS allows multiple <md> elements; and metadata can be associated with any METS element that supports an MDID attribute. Metadata can be expressed according to many current technical description standards or a locally produced XML schema.</xsd:documentation>
      </xsd:annotation>
    </xsd:element>
  </xsd:choice>
  <xsd:attribute name="ID" type="xsd:ID" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:anyAttribute namespace="##other" processContents="lax"/>
</xsd:complexType>
Complex Type mdType
Namespace http://www.loc.gov/METS/v2
Annotations
 
mdType: Complex Type for Metadata Sections
A generic framework for pointing to/including metadata within a METS document.
Diagram
Used by
Model
Children mdRef, mdWrap
Attributes
QName Type Use Annotation
CREATED xsd:dateTime optional 
CREATED (dateTime/O): Specifies the date and time of creation for the metadata.
GROUPID xsd:string optional 
GROUPID (string/O): This identifier is used to indicate that different metadata sections may be considered as part of a group. Two metadata sections with the same GROUPID value are to be considered part of the same group. For example this facility might be used to group changed versions of the same metadata if previous versions are maintained in a file for tracking purposes.
ID xsd:ID required 
ID (ID/R): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR. The ID attribute on the <md> element is required, and its value should be referenced from one or more MDID attributes that are associated with other elements in the METS document. The following elements support references to a <md> element via a MDID attribute: <file>, <fileGrp> <stream>, <div>, <metsHdr>, <md>.
MDID xsd:IDREFS optional 
MDID (IDREFS/O): Contains the ID attribute values of the <md> elements within the <mdSec> of the METS document that contain metadata pertaining to the current <md> element. Typically used in this context to reference preservation metadata (use="DIGIPROV") which applies to the current metadata.
STATUS xsd:string optional 
STATUS (string/O): Indicates the status of this metadata
Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#status-md-mdgrp
USE xsd:string optional 
USE: Specifies the purpose of metadata in this section.
Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#mduse-mdgrpuse
Wildcard: ANY attribute from ANY namespace OTHER than 'http://www.loc.gov/METS/v2'
Source
 
<xsd:complexType name="mdType">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">mdType: Complex Type for Metadata Sections A generic framework for pointing to/including metadata within a METS document.</xsd:documentation>
  </xsd:annotation>
  <xsd:all>
    <xsd:element name="mdRef" minOccurs="0">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">The metadata reference element <mdRef> element is a generic element used throughout the METS schema to provide a pointer to metadata which resides outside the METS document. NB: <mdRef> is an empty element.</xsd:documentation>
      </xsd:annotation>
      <xsd:complexType>
        <xsd:attribute name="ID" type="xsd:ID" use="optional">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
        <xsd:attributeGroup ref="LOCATION"/>
        <xsd:attributeGroup ref="METADATA"/>
        <xsd:attributeGroup ref="FILECORE"/>
        <xsd:attribute name="LABEL" type="xsd:string" use="optional">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">LABEL (string/O): Provides a label to display to the viewer of the METS document that identifies the associated metadata.</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
      </xsd:complexType>
    </xsd:element>
    <xsd:element name="mdWrap" minOccurs="0">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">A metadata wrapper element <mdWrap> provides a wrapper around metadata embedded within a METS document. The element is repeatable. Such metadata can be in one of two forms: 1) XML-encoded metadata, with the XML-encoding identifying itself as belonging to a namespace other than the METS document namespace. 2) Any arbitrary binary or textual form, PROVIDED that the metadata is Base64 encoded and wrapped in a <binData> element within the internal metadata element.</xsd:documentation>
      </xsd:annotation>
      <xsd:complexType>
        <xsd:choice>
          <xsd:element name="binData" type="xsd:base64Binary" minOccurs="0">
            <xsd:annotation>
              <xsd:documentation xml:lang="en">The binary data wrapper element <binData> is used to contain Base64 encoded metadata.</xsd:documentation>
            </xsd:annotation>
          </xsd:element>
          <xsd:element name="xmlData" minOccurs="0">
            <xsd:annotation>
              <xsd:documentation xml:lang="en">The xml data wrapper element <xmlData> is used to contain XML encoded metadata. The content of an <xmlData> element can be in any namespace or in no namespace. As permitted by the XML Schema Standard, the processContents attribute value for the metadata in an <xmlData> is set to “lax”. Therefore, if the source schema and its location are identified by means of an XML schemaLocation attribute, then an XML processor will validate the elements for which it can find declarations. If a source schema is not identified, or cannot be found at the specified schemaLocation, then an XML validator will check for well-formedness, but otherwise skip over the elements appearing in the <xmlData> element.</xsd:documentation>
            </xsd:annotation>
            <xsd:complexType>
              <xsd:sequence>
                <xsd:any namespace="##any" maxOccurs="unbounded" processContents="lax"/>
              </xsd:sequence>
            </xsd:complexType>
          </xsd:element>
        </xsd:choice>
        <xsd:attribute name="ID" type="xsd:ID" use="optional">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
        <xsd:attributeGroup ref="METADATA"/>
        <xsd:attributeGroup ref="FILECORE"/>
        <xsd:attribute name="LABEL" type="xsd:string" use="optional">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">LABEL: an optional string attribute providing a label to display to the viewer of the METS document identifying the metadata.</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
      </xsd:complexType>
    </xsd:element>
  </xsd:all>
  <xsd:attribute name="ID" type="xsd:ID" use="required">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">ID (ID/R): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR. The ID attribute on the <md> element is required, and its value should be referenced from one or more MDID attributes that are associated with other elements in the METS document. The following elements support references to a <md> element via a MDID attribute: <file>, <fileGrp> <stream>, <div>, <metsHdr>, <md>.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="USE" type="xsd:string" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">USE: Specifies the purpose of metadata in this section. Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#mduse-mdgrpuse</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="GROUPID" type="xsd:string" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">GROUPID (string/O): This identifier is used to indicate that different metadata sections may be considered as part of a group. Two metadata sections with the same GROUPID value are to be considered part of the same group. For example this facility might be used to group changed versions of the same metadata if previous versions are maintained in a file for tracking purposes.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="MDID" type="xsd:IDREFS" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">MDID (IDREFS/O): Contains the ID attribute values of the <md> elements within the <mdSec> of the METS document that contain metadata pertaining to the current <md> element. Typically used in this context to reference preservation metadata (use="DIGIPROV") which applies to the current metadata.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="CREATED" type="xsd:dateTime" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">CREATED (dateTime/O): Specifies the date and time of creation for the metadata.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="STATUS" type="xsd:string" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">STATUS (string/O): Indicates the status of this metadata Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#status-md-mdgrp</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:anyAttribute namespace="##other" processContents="lax"/>
</xsd:complexType>
Complex Type fileGrpType
Namespace http://www.loc.gov/METS/v2
Annotations
 
fileGrpType: Complex Type for File Groups
The file group is used to cluster all of the digital files composing a digital library object. 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).
Diagram
Used by
Model
Children file
Attributes
QName Type Use Annotation
ID xsd:ID optional 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
MDID xsd:IDREFS optional 
MDID (IDREF/O): Contains the ID attribute values of the <md> elements within the <mdSec> of the METS document applicable to all of the files in a particular file group.
USE xsd:string optional 
USE (string/O): A tagging attribute to indicate the intended use of files within this file group. A USE attribute can be expressed at the<fileGrp> level, the <file> level, the <FLocat> level and/or the <FContent> level.  A USE attribute value at the <fileGrp> level should pertain to all of the files in the <fileGrp>.  A USE attribute at the <file> level should pertain to all copies of the file as represented by subsidiary <FLocat> and/or <FContent> elements.  A USE attribute at the <FLocat> or <FContent> level pertains to the particular copy of the file that is either referenced (<FLocat>) or wrapped (<FContent>).

              Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#filegrpuse-fileuse
VERSDATE xsd:dateTime optional 
VERSDATE (dateTime/O): An optional dateTime attribute specifying the date this version/fileGrp of the digital object was created.
Wildcard: ANY attribute from ANY namespace OTHER than 'http://www.loc.gov/METS/v2'
Source
 
<xsd:complexType name="fileGrpType">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">fileGrpType: Complex Type for File Groups The file group is used to cluster all of the digital files composing a digital library object. 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).</xsd:documentation>
  </xsd:annotation>
  <xsd:sequence>
    <xsd:element name="file" maxOccurs="unbounded" type="fileType">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">The file element <file> provides access to the content files for the digital object being described by the METS document. A <file> element may contain one or more <FLocat> elements which provide pointers to a content file and/or a <FContent> element which wraps an encoded version of the file. Embedding files using <FContent> can be a valuable feature for exchanging digital objects between repositories or for archiving versions of digital objects for off-site storage. All <FLocat> and <FContent> elements should identify and/or contain identical copies of a single file. The <file> element is recursive, thus allowing sub-files or component files of a larger file to be listed in the inventory. Alternatively, by using the <stream> element, a smaller component of a file or of a related file can be placed within a <file> element. Finally, by using the <transformFile> element, it is possible to include within a <file> element a different version of a file that has undergone a transformation for some reason, such as format migration.</xsd:documentation>
      </xsd:annotation>
    </xsd:element>
  </xsd:sequence>
  <xsd:attribute name="ID" type="xsd:ID" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="VERSDATE" type="xsd:dateTime" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">VERSDATE (dateTime/O): An optional dateTime attribute specifying the date this version/fileGrp of the digital object was created.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="MDID" type="xsd:IDREFS" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">MDID (IDREF/O): Contains the ID attribute values of the <md> elements within the <mdSec> of the METS document applicable to all of the files in a particular file group.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="USE" type="xsd:string" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">USE (string/O): A tagging attribute to indicate the intended use of files within this file group. A USE attribute can be expressed at the<fileGrp> level, the <file> level, the <FLocat> level and/or the <FContent> level. A USE attribute value at the <fileGrp> level should pertain to all of the files in the <fileGrp>. A USE attribute at the <file> level should pertain to all copies of the file as represented by subsidiary <FLocat> and/or <FContent> elements. A USE attribute at the <FLocat> or <FContent> level pertains to the particular copy of the file that is either referenced (<FLocat>) or wrapped (<FContent>). Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#filegrpuse-fileuse</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:anyAttribute namespace="##other" processContents="lax"/>
</xsd:complexType>
Complex Type fileType
Namespace http://www.loc.gov/METS/v2
Annotations
 
fileType: Complex Type for Files
The file element provides access to content files for a METS object.  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 single file element should identify/contain identical copies of a single file.
Diagram
Used by
Model
Children FContent, FLocat, file, stream, transformFile
Attributes
QName Type Use Annotation
BEGIN xsd:string optional 
BEGIN (string/O): An attribute that specifies the point in the parent <file> where the current <file> begins.  When used in conjunction with a <file> element, this attribute is only meaningful when this element is nested, and its parent <file> element represents a container file. It can be used in conjunction with the END attribute as a means of defining the location of the current file within its parent file. However, the BEGIN attribute can be used with or without a companion END attribute. When no END attribute is specified, the end of the parent file is assumed also to be the end point of the current file. The BEGIN and END attributes can only be interpreted meaningfully in conjunction with a BETYPE attribute, which specifies the kind of beginning/ending point values that are being used.
BETYPE xsd:string optional 
BETYPE: Begin/End Type.
BETYPE (string/O): An attribute that specifies the kind of BEGIN and/or END values that are being used.
     Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#filebetype-streambetype
CHECKSUM xsd:string optional 
CHECKSUM (string/O): Provides a checksum value for the associated file or wrapped content.
CHECKSUMTYPE xsd:string optional 
CHECKSUMTYPE (enumerated string/O): Specifies the checksum algorithm used to produce the value contained in the CHECKSUM attribute.
Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#checksumtype-file-mdref-mdwrap
CREATED xsd:dateTime optional 
CREATED (dateTime/O): Specifies the date and time of creation for the associated file or wrapped content.
END xsd:string optional 
END (string/O): An attribute that specifies the point in the parent <file> where the current, nested <file> ends. It can only be interpreted meaningfully in conjunction with the BETYPE, which specifies the kind of ending point values being used. Typically the END attribute would only appear in conjunction with a BEGIN attribute.
GROUPID xsd:string optional 
GROUPID (string/O): 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 the derivative files made from it in other file groups.
ID xsd:ID required 
ID (ID/R): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR. Typically, the ID attribute value on a <file> element would be referenced from one or more FILEID attributes (which are of type IDREF) on <fptr>and/or <area> elements within the <structMap>.  Such references establish links between  structural divisions (<div> elements) and the specific content files or parts of content files that manifest them.
MDID xsd:IDREFS optional 
MDID (IDREFS/O): Contains the ID attribute values of the <md> elements within the <mdSec> of the METS document that contain metadata pertaining to the file.
MIMETYPE xsd:string optional 
MIMETYPE (string/O): The IANA media type (formerly known as MIME type) for the associated file or wrapped content.

        Registered media/MIME types: https://www.iana.org/assignments/media-types/media-types.xhtml
OWNERID xsd:string optional 
OWNERID (string/O): A unique identifier assigned to the file by its owner.  This may be a URI which differs from the URI used to retrieve the file.
SEQ xsd:int optional 
SEQ (integer/O): Indicates the sequence of this <file> relative to the others in its <fileGrp>.
SIZE xsd:long optional 
SIZE (long/O): Specifies the size in bytes of the associated file or wrapped content.
USE xsd:string optional 
USE (string/O): A tagging attribute to indicate the intended use of all copies of the file aggregated by the <file> element. A USE attribute can be expressed at the<fileGrp> level, the <file> level, the <FLocat> level and/or the <FContent> level.  A USE attribute value at the <fileGrp> level should pertain to all of the files in the <fileGrp>.  A USE attribute at the <file> level should pertain to all copies of the file as represented by subsidiary <FLocat> and/or <FContent> elements.  A USE attribute at the <FLocat> or <FContent> level pertains to the particular copy of the file that is either referenced (<FLocat>) or wrapped (<FContent>).

              Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#filegrpuse-fileuse
Wildcard: ANY attribute from ANY namespace OTHER than 'http://www.loc.gov/METS/v2'
Source
 
<xsd:complexType name="fileType">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">fileType: Complex Type for Files The file element provides access to content files for a METS object. 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 single file element should identify/contain identical copies of a single file.</xsd:documentation>
  </xsd:annotation>
  <xsd:sequence>
    <xsd:element name="FLocat" minOccurs="0" maxOccurs="unbounded">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">The file location element <FLocat> provides a pointer to the location of a content file. NOTE: <FLocat> is an empty element.</xsd:documentation>
      </xsd:annotation>
      <xsd:complexType>
        <xsd:attribute name="ID" type="xsd:ID" use="optional">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
        <xsd:attribute name="USE" type="xsd:string" use="optional">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">USE (string/O): A tagging attribute to indicate the intended use of the specific copy of the file represented by the <FLocat> element. A USE attribute can be expressed at the<fileGrp> level, the <file> level, the <FLocat> level and/or the <FContent> level. A USE attribute value at the <fileGrp> level should pertain to all of the files in the <fileGrp>. A USE attribute at the <file> level should pertain to all copies of the file as represented by subsidiary <FLocat> and/or <FContent> elements. A USE attribute at the <FLocat> or <FContent> level pertains to the particular copy of the file that is either referenced (<FLocat>) or wrapped (<FContent>). Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#flocatuse-fcontentuse</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
        <xsd:attributeGroup ref="LOCATION"/>
      </xsd:complexType>
    </xsd:element>
    <xsd:element name="FContent" minOccurs="0">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">The file content element <FContent> is used to identify a content file contained internally within a METS document. The content file must be either Base64 encoded and contained within the subsidiary <binData> wrapper element, or consist of XML information and be contained within the subsidiary <xmlData> wrapper element.</xsd:documentation>
      </xsd:annotation>
      <xsd:complexType>
        <xsd:choice>
          <xsd:element name="binData" type="xsd:base64Binary" minOccurs="0">
            <xsd:annotation>
              <xsd:documentation xml:lang="en">A binary data wrapper element <binData> is used to contain a Base64 encoded file.</xsd:documentation>
            </xsd:annotation>
          </xsd:element>
          <xsd:element name="xmlData" minOccurs="0">
            <xsd:annotation>
              <xsd:documentation xml:lang="en">An xml data wrapper element <xmlData> is used to contain an XML encoded file. The content of an <xmlData> element can be in any namespace or in no namespace. As permitted by the XML Schema Standard, the processContents attribute value for the metadata in an <xmlData> element is set to “lax”. Therefore, if the source schema and its location are identified by means of an xsi:schemaLocation attribute, then an XML processor will validate the elements for which it can find declarations. If a source schema is not identified, or cannot be found at the specified schemaLocation, then an XML validator will check for well-formedness, but otherwise skip over the elements appearing in the <xmlData> element.</xsd:documentation>
            </xsd:annotation>
            <xsd:complexType>
              <xsd:sequence>
                <xsd:any namespace="##any" maxOccurs="unbounded" processContents="lax"/>
              </xsd:sequence>
            </xsd:complexType>
          </xsd:element>
        </xsd:choice>
        <xsd:attribute name="ID" type="xsd:ID" use="optional">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
        <xsd:attribute name="USE" type="xsd:string" use="optional">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">USE (string/O): A tagging attribute to indicate the intended use of the specific copy of the file represented by the <FContent> element. A USE attribute can be expressed at the<fileGrp> level, the <file> level, the <FLocat> level and/or the <FContent> level. A USE attribute value at the <fileGrp> level should pertain to all of the files in the <fileGrp>. A USE attribute at the <file> level should pertain to all copies of the file as represented by subsidiary <FLocat> and/or <FContent> elements. A USE attribute at the <FLocat> or <FContent> level pertains to the particular copy of the file that is either referenced (<FLocat>) or wrapped (<FContent>). Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#flocatuse-fcontentuse</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
      </xsd:complexType>
    </xsd:element>
    <xsd:element name="stream" minOccurs="0" maxOccurs="unbounded">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">A component byte stream element <stream> may be composed of one or more subsidiary streams. An MPEG4 file, for example, might contain separate audio and video streams, each of which is associated with technical metadata. The repeatable <stream> element provides a mechanism to record the existence of separate data streams within a particular file, and the opportunity to <mdSec> elements with those subsidiary data streams if desired.</xsd:documentation>
      </xsd:annotation>
      <xsd:complexType>
        <xsd:complexContent>
          <xsd:restriction base="xsd:anyType">
            <xsd:attribute name="ID" type="xsd:ID" use="optional">
              <xsd:annotation>
                <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
              </xsd:annotation>
            </xsd:attribute>
            <xsd:attribute name="streamType" type="xsd:string" use="optional">
              <xsd:annotation>
                <xsd:documentation xml:lang="en">streamType (string/O): The IANA MIME media type for the bytestream.</xsd:documentation>
              </xsd:annotation>
            </xsd:attribute>
            <xsd:attribute name="OWNERID" type="xsd:string" use="optional">
              <xsd:annotation>
                <xsd:documentation xml:lang="en">OWNERID (string/O): Used to provide a unique identifier (which could include a URI) assigned to the file. This identifier may differ from the URI used to retrieve the file.</xsd:documentation>
              </xsd:annotation>
            </xsd:attribute>
            <xsd:attribute name="MDID" type="xsd:IDREFS" use="optional">
              <xsd:annotation>
                <xsd:documentation xml:lang="en">MDID (IDREFS/O): Contains the ID attribute values of the <md> elements within the <mdSec> of the METS document that contain metadata pertaining to the bytestream.</xsd:documentation>
              </xsd:annotation>
            </xsd:attribute>
            <xsd:attribute name="BEGIN" type="xsd:string" use="optional">
              <xsd:annotation>
                <xsd:documentation xml:lang="en">BEGIN (string/O): An attribute that specifies the point in the parent <file> where the current <stream> begins. It can be used in conjunction with the END attribute as a means of defining the location of the stream within its parent file. However, the BEGIN attribute can be used with or without a companion END attribute. When no END attribute is specified, the end of the parent file is assumed also to be the end point of the stream. The BEGIN and END attributes can only be interpreted meaningfully in conjunction with a BETYPE attribute, which specifies the kind of beginning/ending point values that are being used.</xsd:documentation>
              </xsd:annotation>
            </xsd:attribute>
            <xsd:attribute name="END" type="xsd:string" use="optional">
              <xsd:annotation>
                <xsd:documentation xml:lang="en">END (string/O): An attribute that specifies the point in the parent <file> where the <stream> ends. It can only be interpreted meaningfully in conjunction with the BETYPE, which specifies the kind of ending point values being used. Typically the END attribute would only appear in conjunction with a BEGIN attribute.</xsd:documentation>
              </xsd:annotation>
            </xsd:attribute>
            <xsd:attribute name="BETYPE" use="optional" type="xsd:string">
              <xsd:annotation>
                <xsd:documentation xml:lang="en">BETYPE: Begin/End Type. BETYPE (string/O): An attribute that specifies the kind of BEGIN and/or END values that are being used. Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#filebetype-streambetype</xsd:documentation>
              </xsd:annotation>
            </xsd:attribute>
          </xsd:restriction>
        </xsd:complexContent>
      </xsd:complexType>
    </xsd:element>
    <xsd:element name="transformFile" minOccurs="0" maxOccurs="unbounded">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">The transform file element <transformFile> provides a means to access any subsidiary files listed below a <file> element by indicating the steps required to "unpack" or transform the subsidiary files. This element is repeatable.</xsd:documentation>
      </xsd:annotation>
      <xsd:complexType>
        <xsd:complexContent>
          <xsd:restriction base="xsd:anyType">
            <xsd:attribute name="ID" type="xsd:ID" use="optional">
              <xsd:annotation>
                <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
              </xsd:annotation>
            </xsd:attribute>
            <xsd:attribute name="TRANSFORMTYPE" use="required" type="xsd:string">
              <xsd:annotation>
                <xsd:documentation xml:lang="en">TRANSFORMTYPE (string/R): Is used to indicate the type of transformation needed to render content of a file accessible. This may include unpacking a file into subsidiary files/streams. Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#transformfiletransformtype</xsd:documentation>
              </xsd:annotation>
            </xsd:attribute>
            <xsd:attribute name="TRANSFORMALGORITHM" type="xsd:string" use="required">
              <xsd:annotation>
                <xsd:documentation xml:lang="en">TRANSFORMALGORITHM (string/R): Specifies the decompression or decryption routine used to access the contents of the file. Algorithms for compression can be either loss-less or lossy.</xsd:documentation>
              </xsd:annotation>
            </xsd:attribute>
            <xsd:attribute name="TRANSFORMKEY" type="xsd:string" use="optional">
              <xsd:annotation>
                <xsd:documentation xml:lang="en">TRANSFORMKEY (string/O): A key to be used with the transform algorithm for accessing the file’s contents.</xsd:documentation>
              </xsd:annotation>
            </xsd:attribute>
            <xsd:attribute name="TRANSFORMORDER" type="xsd:positiveInteger" use="required">
              <xsd:annotation>
                <xsd:documentation xml:lang="en">TRANSFORMORDER (postive-integer/R): The order in which the instructions must be followed in order to unpack or transform the container file.</xsd:documentation>
              </xsd:annotation>
            </xsd:attribute>
          </xsd:restriction>
        </xsd:complexContent>
      </xsd:complexType>
    </xsd:element>
    <xsd:element name="file" type="fileType" minOccurs="0" maxOccurs="unbounded"/>
  </xsd:sequence>
  <xsd:attribute name="ID" type="xsd:ID" use="required">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">ID (ID/R): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR. Typically, the ID attribute value on a <file> element would be referenced from one or more FILEID attributes (which are of type IDREF) on <fptr>and/or <area> elements within the <structMap>. Such references establish links between structural divisions (<div> elements) and the specific content files or parts of content files that manifest them.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="SEQ" type="xsd:int" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">SEQ (integer/O): Indicates the sequence of this <file> relative to the others in its <fileGrp>.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attributeGroup ref="FILECORE"/>
  <xsd:attribute name="OWNERID" type="xsd:string" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">OWNERID (string/O): A unique identifier assigned to the file by its owner. This may be a URI which differs from the URI used to retrieve the file.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="MDID" type="xsd:IDREFS" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">MDID (IDREFS/O): Contains the ID attribute values of the <md> elements within the <mdSec> of the METS document that contain metadata pertaining to the file.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="GROUPID" type="xsd:string" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">GROUPID (string/O): 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 the derivative files made from it in other file groups.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="USE" type="xsd:string" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">USE (string/O): A tagging attribute to indicate the intended use of all copies of the file aggregated by the <file> element. A USE attribute can be expressed at the<fileGrp> level, the <file> level, the <FLocat> level and/or the <FContent> level. A USE attribute value at the <fileGrp> level should pertain to all of the files in the <fileGrp>. A USE attribute at the <file> level should pertain to all copies of the file as represented by subsidiary <FLocat> and/or <FContent> elements. A USE attribute at the <FLocat> or <FContent> level pertains to the particular copy of the file that is either referenced (<FLocat>) or wrapped (<FContent>). Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#filegrpuse-fileuse</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="BEGIN" type="xsd:string" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">BEGIN (string/O): An attribute that specifies the point in the parent <file> where the current <file> begins. When used in conjunction with a <file> element, this attribute is only meaningful when this element is nested, and its parent <file> element represents a container file. It can be used in conjunction with the END attribute as a means of defining the location of the current file within its parent file. However, the BEGIN attribute can be used with or without a companion END attribute. When no END attribute is specified, the end of the parent file is assumed also to be the end point of the current file. The BEGIN and END attributes can only be interpreted meaningfully in conjunction with a BETYPE attribute, which specifies the kind of beginning/ending point values that are being used.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="END" type="xsd:string" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">END (string/O): An attribute that specifies the point in the parent <file> where the current, nested <file> ends. It can only be interpreted meaningfully in conjunction with the BETYPE, which specifies the kind of ending point values being used. Typically the END attribute would only appear in conjunction with a BEGIN attribute.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="BETYPE" use="optional" type="xsd:string">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">BETYPE: Begin/End Type. BETYPE (string/O): An attribute that specifies the kind of BEGIN and/or END values that are being used. Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#filebetype-streambetype</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:anyAttribute namespace="##other" processContents="lax"/>
</xsd:complexType>
Complex Type structMapType
Namespace http://www.loc.gov/METS/v2
Annotations
 
structMapType: Complex Type for Structural Maps
The structural map (structMap) outlines a hierarchical structure for the original object being encoded, using a series of nested div elements.
Diagram
Used by
Model
Children div
Attributes
QName Type Use Annotation
ID xsd:ID optional 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
LABEL xsd:string optional 
LABEL (string/O): Describes the <structMap> to viewers of the METS document. This would be useful primarily where more than one <structMap> is provided for a single object. A descriptive LABEL value, in that case, could clarify to users the purpose of each of the available structMaps.
TYPE xsd:string optional 
TYPE (string/O): Identifies the type of structure represented by the <structMap>. For example, a <structMap> that represented a purely logical or intellectual structure could be assigned a TYPE value of “logical” whereas a <structMap> that represented a purely physical structure could be assigned a TYPE value of “physical”. However, the METS schema neither defines nor requires a common vocabulary for this attribute. A METS profile, however, may well constrain the values for the <structMap> TYPE.

        Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#structmaptype
Wildcard: ANY attribute from ANY namespace OTHER than 'http://www.loc.gov/METS/v2'
Source
 
<xsd:complexType name="structMapType">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">structMapType: Complex Type for Structural Maps The structural map (structMap) outlines a hierarchical structure for the original object being encoded, using a series of nested div elements.</xsd:documentation>
  </xsd:annotation>
  <xsd:sequence>
    <xsd:element name="div" type="divType">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">The structural divisions of the hierarchical organization provided by a <structMap> are represented by division <div> elements, which can be nested to any depth. Each <div> element can represent either an intellectual (logical) division or a physical division. 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:annotation>
      <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="TYPE" type="xsd:string" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">TYPE (string/O): Identifies the type of structure represented by the <structMap>. For example, a <structMap> that represented a purely logical or intellectual structure could be assigned a TYPE value of “logical” whereas a <structMap> that represented a purely physical structure could be assigned a TYPE value of “physical”. However, the METS schema neither defines nor requires a common vocabulary for this attribute. A METS profile, however, may well constrain the values for the <structMap> TYPE. Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#structmaptype</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="LABEL" type="xsd:string" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">LABEL (string/O): Describes the <structMap> to viewers of the METS document. This would be useful primarily where more than one <structMap> is provided for a single object. A descriptive LABEL value, in that case, could clarify to users the purpose of each of the available structMaps.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:anyAttribute namespace="##other" processContents="lax"/>
</xsd:complexType>
Complex Type divType
Namespace http://www.loc.gov/METS/v2
Annotations
 
divType: Complex Type for Divisions
					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.

SPECIAL NOTE REGARDING DIV ATTRIBUTE VALUES:
to clarify the differences between the ORDER, ORDERLABEL, and LABEL attributes for the <div> element, 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".
Diagram
Used by
Model
Children div, fptr, mptr
Attributes
QName Type Use Annotation
CONTENTIDS URIs optional 
CONTENTIDS (URI/O): Content IDs for the content represented by the <div> (equivalent to DIDL DII or Digital Item Identifier, a unique external ID).
ID xsd:ID optional 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
LABEL xsd:string optional 
LABEL (string/O): An attribute used, for example, to identify a <div> to an end user viewing the document. Thus a hierarchical arrangement of the <div> LABEL values could provide a table of contents to the digital content represented by a METS document and facilitate the users’ navigation of the digital object. Note that 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 . For further of the distinction between LABEL and ORDERLABEL see the description of the ORDERLABEL attribute.
MDID xsd:IDREFS optional 
MDID (IDREFS/O): Contains the ID attribute values identifying the <md> elements within the <mdSec> of the METS document that contain or link to metadata pertaining to the structural division represented by the <div> element.
ORDER xsd:integer optional 
ORDER (integer/O): A representation of the element's order among its siblings (e.g., its absolute, numeric sequence). For an example, and clarification of the distinction between ORDER and ORDERLABEL, see the description of the ORDERLABEL attribute.
ORDERLABEL xsd:string optional 
ORDERLABEL (string/O): A representation of the element's order among its siblings (e.g., “xii”), or of any non-integer native numbering system. It is presumed that this value will still be machine actionable (e.g., it would support ‘go to page ___’ function), and it should not be used as a replacement/substitute for the LABEL attribute. To understand 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”.
TYPE xsd:string optional 
TYPE (string/O): An attribute that specifies the type of structural division that the <div> element represents.

          Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#divtype
Source
 
<xsd:complexType name="divType">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">divType: Complex Type for Divisions 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. SPECIAL NOTE REGARDING DIV ATTRIBUTE VALUES: to clarify the differences between the ORDER, ORDERLABEL, and LABEL attributes for the <div> element, 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".</xsd:documentation>
  </xsd:annotation>
  <xsd:sequence>
    <xsd:element name="mptr" minOccurs="0" maxOccurs="unbounded">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">Like the <fptr> element, the METS pointer element <mptr> represents digital content that manifests its parent <div> element. Unlike the <fptr>, which either directly or indirectly points to content represented in the <fileSec> of the parent METS document, the <mptr> element points to content represented by an external METS document. Thus, this element allows multiple discrete and separate METS documents to be organized at a higher level by a separate METS document. For example, METS documents representing the individual issues in the series of a journal could be grouped together and organized by a higher level METS document that represents the entire journal series. Each of the <div> elements in the <structMap> of the METS document representing the journal series would point to a METS document representing an issue. It would do so via a child <mptr> element. Thus the <mptr> element gives METS users considerable flexibility in managing the depth of the <structMap> hierarchy of individual METS documents. The <mptr> element points to an external METS document.</xsd:documentation>
      </xsd:annotation>
      <xsd:complexType>
        <xsd:attribute name="ID" type="xsd:ID" use="optional">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
        <xsd:attributeGroup ref="LOCATION"/>
        <xsd:attribute name="CONTENTIDS" type="URIs" use="optional">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">CONTENTIDS (URI/O): Content IDs for the content represented by the <mptr> (equivalent to DIDL DII or Digital Item Identifier, a unique external ID).</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
      </xsd:complexType>
    </xsd:element>
    <xsd:element name="fptr" minOccurs="0" maxOccurs="unbounded">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">The <fptr> or file pointer element represents digital content that manifests its parent <div> element. The content represented by an <fptr> element must consist of integral files or parts of files that are represented by <file> elements in the <fileSec>. Via its FILEID attribute, an <fptr> may point directly to a single integral <file> element that manifests a structural division. However, an <fptr> element may also govern an <area> element, a <par>, or a <seq> which in turn would point to the relevant file or files. A child <area> element can point to part of a <file> that manifests a division, while the <par> and <seq> elements can point to multiple files or parts of files that together manifest a division. More than one <fptr> element can be associated with a <div> element. Typically sibling <fptr> elements represent alternative versions, or manifestations, of the same content</xsd:documentation>
      </xsd:annotation>
      <xsd:complexType>
        <xsd:choice>
          <xsd:element name="par" type="parType" minOccurs="0">
            <xsd:annotation>
              <xsd:documentation xml:lang="en">The <par> or parallel files element aggregates pointers to files, parts of files, and/or sequences of files or parts of files that must be played or displayed simultaneously to manifest a block of digital content represented by an <fptr> element. This might be the case, for example, with multi-media content, where a still image might have an accompanying audio track that comments on the still image. In this case, a <par> element would aggregate two <area> elements, one of which pointed to the image file and one of which pointed to the audio file that must be played in conjunction with the image. The <area> element associated with the image could be further qualified with SHAPE and COORDS attributes if only a portion of the image file was pertinent and the <area> element associated with the audio file could be further qualified with BETYPE, BEGIN, EXTTYPE, and EXTENT attributes if only a portion of the associated audio file should be played in conjunction with the image.</xsd:documentation>
            </xsd:annotation>
          </xsd:element>
          <xsd:element name="seq" type="seqType" minOccurs="0">
            <xsd:annotation>
              <xsd:documentation xml:lang="en">The sequence of files element <seq> aggregates pointers to files, parts of files and/or parallel sets of files or parts of files that must be played or displayed sequentially to manifest a block of digital content. This might be the case, for example, if the parent <div> element represented a logical division, such as a diary entry, that spanned multiple pages of a diary and, hence, multiple page image files. In this case, a <seq> element would aggregate multiple, sequentially arranged <area> elements, each of which pointed to one of the image files that must be presented sequentially to manifest the entire diary entry. If the diary entry started in the middle of a page, then the first <area> element (representing the page on which the diary entry starts) might be further qualified, via its SHAPE and COORDS attributes, to specify the specific, pertinent area of the associated image file.</xsd:documentation>
            </xsd:annotation>
          </xsd:element>
          <xsd:element name="area" type="areaType" minOccurs="0">
            <xsd:annotation>
              <xsd:documentation xml:lang="en">The area element <area> typically points to content consisting of just a portion or area of a file represented by a <file> element in the <fileSec>. In some contexts, however, the <area> element can also point to content represented by an integral file. A single <area> element would appear as the direct child of a <fptr> element when only a portion of a <file>, rather than an integral <file>, manifested the digital content represented by the <fptr>. Multiple <area> elements would appear as the direct children of a <par> element or a <seq> element when multiple files or parts of files manifested the digital content represented by an <fptr> element. When used in the context of a <par> or <seq> element an <area> element can point either to an integral file or to a segment of a file as necessary.</xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:choice>
        <xsd:attribute name="ID" type="xsd:ID" use="optional">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
        <xsd:attribute name="FILEID" type="xsd:IDREF" use="optional">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">FILEID (IDREF/O): An optional attribute that provides the XML ID identifying the <file> element that links to and/or contains the digital content represented by the <fptr>. A <fptr> element should only have a FILEID attribute value if it does not have a child <area>, <par> or <seq> element. If it has a child element, then the responsibility for pointing to the relevant content falls to this child element or its descendants.</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
        <xsd:attribute name="CONTENTIDS" type="URIs" use="optional">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">CONTENTIDS (URI/O): Content IDs for the content represented by the <fptr> (equivalent to DIDL DII or Digital Item Identifier, a unique external ID).</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
        <xsd:anyAttribute namespace="##other" processContents="lax"/>
      </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:annotation>
      <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attributeGroup ref="ORDERLABELS"/>
  <xsd:attribute name="MDID" type="xsd:IDREFS" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">MDID (IDREFS/O): Contains the ID attribute values identifying the <md> elements within the <mdSec> of the METS document that contain or link to metadata pertaining to the structural division represented by the <div> element.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="TYPE" type="xsd:string" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">TYPE (string/O): An attribute that specifies the type of structural division that the <div> element represents. Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#divtype</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="CONTENTIDS" type="URIs" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">CONTENTIDS (URI/O): Content IDs for the content represented by the <div> (equivalent to DIDL DII or Digital Item Identifier, a unique external ID).</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
</xsd:complexType>
Simple Type URIs
Namespace http://www.loc.gov/METS/v2
Diagram
Type list of xsd:anyURI
Used by
Source
 
<xsd:simpleType name="URIs">
  <xsd:list itemType="xsd:anyURI"/>
</xsd:simpleType>
Complex Type parType
Namespace http://www.loc.gov/METS/v2
Annotations
 
parType: Complex Type for Parallel Files
The <par> or parallel files element aggregates pointers to files, parts of files, and/or sequences of files or parts of files that must be played or displayed simultaneously to manifest a block of digital content represented by an <fptr> element.
Diagram
Used by
Model
Children area, seq
Attributes
QName Type Use Annotation
ID xsd:ID optional 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
LABEL xsd:string optional 
LABEL (string/O): An attribute used, for example, to identify a <div> to an end user viewing the document. Thus a hierarchical arrangement of the <div> LABEL values could provide a table of contents to the digital content represented by a METS document and facilitate the users’ navigation of the digital object. Note that 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 . For further of the distinction between LABEL and ORDERLABEL see the description of the ORDERLABEL attribute.
ORDER xsd:integer optional 
ORDER (integer/O): A representation of the element's order among its siblings (e.g., its absolute, numeric sequence). For an example, and clarification of the distinction between ORDER and ORDERLABEL, see the description of the ORDERLABEL attribute.
ORDERLABEL xsd:string optional 
ORDERLABEL (string/O): A representation of the element's order among its siblings (e.g., “xii”), or of any non-integer native numbering system. It is presumed that this value will still be machine actionable (e.g., it would support ‘go to page ___’ function), and it should not be used as a replacement/substitute for the LABEL attribute. To understand 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”.
Wildcard: ANY attribute from ANY namespace OTHER than 'http://www.loc.gov/METS/v2'
Source
 
<xsd:complexType name="parType">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">parType: Complex Type for Parallel Files The <par> or parallel files element aggregates pointers to files, parts of files, and/or sequences of files or parts of files that must be played or displayed simultaneously to manifest a block of digital content represented by an <fptr> element.</xsd:documentation>
  </xsd:annotation>
  <xsd:choice maxOccurs="unbounded">
    <xsd:element name="area" type="areaType" minOccurs="0"/>
    <xsd:element name="seq" type="seqType" minOccurs="0"/>
  </xsd:choice>
  <xsd:attribute name="ID" type="xsd:ID" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attributeGroup ref="ORDERLABELS"/>
  <xsd:anyAttribute namespace="##other" processContents="lax"/>
</xsd:complexType>
Complex Type areaType
Namespace http://www.loc.gov/METS/v2
Annotations
 
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; all information is recorded within its various attributes.
Diagram
Used by
Attributes
QName Type Use Annotation
BEGIN xsd:string optional 
BEGIN (string/O): An attribute that specifies the point in the content file where the relevant section of content begins. It can be used in conjunction with either the END attribute or the EXTENT attribute as a means of defining the relevant portion of the referenced file precisely. It can only be interpreted meaningfully in conjunction with the BETYPE or EXTTYPE, which specify the kind of beginning/ending point values or beginning/extent values that are being used. The BEGIN attribute can be used with or without a companion END or EXTENT element. In this case, the end of the content file is assumed to be the end point.
BETYPE xsd:string optional 
BETYPE: Begin/End Type.
					BETYPE (string/O): An attribute that specifies the kind of BEGIN and/or END values that are being used. For example, if BYTE is specified, then the BEGIN and END point values represent the byte offsets into a file. If IDREF is specified, then the BEGIN element specifies the ID value that identifies the element in a structured text file where the relevant section of the file begins; and the END value (if present) would specify the ID value that identifies the element with which the relevant section of the file ends.

        Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#areabetype
CONTENTIDS URIs optional 
CONTENTIDS (URI/O): Content IDs for the content represented by the <area> (equivalent to DIDL DII or Digital Item Identifier, a unique external ID).
COORDS xsd:string optional 
COORDS (string/O): Specifies the coordinates in an image map for the shape of the pertinent area as specified in the SHAPE attribute. While technically optional, SHAPE and COORDS must both appear together to define the relevant area of image content. COORDS should be used in conjunction with SHAPE in the manner defined for the COORDs and SHAPE attributes on an HTML5 <area> element. COORDS must be a comma delimited string of integer value pairs representing coordinates (plus radius in the case of CIRCLE) within an image. Number of coordinates pairs depends on shape: RECT: x1, y1, x2, y2; CIRC: x1, y1; POLY: x1, y1, x2, y2, x3, y3 . . .
END xsd:string optional 
END (string/O): An attribute that specifies the point in the content file where the relevant section of content ends. It can only be interpreted meaningfully in conjunction with the BETYPE, which specifies the kind of ending point values being used. Typically the END attribute would only appear in conjunction with a BEGIN element.
EXTENT xsd:string optional 
EXTENT (string/O): An attribute that specifies the extent of the relevant section of the content file. Can only be interpreted meaningfully in conjunction with the EXTTYPE which specifies the kind of value that is being used. Typically the EXTENT attribute would only appear in conjunction with a BEGIN element and would not be used if the BEGIN point represents an IDREF.
EXTTYPE xsd:string optional 
EXTTYPE (string/O): An attribute that specifies the kind of EXTENT values that are being used. For example if BYTE is specified then EXTENT would represent a byte count. If TIME is specified the EXTENT would represent a duration of time.

        Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#areaexttype.
FILEID xsd:IDREF required 
FILEID (IDREF/R): An attribute which provides the XML ID value that identifies the <file> element in the <fileSec> that then points to and/or contains the digital content represented by the <area> element. It must contain an ID value represented in an ID attribute associated with a <file> element in the <fileSec> element in the same METS document.
ID xsd:ID optional 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
LABEL xsd:string optional 
LABEL (string/O): An attribute used, for example, to identify a <div> to an end user viewing the document. Thus a hierarchical arrangement of the <div> LABEL values could provide a table of contents to the digital content represented by a METS document and facilitate the users’ navigation of the digital object. Note that 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 . For further of the distinction between LABEL and ORDERLABEL see the description of the ORDERLABEL attribute.
MDID xsd:IDREFS optional 
MDID (IDREFS/O): Contains the ID attribute values identifying the <md> elements within the <mdSec> of the METS document that contain or link to metadata pertaining to the content represented by the <area> element.
ORDER xsd:integer optional 
ORDER (integer/O): A representation of the element's order among its siblings (e.g., its absolute, numeric sequence). For an example, and clarification of the distinction between ORDER and ORDERLABEL, see the description of the ORDERLABEL attribute.
ORDERLABEL xsd:string optional 
ORDERLABEL (string/O): A representation of the element's order among its siblings (e.g., “xii”), or of any non-integer native numbering system. It is presumed that this value will still be machine actionable (e.g., it would support ‘go to page ___’ function), and it should not be used as a replacement/substitute for the LABEL attribute. To understand 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”.
SHAPE xsd:string optional 
SHAPE (string/O): An attribute that can be used as in HTML to define the shape of the relevant area within the content file pointed to by the <area> element. Typically this would be used with image content (still image or video frame) when only a portion of an image pertains. If SHAPE is specified then COORDS must also be present. SHAPE should be used in conjunction with COORDS in the manner defined for the shape and coords attributes on an HTML5 <area> element. Recommended attribute values are those allowed by HTML5; see also https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#areashape
Wildcard: ANY attribute from ANY namespace OTHER than 'http://www.loc.gov/METS/v2'
Source
 
<xsd:complexType name="areaType">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">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; all information is recorded within its various attributes.</xsd:documentation>
  </xsd:annotation>
  <xsd:attribute name="ID" type="xsd:ID" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="FILEID" type="xsd:IDREF" use="required">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">FILEID (IDREF/R): An attribute which provides the XML ID value that identifies the <file> element in the <fileSec> that then points to and/or contains the digital content represented by the <area> element. It must contain an ID value represented in an ID attribute associated with a <file> element in the <fileSec> element in the same METS document.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="SHAPE" type="xsd:string" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">SHAPE (string/O): An attribute that can be used as in HTML to define the shape of the relevant area within the content file pointed to by the <area> element. Typically this would be used with image content (still image or video frame) when only a portion of an image pertains. If SHAPE is specified then COORDS must also be present. SHAPE should be used in conjunction with COORDS in the manner defined for the shape and coords attributes on an HTML5 <area> element. Recommended attribute values are those allowed by HTML5; see also https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#areashape</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="COORDS" type="xsd:string" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">COORDS (string/O): Specifies the coordinates in an image map for the shape of the pertinent area as specified in the SHAPE attribute. While technically optional, SHAPE and COORDS must both appear together to define the relevant area of image content. COORDS should be used in conjunction with SHAPE in the manner defined for the COORDs and SHAPE attributes on an HTML5 <area> element. COORDS must be a comma delimited string of integer value pairs representing coordinates (plus radius in the case of CIRCLE) within an image. Number of coordinates pairs depends on shape: RECT: x1, y1, x2, y2; CIRC: x1, y1; POLY: x1, y1, x2, y2, x3, y3 . . .</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="BEGIN" type="xsd:string" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">BEGIN (string/O): An attribute that specifies the point in the content file where the relevant section of content begins. It can be used in conjunction with either the END attribute or the EXTENT attribute as a means of defining the relevant portion of the referenced file precisely. It can only be interpreted meaningfully in conjunction with the BETYPE or EXTTYPE, which specify the kind of beginning/ending point values or beginning/extent values that are being used. The BEGIN attribute can be used with or without a companion END or EXTENT element. In this case, the end of the content file is assumed to be the end point.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="END" type="xsd:string" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">END (string/O): An attribute that specifies the point in the content file where the relevant section of content ends. It can only be interpreted meaningfully in conjunction with the BETYPE, which specifies the kind of ending point values being used. Typically the END attribute would only appear in conjunction with a BEGIN element.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="BETYPE" type="xsd:string" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">BETYPE: Begin/End Type. BETYPE (string/O): An attribute that specifies the kind of BEGIN and/or END values that are being used. For example, if BYTE is specified, then the BEGIN and END point values represent the byte offsets into a file. If IDREF is specified, then the BEGIN element specifies the ID value that identifies the element in a structured text file where the relevant section of the file begins; and the END value (if present) would specify the ID value that identifies the element with which the relevant section of the file ends. Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#areabetype</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="EXTENT" type="xsd:string" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">EXTENT (string/O): An attribute that specifies the extent of the relevant section of the content file. Can only be interpreted meaningfully in conjunction with the EXTTYPE which specifies the kind of value that is being used. Typically the EXTENT attribute would only appear in conjunction with a BEGIN element and would not be used if the BEGIN point represents an IDREF.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="EXTTYPE" type="xsd:string" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">EXTTYPE (string/O): An attribute that specifies the kind of EXTENT values that are being used. For example if BYTE is specified then EXTENT would represent a byte count. If TIME is specified the EXTENT would represent a duration of time. Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#areaexttype.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="MDID" type="xsd:IDREFS" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">MDID (IDREFS/O): Contains the ID attribute values identifying the <md> elements within the <mdSec> of the METS document that contain or link to metadata pertaining to the content represented by the <area> element.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="CONTENTIDS" type="URIs" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">CONTENTIDS (URI/O): Content IDs for the content represented by the <area> (equivalent to DIDL DII or Digital Item Identifier, a unique external ID).</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attributeGroup ref="ORDERLABELS"/>
  <xsd:anyAttribute namespace="##other" processContents="lax"/>
</xsd:complexType>
Complex Type seqType
Namespace http://www.loc.gov/METS/v2
Annotations
 
seqType: Complex Type for Sequences 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.
Diagram
Used by
Model
Children area, par
Attributes
QName Type Use Annotation
ID xsd:ID optional 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
LABEL xsd:string optional 
LABEL (string/O): An attribute used, for example, to identify a <div> to an end user viewing the document. Thus a hierarchical arrangement of the <div> LABEL values could provide a table of contents to the digital content represented by a METS document and facilitate the users’ navigation of the digital object. Note that 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 . For further of the distinction between LABEL and ORDERLABEL see the description of the ORDERLABEL attribute.
ORDER xsd:integer optional 
ORDER (integer/O): A representation of the element's order among its siblings (e.g., its absolute, numeric sequence). For an example, and clarification of the distinction between ORDER and ORDERLABEL, see the description of the ORDERLABEL attribute.
ORDERLABEL xsd:string optional 
ORDERLABEL (string/O): A representation of the element's order among its siblings (e.g., “xii”), or of any non-integer native numbering system. It is presumed that this value will still be machine actionable (e.g., it would support ‘go to page ___’ function), and it should not be used as a replacement/substitute for the LABEL attribute. To understand 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”.
Wildcard: ANY attribute from ANY namespace OTHER than 'http://www.loc.gov/METS/v2'
Source
 
<xsd:complexType name="seqType">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">seqType: Complex Type for Sequences 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.</xsd:documentation>
  </xsd:annotation>
  <xsd:choice maxOccurs="unbounded">
    <xsd:element name="area" type="areaType" minOccurs="0"/>
    <xsd:element name="par" type="parType" minOccurs="0"/>
  </xsd:choice>
  <xsd:attribute name="ID" type="xsd:ID" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attributeGroup ref="ORDERLABELS"/>
  <xsd:anyAttribute namespace="##other" processContents="lax"/>
</xsd:complexType>
Attribute metsType / metsHdr / agent / @ID
Namespace No namespace
Annotations
 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute metsType / metsHdr / agent / @ROLE
Namespace No namespace
Annotations
 
ROLE (string/R): Specifies the function of the agent with respect to the METS document.
Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#agentrole
Type xsd:string
Properties
use required
Used by
Source
 
<xsd:attribute name="ROLE" use="required" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">ROLE (string/R): Specifies the function of the agent with respect to the METS document. Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#agentrole</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute metsType / metsHdr / agent / @TYPE
Namespace No namespace
Annotations
 
TYPE (string/O): is used to specify the type of AGENT.
Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#agenttype
Type xsd:string
Properties
use optional
Used by
Source
 
<xsd:attribute name="TYPE" use="optional" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">TYPE (string/O): is used to specify the type of AGENT. Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#agenttype</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute metsType / metsHdr / altRecordID / @ID
Namespace No namespace
Annotations
 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute metsType / metsHdr / altRecordID / @TYPE
Namespace No namespace
Annotations
 
TYPE (string/O): A description of the identifier type.
Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#altrecordidtype
Type xsd:string
Properties
use optional
Used by
Source
 
<xsd:attribute name="TYPE" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">TYPE (string/O): A description of the identifier type. Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#altrecordidtype</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute metsType / metsHdr / metsDocumentID / @ID
Namespace No namespace
Annotations
 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute metsType / metsHdr / metsDocumentID / @TYPE
Namespace No namespace
Annotations
 
TYPE (string/O): A description of the identifier type.

                        Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#metsdocumentidtype
Type xsd:string
Properties
use optional
Used by
Source
 
<xsd:attribute name="TYPE" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">TYPE (string/O): A description of the identifier type. Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#metsdocumentidtype</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute metsType / metsHdr / @ID
Namespace No namespace
Annotations
 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute metsType / metsHdr / @MDID
Namespace No namespace
Annotations
 
MDID (IDREFS/O): Contains the ID attribute values of the <md> elements within the <mdSec> of the METS document that contain metadata pertaining to the METS document itself.
Type xsd:IDREFS
Properties
use optional
Used by
Source
 
<xsd:attribute name="MDID" type="xsd:IDREFS" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">MDID (IDREFS/O): Contains the ID attribute values of the <md> elements within the <mdSec> of the METS document that contain metadata pertaining to the METS document itself.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute metsType / metsHdr / @CREATEDATE
Namespace No namespace
Annotations
 
CREATEDATE (dateTime/O): Records the date/time the METS document was created.
Type xsd:dateTime
Properties
use optional
Used by
Source
 
<xsd:attribute name="CREATEDATE" type="xsd:dateTime" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">CREATEDATE (dateTime/O): Records the date/time the METS document was created.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute metsType / metsHdr / @LASTMODDATE
Namespace No namespace
Annotations
 
LASTMODDATE (dateTime/O): Is used to indicate the date/time the METS document was last modified.
Type xsd:dateTime
Properties
use optional
Used by
Source
 
<xsd:attribute name="LASTMODDATE" type="xsd:dateTime" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">LASTMODDATE (dateTime/O): Is used to indicate the date/time the METS document was last modified.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute metsType / metsHdr / @RECORDSTATUS
Namespace No namespace
Annotations
 
RECORDSTATUS (string/O): Specifies the status of the METS document. It is used for internal processing purposes.
Type xsd:string
Properties
use optional
Used by
Source
 
<xsd:attribute name="RECORDSTATUS" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">RECORDSTATUS (string/O): Specifies the status of the METS document. It is used for internal processing purposes.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute mdType / mdRef / @ID
Namespace No namespace
Annotations
 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
Type xsd:ID
Properties
use optional
Used by
Element mdType/mdRef
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute LOCATION / @LOCREF
Namespace No namespace
Annotations
 
LOCREF (string/R): Specifies the location for resources. This may be a directly-resolvable URL (preferred for interoperability), or it may require the use of an external resolver or be system-specific. The LOCTYPE attribute identifies the type of location.
Type xsd:string
Properties
use required
Used by
Attribute Group LOCATION
Source
 
<xsd:attribute name="LOCREF" type="xsd:string" use="required">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">LOCREF (string/R): Specifies the location for resources. This may be a directly-resolvable URL (preferred for interoperability), or it may require the use of an external resolver or be system-specific. The LOCTYPE attribute identifies the type of location.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute LOCATION / @LOCTYPE
Namespace No namespace
Annotations
 
LOCTYPE (string/R): Specifies the locator type used in the LOCREF attribute.
Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#loctype-mptr-mdref-flocat
Type xsd:string
Properties
use required
Used by
Attribute Group LOCATION
Source
 
<xsd:attribute name="LOCTYPE" type="xsd:string" use="required">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">LOCTYPE (string/R): Specifies the locator type used in the LOCREF attribute. Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#loctype-mptr-mdref-flocat</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute METADATA / @MDTYPE
Namespace No namespace
Annotations
 
MDTYPE (string/R): Is used to indicate the type of the associated metadata.
Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#mdtype-mdref-mdwrap
Type xsd:string
Properties
use required
Used by
Attribute Group METADATA
Source
 
<xsd:attribute name="MDTYPE" use="required" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">MDTYPE (string/R): Is used to indicate the type of the associated metadata. Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#mdtype-mdref-mdwrap</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute METADATA / @MDTYPEVERSION
Namespace No namespace
Annotations
 
MDTYPEVERSION(string/O): Provides a means for recording the version of the type of metadata (as recorded in the MDTYPE attribute) that is being used.  This may represent the version of the underlying data dictionary or metadata model rather than a schema version.
Type xsd:string
Properties
use optional
Used by
Attribute Group METADATA
Source
 
<xsd:attribute name="MDTYPEVERSION" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">MDTYPEVERSION(string/O): Provides a means for recording the version of the type of metadata (as recorded in the MDTYPE attribute) that is being used. This may represent the version of the underlying data dictionary or metadata model rather than a schema version.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute FILECORE / @MIMETYPE
Namespace No namespace
Annotations
 
MIMETYPE (string/O): The IANA media type (formerly known as MIME type) for the associated file or wrapped content.

        Registered media/MIME types: https://www.iana.org/assignments/media-types/media-types.xhtml
Type xsd:string
Properties
use optional
Used by
Attribute Group FILECORE
Source
 
<xsd:attribute name="MIMETYPE" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">MIMETYPE (string/O): The IANA media type (formerly known as MIME type) for the associated file or wrapped content. Registered media/MIME types: https://www.iana.org/assignments/media-types/media-types.xhtml</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute FILECORE / @SIZE
Namespace No namespace
Annotations
 
SIZE (long/O): Specifies the size in bytes of the associated file or wrapped content.
Type xsd:long
Properties
use optional
Used by
Attribute Group FILECORE
Source
 
<xsd:attribute name="SIZE" type="xsd:long" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">SIZE (long/O): Specifies the size in bytes of the associated file or wrapped content.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute FILECORE / @CREATED
Namespace No namespace
Annotations
 
CREATED (dateTime/O): Specifies the date and time of creation for the associated file or wrapped content.
Type xsd:dateTime
Properties
use optional
Used by
Attribute Group FILECORE
Source
 
<xsd:attribute name="CREATED" type="xsd:dateTime" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">CREATED (dateTime/O): Specifies the date and time of creation for the associated file or wrapped content.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute FILECORE / @CHECKSUM
Namespace No namespace
Annotations
 
CHECKSUM (string/O): Provides a checksum value for the associated file or wrapped content.
Type xsd:string
Properties
use optional
Used by
Attribute Group FILECORE
Source
 
<xsd:attribute name="CHECKSUM" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">CHECKSUM (string/O): Provides a checksum value for the associated file or wrapped content.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute FILECORE / @CHECKSUMTYPE
Namespace No namespace
Annotations
 
CHECKSUMTYPE (enumerated string/O): Specifies the checksum algorithm used to produce the value contained in the CHECKSUM attribute.
Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#checksumtype-file-mdref-mdwrap
Type xsd:string
Properties
use optional
Used by
Attribute Group FILECORE
Source
 
<xsd:attribute name="CHECKSUMTYPE" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">CHECKSUMTYPE (enumerated string/O): Specifies the checksum algorithm used to produce the value contained in the CHECKSUM attribute. Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#checksumtype-file-mdref-mdwrap</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute mdType / mdRef / @LABEL
Namespace No namespace
Annotations
 
LABEL (string/O): Provides a label to display to the viewer of the METS document that identifies the associated metadata.
Type xsd:string
Properties
use optional
Used by
Element mdType/mdRef
Source
 
<xsd:attribute name="LABEL" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">LABEL (string/O): Provides a label to display to the viewer of the METS document that identifies the associated metadata.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute mdType / mdWrap / @ID
Namespace No namespace
Annotations
 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
Type xsd:ID
Properties
use optional
Used by
Element mdType/mdWrap
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute mdType / mdWrap / @LABEL
Namespace No namespace
Annotations
 
LABEL: an optional string attribute providing a label to display to the viewer of the METS document identifying the metadata.
Type xsd:string
Properties
use optional
Used by
Element mdType/mdWrap
Source
 
<xsd:attribute name="LABEL" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">LABEL: an optional string attribute providing a label to display to the viewer of the METS document identifying the metadata.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute mdType / @ID
Namespace No namespace
Annotations
 
ID (ID/R): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR. The ID attribute on the <md> element is required, and its value should be referenced from one or more MDID attributes that are associated with other elements in the METS document. The following elements support references to a <md> element via a MDID attribute: <file>, <fileGrp> <stream>, <div>, <metsHdr>, <md>.
Type xsd:ID
Properties
use required
Used by
Complex Type mdType
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="required">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">ID (ID/R): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR. The ID attribute on the <md> element is required, and its value should be referenced from one or more MDID attributes that are associated with other elements in the METS document. The following elements support references to a <md> element via a MDID attribute: <file>, <fileGrp> <stream>, <div>, <metsHdr>, <md>.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute mdType / @USE
Namespace No namespace
Annotations
 
USE: Specifies the purpose of metadata in this section.
Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#mduse-mdgrpuse
Type xsd:string
Properties
use optional
Used by
Complex Type mdType
Source
 
<xsd:attribute name="USE" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">USE: Specifies the purpose of metadata in this section. Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#mduse-mdgrpuse</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute mdType / @GROUPID
Namespace No namespace
Annotations
 
GROUPID (string/O): This identifier is used to indicate that different metadata sections may be considered as part of a group. Two metadata sections with the same GROUPID value are to be considered part of the same group. For example this facility might be used to group changed versions of the same metadata if previous versions are maintained in a file for tracking purposes.
Type xsd:string
Properties
use optional
Used by
Complex Type mdType
Source
 
<xsd:attribute name="GROUPID" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">GROUPID (string/O): This identifier is used to indicate that different metadata sections may be considered as part of a group. Two metadata sections with the same GROUPID value are to be considered part of the same group. For example this facility might be used to group changed versions of the same metadata if previous versions are maintained in a file for tracking purposes.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute mdType / @MDID
Namespace No namespace
Annotations
 
MDID (IDREFS/O): Contains the ID attribute values of the <md> elements within the <mdSec> of the METS document that contain metadata pertaining to the current <md> element. Typically used in this context to reference preservation metadata (use="DIGIPROV") which applies to the current metadata.
Type xsd:IDREFS
Properties
use optional
Used by
Complex Type mdType
Source
 
<xsd:attribute name="MDID" type="xsd:IDREFS" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">MDID (IDREFS/O): Contains the ID attribute values of the <md> elements within the <mdSec> of the METS document that contain metadata pertaining to the current <md> element. Typically used in this context to reference preservation metadata (use="DIGIPROV") which applies to the current metadata.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute mdType / @CREATED
Namespace No namespace
Annotations
 
CREATED (dateTime/O): Specifies the date and time of creation for the metadata.
Type xsd:dateTime
Properties
use optional
Used by
Complex Type mdType
Source
 
<xsd:attribute name="CREATED" type="xsd:dateTime" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">CREATED (dateTime/O): Specifies the date and time of creation for the metadata.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute mdType / @STATUS
Namespace No namespace
Annotations
 
STATUS (string/O): Indicates the status of this metadata
Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#status-md-mdgrp
Type xsd:string
Properties
use optional
Used by
Complex Type mdType
Source
 
<xsd:attribute name="STATUS" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">STATUS (string/O): Indicates the status of this metadata Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#status-md-mdgrp</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute mdSecType / mdGrp / @ID
Namespace No namespace
Annotations
 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
Type xsd:ID
Properties
use optional
Used by
Element mdSecType/mdGrp
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional">
  <xsd:annotation>
    <xsd:documentation>ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute mdSecType / mdGrp / @USE
Namespace No namespace
Annotations
 
USE (string/O): Specifies the purpose of the metadata contained in this group.

              Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#mduse-mdgrpuse
Type xsd:string
Properties
use optional
Used by
Element mdSecType/mdGrp
Source
 
<xsd:attribute name="USE" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">USE (string/O): Specifies the purpose of the metadata contained in this group. Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#mduse-mdgrpuse</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute mdSecType / mdGrp / @STATUS
Namespace No namespace
Annotations
 
STATUS (string/O): Indicates the status of this metadata
Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#status-md-mdgrp
Type xsd:string
Properties
use optional
Used by
Element mdSecType/mdGrp
Source
 
<xsd:attribute name="STATUS" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">STATUS (string/O): Indicates the status of this metadata Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#status-md-mdgrp</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute mdSecType / @ID
Namespace No namespace
Annotations
 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
Type xsd:ID
Properties
use optional
Used by
Complex Type mdSecType
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute fileType / FLocat / @ID
Namespace No namespace
Annotations
 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
Type xsd:ID
Properties
use optional
Used by
Element fileType/FLocat
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute fileType / FLocat / @USE
Namespace No namespace
Annotations
 
USE (string/O): A tagging attribute to indicate the intended use of the specific copy of the file  represented by the <FLocat> element. A USE attribute can be expressed at the<fileGrp> level, the <file> level, the <FLocat> level and/or the <FContent> level.  A USE attribute value at the <fileGrp> level should pertain to all of the files in the <fileGrp>.  A USE attribute at the <file> level should pertain to all copies of the file as represented by subsidiary <FLocat> and/or <FContent> elements.  A USE attribute at the <FLocat> or <FContent> level pertains to the particular copy of the file that is either referenced (<FLocat>) or wrapped (<FContent>).

              Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#flocatuse-fcontentuse
Type xsd:string
Properties
use optional
Used by
Element fileType/FLocat
Source
 
<xsd:attribute name="USE" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">USE (string/O): A tagging attribute to indicate the intended use of the specific copy of the file represented by the <FLocat> element. A USE attribute can be expressed at the<fileGrp> level, the <file> level, the <FLocat> level and/or the <FContent> level. A USE attribute value at the <fileGrp> level should pertain to all of the files in the <fileGrp>. A USE attribute at the <file> level should pertain to all copies of the file as represented by subsidiary <FLocat> and/or <FContent> elements. A USE attribute at the <FLocat> or <FContent> level pertains to the particular copy of the file that is either referenced (<FLocat>) or wrapped (<FContent>). Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#flocatuse-fcontentuse</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute fileType / FContent / @ID
Namespace No namespace
Annotations
 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute fileType / FContent / @USE
Namespace No namespace
Annotations
 
USE (string/O): A tagging attribute to indicate the intended use of the specific copy of the file represented by the <FContent> element. A USE attribute can be expressed at the<fileGrp> level, the <file> level, the <FLocat> level and/or the <FContent> level.  A USE attribute value at the <fileGrp> level should pertain to all of the files in the <fileGrp>.  A USE attribute at the <file> level should pertain to all copies of the file as represented by subsidiary <FLocat> and/or <FContent> elements.  A USE attribute at the <FLocat> or <FContent> level pertains to the particular copy of the file that is either referenced (<FLocat>) or wrapped (<FContent>).
 
             Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#flocatuse-fcontentuse
Type xsd:string
Properties
use optional
Used by
Source
 
<xsd:attribute name="USE" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">USE (string/O): A tagging attribute to indicate the intended use of the specific copy of the file represented by the <FContent> element. A USE attribute can be expressed at the<fileGrp> level, the <file> level, the <FLocat> level and/or the <FContent> level. A USE attribute value at the <fileGrp> level should pertain to all of the files in the <fileGrp>. A USE attribute at the <file> level should pertain to all copies of the file as represented by subsidiary <FLocat> and/or <FContent> elements. A USE attribute at the <FLocat> or <FContent> level pertains to the particular copy of the file that is either referenced (<FLocat>) or wrapped (<FContent>). Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#flocatuse-fcontentuse</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute fileType / stream / @ID
Namespace No namespace
Annotations
 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
Type xsd:ID
Properties
use optional
Used by
Element fileType/stream
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute fileType / stream / @streamType
Namespace No namespace
Annotations
 
streamType (string/O): The IANA MIME media type for the bytestream.
Type xsd:string
Properties
use optional
Used by
Element fileType/stream
Source
 
<xsd:attribute name="streamType" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">streamType (string/O): The IANA MIME media type for the bytestream.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute fileType / stream / @OWNERID
Namespace No namespace
Annotations
 
OWNERID (string/O): Used to provide a unique identifier (which could include a URI) assigned to the file. This identifier may differ from the URI used to retrieve the file.
Type xsd:string
Properties
use optional
Used by
Element fileType/stream
Source
 
<xsd:attribute name="OWNERID" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">OWNERID (string/O): Used to provide a unique identifier (which could include a URI) assigned to the file. This identifier may differ from the URI used to retrieve the file.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute fileType / stream / @MDID
Namespace No namespace
Annotations
 
MDID (IDREFS/O): Contains the ID attribute values of the <md> elements within the <mdSec> of the METS document that contain metadata pertaining to the bytestream.
Type xsd:IDREFS
Properties
use optional
Used by
Element fileType/stream
Source
 
<xsd:attribute name="MDID" type="xsd:IDREFS" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">MDID (IDREFS/O): Contains the ID attribute values of the <md> elements within the <mdSec> of the METS document that contain metadata pertaining to the bytestream.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute fileType / stream / @BEGIN
Namespace No namespace
Annotations
 
BEGIN (string/O): An attribute that specifies the point in the parent <file> where the current <stream> begins. It can be used in conjunction with the END attribute as a means of defining the location of the stream within its parent file. However, the BEGIN attribute can be used with or without a companion END attribute. When no END attribute is specified, the end of the parent file is assumed also to be the end point of the stream. The BEGIN and END attributes can only be interpreted meaningfully in conjunction with a BETYPE attribute, which specifies the kind of beginning/ending point values that are being used.
Type xsd:string
Properties
use optional
Used by
Element fileType/stream
Source
 
<xsd:attribute name="BEGIN" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">BEGIN (string/O): An attribute that specifies the point in the parent <file> where the current <stream> begins. It can be used in conjunction with the END attribute as a means of defining the location of the stream within its parent file. However, the BEGIN attribute can be used with or without a companion END attribute. When no END attribute is specified, the end of the parent file is assumed also to be the end point of the stream. The BEGIN and END attributes can only be interpreted meaningfully in conjunction with a BETYPE attribute, which specifies the kind of beginning/ending point values that are being used.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute fileType / stream / @END
Namespace No namespace
Annotations
 
END (string/O): An attribute that specifies the point in the parent <file> where the <stream> ends. It can only be interpreted meaningfully in conjunction with the BETYPE, which specifies the kind of ending point values being used. Typically the END attribute would only appear in conjunction with a BEGIN attribute.
Type xsd:string
Properties
use optional
Used by
Element fileType/stream
Source
 
<xsd:attribute name="END" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">END (string/O): An attribute that specifies the point in the parent <file> where the <stream> ends. It can only be interpreted meaningfully in conjunction with the BETYPE, which specifies the kind of ending point values being used. Typically the END attribute would only appear in conjunction with a BEGIN attribute.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute fileType / stream / @BETYPE
Namespace No namespace
Annotations
 
BETYPE: Begin/End Type.
                    BETYPE (string/O): An attribute that specifies the kind of BEGIN and/or END values that are being used.

                    Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#filebetype-streambetype
Type xsd:string
Properties
use optional
Used by
Element fileType/stream
Source
 
<xsd:attribute name="BETYPE" use="optional" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">BETYPE: Begin/End Type. BETYPE (string/O): An attribute that specifies the kind of BEGIN and/or END values that are being used. Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#filebetype-streambetype</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute fileType / transformFile / @ID
Namespace No namespace
Annotations
 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute fileType / transformFile / @TRANSFORMTYPE
Namespace No namespace
Annotations
 
TRANSFORMTYPE (string/R): Is used to indicate the type of transformation needed to render content of a file accessible. This may include unpacking a file into subsidiary files/streams.

                  Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#transformfiletransformtype
Type xsd:string
Properties
use required
Used by
Source
 
<xsd:attribute name="TRANSFORMTYPE" use="required" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">TRANSFORMTYPE (string/R): Is used to indicate the type of transformation needed to render content of a file accessible. This may include unpacking a file into subsidiary files/streams. Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#transformfiletransformtype</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute fileType / transformFile / @TRANSFORMALGORITHM
Namespace No namespace
Annotations
 
TRANSFORMALGORITHM (string/R): Specifies the decompression or decryption routine used to access the contents of the file. Algorithms for compression can be either loss-less or lossy.
Type xsd:string
Properties
use required
Used by
Source
 
<xsd:attribute name="TRANSFORMALGORITHM" type="xsd:string" use="required">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">TRANSFORMALGORITHM (string/R): Specifies the decompression or decryption routine used to access the contents of the file. Algorithms for compression can be either loss-less or lossy.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute fileType / transformFile / @TRANSFORMKEY
Namespace No namespace
Annotations
 
TRANSFORMKEY (string/O): A key to be used with the transform algorithm for accessing the file’s contents.
Type xsd:string
Properties
use optional
Used by
Source
 
<xsd:attribute name="TRANSFORMKEY" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">TRANSFORMKEY (string/O): A key to be used with the transform algorithm for accessing the file’s contents.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute fileType / transformFile / @TRANSFORMORDER
Namespace No namespace
Annotations
 
TRANSFORMORDER (postive-integer/R): The order in which the instructions must be followed in order to unpack or transform the container file.
Type xsd:positiveInteger
Properties
use required
Used by
Source
 
<xsd:attribute name="TRANSFORMORDER" type="xsd:positiveInteger" use="required">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">TRANSFORMORDER (postive-integer/R): The order in which the instructions must be followed in order to unpack or transform the container file.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute fileType / @ID
Namespace No namespace
Annotations
 
ID (ID/R): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR. Typically, the ID attribute value on a <file> element would be referenced from one or more FILEID attributes (which are of type IDREF) on <fptr>and/or <area> elements within the <structMap>.  Such references establish links between  structural divisions (<div> elements) and the specific content files or parts of content files that manifest them.
Type xsd:ID
Properties
use required
Used by
Complex Type fileType
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="required">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">ID (ID/R): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR. Typically, the ID attribute value on a <file> element would be referenced from one or more FILEID attributes (which are of type IDREF) on <fptr>and/or <area> elements within the <structMap>. Such references establish links between structural divisions (<div> elements) and the specific content files or parts of content files that manifest them.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute fileType / @SEQ
Namespace No namespace
Annotations
 
SEQ (integer/O): Indicates the sequence of this <file> relative to the others in its <fileGrp>.
Type xsd:int
Properties
use optional
Used by
Complex Type fileType
Source
 
<xsd:attribute name="SEQ" type="xsd:int" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">SEQ (integer/O): Indicates the sequence of this <file> relative to the others in its <fileGrp>.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute fileType / @OWNERID
Namespace No namespace
Annotations
 
OWNERID (string/O): A unique identifier assigned to the file by its owner.  This may be a URI which differs from the URI used to retrieve the file.
Type xsd:string
Properties
use optional
Used by
Complex Type fileType
Source
 
<xsd:attribute name="OWNERID" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">OWNERID (string/O): A unique identifier assigned to the file by its owner. This may be a URI which differs from the URI used to retrieve the file.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute fileType / @MDID
Namespace No namespace
Annotations
 
MDID (IDREFS/O): Contains the ID attribute values of the <md> elements within the <mdSec> of the METS document that contain metadata pertaining to the file.
Type xsd:IDREFS
Properties
use optional
Used by
Complex Type fileType
Source
 
<xsd:attribute name="MDID" type="xsd:IDREFS" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">MDID (IDREFS/O): Contains the ID attribute values of the <md> elements within the <mdSec> of the METS document that contain metadata pertaining to the file.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute fileType / @GROUPID
Namespace No namespace
Annotations
 
GROUPID (string/O): 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 the derivative files made from it in other file groups.
Type xsd:string
Properties
use optional
Used by
Complex Type fileType
Source
 
<xsd:attribute name="GROUPID" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">GROUPID (string/O): 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 the derivative files made from it in other file groups.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute fileType / @USE
Namespace No namespace
Annotations
 
USE (string/O): A tagging attribute to indicate the intended use of all copies of the file aggregated by the <file> element. A USE attribute can be expressed at the<fileGrp> level, the <file> level, the <FLocat> level and/or the <FContent> level.  A USE attribute value at the <fileGrp> level should pertain to all of the files in the <fileGrp>.  A USE attribute at the <file> level should pertain to all copies of the file as represented by subsidiary <FLocat> and/or <FContent> elements.  A USE attribute at the <FLocat> or <FContent> level pertains to the particular copy of the file that is either referenced (<FLocat>) or wrapped (<FContent>).

              Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#filegrpuse-fileuse
Type xsd:string
Properties
use optional
Used by
Complex Type fileType
Source
 
<xsd:attribute name="USE" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">USE (string/O): A tagging attribute to indicate the intended use of all copies of the file aggregated by the <file> element. A USE attribute can be expressed at the<fileGrp> level, the <file> level, the <FLocat> level and/or the <FContent> level. A USE attribute value at the <fileGrp> level should pertain to all of the files in the <fileGrp>. A USE attribute at the <file> level should pertain to all copies of the file as represented by subsidiary <FLocat> and/or <FContent> elements. A USE attribute at the <FLocat> or <FContent> level pertains to the particular copy of the file that is either referenced (<FLocat>) or wrapped (<FContent>). Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#filegrpuse-fileuse</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute fileType / @BEGIN
Namespace No namespace
Annotations
 
BEGIN (string/O): An attribute that specifies the point in the parent <file> where the current <file> begins.  When used in conjunction with a <file> element, this attribute is only meaningful when this element is nested, and its parent <file> element represents a container file. It can be used in conjunction with the END attribute as a means of defining the location of the current file within its parent file. However, the BEGIN attribute can be used with or without a companion END attribute. When no END attribute is specified, the end of the parent file is assumed also to be the end point of the current file. The BEGIN and END attributes can only be interpreted meaningfully in conjunction with a BETYPE attribute, which specifies the kind of beginning/ending point values that are being used.
Type xsd:string
Properties
use optional
Used by
Complex Type fileType
Source
 
<xsd:attribute name="BEGIN" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">BEGIN (string/O): An attribute that specifies the point in the parent <file> where the current <file> begins. When used in conjunction with a <file> element, this attribute is only meaningful when this element is nested, and its parent <file> element represents a container file. It can be used in conjunction with the END attribute as a means of defining the location of the current file within its parent file. However, the BEGIN attribute can be used with or without a companion END attribute. When no END attribute is specified, the end of the parent file is assumed also to be the end point of the current file. The BEGIN and END attributes can only be interpreted meaningfully in conjunction with a BETYPE attribute, which specifies the kind of beginning/ending point values that are being used.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute fileType / @END
Namespace No namespace
Annotations
 
END (string/O): An attribute that specifies the point in the parent <file> where the current, nested <file> ends. It can only be interpreted meaningfully in conjunction with the BETYPE, which specifies the kind of ending point values being used. Typically the END attribute would only appear in conjunction with a BEGIN attribute.
Type xsd:string
Properties
use optional
Used by
Complex Type fileType
Source
 
<xsd:attribute name="END" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">END (string/O): An attribute that specifies the point in the parent <file> where the current, nested <file> ends. It can only be interpreted meaningfully in conjunction with the BETYPE, which specifies the kind of ending point values being used. Typically the END attribute would only appear in conjunction with a BEGIN attribute.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute fileType / @BETYPE
Namespace No namespace
Annotations
 
BETYPE: Begin/End Type.
BETYPE (string/O): An attribute that specifies the kind of BEGIN and/or END values that are being used.
     Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#filebetype-streambetype
Type xsd:string
Properties
use optional
Used by
Complex Type fileType
Source
 
<xsd:attribute name="BETYPE" use="optional" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">BETYPE: Begin/End Type. BETYPE (string/O): An attribute that specifies the kind of BEGIN and/or END values that are being used. Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#filebetype-streambetype</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute fileGrpType / @ID
Namespace No namespace
Annotations
 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
Type xsd:ID
Properties
use optional
Used by
Complex Type fileGrpType
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute fileGrpType / @VERSDATE
Namespace No namespace
Annotations
 
VERSDATE (dateTime/O): An optional dateTime attribute specifying the date this version/fileGrp of the digital object was created.
Type xsd:dateTime
Properties
use optional
Used by
Complex Type fileGrpType
Source
 
<xsd:attribute name="VERSDATE" type="xsd:dateTime" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">VERSDATE (dateTime/O): An optional dateTime attribute specifying the date this version/fileGrp of the digital object was created.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute fileGrpType / @MDID
Namespace No namespace
Annotations
 
MDID (IDREF/O): Contains the ID attribute values of the <md> elements within the <mdSec> of the METS document applicable to all of the files in a particular file group.
Type xsd:IDREFS
Properties
use optional
Used by
Complex Type fileGrpType
Source
 
<xsd:attribute name="MDID" type="xsd:IDREFS" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">MDID (IDREF/O): Contains the ID attribute values of the <md> elements within the <mdSec> of the METS document applicable to all of the files in a particular file group.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute fileGrpType / @USE
Namespace No namespace
Annotations
 
USE (string/O): A tagging attribute to indicate the intended use of files within this file group. A USE attribute can be expressed at the<fileGrp> level, the <file> level, the <FLocat> level and/or the <FContent> level.  A USE attribute value at the <fileGrp> level should pertain to all of the files in the <fileGrp>.  A USE attribute at the <file> level should pertain to all copies of the file as represented by subsidiary <FLocat> and/or <FContent> elements.  A USE attribute at the <FLocat> or <FContent> level pertains to the particular copy of the file that is either referenced (<FLocat>) or wrapped (<FContent>).

              Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#filegrpuse-fileuse
Type xsd:string
Properties
use optional
Used by
Complex Type fileGrpType
Source
 
<xsd:attribute name="USE" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">USE (string/O): A tagging attribute to indicate the intended use of files within this file group. A USE attribute can be expressed at the<fileGrp> level, the <file> level, the <FLocat> level and/or the <FContent> level. A USE attribute value at the <fileGrp> level should pertain to all of the files in the <fileGrp>. A USE attribute at the <file> level should pertain to all copies of the file as represented by subsidiary <FLocat> and/or <FContent> elements. A USE attribute at the <FLocat> or <FContent> level pertains to the particular copy of the file that is either referenced (<FLocat>) or wrapped (<FContent>). Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#filegrpuse-fileuse</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute metsType / fileSec / @ID
Namespace No namespace
Annotations
 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute divType / mptr / @ID
Namespace No namespace
Annotations
 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
Type xsd:ID
Properties
use optional
Used by
Element divType/mptr
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute divType / mptr / @CONTENTIDS
Namespace No namespace
Annotations
 
CONTENTIDS (URI/O): Content IDs for the content represented by the <mptr> (equivalent to DIDL DII or Digital Item Identifier, a unique external ID).
Type URIs
Properties
use optional
Used by
Element divType/mptr
Source
 
<xsd:attribute name="CONTENTIDS" type="URIs" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">CONTENTIDS (URI/O): Content IDs for the content represented by the <mptr> (equivalent to DIDL DII or Digital Item Identifier, a unique external ID).</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute areaType / @ID
Namespace No namespace
Annotations
 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
Type xsd:ID
Properties
use optional
Used by
Complex Type areaType
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute areaType / @FILEID
Namespace No namespace
Annotations
 
FILEID (IDREF/R): An attribute which provides the XML ID value that identifies the <file> element in the <fileSec> that then points to and/or contains the digital content represented by the <area> element. It must contain an ID value represented in an ID attribute associated with a <file> element in the <fileSec> element in the same METS document.
Type xsd:IDREF
Properties
use required
Used by
Complex Type areaType
Source
 
<xsd:attribute name="FILEID" type="xsd:IDREF" use="required">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">FILEID (IDREF/R): An attribute which provides the XML ID value that identifies the <file> element in the <fileSec> that then points to and/or contains the digital content represented by the <area> element. It must contain an ID value represented in an ID attribute associated with a <file> element in the <fileSec> element in the same METS document.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute areaType / @SHAPE
Namespace No namespace
Annotations
 
SHAPE (string/O): An attribute that can be used as in HTML to define the shape of the relevant area within the content file pointed to by the <area> element. Typically this would be used with image content (still image or video frame) when only a portion of an image pertains. If SHAPE is specified then COORDS must also be present. SHAPE should be used in conjunction with COORDS in the manner defined for the shape and coords attributes on an HTML5 <area> element. Recommended attribute values are those allowed by HTML5; see also https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#areashape
Type xsd:string
Properties
use optional
Used by
Complex Type areaType
Source
 
<xsd:attribute name="SHAPE" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">SHAPE (string/O): An attribute that can be used as in HTML to define the shape of the relevant area within the content file pointed to by the <area> element. Typically this would be used with image content (still image or video frame) when only a portion of an image pertains. If SHAPE is specified then COORDS must also be present. SHAPE should be used in conjunction with COORDS in the manner defined for the shape and coords attributes on an HTML5 <area> element. Recommended attribute values are those allowed by HTML5; see also https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#areashape</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute areaType / @COORDS
Namespace No namespace
Annotations
 
COORDS (string/O): Specifies the coordinates in an image map for the shape of the pertinent area as specified in the SHAPE attribute. While technically optional, SHAPE and COORDS must both appear together to define the relevant area of image content. COORDS should be used in conjunction with SHAPE in the manner defined for the COORDs and SHAPE attributes on an HTML5 <area> element. COORDS must be a comma delimited string of integer value pairs representing coordinates (plus radius in the case of CIRCLE) within an image. Number of coordinates pairs depends on shape: RECT: x1, y1, x2, y2; CIRC: x1, y1; POLY: x1, y1, x2, y2, x3, y3 . . .
Type xsd:string
Properties
use optional
Used by
Complex Type areaType
Source
 
<xsd:attribute name="COORDS" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">COORDS (string/O): Specifies the coordinates in an image map for the shape of the pertinent area as specified in the SHAPE attribute. While technically optional, SHAPE and COORDS must both appear together to define the relevant area of image content. COORDS should be used in conjunction with SHAPE in the manner defined for the COORDs and SHAPE attributes on an HTML5 <area> element. COORDS must be a comma delimited string of integer value pairs representing coordinates (plus radius in the case of CIRCLE) within an image. Number of coordinates pairs depends on shape: RECT: x1, y1, x2, y2; CIRC: x1, y1; POLY: x1, y1, x2, y2, x3, y3 . . .</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute areaType / @BEGIN
Namespace No namespace
Annotations
 
BEGIN (string/O): An attribute that specifies the point in the content file where the relevant section of content begins. It can be used in conjunction with either the END attribute or the EXTENT attribute as a means of defining the relevant portion of the referenced file precisely. It can only be interpreted meaningfully in conjunction with the BETYPE or EXTTYPE, which specify the kind of beginning/ending point values or beginning/extent values that are being used. The BEGIN attribute can be used with or without a companion END or EXTENT element. In this case, the end of the content file is assumed to be the end point.
Type xsd:string
Properties
use optional
Used by
Complex Type areaType
Source
 
<xsd:attribute name="BEGIN" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">BEGIN (string/O): An attribute that specifies the point in the content file where the relevant section of content begins. It can be used in conjunction with either the END attribute or the EXTENT attribute as a means of defining the relevant portion of the referenced file precisely. It can only be interpreted meaningfully in conjunction with the BETYPE or EXTTYPE, which specify the kind of beginning/ending point values or beginning/extent values that are being used. The BEGIN attribute can be used with or without a companion END or EXTENT element. In this case, the end of the content file is assumed to be the end point.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute areaType / @END
Namespace No namespace
Annotations
 
END (string/O): An attribute that specifies the point in the content file where the relevant section of content ends. It can only be interpreted meaningfully in conjunction with the BETYPE, which specifies the kind of ending point values being used. Typically the END attribute would only appear in conjunction with a BEGIN element.
Type xsd:string
Properties
use optional
Used by
Complex Type areaType
Source
 
<xsd:attribute name="END" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">END (string/O): An attribute that specifies the point in the content file where the relevant section of content ends. It can only be interpreted meaningfully in conjunction with the BETYPE, which specifies the kind of ending point values being used. Typically the END attribute would only appear in conjunction with a BEGIN element.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute areaType / @BETYPE
Namespace No namespace
Annotations
 
BETYPE: Begin/End Type.
					BETYPE (string/O): An attribute that specifies the kind of BEGIN and/or END values that are being used. For example, if BYTE is specified, then the BEGIN and END point values represent the byte offsets into a file. If IDREF is specified, then the BEGIN element specifies the ID value that identifies the element in a structured text file where the relevant section of the file begins; and the END value (if present) would specify the ID value that identifies the element with which the relevant section of the file ends.

        Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#areabetype
Type xsd:string
Properties
use optional
Used by
Complex Type areaType
Source
 
<xsd:attribute name="BETYPE" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">BETYPE: Begin/End Type. BETYPE (string/O): An attribute that specifies the kind of BEGIN and/or END values that are being used. For example, if BYTE is specified, then the BEGIN and END point values represent the byte offsets into a file. If IDREF is specified, then the BEGIN element specifies the ID value that identifies the element in a structured text file where the relevant section of the file begins; and the END value (if present) would specify the ID value that identifies the element with which the relevant section of the file ends. Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#areabetype</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute areaType / @EXTENT
Namespace No namespace
Annotations
 
EXTENT (string/O): An attribute that specifies the extent of the relevant section of the content file. Can only be interpreted meaningfully in conjunction with the EXTTYPE which specifies the kind of value that is being used. Typically the EXTENT attribute would only appear in conjunction with a BEGIN element and would not be used if the BEGIN point represents an IDREF.
Type xsd:string
Properties
use optional
Used by
Complex Type areaType
Source
 
<xsd:attribute name="EXTENT" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">EXTENT (string/O): An attribute that specifies the extent of the relevant section of the content file. Can only be interpreted meaningfully in conjunction with the EXTTYPE which specifies the kind of value that is being used. Typically the EXTENT attribute would only appear in conjunction with a BEGIN element and would not be used if the BEGIN point represents an IDREF.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute areaType / @EXTTYPE
Namespace No namespace
Annotations
 
EXTTYPE (string/O): An attribute that specifies the kind of EXTENT values that are being used. For example if BYTE is specified then EXTENT would represent a byte count. If TIME is specified the EXTENT would represent a duration of time.

        Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#areaexttype.
Type xsd:string
Properties
use optional
Used by
Complex Type areaType
Source
 
<xsd:attribute name="EXTTYPE" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">EXTTYPE (string/O): An attribute that specifies the kind of EXTENT values that are being used. For example if BYTE is specified then EXTENT would represent a byte count. If TIME is specified the EXTENT would represent a duration of time. Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#areaexttype.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute areaType / @MDID
Namespace No namespace
Annotations
 
MDID (IDREFS/O): Contains the ID attribute values identifying the <md> elements within the <mdSec> of the METS document that contain or link to metadata pertaining to the content represented by the <area> element.
Type xsd:IDREFS
Properties
use optional
Used by
Complex Type areaType
Source
 
<xsd:attribute name="MDID" type="xsd:IDREFS" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">MDID (IDREFS/O): Contains the ID attribute values identifying the <md> elements within the <mdSec> of the METS document that contain or link to metadata pertaining to the content represented by the <area> element.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute areaType / @CONTENTIDS
Namespace No namespace
Annotations
 
CONTENTIDS (URI/O): Content IDs for the content represented by the <area> (equivalent to DIDL DII or Digital Item Identifier, a unique external ID).
Type URIs
Properties
use optional
Used by
Complex Type areaType
Source
 
<xsd:attribute name="CONTENTIDS" type="URIs" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">CONTENTIDS (URI/O): Content IDs for the content represented by the <area> (equivalent to DIDL DII or Digital Item Identifier, a unique external ID).</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute ORDERLABELS / @ORDER
Namespace No namespace
Annotations
 
ORDER (integer/O): A representation of the element's order among its siblings (e.g., its absolute, numeric sequence). For an example, and clarification of the distinction between ORDER and ORDERLABEL, see the description of the ORDERLABEL attribute.
Type xsd:integer
Properties
use optional
Used by
Attribute Group ORDERLABELS
Source
 
<xsd:attribute name="ORDER" type="xsd:integer" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">ORDER (integer/O): A representation of the element's order among its siblings (e.g., its absolute, numeric sequence). For an example, and clarification of the distinction between ORDER and ORDERLABEL, see the description of the ORDERLABEL attribute.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute ORDERLABELS / @ORDERLABEL
Namespace No namespace
Annotations
 
ORDERLABEL (string/O): A representation of the element's order among its siblings (e.g., “xii”), or of any non-integer native numbering system. It is presumed that this value will still be machine actionable (e.g., it would support ‘go to page ___’ function), and it should not be used as a replacement/substitute for the LABEL attribute. To understand 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”.
Type xsd:string
Properties
use optional
Used by
Attribute Group ORDERLABELS
Source
 
<xsd:attribute name="ORDERLABEL" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">ORDERLABEL (string/O): A representation of the element's order among its siblings (e.g., “xii”), or of any non-integer native numbering system. It is presumed that this value will still be machine actionable (e.g., it would support ‘go to page ___’ function), and it should not be used as a replacement/substitute for the LABEL attribute. To understand 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”.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute ORDERLABELS / @LABEL
Namespace No namespace
Annotations
 
LABEL (string/O): An attribute used, for example, to identify a <div> to an end user viewing the document. Thus a hierarchical arrangement of the <div> LABEL values could provide a table of contents to the digital content represented by a METS document and facilitate the users’ navigation of the digital object. Note that 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 . For further of the distinction between LABEL and ORDERLABEL see the description of the ORDERLABEL attribute.
Type xsd:string
Properties
use optional
Used by
Attribute Group ORDERLABELS
Source
 
<xsd:attribute name="LABEL" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">LABEL (string/O): An attribute used, for example, to identify a <div> to an end user viewing the document. Thus a hierarchical arrangement of the <div> LABEL values could provide a table of contents to the digital content represented by a METS document and facilitate the users’ navigation of the digital object. Note that 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 . For further of the distinction between LABEL and ORDERLABEL see the description of the ORDERLABEL attribute.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute parType / @ID
Namespace No namespace
Annotations
 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
Type xsd:ID
Properties
use optional
Used by
Complex Type parType
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute seqType / @ID
Namespace No namespace
Annotations
 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
Type xsd:ID
Properties
use optional
Used by
Complex Type seqType
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute divType / fptr / @ID
Namespace No namespace
Annotations
 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
Type xsd:ID
Properties
use optional
Used by
Element divType/fptr
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute divType / fptr / @FILEID
Namespace No namespace
Annotations
 
FILEID (IDREF/O): An optional attribute that provides the XML ID identifying the <file> element that links to and/or contains the digital content represented by the <fptr>. A <fptr> element should only have a FILEID attribute value if it does not have a child <area>, <par> or <seq> element. If it has a child element, then the responsibility for pointing to the relevant content falls to this child element or its descendants.
Type xsd:IDREF
Properties
use optional
Used by
Element divType/fptr
Source
 
<xsd:attribute name="FILEID" type="xsd:IDREF" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">FILEID (IDREF/O): An optional attribute that provides the XML ID identifying the <file> element that links to and/or contains the digital content represented by the <fptr>. A <fptr> element should only have a FILEID attribute value if it does not have a child <area>, <par> or <seq> element. If it has a child element, then the responsibility for pointing to the relevant content falls to this child element or its descendants.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute divType / fptr / @CONTENTIDS
Namespace No namespace
Annotations
 
CONTENTIDS (URI/O): Content IDs for the content represented by the <fptr> (equivalent to DIDL DII or Digital Item Identifier, a unique external ID).
Type URIs
Properties
use optional
Used by
Element divType/fptr
Source
 
<xsd:attribute name="CONTENTIDS" type="URIs" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">CONTENTIDS (URI/O): Content IDs for the content represented by the <fptr> (equivalent to DIDL DII or Digital Item Identifier, a unique external ID).</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute divType / @ID
Namespace No namespace
Annotations
 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
Type xsd:ID
Properties
use optional
Used by
Complex Type divType
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute divType / @MDID
Namespace No namespace
Annotations
 
MDID (IDREFS/O): Contains the ID attribute values identifying the <md> elements within the <mdSec> of the METS document that contain or link to metadata pertaining to the structural division represented by the <div> element.
Type xsd:IDREFS
Properties
use optional
Used by
Complex Type divType
Source
 
<xsd:attribute name="MDID" type="xsd:IDREFS" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">MDID (IDREFS/O): Contains the ID attribute values identifying the <md> elements within the <mdSec> of the METS document that contain or link to metadata pertaining to the structural division represented by the <div> element.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute divType / @TYPE
Namespace No namespace
Annotations
 
TYPE (string/O): An attribute that specifies the type of structural division that the <div> element represents.

          Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#divtype
Type xsd:string
Properties
use optional
Used by
Complex Type divType
Source
 
<xsd:attribute name="TYPE" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">TYPE (string/O): An attribute that specifies the type of structural division that the <div> element represents. Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#divtype</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute divType / @CONTENTIDS
Namespace No namespace
Annotations
 
CONTENTIDS (URI/O): Content IDs for the content represented by the <div> (equivalent to DIDL DII or Digital Item Identifier, a unique external ID).
Type URIs
Properties
use optional
Used by
Complex Type divType
Source
 
<xsd:attribute name="CONTENTIDS" type="URIs" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">CONTENTIDS (URI/O): Content IDs for the content represented by the <div> (equivalent to DIDL DII or Digital Item Identifier, a unique external ID).</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute structMapType / @ID
Namespace No namespace
Annotations
 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
Type xsd:ID
Properties
use optional
Used by
Complex Type structMapType
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute structMapType / @TYPE
Namespace No namespace
Annotations
 
TYPE (string/O): Identifies the type of structure represented by the <structMap>. For example, a <structMap> that represented a purely logical or intellectual structure could be assigned a TYPE value of “logical” whereas a <structMap> that represented a purely physical structure could be assigned a TYPE value of “physical”. However, the METS schema neither defines nor requires a common vocabulary for this attribute. A METS profile, however, may well constrain the values for the <structMap> TYPE.

        Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#structmaptype
Type xsd:string
Properties
use optional
Used by
Complex Type structMapType
Source
 
<xsd:attribute name="TYPE" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">TYPE (string/O): Identifies the type of structure represented by the <structMap>. For example, a <structMap> that represented a purely logical or intellectual structure could be assigned a TYPE value of “logical” whereas a <structMap> that represented a purely physical structure could be assigned a TYPE value of “physical”. However, the METS schema neither defines nor requires a common vocabulary for this attribute. A METS profile, however, may well constrain the values for the <structMap> TYPE. Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#structmaptype</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute structMapType / @LABEL
Namespace No namespace
Annotations
 
LABEL (string/O): Describes the <structMap> to viewers of the METS document. This would be useful primarily where more than one <structMap> is provided for a single object. A descriptive LABEL value, in that case, could clarify to users the purpose of each of the available structMaps.
Type xsd:string
Properties
use optional
Used by
Complex Type structMapType
Source
 
<xsd:attribute name="LABEL" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">LABEL (string/O): Describes the <structMap> to viewers of the METS document. This would be useful primarily where more than one <structMap> is provided for a single object. A descriptive LABEL value, in that case, could clarify to users the purpose of each of the available structMaps.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute metsType / structSec / @ID
Namespace No namespace
Annotations
 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute metsType / @ID
Namespace No namespace
Annotations
 
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.
Type xsd:ID
Properties
use optional
Used by
Complex Type metsType
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute metsType / @OBJID
Namespace No namespace
Annotations
 
OBJID (string/O): Is the primary identifier assigned to the METS object as a whole. Although this attribute is not required, it is strongly recommended. This identifier is used to tag the entire METS object to external systems, in contrast with the ID identifier.
Type xsd:string
Properties
use optional
Used by
Complex Type metsType
Source
 
<xsd:attribute name="OBJID" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">OBJID (string/O): Is the primary identifier assigned to the METS object as a whole. Although this attribute is not required, it is strongly recommended. This identifier is used to tag the entire METS object to external systems, in contrast with the ID identifier.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute metsType / @LABEL
Namespace No namespace
Annotations
 
LABEL (string/O): Is a simple title string used to identify the object/entity being described in the METS document for the user.
Type xsd:string
Properties
use optional
Used by
Complex Type metsType
Source
 
<xsd:attribute name="LABEL" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">LABEL (string/O): Is a simple title string used to identify the object/entity being described in the METS document for the user.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute metsType / @TYPE
Namespace No namespace
Annotations
 
TYPE (string/O): Specifies the class or type of the object.

          Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#metstype
Type xsd:string
Properties
use optional
Used by
Complex Type metsType
Source
 
<xsd:attribute name="TYPE" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">TYPE (string/O): Specifies the class or type of the object. Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#metstype</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute metsType / @PROFILE
Namespace No namespace
Annotations
 
PROFILE (string/O): Indicates the URI of the METS Profile this METS document conforms to.
Type xsd:string
Properties
use optional
Used by
Complex Type metsType
Source
 
<xsd:attribute name="PROFILE" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">PROFILE (string/O): Indicates the URI of the METS Profile this METS document conforms to.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Attribute Group LOCATION
Namespace http://www.loc.gov/METS/v2
Diagram
Used by
Attributes
QName Type Use Annotation
LOCREF xsd:string required 
LOCREF (string/R): Specifies the location for resources. This may be a directly-resolvable URL (preferred for interoperability), or it may require the use of an external resolver or be system-specific. The LOCTYPE attribute identifies the type of location.
LOCTYPE xsd:string required 
LOCTYPE (string/R): Specifies the locator type used in the LOCREF attribute.
Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#loctype-mptr-mdref-flocat
Source
 
<xsd:attributeGroup name="LOCATION">
  <xsd:attribute name="LOCREF" type="xsd:string" use="required">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">LOCREF (string/R): Specifies the location for resources. This may be a directly-resolvable URL (preferred for interoperability), or it may require the use of an external resolver or be system-specific. The LOCTYPE attribute identifies the type of location.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="LOCTYPE" type="xsd:string" use="required">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">LOCTYPE (string/R): Specifies the locator type used in the LOCREF attribute. Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#loctype-mptr-mdref-flocat</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
</xsd:attributeGroup>
Attribute Group METADATA
Namespace http://www.loc.gov/METS/v2
Diagram
Used by
Attributes
QName Type Use Annotation
MDTYPE xsd:string required 
MDTYPE (string/R): Is used to indicate the type of the associated metadata.
Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#mdtype-mdref-mdwrap
MDTYPEVERSION xsd:string optional 
MDTYPEVERSION(string/O): Provides a means for recording the version of the type of metadata (as recorded in the MDTYPE attribute) that is being used.  This may represent the version of the underlying data dictionary or metadata model rather than a schema version.
Source
 
<xsd:attributeGroup name="METADATA">
  <xsd:attribute name="MDTYPE" use="required" type="xsd:string">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">MDTYPE (string/R): Is used to indicate the type of the associated metadata. Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#mdtype-mdref-mdwrap</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="MDTYPEVERSION" type="xsd:string" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">MDTYPEVERSION(string/O): Provides a means for recording the version of the type of metadata (as recorded in the MDTYPE attribute) that is being used. This may represent the version of the underlying data dictionary or metadata model rather than a schema version.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
</xsd:attributeGroup>
Attribute Group FILECORE
Namespace http://www.loc.gov/METS/v2
Diagram
Used by
Elements mdType/mdRef, mdType/mdWrap
Complex Type fileType
Attributes
QName Type Use Annotation
CHECKSUM xsd:string optional 
CHECKSUM (string/O): Provides a checksum value for the associated file or wrapped content.
CHECKSUMTYPE xsd:string optional 
CHECKSUMTYPE (enumerated string/O): Specifies the checksum algorithm used to produce the value contained in the CHECKSUM attribute.
Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#checksumtype-file-mdref-mdwrap
CREATED xsd:dateTime optional 
CREATED (dateTime/O): Specifies the date and time of creation for the associated file or wrapped content.
MIMETYPE xsd:string optional 
MIMETYPE (string/O): The IANA media type (formerly known as MIME type) for the associated file or wrapped content.

        Registered media/MIME types: https://www.iana.org/assignments/media-types/media-types.xhtml
SIZE xsd:long optional 
SIZE (long/O): Specifies the size in bytes of the associated file or wrapped content.
Source
 
<xsd:attributeGroup name="FILECORE">
  <xsd:attribute name="MIMETYPE" type="xsd:string" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">MIMETYPE (string/O): The IANA media type (formerly known as MIME type) for the associated file or wrapped content. Registered media/MIME types: https://www.iana.org/assignments/media-types/media-types.xhtml</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="SIZE" type="xsd:long" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">SIZE (long/O): Specifies the size in bytes of the associated file or wrapped content.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="CREATED" type="xsd:dateTime" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">CREATED (dateTime/O): Specifies the date and time of creation for the associated file or wrapped content.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="CHECKSUM" type="xsd:string" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">CHECKSUM (string/O): Provides a checksum value for the associated file or wrapped content.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="CHECKSUMTYPE" type="xsd:string" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">CHECKSUMTYPE (enumerated string/O): Specifies the checksum algorithm used to produce the value contained in the CHECKSUM attribute. Suggested attribute values: https://github.com/mets/METS-schema/wiki/METS2-Suggested-Attribute-Values#checksumtype-file-mdref-mdwrap</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
</xsd:attributeGroup>
Attribute Group ORDERLABELS
Namespace http://www.loc.gov/METS/v2
Diagram
Used by
Complex Types areaType, divType, parType, seqType
Attributes
QName Type Use Annotation
LABEL xsd:string optional 
LABEL (string/O): An attribute used, for example, to identify a <div> to an end user viewing the document. Thus a hierarchical arrangement of the <div> LABEL values could provide a table of contents to the digital content represented by a METS document and facilitate the users’ navigation of the digital object. Note that 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 . For further of the distinction between LABEL and ORDERLABEL see the description of the ORDERLABEL attribute.
ORDER xsd:integer optional 
ORDER (integer/O): A representation of the element's order among its siblings (e.g., its absolute, numeric sequence). For an example, and clarification of the distinction between ORDER and ORDERLABEL, see the description of the ORDERLABEL attribute.
ORDERLABEL xsd:string optional 
ORDERLABEL (string/O): A representation of the element's order among its siblings (e.g., “xii”), or of any non-integer native numbering system. It is presumed that this value will still be machine actionable (e.g., it would support ‘go to page ___’ function), and it should not be used as a replacement/substitute for the LABEL attribute. To understand 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”.
Source
 
<xsd:attributeGroup name="ORDERLABELS">
  <xsd:attribute name="ORDER" type="xsd:integer" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">ORDER (integer/O): A representation of the element's order among its siblings (e.g., its absolute, numeric sequence). For an example, and clarification of the distinction between ORDER and ORDERLABEL, see the description of the ORDERLABEL attribute.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="ORDERLABEL" type="xsd:string" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">ORDERLABEL (string/O): A representation of the element's order among its siblings (e.g., “xii”), or of any non-integer native numbering system. It is presumed that this value will still be machine actionable (e.g., it would support ‘go to page ___’ function), and it should not be used as a replacement/substitute for the LABEL attribute. To understand 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”.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="LABEL" type="xsd:string" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">LABEL (string/O): An attribute used, for example, to identify a <div> to an end user viewing the document. Thus a hierarchical arrangement of the <div> LABEL values could provide a table of contents to the digital content represented by a METS document and facilitate the users’ navigation of the digital object. Note that 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 . For further of the distinction between LABEL and ORDERLABEL see the description of the ORDERLABEL attribute.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
</xsd:attributeGroup>
XML Schema documentation generated by ® XML Editor.