You are here: MusicXML Reference > Score Schema (XSD) > Complex Types > Complex Type: identification

Complex Type: identification

Description

Identification contains basic metadata about the score. It includes the information in MuseData headers that may apply at a score-wide, movement-wide, or part-wide level. The creator, rights, source, and relation elements are based on Dublin Core.

Derived By

Restricting xs:anyType

Content Model

Contains elements as defined in the following table.

Component  Type  Occurs  Default  Description 
  1..1 
creator  typed-text  0..*  The creator element is borrowed from Dublin Core. It is used for the creators of the score. The type attribute is used to distinguish different creative contributions. Thus, there can be multiple creators within an identification. Standard type values are composer, lyricist, and arranger. Other type values may be used for different types of creative roles. The type attribute should usually be used even if there is just a single creator element. The MusicXML format does not use the creator / contributor distinction from Dublin Core.
rights  typed-text  0..*  The rights element is borrowed from Dublin Core. It contains copyright and other intellectual property notices. Words, music, and derivatives can have different types, so multiple rights tags with different type attributes are supported. Standard type values are music, words, and arrangement, but other types may be used. The type attribute is only needed when there are multiple rights elements.
encoding  encoding  0..1  The encoding element contains information about who did the digital encoding, when, with what software, and in what aspects. Standard type values for the encoder element are music, words, and arrangement, but other types may be used. The type attribute is only needed when there are multiple encoder elements.
source  xs:string  0..1  The source for the music that is encoded. This is similar to the Dublin Core source element.
relation  typed-text  0..*  A related resource for the music that is encoded. This is similar to the Dublin Core relation element. Standard type values are music, words, and arrangement, but other types may be used.
miscellaneous  miscellaneous  0..1  If a program has other metadata not yet supported in the MusicXML format, it can go in the miscellaneous element. The miscellaneous type puts each separate part of metadata into its own miscellaneous-field type.
Referenced By
Definition
<xs:complexType name="identification">
  <xs:annotation>
    <xs:documentation>Identification contains basic metadata about the score. It includes the information in MuseData headers that may apply at a score-wide, movement-wide, or part-wide level. The creator, rights, source, and relation elements are based on Dublin Core.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="creator" type="typed-text" minOccurs="0" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>The creator element is borrowed from Dublin Core. It is used for the creators of the score. The type attribute is used to distinguish different creative contributions. Thus, there can be multiple creators within an identification. Standard type values are composer, lyricist, and arranger. Other type values may be used for different types of creative roles. The type attribute should usually be used even if there is just a single creator element. The MusicXML format does not use the creator / contributor distinction from Dublin Core.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="rights" type="typed-text" minOccurs="0" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>The rights element is borrowed from Dublin Core. It contains copyright and other intellectual property notices. Words, music, and derivatives can have different types, so multiple rights tags with different type attributes are supported. Standard type values are music, words, and arrangement, but other types may be used. The type attribute is only needed when there are multiple rights elements.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="encoding" type="encoding" minOccurs="0">
      <xsd:annotation>
        <xsd:documentation>The encoding element contains information about who did the digital encoding, when, with what software, and in what aspects. Standard type values for the encoder element are music, words, and arrangement, but other types may be used. The type attribute is only needed when there are multiple encoder elements.</xsd:documentation>
      </xsd:annotation>
    </xs:element>
    <xs:element name="source" type="xs:string" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The source for the music that is encoded. This is similar to the Dublin Core source element.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="relation" type="typed-text" minOccurs="0" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>A related resource for the music that is encoded. This is similar to the Dublin Core relation element. Standard type values are music, words, and arrangement, but other types may be used.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="miscellaneous" type="miscellaneous" minOccurs="0">
      <xsd:annotation>
        <xsd:documentation>If a program has other metadata not yet supported in the MusicXML format, it can go in the miscellaneous element. The miscellaneous type puts each separate part of metadata into its own miscellaneous-field type.</xsd:documentation>
      </xsd:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>

 

MusicXML Documentation Home
Last built 2/20/2015

7007 Winchester Circle, Suite 140

Boulder, CO 80301