Complex Type: score-part

Description

Each MusicXML part corresponds to a track in a Standard MIDI Format 1 file. The score-instrument elements are used when there are multiple instruments per track. The midi-device element is used to make a MIDI device or port assignment for the given track or specific MIDI instruments. Initial midi-instrument assignments may be made here as well.

Derived By

Restricting xs:anyType

Attributes

Name	Type	Required?	Default	Description
id	xs:ID	Yes

Content Model

Contains elements as defined in the following table.

Component	Type	Occurs	Description
		1..1
identification	identification	0..1	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.
part-name	part-name	1..1	The part-name type describes the name or abbreviation of a score-part element. Formatting attributes for the part-name element are deprecated in Version 2.0 in favor of the new part-name-display and part-abbreviation-display elements.
part-name-display	name-display	0..1	The part-name-display and part-abbreviation-display elements used in the score.mod file may also be used here to change how a part name or abbreviation is displayed over the course of a piece. They take effect when the current measure or a succeeding measure starts a new system.
part-abbreviation	part-name	0..1	The part-name-display and part-abbreviation-display elements used in the score.mod file may also be used here to change how a part name or abbreviation is displayed over the course of a piece. They take effect when the current measure or a succeeding measure starts a new system.
part-abbreviation-display	name-display	0..1	The part-name-display and part-abbreviation-display elements used in the score.mod file may also be used here to change how a part name or abbreviation is displayed over the course of a piece. They take effect when the current measure or a succeeding measure starts a new system.
group	xs:string	0..*	The group element allows the use of different versions of the part for different purposes. Typical values include score, parts, sound, and data. Ordering information that is directly encoded in MuseData can be derived from the ordering within a MusicXML score or opus.
score-instrument	score-instrument	0..*	The score-instrument type represents a single instrument within a score-part. As with the score-part type, each score-instrument has a required ID attribute, a name, and an optional abbreviation. A score-instrument type is also required if the score specifies MIDI 1.0 channels, banks, or programs. An initial midi-instrument assignment can also be made here. MusicXML software should be able to automatically assign reasonable channels and instruments without these elements in simple cases, such as where part names match General MIDI instrument names.
		0..*
midi-device	midi-device	0..1	The midi-device type corresponds to the DeviceName meta event in Standard MIDI Files. Unlike the DeviceName meta event, there can be multiple midi-device elements per MusicXML part starting in MusicXML 3.0.
midi-instrument	midi-instrument	0..1	The midi-instrument type defines MIDI 1.0 instrument playback. The midi-instrument element can be a part of either the score-instrument element at the start of a part, or the sound element within a part. The id attribute refers to the score-instrument affected by the change.

Referenced By

Element score-part

Definition

<xs:complexType name="score-part">
  <xs:annotation>
    <xs:documentation>Each MusicXML part corresponds to a track in a Standard MIDI Format 1 file. The score-instrument elements are used when there are multiple instruments per track. The midi-device element is used to make a MIDI device or port assignment for the given track or specific MIDI instruments. Initial midi-instrument assignments may be made here as well.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="identification" type="identification" minOccurs="0">
      <xsd:annotation>
        <xsd: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.</xsd:documentation>
      </xsd:annotation>
    </xs:element>
    <xs:element name="part-name" type="part-name">
      <xsd:annotation>
        <xsd:documentation>The part-name type describes the name or abbreviation of a score-part element. Formatting attributes for the part-name element are deprecated in Version 2.0 in favor of the new part-name-display and part-abbreviation-display elements.</xsd:documentation>
      </xsd:annotation>
    </xs:element>
    <xs:element name="part-name-display" type="name-display" minOccurs="0">
      <xsd:annotation>
        <xsd:documentation>The part-name-display and part-abbreviation-display elements used in the score.mod file may also be used here to change how a part name or abbreviation is displayed over the course of a piece. They take effect when the current measure or a succeeding measure starts a new system.</xsd:documentation>
      </xsd:annotation>
    </xs:element>
    <xs:element name="part-abbreviation" type="part-name" minOccurs="0">
      <xsd:annotation>
        <xsd:documentation>The part-name-display and part-abbreviation-display elements used in the score.mod file may also be used here to change how a part name or abbreviation is displayed over the course of a piece. They take effect when the current measure or a succeeding measure starts a new system.</xsd:documentation>
      </xsd:annotation>
    </xs:element>
    <xs:element name="part-abbreviation-display" type="name-display" minOccurs="0">
      <xsd:annotation>
        <xsd:documentation>The part-name-display and part-abbreviation-display elements used in the score.mod file may also be used here to change how a part name or abbreviation is displayed over the course of a piece. They take effect when the current measure or a succeeding measure starts a new system.</xsd:documentation>
      </xsd:annotation>
    </xs:element>
    <xs:element name="group" type="xs:string" minOccurs="0" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>The group element allows the use of different versions of the part for different purposes. Typical values include score, parts, sound, and data. Ordering information that is directly encoded in MuseData can be derived from the ordering within a MusicXML score or opus.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="score-instrument" type="score-instrument" minOccurs="0" maxOccurs="unbounded">
      <xsd:annotation>
        <xsd:documentation>The score-instrument type represents a single instrument within a score-part. As with the score-part type, each score-instrument has a required ID attribute, a name, and an optional abbreviation.
A score-instrument type is also required if the score specifies MIDI 1.0 channels, banks, or programs. An initial midi-instrument assignment can also be made here. MusicXML software should be able to automatically assign reasonable channels and instruments without these elements in simple cases, such as where part names match General MIDI instrument names.</xsd:documentation>
      </xsd:annotation>
    </xs:element>
    <xs:sequence minOccurs="0" maxOccurs="unbounded">
      <xs:element name="midi-device" type="midi-device" minOccurs="0" />
      <xs:element name="midi-instrument" type="midi-instrument" minOccurs="0" />
    </xs:sequence>
  </xs:sequence>
  <xs:attribute name="id" type="xs:ID" use="required">
    <xsd:annotation>
      <xsd:documentation>
      </xsd:documentation>
    </xsd:annotation>
  </xs:attribute>
</xs:complexType>