Showing:

Annotations
Attributes
Diagrams
Facets
Properties
Source
Used by
Complex Type areaType
Namespace http://www.loc.gov/METS/
Annotations
areaType: Complex Type for Area Linking
The area element provides for more sophisticated linking between a div element and content files representing that div, be they text, image, audio, or video files.  An area element can link a div to a point within a file, to a one-dimension segment of a file (e.g., text segment, image line, audio/video clip), or a two-dimensional section of a file 	(e.g, subsection of an image, or a subsection of the  video display of a video file.  The area element has no content; all information is recorded within its various attributes.
Diagram
Used by
Attributes
QName Type Use Annotation
ADMID xsd:IDREFS optional
ADMID (IDREFS/O): Contains the ID attribute values identifying the <rightsMD>, <sourceMD>, <techMD> and/or <digiprovMD> elements within the <amdSec> of the METS document that contain or link to administrative metadata pertaining to the content represented by the <area> element. Typically the <area> ADMID attribute would be used to identify the <rightsMD> element or elements that pertain to the <area>, but it could be used anytime there was a need to link an <area> with pertinent administrative metadata. For more information on using METS IDREFS and IDREF type attributes for internal linking, see Chapter 4 of the METS Primer
BEGIN xsd:string optional
BEGIN (string/O): An attribute that specifies the point in the content file where the relevant section of content begins. It can be used in conjunction with either the END attribute or the EXTENT attribute as a means of defining the relevant portion of the referenced file precisely. It can only be interpreted meaningfully in conjunction with the BETYPE or EXTTYPE, which specify the kind of beginning/ending point values or beginning/extent values that are being used. The BEGIN attribute can be used with or without a companion END or EXTENT element. In this case, the end of the content file is assumed to be the end point.
BETYPE restriction of xsd:string optional
BETYPE: Begin/End Type.
					BETYPE (string/O): An attribute that specifies the kind of BEGIN and/or END values that are being used. For example, if BYTE is specified, then the BEGIN and END point values represent the byte offsets into a file. If IDREF is specified, then the BEGIN element specifies the ID value that identifies the element in a structured text file where the relevant section of the file begins; and the END value (if present) would specify the ID value that identifies the element with which the relevant section of the file ends. Must be one of the following values: 
BYTE
IDREF
SMIL
MIDI
SMPTE-25
SMPTE-24
SMPTE-DF30
SMPTE-NDF30
SMPTE-DF29.97
SMPTE-NDF29.97
TIME
TCF
XPTR
CONTENTIDS URIs optional
CONTENTIDS (URI/O): Content IDs for the content represented by the <area> (equivalent to DIDL DII or Digital Item Identifier, a unique external ID).
COORDS xsd:string optional
COORDS (string/O): Specifies the coordinates in an image map for the shape of the pertinent area as specified in the SHAPE attribute. While technically optional, SHAPE and COORDS must both appear together to define the relevant area of image content. COORDS should be used in conjunction with SHAPE in the manner defined for the COORDs and SHAPE attributes on an HTML4 <area> element. COORDS must be a comma delimited string of integer value pairs representing coordinates (plus radius in the case of CIRCLE) within an image map. Number of coordinates pairs depends on shape: RECT: x1, y1, x2, y2; CIRC: x1, y1; POLY: x1, y1, x2, y2, x3, y3 . . .
END xsd:string optional
END (string/O): An attribute that specifies the point in the content file where the relevant section of content ends. It can only be interpreted meaningfully in conjunction with the BETYPE, which specifies the kind of ending point values being used. Typically the END attribute would only appear in conjunction with a BEGIN element.
EXTENT xsd:string optional
EXTENT (string/O): An attribute that specifies the extent of the relevant section of the content file. Can only be interpreted meaningfully in conjunction with the EXTTYPE which specifies the kind of value that is being used. Typically the EXTENT attribute would only appear in conjunction with a BEGIN element and would not be used if the BEGIN point represents an IDREF.
EXTTYPE restriction of xsd:string optional
EXTTYPE (string/O): An attribute that specifies the kind of EXTENT values that are being used. For example if BYTE is specified then EXTENT would represent a byte count. If TIME is specified the EXTENT would represent a duration of time. EXTTYPE must be one of the following values: 
BYTE
SMIL
MIDI
SMPTE-25
SMPTE-24
SMPTE-DF30
SMPTE-NDF30
SMPTE-DF29.97
SMPTE-NDF29.97
TIME
TCF.
FILEID xsd:IDREF required
FILEID (IDREF/R): An attribute which provides the XML ID value that identifies the <file> element in the <fileSec> that then points to and/or contains the digital content represented by the <area> element. It must contain an ID value represented in an ID attribute associated with a <file> element in the <fileSec> element in the same METS document.
ID xsd:ID optional
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR. For more information on using ID attributes for internal and external linking see Chapter 4 of the METS Primer.
LABEL xsd:string optional
LABEL (string/O): An attribute used, for example, to identify a <div> to an end user viewing the document. Thus a hierarchical arrangement of the <div> LABEL values could provide a table of contents to the digital content represented by a METS document and facilitate the users’ navigation of the digital object. Note that a <div> LABEL should be specific to its level in the structural map. In the case of a book with chapters, the book <div> LABEL should have the book title and the chapter <div>; LABELs should have the individual chapter titles, rather than having the chapter <div> LABELs combine both book title and chapter title . For further of the distinction between LABEL and ORDERLABEL see the description of the ORDERLABEL attribute.
ORDER xsd:integer optional
ORDER (integer/O): A representation of the element's order among its siblings (e.g., its absolute, numeric sequence). For an example, and clarification of the distinction between ORDER and ORDERLABEL, see the description of the ORDERLABEL attribute.
ORDERLABEL xsd:string optional
ORDERLABEL (string/O): A representation of the element's order among its siblings (e.g., “xii”), or of any non-integer native numbering system. It is presumed that this value will still be machine actionable (e.g., it would support ‘go to page ___’ function), and it should not be used as a replacement/substitute for the LABEL attribute. To understand the differences between ORDER, ORDERLABEL and LABEL, imagine a text with 10 roman numbered pages followed by 10 arabic numbered pages. Page iii would have an ORDER of “3”, an ORDERLABEL of “iii” and a LABEL of “Page iii”, while page 3 would have an ORDER of “13”, an ORDERLABEL of “3” and a LABEL of “Page 3”.
SHAPE restriction of xsd:string optional
SHAPE (string/O): An attribute that can be used as in HTML to define the shape of the relevant area within the content file pointed to by the <area> element. Typically this would be used with image content (still image or video frame) when only a portion of an integal image map pertains. If SHAPE is specified then COORDS must also be present. SHAPE should be used in conjunction with COORDS in the manner defined for the shape and coords attributes on an HTML4 <area> element. SHAPE must contain one of the following values: 
RECT 
CIRCLE
POLY
Wildcard: ANY attribute from ANY namespace OTHER than 'http://www.loc.gov/METS/'
Source
<xsd:complexType name="areaType">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">areaType: Complex Type for Area Linking The area element provides for more sophisticated linking between a div element and content files representing that div, be they text, image, audio, or video files. An area element can link a div to a point within a file, to a one-dimension segment of a file (e.g., text segment, image line, audio/video clip), or a two-dimensional section of a file (e.g, subsection of an image, or a subsection of the video display of a video file. The area element has no content; all information is recorded within its various attributes.</xsd:documentation>
  </xsd:annotation>
  <xsd:attribute name="ID" type="xsd:ID" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR. For more information on using ID attributes for internal and external linking see Chapter 4 of the METS Primer.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="FILEID" type="xsd:IDREF" use="required">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">FILEID (IDREF/R): An attribute which provides the XML ID value that identifies the <file> element in the <fileSec> that then points to and/or contains the digital content represented by the <area> element. It must contain an ID value represented in an ID attribute associated with a <file> element in the <fileSec> element in the same METS document.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="SHAPE" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">SHAPE (string/O): An attribute that can be used as in HTML to define the shape of the relevant area within the content file pointed to by the <area> element. Typically this would be used with image content (still image or video frame) when only a portion of an integal image map pertains. If SHAPE is specified then COORDS must also be present. SHAPE should be used in conjunction with COORDS in the manner defined for the shape and coords attributes on an HTML4 <area> element. SHAPE must contain one of the following values: RECT CIRCLE POLY</xsd:documentation>
    </xsd:annotation>
    <xsd:simpleType>
      <xsd:restriction base="xsd:string">
        <xsd:enumeration value="RECT"/>
        <xsd:enumeration value="CIRCLE"/>
        <xsd:enumeration value="POLY"/>
      </xsd:restriction>
    </xsd:simpleType>
  </xsd:attribute>
  <xsd:attribute name="COORDS" type="xsd:string" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">COORDS (string/O): Specifies the coordinates in an image map for the shape of the pertinent area as specified in the SHAPE attribute. While technically optional, SHAPE and COORDS must both appear together to define the relevant area of image content. COORDS should be used in conjunction with SHAPE in the manner defined for the COORDs and SHAPE attributes on an HTML4 <area> element. COORDS must be a comma delimited string of integer value pairs representing coordinates (plus radius in the case of CIRCLE) within an image map. Number of coordinates pairs depends on shape: RECT: x1, y1, x2, y2; CIRC: x1, y1; POLY: x1, y1, x2, y2, x3, y3 . . .</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="BEGIN" type="xsd:string" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">BEGIN (string/O): An attribute that specifies the point in the content file where the relevant section of content begins. It can be used in conjunction with either the END attribute or the EXTENT attribute as a means of defining the relevant portion of the referenced file precisely. It can only be interpreted meaningfully in conjunction with the BETYPE or EXTTYPE, which specify the kind of beginning/ending point values or beginning/extent values that are being used. The BEGIN attribute can be used with or without a companion END or EXTENT element. In this case, the end of the content file is assumed to be the end point.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="END" type="xsd:string" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">END (string/O): An attribute that specifies the point in the content file where the relevant section of content ends. It can only be interpreted meaningfully in conjunction with the BETYPE, which specifies the kind of ending point values being used. Typically the END attribute would only appear in conjunction with a BEGIN element.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="BETYPE" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">BETYPE: Begin/End Type. BETYPE (string/O): An attribute that specifies the kind of BEGIN and/or END values that are being used. For example, if BYTE is specified, then the BEGIN and END point values represent the byte offsets into a file. If IDREF is specified, then the BEGIN element specifies the ID value that identifies the element in a structured text file where the relevant section of the file begins; and the END value (if present) would specify the ID value that identifies the element with which the relevant section of the file ends. Must be one of the following values: BYTE IDREF SMIL MIDI SMPTE-25 SMPTE-24 SMPTE-DF30 SMPTE-NDF30 SMPTE-DF29.97 SMPTE-NDF29.97 TIME TCF XPTR</xsd:documentation>
    </xsd:annotation>
    <xsd:simpleType>
      <xsd:restriction base="xsd:string">
        <xsd:enumeration value="BYTE"/>
        <xsd:enumeration value="IDREF"/>
        <xsd:enumeration value="SMIL"/>
        <xsd:enumeration value="MIDI"/>
        <xsd:enumeration value="SMPTE-25"/>
        <xsd:enumeration value="SMPTE-24"/>
        <xsd:enumeration value="SMPTE-DF30"/>
        <xsd:enumeration value="SMPTE-NDF30"/>
        <xsd:enumeration value="SMPTE-DF29.97"/>
        <xsd:enumeration value="SMPTE-NDF29.97"/>
        <xsd:enumeration value="TIME"/>
        <xsd:enumeration value="TCF"/>
        <xsd:enumeration value="XPTR"/>
      </xsd:restriction>
    </xsd:simpleType>
  </xsd:attribute>
  <xsd:attribute name="EXTENT" type="xsd:string" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">EXTENT (string/O): An attribute that specifies the extent of the relevant section of the content file. Can only be interpreted meaningfully in conjunction with the EXTTYPE which specifies the kind of value that is being used. Typically the EXTENT attribute would only appear in conjunction with a BEGIN element and would not be used if the BEGIN point represents an IDREF.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="EXTTYPE" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">EXTTYPE (string/O): An attribute that specifies the kind of EXTENT values that are being used. For example if BYTE is specified then EXTENT would represent a byte count. If TIME is specified the EXTENT would represent a duration of time. EXTTYPE must be one of the following values: BYTE SMIL MIDI SMPTE-25 SMPTE-24 SMPTE-DF30 SMPTE-NDF30 SMPTE-DF29.97 SMPTE-NDF29.97 TIME TCF.</xsd:documentation>
    </xsd:annotation>
    <xsd:simpleType>
      <xsd:restriction base="xsd:string">
        <xsd:enumeration value="BYTE"/>
        <xsd:enumeration value="SMIL"/>
        <xsd:enumeration value="MIDI"/>
        <xsd:enumeration value="SMPTE-25"/>
        <xsd:enumeration value="SMPTE-24"/>
        <xsd:enumeration value="SMPTE-DF30"/>
        <xsd:enumeration value="SMPTE-NDF30"/>
        <xsd:enumeration value="SMPTE-DF29.97"/>
        <xsd:enumeration value="SMPTE-NDF29.97"/>
        <xsd:enumeration value="TIME"/>
        <xsd:enumeration value="TCF"/>
      </xsd:restriction>
    </xsd:simpleType>
  </xsd:attribute>
  <xsd:attribute name="ADMID" type="xsd:IDREFS" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">ADMID (IDREFS/O): Contains the ID attribute values identifying the <rightsMD>, <sourceMD>, <techMD> and/or <digiprovMD> elements within the <amdSec> of the METS document that contain or link to administrative metadata pertaining to the content represented by the <area> element. Typically the <area> ADMID attribute would be used to identify the <rightsMD> element or elements that pertain to the <area>, but it could be used anytime there was a need to link an <area> with pertinent administrative metadata. For more information on using METS IDREFS and IDREF type attributes for internal linking, see Chapter 4 of the METS Primer</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="CONTENTIDS" type="URIs" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">CONTENTIDS (URI/O): Content IDs for the content represented by the <area> (equivalent to DIDL DII or Digital Item Identifier, a unique external ID).</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attributeGroup ref="ORDERLABELS"/>
  <xsd:anyAttribute namespace="##other" processContents="lax"/>
</xsd:complexType>
Schema location https://raw.githubusercontent.com/mets/METS-schema/5cc5f10c9950b3e43f1424236ca7a3f8fe4e7e76/mets.xsd
Attribute areaType / @ID
Namespace No namespace
Annotations
ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR. For more information on using ID attributes for internal and external linking see Chapter 4 of the METS Primer.
Type xsd:ID
Properties
use optional
Used by
Complex Type areaType
Source
<xsd:attribute name="ID" type="xsd:ID" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">ID (ID/O): This attribute uniquely identifies the element within the METS document, and would allow the element to be referenced unambiguously from another element or document via an IDREF or an XPTR. For more information on using ID attributes for internal and external linking see Chapter 4 of the METS Primer.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Schema location https://raw.githubusercontent.com/mets/METS-schema/5cc5f10c9950b3e43f1424236ca7a3f8fe4e7e76/mets.xsd
Attribute areaType / @FILEID
Namespace No namespace
Annotations
FILEID (IDREF/R): An attribute which provides the XML ID value that identifies the <file> element in the <fileSec> that then points to and/or contains the digital content represented by the <area> element. It must contain an ID value represented in an ID attribute associated with a <file> element in the <fileSec> element in the same METS document.
Type xsd:IDREF
Properties
use required
Used by
Complex Type areaType
Source
<xsd:attribute name="FILEID" type="xsd:IDREF" use="required">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">FILEID (IDREF/R): An attribute which provides the XML ID value that identifies the <file> element in the <fileSec> that then points to and/or contains the digital content represented by the <area> element. It must contain an ID value represented in an ID attribute associated with a <file> element in the <fileSec> element in the same METS document.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Schema location https://raw.githubusercontent.com/mets/METS-schema/5cc5f10c9950b3e43f1424236ca7a3f8fe4e7e76/mets.xsd
Attribute areaType / @SHAPE
Namespace No namespace
Annotations
SHAPE (string/O): An attribute that can be used as in HTML to define the shape of the relevant area within the content file pointed to by the <area> element. Typically this would be used with image content (still image or video frame) when only a portion of an integal image map pertains. If SHAPE is specified then COORDS must also be present. SHAPE should be used in conjunction with COORDS in the manner defined for the shape and coords attributes on an HTML4 <area> element. SHAPE must contain one of the following values: 
RECT 
CIRCLE
POLY
Type restriction of xsd:string
Properties
use optional
Facets
enumeration RECT
enumeration CIRCLE
enumeration POLY
Used by
Complex Type areaType
Source
<xsd:attribute name="SHAPE" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">SHAPE (string/O): An attribute that can be used as in HTML to define the shape of the relevant area within the content file pointed to by the <area> element. Typically this would be used with image content (still image or video frame) when only a portion of an integal image map pertains. If SHAPE is specified then COORDS must also be present. SHAPE should be used in conjunction with COORDS in the manner defined for the shape and coords attributes on an HTML4 <area> element. SHAPE must contain one of the following values: RECT CIRCLE POLY</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:enumeration value="RECT"/>
      <xsd:enumeration value="CIRCLE"/>
      <xsd:enumeration value="POLY"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:attribute>
Schema location https://raw.githubusercontent.com/mets/METS-schema/5cc5f10c9950b3e43f1424236ca7a3f8fe4e7e76/mets.xsd
Attribute areaType / @COORDS
Namespace No namespace
Annotations
COORDS (string/O): Specifies the coordinates in an image map for the shape of the pertinent area as specified in the SHAPE attribute. While technically optional, SHAPE and COORDS must both appear together to define the relevant area of image content. COORDS should be used in conjunction with SHAPE in the manner defined for the COORDs and SHAPE attributes on an HTML4 <area> element. COORDS must be a comma delimited string of integer value pairs representing coordinates (plus radius in the case of CIRCLE) within an image map. Number of coordinates pairs depends on shape: RECT: x1, y1, x2, y2; CIRC: x1, y1; POLY: x1, y1, x2, y2, x3, y3 . . .
Type xsd:string
Properties
use optional
Used by
Complex Type areaType
Source
<xsd:attribute name="COORDS" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">COORDS (string/O): Specifies the coordinates in an image map for the shape of the pertinent area as specified in the SHAPE attribute. While technically optional, SHAPE and COORDS must both appear together to define the relevant area of image content. COORDS should be used in conjunction with SHAPE in the manner defined for the COORDs and SHAPE attributes on an HTML4 <area> element. COORDS must be a comma delimited string of integer value pairs representing coordinates (plus radius in the case of CIRCLE) within an image map. Number of coordinates pairs depends on shape: RECT: x1, y1, x2, y2; CIRC: x1, y1; POLY: x1, y1, x2, y2, x3, y3 . . .</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Schema location https://raw.githubusercontent.com/mets/METS-schema/5cc5f10c9950b3e43f1424236ca7a3f8fe4e7e76/mets.xsd
Attribute areaType / @BEGIN
Namespace No namespace
Annotations
BEGIN (string/O): An attribute that specifies the point in the content file where the relevant section of content begins. It can be used in conjunction with either the END attribute or the EXTENT attribute as a means of defining the relevant portion of the referenced file precisely. It can only be interpreted meaningfully in conjunction with the BETYPE or EXTTYPE, which specify the kind of beginning/ending point values or beginning/extent values that are being used. The BEGIN attribute can be used with or without a companion END or EXTENT element. In this case, the end of the content file is assumed to be the end point.
Type xsd:string
Properties
use optional
Used by
Complex Type areaType
Source
<xsd:attribute name="BEGIN" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">BEGIN (string/O): An attribute that specifies the point in the content file where the relevant section of content begins. It can be used in conjunction with either the END attribute or the EXTENT attribute as a means of defining the relevant portion of the referenced file precisely. It can only be interpreted meaningfully in conjunction with the BETYPE or EXTTYPE, which specify the kind of beginning/ending point values or beginning/extent values that are being used. The BEGIN attribute can be used with or without a companion END or EXTENT element. In this case, the end of the content file is assumed to be the end point.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Schema location https://raw.githubusercontent.com/mets/METS-schema/5cc5f10c9950b3e43f1424236ca7a3f8fe4e7e76/mets.xsd
Attribute areaType / @END
Namespace No namespace
Annotations
END (string/O): An attribute that specifies the point in the content file where the relevant section of content ends. It can only be interpreted meaningfully in conjunction with the BETYPE, which specifies the kind of ending point values being used. Typically the END attribute would only appear in conjunction with a BEGIN element.
Type xsd:string
Properties
use optional
Used by
Complex Type areaType
Source
<xsd:attribute name="END" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">END (string/O): An attribute that specifies the point in the content file where the relevant section of content ends. It can only be interpreted meaningfully in conjunction with the BETYPE, which specifies the kind of ending point values being used. Typically the END attribute would only appear in conjunction with a BEGIN element.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Schema location https://raw.githubusercontent.com/mets/METS-schema/5cc5f10c9950b3e43f1424236ca7a3f8fe4e7e76/mets.xsd
Attribute areaType / @BETYPE
Namespace No namespace
Annotations
BETYPE: Begin/End Type.
					BETYPE (string/O): An attribute that specifies the kind of BEGIN and/or END values that are being used. For example, if BYTE is specified, then the BEGIN and END point values represent the byte offsets into a file. If IDREF is specified, then the BEGIN element specifies the ID value that identifies the element in a structured text file where the relevant section of the file begins; and the END value (if present) would specify the ID value that identifies the element with which the relevant section of the file ends. Must be one of the following values: 
BYTE
IDREF
SMIL
MIDI
SMPTE-25
SMPTE-24
SMPTE-DF30
SMPTE-NDF30
SMPTE-DF29.97
SMPTE-NDF29.97
TIME
TCF
XPTR
Type restriction of xsd:string
Properties
use optional
Facets
enumeration BYTE
enumeration IDREF
enumeration SMIL
enumeration MIDI
enumeration SMPTE-25
enumeration SMPTE-24
enumeration SMPTE-DF30
enumeration SMPTE-NDF30
enumeration SMPTE-DF29.97
enumeration SMPTE-NDF29.97
enumeration TIME
enumeration TCF
enumeration XPTR
Used by
Complex Type areaType
Source
<xsd:attribute name="BETYPE" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">BETYPE: Begin/End Type. BETYPE (string/O): An attribute that specifies the kind of BEGIN and/or END values that are being used. For example, if BYTE is specified, then the BEGIN and END point values represent the byte offsets into a file. If IDREF is specified, then the BEGIN element specifies the ID value that identifies the element in a structured text file where the relevant section of the file begins; and the END value (if present) would specify the ID value that identifies the element with which the relevant section of the file ends. Must be one of the following values: BYTE IDREF SMIL MIDI SMPTE-25 SMPTE-24 SMPTE-DF30 SMPTE-NDF30 SMPTE-DF29.97 SMPTE-NDF29.97 TIME TCF XPTR</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:enumeration value="BYTE"/>
      <xsd:enumeration value="IDREF"/>
      <xsd:enumeration value="SMIL"/>
      <xsd:enumeration value="MIDI"/>
      <xsd:enumeration value="SMPTE-25"/>
      <xsd:enumeration value="SMPTE-24"/>
      <xsd:enumeration value="SMPTE-DF30"/>
      <xsd:enumeration value="SMPTE-NDF30"/>
      <xsd:enumeration value="SMPTE-DF29.97"/>
      <xsd:enumeration value="SMPTE-NDF29.97"/>
      <xsd:enumeration value="TIME"/>
      <xsd:enumeration value="TCF"/>
      <xsd:enumeration value="XPTR"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:attribute>
Schema location https://raw.githubusercontent.com/mets/METS-schema/5cc5f10c9950b3e43f1424236ca7a3f8fe4e7e76/mets.xsd
Attribute areaType / @EXTENT
Namespace No namespace
Annotations
EXTENT (string/O): An attribute that specifies the extent of the relevant section of the content file. Can only be interpreted meaningfully in conjunction with the EXTTYPE which specifies the kind of value that is being used. Typically the EXTENT attribute would only appear in conjunction with a BEGIN element and would not be used if the BEGIN point represents an IDREF.
Type xsd:string
Properties
use optional
Used by
Complex Type areaType
Source
<xsd:attribute name="EXTENT" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">EXTENT (string/O): An attribute that specifies the extent of the relevant section of the content file. Can only be interpreted meaningfully in conjunction with the EXTTYPE which specifies the kind of value that is being used. Typically the EXTENT attribute would only appear in conjunction with a BEGIN element and would not be used if the BEGIN point represents an IDREF.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Schema location https://raw.githubusercontent.com/mets/METS-schema/5cc5f10c9950b3e43f1424236ca7a3f8fe4e7e76/mets.xsd
Attribute areaType / @EXTTYPE
Namespace No namespace
Annotations
EXTTYPE (string/O): An attribute that specifies the kind of EXTENT values that are being used. For example if BYTE is specified then EXTENT would represent a byte count. If TIME is specified the EXTENT would represent a duration of time. EXTTYPE must be one of the following values: 
BYTE
SMIL
MIDI
SMPTE-25
SMPTE-24
SMPTE-DF30
SMPTE-NDF30
SMPTE-DF29.97
SMPTE-NDF29.97
TIME
TCF.
Type restriction of xsd:string
Properties
use optional
Facets
enumeration BYTE
enumeration SMIL
enumeration MIDI
enumeration SMPTE-25
enumeration SMPTE-24
enumeration SMPTE-DF30
enumeration SMPTE-NDF30
enumeration SMPTE-DF29.97
enumeration SMPTE-NDF29.97
enumeration TIME
enumeration TCF
Used by
Complex Type areaType
Source
<xsd:attribute name="EXTTYPE" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">EXTTYPE (string/O): An attribute that specifies the kind of EXTENT values that are being used. For example if BYTE is specified then EXTENT would represent a byte count. If TIME is specified the EXTENT would represent a duration of time. EXTTYPE must be one of the following values: BYTE SMIL MIDI SMPTE-25 SMPTE-24 SMPTE-DF30 SMPTE-NDF30 SMPTE-DF29.97 SMPTE-NDF29.97 TIME TCF.</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:enumeration value="BYTE"/>
      <xsd:enumeration value="SMIL"/>
      <xsd:enumeration value="MIDI"/>
      <xsd:enumeration value="SMPTE-25"/>
      <xsd:enumeration value="SMPTE-24"/>
      <xsd:enumeration value="SMPTE-DF30"/>
      <xsd:enumeration value="SMPTE-NDF30"/>
      <xsd:enumeration value="SMPTE-DF29.97"/>
      <xsd:enumeration value="SMPTE-NDF29.97"/>
      <xsd:enumeration value="TIME"/>
      <xsd:enumeration value="TCF"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:attribute>
Schema location https://raw.githubusercontent.com/mets/METS-schema/5cc5f10c9950b3e43f1424236ca7a3f8fe4e7e76/mets.xsd
Attribute areaType / @ADMID
Namespace No namespace
Annotations
ADMID (IDREFS/O): Contains the ID attribute values identifying the <rightsMD>, <sourceMD>, <techMD> and/or <digiprovMD> elements within the <amdSec> of the METS document that contain or link to administrative metadata pertaining to the content represented by the <area> element. Typically the <area> ADMID attribute would be used to identify the <rightsMD> element or elements that pertain to the <area>, but it could be used anytime there was a need to link an <area> with pertinent administrative metadata. For more information on using METS IDREFS and IDREF type attributes for internal linking, see Chapter 4 of the METS Primer
Type xsd:IDREFS
Properties
use optional
Used by
Complex Type areaType
Source
<xsd:attribute name="ADMID" type="xsd:IDREFS" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">ADMID (IDREFS/O): Contains the ID attribute values identifying the <rightsMD>, <sourceMD>, <techMD> and/or <digiprovMD> elements within the <amdSec> of the METS document that contain or link to administrative metadata pertaining to the content represented by the <area> element. Typically the <area> ADMID attribute would be used to identify the <rightsMD> element or elements that pertain to the <area>, but it could be used anytime there was a need to link an <area> with pertinent administrative metadata. For more information on using METS IDREFS and IDREF type attributes for internal linking, see Chapter 4 of the METS Primer</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Schema location https://raw.githubusercontent.com/mets/METS-schema/5cc5f10c9950b3e43f1424236ca7a3f8fe4e7e76/mets.xsd
Attribute areaType / @CONTENTIDS
Namespace No namespace
Annotations
CONTENTIDS (URI/O): Content IDs for the content represented by the <area> (equivalent to DIDL DII or Digital Item Identifier, a unique external ID).
Type URIs
Properties
use optional
Used by
Complex Type areaType
Source
<xsd:attribute name="CONTENTIDS" type="URIs" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">CONTENTIDS (URI/O): Content IDs for the content represented by the <area> (equivalent to DIDL DII or Digital Item Identifier, a unique external ID).</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Schema location https://raw.githubusercontent.com/mets/METS-schema/5cc5f10c9950b3e43f1424236ca7a3f8fe4e7e76/mets.xsd