att.plist

Attributes listing the active participants in a user-defined collection.
Module
Attributes
@plist
@plist(optional)When the target attribute is present, plist identifies the active participants; that is, those entities pointed "from", in a relationship with the specified target(s). When the target attribute is not present, it identifies participants in a mutual relationship. One or more values from data.URI, separated by spaces.
@plist(optional)When the target attribute is present, plist identifies the active participants; that is, those entities pointed "from", in a relationship with the specified target(s). When the target attribute is not present, it identifies participants in a mutual relationship. One or more values from data.URI, separated by spaces.
Component declarations that are shared between two or more modules.
@plist(optional)When the target attribute is present, plist identifies the active participants; that is, those entities pointed "from", in a relationship with the specified target(s). When the target attribute is not present, it identifies participants in a mutual relationship. One or more values from data.URI, separated by spaces.
Available at
<annot>Provides a statement explaining the text or indicating the basis for an assertion.
<beatRpt>An indication that material on a preceding beat should be repeated.
<expansion>Indicates how a section may be programmatically expanded into its 'through-composed' form.
<relation>Describes a relationship or linkage amongst entities.
<signifLet>Significantive letter(s).
<arpeg>Indicates that the notes of a chord are to be performed successively rather than simultaneously, usually from lowest to highest. Sometimes called a "roll".
<beamSpan>Alternative element for explicitly encoding beams, particularly those which extend across bar lines.
<bend>A variation in pitch (often micro-tonal) upwards or downwards during the course of a note.
<bracketSpan>Marks a sequence of notational events grouped by a bracket.
<fermata>An indication placed over a note or rest to indicate that it should be held longer than its written value. May also occur over a bar line to indicate the end of a phrase or section. Sometimes called a 'hold' or 'pause'.
<gliss>A continuous or sliding movement from one pitch to another, usually indicated by a straight or wavy line.
<hairpin>Indicates continuous dynamics expressed on the score as wedge-shaped graphics, e.g., < and >.
<harpPedal>Harp pedal diagram.
<lv>A "tie-like" indication that a note should ring beyond its written duration.
<octave>An indication that a passage should be performed one or more octaves above or below its written pitch.
<pedal>Piano pedal mark.
<slur>Indication of 1) a "unified melodic idea" or 2) performance technique.
<tie>An indication that two notes of the same pitch form a single note with their combined rhythmic values.
<tupletSpan>Alternative element for encoding tuplets, especially useful for tuplets that extend across bar lines.
<mordent>An ornament indicating rapid alternation of the main note with a secondary note, usually a step below, but sometimes a step above.
<trill>Rapid alternation of a note with another (usually at the interval of a second above).
<turn>An ornament consisting of four notes — the upper neighbor of the written note, the written note, the lower neighbor, and the written note.
<sp>Contains an individual speech in a performance text.
<stageDir>Contains any kind of stage direction within a dramatic text or fragment.
<cpMark>A verbal or graphical indication to copy musical material written elsewhere.
<metaMark>A graphical or textual statement with additional / explanatory information about the musical text. The textual consequences of this intervention are encoded independently via other means; that is, with elements such as <add>, <del>, etc.
<fing>An individual finger in a fingering indication.
<fingGrp>A group of individual fingers in a fingering indication.
<f>Single element of a figured bass indication.
<harm>An indication of harmony, e.g., chord names, tablature grids, harmonic analysis, figured bass.
<accid>Records a temporary alteration to the pitch of a note.
<artic>An indication of how to play a note or chord.
<attacca>An instruction to begin the next section or movement of a composition without pause.
<dir>An instruction expressed as a combination of text and symbols, typically above, below, or between staves, but not on the staff — that is not encoded elsewhere in more specific elements, like <tempo>, <dynam> or <repeatMark>.
<dot>Dot of augmentation or division.
<dynam>Indication of the volume of a note, phrase, or section of music.
<ornam>An element indicating an ornament that is not a mordent, turn, or trill.
<phrase>Indication of 1) a "unified melodic idea" or 2) performance technique.
<repeatMark> An instruction expressed as a combination of text and symbols – segno and coda – typically above, below, or between staves, but not on the staff.
<tempo>Text and symbols descriptive of tempo, mood, or style, e.g., "allarg.", "a tempo", "cantabile", "Moderato", "♩=60", "Moderato ♩ =60").
<line>A visual line that cannot be represented by a more specific; i.e., semantic, element.
Common Music Notation (CMN) repertoire component declarations.
<arpeg>Indicates that the notes of a chord are to be performed successively rather than simultaneously, usually from lowest to highest. Sometimes called a "roll".
<attacca>An instruction to begin the next section or movement of a composition without pause.
<beamSpan>Alternative element for explicitly encoding beams, particularly those which extend across bar lines.
<beatRpt>An indication that material on a preceding beat should be repeated.
<bend>A variation in pitch (often micro-tonal) upwards or downwards during the course of a note.
<bracketSpan>Marks a sequence of notational events grouped by a bracket.
<fermata>An indication placed over a note or rest to indicate that it should be held longer than its written value. May also occur over a bar line to indicate the end of a phrase or section. Sometimes called a 'hold' or 'pause'.
<gliss>A continuous or sliding movement from one pitch to another, usually indicated by a straight or wavy line.
<hairpin>Indicates continuous dynamics expressed on the score as wedge-shaped graphics, e.g., < and >.
<harpPedal>Harp pedal diagram.
<lv>A "tie-like" indication that a note should ring beyond its written duration.
<octave>An indication that a passage should be performed one or more octaves above or below its written pitch.
<pedal>Piano pedal mark.
<repeatMark> An instruction expressed as a combination of text and symbols – segno and coda – typically above, below, or between staves, but not on the staff.
<slur>Indication of 1) a "unified melodic idea" or 2) performance technique.
<tie>An indication that two notes of the same pitch form a single note with their combined rhythmic values.
<tupletSpan>Alternative element for encoding tuplets, especially useful for tuplets that extend across bar lines.
CMN ornament component declarations.
<mordent>An ornament indicating rapid alternation of the main note with a secondary note, usually a step below, but sometimes a step above.
<trill>Rapid alternation of a note with another (usually at the interval of a second above).
<turn>An ornament consisting of four notes — the upper neighbor of the written note, the written note, the lower neighbor, and the written note.
Dramatic text component declarations.
<sp>Contains an individual speech in a performance text.
<stageDir>Contains any kind of stage direction within a dramatic text or fragment.
Editorial and transcriptional component declarations.
<cpMark>A verbal or graphical indication to copy musical material written elsewhere.
<metaMark>A graphical or textual statement with additional / explanatory information about the musical text. The textual consequences of this intervention are encoded independently via other means; that is, with elements such as <add>, <del>, etc.
Fingering component declarations.
<fing>An individual finger in a fingering indication.
<fingGrp>A group of individual fingers in a fingering indication.
Harmony component declarations.
<f>Single element of a figured bass indication.
<harm>An indication of harmony, e.g., chord names, tablature grids, harmonic analysis, figured bass.
Neume repertoire component declarations.
<episema>Episema.
<hispanTick>Hispanic tick.
<signifLet>Significantive letter(s).
Component declarations that are shared between two or more modules.
<accid>Records a temporary alteration to the pitch of a note.
<annot>Provides a statement explaining the text or indicating the basis for an assertion.
<artic>An indication of how to play a note or chord.
<dir>An instruction expressed as a combination of text and symbols, typically above, below, or between staves, but not on the staff — that is not encoded elsewhere in more specific elements, like <tempo>, <dynam> or <repeatMark>.
<dot>Dot of augmentation or division.
<dynam>Indication of the volume of a note, phrase, or section of music.
<expansion>Indicates how a section may be programmatically expanded into its 'through-composed' form.
<ornam>An element indicating an ornament that is not a mordent, turn, or trill.
<phrase>Indication of 1) a "unified melodic idea" or 2) performance technique.
<relation>Describes a relationship or linkage amongst entities.
<tempo>Text and symbols descriptive of tempo, mood, or style, e.g., "allarg.", "a tempo", "cantabile", "Moderato", "♩=60", "Moderato ♩ =60").
User-defined symbols component declarations.
<line>A visual line that cannot be represented by a more specific; i.e., semantic, element.
Constraints

@plist attribute should have content.
Each value in @plist should correspond to the @xml:id attribute of an element.

Declaration
<classSpec ident="att.plist" module="MEI.shared" type="atts">
<desc xml:lang="en">Attributes listing the active participants in a user-defined collection.</desc>
<attList>
<attDef ident="plist" usage="opt">
<desc xml:lang="en">When the target attribute is present, plist identifies the active participants; that is, those entities pointed "from", in a relationship with the specified target(s). When the target attribute is not present, it identifies participants in a mutual relationship.</desc>
<datatype maxOccurs="unbounded">
<rng:ref name="data.URI"/>
</datatype>
<constraintSpec ident="check_plistTarget" scheme="schematron">
<constraint>
<sch:rule context="@plist">
<sch:assert role="warning" test="not(normalize-space(.) eq '')">@plist attribute should have content.</sch:assert>
<sch:assert role="warning" test="every $i in tokenize(., '\s+') satisfies substring($i,2)=//mei:*/@xml:id">Each value in @plist should correspond to the @xml:id attribute of an element.</sch:assert>
</sch:rule>
</constraint>
</constraintSpec>
</attDef>
</attList>
</classSpec>