Showing:

Annotations
Attributes
Diagrams
Facets
Instances
Model
Properties
Source
Used by
Main schema METS2_profile.xsd
Namespace http://www.loc.gov/METS_Profile/vNNN
Annotations
 
METS 2 Profile Schema Version NNN

      This document is available under the Creative Commons CC0 1.0 Universal Public Domain Dedication 
      (http://creativecommons.org/publicdomain/zero/1.0/). The Digital Library Federation, 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)

      March, 2024
      Version NNN
 
The METS Profile schema defines a document format for creating profiles of
a class of METS documents.  METS Profiles are intended to allow an individual
or organization to specify limitations and restrictions on the creation of METS
instance documents in order to define a document class.  METS instance 
documents which abide by those limitations and restrictions are said to conform to the profile.
      
METS profiles may serve a variety of purposes, but their primary purpose is
to promote interoperability and exchange of METS documents.  By allowing
any given institution to specify and publicize its practices with regards to creation
and use of METS documents, it can assist others both in creating METS
instances to be submitted to that institution and in processing METS documents
created by that institution.
 
Change log

      Version NNN (March 2024 - DRAFT) updates the profile schema for use with the
      METS schema version 2.

      Changes to align with linking and external references in METS 2:
      * allows any values for LOCTYPE and provides a link to suggested values
      * removes the OTHERLOCTYPE attribute.
      * removes the XLink schema and the xlink attributes for the testRef element
      * adds LOCREF and LOCTYPE attributes for the testRef element

      Changes to align with METS 2 elements:
      * replaces amdSec, dmdSec elements with mdSec
      * replaces structMap element with structSec,
      * removes structLink and behaviorSec elements
      * removes behavior_files element
      
      Version 2.1 (April 2018) added the Creative Commons CC0 1.0 license.  This version also added the xml:lang 
      attribute to more elements to make it easier to create multi-lingual profiles.  These elements were affected:
      
      * The external_schema/name element is now repeatable and allows the xml:lang attribute
      * The external_schema/context element now allows the xml:lang attribute
      * The controlled_vocabularies/vocabulary/name element is now repeatable and allows the xml:lang attribute
      * The controlled_vocabularies/vocabulary/context element now allows the xml:lang attribute	
      * The tool/name element is now repeatable and allows the xml:lang attribute	
      * The textSection/head complextype now allows the xml:lang attribute

      Version 2 of the METS profile schema extends the provisions of version 1.  In particular, it provides much 
      more extensive support for formatting documentation by means of xhtml elements which can be
      used in the context of the textSection data type.  In addition, as a first step towards machine actionability,
      the schema provides a means of specifying tests that can be applied to verify that specified requirements
      have been met.  Additional enhancements over the version 1 profile schema are described in the
      schema documentation.
 
Institutions wishing to make their profiles widely available may wish to consider
submitting them as public examples. Instructions for submitting a profile may be found
at https://github.com/METS/METS-profiles. This process replaces the formal registration
process used with earlier versions of METS profiles.
Properties
attribute form default unqualified
element form default qualified
Element METS_Profile
Namespace http://www.loc.gov/METS_Profile/vNNN
Annotations
 
Root element for a METS Profile
Diagram
Properties
content complex
Model
Children Appendix, Example, URI, abstract, contact, controlled_vocabularies, date, description_rules, external_schema, profile_context, related_profile, structural_requirements, technical_requirements, title, tool
Instance
 
<METS_Profile ID="" STATUS="" xmlns="http://www.loc.gov/METS_Profile/vNNN">
  <URI ASSIGNEDBY="" ID="" LOCTYPE="" REGDATE="">{1,unbounded}</URI>
  <title ID="" xml:lang="">{1,unbounded}</title>
  <abstract ID="" xml:lang="">{1,unbounded}</abstract>
  <date ID="">{1,1}</date>
  <contact ID="" ROLE="">{1,unbounded}</contact>
  <related_profile ID="" RELATIONSHIP="" URI="">{1,unbounded}</related_profile>
  <profile_context>{1,1}</profile_context>
  <external_schema ID="">{1,unbounded}</external_schema>
  <description_rules ID="">{1,1}</description_rules>
  <controlled_vocabularies ID="">{1,1}</controlled_vocabularies>
  <structural_requirements ID="">{1,1}</structural_requirements>
  <technical_requirements ID="">{1,1}</technical_requirements>
  <tool ID="">{1,unbounded}</tool>
  <Example ID="" LABEL="">{0,unbounded}</Example>
  <Appendix ID="" LABEL="" NUMBER="">{1,unbounded}</Appendix>
</METS_Profile>
Attributes
QName Type Use
ID xsd:ID optional
STATUS restriction of xsd:string required
Source
 
<xsd:element name="METS_Profile">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">Root element for a METS Profile</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="URI" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">Every METS profile must be assigned a unique URI RFC 2396 by the institution responsible for its creation. This URI must have the attribute ASSIGNEDBY="local".</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:simpleContent>
            <xsd:extension base="xsd:anyURI">
              <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
              <xsd:attribute name="LOCTYPE" type="xsd:string" use="required"/>
              <xsd:attribute name="ASSIGNEDBY" use="required">
                <xsd:simpleType>
                  <xsd:restriction base="xsd:string">
                    <xsd:enumeration value="metsboard"/>
                    <xsd:enumeration value="local"/>
                  </xsd:restriction>
                </xsd:simpleType>
              </xsd:attribute>
              <xsd:attribute name="REGDATE" type="xsd:date" use="optional"/>
            </xsd:extension>
          </xsd:simpleContent>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="title" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">The profile must contain a short, human readable string describing the class of METS objects being profiled (e.g., "NYU Monograph", "Stereographic Image", "SCORM object", etc.). This title must not exceed 256 characters.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:simpleContent>
            <xsd:extension base="medString">
              <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
              <xsd:attribute ref="xml:lang" use="optional"/>
            </xsd:extension>
          </xsd:simpleContent>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="abstract" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">The profile must contain a one-paragraph description of the profile's nature and purpose. This abstract must not exceed 2048 characters in length.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:simpleContent>
            <xsd:extension base="longString">
              <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
              <xsd:attribute ref="xml:lang" use="optional"/>
            </xsd:extension>
          </xsd:simpleContent>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="date">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">The profile must include the date and time the profile was created by the responsible institution.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:simpleContent>
            <xsd:extension base="xsd:dateTime">
              <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
            </xsd:extension>
          </xsd:simpleContent>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="contact" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">The profile must contain contact information for an individual or entity responsible for the profile's creation and who may be contacted for clarification of the contents of the profile. Contact information must include a mailing address that can be used to contact someone regarding the profile, and may also include the name of a specific individual to contact for information regarding the profile, the name of the institution responsible for creating the schema, a phone number for a contact individual and an e-mail address.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element name="name" minOccurs="0">
              <xsd:annotation>
                <xsd:documentation xml:lang="en">The name of an individual who may be contacted regarding the profile.</xsd:documentation>
              </xsd:annotation>
              <xsd:complexType>
                <xsd:simpleContent>
                  <xsd:extension base="xsd:string">
                    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                  </xsd:extension>
                </xsd:simpleContent>
              </xsd:complexType>
            </xsd:element>
            <xsd:element name="institution" minOccurs="0">
              <xsd:annotation>
                <xsd:documentation xml:lang="en">The name of an institution which may be contacted regarding the profile.</xsd:documentation>
              </xsd:annotation>
              <xsd:complexType>
                <xsd:simpleContent>
                  <xsd:extension base="xsd:string">
                    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                  </xsd:extension>
                </xsd:simpleContent>
              </xsd:complexType>
            </xsd:element>
            <xsd:element name="address">
              <xsd:annotation>
                <xsd:documentation xml:lang="en">The address for the individual and/or institution which may be contacted regarding the profile.</xsd:documentation>
              </xsd:annotation>
              <xsd:complexType>
                <xsd:simpleContent>
                  <xsd:extension base="xsd:string">
                    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                  </xsd:extension>
                </xsd:simpleContent>
              </xsd:complexType>
            </xsd:element>
            <xsd:element name="phone" minOccurs="0">
              <xsd:annotation>
                <xsd:documentation xml:lang="en">A phone number which people may call for information regarding the profile.</xsd:documentation>
              </xsd:annotation>
              <xsd:complexType>
                <xsd:simpleContent>
                  <xsd:extension base="xsd:string">
                    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                  </xsd:extension>
                </xsd:simpleContent>
              </xsd:complexType>
            </xsd:element>
            <xsd:element name="email" minOccurs="0">
              <xsd:annotation>
                <xsd:documentation xml:lang="en">An e-mail address which people may contact for information regarding the profile.</xsd:documentation>
              </xsd:annotation>
              <xsd:complexType>
                <xsd:simpleContent>
                  <xsd:extension base="xsd:string">
                    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                  </xsd:extension>
                </xsd:simpleContent>
              </xsd:complexType>
            </xsd:element>
          </xsd:sequence>
          <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
          <xsd:attribute name="ROLE" type="xsd:string" use="optional"/>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="related_profile" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">A profile may indicate its relationship with other METS profiles. METS profiles are not explicitly versioned, as implementations may exist that use older editions of METS profiles. For each related profile, the profile should specify a URI for the related profile and the nature of the relationship between the current profile and the related profile.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:simpleContent>
            <xsd:extension base="xsd:string">
              <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
              <xsd:attribute name="URI" type="xsd:anyURI" use="optional"/>
              <xsd:attribute name="RELATIONSHIP" type="xsd:string" use="optional">
                <xsd:annotation>
                  <xsd:documentation xml:lang="en">While this attribute is optional, and no controlled vocabulary is prescribed for it, the following vocabulary is recommended for common relationships: supersedes -- profile is a new, revised version of an existing profile extends -- profile builds on and extends an existing profile</xsd:documentation>
                </xsd:annotation>
              </xsd:attribute>
            </xsd:extension>
          </xsd:simpleContent>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="profile_context">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">A profile may document the context in which it operates through the inclusion of a Resource Model and statement of Use Cases.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element name="resource_model" minOccurs="0" type="textSection">
              <xsd:annotation>
                <xsd:documentation xml:lang="en">This section is made up of simple text describing what the objects are that the Profile deals with, and could include information such as whether the profile is intended for an OAIS SIP, AIP, or DIP. Available are an optional head subelement and some available text formatting elements from the xhtml namespace. Available xhtml elements include p, various list/item elements, text formatting such as b and i, a, and img.</xsd:documentation>
              </xsd:annotation>
            </xsd:element>
            <xsd:element name="uses" minOccurs="0" maxOccurs="unbounded">
              <xsd:annotation>
                <xsd:documentation xml:lang="en">This section is made up of one uses element containing one or more use subelements, each describing a single use case. It is primarily envisioned to describe different requirements for METS documents at different points in their project lifecycle with a single profile, connecting a processing action with a specific feature of a METS document. The use element has an optional REQID attribute, which is an IDREF to the ID of a specific <requirement> element declared in the same profile.</xsd:documentation>
              </xsd:annotation>
              <xsd:complexType>
                <xsd:sequence>
                  <xsd:element name="use" maxOccurs="unbounded">
                    <xsd:annotation>
                      <xsd:documentation xml:lang="en">The use element has an optional head subelement and some available text formatting elements from the xhtml namespace. Available xhtml elements include p, various list/item elements, text formatting such as b and i, a, and img. The latter could be used to embed within the profile documentation such as a diagram of a business process that uses a METS document conforming to the profile.</xsd:documentation>
                    </xsd:annotation>
                    <xsd:complexType>
                      <xsd:complexContent>
                        <xsd:extension base="textSection">
                          <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                          <xsd:attribute name="REQID" type="xsd:IDREFS" use="optional"/>
                        </xsd:extension>
                      </xsd:complexContent>
                    </xsd:complexType>
                  </xsd:element>
                </xsd:sequence>
              </xsd:complexType>
            </xsd:element>
          </xsd:sequence>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="external_schema" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">A single external_schema element should used for each external schema listed in the profile. Multiple external_schema elements may be used within a single profile. For each external schema described, you may provide a name of the schema, a URI assigned to the schema, a context description indicating where in a conforming METS document the schema may be used, and an additional note. The note element has an optional head subelement and some available text formatting elements from the xhtml namespace. Available xhtml elements include p, various list/item elements, text formatting such as b and i, a, and img.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element name="name" minOccurs="0" maxOccurs="unbounded">
              <xsd:annotation>
                <xsd:documentation xml:lang="en">The external schema name may be repeated if it is available in different languages; use the xml:lang attribute to differentiate.</xsd:documentation>
              </xsd:annotation>
              <xsd:complexType>
                <xsd:simpleContent>
                  <xsd:extension base="xsd:string">
                    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                    <xsd:attribute ref="xml:lang" use="optional"/>
                  </xsd:extension>
                </xsd:simpleContent>
              </xsd:complexType>
            </xsd:element>
            <xsd:element name="URL" minOccurs="0" maxOccurs="unbounded">
              <xsd:complexType>
                <xsd:simpleContent>
                  <xsd:extension base="xsd:anyURI">
                    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                    <xsd:attribute name="TARGETNAMESPACE" type="xsd:anyURI" use="optional"/>
                  </xsd:extension>
                </xsd:simpleContent>
              </xsd:complexType>
            </xsd:element>
            <xsd:element name="context" minOccurs="0" maxOccurs="unbounded">
              <xsd:annotation>
                <xsd:documentation xml:lang="en">The external schema context may be repeated. Use the xml:lang attribute to indicate contexts provided in different languages.</xsd:documentation>
              </xsd:annotation>
              <xsd:complexType>
                <xsd:simpleContent>
                  <xsd:extension base="xsd:string">
                    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                    <xsd:attribute ref="xml:lang" use="optional"/>
                  </xsd:extension>
                </xsd:simpleContent>
              </xsd:complexType>
            </xsd:element>
            <xsd:element name="note" minOccurs="0">
              <xsd:complexType>
                <xsd:complexContent>
                  <xsd:extension base="textSection">
                    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                  </xsd:extension>
                </xsd:complexContent>
              </xsd:complexType>
            </xsd:element>
          </xsd:sequence>
          <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="description_rules">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">An institution may choose to employ particular rules of description when encoding text within elements and attributes of a METS document. For example, a library might decide that descriptive metadata within a <dmdSec><mdWrap> section will be encoded using the Library of Congress' MARC 21 XML Schema MARCXML, and that the content of all elements and attributes within the MARC 21 XML sections must be prepared in accordance with the Anglo-American Cataloguing Rules 2nd Edition AACR2. The Rules of Description portion of a METS profile for that institution's METS objects should indicate that AACR2 must be applied to all content within a MARC 21 XML Schema portion of a METS document conforming to that profile. The description_rules element has an optional head subelement and some available text formatting elements from the xhtml namespace. Available xhtml elements include p, various list/item elements, text formatting such as b and i, a, and img.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:complexContent>
            <xsd:extension base="textSection">
              <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
            </xsd:extension>
          </xsd:complexContent>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="controlled_vocabularies">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">An institution may choose to employ certain controlled vocabularies, such as the Library of Congress Subject Headings or the Getty Thesaurus of Geographic Names, for the content of elements within portions of a METS document. If use of a particular controlled vocabulary is mandatory in any section of a conforming METS document, that controlled vocabulary must be listed in this section of a profile. For all such controlled vocabularies, you should provide a name for the controlled vocabulary, an agency responsible for the vocabulary's maintenance, and a URI assigned to the vocabulary. If you desire, you may also include the individual values/terms within the controlled vocabulary, although it is anticipated that this will only be done when you wish to publicize the contents of a locally-produced controlled vocabulary to others who wish to produce conforming METS documents; there is no need to itemize the contents of well-known controlled vocabularies such as LCSH. For all controlled vocabularies, you should provide contextual information indicating where within a conforming METS document the vocabulary may be used, and if desired brief description of the vocabulary and its purpose. The context and description subelements of vocabulary have an optional head subelement and some available text formatting elements from the xhtml namespace. Available xhtml elements include p, various list/item elements, text formatting such as b and i, a, and img.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element name="vocabulary" minOccurs="0" maxOccurs="unbounded">
              <xsd:complexType>
                <xsd:sequence>
                  <xsd:element name="name" minOccurs="0" maxOccurs="unbounded">
                    <xsd:annotation>
                      <xsd:documentation xml:lang="en">The vocabulary name may be repeated if there are multiple versions of the name in different languages; use the xml:lang attribute to differentiate them.</xsd:documentation>
                    </xsd:annotation>
                    <xsd:complexType>
                      <xsd:simpleContent>
                        <xsd:extension base="xsd:string">
                          <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                          <xsd:attribute ref="xml:lang" use="optional"/>
                        </xsd:extension>
                      </xsd:simpleContent>
                    </xsd:complexType>
                  </xsd:element>
                  <xsd:element name="maintenance_agency" minOccurs="0">
                    <xsd:complexType>
                      <xsd:simpleContent>
                        <xsd:extension base="xsd:string">
                          <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                        </xsd:extension>
                      </xsd:simpleContent>
                    </xsd:complexType>
                  </xsd:element>
                  <xsd:element name="URI" minOccurs="0">
                    <xsd:complexType>
                      <xsd:simpleContent>
                        <xsd:extension base="xsd:anyURI">
                          <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                        </xsd:extension>
                      </xsd:simpleContent>
                    </xsd:complexType>
                  </xsd:element>
                  <xsd:element name="values" minOccurs="0">
                    <xsd:complexType>
                      <xsd:sequence>
                        <xsd:element name="value" maxOccurs="unbounded">
                          <xsd:complexType>
                            <xsd:simpleContent>
                              <xsd:extension base="xsd:string">
                                <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                              </xsd:extension>
                            </xsd:simpleContent>
                          </xsd:complexType>
                        </xsd:element>
                      </xsd:sequence>
                      <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                    </xsd:complexType>
                  </xsd:element>
                  <xsd:element name="context" minOccurs="0" maxOccurs="unbounded">
                    <xsd:annotation>
                      <xsd:documentation xml:lang="en">The vocabulary context may be repeated if there are multiple versions of the context in different languages; use the xml:lang attribute to differentiate them.</xsd:documentation>
                    </xsd:annotation>
                    <xsd:complexType>
                      <xsd:simpleContent>
                        <xsd:extension base="xsd:string">
                          <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                          <xsd:attribute ref="xml:lang" use="optional"/>
                        </xsd:extension>
                      </xsd:simpleContent>
                    </xsd:complexType>
                  </xsd:element>
                  <xsd:element name="description" minOccurs="0">
                    <xsd:complexType>
                      <xsd:complexContent>
                        <xsd:extension base="textSection">
                          <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                        </xsd:extension>
                      </xsd:complexContent>
                    </xsd:complexType>
                  </xsd:element>
                </xsd:sequence>
                <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
              </xsd:complexType>
            </xsd:element>
          </xsd:sequence>
          <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="structural_requirements">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">The METS document structure is extraordinarily flexible; that flexibility may be problematic inasmuch as creating software to process any arbitrary METS document in any but the most rudimentary way (XML parsing and validation) is a non-trivial task. This task can be simplified to some degree if those creating software to process METS documents know that there are further constraints on the structure of a METS document beyond those of the METS schema itself. The structural requirements portion of a METS profile allows an institution to delineate additional restrictions on the structure of a conforming METS document beyond those specified by the METS format itself. It is permissible to specify restrictions on the structure of a conforming METS document which cannot be validated by standard XML validation tools. For example, it would be a permissible restriction to state that master still images within a METS document should be contained within a separate file group from derivative images. It is impossible to fully delineate the possible additional structural restrictions that institutions may wish to set forth in their profiles, but the following list identifies some major areas of concern that institutions may wish to address in the Structural Requirements portion of a profile: --Are there any restrictions on the number of occurrences of elements or attributes set forth in the METS schema beyond those specified by the METS schema itself (e.g., there should only be one occurrence of a dmdSec, every conforming document must include a metsHdr element, etc.)? --Are there any restrictions on the number of occurrences of elements or attributes encoded using extension schema beyond those specified by those schema? --May extension schema only be used within a particular portion of a METS document (e.g., you may wish to specify that a particular extension schema may be used within a <mdWrap> element within a <techMD> section, but that it should not be used within a <sourceMD> section). --Should the structural map conform to a particular model? For instance, a profile for monographs might specify that the root <div> element must have a TYPE attribute of "book", that all immediately subsidiary <div>s have a TYPE attribute of "chapter". Alternatively, it might specify that there be a root <div> with a TYPE attribute of "text" with subsidiary <div>s having a TYPE attribute of "page". Structural metadata is the heart of a METS document, and those creating profiles should try to be as explicit and precise as possible in specifying how structural maps should be created, and may wish to include examples within an appendix to the profile. --Should document authors include metadata within a METS document using mdWrap, or reference it using mdRef? Or are both allowable? --Should content files be included within a METS document using Fcontent, or referenced using FLocat? Or are both allowable? The structural_requirements is subdivided into subelements for each major section of a METS document. Requirements pertaining to a particular section should be listed underneath the section of the METS document to which they pertain. If you need to specify a structural requirement that involves more than one major section of the METS document, list it underneath the multiSection subelement within the structural_requirements element. Every subelement within the structural_requirements section is composed of a sequence of individual requirement elements.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element name="metsRootElement" minOccurs="0">
              <xsd:complexType>
                <xsd:complexContent>
                  <xsd:extension base="reqs">
                    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                  </xsd:extension>
                </xsd:complexContent>
              </xsd:complexType>
            </xsd:element>
            <xsd:element name="metsHdr" minOccurs="0">
              <xsd:complexType>
                <xsd:complexContent>
                  <xsd:extension base="reqs">
                    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                  </xsd:extension>
                </xsd:complexContent>
              </xsd:complexType>
            </xsd:element>
            <xsd:element name="mdSec" minOccurs="0">
              <xsd:complexType>
                <xsd:complexContent>
                  <xsd:extension base="reqs">
                    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                  </xsd:extension>
                </xsd:complexContent>
              </xsd:complexType>
            </xsd:element>
            <xsd:element name="fileSec" minOccurs="0">
              <xsd:complexType>
                <xsd:complexContent>
                  <xsd:extension base="reqs">
                    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                  </xsd:extension>
                </xsd:complexContent>
              </xsd:complexType>
            </xsd:element>
            <xsd:element name="structSec" minOccurs="0">
              <xsd:complexType>
                <xsd:complexContent>
                  <xsd:extension base="reqs">
                    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                  </xsd:extension>
                </xsd:complexContent>
              </xsd:complexType>
            </xsd:element>
            <xsd:element name="multiSection" minOccurs="0">
              <xsd:complexType>
                <xsd:complexContent>
                  <xsd:extension base="reqs">
                    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                  </xsd:extension>
                </xsd:complexContent>
              </xsd:complexType>
            </xsd:element>
          </xsd:sequence>
          <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="technical_requirements">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">A METS document may reference a variety of external files, including the content files for the METS object (via <FLocat>elements), executable behaviors (via the <mechanism> element), and external metadata files (via <mdRef> elements). Non-XML content and metadata files may also be embedded within a METS instance, if they have been Base64 encoded. Institutions may wish to place restrictions on the nature of these external and non-XML files, such as insisting that all image files be in the TIFF 6.0 format and have a bit-depth between 16 and 32 bits, or that references to external metadata identified as being of type "MARC" via the MDTYPE attribute will point to MARC records conforming to the MARC 21 standard (or alternatively, to an HTML display of a MARC 21 record). The Technical Requirements section of a profile allows institutions to set forth the full set of restrictions on the technical nature of files which may be referenced from a conforming METS document. It is subdivided into sections for restrictions on content files, restrictions on behavior files, and restrictions on metadata files. Profile authors should bear in mind that one of the primary purposes of the Technical Requirements section is to allow software developers to anticipate what types of content will be accessible via links from the METS objects, and hence what software is needed to process that content. Every subelement within the technical_requirements section is composed of a sequence of individual requirement elements.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element name="content_files" minOccurs="0">
              <xsd:complexType>
                <xsd:complexContent>
                  <xsd:extension base="reqs">
                    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                  </xsd:extension>
                </xsd:complexContent>
              </xsd:complexType>
            </xsd:element>
            <xsd:element name="metadata_files" minOccurs="0">
              <xsd:complexType>
                <xsd:complexContent>
                  <xsd:extension base="reqs">
                    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                  </xsd:extension>
                </xsd:complexContent>
              </xsd:complexType>
            </xsd:element>
          </xsd:sequence>
          <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="tool" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">A profile should provide a description of any affiliated tools, including validators, stylesheets, authoring tools, rendering applications, which can or should be used with METS documents conforming to the profile. The description should provide a name for the tool, the agency responsible for its development, a description of the tool, and a URI for obtaining the tool or further information regarding it. The description and note subelments of tool have an optional head subelement and some available text formatting elements from the xhtml namespace. Available xhtml elements include p, various list/item elements, text formatting such as b and i, a, and img.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element name="name" minOccurs="0" maxOccurs="unbounded">
              <xsd:annotation>
                <xsd:documentation xml:lang="en">The tool name may be repeated if there are multiple versions of the name in different languages; use the xml:lang attribute to differentiate them.</xsd:documentation>
              </xsd:annotation>
              <xsd:complexType>
                <xsd:simpleContent>
                  <xsd:extension base="xsd:string">
                    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                    <xsd:attribute ref="xml:lang" use="optional"/>
                  </xsd:extension>
                </xsd:simpleContent>
              </xsd:complexType>
            </xsd:element>
            <xsd:element name="agency" minOccurs="0">
              <xsd:complexType>
                <xsd:simpleContent>
                  <xsd:extension base="xsd:string">
                    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                  </xsd:extension>
                </xsd:simpleContent>
              </xsd:complexType>
            </xsd:element>
            <xsd:element name="URI" minOccurs="0" maxOccurs="unbounded">
              <xsd:complexType>
                <xsd:simpleContent>
                  <xsd:extension base="xsd:anyURI">
                    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                  </xsd:extension>
                </xsd:simpleContent>
              </xsd:complexType>
            </xsd:element>
            <xsd:element name="description" minOccurs="0">
              <xsd:complexType>
                <xsd:complexContent>
                  <xsd:extension base="textSection">
                    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                  </xsd:extension>
                </xsd:complexContent>
              </xsd:complexType>
            </xsd:element>
            <xsd:element name="note" minOccurs="0">
              <xsd:complexType>
                <xsd:complexContent>
                  <xsd:extension base="textSection">
                    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                  </xsd:extension>
                </xsd:complexContent>
              </xsd:complexType>
            </xsd:element>
          </xsd:sequence>
          <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="Example" minOccurs="0" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">A METS profile may contain one or more Example elements. Unlike Appendix elements, which are expected to contain complete METS encodings, an Example element would contain just a code snippet intended to demonstrate some requirement of the profile. The data type of the Examples element allows for partial, well-formed encodings that still might not satisfy all of the requirements for a full METS encoding. A requirement can link to one or more Example elements by referencing the ID value of the pertinent Example elements in its EXAMPLES attribute. The Example element has two attributes: 1. ID. This attribute is required, as every Example should be linked to from the requirement of which it is an example. 2. LABEL. This optional attribute allows for the descriptive labeling of an example.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:sequence>
            <xsd:any namespace="##any" maxOccurs="unbounded" processContents="skip"/>
          </xsd:sequence>
          <xsd:attribute name="ID" type="xsd:ID" use="required"/>
          <xsd:attribute name="LABEL" type="xsd:string" use="optional"/>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="Appendix" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">A profile must contain an appendix containing an example METS document which conforms to the requirements set out in the profile. Profile authors should note that in order to insure that the completed profile document is valid, any namespace and schemaLocation declarations contained in the root <mets> element should be moved to the root <METS_Profile> element.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:sequence>
            <xsd:any namespace="##any" maxOccurs="unbounded"/>
          </xsd:sequence>
          <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
          <xsd:attribute name="NUMBER" type="xsd:integer" use="required"/>
          <xsd:attribute name="LABEL" type="xsd:string" use="optional"/>
        </xsd:complexType>
      </xsd:element>
    </xsd:sequence>
    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
    <xsd:attribute name="STATUS" use="required">
      <xsd:simpleType>
        <xsd:restriction base="xsd:string">
          <xsd:enumeration value="final"/>
          <xsd:enumeration value="provisional"/>
        </xsd:restriction>
      </xsd:simpleType>
    </xsd:attribute>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / URI
Namespace http://www.loc.gov/METS_Profile/vNNN
Annotations
 
Every METS profile must be assigned a unique URI RFC 2396 by the institution responsible for its creation. This URI must have the attribute ASSIGNEDBY="local".
Diagram
Type extension of xsd:anyURI
Properties
content complex
maxOccurs unbounded
Attributes
QName Type Use
ASSIGNEDBY restriction of xsd:string required
ID xsd:ID optional
LOCTYPE xsd:string required
REGDATE xsd:date optional
Source
 
<xsd:element name="URI" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">Every METS profile must be assigned a unique URI RFC 2396 by the institution responsible for its creation. This URI must have the attribute ASSIGNEDBY="local".</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="xsd:anyURI">
        <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
        <xsd:attribute name="LOCTYPE" type="xsd:string" use="required"/>
        <xsd:attribute name="ASSIGNEDBY" use="required">
          <xsd:simpleType>
            <xsd:restriction base="xsd:string">
              <xsd:enumeration value="metsboard"/>
              <xsd:enumeration value="local"/>
            </xsd:restriction>
          </xsd:simpleType>
        </xsd:attribute>
        <xsd:attribute name="REGDATE" type="xsd:date" use="optional"/>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / title
Namespace http://www.loc.gov/METS_Profile/vNNN
Annotations
 
The profile must contain a short, human readable string describing the class of METS objects being profiled (e.g., "NYU Monograph", "Stereographic Image", "SCORM object", etc.). This title must not exceed 256 characters.
Diagram
Type extension of medString
Type hierarchy
Properties
content complex
maxOccurs unbounded
Attributes
QName Type Use Annotation
ID xsd:ID optional
xml:lang union of(xs:language, restriction of xs:string) optional 
Attempting to install the relevant ISO 2- and 3-letter
         codes as the enumerated possible values is probably never
         going to be a realistic possibility.  See
         RFC 3066 at http://www.ietf.org/rfc/rfc3066.txt and the IANA registry
         at http://www.iana.org/assignments/lang-tag-apps.htm for
         further information.

         The union allows for the 'un-declaration' of xml:lang with
         the empty string.
Source
 
<xsd:element name="title" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The profile must contain a short, human readable string describing the class of METS objects being profiled (e.g., "NYU Monograph", "Stereographic Image", "SCORM object", etc.). This title must not exceed 256 characters.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="medString">
        <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
        <xsd:attribute ref="xml:lang" use="optional"/>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / abstract
Namespace http://www.loc.gov/METS_Profile/vNNN
Annotations
 
The profile must contain a one-paragraph description of the profile's nature and purpose. This abstract must not exceed 2048 characters in length.
Diagram
Type extension of longString
Type hierarchy
Properties
content complex
maxOccurs unbounded
Attributes
QName Type Use Annotation
ID xsd:ID optional
xml:lang union of(xs:language, restriction of xs:string) optional 
Attempting to install the relevant ISO 2- and 3-letter
         codes as the enumerated possible values is probably never
         going to be a realistic possibility.  See
         RFC 3066 at http://www.ietf.org/rfc/rfc3066.txt and the IANA registry
         at http://www.iana.org/assignments/lang-tag-apps.htm for
         further information.

         The union allows for the 'un-declaration' of xml:lang with
         the empty string.
Source
 
<xsd:element name="abstract" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The profile must contain a one-paragraph description of the profile's nature and purpose. This abstract must not exceed 2048 characters in length.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="longString">
        <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
        <xsd:attribute ref="xml:lang" use="optional"/>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / date
Namespace http://www.loc.gov/METS_Profile/vNNN
Annotations
 
The profile must include the date and time the profile was created by the responsible institution.
Diagram
Type extension of xsd:dateTime
Properties
content complex
Attributes
QName Type Use
ID xsd:ID optional
Source
 
<xsd:element name="date">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The profile must include the date and time the profile was created by the responsible institution.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="xsd:dateTime">
        <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / contact
Namespace http://www.loc.gov/METS_Profile/vNNN
Annotations
 
The profile must contain contact information for an individual or entity responsible for the profile's creation and who may be contacted for clarification of the contents of the profile. Contact information must include a mailing address that can be used to contact someone regarding the profile, and may also include the name of a specific individual to contact for information regarding the profile, the name of the institution responsible for creating the schema, a phone number for a contact individual and an e-mail address.
Diagram
Properties
content complex
maxOccurs unbounded
Model
Children address, email, institution, name, phone
Instance
 
<contact ID="" ROLE="" xmlns="http://www.loc.gov/METS_Profile/vNNN">
  <name ID="">{0,1}</name>
  <institution ID="">{0,1}</institution>
  <address ID="">{1,1}</address>
  <phone ID="">{0,1}</phone>
  <email ID="">{0,1}</email>
</contact>
Attributes
QName Type Use
ID xsd:ID optional
ROLE xsd:string optional
Source
 
<xsd:element name="contact" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The profile must contain contact information for an individual or entity responsible for the profile's creation and who may be contacted for clarification of the contents of the profile. Contact information must include a mailing address that can be used to contact someone regarding the profile, and may also include the name of a specific individual to contact for information regarding the profile, the name of the institution responsible for creating the schema, a phone number for a contact individual and an e-mail address.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="name" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">The name of an individual who may be contacted regarding the profile.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:simpleContent>
            <xsd:extension base="xsd:string">
              <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
            </xsd:extension>
          </xsd:simpleContent>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="institution" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">The name of an institution which may be contacted regarding the profile.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:simpleContent>
            <xsd:extension base="xsd:string">
              <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
            </xsd:extension>
          </xsd:simpleContent>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="address">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">The address for the individual and/or institution which may be contacted regarding the profile.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:simpleContent>
            <xsd:extension base="xsd:string">
              <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
            </xsd:extension>
          </xsd:simpleContent>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="phone" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">A phone number which people may call for information regarding the profile.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:simpleContent>
            <xsd:extension base="xsd:string">
              <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
            </xsd:extension>
          </xsd:simpleContent>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="email" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">An e-mail address which people may contact for information regarding the profile.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:simpleContent>
            <xsd:extension base="xsd:string">
              <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
            </xsd:extension>
          </xsd:simpleContent>
        </xsd:complexType>
      </xsd:element>
    </xsd:sequence>
    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
    <xsd:attribute name="ROLE" type="xsd:string" use="optional"/>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / contact / name
Namespace http://www.loc.gov/METS_Profile/vNNN
Annotations
 
The name of an individual who may be contacted regarding the profile.
Diagram
Type extension of xsd:string
Properties
content complex
minOccurs 0
Attributes
QName Type Use
ID xsd:ID optional
Source
 
<xsd:element name="name" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The name of an individual who may be contacted regarding the profile.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="xsd:string">
        <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / contact / institution
Namespace http://www.loc.gov/METS_Profile/vNNN
Annotations
 
The name of an institution which may be contacted regarding the profile.
Diagram
Type extension of xsd:string
Properties
content complex
minOccurs 0
Attributes
QName Type Use
ID xsd:ID optional
Source
 
<xsd:element name="institution" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The name of an institution which may be contacted regarding the profile.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="xsd:string">
        <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / contact / address
Namespace http://www.loc.gov/METS_Profile/vNNN
Annotations
 
The address for the individual and/or institution which may be contacted regarding the profile.
Diagram
Type extension of xsd:string
Properties
content complex
Attributes
QName Type Use
ID xsd:ID optional
Source
 
<xsd:element name="address">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The address for the individual and/or institution which may be contacted regarding the profile.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="xsd:string">
        <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / contact / phone
Namespace http://www.loc.gov/METS_Profile/vNNN
Annotations
 
A phone number which people may call for information regarding the profile.
Diagram
Type extension of xsd:string
Properties
content complex
minOccurs 0
Attributes
QName Type Use
ID xsd:ID optional
Source
 
<xsd:element name="phone" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">A phone number which people may call for information regarding the profile.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="xsd:string">
        <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / contact / email
Namespace http://www.loc.gov/METS_Profile/vNNN
Annotations
 
An e-mail address which people may contact for information regarding the profile.
Diagram
Type extension of xsd:string
Properties
content complex
minOccurs 0
Attributes
QName Type Use
ID xsd:ID optional
Source
 
<xsd:element name="email" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">An e-mail address which people may contact for information regarding the profile.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="xsd:string">
        <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / related_profile
Namespace http://www.loc.gov/METS_Profile/vNNN
Annotations
Diagram
Type extension of xsd:string
Properties
Attributes
Source
Element METS_Profile / profile_context
Namespace http://www.loc.gov/METS_Profile/vNNN
Annotations
 
A profile may document the context in which it operates through the inclusion of a Resource Model and statement of Use Cases.
Diagram
Properties
content complex
Model
Children resource_model, uses
Instance
 
<profile_context xmlns="http://www.loc.gov/METS_Profile/vNNN">
  <resource_model>{0,1}</resource_model>
  <uses>{0,unbounded}</uses>
</profile_context>
Source
 
<xsd:element name="profile_context">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">A profile may document the context in which it operates through the inclusion of a Resource Model and statement of Use Cases.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="resource_model" minOccurs="0" type="textSection">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">This section is made up of simple text describing what the objects are that the Profile deals with, and could include information such as whether the profile is intended for an OAIS SIP, AIP, or DIP. Available are an optional head subelement and some available text formatting elements from the xhtml namespace. Available xhtml elements include p, various list/item elements, text formatting such as b and i, a, and img.</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="uses" minOccurs="0" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">This section is made up of one uses element containing one or more use subelements, each describing a single use case. It is primarily envisioned to describe different requirements for METS documents at different points in their project lifecycle with a single profile, connecting a processing action with a specific feature of a METS document. The use element has an optional REQID attribute, which is an IDREF to the ID of a specific <requirement> element declared in the same profile.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element name="use" maxOccurs="unbounded">
              <xsd:annotation>
                <xsd:documentation xml:lang="en">The use element has an optional head subelement and some available text formatting elements from the xhtml namespace. Available xhtml elements include p, various list/item elements, text formatting such as b and i, a, and img. The latter could be used to embed within the profile documentation such as a diagram of a business process that uses a METS document conforming to the profile.</xsd:documentation>
              </xsd:annotation>
              <xsd:complexType>
                <xsd:complexContent>
                  <xsd:extension base="textSection">
                    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                    <xsd:attribute name="REQID" type="xsd:IDREFS" use="optional"/>
                  </xsd:extension>
                </xsd:complexContent>
              </xsd:complexType>
            </xsd:element>
          </xsd:sequence>
        </xsd:complexType>
      </xsd:element>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / profile_context / resource_model
Namespace http://www.loc.gov/METS_Profile/vNNN
Annotations
 
This section is made up of simple text describing what the objects are that the Profile deals with, and could include information such as whether the profile is intended for an OAIS SIP, AIP, or DIP. Available are an optional head subelement and some available text formatting elements from the xhtml namespace. Available xhtml elements include p, various list/item elements, text formatting such as b and i, a, and img.
Diagram
Type textSection
Properties
content complex
minOccurs 0
Model
(head{0,1} | p | ul | ol | dl)
Children dl, head, ol, p, ul
Instance
 
<resource_model xmlns="http://www.loc.gov/METS_Profile/vNNN" xmlns:xhtml="http://www.w3.org/1999/xhtml">
  <head ID="" xml:lang="">{0,1}</head>
  <xhtml:p class="" dir="" id="" lang="" xml:lang="" onclick="" ondblclick="" onkeydown="" onkeypress="" onkeyup="" onmousedown="" onmousemove="" onmouseout="" onmouseover="" onmouseup="" style="" title="">{1,1}</xhtml:p>
  <xhtml:ul class="" dir="" id="" lang="" xml:lang="" onclick="" ondblclick="" onkeydown="" onkeypress="" onkeyup="" onmousedown="" onmousemove="" onmouseout="" onmouseover="" onmouseup="" style="" title="">{1,1}</xhtml:ul>
  <xhtml:ol class="" dir="" id="" lang="" xml:lang="" onclick="" ondblclick="" onkeydown="" onkeypress="" onkeyup="" onmousedown="" onmousemove="" onmouseout="" onmouseover="" onmouseup="" style="" title="">{1,1}</xhtml:ol>
  <xhtml:dl class="" dir="" id="" lang="" xml:lang="" onclick="" ondblclick="" onkeydown="" onkeypress="" onkeyup="" onmousedown="" onmousemove="" onmouseout="" onmouseover="" onmouseup="" style="" title="">{1,1}</xhtml:dl>
</resource_model>
Source
 
<xsd:element name="resource_model" minOccurs="0" type="textSection">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">This section is made up of simple text describing what the objects are that the Profile deals with, and could include information such as whether the profile is intended for an OAIS SIP, AIP, or DIP. Available are an optional head subelement and some available text formatting elements from the xhtml namespace. Available xhtml elements include p, various list/item elements, text formatting such as b and i, a, and img.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
Element textSection / head
Namespace http://www.loc.gov/METS_Profile/vNNN
Annotations
 
The section head may be repeated.  If there are multiple versions of the head in different languages; use the xml:lang attribute to differentiate them.
Diagram
Type extension of xsd:string
Properties
content complex
minOccurs 0
maxOccurs 1
Attributes
QName Type Use Annotation
ID xsd:ID optional
xml:lang union of(xs:language, restriction of xs:string) optional 
Attempting to install the relevant ISO 2- and 3-letter
         codes as the enumerated possible values is probably never
         going to be a realistic possibility.  See
         RFC 3066 at http://www.ietf.org/rfc/rfc3066.txt and the IANA registry
         at http://www.iana.org/assignments/lang-tag-apps.htm for
         further information.

         The union allows for the 'un-declaration' of xml:lang with
         the empty string.
Source
 
<xsd:element name="head" minOccurs="0" maxOccurs="1">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The section head may be repeated. If there are multiple versions of the head in different languages; use the xml:lang attribute to differentiate them.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="xsd:string">
        <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
        <xsd:attribute ref="xml:lang" use="optional"/>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / profile_context / uses
Namespace http://www.loc.gov/METS_Profile/vNNN
Annotations
 
This section is made up of one uses element containing one or more use subelements, each describing a single use case. It is primarily envisioned to describe different requirements for METS documents at different points in their project lifecycle with a single profile, connecting a processing action with a specific feature of a METS document. The use element has an optional REQID attribute, which is an IDREF to the ID of a specific <requirement> element declared in the same profile.
Diagram
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children use
Instance
 
<uses xmlns="http://www.loc.gov/METS_Profile/vNNN">
  <use ID="" REQID="">{1,unbounded}</use>
</uses>
Source
 
<xsd:element name="uses" minOccurs="0" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">This section is made up of one uses element containing one or more use subelements, each describing a single use case. It is primarily envisioned to describe different requirements for METS documents at different points in their project lifecycle with a single profile, connecting a processing action with a specific feature of a METS document. The use element has an optional REQID attribute, which is an IDREF to the ID of a specific <requirement> element declared in the same profile.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="use" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">The use element has an optional head subelement and some available text formatting elements from the xhtml namespace. Available xhtml elements include p, various list/item elements, text formatting such as b and i, a, and img. The latter could be used to embed within the profile documentation such as a diagram of a business process that uses a METS document conforming to the profile.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:complexContent>
            <xsd:extension base="textSection">
              <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
              <xsd:attribute name="REQID" type="xsd:IDREFS" use="optional"/>
            </xsd:extension>
          </xsd:complexContent>
        </xsd:complexType>
      </xsd:element>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / profile_context / uses / use
Namespace http://www.loc.gov/METS_Profile/vNNN
Annotations
 
The use element has an optional head subelement and some available text formatting elements from the xhtml namespace. Available xhtml elements include p, various list/item elements, text formatting such as b and i, a, and img. The latter could be used to embed within the profile documentation such as a diagram of a business process that uses a METS document conforming to the profile.
Diagram
Type extension of textSection
Type hierarchy
Properties
content complex
maxOccurs unbounded
Model
(head{0,1} | p | ul | ol | dl)
Children dl, head, ol, p, ul
Instance
 
<use ID="" REQID="" xmlns="http://www.loc.gov/METS_Profile/vNNN" xmlns:xhtml="http://www.w3.org/1999/xhtml">
  <head ID="" xml:lang="">{0,1}</head>
  <xhtml:p class="" dir="" id="" lang="" xml:lang="" onclick="" ondblclick="" onkeydown="" onkeypress="" onkeyup="" onmousedown="" onmousemove="" onmouseout="" onmouseover="" onmouseup="" style="" title="">{1,1}</xhtml:p>
  <xhtml:ul class="" dir="" id="" lang="" xml:lang="" onclick="" ondblclick="" onkeydown="" onkeypress="" onkeyup="" onmousedown="" onmousemove="" onmouseout="" onmouseover="" onmouseup="" style="" title="">{1,1}</xhtml:ul>
  <xhtml:ol class="" dir="" id="" lang="" xml:lang="" onclick="" ondblclick="" onkeydown="" onkeypress="" onkeyup="" onmousedown="" onmousemove="" onmouseout="" onmouseover="" onmouseup="" style="" title="">{1,1}</xhtml:ol>
  <xhtml:dl class="" dir="" id="" lang="" xml:lang="" onclick="" ondblclick="" onkeydown="" onkeypress="" onkeyup="" onmousedown="" onmousemove="" onmouseout="" onmouseover="" onmouseup="" style="" title="">{1,1}</xhtml:dl>
</use>
Attributes
QName Type Use
ID xsd:ID optional
REQID xsd:IDREFS optional
Source
 
<xsd:element name="use" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The use element has an optional head subelement and some available text formatting elements from the xhtml namespace. Available xhtml elements include p, various list/item elements, text formatting such as b and i, a, and img. The latter could be used to embed within the profile documentation such as a diagram of a business process that uses a METS document conforming to the profile.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:complexContent>
      <xsd:extension base="textSection">
        <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
        <xsd:attribute name="REQID" type="xsd:IDREFS" use="optional"/>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / external_schema
Namespace http://www.loc.gov/METS_Profile/vNNN
Annotations
 
A single external_schema element should used for each external schema listed in the profile. Multiple external_schema elements may be used within a single profile. For each external schema described, you may provide a name of the schema, a URI assigned to the schema, a context description indicating where in a conforming METS document the schema may be used, and an additional note. The note element has an optional head subelement and some available text formatting elements from the xhtml namespace. Available xhtml elements include p, various list/item elements, text formatting such as b and i, a, and img.
Diagram
Properties
content complex
maxOccurs unbounded
Model
Children URL, context, name, note
Instance
 
<external_schema ID="" xmlns="http://www.loc.gov/METS_Profile/vNNN">
  <name ID="" xml:lang="">{0,unbounded}</name>
  <URL ID="" TARGETNAMESPACE="">{0,unbounded}</URL>
  <context ID="" xml:lang="">{0,unbounded}</context>
  <note ID="">{0,1}</note>
</external_schema>
Attributes
QName Type Use
ID xsd:ID optional
Source
 
<xsd:element name="external_schema" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">A single external_schema element should used for each external schema listed in the profile. Multiple external_schema elements may be used within a single profile. For each external schema described, you may provide a name of the schema, a URI assigned to the schema, a context description indicating where in a conforming METS document the schema may be used, and an additional note. The note element has an optional head subelement and some available text formatting elements from the xhtml namespace. Available xhtml elements include p, various list/item elements, text formatting such as b and i, a, and img.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="name" minOccurs="0" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">The external schema name may be repeated if it is available in different languages; use the xml:lang attribute to differentiate.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:simpleContent>
            <xsd:extension base="xsd:string">
              <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
              <xsd:attribute ref="xml:lang" use="optional"/>
            </xsd:extension>
          </xsd:simpleContent>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="URL" minOccurs="0" maxOccurs="unbounded">
        <xsd:complexType>
          <xsd:simpleContent>
            <xsd:extension base="xsd:anyURI">
              <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
              <xsd:attribute name="TARGETNAMESPACE" type="xsd:anyURI" use="optional"/>
            </xsd:extension>
          </xsd:simpleContent>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="context" minOccurs="0" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">The external schema context may be repeated. Use the xml:lang attribute to indicate contexts provided in different languages.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:simpleContent>
            <xsd:extension base="xsd:string">
              <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
              <xsd:attribute ref="xml:lang" use="optional"/>
            </xsd:extension>
          </xsd:simpleContent>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="note" minOccurs="0">
        <xsd:complexType>
          <xsd:complexContent>
            <xsd:extension base="textSection">
              <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
            </xsd:extension>
          </xsd:complexContent>
        </xsd:complexType>
      </xsd:element>
    </xsd:sequence>
    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / external_schema / name
Namespace http://www.loc.gov/METS_Profile/vNNN
Annotations
 
The external schema name may be repeated if it is available in different languages; use the xml:lang attribute to differentiate.
Diagram
Type extension of xsd:string
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
QName Type Use Annotation
ID xsd:ID optional
xml:lang union of(xs:language, restriction of xs:string) optional 
Attempting to install the relevant ISO 2- and 3-letter
         codes as the enumerated possible values is probably never
         going to be a realistic possibility.  See
         RFC 3066 at http://www.ietf.org/rfc/rfc3066.txt and the IANA registry
         at http://www.iana.org/assignments/lang-tag-apps.htm for
         further information.

         The union allows for the 'un-declaration' of xml:lang with
         the empty string.
Source
 
<xsd:element name="name" minOccurs="0" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The external schema name may be repeated if it is available in different languages; use the xml:lang attribute to differentiate.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="xsd:string">
        <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
        <xsd:attribute ref="xml:lang" use="optional"/>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / external_schema / URL
Namespace http://www.loc.gov/METS_Profile/vNNN
Diagram
Type extension of xsd:anyURI
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
QName Type Use
ID xsd:ID optional
TARGETNAMESPACE xsd:anyURI optional
Source
 
<xsd:element name="URL" minOccurs="0" maxOccurs="unbounded">
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="xsd:anyURI">
        <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
        <xsd:attribute name="TARGETNAMESPACE" type="xsd:anyURI" use="optional"/>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / external_schema / context
Namespace http://www.loc.gov/METS_Profile/vNNN
Annotations
 
The external schema context may be repeated.  Use the xml:lang attribute to indicate contexts provided in different languages.
Diagram
Type extension of xsd:string
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
QName Type Use Annotation
ID xsd:ID optional
xml:lang union of(xs:language, restriction of xs:string) optional 
Attempting to install the relevant ISO 2- and 3-letter
         codes as the enumerated possible values is probably never
         going to be a realistic possibility.  See
         RFC 3066 at http://www.ietf.org/rfc/rfc3066.txt and the IANA registry
         at http://www.iana.org/assignments/lang-tag-apps.htm for
         further information.

         The union allows for the 'un-declaration' of xml:lang with
         the empty string.
Source
 
<xsd:element name="context" minOccurs="0" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The external schema context may be repeated. Use the xml:lang attribute to indicate contexts provided in different languages.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="xsd:string">
        <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
        <xsd:attribute ref="xml:lang" use="optional"/>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / external_schema / note
Namespace http://www.loc.gov/METS_Profile/vNNN
Diagram
Type extension of textSection
Type hierarchy
Properties
content complex
minOccurs 0
Model
(head{0,1} | p | ul | ol | dl)
Children dl, head, ol, p, ul
Instance
 
<note ID="" xmlns="http://www.loc.gov/METS_Profile/vNNN" xmlns:xhtml="http://www.w3.org/1999/xhtml">
  <head ID="" xml:lang="">{0,1}</head>
  <xhtml:p class="" dir="" id="" lang="" xml:lang="" onclick="" ondblclick="" onkeydown="" onkeypress="" onkeyup="" onmousedown="" onmousemove="" onmouseout="" onmouseover="" onmouseup="" style="" title="">{1,1}</xhtml:p>
  <xhtml:ul class="" dir="" id="" lang="" xml:lang="" onclick="" ondblclick="" onkeydown="" onkeypress="" onkeyup="" onmousedown="" onmousemove="" onmouseout="" onmouseover="" onmouseup="" style="" title="">{1,1}</xhtml:ul>
  <xhtml:ol class="" dir="" id="" lang="" xml:lang="" onclick="" ondblclick="" onkeydown="" onkeypress="" onkeyup="" onmousedown="" onmousemove="" onmouseout="" onmouseover="" onmouseup="" style="" title="">{1,1}</xhtml:ol>
  <xhtml:dl class="" dir="" id="" lang="" xml:lang="" onclick="" ondblclick="" onkeydown="" onkeypress="" onkeyup="" onmousedown="" onmousemove="" onmouseout="" onmouseover="" onmouseup="" style="" title="">{1,1}</xhtml:dl>
</note>
Attributes
QName Type Use
ID xsd:ID optional
Source
 
<xsd:element name="note" minOccurs="0">
  <xsd:complexType>
    <xsd:complexContent>
      <xsd:extension base="textSection">
        <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / description_rules
Namespace http://www.loc.gov/METS_Profile/vNNN
Annotations
 
An institution may choose to employ particular rules of description when encoding text within elements and attributes of a METS document. For example, a library might decide that descriptive metadata within a <dmdSec><mdWrap> section will be encoded using the Library of Congress' MARC 21 XML Schema MARCXML, and that the content of all elements and attributes within the MARC 21 XML sections must be prepared in accordance with the Anglo-American Cataloguing Rules 2nd Edition AACR2. The Rules of Description portion of a METS profile for that institution's METS objects should indicate that AACR2 must be applied to all content within a MARC 21 XML Schema portion of a METS document conforming to that profile. The description_rules element has an optional head subelement and some available text formatting elements from the xhtml namespace. Available xhtml elements include p, various list/item elements, text formatting such as b and i, a, and img.
Diagram
Type extension of textSection
Type hierarchy
Properties
content complex
Model
(head{0,1} | p | ul | ol | dl)
Children dl, head, ol, p, ul
Instance
 
<description_rules ID="" xmlns="http://www.loc.gov/METS_Profile/vNNN" xmlns:xhtml="http://www.w3.org/1999/xhtml">
  <head ID="" xml:lang="">{0,1}</head>
  <xhtml:p class="" dir="" id="" lang="" xml:lang="" onclick="" ondblclick="" onkeydown="" onkeypress="" onkeyup="" onmousedown="" onmousemove="" onmouseout="" onmouseover="" onmouseup="" style="" title="">{1,1}</xhtml:p>
  <xhtml:ul class="" dir="" id="" lang="" xml:lang="" onclick="" ondblclick="" onkeydown="" onkeypress="" onkeyup="" onmousedown="" onmousemove="" onmouseout="" onmouseover="" onmouseup="" style="" title="">{1,1}</xhtml:ul>
  <xhtml:ol class="" dir="" id="" lang="" xml:lang="" onclick="" ondblclick="" onkeydown="" onkeypress="" onkeyup="" onmousedown="" onmousemove="" onmouseout="" onmouseover="" onmouseup="" style="" title="">{1,1}</xhtml:ol>
  <xhtml:dl class="" dir="" id="" lang="" xml:lang="" onclick="" ondblclick="" onkeydown="" onkeypress="" onkeyup="" onmousedown="" onmousemove="" onmouseout="" onmouseover="" onmouseup="" style="" title="">{1,1}</xhtml:dl>
</description_rules>
Attributes
QName Type Use
ID xsd:ID optional
Source
 
<xsd:element name="description_rules">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">An institution may choose to employ particular rules of description when encoding text within elements and attributes of a METS document. For example, a library might decide that descriptive metadata within a <dmdSec><mdWrap> section will be encoded using the Library of Congress' MARC 21 XML Schema MARCXML, and that the content of all elements and attributes within the MARC 21 XML sections must be prepared in accordance with the Anglo-American Cataloguing Rules 2nd Edition AACR2. The Rules of Description portion of a METS profile for that institution's METS objects should indicate that AACR2 must be applied to all content within a MARC 21 XML Schema portion of a METS document conforming to that profile. The description_rules element has an optional head subelement and some available text formatting elements from the xhtml namespace. Available xhtml elements include p, various list/item elements, text formatting such as b and i, a, and img.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:complexContent>
      <xsd:extension base="textSection">
        <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / controlled_vocabularies
Namespace http://www.loc.gov/METS_Profile/vNNN
Annotations
 
An institution may choose to employ certain controlled vocabularies, such as the Library of Congress Subject Headings or the Getty Thesaurus of Geographic Names, for the content of elements within portions of a METS document. If use of a particular controlled vocabulary is mandatory in any section of a conforming METS document, that controlled vocabulary must be listed in this section of a profile. For all such controlled vocabularies, you should provide a name for the controlled vocabulary, an agency responsible for the vocabulary's maintenance, and a URI assigned to the vocabulary. If you desire, you may also include the individual values/terms within the controlled vocabulary, although it is anticipated that this will only be done when you wish to publicize the contents of a locally-produced controlled vocabulary to others who wish to produce conforming METS documents; there is no need to itemize the contents of well-known controlled vocabularies such as LCSH. For all controlled vocabularies, you should provide contextual information indicating where within a conforming METS document the vocabulary may be used, and if desired brief description of the vocabulary and its purpose. The context and description subelements of vocabulary have an optional head subelement and some available text formatting elements from the xhtml namespace. Available xhtml elements include p, various list/item elements, text formatting such as b and i, a, and img.
Diagram
Properties
content complex
Model
Children vocabulary
Instance
 
<controlled_vocabularies ID="" xmlns="http://www.loc.gov/METS_Profile/vNNN">
  <vocabulary ID="">{0,unbounded}</vocabulary>
</controlled_vocabularies>
Attributes
QName Type Use
ID xsd:ID optional
Source
 
<xsd:element name="controlled_vocabularies">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">An institution may choose to employ certain controlled vocabularies, such as the Library of Congress Subject Headings or the Getty Thesaurus of Geographic Names, for the content of elements within portions of a METS document. If use of a particular controlled vocabulary is mandatory in any section of a conforming METS document, that controlled vocabulary must be listed in this section of a profile. For all such controlled vocabularies, you should provide a name for the controlled vocabulary, an agency responsible for the vocabulary's maintenance, and a URI assigned to the vocabulary. If you desire, you may also include the individual values/terms within the controlled vocabulary, although it is anticipated that this will only be done when you wish to publicize the contents of a locally-produced controlled vocabulary to others who wish to produce conforming METS documents; there is no need to itemize the contents of well-known controlled vocabularies such as LCSH. For all controlled vocabularies, you should provide contextual information indicating where within a conforming METS document the vocabulary may be used, and if desired brief description of the vocabulary and its purpose. The context and description subelements of vocabulary have an optional head subelement and some available text formatting elements from the xhtml namespace. Available xhtml elements include p, various list/item elements, text formatting such as b and i, a, and img.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="vocabulary" minOccurs="0" maxOccurs="unbounded">
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element name="name" minOccurs="0" maxOccurs="unbounded">
              <xsd:annotation>
                <xsd:documentation xml:lang="en">The vocabulary name may be repeated if there are multiple versions of the name in different languages; use the xml:lang attribute to differentiate them.</xsd:documentation>
              </xsd:annotation>
              <xsd:complexType>
                <xsd:simpleContent>
                  <xsd:extension base="xsd:string">
                    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                    <xsd:attribute ref="xml:lang" use="optional"/>
                  </xsd:extension>
                </xsd:simpleContent>
              </xsd:complexType>
            </xsd:element>
            <xsd:element name="maintenance_agency" minOccurs="0">
              <xsd:complexType>
                <xsd:simpleContent>
                  <xsd:extension base="xsd:string">
                    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                  </xsd:extension>
                </xsd:simpleContent>
              </xsd:complexType>
            </xsd:element>
            <xsd:element name="URI" minOccurs="0">
              <xsd:complexType>
                <xsd:simpleContent>
                  <xsd:extension base="xsd:anyURI">
                    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                  </xsd:extension>
                </xsd:simpleContent>
              </xsd:complexType>
            </xsd:element>
            <xsd:element name="values" minOccurs="0">
              <xsd:complexType>
                <xsd:sequence>
                  <xsd:element name="value" maxOccurs="unbounded">
                    <xsd:complexType>
                      <xsd:simpleContent>
                        <xsd:extension base="xsd:string">
                          <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                        </xsd:extension>
                      </xsd:simpleContent>
                    </xsd:complexType>
                  </xsd:element>
                </xsd:sequence>
                <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
              </xsd:complexType>
            </xsd:element>
            <xsd:element name="context" minOccurs="0" maxOccurs="unbounded">
              <xsd:annotation>
                <xsd:documentation xml:lang="en">The vocabulary context may be repeated if there are multiple versions of the context in different languages; use the xml:lang attribute to differentiate them.</xsd:documentation>
              </xsd:annotation>
              <xsd:complexType>
                <xsd:simpleContent>
                  <xsd:extension base="xsd:string">
                    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                    <xsd:attribute ref="xml:lang" use="optional"/>
                  </xsd:extension>
                </xsd:simpleContent>
              </xsd:complexType>
            </xsd:element>
            <xsd:element name="description" minOccurs="0">
              <xsd:complexType>
                <xsd:complexContent>
                  <xsd:extension base="textSection">
                    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                  </xsd:extension>
                </xsd:complexContent>
              </xsd:complexType>
            </xsd:element>
          </xsd:sequence>
          <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
        </xsd:complexType>
      </xsd:element>
    </xsd:sequence>
    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / controlled_vocabularies / vocabulary
Namespace http://www.loc.gov/METS_Profile/vNNN
Diagram
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children URI, context, description, maintenance_agency, name, values
Instance
 
<vocabulary ID="" xmlns="http://www.loc.gov/METS_Profile/vNNN">
  <name ID="" xml:lang="">{0,unbounded}</name>
  <maintenance_agency ID="">{0,1}</maintenance_agency>
  <URI ID="">{0,1}</URI>
  <values ID="">{0,1}</values>
  <context ID="" xml:lang="">{0,unbounded}</context>
  <description ID="">{0,1}</description>
</vocabulary>
Attributes
QName Type Use
ID xsd:ID optional
Source
 
<xsd:element name="vocabulary" minOccurs="0" maxOccurs="unbounded">
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="name" minOccurs="0" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">The vocabulary name may be repeated if there are multiple versions of the name in different languages; use the xml:lang attribute to differentiate them.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:simpleContent>
            <xsd:extension base="xsd:string">
              <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
              <xsd:attribute ref="xml:lang" use="optional"/>
            </xsd:extension>
          </xsd:simpleContent>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="maintenance_agency" minOccurs="0">
        <xsd:complexType>
          <xsd:simpleContent>
            <xsd:extension base="xsd:string">
              <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
            </xsd:extension>
          </xsd:simpleContent>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="URI" minOccurs="0">
        <xsd:complexType>
          <xsd:simpleContent>
            <xsd:extension base="xsd:anyURI">
              <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
            </xsd:extension>
          </xsd:simpleContent>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="values" minOccurs="0">
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element name="value" maxOccurs="unbounded">
              <xsd:complexType>
                <xsd:simpleContent>
                  <xsd:extension base="xsd:string">
                    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                  </xsd:extension>
                </xsd:simpleContent>
              </xsd:complexType>
            </xsd:element>
          </xsd:sequence>
          <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="context" minOccurs="0" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">The vocabulary context may be repeated if there are multiple versions of the context in different languages; use the xml:lang attribute to differentiate them.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:simpleContent>
            <xsd:extension base="xsd:string">
              <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
              <xsd:attribute ref="xml:lang" use="optional"/>
            </xsd:extension>
          </xsd:simpleContent>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="description" minOccurs="0">
        <xsd:complexType>
          <xsd:complexContent>
            <xsd:extension base="textSection">
              <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
            </xsd:extension>
          </xsd:complexContent>
        </xsd:complexType>
      </xsd:element>
    </xsd:sequence>
    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / controlled_vocabularies / vocabulary / name
Namespace http://www.loc.gov/METS_Profile/vNNN
Annotations
 
The vocabulary name may be repeated if there are multiple versions of the name in different languages; use the xml:lang attribute to differentiate them.
Diagram
Type extension of xsd:string
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
QName Type Use Annotation
ID xsd:ID optional
xml:lang union of(xs:language, restriction of xs:string) optional 
Attempting to install the relevant ISO 2- and 3-letter
         codes as the enumerated possible values is probably never
         going to be a realistic possibility.  See
         RFC 3066 at http://www.ietf.org/rfc/rfc3066.txt and the IANA registry
         at http://www.iana.org/assignments/lang-tag-apps.htm for
         further information.

         The union allows for the 'un-declaration' of xml:lang with
         the empty string.
Source
 
<xsd:element name="name" minOccurs="0" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The vocabulary name may be repeated if there are multiple versions of the name in different languages; use the xml:lang attribute to differentiate them.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="xsd:string">
        <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
        <xsd:attribute ref="xml:lang" use="optional"/>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / controlled_vocabularies / vocabulary / maintenance_agency
Namespace http://www.loc.gov/METS_Profile/vNNN
Diagram
Type extension of xsd:string
Properties
content complex
minOccurs 0
Attributes
QName Type Use
ID xsd:ID optional
Source
 
<xsd:element name="maintenance_agency" minOccurs="0">
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="xsd:string">
        <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / controlled_vocabularies / vocabulary / URI
Namespace http://www.loc.gov/METS_Profile/vNNN
Diagram
Type extension of xsd:anyURI
Properties
content complex
minOccurs 0
Attributes
QName Type Use
ID xsd:ID optional
Source
 
<xsd:element name="URI" minOccurs="0">
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="xsd:anyURI">
        <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / controlled_vocabularies / vocabulary / values
Namespace http://www.loc.gov/METS_Profile/vNNN
Diagram
Properties
content complex
minOccurs 0
Model
Children value
Instance
 
<values ID="" xmlns="http://www.loc.gov/METS_Profile/vNNN">
  <value ID="">{1,unbounded}</value>
</values>
Attributes
QName Type Use
ID xsd:ID optional
Source
 
<xsd:element name="values" minOccurs="0">
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="value" maxOccurs="unbounded">
        <xsd:complexType>
          <xsd:simpleContent>
            <xsd:extension base="xsd:string">
              <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
            </xsd:extension>
          </xsd:simpleContent>
        </xsd:complexType>
      </xsd:element>
    </xsd:sequence>
    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / controlled_vocabularies / vocabulary / values / value
Namespace http://www.loc.gov/METS_Profile/vNNN
Diagram
Type extension of xsd:string
Properties
content complex
maxOccurs unbounded
Attributes
QName Type Use
ID xsd:ID optional
Source
 
<xsd:element name="value" maxOccurs="unbounded">
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="xsd:string">
        <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / controlled_vocabularies / vocabulary / context
Namespace http://www.loc.gov/METS_Profile/vNNN
Annotations
 
The vocabulary context may be repeated if there are multiple versions of the context in different languages; use the xml:lang attribute to differentiate them.
Diagram
Type extension of xsd:string
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
QName Type Use Annotation
ID xsd:ID optional
xml:lang union of(xs:language, restriction of xs:string) optional 
Attempting to install the relevant ISO 2- and 3-letter
         codes as the enumerated possible values is probably never
         going to be a realistic possibility.  See
         RFC 3066 at http://www.ietf.org/rfc/rfc3066.txt and the IANA registry
         at http://www.iana.org/assignments/lang-tag-apps.htm for
         further information.

         The union allows for the 'un-declaration' of xml:lang with
         the empty string.
Source
 
<xsd:element name="context" minOccurs="0" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The vocabulary context may be repeated if there are multiple versions of the context in different languages; use the xml:lang attribute to differentiate them.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="xsd:string">
        <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
        <xsd:attribute ref="xml:lang" use="optional"/>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / controlled_vocabularies / vocabulary / description
Namespace http://www.loc.gov/METS_Profile/vNNN
Diagram
Type extension of textSection
Type hierarchy
Properties
content complex
minOccurs 0
Model
(head{0,1} | p | ul | ol | dl)
Children dl, head, ol, p, ul
Instance
 
<description ID="" xmlns="http://www.loc.gov/METS_Profile/vNNN" xmlns:xhtml="http://www.w3.org/1999/xhtml">
  <head ID="" xml:lang="">{0,1}</head>
  <xhtml:p class="" dir="" id="" lang="" xml:lang="" onclick="" ondblclick="" onkeydown="" onkeypress="" onkeyup="" onmousedown="" onmousemove="" onmouseout="" onmouseover="" onmouseup="" style="" title="">{1,1}</xhtml:p>
  <xhtml:ul class="" dir="" id="" lang="" xml:lang="" onclick="" ondblclick="" onkeydown="" onkeypress="" onkeyup="" onmousedown="" onmousemove="" onmouseout="" onmouseover="" onmouseup="" style="" title="">{1,1}</xhtml:ul>
  <xhtml:ol class="" dir="" id="" lang="" xml:lang="" onclick="" ondblclick="" onkeydown="" onkeypress="" onkeyup="" onmousedown="" onmousemove="" onmouseout="" onmouseover="" onmouseup="" style="" title="">{1,1}</xhtml:ol>
  <xhtml:dl class="" dir="" id="" lang="" xml:lang="" onclick="" ondblclick="" onkeydown="" onkeypress="" onkeyup="" onmousedown="" onmousemove="" onmouseout="" onmouseover="" onmouseup="" style="" title="">{1,1}</xhtml:dl>
</description>
Attributes
QName Type Use
ID xsd:ID optional
Source
 
<xsd:element name="description" minOccurs="0">
  <xsd:complexType>
    <xsd:complexContent>
      <xsd:extension base="textSection">
        <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / structural_requirements
Namespace http://www.loc.gov/METS_Profile/vNNN
Annotations
 
The METS document structure is extraordinarily flexible; that flexibility may be problematic inasmuch as creating software to process any arbitrary METS document in any but the most rudimentary way (XML parsing and validation) is a non-trivial task. This task can be simplified to some degree if those creating software to process METS documents know that there are further constraints on the structure of a METS document beyond those of the METS schema itself. The structural requirements portion of a METS profile allows an institution to delineate additional restrictions on the structure of a conforming METS document beyond those specified by the METS format itself. It is permissible to specify restrictions on the structure of a conforming METS document which cannot be validated by standard XML validation tools. For example, it would be a permissible restriction to state that master still images within a METS document should be contained within a separate file group from derivative images. It is impossible to fully delineate the possible additional structural restrictions that institutions may wish to set forth in their profiles, but the following list identifies some major areas of concern that institutions may wish to address in the Structural Requirements portion of a profile: 
--Are there any restrictions on the number of occurrences of elements or attributes set forth in the METS schema beyond those specified by the METS schema itself (e.g., there should only be one occurrence of a dmdSec, every conforming document must include a metsHdr element, etc.)? 
--Are there any restrictions on the number of occurrences of elements or attributes encoded using extension schema beyond those specified by those schema? 
--May extension schema only be used within a particular portion of a METS document (e.g., you may wish to specify that a particular extension schema may be used within a <mdWrap> element within a <techMD> section, but that it should not be used within a <sourceMD> section). 
--Should the structural map conform to a particular model? For instance, a profile for monographs might specify that the root <div> element must have a TYPE attribute of "book", that all immediately subsidiary <div>s have a TYPE attribute of "chapter". Alternatively, it might specify that there be a root <div> with a TYPE attribute of "text" with subsidiary <div>s having a TYPE attribute of "page". Structural metadata is the heart of a METS document, and those creating profiles should try to be as explicit and precise as possible in specifying how structural maps should be created, and may wish to include examples within an appendix to the profile. 
--Should document authors include metadata within a METS document using mdWrap, or reference it using mdRef? Or are both allowable? 
--Should content files be included within a METS document using Fcontent, or referenced using FLocat? Or are both allowable?
The structural_requirements is subdivided into subelements for each major section of a METS document. Requirements pertaining to a particular section should be listed underneath the section of the METS document to which they pertain. If you need to specify a structural requirement that involves more than one major section of the METS document, list it underneath the multiSection subelement within the structural_requirements element. Every subelement within the structural_requirements section is composed
of a sequence of individual requirement elements.
Diagram
Properties
content complex
Model
Children fileSec, mdSec, metsHdr, metsRootElement, multiSection, structSec
Instance
 
<structural_requirements ID="" xmlns="http://www.loc.gov/METS_Profile/vNNN">
  <metsRootElement ID="">{0,1}</metsRootElement>
  <metsHdr ID="">{0,1}</metsHdr>
  <mdSec ID="">{0,1}</mdSec>
  <fileSec ID="">{0,1}</fileSec>
  <structSec ID="">{0,1}</structSec>
  <multiSection ID="">{0,1}</multiSection>
</structural_requirements>
Attributes
QName Type Use
ID xsd:ID optional
Source
 
<xsd:element name="structural_requirements">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The METS document structure is extraordinarily flexible; that flexibility may be problematic inasmuch as creating software to process any arbitrary METS document in any but the most rudimentary way (XML parsing and validation) is a non-trivial task. This task can be simplified to some degree if those creating software to process METS documents know that there are further constraints on the structure of a METS document beyond those of the METS schema itself. The structural requirements portion of a METS profile allows an institution to delineate additional restrictions on the structure of a conforming METS document beyond those specified by the METS format itself. It is permissible to specify restrictions on the structure of a conforming METS document which cannot be validated by standard XML validation tools. For example, it would be a permissible restriction to state that master still images within a METS document should be contained within a separate file group from derivative images. It is impossible to fully delineate the possible additional structural restrictions that institutions may wish to set forth in their profiles, but the following list identifies some major areas of concern that institutions may wish to address in the Structural Requirements portion of a profile: --Are there any restrictions on the number of occurrences of elements or attributes set forth in the METS schema beyond those specified by the METS schema itself (e.g., there should only be one occurrence of a dmdSec, every conforming document must include a metsHdr element, etc.)? --Are there any restrictions on the number of occurrences of elements or attributes encoded using extension schema beyond those specified by those schema? --May extension schema only be used within a particular portion of a METS document (e.g., you may wish to specify that a particular extension schema may be used within a <mdWrap> element within a <techMD> section, but that it should not be used within a <sourceMD> section). --Should the structural map conform to a particular model? For instance, a profile for monographs might specify that the root <div> element must have a TYPE attribute of "book", that all immediately subsidiary <div>s have a TYPE attribute of "chapter". Alternatively, it might specify that there be a root <div> with a TYPE attribute of "text" with subsidiary <div>s having a TYPE attribute of "page". Structural metadata is the heart of a METS document, and those creating profiles should try to be as explicit and precise as possible in specifying how structural maps should be created, and may wish to include examples within an appendix to the profile. --Should document authors include metadata within a METS document using mdWrap, or reference it using mdRef? Or are both allowable? --Should content files be included within a METS document using Fcontent, or referenced using FLocat? Or are both allowable? The structural_requirements is subdivided into subelements for each major section of a METS document. Requirements pertaining to a particular section should be listed underneath the section of the METS document to which they pertain. If you need to specify a structural requirement that involves more than one major section of the METS document, list it underneath the multiSection subelement within the structural_requirements element. Every subelement within the structural_requirements section is composed of a sequence of individual requirement elements.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="metsRootElement" minOccurs="0">
        <xsd:complexType>
          <xsd:complexContent>
            <xsd:extension base="reqs">
              <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
            </xsd:extension>
          </xsd:complexContent>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="metsHdr" minOccurs="0">
        <xsd:complexType>
          <xsd:complexContent>
            <xsd:extension base="reqs">
              <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
            </xsd:extension>
          </xsd:complexContent>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="mdSec" minOccurs="0">
        <xsd:complexType>
          <xsd:complexContent>
            <xsd:extension base="reqs">
              <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
            </xsd:extension>
          </xsd:complexContent>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="fileSec" minOccurs="0">
        <xsd:complexType>
          <xsd:complexContent>
            <xsd:extension base="reqs">
              <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
            </xsd:extension>
          </xsd:complexContent>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="structSec" minOccurs="0">
        <xsd:complexType>
          <xsd:complexContent>
            <xsd:extension base="reqs">
              <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
            </xsd:extension>
          </xsd:complexContent>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="multiSection" minOccurs="0">
        <xsd:complexType>
          <xsd:complexContent>
            <xsd:extension base="reqs">
              <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
            </xsd:extension>
          </xsd:complexContent>
        </xsd:complexType>
      </xsd:element>
    </xsd:sequence>
    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / structural_requirements / metsRootElement
Namespace http://www.loc.gov/METS_Profile/vNNN
Diagram
Type extension of reqs
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children requirement
Instance
 
<metsRootElement ID="" xmlns="http://www.loc.gov/METS_Profile/vNNN">
  <requirement EXAMPLES="" ID="" RELATEDMAT="" REQLEVEL="">{1,unbounded}</requirement>
</metsRootElement>
Attributes
QName Type Use
ID xsd:ID optional
Source
 
<xsd:element name="metsRootElement" minOccurs="0">
  <xsd:complexType>
    <xsd:complexContent>
      <xsd:extension base="reqs">
        <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
</xsd:element>
Element reqs / requirement
Namespace http://www.loc.gov/METS_Profile/vNNN
Annotations
 
The requirement element has four attributes:
1.	an optional XML ID attribute, 
2.	an optional IDREFS attribute called RELATEDMAT, which you may use to indicate other portions of the profile document where this particular requirement is relevant.  Requirement elements are in turn composed of a sequence of paragraph <p> elements,
3.	an optional IDREFS attribute called EXAMPLES, which you may use to point to examples in the <Examples> section that demonstrate the requirement, and
4.	an optional REQLEVEL attribute with values drawn from RFC 2119 (http://www.ietf.org/rfc/rfc2119.txt) .
-----MUST: This word means that the definition is an absolute requirement.
-----SHOULD: This word means that there may exist valid reasons in particular circumstances to ignore the requirement, but the full implications must be understood and carefully weighed before choosing a different course.
-----MUST NOT: This phrase means that the prohibition described in the requirement is an absolute prohibition of the profile.
-----SHOULD NOT: This phrase means that there may exist valid reasons in particular circumstances when violating the prohibition described in the requirement is acceptable or even useful, but the full implications should be understood and the case carefully weighed before doing so. The requirement text should clarify such circumstances.
-----MAY: This word means that an item is not prohibited but fully optional.
The requirement element has two children: description and tests. The required description element has an optional head subelement and some available text formatting elements from the xhtml namespace. Available xhtml elements include p, various list/item elements, text formatting such as b and i, a, and img.
Diagram
Type extension of requirementsType
Type hierarchy
Properties
content complex
maxOccurs unbounded
Model
Children description, tests
Instance
 
<requirement EXAMPLES="" ID="" RELATEDMAT="" REQLEVEL="" xmlns="http://www.loc.gov/METS_Profile/vNNN">
  <description>{1,1}</description>
  <tests ID="">{0,1}</tests>
</requirement>
Attributes
QName Type Use Annotation
EXAMPLES xsd:IDREFS optional
ID xsd:ID optional
RELATEDMAT xsd:IDREFS optional
REQLEVEL restriction of xsd:string optional 
The enumeration values for this element are drawn from RFC 2119 (http://www.ietf.org/rfc/rfc2119.txt).  The definitions provided below are drawn from that source
Source
 
<xsd:element name="requirement" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The requirement element has four attributes: 1. an optional XML ID attribute, 2. an optional IDREFS attribute called RELATEDMAT, which you may use to indicate other portions of the profile document where this particular requirement is relevant. Requirement elements are in turn composed of a sequence of paragraph <p> elements, 3. an optional IDREFS attribute called EXAMPLES, which you may use to point to examples in the <Examples> section that demonstrate the requirement, and 4. an optional REQLEVEL attribute with values drawn from RFC 2119 (http://www.ietf.org/rfc/rfc2119.txt) . -----MUST: This word means that the definition is an absolute requirement. -----SHOULD: This word means that there may exist valid reasons in particular circumstances to ignore the requirement, but the full implications must be understood and carefully weighed before choosing a different course. -----MUST NOT: This phrase means that the prohibition described in the requirement is an absolute prohibition of the profile. -----SHOULD NOT: This phrase means that there may exist valid reasons in particular circumstances when violating the prohibition described in the requirement is acceptable or even useful, but the full implications should be understood and the case carefully weighed before doing so. The requirement text should clarify such circumstances. -----MAY: This word means that an item is not prohibited but fully optional. The requirement element has two children: description and tests. The required description element has an optional head subelement and some available text formatting elements from the xhtml namespace. Available xhtml elements include p, various list/item elements, text formatting such as b and i, a, and img.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:complexContent>
      <xsd:extension base="requirementsType">
        <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
        <xsd:attribute name="RELATEDMAT" type="xsd:IDREFS" use="optional"/>
        <xsd:attribute name="EXAMPLES" type="xsd:IDREFS" use="optional"/>
        <xsd:attribute name="REQLEVEL" use="optional">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">The enumeration values for this element are drawn from RFC 2119 (http://www.ietf.org/rfc/rfc2119.txt). The definitions provided below are drawn from that source</xsd:documentation>
          </xsd:annotation>
          <xsd:simpleType>
            <xsd:restriction base="xsd:string">
              <xsd:enumeration value="MUST">
                <xsd:annotation>
                  <xsd:documentation xml:lang="en">This word means that the definition is an absolute requirement.</xsd:documentation>
                </xsd:annotation>
              </xsd:enumeration>
              <xsd:enumeration value="SHOULD">
                <xsd:annotation>
                  <xsd:documentation xml:lang="en">This word means that there may exist valid reasons in particular circumstances to ignore the requirement, but the full implications must be understood and carefully weighed before choosing a different course.</xsd:documentation>
                </xsd:annotation>
              </xsd:enumeration>
              <xsd:enumeration value="MUST NOT">
                <xsd:annotation>
                  <xsd:documentation xml:lang="en">This phrase means that the prohibition described in the requirement is an absolute prohibition of the profile.</xsd:documentation>
                </xsd:annotation>
              </xsd:enumeration>
              <xsd:enumeration value="SHOULD NOT">
                <xsd:annotation>
                  <xsd:documentation xml:lang="en">This phrase means that there may exist valid reasons in particular circumstances when violating the prohibition described in the requirement is acceptable or even useful, but the full implications should be understood and the case carefully weighed before doing so. The requirement text should clarify such circumstances.</xsd:documentation>
                </xsd:annotation>
              </xsd:enumeration>
              <xsd:enumeration value="MAY">
                <xsd:annotation>
                  <xsd:documentation xml:lang="en">This word means that an item is not prohibited but fully optional.</xsd:documentation>
                </xsd:annotation>
              </xsd:enumeration>
            </xsd:restriction>
          </xsd:simpleType>
        </xsd:attribute>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
</xsd:element>
Element requirementsType / description
Namespace http://www.loc.gov/METS_Profile/vNNN
Diagram
Type textSection
Properties
content complex
minOccurs 1
Model
(head{0,1} | p | ul | ol | dl)
Children dl, head, ol, p, ul
Instance
 
<description xmlns="http://www.loc.gov/METS_Profile/vNNN" xmlns:xhtml="http://www.w3.org/1999/xhtml">
  <head ID="" xml:lang="">{0,1}</head>
  <xhtml:p class="" dir="" id="" lang="" xml:lang="" onclick="" ondblclick="" onkeydown="" onkeypress="" onkeyup="" onmousedown="" onmousemove="" onmouseout="" onmouseover="" onmouseup="" style="" title="">{1,1}</xhtml:p>
  <xhtml:ul class="" dir="" id="" lang="" xml:lang="" onclick="" ondblclick="" onkeydown="" onkeypress="" onkeyup="" onmousedown="" onmousemove="" onmouseout="" onmouseover="" onmouseup="" style="" title="">{1,1}</xhtml:ul>
  <xhtml:ol class="" dir="" id="" lang="" xml:lang="" onclick="" ondblclick="" onkeydown="" onkeypress="" onkeyup="" onmousedown="" onmousemove="" onmouseout="" onmouseover="" onmouseup="" style="" title="">{1,1}</xhtml:ol>
  <xhtml:dl class="" dir="" id="" lang="" xml:lang="" onclick="" ondblclick="" onkeydown="" onkeypress="" onkeyup="" onmousedown="" onmousemove="" onmouseout="" onmouseover="" onmouseup="" style="" title="">{1,1}</xhtml:dl>
</description>
Source
 
<xsd:element name="description" type="textSection" minOccurs="1"/>
Element requirementsType / tests
Namespace http://www.loc.gov/METS_Profile/vNNN
Annotations
 
The optional tests subelement of description exists to supplement a textual description of a requirement with one that can be used to eventually provide machine validation. It includes one or more testGrp elements, which in turn contain testWrap or testRep elements. It is assumed each test’s desired outcome is to evaluate to "true." Implementers must ensure that the requirement level indicated and any formal test evaluation pattern are aligned so that the test indicates conformance rather than an error.
Diagram
Properties
content complex
minOccurs 0
Model
Children test
Instance
 
<tests ID="" xmlns="http://www.loc.gov/METS_Profile/vNNN">
  <test ID="" LABEL="" TESTLANGUAGE="" TESTLANGUAGEURI="" TESTLANGUAGEVERSION="">{1,unbounded}</test>
</tests>
Attributes
QName Type Use
ID xsd:ID optional
Source
 
<xsd:element name="tests" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The optional tests subelement of description exists to supplement a textual description of a requirement with one that can be used to eventually provide machine validation. It includes one or more testGrp elements, which in turn contain testWrap or testRep elements. It is assumed each test’s desired outcome is to evaluate to "true." Implementers must ensure that the requirement level indicated and any formal test evaluation pattern are aligned so that the test indicates conformance rather than an error.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="test" minOccurs="1" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">The test element contains the following attributes: 1. ID: an optional attribute uniquely identifying this element within the METS Profile document 2. LABEL: an optional textual description of the test being performed 3. TESTLANGUAGE: a required attribute indicating the language in which the test is expressed, such as XPath or XQuery 4. TESTLANGUAGEVERSION: an optional attribute indicating what version of the testing language has been used 5. TESTLANGUAGEURI: an optional attribute indicating an authoritative URI for the testing language used</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:choice>
            <xsd:element name="testString">
              <xsd:complexType>
                <xsd:simpleContent>
                  <xsd:extension base="xsd:string">
                    <xsd:attribute name="CONTEXT" type="xsd:string" use="optional"/>
                    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                  </xsd:extension>
                </xsd:simpleContent>
              </xsd:complexType>
            </xsd:element>
            <xsd:element name="testWrap">
              <xsd:annotation>
                <xsd:documentation xml:lang="en">The testWrap element has a test subelement with an optional CONTEXT attribute used to indicate the context in which a test should be evaluated. The value of the text element should be the actual text expression in the selected testing language.</xsd:documentation>
              </xsd:annotation>
              <xsd:complexType>
                <xsd:choice>
                  <xsd:element name="testBin">
                    <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:complexType>
                      <xsd:simpleContent>
                        <xsd:extension base="xsd:base64Binary">
                          <xsd:attribute name="CONTEXT" type="xsd:string" use="optional"/>
                          <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                        </xsd:extension>
                      </xsd:simpleContent>
                    </xsd:complexType>
                  </xsd:element>
                  <xsd:element name="testXML">
                    <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:attribute name="CONTEXT" type="xsd:string" use="optional"/>
                      <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                    </xsd:complexType>
                  </xsd:element>
                </xsd:choice>
                <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
              </xsd:complexType>
            </xsd:element>
            <xsd:element name="testRef">
              <xsd:annotation>
                <xsd:documentation xml:lang="en">The testRef element is intended to point to testing code stored elsewhere. It contains a LOCREF attribute to point to this testing code. When using testing code not easily embedded inside the METS Profile, such as that written in Perl, testRef is preferred over testWrap.</xsd:documentation>
              </xsd:annotation>
              <xsd:complexType>
                <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                <xsd:attribute name="LOCREF" type="xsd:string" use="required"/>
                <xsd:attribute name="LOCTYPE" type="xsd:string" use="required"/>
              </xsd:complexType>
            </xsd:element>
          </xsd:choice>
          <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
          <xsd:attribute name="LABEL" type="xsd:string" use="optional"/>
          <xsd:attribute name="TESTLANGUAGE" type="xsd:string" use="required"/>
          <xsd:attribute name="TESTLANGUAGEVERSION" type="xsd:string"/>
          <xsd:attribute name="TESTLANGUAGEURI" type="xsd:anyURI"/>
        </xsd:complexType>
      </xsd:element>
    </xsd:sequence>
    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
  </xsd:complexType>
</xsd:element>
Element requirementsType / tests / test
Namespace http://www.loc.gov/METS_Profile/vNNN
Annotations
 
The test element contains the following attributes:
1.	ID: an optional attribute uniquely identifying this element within the METS Profile document
2.	LABEL: an optional textual description of the test being performed
3.	TESTLANGUAGE: a required attribute indicating the language in which the test is expressed, such as XPath or XQuery
4.	TESTLANGUAGEVERSION: an optional attribute indicating what version of the testing language has been used
5.	TESTLANGUAGEURI: an optional attribute indicating an authoritative URI for the testing language used
Diagram
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children testRef, testString, testWrap
Instance
 
<test ID="" LABEL="" TESTLANGUAGE="" TESTLANGUAGEURI="" TESTLANGUAGEVERSION="" xmlns="http://www.loc.gov/METS_Profile/vNNN">
  <testString CONTEXT="" ID="">{1,1}</testString>
  <testWrap ID="">{1,1}</testWrap>
  <testRef ID="" LOCREF="" LOCTYPE="">{1,1}</testRef>
</test>
Attributes
QName Type Use
ID xsd:ID optional
LABEL xsd:string optional
TESTLANGUAGE xsd:string required
TESTLANGUAGEURI xsd:anyURI optional
TESTLANGUAGEVERSION xsd:string optional
Source
 
<xsd:element name="test" minOccurs="1" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The test element contains the following attributes: 1. ID: an optional attribute uniquely identifying this element within the METS Profile document 2. LABEL: an optional textual description of the test being performed 3. TESTLANGUAGE: a required attribute indicating the language in which the test is expressed, such as XPath or XQuery 4. TESTLANGUAGEVERSION: an optional attribute indicating what version of the testing language has been used 5. TESTLANGUAGEURI: an optional attribute indicating an authoritative URI for the testing language used</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:choice>
      <xsd:element name="testString">
        <xsd:complexType>
          <xsd:simpleContent>
            <xsd:extension base="xsd:string">
              <xsd:attribute name="CONTEXT" type="xsd:string" use="optional"/>
              <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
            </xsd:extension>
          </xsd:simpleContent>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="testWrap">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">The testWrap element has a test subelement with an optional CONTEXT attribute used to indicate the context in which a test should be evaluated. The value of the text element should be the actual text expression in the selected testing language.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:choice>
            <xsd:element name="testBin">
              <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:complexType>
                <xsd:simpleContent>
                  <xsd:extension base="xsd:base64Binary">
                    <xsd:attribute name="CONTEXT" type="xsd:string" use="optional"/>
                    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                  </xsd:extension>
                </xsd:simpleContent>
              </xsd:complexType>
            </xsd:element>
            <xsd:element name="testXML">
              <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:attribute name="CONTEXT" type="xsd:string" use="optional"/>
                <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
              </xsd:complexType>
            </xsd:element>
          </xsd:choice>
          <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="testRef">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">The testRef element is intended to point to testing code stored elsewhere. It contains a LOCREF attribute to point to this testing code. When using testing code not easily embedded inside the METS Profile, such as that written in Perl, testRef is preferred over testWrap.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
          <xsd:attribute name="LOCREF" type="xsd:string" use="required"/>
          <xsd:attribute name="LOCTYPE" type="xsd:string" use="required"/>
        </xsd:complexType>
      </xsd:element>
    </xsd:choice>
    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
    <xsd:attribute name="LABEL" type="xsd:string" use="optional"/>
    <xsd:attribute name="TESTLANGUAGE" type="xsd:string" use="required"/>
    <xsd:attribute name="TESTLANGUAGEVERSION" type="xsd:string"/>
    <xsd:attribute name="TESTLANGUAGEURI" type="xsd:anyURI"/>
  </xsd:complexType>
</xsd:element>
Element requirementsType / tests / test / testString
Namespace http://www.loc.gov/METS_Profile/vNNN
Diagram
Type extension of xsd:string
Properties
content complex
Attributes
QName Type Use
CONTEXT xsd:string optional
ID xsd:ID optional
Source
 
<xsd:element name="testString">
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="xsd:string">
        <xsd:attribute name="CONTEXT" type="xsd:string" use="optional"/>
        <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
Element requirementsType / tests / test / testWrap
Namespace http://www.loc.gov/METS_Profile/vNNN
Annotations
 
The testWrap element has a test subelement with an optional CONTEXT attribute used to indicate the context in which a test should be evaluated. The value of the text element should be the actual text expression in the selected testing language.
Diagram
Properties
content complex
Model
Children testBin, testXML
Instance
 
<testWrap ID="" xmlns="http://www.loc.gov/METS_Profile/vNNN">
  <testBin CONTEXT="" ID="">{1,1}</testBin>
  <testXML CONTEXT="" ID="">{1,1}</testXML>
</testWrap>
Attributes
QName Type Use
ID xsd:ID optional
Source
 
<xsd:element name="testWrap">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The testWrap element has a test subelement with an optional CONTEXT attribute used to indicate the context in which a test should be evaluated. The value of the text element should be the actual text expression in the selected testing language.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:choice>
      <xsd:element name="testBin">
        <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:complexType>
          <xsd:simpleContent>
            <xsd:extension base="xsd:base64Binary">
              <xsd:attribute name="CONTEXT" type="xsd:string" use="optional"/>
              <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
            </xsd:extension>
          </xsd:simpleContent>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="testXML">
        <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:attribute name="CONTEXT" type="xsd:string" use="optional"/>
          <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
        </xsd:complexType>
      </xsd:element>
    </xsd:choice>
    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
  </xsd:complexType>
</xsd:element>
Element requirementsType / tests / test / testWrap / testBin
Namespace http://www.loc.gov/METS_Profile/vNNN
Annotations
 
A binary data wrapper element <binData> is used to contain a Base64 encoded file.
Diagram
Type extension of xsd:base64Binary
Properties
content complex
Attributes
QName Type Use
CONTEXT xsd:string optional
ID xsd:ID optional
Source
 
<xsd:element name="testBin">
  <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:complexType>
    <xsd:simpleContent>
      <xsd:extension base="xsd:base64Binary">
        <xsd:attribute name="CONTEXT" type="xsd:string" use="optional"/>
        <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
Element requirementsType / tests / test / testWrap / testXML
Namespace http://www.loc.gov/METS_Profile/vNNN
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
Model
ANY element from ANY namespace
Attributes
QName Type Use
CONTEXT xsd:string optional
ID xsd:ID optional
Source
 
<xsd:element name="testXML">
  <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:attribute name="CONTEXT" type="xsd:string" use="optional"/>
    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
  </xsd:complexType>
</xsd:element>
Element requirementsType / tests / test / testRef
Namespace http://www.loc.gov/METS_Profile/vNNN
Annotations
 
The testRef element is intended to point to testing code stored elsewhere. It contains a LOCREF attribute to point to this testing code. When using testing code not easily embedded inside the METS Profile, such as that written in Perl, testRef is preferred over testWrap.
Diagram
Properties
content complex
Attributes
QName Type Use
ID xsd:ID optional
LOCREF xsd:string required
LOCTYPE xsd:string required
Source
 
<xsd:element name="testRef">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The testRef element is intended to point to testing code stored elsewhere. It contains a LOCREF attribute to point to this testing code. When using testing code not easily embedded inside the METS Profile, such as that written in Perl, testRef is preferred over testWrap.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
    <xsd:attribute name="LOCREF" type="xsd:string" use="required"/>
    <xsd:attribute name="LOCTYPE" type="xsd:string" use="required"/>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / structural_requirements / metsHdr
Namespace http://www.loc.gov/METS_Profile/vNNN
Diagram
Type extension of reqs
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children requirement
Instance
 
<metsHdr ID="" xmlns="http://www.loc.gov/METS_Profile/vNNN">
  <requirement EXAMPLES="" ID="" RELATEDMAT="" REQLEVEL="">{1,unbounded}</requirement>
</metsHdr>
Attributes
QName Type Use
ID xsd:ID optional
Source
 
<xsd:element name="metsHdr" minOccurs="0">
  <xsd:complexType>
    <xsd:complexContent>
      <xsd:extension base="reqs">
        <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / structural_requirements / mdSec
Namespace http://www.loc.gov/METS_Profile/vNNN
Diagram
Type extension of reqs
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children requirement
Instance
 
<mdSec ID="" xmlns="http://www.loc.gov/METS_Profile/vNNN">
  <requirement EXAMPLES="" ID="" RELATEDMAT="" REQLEVEL="">{1,unbounded}</requirement>
</mdSec>
Attributes
QName Type Use
ID xsd:ID optional
Source
 
<xsd:element name="mdSec" minOccurs="0">
  <xsd:complexType>
    <xsd:complexContent>
      <xsd:extension base="reqs">
        <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / structural_requirements / fileSec
Namespace http://www.loc.gov/METS_Profile/vNNN
Diagram
Type extension of reqs
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children requirement
Instance
 
<fileSec ID="" xmlns="http://www.loc.gov/METS_Profile/vNNN">
  <requirement EXAMPLES="" ID="" RELATEDMAT="" REQLEVEL="">{1,unbounded}</requirement>
</fileSec>
Attributes
QName Type Use
ID xsd:ID optional
Source
 
<xsd:element name="fileSec" minOccurs="0">
  <xsd:complexType>
    <xsd:complexContent>
      <xsd:extension base="reqs">
        <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / structural_requirements / structSec
Namespace http://www.loc.gov/METS_Profile/vNNN
Diagram
Type extension of reqs
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children requirement
Instance
 
<structSec ID="" xmlns="http://www.loc.gov/METS_Profile/vNNN">
  <requirement EXAMPLES="" ID="" RELATEDMAT="" REQLEVEL="">{1,unbounded}</requirement>
</structSec>
Attributes
QName Type Use
ID xsd:ID optional
Source
 
<xsd:element name="structSec" minOccurs="0">
  <xsd:complexType>
    <xsd:complexContent>
      <xsd:extension base="reqs">
        <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / structural_requirements / multiSection
Namespace http://www.loc.gov/METS_Profile/vNNN
Diagram
Type extension of reqs
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children requirement
Instance
 
<multiSection ID="" xmlns="http://www.loc.gov/METS_Profile/vNNN">
  <requirement EXAMPLES="" ID="" RELATEDMAT="" REQLEVEL="">{1,unbounded}</requirement>
</multiSection>
Attributes
QName Type Use
ID xsd:ID optional
Source
 
<xsd:element name="multiSection" minOccurs="0">
  <xsd:complexType>
    <xsd:complexContent>
      <xsd:extension base="reqs">
        <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / technical_requirements
Namespace http://www.loc.gov/METS_Profile/vNNN
Annotations
 
A METS document may reference a variety of external files, including the content files for the METS object (via <FLocat>elements), executable behaviors (via the <mechanism> element), and external metadata files (via <mdRef> elements). Non-XML content and metadata files may also be embedded within a METS instance, if they have been Base64 encoded. Institutions may wish to place restrictions on the nature of these external and non-XML files, such as insisting that all image files be in the TIFF 6.0 format and have a bit-depth between 16 and 32 bits, or that references to external metadata identified as being of type "MARC" via the MDTYPE attribute will point to MARC records conforming to the MARC 21 standard (or alternatively, to an HTML display of a MARC 21 record). 
The Technical Requirements section of a profile allows institutions to set forth the full set of restrictions on the technical nature of files which may be referenced from a conforming METS document. It is subdivided into sections for restrictions on content files, restrictions on behavior files, and restrictions on metadata files. Profile authors should bear in mind that one of the primary purposes of the Technical Requirements section is to allow software developers to anticipate what types of content will be accessible via links from the METS objects, and hence what software is needed to process that content. 
Every subelement within the technical_requirements section is composed of a sequence of individual requirement elements.
Diagram
Properties
content complex
Model
Children content_files, metadata_files
Instance
 
<technical_requirements ID="" xmlns="http://www.loc.gov/METS_Profile/vNNN">
  <content_files ID="">{0,1}</content_files>
  <metadata_files ID="">{0,1}</metadata_files>
</technical_requirements>
Attributes
QName Type Use
ID xsd:ID optional
Source
 
<xsd:element name="technical_requirements">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">A METS document may reference a variety of external files, including the content files for the METS object (via <FLocat>elements), executable behaviors (via the <mechanism> element), and external metadata files (via <mdRef> elements). Non-XML content and metadata files may also be embedded within a METS instance, if they have been Base64 encoded. Institutions may wish to place restrictions on the nature of these external and non-XML files, such as insisting that all image files be in the TIFF 6.0 format and have a bit-depth between 16 and 32 bits, or that references to external metadata identified as being of type "MARC" via the MDTYPE attribute will point to MARC records conforming to the MARC 21 standard (or alternatively, to an HTML display of a MARC 21 record). The Technical Requirements section of a profile allows institutions to set forth the full set of restrictions on the technical nature of files which may be referenced from a conforming METS document. It is subdivided into sections for restrictions on content files, restrictions on behavior files, and restrictions on metadata files. Profile authors should bear in mind that one of the primary purposes of the Technical Requirements section is to allow software developers to anticipate what types of content will be accessible via links from the METS objects, and hence what software is needed to process that content. Every subelement within the technical_requirements section is composed of a sequence of individual requirement elements.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="content_files" minOccurs="0">
        <xsd:complexType>
          <xsd:complexContent>
            <xsd:extension base="reqs">
              <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
            </xsd:extension>
          </xsd:complexContent>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="metadata_files" minOccurs="0">
        <xsd:complexType>
          <xsd:complexContent>
            <xsd:extension base="reqs">
              <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
            </xsd:extension>
          </xsd:complexContent>
        </xsd:complexType>
      </xsd:element>
    </xsd:sequence>
    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / technical_requirements / content_files
Namespace http://www.loc.gov/METS_Profile/vNNN
Diagram
Type extension of reqs
Type hierarchy
Properties
content complex
minOccurs 0
Model
requirement+
Children requirement
Instance
 
<content_files ID="" xmlns="http://www.loc.gov/METS_Profile/vNNN">
  <requirement EXAMPLES="" ID="" RELATEDMAT="" REQLEVEL="">{1,unbounded}</requirement>
</content_files>
Attributes
QName Type Use
ID xsd:ID optional
Source
 
<xsd:element name="content_files" minOccurs="0">
  <xsd:complexType>
    <xsd:complexContent>
      <xsd:extension base="reqs">
        <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / technical_requirements / metadata_files
Namespace http://www.loc.gov/METS_Profile/vNNN
Diagram
Type extension of reqs
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children requirement
Instance
 
<metadata_files ID="" xmlns="http://www.loc.gov/METS_Profile/vNNN">
  <requirement EXAMPLES="" ID="" RELATEDMAT="" REQLEVEL="">{1,unbounded}</requirement>
</metadata_files>
Attributes
QName Type Use
ID xsd:ID optional
Source
 
<xsd:element name="metadata_files" minOccurs="0">
  <xsd:complexType>
    <xsd:complexContent>
      <xsd:extension base="reqs">
        <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / tool
Namespace http://www.loc.gov/METS_Profile/vNNN
Annotations
 
A profile should provide a description of any affiliated tools, including validators, stylesheets, authoring tools, rendering applications, which can or should be used with METS documents conforming to the profile. The description should provide a name for the tool, the agency responsible for its development, a description of the tool, and a URI for obtaining the tool or further information regarding it. The description and note subelments of tool have an optional head subelement and some available text formatting elements from the xhtml namespace. Available xhtml elements include p, various list/item elements, text formatting such as b and i, a, and img.
Diagram
Properties
content complex
maxOccurs unbounded
Model
Children URI, agency, description, name, note
Instance
 
<tool ID="" xmlns="http://www.loc.gov/METS_Profile/vNNN">
  <name ID="" xml:lang="">{0,unbounded}</name>
  <agency ID="">{0,1}</agency>
  <URI ID="">{0,unbounded}</URI>
  <description ID="">{0,1}</description>
  <note ID="">{0,1}</note>
</tool>
Attributes
QName Type Use
ID xsd:ID optional
Source
 
<xsd:element name="tool" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">A profile should provide a description of any affiliated tools, including validators, stylesheets, authoring tools, rendering applications, which can or should be used with METS documents conforming to the profile. The description should provide a name for the tool, the agency responsible for its development, a description of the tool, and a URI for obtaining the tool or further information regarding it. The description and note subelments of tool have an optional head subelement and some available text formatting elements from the xhtml namespace. Available xhtml elements include p, various list/item elements, text formatting such as b and i, a, and img.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="name" minOccurs="0" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">The tool name may be repeated if there are multiple versions of the name in different languages; use the xml:lang attribute to differentiate them.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:simpleContent>
            <xsd:extension base="xsd:string">
              <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
              <xsd:attribute ref="xml:lang" use="optional"/>
            </xsd:extension>
          </xsd:simpleContent>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="agency" minOccurs="0">
        <xsd:complexType>
          <xsd:simpleContent>
            <xsd:extension base="xsd:string">
              <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
            </xsd:extension>
          </xsd:simpleContent>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="URI" minOccurs="0" maxOccurs="unbounded">
        <xsd:complexType>
          <xsd:simpleContent>
            <xsd:extension base="xsd:anyURI">
              <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
            </xsd:extension>
          </xsd:simpleContent>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="description" minOccurs="0">
        <xsd:complexType>
          <xsd:complexContent>
            <xsd:extension base="textSection">
              <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
            </xsd:extension>
          </xsd:complexContent>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="note" minOccurs="0">
        <xsd:complexType>
          <xsd:complexContent>
            <xsd:extension base="textSection">
              <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
            </xsd:extension>
          </xsd:complexContent>
        </xsd:complexType>
      </xsd:element>
    </xsd:sequence>
    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / tool / name
Namespace http://www.loc.gov/METS_Profile/vNNN
Annotations
 
The tool name may be repeated if there are multiple versions of the name in different languages; use the xml:lang attribute to differentiate them.
Diagram
Type extension of xsd:string
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
QName Type Use Annotation
ID xsd:ID optional
xml:lang union of(xs:language, restriction of xs:string) optional 
Attempting to install the relevant ISO 2- and 3-letter
         codes as the enumerated possible values is probably never
         going to be a realistic possibility.  See
         RFC 3066 at http://www.ietf.org/rfc/rfc3066.txt and the IANA registry
         at http://www.iana.org/assignments/lang-tag-apps.htm for
         further information.

         The union allows for the 'un-declaration' of xml:lang with
         the empty string.
Source
 
<xsd:element name="name" minOccurs="0" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The tool name may be repeated if there are multiple versions of the name in different languages; use the xml:lang attribute to differentiate them.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="xsd:string">
        <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
        <xsd:attribute ref="xml:lang" use="optional"/>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / tool / agency
Namespace http://www.loc.gov/METS_Profile/vNNN
Diagram
Type extension of xsd:string
Properties
content complex
minOccurs 0
Attributes
QName Type Use
ID xsd:ID optional
Source
 
<xsd:element name="agency" minOccurs="0">
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="xsd:string">
        <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / tool / URI
Namespace http://www.loc.gov/METS_Profile/vNNN
Diagram
Type extension of xsd:anyURI
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
QName Type Use
ID xsd:ID optional
Source
 
<xsd:element name="URI" minOccurs="0" maxOccurs="unbounded">
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="xsd:anyURI">
        <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / tool / description
Namespace http://www.loc.gov/METS_Profile/vNNN
Diagram
Type extension of textSection
Type hierarchy
Properties
content complex
minOccurs 0
Model
(head{0,1} | p | ul | ol | dl)
Children dl, head, ol, p, ul
Instance
 
<description ID="" xmlns="http://www.loc.gov/METS_Profile/vNNN" xmlns:xhtml="http://www.w3.org/1999/xhtml">
  <head ID="" xml:lang="">{0,1}</head>
  <xhtml:p class="" dir="" id="" lang="" xml:lang="" onclick="" ondblclick="" onkeydown="" onkeypress="" onkeyup="" onmousedown="" onmousemove="" onmouseout="" onmouseover="" onmouseup="" style="" title="">{1,1}</xhtml:p>
  <xhtml:ul class="" dir="" id="" lang="" xml:lang="" onclick="" ondblclick="" onkeydown="" onkeypress="" onkeyup="" onmousedown="" onmousemove="" onmouseout="" onmouseover="" onmouseup="" style="" title="">{1,1}</xhtml:ul>
  <xhtml:ol class="" dir="" id="" lang="" xml:lang="" onclick="" ondblclick="" onkeydown="" onkeypress="" onkeyup="" onmousedown="" onmousemove="" onmouseout="" onmouseover="" onmouseup="" style="" title="">{1,1}</xhtml:ol>
  <xhtml:dl class="" dir="" id="" lang="" xml:lang="" onclick="" ondblclick="" onkeydown="" onkeypress="" onkeyup="" onmousedown="" onmousemove="" onmouseout="" onmouseover="" onmouseup="" style="" title="">{1,1}</xhtml:dl>
</description>
Attributes
QName Type Use
ID xsd:ID optional
Source
 
<xsd:element name="description" minOccurs="0">
  <xsd:complexType>
    <xsd:complexContent>
      <xsd:extension base="textSection">
        <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / tool / note
Namespace http://www.loc.gov/METS_Profile/vNNN
Diagram
Type extension of textSection
Type hierarchy
Properties
content complex
minOccurs 0
Model
(head{0,1} | p | ul | ol | dl)
Children dl, head, ol, p, ul
Instance
 
<note ID="" xmlns="http://www.loc.gov/METS_Profile/vNNN" xmlns:xhtml="http://www.w3.org/1999/xhtml">
  <head ID="" xml:lang="">{0,1}</head>
  <xhtml:p class="" dir="" id="" lang="" xml:lang="" onclick="" ondblclick="" onkeydown="" onkeypress="" onkeyup="" onmousedown="" onmousemove="" onmouseout="" onmouseover="" onmouseup="" style="" title="">{1,1}</xhtml:p>
  <xhtml:ul class="" dir="" id="" lang="" xml:lang="" onclick="" ondblclick="" onkeydown="" onkeypress="" onkeyup="" onmousedown="" onmousemove="" onmouseout="" onmouseover="" onmouseup="" style="" title="">{1,1}</xhtml:ul>
  <xhtml:ol class="" dir="" id="" lang="" xml:lang="" onclick="" ondblclick="" onkeydown="" onkeypress="" onkeyup="" onmousedown="" onmousemove="" onmouseout="" onmouseover="" onmouseup="" style="" title="">{1,1}</xhtml:ol>
  <xhtml:dl class="" dir="" id="" lang="" xml:lang="" onclick="" ondblclick="" onkeydown="" onkeypress="" onkeyup="" onmousedown="" onmousemove="" onmouseout="" onmouseover="" onmouseup="" style="" title="">{1,1}</xhtml:dl>
</note>
Attributes
QName Type Use
ID xsd:ID optional
Source
 
<xsd:element name="note" minOccurs="0">
  <xsd:complexType>
    <xsd:complexContent>
      <xsd:extension base="textSection">
        <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / Example
Namespace http://www.loc.gov/METS_Profile/vNNN
Annotations
 
A METS profile may contain one or more Example elements.  Unlike Appendix elements, which are expected to contain complete METS encodings, an Example element would contain just a code snippet intended to demonstrate some requirement of the profile. The data type of the Examples element allows for partial, well-formed encodings that still might not satisfy all of the requirements for a full METS encoding.  
A requirement can link to one or more Example elements by referencing the ID value of the pertinent Example elements in its EXAMPLES attribute. 
The Example element has two attributes: 
1.	ID.  This attribute is required, as every Example should be linked to from the requirement of which it is an example.  
2.	LABEL.  This optional attribute allows for the descriptive labeling of an example.
Diagram
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
ANY element from ANY namespace
Attributes
QName Type Use
ID xsd:ID required
LABEL xsd:string optional
Source
 
<xsd:element name="Example" minOccurs="0" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">A METS profile may contain one or more Example elements. Unlike Appendix elements, which are expected to contain complete METS encodings, an Example element would contain just a code snippet intended to demonstrate some requirement of the profile. The data type of the Examples element allows for partial, well-formed encodings that still might not satisfy all of the requirements for a full METS encoding. A requirement can link to one or more Example elements by referencing the ID value of the pertinent Example elements in its EXAMPLES attribute. The Example element has two attributes: 1. ID. This attribute is required, as every Example should be linked to from the requirement of which it is an example. 2. LABEL. This optional attribute allows for the descriptive labeling of an example.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:any namespace="##any" maxOccurs="unbounded" processContents="skip"/>
    </xsd:sequence>
    <xsd:attribute name="ID" type="xsd:ID" use="required"/>
    <xsd:attribute name="LABEL" type="xsd:string" use="optional"/>
  </xsd:complexType>
</xsd:element>
Element METS_Profile / Appendix
Namespace http://www.loc.gov/METS_Profile/vNNN
Annotations
 
A profile must contain an appendix containing an example METS document which conforms to the requirements set out in the profile. Profile authors should note that in order to insure that the completed profile document is valid, any namespace and schemaLocation declarations contained in the root <mets> element should be moved to the root <METS_Profile> element.
Diagram
Properties
content complex
maxOccurs unbounded
Model
ANY element from ANY namespace
Attributes
QName Type Use
ID xsd:ID optional
LABEL xsd:string optional
NUMBER xsd:integer required
Source
 
<xsd:element name="Appendix" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">A profile must contain an appendix containing an example METS document which conforms to the requirements set out in the profile. Profile authors should note that in order to insure that the completed profile document is valid, any namespace and schemaLocation declarations contained in the root <mets> element should be moved to the root <METS_Profile> element.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:any namespace="##any" maxOccurs="unbounded"/>
    </xsd:sequence>
    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
    <xsd:attribute name="NUMBER" type="xsd:integer" use="required"/>
    <xsd:attribute name="LABEL" type="xsd:string" use="optional"/>
  </xsd:complexType>
</xsd:element>
Simple Type medString
Namespace http://www.loc.gov/METS_Profile/vNNN
Diagram
Type restriction of xsd:string
Facets
minLength 1
maxLength 256
Used by
Source
 
<xsd:simpleType name="medString">
  <xsd:restriction base="xsd:string">
    <xsd:maxLength value="256"/>
    <xsd:minLength value="1"/>
  </xsd:restriction>
</xsd:simpleType>
Simple Type longString
Namespace http://www.loc.gov/METS_Profile/vNNN
Diagram
Type restriction of xsd:string
Facets
minLength 1
maxLength 2048
Used by
Source
 
<xsd:simpleType name="longString">
  <xsd:restriction base="xsd:string">
    <xsd:maxLength value="2048"/>
    <xsd:minLength value="1"/>
  </xsd:restriction>
</xsd:simpleType>
Complex Type textSection
Namespace http://www.loc.gov/METS_Profile/vNNN
Annotations
 
Complex type for elements with extensive textual material
Diagram
Used by
Model
(head{0,1} | p | ul | ol | dl)
Children dl, head, ol, p, ul
Source
 
<xsd:complexType name="textSection">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">Complex type for elements with extensive textual material</xsd:documentation>
  </xsd:annotation>
  <xsd:sequence>
    <xsd:choice minOccurs="0" maxOccurs="unbounded">
      <xsd:element name="head" minOccurs="0" maxOccurs="1">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">The section head may be repeated. If there are multiple versions of the head in different languages; use the xml:lang attribute to differentiate them.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:simpleContent>
            <xsd:extension base="xsd:string">
              <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
              <xsd:attribute ref="xml:lang" use="optional"/>
            </xsd:extension>
          </xsd:simpleContent>
        </xsd:complexType>
      </xsd:element>
      <xsd:group ref="xhtmlelements"/>
    </xsd:choice>
  </xsd:sequence>
</xsd:complexType>
Complex Type reqs
Namespace http://www.loc.gov/METS_Profile/vNNN
Diagram
Used by
Model
Children requirement
Source
 
<xsd:complexType name="reqs">
  <xsd:sequence>
    <xsd:element name="requirement" maxOccurs="unbounded">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">The requirement element has four attributes: 1. an optional XML ID attribute, 2. an optional IDREFS attribute called RELATEDMAT, which you may use to indicate other portions of the profile document where this particular requirement is relevant. Requirement elements are in turn composed of a sequence of paragraph <p> elements, 3. an optional IDREFS attribute called EXAMPLES, which you may use to point to examples in the <Examples> section that demonstrate the requirement, and 4. an optional REQLEVEL attribute with values drawn from RFC 2119 (http://www.ietf.org/rfc/rfc2119.txt) . -----MUST: This word means that the definition is an absolute requirement. -----SHOULD: This word means that there may exist valid reasons in particular circumstances to ignore the requirement, but the full implications must be understood and carefully weighed before choosing a different course. -----MUST NOT: This phrase means that the prohibition described in the requirement is an absolute prohibition of the profile. -----SHOULD NOT: This phrase means that there may exist valid reasons in particular circumstances when violating the prohibition described in the requirement is acceptable or even useful, but the full implications should be understood and the case carefully weighed before doing so. The requirement text should clarify such circumstances. -----MAY: This word means that an item is not prohibited but fully optional. The requirement element has two children: description and tests. The required description element has an optional head subelement and some available text formatting elements from the xhtml namespace. Available xhtml elements include p, various list/item elements, text formatting such as b and i, a, and img.</xsd:documentation>
      </xsd:annotation>
      <xsd:complexType>
        <xsd:complexContent>
          <xsd:extension base="requirementsType">
            <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
            <xsd:attribute name="RELATEDMAT" type="xsd:IDREFS" use="optional"/>
            <xsd:attribute name="EXAMPLES" type="xsd:IDREFS" use="optional"/>
            <xsd:attribute name="REQLEVEL" use="optional">
              <xsd:annotation>
                <xsd:documentation xml:lang="en">The enumeration values for this element are drawn from RFC 2119 (http://www.ietf.org/rfc/rfc2119.txt). The definitions provided below are drawn from that source</xsd:documentation>
              </xsd:annotation>
              <xsd:simpleType>
                <xsd:restriction base="xsd:string">
                  <xsd:enumeration value="MUST">
                    <xsd:annotation>
                      <xsd:documentation xml:lang="en">This word means that the definition is an absolute requirement.</xsd:documentation>
                    </xsd:annotation>
                  </xsd:enumeration>
                  <xsd:enumeration value="SHOULD">
                    <xsd:annotation>
                      <xsd:documentation xml:lang="en">This word means that there may exist valid reasons in particular circumstances to ignore the requirement, but the full implications must be understood and carefully weighed before choosing a different course.</xsd:documentation>
                    </xsd:annotation>
                  </xsd:enumeration>
                  <xsd:enumeration value="MUST NOT">
                    <xsd:annotation>
                      <xsd:documentation xml:lang="en">This phrase means that the prohibition described in the requirement is an absolute prohibition of the profile.</xsd:documentation>
                    </xsd:annotation>
                  </xsd:enumeration>
                  <xsd:enumeration value="SHOULD NOT">
                    <xsd:annotation>
                      <xsd:documentation xml:lang="en">This phrase means that there may exist valid reasons in particular circumstances when violating the prohibition described in the requirement is acceptable or even useful, but the full implications should be understood and the case carefully weighed before doing so. The requirement text should clarify such circumstances.</xsd:documentation>
                    </xsd:annotation>
                  </xsd:enumeration>
                  <xsd:enumeration value="MAY">
                    <xsd:annotation>
                      <xsd:documentation xml:lang="en">This word means that an item is not prohibited but fully optional.</xsd:documentation>
                    </xsd:annotation>
                  </xsd:enumeration>
                </xsd:restriction>
              </xsd:simpleType>
            </xsd:attribute>
          </xsd:extension>
        </xsd:complexContent>
      </xsd:complexType>
    </xsd:element>
  </xsd:sequence>
</xsd:complexType>
Complex Type requirementsType
Namespace http://www.loc.gov/METS_Profile/vNNN
Diagram
Used by
Model
Children description, tests
Source
 
<xsd:complexType name="requirementsType">
  <xsd:sequence>
    <xsd:element name="description" type="textSection" minOccurs="1"/>
    <xsd:element name="tests" minOccurs="0">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">The optional tests subelement of description exists to supplement a textual description of a requirement with one that can be used to eventually provide machine validation. It includes one or more testGrp elements, which in turn contain testWrap or testRep elements. It is assumed each test’s desired outcome is to evaluate to "true." Implementers must ensure that the requirement level indicated and any formal test evaluation pattern are aligned so that the test indicates conformance rather than an error.</xsd:documentation>
      </xsd:annotation>
      <xsd:complexType>
        <xsd:sequence>
          <xsd:element name="test" minOccurs="1" maxOccurs="unbounded">
            <xsd:annotation>
              <xsd:documentation xml:lang="en">The test element contains the following attributes: 1. ID: an optional attribute uniquely identifying this element within the METS Profile document 2. LABEL: an optional textual description of the test being performed 3. TESTLANGUAGE: a required attribute indicating the language in which the test is expressed, such as XPath or XQuery 4. TESTLANGUAGEVERSION: an optional attribute indicating what version of the testing language has been used 5. TESTLANGUAGEURI: an optional attribute indicating an authoritative URI for the testing language used</xsd:documentation>
            </xsd:annotation>
            <xsd:complexType>
              <xsd:choice>
                <xsd:element name="testString">
                  <xsd:complexType>
                    <xsd:simpleContent>
                      <xsd:extension base="xsd:string">
                        <xsd:attribute name="CONTEXT" type="xsd:string" use="optional"/>
                        <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                      </xsd:extension>
                    </xsd:simpleContent>
                  </xsd:complexType>
                </xsd:element>
                <xsd:element name="testWrap">
                  <xsd:annotation>
                    <xsd:documentation xml:lang="en">The testWrap element has a test subelement with an optional CONTEXT attribute used to indicate the context in which a test should be evaluated. The value of the text element should be the actual text expression in the selected testing language.</xsd:documentation>
                  </xsd:annotation>
                  <xsd:complexType>
                    <xsd:choice>
                      <xsd:element name="testBin">
                        <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:complexType>
                          <xsd:simpleContent>
                            <xsd:extension base="xsd:base64Binary">
                              <xsd:attribute name="CONTEXT" type="xsd:string" use="optional"/>
                              <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                            </xsd:extension>
                          </xsd:simpleContent>
                        </xsd:complexType>
                      </xsd:element>
                      <xsd:element name="testXML">
                        <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:attribute name="CONTEXT" type="xsd:string" use="optional"/>
                          <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                        </xsd:complexType>
                      </xsd:element>
                    </xsd:choice>
                    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                  </xsd:complexType>
                </xsd:element>
                <xsd:element name="testRef">
                  <xsd:annotation>
                    <xsd:documentation xml:lang="en">The testRef element is intended to point to testing code stored elsewhere. It contains a LOCREF attribute to point to this testing code. When using testing code not easily embedded inside the METS Profile, such as that written in Perl, testRef is preferred over testWrap.</xsd:documentation>
                  </xsd:annotation>
                  <xsd:complexType>
                    <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
                    <xsd:attribute name="LOCREF" type="xsd:string" use="required"/>
                    <xsd:attribute name="LOCTYPE" type="xsd:string" use="required"/>
                  </xsd:complexType>
                </xsd:element>
              </xsd:choice>
              <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
              <xsd:attribute name="LABEL" type="xsd:string" use="optional"/>
              <xsd:attribute name="TESTLANGUAGE" type="xsd:string" use="required"/>
              <xsd:attribute name="TESTLANGUAGEVERSION" type="xsd:string"/>
              <xsd:attribute name="TESTLANGUAGEURI" type="xsd:anyURI"/>
            </xsd:complexType>
          </xsd:element>
        </xsd:sequence>
        <xsd:attribute name="ID" type="xsd:ID" use="optional"/>
      </xsd:complexType>
    </xsd:element>
  </xsd:sequence>
</xsd:complexType>
Complex Type pType
Namespace http://www.loc.gov/METS_Profile/vNNN
Diagram
Properties
mixed true
Model
p | ul | ol | dl
Children dl, ol, p, ul
Source
 
<xsd:complexType name="pType" mixed="true">
  <xsd:choice minOccurs="0" maxOccurs="unbounded">
    <xsd:group ref="xhtmlelements"/>
  </xsd:choice>
</xsd:complexType>
Attribute METS_Profile / URI / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute METS_Profile / URI / @LOCTYPE
Namespace No namespace
Type xsd:string
Properties
use required
Used by
Source
 
<xsd:attribute name="LOCTYPE" type="xsd:string" use="required"/>
Attribute METS_Profile / URI / @ASSIGNEDBY
Namespace No namespace
Type restriction of xsd:string
Properties
use required
Facets
enumeration metsboard
enumeration local
Used by
Source
 
<xsd:attribute name="ASSIGNEDBY" use="required">
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:enumeration value="metsboard"/>
      <xsd:enumeration value="local"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:attribute>
Attribute METS_Profile / URI / @REGDATE
Namespace No namespace
Type xsd:date
Properties
use optional
Used by
Source
 
<xsd:attribute name="REGDATE" type="xsd:date" use="optional"/>
Attribute METS_Profile / title / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute METS_Profile / abstract / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute METS_Profile / date / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute METS_Profile / contact / name / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute METS_Profile / contact / institution / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute METS_Profile / contact / address / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute METS_Profile / contact / phone / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute METS_Profile / contact / email / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute METS_Profile / contact / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute METS_Profile / contact / @ROLE
Namespace No namespace
Type xsd:string
Properties
use optional
Used by
Source
 
<xsd:attribute name="ROLE" type="xsd:string" use="optional"/>
Attribute METS_Profile / related_profile / @ID
Namespace No namespace
Type xsd:ID
Properties
Used by
Source
Attribute METS_Profile / related_profile / @URI
Namespace No namespace
Type xsd:anyURI
Properties
Used by
Source
Attribute METS_Profile / related_profile / @RELATIONSHIP
Namespace No namespace
Annotations
Type xsd:string
Properties
Used by
Source
Attribute textSection / head / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute METS_Profile / profile_context / uses / use / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute METS_Profile / profile_context / uses / use / @REQID
Namespace No namespace
Type xsd:IDREFS
Properties
use optional
Used by
Source
 
<xsd:attribute name="REQID" type="xsd:IDREFS" use="optional"/>
Attribute METS_Profile / external_schema / name / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute METS_Profile / external_schema / URL / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute METS_Profile / external_schema / URL / @TARGETNAMESPACE
Namespace No namespace
Type xsd:anyURI
Properties
use optional
Used by
Source
 
<xsd:attribute name="TARGETNAMESPACE" type="xsd:anyURI" use="optional"/>
Attribute METS_Profile / external_schema / context / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute METS_Profile / external_schema / note / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute METS_Profile / external_schema / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute METS_Profile / description_rules / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute METS_Profile / controlled_vocabularies / vocabulary / name / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute METS_Profile / controlled_vocabularies / vocabulary / maintenance_agency / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute METS_Profile / controlled_vocabularies / vocabulary / URI / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute METS_Profile / controlled_vocabularies / vocabulary / values / value / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute METS_Profile / controlled_vocabularies / vocabulary / values / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute METS_Profile / controlled_vocabularies / vocabulary / context / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute METS_Profile / controlled_vocabularies / vocabulary / description / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute METS_Profile / controlled_vocabularies / vocabulary / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute METS_Profile / controlled_vocabularies / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute requirementsType / tests / test / testString / @CONTEXT
Namespace No namespace
Type xsd:string
Properties
use optional
Used by
Source
 
<xsd:attribute name="CONTEXT" type="xsd:string" use="optional"/>
Attribute requirementsType / tests / test / testString / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute requirementsType / tests / test / testWrap / testBin / @CONTEXT
Namespace No namespace
Type xsd:string
Properties
use optional
Used by
Source
 
<xsd:attribute name="CONTEXT" type="xsd:string" use="optional"/>
Attribute requirementsType / tests / test / testWrap / testBin / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute requirementsType / tests / test / testWrap / testXML / @CONTEXT
Namespace No namespace
Type xsd:string
Properties
use optional
Used by
Source
 
<xsd:attribute name="CONTEXT" type="xsd:string" use="optional"/>
Attribute requirementsType / tests / test / testWrap / testXML / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute requirementsType / tests / test / testWrap / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute requirementsType / tests / test / testRef / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute requirementsType / tests / test / testRef / @LOCREF
Namespace No namespace
Type xsd:string
Properties
use required
Used by
Source
 
<xsd:attribute name="LOCREF" type="xsd:string" use="required"/>
Attribute requirementsType / tests / test / testRef / @LOCTYPE
Namespace No namespace
Type xsd:string
Properties
use required
Used by
Source
 
<xsd:attribute name="LOCTYPE" type="xsd:string" use="required"/>
Attribute requirementsType / tests / test / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute requirementsType / tests / test / @LABEL
Namespace No namespace
Type xsd:string
Properties
use optional
Used by
Source
 
<xsd:attribute name="LABEL" type="xsd:string" use="optional"/>
Attribute requirementsType / tests / test / @TESTLANGUAGE
Namespace No namespace
Type xsd:string
Properties
use required
Used by
Source
 
<xsd:attribute name="TESTLANGUAGE" type="xsd:string" use="required"/>
Attribute requirementsType / tests / test / @TESTLANGUAGEVERSION
Namespace No namespace
Type xsd:string
Properties
content simple
Used by
Source
 
<xsd:attribute name="TESTLANGUAGEVERSION" type="xsd:string"/>
Attribute requirementsType / tests / test / @TESTLANGUAGEURI
Namespace No namespace
Type xsd:anyURI
Properties
content simple
Used by
Source
 
<xsd:attribute name="TESTLANGUAGEURI" type="xsd:anyURI"/>
Attribute requirementsType / tests / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute reqs / requirement / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute reqs / requirement / @RELATEDMAT
Namespace No namespace
Type xsd:IDREFS
Properties
use optional
Used by
Source
 
<xsd:attribute name="RELATEDMAT" type="xsd:IDREFS" use="optional"/>
Attribute reqs / requirement / @EXAMPLES
Namespace No namespace
Type xsd:IDREFS
Properties
use optional
Used by
Source
 
<xsd:attribute name="EXAMPLES" type="xsd:IDREFS" use="optional"/>
Attribute reqs / requirement / @REQLEVEL
Namespace No namespace
Annotations
 
The enumeration values for this element are drawn from RFC 2119 (http://www.ietf.org/rfc/rfc2119.txt).  The definitions provided below are drawn from that source
Type restriction of xsd:string
Properties
use optional
Facets
enumeration MUST 
This word means that the definition is an absolute requirement.
enumeration SHOULD 
This word means that there may exist valid reasons in particular circumstances to ignore the requirement, but the full implications must be understood and carefully weighed before choosing a different course.
enumeration MUST NOT 
This phrase means that the prohibition described in the requirement is an absolute prohibition of the profile.
enumeration SHOULD NOT 
This phrase means that there may exist valid reasons in particular circumstances when violating the prohibition described in the requirement is acceptable or even useful, but the full implications should be understood and the case carefully weighed before doing so. The requirement text should clarify such circumstances.
enumeration MAY 
This word means that an item is not prohibited but fully optional.
Used by
Source
 
<xsd:attribute name="REQLEVEL" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The enumeration values for this element are drawn from RFC 2119 (http://www.ietf.org/rfc/rfc2119.txt). The definitions provided below are drawn from that source</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:enumeration value="MUST">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">This word means that the definition is an absolute requirement.</xsd:documentation>
        </xsd:annotation>
      </xsd:enumeration>
      <xsd:enumeration value="SHOULD">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">This word means that there may exist valid reasons in particular circumstances to ignore the requirement, but the full implications must be understood and carefully weighed before choosing a different course.</xsd:documentation>
        </xsd:annotation>
      </xsd:enumeration>
      <xsd:enumeration value="MUST NOT">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">This phrase means that the prohibition described in the requirement is an absolute prohibition of the profile.</xsd:documentation>
        </xsd:annotation>
      </xsd:enumeration>
      <xsd:enumeration value="SHOULD NOT">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">This phrase means that there may exist valid reasons in particular circumstances when violating the prohibition described in the requirement is acceptable or even useful, but the full implications should be understood and the case carefully weighed before doing so. The requirement text should clarify such circumstances.</xsd:documentation>
        </xsd:annotation>
      </xsd:enumeration>
      <xsd:enumeration value="MAY">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">This word means that an item is not prohibited but fully optional.</xsd:documentation>
        </xsd:annotation>
      </xsd:enumeration>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:attribute>
Attribute METS_Profile / structural_requirements / metsRootElement / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute METS_Profile / structural_requirements / metsHdr / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute METS_Profile / structural_requirements / mdSec / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute METS_Profile / structural_requirements / fileSec / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute METS_Profile / structural_requirements / structSec / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute METS_Profile / structural_requirements / multiSection / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute METS_Profile / structural_requirements / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute METS_Profile / technical_requirements / content_files / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Element METS_Profile/technical_requirements/content_files
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute METS_Profile / technical_requirements / metadata_files / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute METS_Profile / technical_requirements / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute METS_Profile / tool / name / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute METS_Profile / tool / agency / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute METS_Profile / tool / URI / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute METS_Profile / tool / description / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute METS_Profile / tool / note / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute METS_Profile / tool / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute METS_Profile / Example / @ID
Namespace No namespace
Type xsd:ID
Properties
use required
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="required"/>
Attribute METS_Profile / Example / @LABEL
Namespace No namespace
Type xsd:string
Properties
use optional
Used by
Source
 
<xsd:attribute name="LABEL" type="xsd:string" use="optional"/>
Attribute METS_Profile / Appendix / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute METS_Profile / Appendix / @NUMBER
Namespace No namespace
Type xsd:integer
Properties
use required
Used by
Source
 
<xsd:attribute name="NUMBER" type="xsd:integer" use="required"/>
Attribute METS_Profile / Appendix / @LABEL
Namespace No namespace
Type xsd:string
Properties
use optional
Used by
Source
 
<xsd:attribute name="LABEL" type="xsd:string" use="optional"/>
Attribute METS_Profile / @ID
Namespace No namespace
Type xsd:ID
Properties
use optional
Used by
Element METS_Profile
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional"/>
Attribute METS_Profile / @STATUS
Namespace No namespace
Type restriction of xsd:string
Properties
use required
Facets
enumeration final
enumeration provisional
Used by
Element METS_Profile
Source
 
<xsd:attribute name="STATUS" use="required">
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:enumeration value="final"/>
      <xsd:enumeration value="provisional"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:attribute>
Element Group xhtmlelements
Namespace http://www.loc.gov/METS_Profile/vNNN
Annotations
 
only the following group of HTML elements are allowed:
Paragraphs: <p>
All list elements: <ul>,<ol>,<dl>
Preformatted text: <pre>
Table: <table>
Image: <img>
Diagram
Used by
Model
p | ul | ol | dl
Children dl, ol, p, ul
Source
 
<xsd:group name="xhtmlelements">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">only the following group of HTML elements are allowed: Paragraphs: <p> All list elements: <ul>,<ol>,<dl> Preformatted text: <pre> Table: <table> Image: <img></xsd:documentation>
  </xsd:annotation>
  <xsd:choice>
    <xsd:element ref="xhtml:p"/>
    <xsd:group ref="xhtml:lists"/>
  </xsd:choice>
</xsd:group>
XML Schema documentation generated by ® XML Editor.