diff --git a/_config.yml b/_config.yml index 25123dc6fb0..0aae03b1724 100644 --- a/_config.yml +++ b/_config.yml @@ -69,3 +69,6 @@ sidebar: - id: datatypes label: 'Data Types' url: 'data-types.html' + - id: datatypes + label: 'Macro Groups' + url: 'macro-groups.html' diff --git a/tools/canonicalized4.0.0.xml b/tools/canonicalized4.0.0.xml index 3d8f299ca0c..b2003f0cb5b 100644 --- a/tools/canonicalized4.0.0.xml +++ b/tools/canonicalized4.0.0.xml @@ -1,43 +1,27 @@ - - + The Music Encoding Initiative Guidelines Edited by - Perry Roland - Johannes Kepper + Perry Roland + Johannes Kepper With contributions by - Benjamin Bohl - Andrew Hankinson - Maja Hartwig - Zoltán Kömíves - Laurent Pugin - Kristina Richts - Axel Teich Geertinger - Raffaele Viglianti - Thomas Weber + Benjamin Bohl + Andrew Hankinson + Maja Hartwig + Zoltán Kömíves + Laurent Pugin + Kristina Richts + Axel Teich Geertinger + Raffaele Viglianti + Thomas Weber + Klaus Rettinghaus @@ -45,13091 +29,383 @@ Music Encoding Initiative (MEI) Council - -

Music Encoding Initiative (MEI)

-

NOTICE: Copyright (c) 2018 by the Music Encoding Initiative (MEI) Council.

-

Licensed under the Educational Community License, Version 2.0 (the "License"); you may + +

+ Music Encoding Initiative (MEI) +

+

NOTICE: Copyright (c) 2018 by the Music Encoding Initiative (MEI) Council.

+

Licensed under the Educational Community License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://opensource.org/licenses/ECL-2.0.

-

Unless required by applicable law or agreed to in writing, software distributed under +

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

-

This is a derivative work based on earlier versions of the schema copyright (c) +

This is a derivative work based on earlier versions of the schema copyright (c) 2001-2006 Perry Roland and the Rector and Visitors of the University of Virginia; licensed under the Educational Community License version 1.0.

-

CONTACT: contact@music-encoding.org

+

CONTACT: contact@music-encoding.org

- -

+ +

- + - - - - - - Music Encoding Initiative Guidelines - - - - Version 3.0.0 - - Prepared and maintained by the Music Encoding Initiative Council -
- -
- - - Edited by Perry Roland and Johannes KepperWith contributions by Benjamin Bohl, - Andrew Hankinson, Maja Hartwig, Zoltán Kömíves,Laurent Pugin, Kristina Richts, Raffaele - Viglianti, and Thomas Weber - - - - © by the Music Encoding Initiative (MEI) Council. - Charlottesville and Detmold2016 - - Licensed under the Educational Community License, Version 2.0 (the "License"); - you may not use this file except in compliance with the License. You may obtain a - copy of the License at http://www.osedu.org/licenses/ECL-2.0. - -
- - -
- - - -
- Acknowledgments -

Many institutions and individuals assisted in the preparation of these Guidelines and in the - overall development of the Music Encoding Initiative (MEI) schema.

-

Grateful acknowledgment is given to the following institutions for their generous - contributions: the National Endowment for the Humanities (NEH) and the Deutsche - Forschungsgemeinschaft (DFG) for their joint financial support of the MEI project, the - Institute for Advanced Technology in the Humanities (IATH) at the University of Virginia and - the Hochschule für Musik in Detmold for graciously hosting grant-funded meetings, the Center - for Computer-Assisted Research in the Humanities (CCARH) at Stanford University for permission - to make use of their large collection of encoded music, and the Distributed Digital Music - Archives & Libraries (DDMAL) Lab at McGill University and the Social Sciences and - Humanities Research Council of Canada (SSHRC) for their continuing support of MEI-based - research. The Akademie der Wissenschaften und der Literatur in Mainz deserves special - recognition for being the official host of MEI and promoting its use through their granting - activities. Finally, the editors wish to thank their own home institutions, the - Musikwissenschaftliches Seminar Detmold/Paderborn and the University of Virginia Library, for - providing financial support and environments that encourage experimentation.

-

The Text Encoding Initiative is also owed a special debt of gratitude. In addition to - providing much of the inspiration for MEI, the TEI organization supplied funding for the MEI - Technical Group in its efforts to adopt ODD. The editors of these Guidelines are grateful for - those of the TEI, which provided a stellar exemplar and from which we have borrowed - shamelessly.

-

The following individuals have provided much-appreciated commitments of time and energy to - the development of MEI: Donald Byrd (Indiana University, Bloomington); Giuliano Di Bacco - (Indiana University); Richard Freedman (Haverford College); Ichiro Fujinaga (McGill - University, Montréal); Andrew Hankinson (McGill University); Erin Mayhood (University of - Virginia Library); Stefan Morent (University of Tübingen); Daniel Pitti (Institute for - Advanced Technology in the Humanities, University of Virginia); Laurent Pugin (RISM - Switzerland); Daniel Röwenstrunk (Musikwissenschaftliches Seminar Detmold/Paderborn); Craig - Sapp (Center for Computer-Assisted Research in the Humanities, Stanford University); Eleanor - Selfridge-Field (Center for Computer-Assisted Research in the Humanities, Stanford); Christine - Siegert (Beethoven-Haus, Bonn); Axel Teich Geertinger (Royal Danish Library, Copenhagen); - Joachim Veit (Carl-Maria-von-Weber-Gesamtausgabe, Detmold); and Raffaele Viglianti (University - of Maryland, College Park).

-

Thanks to Bernhard R. Appel (Beethoven-Haus); J. Stephen Downie (University of Illinois, - Urbana-Champaign); Oliver Huck (Universität Hamburg); Fotis Jannidis (Universität Würzburg); - and Frans Wiering (University of Utrecht) for providing expertise on a wide range of topics - related to music notation modelling.

-

Also thanks to Syd Bauman and Terry Catapano for their invaluable problem-solving assistance - during the development of the 2010 RNG schema. Thanks to the late Sebastian Rahtz and James - Cummings of the Text Encoding Initiative (TEI) for their help with making ODD work with MEI, - their assistance in more closely aligning MEI and TEI, and their quick responses to questions - and Roma bug reports.

-
-
- Introduction -

This release of the Music Encoding Initiative (MEI) provides three major components:

- - formalized rules for recording the intellectual and physical characteristics of music - notation documents so that the information contained in them may be searched, retrieved, - displayed, and exchanged in a predictable and platform-independent manner; - a data dictionary that documents the components of the MEI model; and - best practices guidelines for the application of those rules. - -

Both the MEI rules and their documentation are expressed in the form of a One Document - Does-it-all (ODD) document, a format developed by the Text Encoding Initiative (TEI). The MEI - ODD document has been processed to create the MEI application guidelines, data dictionary, and - accompanying schemas.

-

The MEI Guidelines, which include the data dictionary, are intended to serve as a reference - tool for music encoders. Through the use of natural-language definitions and examples, this - document assists users of MEI in achieving effective and consistent markup. Despite - translating XML and RNG terminology and concepts into more accessible language, it is still a - technical one that presupposes a minimal understanding of XML and music notation. Novice - encoders will need to supplement their use of the Guidelines by participating in discussions - on the MEI-L list, attending introductory MEI workshops and training classes and by referring - to other information sources.

-

As a natural-language translation of the MEI conceptual model, the Guidelines convey - information about the three principal tasks accomplished by the model. First, the model breaks - down the content of music notation documents into data fields or categories of information - called "elements". All of these elements are named, defined, and described in the data - dictionary. Second, the data dictionary identifies and defines attributes associated with - those elements. Attributes are characteristics or properties that further refine the element. - Last, and perhaps most importantly, the data dictionary documents the structure of the MEI - model by explaining the relationship between elements, specifying where the elements may be - used and describing how they may be modified by attributes. While two of the basic purposes of - MEI encompass the searching and display of encoded music notation documents in an electronic - environment, nothing in the data dictionary specifically addresses their implementation. - Searching and display are entirely dependent on software applications outside the scope of the - MEI model.

-

The MEI model contains only a few required elements, the majority are optional. Therefore, - the amount of markup desired will vary from one situation to another depending on - intellectual, technical, and temporal considerations. Creating encoded music notation - documents for inclusion in union databases may also result in tagging requirements that are - separate from those dictated by the model.

-

Suggestions for new elements, revised descriptions, and more illustrative examples may be - submitted to the MEI Working Group via the MEI discussion list at mei-l@lists.uni-paderborn.de. The model and - Guidelines will be updated periodically based on the feedback received from the users of - MEI.

-
-
- MEI Design Principles -

This section of the Guidelines defines principles and criteria for designing, developing, and - maintaining an XML-based encoding scheme for music notation documents.

- - Definitions and Parameters - A music notation document is one that contains music notation; that is, any one of a - number of "visual analogues of musical sound, either as a record of sound heard or imagined, - or as a set of visual instructions for performers." (Ian D. Bent, et al. "Notation." Grove - Music Online. Oxford Music Online. 25 May 2010. <http://www.oxfordmusiconline.com/subscriber/article/grove/music/20114>.) - The encoding scheme permits both the creation of new music notation documents and the - conversion of existing ones from print and other electronic formats. However, conversion of - existing documents may require revisions in content or rearrangement of information. - - - General Principles - No prima facie distinction is made between a primary source of music notation, such as - an autograph or published score, and a secondary source, such as a scholarly edition based - on one or more primary sources. The tag set encompasses both, and the encoder must choose - the elements and attributes most appropriate in each case. - As an encoded representation of one or more music notation documents, an MEI file may be - employed as a surrogate for the original materials. - Although the encoding scheme does not define or prescribe intellectual content for music - notation documents, it does define content designation and is intended to be used with - available data content standards. MEI identifies the essential data elements within music - notation documents and establishes codes and conventions necessary for capturing and - distinguishing information within those elements for future action or manipulation. While - there are a few elements that ought to appear in any MEI document, various intellectual, - technical, and economic factors influence the level of detail of analysis and encoding - actually undertaken. Taking this into consideration, the encoding scheme is designed with a - minimum of required elements and allows for progressively more detailed levels of - description as desired. - The encoding scheme preserves and enhances the current functionality of existing music - notation documents. It permits identification of document structures and content that - support description, navigation, analysis, and online and print presentation. - The encoding scheme is intended to facilitate interchange between notational tools. It - aims to assist in the creation of more effective and consistent encoding, encourage the - creation of cooperatively-created and widely available databases of music notation - documents, and permit the reuse of encoded data for multiple output purposes. It will also - ensure that machine-readable music notation documents will outlive changing hardware and - software environments because they are based on a platform-independent standard. - - - Structural Features - The encoding scheme is based on eXtensible Markup Language (XML), a text-based format - for representing structured information. It is expressed as a One Document Does-it-all (ODD) - document, referred to as the "Music Encoding (MEI) Guidelines". For more information on ODD, - please refer to TEI Guidelines chapter 22 (http://www.tei-c.org/release/doc/tei-p5-doc/en/html/TD.html), chapter 23 (http://www.tei-c.org/release/doc/tei-p5-doc/en/html/USE.html), and to the TEI's - "Getting Started with P5 ODDs" document (http://www.tei-c.org/Guidelines/Customization/odds.xml). - Related or complementary standards, such as the Text Encoding Initiative (TEI) - Guidelines for Electronic Text Encoding and Interchange (http://www.tei-c.org/Guidelines/P5/), - the Encoded Archival Description (EAD) (http://www.loc.gov/ead/), MARC 21 Format for Bibliographic Data (http://www.loc.gov/marc/bibliographic/ecbdhome.html), existing notation encoding - schemes, etc. have been consulted and employed as appropriate. For example, the data model - includes a header that is comparable to the TEI header, and TEI and EAD naming conventions - and tag structures have been used whenever feasible. However, while some feature names are - similar, or even the same, it is important to recognize that MEI and TEI have different - semantic scope. Obviously, a note element in MEI does not carry the same meaning as the - element of the same name in TEI. Perhaps less obviously, a phrase in music notation is - unrelated to a textual phrase. - With respect to metadata, MEI recognizes the close relationship between the metadata - content found in the MEI header and that of catalog records, authority records, and finding - aids, and it provides for the use of an encoding equivalency attribute for MEI elements - corresponding to fields in other metadata standards. - To ensure broad international and multi-repertoire application of MEI, existing musical - terminology was used in building the data model where practical. In addition, a method for - localization of the data model's names has been provided. Finally, extensive use of - attributes in the schema permits the refinement of element meanings with specific musical, - geographic, or temporal contexts. - - - Control and Maintenance - Control and maintenance of the MEI model, schemas and documentation will be provided by - a maintenance agency working in concert with the national and international music - communities, assisted in an advisory capacity by other interested groups of users. - -
-
- About Version 3.0.0 -

The first major goal established for the 3.0.0 release was to refine the MEI object model; - that is, identify and correct problems affecting MEI’s ability to capture data conveniently - and effectively. While a few revisions modified the class structure of MEI without changing - the resulting schema — mostly for schema construction convenience and "future proofing" - reasons, but also to maintain compliance with recent changes to the TEI ODD framework — the - usual outcome was the creation of both restrictions and extensions to the existing model. - Extensions, such as allowing Scalable Vector Graphics (SVG) markup in certain contexts, adding - new elements, and providing additional attributes on existing elements, presented no backward - compatibility problems. Restrictions, however, such as separating data that had been recorded - in a single attribute value into multiple attributes, moving elements from one location to - another, tightening the definitions for datatypes, and adding new contextual constraints, - resulted, as they usually do, in backward compatibility issues. To mitigate the effect of - these compatibility problems, an XSLT stylesheet (mei21To30.xsl) was created that converts a - file conforming to the previous version of MEI to one that validates against the - mei-all_anyStart schema in this release. Every effort was made to thoroughly test this - transformation. However, since the corpus of files available for testing was relatively small - and its contents were somewhat homogenous, no guarantee is made that the conversion will be - successful in all cases. Problems with the conversion reported to MEI-L or contact@music-encoding.org will be evaluated and - addressed.

-

Another major goal for this release was improvement of the Guidelines, including the - reference section formerly known as the "Tag Library", now called the "Data Dictionary". The - changes here included correction of typographical and grammatical errors, designating - annotations previously given in XML comments as formal remarks, and reworking some parts of - the document to make them more concise and (we hope) more informative.

-

To see all of the changes made for this revision, please visit the Git repositories https://github.com/music-encoding/music-encoding, https://github.com/music-encoding/encoding-tools, and https://github.com/music-encoding/sample-encodings.

-

The editors wish to thank everyone who participated in this process. Of course, errors are - the sole responsibility of the editors.

-
- - -
- Shared Elements, Models, and Attributes -

This chapter describes the elements, models, and attributes that are part of the MEI.shared - module. The shared module contains declarations that are common to two or more other - modules.

-
- - Structural Elements -
- Document Elements -

The following elements are available for the representation of the outermost structure of - an MEI document:

-

- - - - - - - -

-

A typical MEI document contains an mei element, which in turn - contains metadata, represented by an meiHead element, and the musical - text itself, represented by a music element. The meiHead element, formally declared in the MEI.header module, is described in chapter - .

-

Other variations on this basic form are also available for the representation of a:

- - collection of related MEI-encoded texts, each with its own metadata, known as a - corpus - document that contain only metadata, known as an independent or stand-alone - header - music notation markup without metadata, typically intended to be embedded within - another kind of markup, such as TEI - -

Further information regarding the organization and encoding of music corpora is given in - chapter . Stand-alone headers are more fully described in chapter - .

-

Inclusion of MEI encodings (partial or complete) inside Text Encoding Initiative (TEI) - documents is covered in the TEI Guidelines at http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html#FTNM and by the TEI - Music Special Interest Group at http://www.tei-c.org/SIG/Music/twm/index.html.

-
-
- Music Element -

MEI texts may be regarded either as unitary; that is, forming an organic whole, or as - composite; that is, consisting of several components which are in some important sense - independent of each other. The distinction is not always entirely obvious. For example, a - collection of songs might be regarded as a single item in some circumstances, or as a number - of distinct items in others. In such borderline cases, the encoder must choose whether to - treat the text as unitary or composite; each option may have advantages and - disadvantages.

-

Whether unitary or composite, the musical text is marked with the music tag and may contain front matter, a body, and back matter. In unitary texts, - the body is tagged using the body element; in composite texts, - however, where the textual body consists of a series of subordinate musical texts or other - groups, it is tagged with the group element. The overall structure of - any musical text, unitary or composite, is thus defined by the following elements:

-

- - - - - - -

-

Critical editions and collections of works often contain extensive text, such as a title - page, table of contents, an introductory essay, commentary, biographical sketch, index, etc. - These textual items may appear in either the front or back elements. The front and back - elements, available only when the MEI.text module is activated, are described more fully in - chapter .

-

The overall structure of a single musical text is:

- - - - - - - - - - - - - - - - - - -

The top-level structure of a composite musical text made up of two unitary musical texts - is:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Grouped Texts -

The group element may be used to represent a collection of - independent musical texts which is to be regarded as a single unit for processing or other - purposes. It is provided to simplify the encoding of collections, anthologies, and cyclic - works. It can also be used to record the potentially complex internal structure of - corpora, covered more fully in chapter .

-

- - - -

-

Examples of composite texts which may be represented using the group element include anthologies and other collections. The presence of common - front matter referring to the whole collection, possibly in addition to front matter - relating to each individual musical text, is a good indication that a given musical text - might usefully be encoded in this way.

-

For example, the overall structure of a collection of songs might be encoded as - follows:

- - - - - - - - - -

A group of musical texts may contain other unitary and grouped texts:

- - - - - - - - - - - - -

The group element may be used to encode any kind of collection in - which the constituents are regarded by the encoder as works in their own right, such as - ad hoc single- or multiple-composer collections or anthologies of - works not originally conceived of as a single composition.

-
-
- Divisions of the Body -

This section describes sub-division of the body of a musical text. Front and back matter - are described in chapter .

-

The body of a unitary musical text may contain one or more discrete, linear segments. The - names commonly used for these structural subdivisions vary with the genre, style, and time - period of the music, or even at the whim of the author, editor, or publisher. For example, - a major subdivision of a symphony is generally referred to as a ‘movement’. An opera, on - the other hand, is usually organized into ‘acts’ and then further by ‘scenes’. All such - divisions are treated as occurrences of the same neutrally-named element, with a - type attribute used to categorize them independently of their hierarchic - level.

-

The following element is used to identify musical subdivisions. As a member of the class - att.typed, the mdiv element has attributes which can be used to - classify it according to a two-tier hierarchy.

-

- - - - -

-

To accommodate "divisions within divisions", an mdiv element may - contain additional mdiv sub-elements nested to any level required. - For example, the encoding of a multi-movement work, such as a symphony, frequently have - the following structure:

- - - - - - - - - - - - - - - - - - -

while dramatic works, such as Verdi's opera, Il Trovatore, often exhibit a - more deeply-nested structure:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Conventionally, in performance the musical structures represented by mdiv elements are separated by pauses; however, attacca, - attacca subito, seque, or similar terms are - sometimes used at the end of an mdiv to indicate that the next mdiv should begin immediately after the conclusion of the current one. - These terms have no effect, however, on the logical segmentation of musical content using - mdiv elements. - -

-
-
- Content of Musical Divisions -

The mdiv element may contain one or both of two possible views: - score and parts.

-

- - - - -

-

The score element represents notation in which all the parts of an - ensemble are arranged on vertically aligned staves, while the parts - element collects the individually notated parts for each performer or group of performers. - The explicit encoding of these two views is necessary because it is - not always possible or desirable to automatically derive one view from the other. In - addition, separating scores and parts can eliminate a great deal of markup complexity.

- - - - - - - - - - - - - -

The score and parts elements may also be - employed to accommodate different methods of organizing the markup – with no particular - presentation implied. In this case, software may render a collection of parts as a score - or a score as a collection of parts.

-

Within the collective parts element, notation for a single - performer is represented by the part element:

-

- - - -

-

A part is effectively a small-scale score, allowing all the - encoding features of a full score, such as multiple staves, performance directives, and so - on. A group of part element is useful for encoding performing parts - when there is no score, such as in early music part books; when the parts have - non-aligning bar lines; when different layout features, such as page turns, are needed for - the score and parts; or for accommodating software that requires part-by-part - encoding.

-

Please note that part elements in MEI are not an indication of - voice leading or staff grouping. Voice leading can be encoded using the next - attribute, available on all the members of the model.eventLike - class. The staffGrp element handles grouping of staves in the score - context.

- - - - - - - - - - - -

In both score and part views, the scoreDef element is used to - describe logical characteristics of the encoded music, such as key signature, the sounding - key (as opposed to the notated key signature), meter, etc., and visual features, such as - page size, staff groupings and display labels, etc. The staffGrp - elements within scoreDef and the order of staffDef elements inside staffGrp should follow the score - order of the source for the encoding.

-

A part or score may be further divided into - linear segments called "sections".

-

- - - -

-

section elements are often used as a scoping mechanism for clef - signs, key and meter signatures, as well as metronome, tempo, and expression markings. - Using section elements can help to minimize the need for backward - scanning to establish context when the starting point for access is not at the beginning - of the score. section elements may also be used for other - user-defined, i.e., analytical or editorial, purposes and may therefore be arbitrarily - nested to any desired level.

-

The ending element shares the same model as the section element. Unlike section, however, it may not be - recursively nested.

-

- - - -

-

The most common (non-analytical, non-editorial) use of section and - ending elements is illustrated below:

- - - - - -
- -
- - - - - - -
- -
- - - - - -

Within section elements, several methods of organization are - possible, depending upon the notational style of the source material and the encoder's - needs. For example, when the MEI.cmn module is used, the default organization is - measure-by-measure, with staff and layer - sub-elements within each measure. Further discussion of CMN notation - is continued in chapter .

-

However, staff-by-staff organization is more appropriate for music without measures and - is provided when either the MEI.mensural or MEI.neumes module is employed. Coverage of - mensural notation is provided in chapter , while describes neumatic notation.

-

It must be noted that, when both the MEI.cmn and MEI.mensural modules are available, it - is possible to encode CMN notation without using measure elements; - that is, staff-by-staff organization may be used and the ends of measures marked using barLine elements.

- -

In certain circumstances, this approach may be preferable for reproduction of the visual - layout of the music. However, the simultaneous use of the measure - and barLine elements may lead to confusion and should be - avoided.

-

Typically, MEI follows the order of sections as they appear in the document being - encoded. When performance requires a different order, for instance in the case of D.C. and - D.S. directives, the following element may be used to define the performance order.

-

- - - -

-

In the following example, expansion is used to indicate how the - notated sections should be ordered in a "through-composed" rendition, for example for - machine performance or analysis. The plist attribute contains an ordered list of - identifiers of descendant section, ending, lem, or rdg elements. The sequence of values in - the plist attribute indicates that the section labelled 'A' comes first, then the section - labelled 'B', followed by the 'A' section again. This mechanism must be specified - independently of any textual directives, such as "Da capo" or "D.S. al Fine", that may be - present in the document.

- - - - - -
- -
- -
-
- -
-
- - - - - -
-
-
-
- - Shared Musical Elements -

This section lists the elements defined in the shared module that are available within the - music element.

-
- Score and Parts -

The following elements are provided for the capture of scores and parts:

-

- - - - - - - - - - - - - - - -

-

The character of elements specifying one or more score or staff parameters, such as meter - and key signature, clefs, etc., is that of a milestone; that is, they affect all subsequent - material until a following redefinition. A scoreDef element, which may - affect more than just one staff, is allowed only within score, part and section elements, whereas staffDef is allowed only within staffGrp, staff and layer. A staffDef - nested inside a staff must bear the same value for its n - attribute as its parent staff and may thus not affect other staves.

-

The actual use of these elements depends on the repertoire and historical context of the - source material. For details on their use in Common Western Notation, please refer to - chapter .

-
-
- Staves and Layers -

The elements below are used to capture the logical organization of musical notation:

-

- - - - -

-

The actual use of the staff and layer elements - depends on the repertoire and historical context of the source material. For details on - their use in Common Western Notation, please refer to chapter . - For mensural notation, see chapter , and for neumatic notation, - chapter .

-
-
- Basic Music Events -

The basic features of music notation are represented by the following elements:

-

- - - - - -

-

The characteristics of stems on notes and chords are indicated by means of attributes found - in the att.stems class.

-

- - - -

-
-
- Other events -

Because they can occur in the context of a stream of events on the staff, some elements - which are used in other contexts are also treated as events. For example, in addition to - being used to define the initial clef of a staff, the clef element can - also be used to indicate a clef change.

-
- Key Signatures and Clefs -

Key signatures and clefs as well as intra-staff changes to these musical parameters are - treated as events.

-

- - - - - - -

-
-
- Bar Lines and Custos Signs -

Measure separators, i.e., bar lines, and custos signs are also considered to be - events.

-

- - - - -

-
-
- Accidentals, Articulation Symbols, Augmentation Dots, and Custos Signs -

The following elements are regarded as events primarily because they sometimes occur - independently of any associated notes, rests, or chords, especially in mensural and neume - repertoires.

-

- - - - - -

-
-
- Lyric Syllables -

The syl element is used to mark a word or portion of a word that is - to be vocally performed. A fuller description of its use is provided in chapter .

-

- - - -

-
-
- Event Spacing -

The following elements provide control over the horizontal spacing of notational events, - such as notes, chords, rests, etc.:

-

- - - - -

-

In this context, the term space is used to mean whitespace that is - required to meaningfully align multiple voices in a multi-voice texture. In DARMS these - were referred to as push codes. The space - element is most often used when a new voice appears on a staff mid-measure.

- -

The space element may also be used to align material that crosses - staves.

- -

Space can be thought of as another kind of event. In fact, some - refer to this concept as an invisible rest.

-

While space is meaningful, padding is - non-essential whitespace that is used to shift the position of the events which - follow.

- -

The pad element is provided in order to capture software-dependent - placement information when it is desirable to do so. Unless the MEI file will be used as - an intermediate file format, this is usually not necessary.

-
-
-
- Expression Marks -

Expression marks are instructions in the form of words, abbreviations, or symbols that - convey aspects of performance that cannot be expressed purely through the musical - notation.

-
- Text Directives -

All of the following elements can be considered text directives; however, MEI uses the - dir element specifically for words, abbreviations, numbers, or - symbols specifying or suggesting the manner of performance that are not encoded elsewhere - using the more specific elements of tempo and dynam.

-

- - - -

-

Examples of directives include text strings such as 'affettuoso', fingering numbers, or - music symbols such as segno and coda symbols or fermatas over a bar line. Directives can - be control elements. That is, they can linked via their attributes to other events. The - starting point of the directive may be indicated by either a tstamp, tstamp.ges, - tstamp.real or startid attribute, while the ending point may be recorded by either a - tstamp2, dur, dur.ges or endid attribute. It is a semantic error not to specify a starting - point attribute.

- -
-
- Tempo -

Tempo marks are indications through words, abbreviations, or specific metronome settings - of the speed at which a piece of music is to be performed. Both instantaneous and - continuous tempo markings may be encoded using this element.

-

- - - -

-
-
- Dynamics -

Dynamics, or dynamic marks, are terms, abbreviations, and symbols that indicate the - specific degrees of volume of a note, phrase, or section of music, e.g., "piano", "forte". - Transitions from one volume level to another, e.g., "crescendo", "diminuendo", are also - specified through dynamic marks.

-

- - - -

-
-
- Phrase Marks -

Phrase marks are curved lines placed over or under notes to delineate short sections of a - work that represent a unified melodic idea, analogous to a phrase in literature.

-

- - - - -

-

MEI maintains a distinction between phrase marks and slurs, the latter being curved lines - over or under a sequence of notes indicating they are to be performed using a particular - playing/singing technique, notes that should be taken in a single breath by wind - instruments or played by string instruments using a single stroke of the bow. Often, a - slur also indicates that the affected notes should be played in a - legato manner.

-

Even so, it is common for both of these concepts to be referred to generically as - "slurs". Therefore, unless one is encoding music from a repertoire in which this - distinction is important, the slur element should be preferred over - phrase.

-
-
- Ornaments -

Ornaments are formulae of embellishment that can be realized by adding supplementary - notes to one or more notes of the melody.

-

- - - -

-

MEI provides a generic element for encoding an ornament symbol that is not a mordent, - turn, or trill. For those common CMN ornaments, please refer to .

-

Ornaments can be represented as textual strings (e.g. with a Unicode symbol) or with a - user defined symbol. Ornaments can be control elements. That is, they be can linked via - their attributes to other events. It is a semantic error not to specify a starting point - attribute with either tstamp or startid.

-
-
-
-
- - Shared Textual Elements -

This section lists elements declared in the shared module that pertain to the encoding of - prose.

-
- Paragraphs -

A paragraph is a structural unit of a larger text. Usually, it is typographically distinct; - that is, it usually begins on a new line and the first letter of the content is often - indented, enlarged, or both. This element has a similar meaning as the corresponding - elements in Encoded Archival Description (EAD), Text Encoding Initiative (TEI), and - HTML.

-

- - - -

-

In MEI, a p is used in many different situations, including - transcriptional use within a titlePage or descriptive purposes as in a - changeDesc.

-
-
- Text Rendition -

Sometimes, it is desirable to capture the typographical qualities of a word or phrase - without assigning it a special meaning. For this purpose, MEI offers the rend element, similar to TEI's hi element. Using CSS-like values, - its rend attribute can be used to specify many typographic features, such as font - style, font variants, and relative font size and weight. In addition, text decoration, - direction, and enclosing boxes may be captured. While rend - is used to record relative font size and weight, absolute values for these qualities - (measured in printers points) should be specified using the fontsize and - fontweight attibutes. In addition to commonly found typographical qualities, - MEI provides the altrend attribute for the capture of additional, user-defined - rendition information.

-

- - - - -

-
- -
- Transcription of Titlepages -

A specialized element is furnished for the capture of titlepage information.

-

- - - -

-

The titlePage element, modelled after a similar element in Encoded - Archival Description (EAD), may occur within the textual matter preceding or following the - musical content of the encoding. Since a diplomatic transcription of the titlepage is often - necessary to accurately identify musical material contained within a source, titlePage may also be used within the metadata header as a child of the - physDesc element.

-
-
- Names, Dates, Numbers, Abbreviations, and Addresses -
- Names and Dates -

The name and date elements may be used to - mark up portions of a text that function as names or dates.

-

- - - - -

-

The name element is intended for generic applications and may be - used to identify any named entity, such as a person, item, application, place, etc. The - namesDates module documented in offers the more specific - elements persName, corpName and geogName.

-
-
- Numbers -

The num element may be used to identify any numeric information in - a text. The unit may be used to specify the unit of measurement.

-

- - - - -

-

This element is useful when it is necessary to provide specific information about numeric - data, such as the unit of measurement or the kind of quanity described, or when it should - be displayed in a special manner.

-
-
- Addresses -

Addresses may be encoded using the address element, which itself - may hold an arbitrary number of addrLine elements.

-

- - - - -

-

It is important to note that the address element does not hold a - reference to the person or organization whose address is specified. This must be provided - in a separate element, as in the following example:

- -

- Universität Paderborn -

- Warburger Straße 100 - 33098 Paderborn - Germany -
-

- -
-
-
- Annotations -

Annotations are one of the most versatile features of MEI. They are provided using the annot element.

-

- - - -

-

This element may be contained by a wide range of other elements and may contain a large - number of other elements. While this offers great flexibility in addressing the wide variety - of textual features that might occur within an annotation, it may lead to markup that cannot - be effectively processed mechanistically.

-

In all cases, annot provides a comment upon a feature of the - encoding, but never contains textual transcription. Depending on its context, an annotation - will deal with either its parent element, or, more usually, with the element(s) specified in - its plist attribute. This attribute uses URI references to link to one or more - other elements using their xml:id attribute values, as in the following - example:

- - - - - - - - -
- -
- Bibliographic Citations and References -

The following element is used in the encoding of bibliographic citations and - references:

-

- - - -

-

The bibl element may contain a mix of text and more specific - elements, including the following:

-

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

-

These elements fall into the following categories: - identification of the bibliographic entity and those responsible for its - intellectual content - publication and distribution data for the bibliographic entity - description of the physical characteristics of the item - annotation of the bibliographic citation and additional details regarding the item's - intellectual content - -

-

The elements title, edition, series, and identifier fall into the first category as do the - elements arranger, author, composer, librettist, lyricist, funder, sponsor, and respStmt. The respStmt element is provided for marking responsibility roles that - cannot be recorded using more specific elements. The biblScope element - also carries information of an identifying nature.

-

The identifier for a given item may be an International Standard - Book/Music Number, Library of Congress Control Number, a publisher's or plate number, a - personal identification number, an entry in a bibliography or catalog, etc.

-

To classify the title according to some convenient typology, the - type attribute may be used. Sample values include: main (main title), - subordinate (subtitle, title of part), abbreviated (abbreviated form of title), alternative - (alternate title by which the work is also known), translated (translated form of title), - uniform (collective title). The type attribute is provided for convenience in - analysing titles and processing them according to their type; where such specialized - processing is not necessary, there is no need for such analysis, and the entire title, - including subtitles and any parallel titles, may be enclosed within a single title element. Title parts may be encoded in title - sub-elements. The name of the list from which a controlled value is taken may be recorded - using the authority attribute.

-

Publication and distribution data may be captured using pubPlace, publisher, distributor, and date elements directly inside bibl when the citation is - unstructured. However, these elements should be grouped within imprint - whenever practical.

-

The physical characteristics of the cited item may be described using the extent element.

-

Annotation of the bibliographic citation and the provision of other pertinent details are - addressed by several elements. Commentary on the bibliographic item or citation is - accommodated by the annot and creation elements. - The annot element is provided for generic comments, while creation is intended to hold information about the context of the - creation of the cited item. Terms by which the bibliographic item can be classified may be - placed in genre. For letters and other correspondence, recipient captures the name of the person or organization to whom the - item was addressed. The natural language(s) of the item may be recorded in one or more textLang elements. Finally, a holding institution may be documented - using the repository element directly within bibl, but physLoc should be used whenever possible as a - grouping mechanism for location and shelfmark information. To identify sub-units of the - holding institution, repository sub-elements may be used. The name of - the list from which a controlled value for the agency name is taken may be recorded using - the authority attribute.

-

When supplied with a target attribute, bibl may function - as a hypertext reference to an external electronic resource. In addition, other related - bibliographic items may be described or referenced using the relatedItem element.

- - - letter - Carl Nielsen - Gustav Hetsch - - 1915-04-08 - - - - DK-Kk - - CNA IAc - - - - CNB - V/210 - - - - -

Please consult and for - more information about recording the names and dates frequently found in bibliographic - citations.

-
- -
- Related Items -

In some situations it is necessary to provide references from one bibliographic item to - another. For these situations, MEI offers the relatedItem element. A - relatedItem may be used inside of bibl, and - may either point to a different entity using its target attribute, or may hold - the related item as a child.

- - - letter - Carl Nielsen - Gustav Hetsch - - 1915-04-08 - - - - DK-Kk - - CNA IAc - - - - CNB - V/210 - - - - -

In this example, the nested relatedItem / bibl - provides information about the container where the outer bibl may be found. The kind of relation is expressed using the - rel attribute. It describes the relationship of the child bibl to the relatedItem's parent bibl.

-

- - - -

-

In these relations, the subject is always the relatedItem, and the object is always the - parent of the relatedItem. Thus, a value of rel="preceding" indicates that the - resource described within the relatedItem (or referenced by its target attribute) - precedes the bibl containing the relatedItem. - Following MODS, both values of "preceding" and "succeeding" indicate a temporal order.

-

It is important not to confuse relatedItem with the concepts of FRBR; see .

-
- -
-
- Common Attributes -

The following attributes, provided by the att.common attribute - class, are available on nearly all elements in an MEI encoding. They provide the means to - identify, label, and access elements in MEI-encoded files.

-

- - - -

-

The value of the xml:id attribute serves as an identifier for an element and its - content. Its value must be unique in the context of the current document and must conform to - the definition of an XML Name provided by the W3C Recommendation at http://www.w3.org/TR/xml/#NT-Name. - Suggestions for constructing an ID value can be found at http://www.w3.org/TR/xml/#sec-suggested-names.

-

The xml:id attribute may take values similar to the following:

- - - - - - - - -

This is an example of an incorrectly-formulated xml:id value:

- - - - - -

The label and n attributes both serve a labeling function; however, - they differ in the values they allow. The n attribute must be a single token, while - label may contain a string value that includes spaces. This makes - label useful for the capture of free-text labels, but a name or number specified - with n may be easier to process.

- - - … - - - - - -

When a reference to an external entity is not a complete URI, the xml:base - attribute can record a value against which it can be resolved into a complete, or absolute, - location.

- - - -

The value of xml:base can be inherited from an ancestor. In the following example, - the values of the graphic elements' target attribute can be completed by the - xml:base value specified for the facsimile element:

- - - - - - - - -

See http://www.w3.org/TR/xmlbase/ for more - details on xml:base.

-
- -
-
- The MEI Header -

This chapter addresses the description of an encoded item so that the musical text, as well as - its sources, encoding, and revisions are all thoroughly documented. Such documentation is - necessary for scholars using the texts, for software processing them, and for catalogers in - libraries and archives. Together these descriptions and declarations provide an electronic - analog to the title page attached to a printed work. They also constitute an equivalent for the - content of the code books or introductory manuals customarily accompanying electronic data - sets.

-

Every MEI-conformant text not embedded in another XML carrier that provides for capturing - metadata, such as TEI or METS, must carry a set of descriptions, prefixed to it and encoded as - described in this chapter. This set is known as the MEI header, tagged meiHead, and has six major parts:

- - zero or more alternative identifiers, tagged with altId, each of - which provides an identifying name or number associated with the file. - a file description, tagged fileDesc, containing a full - bibliographic description of the computer file itself, from which a user of the text could - derive a proper bibliographic citation, or which a librarian or archivist could use in - creating a catalog entry recording its presence within a library or archive. The term - computer file here is to be understood as referring to the whole intellectual - entity or document described by the header, even when this is stored in multiple physical - operating system files. The file description also includes information about the source or - sources from which the electronic document was derived. The MEI elements used to encode the - file description are described in section below. - an optional encoding description, tagged encodingDesc, - which describes the relationship between an electronic text and its source or sources. It - allows for detailed description of whether (or how) the text was normalized during - transcription, how the encoder resolved ambiguities in the source, what levels of encoding or - analysis were applied, and similar matters. The MEI elements used to encode the encoding - description are described in section below. - an optional work description, tagged workDesc, - containing classification and contextual information about the work, such as its subject - matter, the situation in which it was produced, the individuals described by or participating - in producing it, and so forth. Such a work profile is of particular use in highly structured - composite texts such as corpora or language collections, where it is often highly desirable to - enforce a controlled descriptive vocabulary or to perform retrievals from a body of text in - terms of text type or origin. The work description may however be of use in any form of - automatic text processing. The MEI elements used to encode the work description - are described in section below. - zero or more elements, tagged extMeta, containing non-MEI - metadata. - a revision history, tagged revisionDesc, which allows - the encoder to provide a history of changes made during the development of the electronic - text. The revision history is important for version control and for resolving - questions about the history of a file. The MEI elements used to encode the revision - description are described in section below. - -
- File Description -

The structure of the bibliographic description of a machine-readable or digital musical text - resembles that of a book, an article, or other kinds of textual objects. The file description - element of the MEI header has therefore been closely modelled on existing standards in library - cataloging; it should thus provide enough information to allow users to give standard - bibliographic references to the electronic text, and to allow catalogers to catalog it. - Bibliographic citations occurring elsewhere in the header, and in the text itself, are derived - from the same model.

-

The bibliographic description of an electronic musical text should be supplied by the - mandatory fileDesc element:

-

- - - -

-

The fileDesc element contains two mandatory and six optional elements, - each of which is described in more detail below. These elements are listed below in the order - in which they must occur within the fileDesc element.

-

- - - - - - - - - -

-

A complete file description will resemble the following example:

- - - - - - - - - - - - - - - - - - - - - - - -
- Title Statement -

The titleStmt element is the first component of the fileDesc element, and is mandatory:

-

- - - -

-

The title statement contains the title given to the electronic work, together with one or - more optional statements of responsibility which identify the encoder, editor, author, - compiler, or other parties responsible for it:

-

- - - - - - - - - - - - -

-

The title element contains the chief name of the electronic work. Its - content takes the form considered appropriate by its creator. The element may be repeated, - if the work has more than one title (perhaps in different languages). Where the electronic - work is derived from an existing source text, it is strongly recommended that the title for - the former should be derived from the latter, but clearly distinguishable from it, for - example by the addition of a phrase such as ‘: an electronic transcription’ or ‘a digital - edition’. This will distinguish the electronic work from the source text in citations and in - catalogs, which contain descriptions of both types of material.

- - - Lieder-Album für die Jugend - für Singstimme(n) und Klavier, <identifier>op. - 79</identifier> - an electronic transcription - - -

Other alternative titles or subtitles may be encoded in additional title elements with - values in the type attribute that distinguish them from the chief title. Sample - values for the type attribute include: main (main title), subordinate (subtitle, - title of part), abbreviated (abbreviated form of title), alternative (alternate title by - which the work is also known), translated (translated form of title), uniform (collective - title).

-

The type attribute is provided for convenience in analyzing titles and - processing them according to their type; where such specialized processing is not necessary, - there is no need for such analysis, and the entire title, including subtitles and any - parallel titles, may be enclosed within a single title element, as in - the following example:

- -Symphony No. 5 in C Minor : an electronic transcription - -

The electronic work will also have an external name (its ‘filename’ or ‘data set name’) or - reference number on the computer system where it resides at any time. This name is likely to - change frequently, as new copies of the file are made on the computer system. Its form is - entirely dependent on the particular computer system in use and thus cannot always easily be - transferred from one system to another. Moreover, a given work may be composed of many - files. For these reasons, these Guidelines strongly recommend that such names should not be - used as the title for any electronic work.

-

Helpful guidance on the formulation of useful descriptive titles in difficult cases may be - found in the Anglo-American Cataloguing Rules (Gorman and Winkler, 1978, chapter 25) or in - equivalent national-level bibliographical documentation.

-

At a minimum, the creator of the musical text and the creator of the file should be - identified. If the bibliographic description is for a corpus, identify the creator of the - corpus. Optionally also include the names of others involved in the transcription or - elaboration of the text, sponsors, and funding agencies. The name of the person responsible - for physical data input need not normally be recorded, unless that person is also - intellectually responsible for some aspect of the creation of the file.

-

In traditional bibliographic practice, those with primary creative responsibility are given - special prominence. MEI accommodates this approach by providing responsibility-role - elements. For example:

- - - Auf dem Hügel sitz ich spähend : an electronic transcription - Ludwig van Beethoven - Aloys Jeitteles - - -

Secondary intellectual responsibility in this case is encoded using respStmt. The respStmt element has two subcomponents: a name element identifying a responsible individual or organization, and a - resp element indicating the nature of the responsibility. All names - should be stated in the form in which the persons or bodies wish to be publicly cited. This - will usually be the fullest form of the name, including first names. No specific - recommendations are made at this time as to appropriate content for resp. However, it should make clear the nature of the responsibility.

- - - Auf dem Hügel sitz ich spähend : an electronic transcription - Ludwig van Beethoven - Aloys Jeitteles - - Encoded by - Maja Hartwig - Kristina Richts - - - -

This method of encoding facilitates exchange of bibliographic data with library catalogs - and bibliographic databases as well as applications whose handling of bibliographic data is - restricted to traditional responsibility roles. Additional information regarding these - responsibility-role elements can be found in chapter .

-

When the MEI.namesdates module is enabled, two additional elements are also permitted - within respStmt:

-

- - - - -

-

These elements allow for more precise identification of the entity associated with the name - than is permitted by the simpler name element. The following example - shows how a precise date range can be associated with a personal or corporate name.

- - - Machine-readable transcription by: - John Doe - - -

For additional information about corporate and personal names, see chapter .

-

In addition to, or instead of the resp element, the role - attribute on name, persName, and corpName may be used to capture the nature of responsibility. While resp accommodates capturing the wide variety of text that may occur in - responsibility statements, use of the role attribute provides the possibility of - recording a controlled value independently of the textual content of resp.

- - - Encoded by - Members of the Local Symphony Orchestra - - -

Values from the MARC relator code list (http://www.loc.gov/marc/relators/relacode.html) or term list (http://www.loc.gov/marc/relators/relaterm.html) are recommended for - role, where applicable.

-

Where it is necessary to group responsibilities and names, multiple responsibility - statements may be used. For example:

- - - Symphony No. 5 in C Minor : an electronic transcription - - Encoded by - Joe Encoder - Jane Decoder - - - Images scanned by - Ludwig van Ludwig - - - -

It is often desirable to mix primary and secondary intellectual responsibility information. - Treating all intellectual roles the same way can allow literal transcription of existing - responsibility statements and simplify programmatic processing. The following example - demonstrates how a responsibility statement may be transcribed using interleaved resp and persName elements:

- - - Symphony No. 5 in C Minor : an electronic transcription - - Composed by: - Ludwig van Beethoven - Johannes Jones: - Machine-readable transcription - - - -

However, eliminating explanatory text and relying on standardized values for - role, as in the following example, allows data creation and processing tools of - the greatest simplicity.

- - - Symphony No. 5 in C Minor : an electronic transcription - - Ludwig van Beethoven - Johannes Jones - - - -
-
- Edition Statement -

The editionStmt element is the second component of the fileDesc element. It is optional but recommended when applicable.

-

- - - -

-

It contains elements for identifying the edition and those responsible for it:

-

- - - - -

-

For printed texts, the term edition applies to the set of all the - identical copies of an item produced from one master copy and issued by a particular - publishing agency or a group of such agencies. A change in the identity of the distributing - body or bodies does not normally constitute a change of edition, while a change in the - master copy does.

-

For electronic texts, the notion of a master copy is not entirely - appropriate, since they are far more easily copied and modified than printed ones; - nonetheless, the term edition may be used for a particular state of a machine-readable text - at which substantive changes are made and fixed. Synonymous terms used in these Guidelines - are version, level, and - release. The words revision and - update, by contrast, are used for minor changes to a file which do - not amount to a new edition.

-

No simple rule can specify how substantive changes have to be before they are regarded as - producing a new edition, rather than a simple update. The general principle proposed here is - that the production of a new edition entails a significant change in the intellectual - content of the file, rather than its encoding or appearance. The addition of analytic coding - to a text would thus constitute a new edition, while automatic conversion from one coded - representation to another would not. Changes relating to the character code or physical - storage details, corrections of misspellings, simple changes in the arrangement of the - contents and changes in the output format do not normally constitute a new edition, whereas - the addition of new information (e.g., annotations, sound or images, links to external data) - almost always does.

-

Clearly, there will always be borderline cases and the matter is somewhat arbitrary. The - simplest rule is: if you think that your file is a new edition, then call it such. An - edition statement is optional for the first release of a computer file; it is mandatory for - each later release, though this requirement cannot be enforced.

-

Note that all changes in a file, whether or not they are regarded as constituting a new - edition or simply a revision, should be independently noted in the revision description - section of the file header (see section ).

-

The edition element should contain phrases describing the edition or version, including the - word 'edition', 'version', or an equivalent term, together with a number or date, or terms - indicating difference from other editions such as 'new edition', 'revised edition', etc. Any - dates that occur within the edition statement should be marked with the date element. The n attribute of the edition element may be used as - elsewhere to supply any formal identification (such as a version number) for the - edition.

-

One or more respStmt elements may also be used to supply statements - of responsibility for the edition in question. These may refer to individuals or corporate - bodies and can indicate functions such as that of a reviser, or can name the person or body - responsible for the provision of supplementary matter, of appendices, etc., in a new - edition.

-

Some examples follow:

- - - Second draft, substantially extended, revised, and - corrected. - - - - - Student's edition, June 1987 - - New annotations by - George Brown - - - -
-
- Physical Description of the File -

The third component of the fileDesc is a description of the physical qualities of the file. - The extent element is provided for this purpose.

-

- - - -

-

The extent element describes the approximate size of a text as stored - on some carrier medium, whether digital or non-digital, specified in any convenient - units.

-

For printed books, information about the carrier, such as the kind of medium used and its - size, are of great importance in cataloging procedures. The print-oriented rules for - bibliographic description of an item's medium and extent need some re-interpretation when - applied to electronic media. An electronic file exists as a distinct entity quite - independently of its carrier and remains the same intellectual object whether it is stored - as file on a hard disc drive, a CD-ROM, a set of USB devices, or in the internet. Since, - moreover, these Guidelines are specifically aimed at facilitating transparent document - storage and interchange, any purely machine-dependent information should be irrelevant as - far as the file header is concerned.

-

This is particularly true of information about file-type although library-oriented rules - for cataloging often distinguish two types of computer file: ‘data’ and ‘programs’. This - distinction is quite difficult to draw in some cases, for example, hypermedia or texts with - built-in search and retrieval software.

-

Although it is equally system-dependent, some measure of the size of the computer file may - be of use for cataloging and other practical purposes. Because the measurement and - expression of file size is fraught with difficulties, only very general recommendations are - possible; the element extent should contain a phrase indicating the - size or approximate size of the computer file in one of the following ways:

- - in bytes of a specified length (e.g. ‘4000 bytes’) - as falling within a range of values, for example: - less than 1 Mb - between 1 Mb and 5 Mb - between 6 Mb and 10 Mb - over 10 Mb - - - in terms of any convenient logical units (for example, words or sentences, citations, - paragraphs) - in terms of any convenient physical units (for example, compact discs, removable hard - drives, DVDs) - -

The use of standard abbreviations for units of quantity is recommended where applicable, - here as elsewhere (see http://physics.nist.gov/cuu/Units/binary.html).

- - - between 1 MB and 2 MB - 4.2 MiB - 4532 Mbytes - 3200 sentences - 5 90-mm high density diskettes - - -

For ease of processability, the use of the unit attribute is recommended, as in - the following example:

- -3200 - -
-
- Publication, Distribution, etc. -

The pubStmt element is the fourth component of the fileDesc element and is mandatory.

-

- - - -

-

It may contain either a single unpub element, indicating that the - file has yet to be published, or in the case of published material, one or more elements - from the model.pubStmtPart class. The following elements may be - used to provide details regarding the file's publication and distribution:

-

- - - - - - - - - - -

-

The publisher is the person or institution by whose authority a given edition of the file - is made public. The distributor is the person or institution from whom copies of the text - may be obtained. Use respStmt to identify other responsible persons or - corporate bodies.

-

The sub-elements of availability should be used to provide detailed - information regarding access to the MEI file.

-

- - - - - - - -

- - - - Musikwissenschaftliches Seminar <Detmold> - -
- Gartenstrasse 20 - 32756 Detmold - Germany -
- 2011 - - © 2004, MEI Consortium - - - - - - - Segno Press Inc. - - - University of Virginia -
- 221 B LowWater Street, - Charlottesville, Virginia - 22901 -
- - 2010 - 1234 - - Available for purposes of academic research and teaching - only. - - - -

Give any other useful information (e.g., dates of collection of data) in an annotation - within the notes statement, which is described below.

-

Here, as in the description of intellectual responsibility described above, the respStmt element may be used to contain all statements of responsibility - regarding publication and distribution when uniformity is desired regardless of the role of - participants in the publication process:

- - - MEI Project - German Research Foundation - National Endowment for the - Humanities - - -
-
- Series Statement -

The seriesStmt element is the fifth component of the fileDesc element and is optional.

-

- - - -

-

A series may be defined in one of the following ways:

- - A group of separate items related to one another by the fact that each item bears, in - addition to its own title proper, a collective title applying to the group as a whole. The - individual items may or may not be numbered. - Each of two or more volumes of essays, lectures, articles, or other items, similar in - character and issued in sequence. - A separately numbered sequence of volumes within a series or serial. - -

The seriesStmt element may contain one or more of the following more - specific elements:

-

- - - - - - - - -

-

The title, editor and identifier elements have the same function described above: identification of the - item, in this case the series, and the individuals or groups responsible for its creation. - The title element is required within seriesStmt.

- - - MEI Sample Collection - - -

The identifier element may be used to supply any identifying number - associated with the series, including both standard numbers such as an ISSN and particular - issue numbers. Its type attribute is used to categorize the number further, - taking the value 'ISSN' for an ISSN, for example.

- - - Studies in Ornamentation - Jacques Composeur - 0-345-6789 - - -

The contents of the series may be enumerated using the contents - element. Use of this element should be determined by the complexity of the resource and - whether or not the information is readily available. The contents - element may consist of a single paragraph when unstructured information is sufficient.

- - -

On Wenlock Edge -- From Far, From Eve and Morning -- Is My Team Ploughing? -- Oh, When - I Was In Love With You -- Bredon Hill -- Clun

- - -

Alternatively, contentItem elements may be used to provide structure - for the content description.

- - - Contents - On Wenlock Edge - From Far, From Eve and Morning - Is My Team Ploughing? - Oh, When I Was In Love With You - Bredon Hill - Clun - - -

Finally, using the target attribute, a link to an external table of contents may - be supplied in lieu of or in addition to the child elements of contents.

- - - -

The seriesStmt element is allowed to nest within itself in order to - accommodate a series within a series.

- -
-
- Notes Statement -

The notesStmt element is the sixth component of the fileDesc element and is optional. If used, it contains one or more annot elements, each containing a single piece of descriptive information of the - kind treated as ‘general notes’ in traditional bibliographic descriptions.

-

- - - -

-

Some information found in the notes area in conventional bibliography has been assigned - specific elements in these Guidelines; in particular the following items should be tagged as - indicated, rather than as general notes:

- - the nature, scope, artistic form, or purpose of the work; also the genre or other - intellectual category to which it may belong. These should be formally described within - the workDesc element (section ). - bibliographic details relating to the source or sources of an electronic text: e.g., - ‘Transcribed from a facsimile of the 1743 publication’. These should be formally described - in the sourceDesc element (section ). - further information relating to publication, distribution, or release of the text, - including sources from which the text may be obtained, any restrictions on its use or - formal terms on its availability. These should be placed in the appropriate division of - the pubStmt element (section ). - publicly documented numbers associated with the file should be placed in - an altId element within the meiHead element. - International Standard Serial Numbers (ISSN), International Standard Book Numbers (ISBN), - and other internationally agreed upon standard numbers that uniquely identify an item, - should be treated in the same way, rather than as specialized bibliographic notes. As - described elsewhere, identifiers for sources of the file should be recorded - within the sourceDesc. - -

Nevertheless, the notesStmt element may be used to record potentially - significant details about the file and its features, for example:

- - dates, when they are relevant to the content or condition of the computer file: e.g. - ‘manual dated 2010’, ‘file validated Apr 2011’ - names of persons or bodies connected with the technical production, administration, or - consulting functions of the effort which produced the file, if these are not named in - statements of responsibility in the title or edition statements of the file description: - e.g. ‘Historical commentary provided by members of the Big Symphony Orchestra’ - availability of the file in an additional medium or information not already recorded - about the availability of documentation: e.g. ‘User manual is loose-leaf in eleven - paginated sections’ - language of work and abstract, if not encoded in the langUsage - element, e.g. ‘Text in English with stage directions in French and German’ - -

Each such item of information may be tagged using the general-purpose annot element. Groups of annotations are contained within the notesStmt element, as in the following example:

- - - Historical commentary provided by John Smith. - OCR scanning performed at University of Virginia. - - -

There are advantages, however, to encoding such information with more precise elements - elsewhere in the MEI header, when such elements are available. For example, the notes above - might be encoded as follows:

- - - … - - John Smith - historical commentary - - - University of Virginia - OCR scanning - - - -
-
- Source Description -

The sourceDesc element is the seventh and final component of the fileDesc element. In MEI, sourceDesc is a grouping - element containing one or more source elements, each of which records - details of a source from which the computer file is derived. This might be a printed text or - manuscript, another computer file, an audio or video recording, or a combination of these. - An electronic file may also have no source, if what is being cataloged is an original text - created in electronic form.

-

- - - - -

-

The content model of the source element is similar to that of the fileDesc and work elements. The list below - reflects the order in which the optional components of source must - occur.

-

- - - - - - - - - - - - - - - -

-

When the MEI.frbr module is available, the following elements may also appear after the - classification element. Additional information regarding FRBR (Functional Requirements for - Bibliographic Records) can be found at .

-

- - - - - -

-

In the simplest case, the source element may contain nothing more - than a notes statement giving a simple prose description or a brief note stating that the - document has no physical source:

- - - - - Based on the Porter Wagner edition. - - - - - - - - - Born digital. - - - - -

Alternatively, it may contain a basic bibliographic citation, also in an annotation:

- - - - - Bach, Carl Philipp Emanuel. Sonata in B-flat major, Wq.62/1 (H.2) - - - - -

However, more structured bibliographic data, such as that in the example below, facilitates - better machine-processing:

- - - - s1 - - Sonata in B-flat major, <identifier>Wq. 62/1 (H.2)</identifier> - - Bach, Carl Philipp Emanuel - - - - Paris - - A. Farrenc - - 1861-72 - - - Tresor des Pianistes, Vol. 13 - - - reprinted New York: Dover Publications, n.d. - - - - -

A description of more precise capture of dates and date ranges is provided in chapter .

-

The identifier element is provided within source in order to accommodate identifying strings which cannot be captured by the - xml:id attribute, such as numbers or strings requiring XML markup.

-

The titleStmt, editionStmt, pubStmt, seriesStmt, and notesStmt - elements function in exactly the same way as described in section above and below - and will not be covered again here.

-

If a source of the file is an unpublished manuscript, it is recommended that the unpub element be used as the only content of the source's pubStmt element. Other identifying information for the manuscript may be - collected in the notesStmt element, as described in section .

- - - - [Untitled Bach Manuscript] - - Johann Sebastian Bach - - - - - - - Manuscript discovered in library stacks, 2012 - - - -
- Associating Metadata and Data -

In the MEI header, the data attribute may be used to associate metadata with - related notational elements.

- -

Similarly, in the body of the MEI document, the decls attribute may be used to - associate parts of the encoded text with related metadata.

- -

The most useful associations of this type are between the bibliographic description of a - source and the material taken from it.

-
-
-
-
- Encoding Description -

The encodingDesc element is the second major subdivision of the MEI - header. It specifies the methods and editorial principles which governed the transcription or - encoding of the source material. Though not formally required, its use is highly - recommended.

-

- - - -

-

The encoding description may contain elements taken from the model.encodingPart class. By - default, this class makes available the following elements:

-

- - - - - - -

-

Each of these elements is further described in the appropriate section below.

-
- Application Information -

It is sometimes convenient to store information relating to the processing of an encoded - resource within its header. Typical uses for such information might be:

- - to allow an application to discover that it has previously opened or edited a file, - and what version of itself was used to do that; - to show (through a date) which application last edited the file to allow for diagnosis - of any problems that might have been caused by that application; - to allow users to discover information about an application used to edit the - file - to allow the application to declare an interest in elements of the file which it has - edited, so that other applications or human editors may be more wary of making changes to - those sections of the file. - -

- - - - -

-

Each application element identifies the current state of one software - application with regard to the current file. This element is a member of the att.datable - class, which provides a variety of attributes for associating this state with a date and - time, or a temporal range. The xml:id and version attributes should be - used to uniquely identify the application and its major version number (for example, 'Music - Markup Tool 1.5'). It is not intended that a software application should add a new application element each time it touches the file.

-

The following example shows how these elements might be used to record the fact that - version 1.5 of an application called ‘Music Markup Tool’ has an interest in two parts of a - document. The parts concerned are accessible at the URLs given as targets of the two ptr elements. When used on application, the - date attribute specifies when the application was employed, in this case June - 6, 2011. Version information for the application should be placed in version.

- - - - Music Markup Tool - - - - - -
-
- Declaration of Editorial Principles -

The editorialDecl element is used to provide details of the editorial - practices applied during the encoding of a musical text.

-

It may contain a prose description only, or one or more of a set of specialized elements; - that is, members of the MEI model.editorialDeclPart class. -

-

Some of these policy elements carry attributes to support automated processing of certain - well-defined editorial decisions; all of them contain a prose description of the editorial - principles adopted with respect to the particular feature concerned. Examples of the kinds - of questions which these descriptions are intended to answer are given in the list - below.

- - - - - - -

Was the text corrected during or after data capture? If so, were corrections made - silently or are they marked using the tags described in chapter ? What principles have been adopted with respect to omissions, truncations, dubious - corrections, alternate readings, false starts, repetitions, etc.?

 - - - -

Has any analytic or ‘interpretive’ information been provided — that is, information - which is felt to be non-obvious, or potentially contentious? If so, how was it - generated? How was it encoded?

 - - - - -

Was the text normalized, for example by regularizing any non-standard enharmonic - spellings, etc.? If so, were normalizations performed silently or are they marked using - the tags described in chapter ? What authority was used for - the regularization? Also, what principles were used when normalizing numbers to provide - the standard values for the value attribute described in section and what format is used for them?

- - - - -

How is the musical text segmented? If mdiv and/or section elements have been used to - partition the music for analysis, how are they marked and how was the segmentation - arrived at?

- - - - -

In most cases, attributes bearing standardized values should conform to a defined - datatype. In cases where this is not appropriate, this element may be used to describe - the standardization methods underlying the values supplied.

 - -

Experience shows that a full record should be kept of decisions relating to editorial - principles and encoding practice, both for future users of the text and for the project - which produced the text in the first instance. Any information about the editorial - principles applied not falling under one of the above headings may be recorded as additional - prose following the special-use elements.

- - - -

Separate mdiv elements have been created for each movement of the work.

- - -

The harmonic analysis applied throughout movement 1 was added by hand and has not - been checked.

- - -

Errors in transcription controlled by using the Finale editor.

- - -

All sung text converted to Modern American spelling following Webster’s 9th - Collegiate dictionary.

- -

- - -

An editorial practices declaration which applies to more than one text or division of a - text need not be repeated in the header of each text or division. Instead, the - decls attribute of each text (or subdivision of the text) to which it applies - may be used to supply a cross-reference to a single declaration encoded in the header.

-
-
- Project Description -

- - - -

-

The projectDesc element may be used to describe, in prose, the - purpose for which a digital resource was created, together with any other relevant - information concerning the process by which it was assembled or collected. This is of - particular importance for corpora or miscellaneous collections, but may be of use for any - text, for example to explain why one kind of encoding practice has been followed rather than - another.

-

For example:

- - - -

Texts collected for use in the MEI Summer Workshop, Aug. 2012.

- - - -
-
- Sampling Declaration -

The samplingDecl element holds a prose description of the rationale and methods used in - selecting texts, or parts of text, for inclusion in the resource.

-

- - - -

-

The samplingDecl element should include information about such - matters as:

- - the size of individual samples - the method or methods by which they were selected - the underlying population being sampled - the object of the sampling procedure used - -

but is not restricted to these.

- - -

Encoding contains 40 randomly-selected measures.

- - -

It may also include a simple description of any parts of the source text included or - excluded:

- - -

Only the songs have been transcribed. Advertisements have been silently omitted. All - mathematical expressions have been omitted, and their place marked with a gap - element.

- - - - -

Only the first 6 measures of movement 1 are encoded.

- - -

A sampling declaration which applies to more than one text or division of a text need not - be repeated in the header of each such text. Instead, the decls attribute of each - text (or subdivision of the text) to which the sampling declaration applies may be used to - supply a cross-reference to it, as further described in section .

-
-
-
- Work Description -

The workDesc element is the third major subdivision of the MEI Header. - It is an optional element, the purpose of which is to enable the recording of information - characterizing various descriptive aspects of the abstract work.

-

- - - -

-

Within workDesc, the work element is used to hold - information for each resource being described.

-

- - - -

-

All the components of work are optional, but they must occur in the - following order:

- - identifier - titleStmt - incip - key - mensuration - meter - tempo - otherChar - history - langUsage - perfMedium - audience - contents - context - biblList - notesStmt - classification - - - -

These work description components may be classed into two groups based on their function: - - identification of the work: identifier, titleStmt, incip, key, mensuration, meter, - tempo, otherChar - contextual information for the work: history, langUsage, perfMedium, audience, - contents, context, biblList, notesStmt, classification - -

-
- Work Identification -

The following elements provide minimal identifying information for the intellectual - work:

-

- - - - -

-

The identifier and title values recorded here may or may not be the same as those assigned - to published versions of the work. Fuller details regarding the use of titleStmt are available in section .

-
-
- Incipits -

- - - -

-

The first few notes and/or words of a piece of music are often used for identification - purposes, especially when the piece has only a generic title, such as "Sonata no. 3". They - appear in catalogs of music and in tables of contents of printed music that include multiple - works.

-

The following elements are provided for the inclusion of incipits:

-

- - - - - -

-

The elements incipCode and incipText are - available for the inclusion of coded incipits of music notation and textual incipits, - respectively. The incipText element should contain only the initial - performed text of the work, while incipCode may contain both words and - music, depending on the capabilities of the scheme used to encode it. When both music and - text are provided in incipCode, it may be helpful to repeat the text - in incipText in order to provide easier access to only the text, for - example, for indexing of the text without having to extract it from the coded incipit.

- -

Both incipCode and incipText allow reference to - an external file location via the target attribute and specification of the - internet media type of the external file via the mimetype attribute.

- -

An MEI-encoded incipit may be captured in a score sub-element.

- -

In addition, graphic may be used as a sub-element of incip to include an image of an incipit.

- -

To facilitate the capture of metadata associated with an incipit, MEI allows the following - sub-elements within incip. The order of their presentation below - follows the order in which they must appear in this context.

-

- - - - - - - - - - - - -

-

Usually, the metadata captured in this manner is rendered alongside or in lieu of a coded - or graphical incipit. It may or may not serve in a work identification capacity, depending - on whether the incipit is intended to represent the entire work or a segment of the work. - For example, if an incipit is provided for each aria in an opera, then the metadata pertains - only to the aria, not the entire work.

-
-
- Key, Tempo, and Meter -

The attributes key, tempo, and meter are often helpful for identifying a musical work when - it does not have a distinctive title.

-

- - - - - - -

-

The key element is used exclusively within bibliographic - descriptions. Do not confuse this element with keySig, which is used - within the body of an MEI file to record this data for musical notation. Likewise, meter should not be confused with the attributes used by staffDef and - scoreDef to record meter-related data for notated music. The tempo - element can be used here as well as in the body of an MEI document; however, its attributes - other than xml:id, label, n, base, and - lang are meaningless in the MEI header context, and therefore should be avoided - within a work description. The mensuration element is available for - the description of works in the mensural repertoire. When a work uses meter and mensural - signs, both mensuration and meter elements may - be used.

-
-
- Other Identifying Characteristics -

Additional information that aids the identification of the work may be encoded using otherChar.

-

- - - -

-

The following components provide detailed information about the work's context, including - the circumstances of its creation, the languages used within it, high-level musical - attributes, performing forces, etc.

-
-
- Work History -

The following elements are provided to capture the history of a musical work:

-

- - - - - - -

-

The creation element is intended to contain a brief, - machine-processable statement of the circumstances of the work's creation. Its content is - limited to text and the date and geogName - elements.

-

The history element is a container for additional non-bibliographic - details relating to a work. It may use the eventList element to - provide a list of key events in the creation and performance history of the work. The eventList element is comprised of event elements - containing a brief description of the associated event, including dates and locations where - the event took place. An event list may use the type attribute to distinguish - between multiple event lists with different functions, such as a list of events in the - compositional process and a list of performance dates.

-

Event lists and other text components, such as paragraphs, tables, lists, and text - divisions (div) may be interleaved when an 'essay-like' work history - is desired.

-

The event element permits either a text-centric or a data-centric - model. The text-centric model is provided for prose descriptions, while the data-centric - model accommodates event descriptions that consist of a collection of descriptive phrases. - In the text-centric model, paragraphs, tables, and lists may be used. In the data-centric - model, however, only certain phrase-level elements, may appear.

-
-
- Language Usage -

The langUsage element is used within the workDesc element to describe the languages, sublanguages, dialects, etc. represented - within a work. It contains one or more language elements, each of - which provides information about a single language.

-

- - - - -

-

A language element may be supplied for each different language used - in a document. If used, its xml:id attribute should specify an appropriate - language identifier. This is particularly important if extended language identifiers have - been used as the value of @xml:lang attributes elsewhere in the document.

-

Here is an example of the use of this element:

- - - Québecois - Canadian English - British English - - - - - - -
-
- Performance Medium -

The following elements are available for description of a composition's performing - forces:

-

- - - - - -

-

The perfMedium element provides the possibility of describing a work - in terms of its medium of performance; that is, the performing forces required. In the case - of a dramatic work, the dramatis personae and associated voice qualities may be enumerated - using castList. The perfResList element - describes the necessary instrumental and vocal resources.

-
- Cast Lists -

A cast list is a specialized form of list, conventionally found at the start or end of a - dramatic work, usually listing all the speaking/singing and non-speaking/singing roles in - the play, often with additional description (‘Cataplasma, a maker of Periwigges and - Attires’) or the name of an actor or actress (‘Old Lady Squeamish. Mrs Rutter’).

-

- - - - - -

-

Cast lists often function as identifying metadata and for this reason are permitted - within the description of a work.

-

Because the format and internal structure of cast lists are unpredictable, a castList may contain any combination of castItem - and castGrp elements.

-

A castItem element may contain any mixture of text and the - following elements:

-

- - - - - -

-

In the following example, role provides the name of the dramatic - character and roleDesc contains a brief description of the role. The - perfRes element is used to describe the voice range of the - role.

- - - - Ursula - Queen of the Britons - Soprano - - - Dersagrena - Handmaiden to Ursula - Mezzo-Soprano - - - Fingal - King of the Britons - Baritone - - - -

The vocal qualities and associated roles for Beethoven's opera Fidelio may - be encoded as:

- - - - - Tenor - Florestan - - - Soprano - Leonore, his wife - - - Bass - Rocco, gaoler - - - Soprano - Marzelline, his daughter - - - Tenor - Jaquino, assistant to Rocco - - - Bass-baritone - Don Pizarro, governor of the prison - - - Bass - Don Fernando, King's minister - - - - -

The castItem element may also contain:

-

- - - -

-

However, this element is unlikely to be useful in the context of a work description. It - may be used here, however, for the very rare occasion when a work was conceived for and is - only performable by a single person or group, as for certain "performance art" works.

-

It is common to find some roles presented in groups or sublists. Roles are also often - grouped together by their function. To accommodate these situations, the castGrp element is provided as a component of castList. It - may contain any combination of castItem, castGrp, and roleDesc elements.

- -
-
- Instrumentation -

The perfResList element is used to capture the solo and ensemble - instrumental and vocal resources of a composition. For example, a work for a standard - ensemble may be indicated thus:

- - - - Orchestra - - - -

The detailed make-up of standard and non-standard ensembles may also be enumerated:

- - - - Orchestration - Flute - Oboe - English Horn - 2 Horns in D - Strings - - - -

Where multiple instruments of the same kind are used, the count attribute on - perfRes may be used to encode the exact number of players called - for.

- - - - - Piccolo - Flute - 1st Clarinet - 2nd Clarinet - 3rd Clarinet - - - - -

Instrument or voice specifications may be grouped using the perfResList element and a label assigned to the group with head. For example:

- - - - - - Woodwinds - Piccolo - Flute - 1st Clarinet - 2nd Clarinet - 3rd Clarinet - - - - Brass - 1st Trumpet - 2nd Trumpet - 3rd Trumpet - - - - - - - - - - - Woodwinds - 2 Flutes (2. piccolo) - 1 Oboe - - - - Strings (8-6-4-4-2) - Violin 1 - Violin 2 - Viola - Violoncello - Double Bass - - - - -

The preceding example also demonstrates how instrumental doublings can be accommodate - through the use of nested perfRes elements. Only the outer-most - perfRes element should use the count attribute. Its value should reflect the - total number of performers, not the number of instruments played.

-

The perfRes element provides the codedval attribute, - which can be used to record a coded value that represents the string value stored as the - element's content. It is recommended that coded values be taken from a standardized list, - such as the International Association of Music Libraries' Medium of Performance Codes List or - the MARC Instruments - and Voices Code List.

- - - - - Horn - Trumpet - Trombone - - - -

Solo parts may be marked with the solo attribute of perfRes, like so:

- - - Violin - Violin - Violin - Viola - Violoncello - - -

Music for a single player should, however, never use the solo attribute.

- - - - Piano - - -

- -
-
-
- Audience and Context -

- - - - -

-

The intended audience for the work and additional information about context for the work - that is not captured in more specific elements elsewhere, such as history and its sub-components, may be recorded in the audience and context elements.

-
-
- Work Contents -

- - - - -

-

Often, it is helpful to identify an entity by listing its constituent parts. A simple - description of the work's content, such as may be found in a bibliographic record, can be - given in single paragraph element:

- - -

A suitable tone ; Left hand colouring ; Rhythm and accent ; Tempo ; Flexibility ; - Ornaments

- - -

Alternatively, a structured list of contents may be constructed using the contentItem element:

- - - Sonata in D major, op. V, no. 1 / Corelli - Sonata in G minor / Purcell (with Robert Donington, gamba) - Forlane from Concert royal no. 3 / Couperin - - -

Each contentItem element may be preceded by an optional label:

- - - Sonata in D major, op. V, no. 1 / Corelli - Sonata in G minor / Purcell (with Robert Donington, - gamba) - Forlane from Concert royal no. 3 / Couperin - - -

To reference a contents list in an external location, use the target - attribute:

- - - -

To facilitate the creation of music catalogs based on MEI header information, contents may contain a heading:

- - - Contents of this Work: - Sonata No. 1 - Sonata No. 2 - Sonata No. 3 - - -
-
- Bibliographic Evidence -

- - - -

-

The biblList element allows citation of bibliographic evidence - supporting assertions made within other sub-components of the work description.

-
-
- Notes Statement -

The notesStmt element may be used within the description of the - musical work to capture information not accounted for by the other elements of the - description.

-
-
- Classification -

The next component of the core workDesc element is the classification element. This element is used to classify a musical text - according to one or more of the following methods:

- - by reference to a recognized international classification scheme such as the Dewey - Decimal Classification, the Universal Decimal Classification, the Colon Classification, - the Library of Congress Classification, or any other system widely used in library and - documentation work - by providing a set of keywords, as provided, for example, by British Library or - Library of Congress Cataloguing in Publication data. - -

The following elements are provided for this purpose:

-

- - - - - -

-

The termList element categorizes an individual text by supplying a - set of terms which may describe its topic or subject matter, its physical or intellectual - form, date, etc. Each term is indicated by a term element. In some - schemes, the order of items in the list is significant, for example, from major topic to - minor; in others, the list has an organized substructure of its own. No recommendations are - made here as to which method is to be preferred. Wherever possible, such terms should be - taken from a recognized source.

-

The classDecls element offers the possibility of capturing a - bibliographic citation and/or a URI at which the classification scheme or information about - it may be found.

- -Library of Congress subject headings. Prepared by the - Cataloging Policy and Support Office, Collections Services. Washington, D.C.: Library of - Congress, Cataloging Distribution Service, 1993- . - - - - - -Library of - Congress subject headings. Prepared by the Cataloging Policy and Support Office, - Collections Services. Washington, D.C.: Library of Congress, Cataloging Distribution - Service, 1993- . - -

The term attribute may be used on each term element to make reference, by - means of an identifier, to the classification scheme from which it is drawn.

- - - - - - Guitar music (Rock) - Rock music 1971-1980. - M1630.18.Z26 O6 2011 - - - -

Alternatively, term may be used on termList when all - the contained terms come from the same source.

- - - - - - Guitar music (Rock) - Rock music 1971-1980. - - - M1630.18.Z26 O6 2011 - - - -
-
- Work Relationships -

When the FRBR (Functional Requirements for Bibliographic Records) module is available, the - following elements may be used within work to describe relationships - between the work being described and other works or between the work and expressions of - it:

-

- - - - - -

-

For more information about FRBR and the use of these elements, see chapter .

-
- -
-
- Other Metadata -

The following element is provided to accommodate non-MEI metadata:

-

- - - -

-

The extMeta element may contain text and any number of well-formed XML - fragments, XML comments, and CDATA sections, except for MEI markup, which is prohibited. The - document element of each fragment must explicitly declare its namespace.

- - - - - Simple dreams : - a musical memoir / - Linda Ronstadt. - - - -

An MEI processor is not required to validate or otherwise process any markup within the extMeta element. Therefore, the extMeta element - itself is the lowest level at which an association can be created between - foreign metadata and other MEI elements as described in section .

-
-
- Revision Description -

The final sub-element of the MEI header, the revisionDesc element, - provides a detailed change log in which each change made to a text may be recorded. Its use is - optional but highly recommended. It provides essential information for the administration of - large numbers of files which are being updated, corrected, or otherwise modified as well as - extremely useful documentation for files being passed from researcher to researcher or system - to system. Without change logs, it is easy to confuse different versions of a file, or to - remain unaware of small but important changes made in the file by some earlier link in the - chain of distribution. No change should be made in any MEI-conformant file without - corresponding entries being made in the change log.

-

- - - - -

- -

The main purpose of the revision description is to record changes in the text to which a - header is prefixed. However, it is recommended practice to include entries also for - significant changes in the header itself (other than the revision description itself, of - course). At the very least, an entry should be supplied indicating the date of creation of the - header.

-

The log consists of a list of change elements, each of which contains a - detailed description of the changes made. If a number is to be associated with one or more - changes (for example, a revision number), the n attribute may be used to indicate - it. The person responsible for the change and the date of the change may be indicated by the - respStmt and date elements. The description of - the change itself is contained within the changeDesc element, which can - hold one or more paragraphs.

-

It is recommended to give changes in reverse chronological order, most recent first.

-

For example:

- - - - - KR - - -

Cleaned up MEI file automatically using Header.xsl.

- - - - - - KR - - -

Cleaned up MEI file automatically using ppq.xsl.

- - - - - -

A slightly shorter form for recording changes is also available when a the date of the change - can be described by a single date in a standard ISO form and when the name of the agent(s) - responsible for the change, encoded elsewhere in the header, can be referred to by one or more - URIs given in the resp attribute. For example:

- - - -

Cleaned up MEI file automatically using ppq.xsl.

- - - -
-
- Minimal and Recommended Header Information -

The MEI header allows for the provision of a very large amount of information concerning the - text itself, its source, its encodings, and revisions of it, as well as a wealth of - descriptive information, such as the languages it uses and the situation(s) in which it was - produced, together with the setting and identity of participants within it. This diversity and - richness reflects the diversity of uses to which it is envisaged that electronic texts - conforming to these Guidelines will be put. It is emphatically not intended that all of the - elements described above should be present in every MEI Header.

-

The amount of encoding in a header will depend both on the nature and the intended use of the - text. At one extreme, an encoder may expect that the header will be needed only to provide a - bibliographic identification of the text adequate to local needs. At the other, wishing to - ensure that their texts can be used for the widest range of applications, encoders will want - to document as explicitly as possible both bibliographic and descriptive information, in such - a way that no prior or ancillary knowledge about the text is needed in order to process it. - The header in such a case will be very full, approximating the kind of documentation often - supplied in the form of a manual. Most texts will lie somewhere between these extremes; - textual corpora in particular will tend more to the latter extreme. In the remainder of this - section we demonstrate first the minimal, and then a commonly recommended, level of encoding - for the bibliographic information held by the MEI header.

-

Supplying only the level of encoding required, the MEI header of a single text will look like - the following example:

- - - - - Fughette (in Gottes Namen Fahren wir - Dies sind die heil'gen zehn Gebote) for - Brass Quintett : an electronic transcription - - - - Musikwissenschaftliches Seminar <Detmold> - - - - - -

The only mandatory component of the MEI Header is the fileDesc element. - Within this element, titleStmt and pubStmt are - required constituents. Within the title statement, a title is required. Within the pubStmt, a publisher, distributor, or other agency responsible for the - file is required.

-

While not formally required, additional information is recommended for a minimally effective - header. For example, it is recommended that the person or corporate entity responsible for the - creation of the encoding should be specified using respStmt within the - titleStmt element. It is also recommended that information about the - source, or sources, of the encoding be included. Each source element - should contain at the least a loosely structured bibliographic citation that identifies the - source used to construct the MEI file.

-

Furthermore, If the electronic transcription is a member of a series of publications, the - series title and publisher should be included using the seriesStmt - element. It is also common for cataloging records to include genre and/or form information, - here represented by the MEI classification element.

-

We now present the same example header, expanded to include additionally recommended - information, adequate for most bibliographic purposes, in particular to allow for the creation - of an AACR2-conformant bibliographic record.

- - - - - Fughette (in Gottes Namen Fahren wir - Dies sind die heil'gen zehn Gebote) for - Brass Quintett : an electronic transcription - - Encoded by: - Maja Hartwig - Kristina Richts - - - - - Musikwissenschaftliches Seminar <Detmold> - - 2011 - - - MEI Sample Collection - - MEI Project - - - - - - Fughette (in Gottes Namen Fahren wir - Dies sind die heil'gen zehn Gebote) - for Brass Quintett - - Johann Christoph Bach - Michel Rondeau - - - - http://icking-music-archive.org/scores/j.chr.bach/JCBIN-xml.zip - - - Werner Icking Music Archive - - - © 2010 - Gatineau,Qc.Ca. - - - - - - 785.15 - - - - - - - -
-
- Independent Headers -

Many libraries, repositories, research sites and related institutions collect bibliographic - and documentary information about machine readable music documents without necessarily - collecting the music documents themselves. Such institutions may thus want access to the - header of an MEI document without its attached text in order to build catalogs, indexes and - databases that can be used to locate relevant texts at remote locations, obtain full - documentation about those texts, and learn how to obtain them. This section describes a set of - practices by which the metadata headers of MEI documents can be encoded separately from those - documents and exchanged as freestanding MEI documents. Headers exchanged independently of the - documents they describe are called independent headers.

-
- Definition and Principles for Encoders -

An independent header is an MEI metadata header that can be exchanged as an independent - document between libraries, archives, collections, projects, and individuals.

-

The structure of an independent header is exactly the same as that of an header attached to - a document. This means that an meiHead can be extracted from an MEI - document and sent to a receiving institution with little or no change. -

-

When deciding which information to include in the independent header, and the format or - structure of that information, the following should be kept in mind:

- - The independent header should provide full bibliographic information about the encoded - text, its sources, where the text can be located, and any restrictions governing its - use. - The independent header should contain useful information about the encoding of the - text itself. In this regard, it is highly recommended that the encoding description be as - complete as possible. The Guidelines do not require that the encoding description be - included in the header (since some simple transcriptions of small items may not require - it), but in practice the use of a header without an encoding description would be severely - limited. - The independent header should be amenable to automatic processing, particularly for - loading into databases and for the creation of publications, indexes, and finding aids, - without undue editorial intervention on the part of the receiving institution. For this - reason, two recommendations are made regarding the format or structure of the header: - first, where there is a choice between a prose content model and one that contains a - formal series of specialized elements, wherever possible and appropriate the specialized - elements should be preferred to unstructured prose. Second, with respect to corpora, - information about each of the texts within a corpus should be included in the overall - corpus-level meiHead. That is, source information, editorial - practices, encoding descriptions, and the like should be included in the relevant sections - of the corpus meiHead, with pointers to them from the headers of the - individual texts included in the corpus. There are three reasons for this recommendation: - first, the corpus-level header will contain the full array of bibliographic and - documentary information for each of the texts in a corpus, and thus be of great benefit to - remote users, who may have access only to the independent header; second, such a layout is - easier for the coder to maintain than searching for information throughout a text; and - third, generally speaking, this practice results in greater overall consistency, - especially with respect to bibliographic citations. - -
-
-
- Header Elements and their Relationship to Other Bibliographic Standards -

Mapping elements from the MEI metadata header to another descriptive system may help a - repository harvest selected data from the MEI file to build a basic catalog record. For this - purpose, the following attribute is provided on most elements occurring within meiHead:

-

- - - -

-

The encoding system to which fields are mapped must be specified in analog. When - possible, subfields as well as fields should be specified, e.g., subfields within MARC - fields.

- - -
-
- RelatedItem vs. FRBR -

MEI offers two related concepts for capturing relations between bibliographic items. The - model of relatedItem, as described in chapter of these Guidelines, is derived from MODS v3.4 (see - documentation here). Its purpose in MEI is to encode bibliographic references between mostly - "secondary" material, like reviews, articles, and so on. It may be used to provide - cross-references between information encoded in different places of the header.

- -

However, relatedItem is less ideal for describing the relations between - works, differing versions of these works, the sources in which those versions are transmitted, - and where applicable the individual copies of a print. For these situations, it is strongly - recommended to use the FRBR module instead. This module is based on - the Functional Requirements for Bibliographic Records, as specified by the IFLA. It allows a much finer - description of relationships between such "primary" entities. For compatibility reasons, both - models should not be confused or mixed under any circumstances.

-
-
-
- Functional Requirements for Bibliographic Records (FRBR) -

MEI header information may refer to different levels of description of the encoded work: Some - information may apply the work in all its various forms and realizations, e.g., the name of its - composer. Other information may describe a certain version of the work, or a source such as the - printed first edition, or only a single copy of that source. Core MEI limits the header - information to two such levels of description: work and source, respectively.

-

However, when the FRBR module is available more detailed descriptions are possible. With - certain limitations, mainly due to the musical nature of the works encoded in MEI, the FRBR - module adapts the Functional Requirements for Bibliographic Records (FRBR) as recommended by the - International Federation of Library Associations and Institutions (IFLA) [http://www.ifla.org/publications/functional-requirements-for-bibliographic-records].

-

The IFLA’s FRBR model distinguishes four levels of abstraction, or entities:

-

- - FRBR defines a work as a "distinct intellectual or artistic creation", an abstract - entity because there is no single material object one can point to as the work. - - An expression is defined as "the intellectual or artistic realization of a work in the - form of [...] notation, sound, image, object, movement, etc., or any combination of such - forms". Expressions are also abstract entities. - - A manifestation is defined as "the physical embodiment of an expression of a work", - including, for instance, manuscripts, books, sound recordings, films, video recordings, - CD-ROMs, multimedia kits, etc. The manifestation represents all the physical objects that - bear the same characteristics, with respect to both intellectual content and physical - form. - - A single exemplar of a manifestation is called an item, e.g., a specific copy of a - printed score. With manuscripts, item and manifestation levels are nearly identical. A - manuscript may be regarded as a manifestation having only one item. - -

-
- FRBR Entities in MEI -

When the FRBR module is available, MEI offers four elements corresponding to the FRBR - entities:

-

- - - - - - -

-

The names of the MEI entities generally follow those of FRBR: the work - element is a container for description at the FRBR "work" level, expression is for description at the FRBR "expression" level, and item holds FRBR "item" level description. The source element, - however, is the MEI equivalent to FRBR "manifestation" level description. The name "source" is - used because it is both shorter and more familiar than "manifestation" to users of existing - bibliographic markup schemes.

-

The work element has an optional child element to hold the expression - elements:

-

- - - -

-

As expressionList is a container element for descriptions of different - expressions of the same work, it may contain only expression - elements.

-

The content model of expression is similar to that of work. It does not, however, permit expressionList and audience elements. But it adds elements that aid identification and - description of specific versions of a work:

-

- - - - -

-

Since expressions, like works, are abstractions, their titles are often nebulous. Usually, - however, the title of an expression is the same as the work it represents. When the - relationship between a work and an expression is encoded hierarchically, the expression’s - title element may be omitted with the assumption that it will be inherited from the work. If - no title is provided for an expression, distinguishing characteristics must be provided in - other elements, such as perfMedium, as in the following example:

- - - - Pavane pour une infante défunte - - - - - - piano - - - - - - - orchestra - - - - - - -

Programmatic concatenation of the work title and one or more characteristics of the - expression can be used to provide identification for the expression. For example, the - expressions above may be identified by "Pavane pour une infante défunte (piano)" and "Pavane - pour une infante défunte (orchestra)". In some cases, it may be helpful to assign a - descriptive title to the expression, as illustrated below. The carrier of the manifestation is - often a good source of this kind of descriptive text.

- - - - Pavane pour une infante défunte - - - - - Version for piano - - - - piano - - - - - - Version for orchestra - - - - orchestra - - - - - - - - - - Sonata No. 2 - - - - - Live recording at Carnegie Hall - - - - - Studio recording - - - - - -

The itemList element provides functionality similar to that of expressionList; that is, it - can be used to group descriptions of individual items (exemplars) of the parent source. Just - like expressionList, which can only hold expression sub-components, itemList may only contain item elements.

-

- - - - -

- - - - Trois trios pour le piano-forte violon, et violoncelle - - - - - - Stanford University Library - - - - - - - Dresden, Sächsische Landesbibliothek - Staats- und - Universitätsbibliothek - - - - - - -
-
- Component Parts in FRBR -

Each of the four MEI elements corresponding to FRBR entities may contain a list of - constituent parts. All four entities utilize the same element:

-

- - - -

-

However, the child elements of a component group must be the same type as the group's parent. - This allows for a more detailed description than is possible using the core MEI contents element. For example, a work element’s componentList element can only contain work elements, etc. In - this way, the componentList element may be employed to describe composite - works, as in the example below:

- - - - Der Ring des Nibelungen - - - - - Das Rheingold - - - - - Die Walküre - - - - - Siegfried - - - - - Götterdämmerung - - - - - -

This technique can also be applied when a single intellectual source is comprised of multiple - physical parts. In the following example, the choral parts were published in four physically - separate "signatures":

- - - - Printed choral parts - - - Horneman & Erslev - Copenhagen - 1871 - - - - - Soprani - - - 4 - - - - - Alti - - - 4 - - - - - Tenori - - - 6 - - - - - Bassi - - - 6 - - - - - -
-
- FRBR Relationships -

FRBR defines a number of terms that describe how the basic entities relate to each other. MEI - provides the following elements for this purpose.

-

- - - - - -

-

Each of the four FRBR entity equivalents – the work, expression, source, and item elements – - allows a list of such relationship descriptions as its last child element. relationList provides a container for individual relation - elements. The nature of the relationship must be specified by the rel attribute and - the target of the relationship must be identified by the target attribute. The - values allowed by rel follow those defined for FRBR at http://www.ifla.org/files/assets/cataloguing/frbr/frbr_2008.pdf.

-

Since relations are bidirectional, they may be defined on both entities involved, using pairs - of oppositely-directed relation descriptors. The following FRBR relations are allowed in MEI - as values of the relation element’s rel attribute (shown in pairs for clarity): - - hasAbridgement / isAbridgementOf - hasAdaptation / isAdaptationOf - hasAlternate / isAlternateOf - hasArrangement / isArrangementOf - hasComplement / isComplementOf - hasEmbodiment / isEmbodimentOf - hasExemplar / isExemplarOf - hasImitation / isImitationOf - hasPart / isPartOf - hasRealization / isRealizationOf - hasReconfiguration / isReconfigurationOf - hasReproduction / isReproductionOf - hasRevision / isRevisionOf - hasSuccessor / isSuccessorOf - hasSummarization / isSummarizationOf - hasSupplement / isSupplementOf - hasTransformation / isTransformationOf - hasTranslation / isTranslationOf - -

-

Some of these relationships are already implicitly expressed by the MEI structural model: - FRBR defines an expression entity as a realization of a work, but as this relation is implied - by the expressionList element’s child relationship to its parent work element, the - hasRealization/isRealizationOf relation does not need to be explicitly declared. Likewise, it - is not necessary to specify by means of relation elements that an item is an exemplar of the - source described by its parent source element. This resembles the FRBR model, which allows 1:n - relationships both between works and expressions, and between manifestations and items.

-

However, as FRBR allows n:n relations between expressions and manifestations (in MEI: - sources), a hierarchical model based on the strucutre of XML is clearly insufficient to - express all possible expression / manifestation combinations. It is therefore required to - declare these relations explicitly. In FRBR terms, a manifestation / source is an embodiment - of an expression.

- - - - Score, first edition - - - - - - -

Within the componentList element, the order of child elements implicitly - describes a hasSuccessor/isSuccessorOf relationship between components, i.e. it defines a - certain sequence such as the movements of a work. In other cases, relation elements may be needed to explicitly encode relationships not otherwise - defined by encoding order or hierarchy. For instance, the hasReproduction/isReproductionOf - relationship may be used to indicate that one source is a reprint of another.

- - - - Horneman & Erslev - Copenhagen - 1874 - - - - - - -

Moreover, the use of componentList implicitly defines a hasPart/isPartOf - relationship between the componentList element’s parent and its child elements. Using the relationList and relation elements to define their relationship, the four - component works in the "Der Ring des Nibelungen" example above could alternatively be encoded - as sibling work elements to the "Ring" work element.

- - - - - Der Ring des Nibelungen - - - - - - - - - - - Das Rheingold - - - - - - - - Die Walküre - - - - - - - - Siegfried - - - - - - - - Götterdämmerung - - - - - - - -

Relations may also be used to point to external resources. For instance, each of the - individual component works of the "Ring" could be encoded in separate files, with relations - pointing to them.

-

In the file "ring.xml":

- - - - - Der Ring des Nibelungen - - - - - - - - - - -

In the file "rheingold.xml":

- - - - - Das Rheingold - - - - - - - -
-
-
- Common Music Notation -

The module described in this chapter offers the means to describe music in so-called - Common Music Notation (CMN, sometimes referred to as - Common Western Music Notation). For this purpose, it provides a number of - special elements and adds several attribute classes to elements from the Shared module.

-
- Basic Elements of CMN -

This section describes the use of basic features of MEI important for encoding CMN material. - Most of the elements discussed here are defined in chapter of these - Guidelines, but are used in music from the CMN repertoire in specialized ways.

- -
- The Role of the Measure Element -

Arguably, the most important element of the CMN module is the measure - element. It is used as a structural unit inside section elements and - acts as a container for events from the model.eventLike class, such as notes, chords and rests as well as - control events from the model.controlEventLike class, such as slurs and indications of dynamics.

-

The following example demonstrates the use of the measure - element:

- -
- - - - - - - - - - - - - - - - -
- - -

A measure slices the flow of a score or part into chunks that - normally comply with a duration determined by the meter defined within a preceding scoreDef or staffDef element. Each staff in the - source material is represented by a staff element. As the order of the - staff elements in the file does not have to reflect their order in the original document, to - eliminate confusion they should always refer to a staffDef element, - using either an n or def attribute. Whereas the def - attribute uses the xs:anyURI datatype, the n value refers to the - closest preceding staffDef or layerDef with the - same value in its n attribute.

- - - - - - - - - - - - - - -

Each staff may hold a number of layer elements - to reflect multiple voices. Just as with staff, - the order of the layer elements in the file does not have to reflect - their original order in the document, so they also possess n and def - attributes for association with the appropriate layer definition.

- - - - - -

Later in the file:

- -
- - - - - - - - - - - -
- -
- -
- Defining Score Parameters for CMN -

When encoding a score in CMN, MEI relies on the following elements from the Shared module:

-

- - - - - - -

-

A scoreDef element is used to specify the common parameters of a - score, e.g., key and meter. The most important attributes for this purpose are:

-

- - - - - -

-

The following example describes a score in common time with 3 flats:

- - - - -

Other attributes allow the description of default page and system margins and fonts for - text and music:

-

- - - -

-

There are other attributes that allow the specification of many further details of a score. - These are available from the element definitions accessible at scoreDef, staffDef, staffGrp and layerDef.

- -

When content is provided for scoreDef, it must contain a staffGrp element. This element is used to gather individual staves and - other staff groups. This is useful for collecting instrumental or vocal groups in a large - score, such as woodwinds, brasses, etc., and for assigning a shared label to the group, - using the label and label.abbr attributes. The staffGrp element is also used for the two staves of a grand staff. The - barthru attribute on staffGrp allows one to specify - whether barlines are drawn across the space between staves of that group or only on the - staves themselves.

-

A staffDef element is used to describe an individual staff of a score or performer part. It bears most of the - attributes described above, including label and label.abbr for - providing staff labels for the first and subsequent pages.

-

Every staffDef must have an n attribute with an integer as - its value. The first occurence of a staffDef with a given number must - also indicate the number of staff lines via the lines attribute.

-

The order of staffDef elements within scoreDef - follows the order of staves in the source document or planned rendering. The individual staff elements within a measure refer to these staffDef declarations using their own n attribute values. - Therefore, the encoding order of staves within a measure does not have to mimic the order of - the staffDef elements with scoreDef.

-

In addition to the parameters inherited from scoreDef, the following - attributes are important for staffDef elements:

-

- - - -

- -

A staff with a tenor clef is encoded as in the following example:

- - - - -

In the case of transposing instruments, the key-related attributes described above may be - used to override the written key expressed in the scoreDef element. As - a basic principle, MEI always captures written pitches, so the trans.diat and - trans.semi attributes may be used to indicate the number of diatonic steps and - semitones to calculate sounded pitch from written pitch. The piccolo and E♭ clarinet staves - in the example below utilize these attributes:

- - - - - - - - - - - - - - -

There are a number of additional elements that can be used as children of staffDef in order to describe additional features of the staff, such as the color of - a clef or a key signature added in a different hand. These elements include:

-

- - - - - - - - - -

- -

With the exception of label, these elements may also occur within the - flow of musical events captured in a layer, since they are members of - model.eventLike. In the layer context they function as - milestones and affect all following content assigned to the layer (even in subsequent - measures) until their information is again overridden either by the same element bearing - different information or a staffDef or scoreDef. - In this context, it is also possible to combine them with the elements described in chapters - and of these Guidelines.

-

Such flexibility as this may require close inspection of an encoding to retrieve the - correct definitions for a given staff. As a general rule, the closest preceding and most - specific element provides this information: For example, a keySig in - the preceding measure is more relevant than a staffDef at the - beginning of the section, which is more relevant than a scoreDef at - the beginning of the score. However, a section-specific scoreDef that - provides only information about the meter does not override the more specific information - about key signature gathered from a staffDef for a transposing - instrument.

-

Every staffDef may contain a number of layerDef - elements, which may be used to establish default values for the distinct layers sharing one - staff. MEI does not use the term voice to describe these - musical threads because that term implies continuity across measure - boundaries. Given the sometimes arbitrary relationships between these threads from measure - to measure as well as across staves, MEI uses the more neutral term - layer.

- -
-
- - Redefinition of Score Parameters -

Sometimes it is necessary to provide the parameters of a score or a staff with new values. - For example. a score may change keys, gain or lose staves, use different layout settings at - any point, etc. Likewise, a staff may change its clef, gain or lose layers, or become - invisible, and so on. To accommodate these circumstances, in CMN staffDef is allowed to occur in the following locations:

- - within the description of staff groups; that is, in staffGrp, - within the content of a measure, - between measures; that is, directly within section and ending elements, and - between sections and endings; that is, directly within a score - or part element. - - -

In addition, scoreDef is allowed to occur:

- - within sections and endings; that is, inside section and ending elements; and - between sections and endings; that is, directly within a score - or part. - - -

The possibility also exists to include scoreDef and staffDef in staves and layers when the mei-all schema is in use; however, this - practice is not recommended for the CMN repertoire.

- -
-
- Notes, Chords and Rests in CMN -
- Notes -

Undoubtedly, the most important element for any music notation representation is the note element, which is defined in section . This section describes the usage of note in the CMN repertoire as well as CMN-specific additions to the basic - definition in the shared module.

-
- Basic Usage of Notes in CMN -

In CMN, notes are determined by three basic parameters:

- - pitch name (using pname) - octave (using oct) - duration (using dur) - -

A typical note, in this case a quarter note C4, is therefore encoded like so:

- - - -

Because these attributes may not be required in all situations (such as dur - for the notes of a chord), processing software should anticipate retrieving the - information that would have been provided by missing attributes from a preceding note or - chord parent in the same layer. Only - information from pname, oct and dur attributes can be - gathered in this fashion. No other attributes can be treated this way.

-

The default values for pname and oct conform to the Acoustical - Society of America representation for pitch name; that is, the letters A - G, albeit in - lower case, and the numbers 0 - 9.

-

The usual CMN-specific values for dur are:

- - - - whole note - - - half note - - - quarter note - - - eighth note - - - sixteenth note - - - - - 2048th note - -

Additionally, the following two values borrowed from mensural notation are allowed, as - they sometimes also appear in CMN:

- - - - double whole - - - quadruple whole - -

Please note that their mensural counterparts bear different names in order to clearly - distinguish between repertoires.

-

Dotted durational values are accommodated by the dots attribute, which - records the number of written augmentation dots. Thus, a dotted quarter note is - represented as in the following example:

- - - -
-
- Grace Notes -

The CMN module adds two optional attributes, grace and - grace.time, to note and chord. - The presence of the grace attribute indicates a grace note or chord.

-
- Grace notes - -
-

The encoding of the left-most example would look like this:

- - - - - - - - - - - -

Grace notes are not counted when determining the measure's conformance to the current - time signature. Therefore, the dur attribute records only the - written rhythmic value of the grace note. The time necessary for the - performance of grace notes can be unspecified, calculated based on taking time from - other non-grace notes, or specified precisely using the dur.ges - attribute.

-

The values of grace indicate from which note time is - borrowed to perform the grace note: The preceding note, in which - case the value 'unacc' (unaccented) is used, or the following note, when the value 'acc' - (accented) is appropriate. Technically, this value determines if the note following the - grace will keep its original onset time or will be slightly delayed to allow the grace - note itself to be accented. Sometimes it is not clear how to perform a grace; in these - situations the value 'unknown' allows one to indicate a grace note while unambiguously - stating that its performed duration remains unknown.

-

The grace.time attribute is only to be used in combination with the - grace attribute. It records the amount of time (as a percentage of the - written duration) that the grace note should steal from the - preceding note (when grace='unacc') or the following note (when - grace='acc').

-

More information about grace notes in the context of other CMN ornaments is available - in chapter .

-
-
- Stem Modifications -

The stem.mod attribute accommodates various stem modifiers found in the CMN - repertoire. These symbols are placed on a note or chord's stem and generally indicate - different types of tremolo and Sprechstimme. The following values are - allowed:

- - - - 1 slash through stem - - - 2 slashes through stem - - - 3 slashes through stem - - - 4 slashes through stem - - - 5 slashes through stem - - - 6 slashes through stem - - - X placed on stem - - - Z placed on stem - -

The stem.mod attibute is normally used in accordance with practices - described in section .

- - -

The CMN module makes the att.stems.cmn attribute class - available, which adds the optional stem.with attribute to note and chord. The attribute stem.with allows - for the indication of a stem that joins notes on adjacent staves.

-
- Cross-staff chord - -
-

The following code demonstrates one method of encoding the first chord in the last - measure in the image above. The stem.with attribute must occur on all the - notes or chords attached to the cross-staff stem.

- - - - - - - - - - - - - - - - - -

Alternatively, the encoder may choose to treat the notes in the lower staff as - logically belonging to the top staff and to displace them using the - staff attribute on note. Some use cases, however, may - require filling the time that those notes would normally occupy using the space element described in section . Using this mechanism, the example above could also be encoded like so:

- - - - - - - - - - - - - - - - - - - - -

The choice between these two methods of representing material that crosses staves is - often software-dependent.

-
-
-
- Rests -

The dur attribute on rest captures the written duration - of the rest and allows the same values as on note and chord. The CMN module also makes three more elements available for - special forms of rest:

-

- - - - - -

-
- Measure Rests -

The mRest (measure rest) element is used to - indicate a complete measure rest, independent from the meter of the current measure.

-

The cutout attribute provides for the description of the rendition of the - mRest. If cutout is set to - cutout (the only value allowed), then the complete staff - including the staff lines will not be rendered for this measure.

- - - - - - - - - -

It is a semantic error to mix an mRest with other events in the - same layer. However, other control events, - such as fermata, may be used at the same time as mRest.

- -
-
- Multiple-Measure Rests -

The multiRest (multiple measure rest) element is - used to encode multiple measures of rest. It is commonly used in performer parts, but - due to the problem of synchronicity with other staves, it is never found in scores. A - numeric value, stored in the num attribute, indicates the number of resting - measures. The various visual forms displayed below are not captured by multiRest, but may be created by rendering software.

-
- Forms of multiple measure rests - -
- - - - - - - -
-
- Empty Measures -

The mSpace (measure space) element is closely - related to the space and mRest elements. It - is used to explicitly indicate that a layer has no content but that no information is - missing from the encoding.

-
- Empty measure - -
- - - - - - - - - - -
-
-
-
- Timestamps and Durations -

MEI offers multiple ways of defining onsets and offsets of timed musical events such as - notes and slurs. The most common and most musician-friendly approach to this is through the - use of a combination of the attributes tstamp and dur, which are made - available by the attribute classes att.timestamp.logical - (inherited by att.controlEvent) and att.timestamp2.logical, both from the shared module.

-

The timestamp (tstamp) of a musical event is calculated in relation - to the meter of the current measure and resembles the so-called beat - position. In a common time measure with four quarter notes, the timestamp of each quarter - equals its beat position in the measure: The first quarter has a timestamp of 1, the second - has a timestamp of 2, and so on. MEI defines the value of tstamp as a real - number; the second eighth note position in a measure would thus be represented by the value - of "1.5". The range of possible values is defined as starting with zero and ending with the - number of metrical units in a measure (the numerator in a time - signature) + 1. This allows the capture of all graphical positions starting from the left - barline ('0') and ending with the right barline of the measure ('5', in the case of 4/4 - time).

-

For expressing durations, MEI offers the dur attribute. This attribute is - described in section .

-

For spanning elements like slurs, which are members of the model.controlEventLike class, it is often more intuitive to record - two timestamps – one for the onset of the event and one for its termination. Because the - termination of the event may be in a succeeding measure, the second timestamp - (tstamp2) has a slightly different datatype than the one marking the initiation - of the event. Its datatype is constrained to values following the formula "xm + - y", where x is the number of full measures that this particular - feature lasts (or the number of bar lines crossed) and y is the timestamp in - the target measure where the feature ends. The timestamp is expressed using the same logic - as described above. For example, a value of "0m+3" in 4/4 time indicates that the element - bearing this attribute, a slur for example, ends on beat 3 of the same measure where it - started. A value of "1m+1.5" would indicate an end on the second eighth note of the - following measure. In 6/8 time, the value "2m+3" means that the feature ends two measures - later on the third eighth note.

-
- -
-
- Advanced CMN Features -

Over time, in addition to the basic features of note, chord, and rest, many other symbols - have been added to CMN. The following section describes some of these symbols and introduces - their handling in MEI.

- -
- Beams -

A very common feature of music from the CMN repertoire is the beaming of eighth or shorter - notes. MEI provides two elements for the explicit encoding of features joined by beams.

-

- - - - -

- -

Use of the beam element is straightforward. The beamed notes, rests, - or chords are simply enclosed by the beam element:

- - - - - - - - - -

Whereas in music notation every note value shorter than an eighth adds another beam - (sometimes referred to as secondary beams), in MEI only one beam - element is used, no matter the durations of the contained notes. The visual rendition of a - set of beamed notes is presumed to be handled by rendering processes.

- - - - - - - - - - - - - - -

From the 19th century onwards, it became quite common to break secondary beams to increase - readability of longer beamed passages. The optional breaksec attribute on notes and chords under the beam may be used to - encode the breaking of secondary beams after the note or chord bearing the - attribute. The value of breaksec indicates the number of continuous beams. For - example:

-
- Primary and secondary beams - -
- - - - - - - - - - - - - - - - - - -

In the music of the second half of the 20th century, it is quite common to indicate - acceleration or deceleration using converging beams as in the image below:

- -

The encoding of such a beam is accomplished using the rend attribute of the - beam, which allows the following values:

- - - - The secondary beams start in their usual position and gradually converge until they - meet with the primary beam on the last note (or, the first eighth note under the beam). - - - The secondary beams gradually diverge until they reach their regular distance. - - - The secondary beams diverge and converge arbitrarily. - - - The beam is rendered as usual (default). - - - - - - - - - - - - - - - -

The duration of notes, rests, or chords under a beam which carries the rend - attribute with a value of 'acc', 'rit', or 'mixed' must be treated specially. The first and - last contained elements must specify a duration which matches the number of beams displayed - at the point of these events. In the case of a 'mixed' beam, each event at the point of - change in the number of secondary beams must carry a dur attribute. Beams like - this may be encoded thusly:

-
- Accelerando beams - -
-

- - - - - - - - - - - - - - - - - - - - - - - -

- - -
- Cross-staff beam - -
- -

Beams that connect events on different staves may be encoded in two different ways. First, - a single-layer approach may be taken that treats the events lying under the beam as - logically belonging to the same layer as the initial event but visually - displaced to an adjacent staff. In the example below, the last two - notes under the beam carry a staff attribute value that contradicts the - normal staff placement indicated by the n attribute on - their ancestor staff.

- - - - - - - - - - - - -

Alternatively, a staff-by-staff methodology may be employed in which the notes are encoded - according to the staff on which they appear. This encoding style requires that each beam element account for the total time encompassed by the beam; that - is, each beam must use one or more space - elements to account for the time occupied by notes on the opposing staff. For example, the - time used by the first two notes of the beam must be represented on staff number 1 and the - time taken by the last two notes of the beam must be filled on staff number 2.

- - - - - - - - - - - - - - - - - - - - - - -

Downstream processing needs are the determining factor in the choice between the two - alternative encoding methods.

- -

Due to the potential problem of overlapping hierarchies, the beam - element only allows the encoding of beams that do not cross barlines. When beams cross - barlines, the use of the beamSpan element is required. Unlike beam, the beamSpanelement does not contain the - beamed notes as its children. Instead, it references the xml:id values of all - affected notes in its plist attribute and denotes the initial and terminal notes - of the beam using startid and endid attributes. This configuration - allows beams to cross measure boundaries. The following example demonstrates a typical - example of such hierarchy-crossing beams:

- - - - -

In addition to the explicit encoding of beams accommodated by the beam and beamSpan elements and the beam attribute, - MEI allows for specification of default beaming behavior using the following attributes on - scoreDef, staffDef, and layerDef:

- - - - Provides an example of how automated beaming (including secondary beams) is to be - performed. - - - Indicates whether automatically-drawn beams should include rests shorter than a - quarter note duration. - - -

The beam.group attribute can be used to set a default beaming pattern to be used - when no beaming is indicated at the layer level. It must contain a comma-separated list of - time values that add up to a measure in the current meter, e.g., '4,4,4,4' in 4/4 time - indicates that each quarter note worth of shorter notes should be beamed together. - Parentheses can be used to indicate sub-groupings of secondary beams. For example, - '(4.,4.,4.)' in 9/8 meter indicates one primary beam per measure with secondary beams broken - at each dotted quarter duration, while '(4,4),(4,4)' in 4/4 will result in a measure of 16th - notes being rendered with a primary beam covering all the notes and secondary beams for each - group of four 16th notes.

-

The beam.group attribute is available on scoreDef, staffDef, and layerDef elements, making it - possible to set different beaming patterns for each of these. Also, the beaming pattern can - be changed anywhere score parameters may be changed, for example, at the start of sections. - This beaming "directive" can be overridden by using beam, beamSpan, or beam attributes as described above. If none of - these beaming specifications is used, then no beaming is implied. Default beaming can be - explicitly 'turned off' by setting beam.group to an empty string.

- -
- -
- Ties, Slurs and Phrase Marks -

One of the most specific features of CMN is the use of curved lines - which connect notes. These lines are used to indicate various musical features, depending on - their context.

-

A tie is a curved line connecting two notes of the same - pitch. The purpose of a tie is to join the durations of both notes, so that the - first note sounds for the combined duration. In other words, there is only one onset for - both notes.

-

In MEI, ties can be encoded in different ways, depending on the level of detail that the - encoder wants to preserve. The simplest solution is to use the tie attribute - found on note and chord.

- - - - - - - -

This attribute allows three values:

- - - - Marks the start of a tie - - - Marks a participant in a tie other than the first or last - - - Marks the end of a tie - - -

The scope of the tie attribute is the musical layer; that - is, a tie started in one layer may only be ended by a subsequent musical event with a - tie attribute with an m or t value in the same layer. - The tie-terminating event may lie in the following measure.

-
- Ties across barlines - -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

When tie is used on chords, it functions as a shorthand indication for multiple - tie markings; that is, a separate tie is drawn for every pitch in the chord that remains - unchanged in the succeeding chord.

- - - - - - - - - - - - - - - - - -

This is equivalent to the following, more verbose version:

- - - - - - - - - - - - - - - - - -

A slur is a curved line that connects a group of notes of different pitch. It - normally indicates that an instrument-specific performance technique should be applied to - the affected notes. For example, in notation for winds, the notes should be played in one - breath, while a single bow is indicated for string instruments.

-
- Slurs - -
- -

In MEI, slurs may be encoded in a similar way to ties: note and chord bear a slur attribute that allows the commencement or - ending of a slur at this element. The allowed values, however, are slightly different: The - i, m or t are followed by a single digit in the - range 1 to 6, as in the following example:

- - - - - - - - -

The reason for this difference is that slurs, unlike ties, may overlap, so that a second - slur may start while the first slur is still ongoing. The digit indicates the level of - nesting of slurs on the note; '1' indicates no nesting, while '2' indicates the existence of - 2 slurs in which this note participates, and so on. In the example below, the second and - third quarter notes lie under 2 slurs. The second note is covered by the slur that begins on - the preceding note and by the one that it starts. The third note is affected by the slur - that begins on note one and by the one that starts on note two.

- - - - - - - - - - - - - - - - -

To support analytical operations, slur may take on more than one value. For - example, the example above may be more explicitly encoded as:

- - - - - - - - - - - - - - -

In this encoding, the notes in the beamed group are marked as participating in two slurs – - one connecting just the beamed notes and one connecting the first and last notes of the - layer. In nested slurs like this, the function of the slurs is usually - different. Here, the slur connecting the 8th notes indicates legato - performance, while the longer slur functions as a phrase mark.

- -

While ties are not normally allowed to cross layers or staves, slurs may. The following - example demonstrates how cross-staff slurs may be encoded using the slur - attribute:

- - - - - - - - - - - - - - - - - - - -

Slurs and ties that cross system or page breaks are often split into two separate symbols - for rendering. One slur or tie ends at the last barline, another one starts at the beginning - of the new system. MEI expects this to be the default rendering behaviour, so that in - situations like these, the regular tie or slur attributes are - sufficient to describe both curved lines resulting from the split.

-

Sometimes, however, one of these two symbols is missing in the document, or the encoder - wants to provide additional (often visual) information about the slur or tie. In these - cases, using an attribute is not an adequate solution. Therefore, MEI offers dedicated tie and slur elements. A third element, phrase, is used to identify a unified melodic idea (in German: - Phrasierungsbogen), whereas the slur element is - used as a generic element for all curved lines (in German: Bogensetzung) - except ties. All three elements have nearly identical models.

-

Another reason for using elements instead of attributes for ties, slurs, and phrase marks - is that only elements may be combined with the functionality provided in chapters and of these Guidelines.

-

Although these elements are allowed within a layer to accommodate - unmeasured notation, by convention in CMN they are normally placed inside measure, after the encoding of staves, alongside other so-called control - events.

- - - - - - - - - - - - - - - - -

Obviously, to be complete the slur in the above example needs to be - attached to the notes somehow. The vertical - assignment can be indicated for the example above using the staff - and layer attributes like so:

- - - - -

For the horizontal assignment, the encoder may choose between two - different mechanisms. The first uses two timestamp attributes as described in section . The start and end points of the slur may be indicated thusly:

- - - - -

By using tstamp and tstamp2 attributes, the encoder denotes a rather - loose connection – the slur (or tie) is attached to a certain position in the measure, not - to a specific note or chord. If the encoder wants to specify a close connection to a - particular event, the startid and endid attributes may be used - instead. Here, the xml:ids of the first and last note of the slur are referenced. - This mechanism also allows the crossing of layers and staves. -

- - -

For human readability, it is recommended to encode slur, tie and phrase features in the measure where they begin; that is, in the measure that holds the element referenced - by startid. On the other hand, for machine processability, it may be desirable to - place slur, tie, and phrase elements in the measure where they end or even in the last - measure regardless of their beginning and ending points in the music. This last - option makes all references contained within these elements back - references. Back references are necessary when using processing software that - treats the encoded file as a stream; that is, programs that process the file without - creating an in-memory representation of its contents.

-

When using the tie, slur or phrase elements, the curvature of the line may be described using the - curvedir, bulge and bezier attributes. Whereas the first - attribute allows only specification of the slur's vertical placement, the others give - increasingly more precise control of the curve.

-

If the encoder wishes to draw attention to the appearance of a slur or tie in a given - source, the facs attribute may be used instead of (or in addition to) the curve - description attributes to point to a graphic image or a zone within an image (see ).

-
- -
- Dynamics in CMN -

Common Music Notation provides two different methodologies for expressing the volume of a - note, phrase, section, etc. The first is a verbal instruction providing such information in - human language, possibly in an abbreviated form. An example is the word - piano, indicating a quiet volume, often abbreviated as - p. In MEI, verbal instructions like this are encoded using the - dynam element from the Shared module (see chapter ):

- -p - - -

By convention, dynam elements, like slur and - other elements belonging to the model.controlEventLike class, - are encoded at the end of the measure to which they belong. This - requires dynam to be assigned to a certain staff - using the staff attribute, whose value refers to the target element's - n attribute. In the absence of other information, all layers within the staff - are assumed to have the same dynamic marking.

- -p - - -

However, when the layers of a staff have different dynamic indications, the - layer attribute may be used to associate a dynamic marking with a particular - layer:

- - - p - mf - - - -

A value in the range 0-127 may be assigned to a dynamic marking using the val - attribute:

- -f - - -

The location of a dynamic marking in relation to a staff may be specified using the - place attribute, which may be given as above, within, - or below the staff:

- -p - - -

Dynamics must also be associated with a particular time point in a measure, using the - tstamp, or with a particular event, using the startid attribute. - Linking a control event with measures and events is discussed in section :

- - - - - - - - - - - - - - - p - cresc. poco a poco - - -

Dynamics which do not have an explicit endpoint are often referred to as - instantaneous. On the other hand, some dynamic directions indicate a - continuous change that must have a defined end point. It is possible to specify the logical - scope of continuous dynamic marks using the attributes tstamp2, dur or - endid. In order to capture the fact that they continue until the first beat of - the next measure, the crescendi in the example above may be marked:

- - -cresc. poco a poco - - - -cresc. poco a poco - - -

Any combination of tstamp, startid, tstamp2, and - endid attributes may be used to define the scope of a dynamic, although the - tstamp and tstamp2 or the startid and endid - combinations are the most logical combinations. For example, the following alternatives are - all possibilities for encoding up a crescendo. The choice of attributes is - often task or processor dependent.

- - -cresc. poco a poco - - - -cresc. poco a - poco - - - -cresc. poco a - poco - - - -cresc. poco - a poco - - -

All musical elements affected by the dynam may be explicitly - specified using the plist attribute, which contains xml:id attribute - value references:

- -cresc. poco a poco - - -

It is recommended that the list of references in plist include all participants - in the dynamic marking, including the first and last notes as in the preceding example, even - though they are duplicated by startid and endid attributes.

- -

In addition to verbal instructions, Common Music Notation uses graphical symbols to - indicate continuous dynamics. These crescendo and - decrescendo (or diminuendo) symbols are encoded in MEI using the - hairpin element. It also is a member of the model.controlEventLike class, which means it too is used just before the close of - a measure element, following the encoding of all staves. The required - attribute form specifies the direction of the symbol by taking one of two - possible values: cres (growing louder) or dim (getting - softer).

- - - - -

Marking the logical extent of hairpins is possible using the same attributes as for dynam. The following example shows a hairpin that begins on the second - half of beat 2 (in the current measure) and ends on beat 1 (of the following measure).

- - - - - - -
-
- Tuplets -

Tuplets indicate a localized change of meter; that is, a given duration in the regular - meter is divided between a group of notes with irregular (according to the current meter) - rhythmic values. The most common tuplet is a so-called triplet, in - which three notes take the time normally occupied by two.

-

The relation of the tuplet to the underlying meter is specified using the num - and numbase attributes, where num specifies the number of replacing - notes and numbase specifies the number of notes of the same duration - to be replaced. For example, when three eighth notes replace one quarter note in common - time, num takes a value of "3", whereas numbase reads "2", because a - quarter note in common time is normally divided into two eighths. When three quarters - replace two in the same meter, numbase also reads "2". The combination of these - attributes may be read as "3 in the time of 2" in either case.

-

The duration of the entire tuplet may be encoded using the usual power of - 2 values, e.g., 1, 2, 4, etc., in the dur attribute, and the - dots attribute, if necessary.

- - - - - - - - - - - - - -

Tuplets are often highlighted using brackets above or below the affected notes. The - presence and position of these brackets can be encoded using the bracket.place - (above / below) and bracket.visible (true / false) attributes.

-

Usually, however, tuplets are rendered with a bracket (bracket.visible="true") - and a single number (num.format="count" and num.visible="true"). - However, the number-to-numbase ratio may be provided in addition to, or in some cases as a - replacement for, the bracket. The num.format attribute indicates whether a plain - number (the value of num) or a ratio (comprised of num and - numbase, e.g., "3:2") should be displayed and num.visible indicates - the general presence of such a number.

- - -

In addition to note elements, tuplet may - contain other elements, such as rest or space, - to match the content of a source document or an intended rendering. In particular, the beam element is allowed so that custom beaming may be indicated, e.g., a - septuplet may be divided into a group of three plus a group of four - notes.

- - -

The tuplet element may also be used for repetition of the same pitch; - that is, a single note or chord may be the only content of the tuplet. In some cases, - optical music recognition software may treat these instances as bowed tremolandi due to the - knowledge of the complete semantics of the notation at the time of recognition. However, - marking these as tuplets is the recommended practice.

- -

In some situations, a tuplet is made up of events in different measures. As this raises the - issue of non-concurrent hierarchies, it is not possible to encode such situations with the - tuplet element described above. Therefore, MEI offers the tupletSpan element, which is member of the model.controlEventLike class. It is nested inside of measure, following all the measure's staff children. It uses - the same attributes as tuplet to describe tuplets, but instead of - nesting all affected notes inside itself, it references the xml:id values of all - affected notes in its plist attribute and the initial and terminal notes of the - tuplet using startid and endid attributes. This configuration allows - tuplets to cross measure boundaries. The following example demonstrates a typical example of - such hierarchy-crossing tuplets:

- - - - -
- -
- Articulation and Performance Instructions in CMN -

This section introduces elements and attributes which may hold CMN-specific performance - instructions. The functionality described herein is related to the artic - attribute and artic element introduced in . The - following elements are relevant in this context:

-

- - - - - - - - - -

-
- Arpeggio and Glissando -

In CMN, the notes of a chord are sometimes performed successively rather than - simultaneously. This behavior, called arpeggiation, is normally indicated - using a wavy line preceding the chord. MEI offers the arpeg element - to describe arpeggios. This element is a member of the model.controlEventLike class and, like other members of this class, uses the - staff, layer and tstamp or the startid and - endid attributes to connect it to the affected chord.

- - - - - - - - - - - - - - - - - - - -

The usual direction for the performance of an arpeggio is from lowest note to highest, - but this is not always the case. The customary signal of an downward arpeggio is an - arrowhead added to the bottom of the wavy line. The indication of the presence of an - arrowhead and the direction of the arpeggio are handled separately, however. The - arrow attribute indicates the presence of an arrowhead in the arpeggiation - sign, while the order attribute records the preferred sequence of notes.

-

The following examples illustrate various ways in which the arrow and order attributes - may be employed. The default visual rendition and performance are assumed in the absence - of both attributes, while the typical downward arpeggio is indicated by the presence of - both attributes. The last two possibilities occur less frequently, but are sometimes - appropriate: The presence of the arrow attribute without the order attribute may be used - in those cases where the arrowhead is redundant but is added to the symbol for the sake of - consistency or when the direction of successive arpeggios changes frequently. The last - possibility, an order attribute without an arrow attribute, is ambiguous; however, it can - be used as an encoding shortcut since a downward arpeggio must have a visual indication of - its direction to distinguish it from the upward arpeggio; therefore, the presence of the - arrowhead can be implied.

- - - - - - - - - - - - - - - - - -

A third, and somewhat counter-intuitive, value for order, "nonarp", indicates - that no arpeggio shall be performed. Normally rendered as a bracket instead of a wavy - line, this form of arpeggio is used to indicate a non-arpeggiated chord intervening in a - sequence of arpeggiated ones. This is common in music for the harp, where arpeggiation is - the usual method of performing chords and deviation from the norm must be explicitly - indicated.

- - -

For arpeggios that involve chords spanning multiple staves as a continuous arpeggio - (instead of two separate arpeggios), the plist attribute may be used to point - to all affected chord elements' xml:id attributes.

- - -

Whereas an arpeggio staggers the onset times of the notes of a - chord, a glissando denotes a situation where the pitch - slides from one note to another. It makes no difference whether - this slide produces distinct intermediate pitches (as on the piano) or not (as on the - trombone), though the latter is sometimes referred to as portamento. The - visual appearance of a glissando, which MEI encodes as gliss, is - normally a line connecting the two most distant notes in the glissando.

- -

The gliss element is a member of the model.controlEventLike class and therefore, like other control events, it - occurs inside a measure after the staves and uses its staff, layer, - tstamp, tstamp2, startid and endid - attributes to connect it to the affected notes or chords. It is a semantic error not to - specify a starting point attribute. The visual appearance of the indicating line may be - recorded in the rend attribute. Any text accompanying the line, such as - "gliss.", may be provided in the text attribute.

- -
-
- Bend -

A bend is a variation in pitch (often microtonal) upwards or downwards during the course - of a note. Typically, the performer attacks the note at true pitch, - changes the intonation, then returns to true pitch. The bend element - can also be used for so-called scoop, plop, falloff, and doit performance effects. It - should not be used for laissez vibrer (l.v.) indications. As with other - control events, the starting point of the bend may be indicated by either a tstamp, - tstamp.ges, tstamp.real or startid attribute. It is a semantic error not to specify a - starting attribute.

-
-
- Tremolandi - -

CMN has two slightly different concepts which are both called tremolo. The - first is a rapid repetition of a single pitch or chord, whereas the second is a rapid - alternation between two different notes or chords. In addition, either species of tremolo - may be measured or unmeasured. A measured tremolo is an - abbreviation for written-out notation; that is, the tremolo is intended to be perceived as - notes with distinct rhythmic values. On the other hand, in an unmeasured tremolo no - specific number of alternations is intended.

-

For the repetition of a single note or chord, MEI offers the bTrem - (bowed tremolo) element, which is a member of the model.eventLike class, meaning it is encoded following the normal course of - musical events within a layer. It holds exactly one note or chord element that is to be repeated.

-
- Bowed tremolandi - -
- - - - - - -

The measperf attribute value indicates the exact note values in an aural - rendition of a measured tremolo, i.e., quarters, 8ths, and so on. The stem modifier must - also be explicity set on the child note or chord element for a complete visual representation. The number of slashes present - on the note may disagree with the number of slashes that should be present according to - the measperf attribute, especially in music manuscripts.

- - - - - - -

The bTrem element can be used as shorthand for a tuplet consisting - of repetitions of a single note or chord. This kind of markup may be the result of an - optical music recognition process in which complete semantics cannot be determined - a priori. When used this way, the num attribute on bTrem can record a number to be rendered along with the pseudo-tuplet. - In spite of this capability, the tuplet element is preferred.

- - - - - - -

In the case of alternating pitches, MEI offers the fTrem (fingered - tremolo) element. While it mostly behaves the same as bTrem, a - fingered tremolo requires exactly two child elements, either being a note or chord. The measperf attribute value - indicates the exact note values in an aural rendition of a measured tremolo, i.e., 4ths, - 8ths, 16ths, etc. The number of slashes present in the source is captured by the - slash attribute. The number of slashes present may disagree with the rhythmic - value indicated by the measperf attribute, especially in manuscript - sources.

- - - - - - - - -
-
- Fermata -

A very common feature of music notation from the CMN period is the so-called - fermata. It is usually written as a dot above or below an arc. It - may stand above or below the staff it affects. If this symbol is used, its - open side always faces the staff. A fermata indicates that the note - or rest under it should be held longer than its written duration would normally require. - Sometimes, a fermata occurs over a barline to indicate the end of a phrase or section.

-

In MEI, fermatas may be encoded using an attribute on note, chord or rest. This attribute allows placement - of a fermata above or below the element to which it's attached.

- - - -

However, if there is further information about the fermata that should be addressed in - the encoding, MEI offers the fermata element. This element, which is - a member of the model.controlEventLike class and therefore - requires the use of such attributes as staff, layer, - tstamp and startid, allows specification of the orientation of the - fermata using its form attribute. In addition, the shape attribute - may be used to indicate whether the fermata is rendered as a semicircle ("curved"), - semisquare ("square"), or triangle ("angular"). If the fermata should be rendered using - some other symbol, a user-defined symbol may be referred to using an altsym or - extsym attribute.

- - - - - - - -
-
- Octave Shift -

An indication that a passage should be performed one or more octaves above or below its - written pitch is represented by the octave element.

-
- Octave displacement - -
-

Its dis and dis.place attributes record the amount and direction of - displacement, respectively. The lform attribute captures the appearance of the - continuation line associated with the octave displacement. The starting point of the - octave displacement may be indicated by either a tstamp, tstamp.ges, - tstamp.real or startid attribute, while the ending point may be - recorded by either a tstamp2, dur, dur.ges or - endid attribute. It is a semantic error not to specify one starting-type - attribute and one ending-type attribute.

-
-
- -
- Instrument-specific Symbols in CMN -

CMN contains a number of symbols which are closely related to a specific instrument. MEI - offers elements for three of these symbols, namely breath marks, harp pedal diagrams, and - piano pedals.

-
- Breath Marks -

A breath mark indicates a point at which the performer of a wind instrument - or singer may breathe. It is sometimes also used to indicate a short pause or break for - instruments not requiring breath, which allows it to also serve as a guide to - phrasing. In MEI, breath marks are encoded using the breath element, - which is a member of model.controlEventLike. It is a semantic - error not to specify a starting point attribute.

- - - - - - - - - - - - - -

The usual sign for the breath mark is a comma; however, other visual forms of the breath - mark may be indicated using the altsym attribute (see chapter for further details).

-
-
- Harp Pedals -

Modern harps have seven pedals which allow adjustment of their strings to different - pitches. The settings for these pedals occur at the beginning of the harp notation and/or - whenever it is necessary to change the harp's tuning. These settings may be rendered using - letter pitches (in the order of the pedals from left to right) or in a diagrammatic - fashion, such as the form invented by Carlos Salzedo.

-

In MEI, harp pedal settings are encoded using the harpPedal - element. It is a member of the model.controlEventLike class - and is therefore placed within measure, following all staff children. The staff and layer attributes - may be used to assign it to a certain staff or layer. Either a tstamp or startid attribute must be used to - indicate the placement within the measure (see and for further details about those linking mechanisms).

-

The musical intention of the element is described using the c, d, - e, f, g, a and b attributes, - which affect the corresponding strings of the harp. All of these attributes may take the - values "f" (flat), "s" (sharp) or "n" (natural), - where "n" is the default value, which is assumed when one of these attributes is not - specified.

- - - - - - - -

In the preceding example, the A, B, and E pedals are in the flat position, while the - other, non-specified pedals are in the natural position.

- -
-
- Piano Pedal -

Music for piano also often includes indications of the use of pedals. In MEI, these - symbols are encoded using the pedal element. As a member of the - model.controlEventLike class, it is located within measure and refers to a staff, layer and timestamp using the - staff, layer and tstamp attributes. Alternatively, the - startid attribute may be used to identify a note or chord to which the mark should be assigned.

-

The meaning of the mark is captured using the dir attribute, which provides - the following values:

- - - - depress the pedal - - - release the pedal - - - release, then immediately depress the pedal again - - - depress the pedal half way - - - - - - - -
- - -
- -
- Ossia -

The term ossia, Italian for "or", denotes an alternative for a certain passage - which is provided by the composer without any preference of one alternative - over another. An ossia often provides a simpler (easier to perform) version of the original - content. Another frequent use case for ossia is the provision of indications about - performance practice, such as an alternative version with ornamentation written out in full. - In all cases, it is up to the performer to choose between the alternatives.

- -

Most often an ossia is rendered above the main staff on a reduced-size staff. Sometimes, - however, the alternate material occurs on the same staff as the primary text, but in a - separate layer. In this case, the alternative material is usually rendered in small-sized - notation on the normal-sized staff. For both situations, MEI offers the ossia element, which may be nested either inside measure to - reflect an ossia on a separate staff, or inside staff to reflect an - inline ossia in a separate layer. The following example demonstrates an ossia on a separate - staff:

- - - - - - - - - - - - - - - - - - - -

The example above demonstrates that only one of the two staff - elements within ossia has an n attribute. This mechanism - allows one to distinguish between the "regular" and the "alternative" content: The one - bearing the n attribute goes in line with the preceding measure's staff, the - other one is printed in reduced size above. In this case, the vertical order of staves - follows document order: The top-most staff is encoded as the first child, the lowest comes - last. In combination with the presence of the n attribute, this allows the - capture of multiple simultaneous ossia staves.

-

All staves within ossia, even the alternative ones without a direct - reference, obey the definitions of the associated staffDef, which can - be derived from the value of the n attribute. Alternatively, a separate staffDef may be given at the beginning of the contained layer element(s).

-

In case of an inline ossia, the whole setup of elements moves down one step in the - hierarchy, as seen in the following example:

- - - - - - - - - - - - - - - - - - - - - - - -
- -
- Directions and Rehearsal marks -

In CMN scores, there is often a large number of natural language instructions. Some of them - concern the loudness and the speed of the performance, in which case MEI offers the elements - dynam (described at ) and tempo. In other cases, however, they provide other instructions for the performer. - Instead of providing separate elements for all possible types of such directions, MEI offers - the generic dir element. Although this element is not CMN specific (it - is defined in ), it is especially important in this repertoire.

-

A tempo or character indication is often provided above the topmost staff of the first - measure of a score, movement, or section. This indication, such as "Allegro moderato" or - "Andante maestoso", may be regarded as a label. Though it is possible to label the movement, - etc. using a label attribute attached to the enclosing structural entity (that - is, on mdiv or section), it is often required to - capture the exact position, spelling, or other features of the label as found in the - underlying source material. In these cases, an element is necessary.

-

Labels which address the tempo at which the music should be performed should be encoded - using the tempo element, which is a specialized form of dir. tempo is a member of the model.controlEventLike class and as such occurs as a child of measure, following all staff children. Its staff, - layer and tstamp attributes are used to ensure correct semantic - positioning, and place indicates a visual position with respect to the staff.

- - - - Allegro moderato - - - -

Rehearsal marks are another specialized kind of directive. Consisting of - letters, numbers, or a combination of both, rehearsal marks are used in scores and - corresponding performer parts to identify convenient points to restart rehearsal after - breaks or interruptions. For this reason, they are often visually emphasized by placing them - within a square or circle. In MEI, they are encoded using the reh - element, which holds the textual content of the rehearsal mark. The visual rendition of the - rehearsal mark, including the surrounding shape, may be captured using the rend element described in chapter .

-

The following detail from an edition of Hector Berlioz' Symphonie - Fantastique shows a typical example:

-
- Rehearsal mark - -
- - - - - - - - - - - - - 37 - - - - -

The following example demonstrates how rehearsal marks often apply to more than one staff. - In this instance, the rehearsal mark is placed above staff 1 and below staves 7 and 11.

- - - A - A - - - -
- -
- Repetition in CMN -

Repetition is a characteristic feature of music. Many musical forms rely on repetition - (sometimes with modification) of distinct sections of the music. Repetition in this sense - can be thought of as structural. At the same time, composers and - engravers of music often use local symbols for repeating smaller portions of music instead - of writing them in full more than once. In this case, the repetition is better defined as a - species of abbreviation.

-
- Structural Repetition -

Large-scale structural repetition, utilizing section and expansion elements, is discussed in section . This section will focus on repetition within sections. - -

-
-
- Measure-Level Repetition Symbols -

In addition to repetition at the section level, CMN includes a number of different - symbols for measure-level repetitions. Many of these symbols are found in manuscripts and - may be regarded as personal conventions of their respective authors. Some signs, however, - have been widely adopted. For example, it is common to indicate the repetition of a single - beat or an entire measure with one or more diagonal lines, sometimes with dots at the - upper left and lower right, much like a percent sign. The illustration below contains the - most common signs:

-
- Beat repeat signs - -
-

In general, MEI places primary emphasis on the capture of the semantic meaning of - symbols, not their visual rendition. In this case, the focus is on the material being - repeated, for example, a beat, a measure, a 2-measure fragment, etc. The following - elements are provided for this purpose:

-

- - - - - - - -

- -

The beatRpt element is used to represent a single repeated beat. - Its visual rendition can be recorded using the rend attribute. This attribute - indicates the number of slashes required to render the appropriate repeat symbol, which, - as demonstrated in the preceding figure, depends on the rhythmic content of the beat being - repeated. When a beat that consists of a single note or chord is repeated, the repetition - sign is typically rendered as a single thick, slanting slash; therefore, the value '1' - should be used. The following values should be used when the beat is divided into even - notes: 4ths or 8ths=1, 16ths=2, 32nds=3, 64ths=4, 128ths=5. When the beat is comprised of - mixed duration values, the symbol is always rendered as 2 slashes and 2 dots.

-

In addition to its indication of a repeated beat, the beatRpt element is sometimes used - in popular music notation, especially in guitar or percussion parts, to indicate a - repeated rhythmic pattern. The beatRpt element can be used, but when - these parts require durations longer or shorter than a beat, note elements with - appropriately-shaped note heads should be employed instead.

- - -

The mRpt element is available for repetition of an entire measure. - Like mRest, it must be the sole child of layer, no other events should be used. The n attribute of mRpt should not be used to record the number displayed above the - measure in the figure below. Instead, the numbering of repetitions of the written-out - measure can be enabled using the multi.number attribute available on the scoreDef and staffDef elements.

-
- Measure repetition - -
- -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - -

The halfmRpt element represents the incorrect, but frequently - found, use of the measure repeat (or similar) sign to indicate repetition of half of a - measure. This practice mostly occurs in hand-written notation and usually involves the - repetition of the second half of a measure in duple time. This element is necessary - because the function of the symbol, not the visual symbol itself, is of primary - importance. The following example from the beginning of Beethoven's - Waldstein sonata illustrates such usage:

-
- Half-measure repeat - -
- -
- - - - - - - - - - - - - - - - - - - - - - -
- - -

As seen in the example above, it is possible to continuously repeat half measures, even - across barlines.

-

The mRpt2 and multiRpt elements (like the multiRest element) never occur in scores, only in performer parts, - where it is often necessary to abbreviate the notation due to page size limitations.

-
- Two-measure repetition - -
-
- Multi-measure repetition - -
- -

The mRpt2 element represents repetition of a 2-measure fragment, - while multiRpt is for repetition of fragments longer than two - measures. In modern publishing practice, repeats of more than two measures are written out - using repeat signs. This element is provided, however, for handling non-standard practices - often found in manuscripts. The num attribute on multiRpt - records the number of preceding measures to be repeated.

-

All elements described above allow for association of the sign with a symbol in a digital - facsimile (via the facs attribute) and with a user-defined symbol (using - altsym). See and for - further details. In addition, the expand attribute is available on the - foregoing elements to inform a rendering process whether to use the repeat symbol or the - full content represented by it. A value of "true" indicates that the content should be - displayed, while a "false" value means to show only the repeat symbol.

-
-
-
- -
-
- Mensural Notation -

This chapter describes the module for encoding mensural notation from the late 13th century to - about 1600. Historically, mensural notation preceded the development of Common Music Notation - (CMN) and it included a wide range of features that persist in CMN and that can be encoded in a - standard manner in MEI. In mensural notation, pitches are notated as in CMN, leaving out here - the major exception of musica ficta. The pitch is given by the position of the note - on the staff and the current clef as in CMN, and the mensural module introduces no modification - to MEI regarding how pitches are encoded.

- -

There are a certain number of differences, however, regarding the representation of duration in - mensural notation. The mensural module introduces specific attribute values for notes and rests - for appropriately encoding mensural durations. One of the main particularities is that the - actual duration of a note is not given only by its symbol but also by position and the context - in which the symbol appears. The general context is given by one of the 16 mensural - species provide four levels of division: modus major, modus - minor, tempus and prolatio. Depending on the context, certain - rules must be applied in order to determine the duration of a note. In these cases, encoding - both the sign and its actual duration is highy desirable.

- -

Another particularity of mensural notation is the use of proportions that are indicated by - numeric proportions or by specific mensuration signs. The proportions indicate that the - durations have to be modified accordingly and they can be combined in a very complex manner. - Over time, proportions and mensuration signs were simplified and became time signatures in CMN. - The attributes and elements that are necessary for encoding proportions and mensural signs are - made available by the module.

- -

In mensural notation, notes can also be notated in ligatures that regroup two or more notes. - Ligatures were a legacy from an earlier notation system that were still widely used in - Renaissance music notation. They gradually disappeared during the seventeenth century. The - mensural module provides multiple ways of encoding the ligatures.

- -
- Note and Rest Values -

When the mensural module is included, dur on note, rest, and other elements can take the following values:

- - maxima - longa - brevis - semibrevis - minima - semiminima - fusa - semifusa - - -
- Actual Duration with Alterations and Imperfections -

In ternary divisions, the dichotomy between the duration sign of the notes and their actual - duration requires specific attention. The rules of mensural notation can require the - alteration or the imperfection of a note; that is, an increase or reduction in its performed - duration. In these cases, if the encoding is intended to be suitable for more than just - graphically representing the notation, encoding only the duration of the sign can quickly - become insufficient. It that case, it is recommended to encode the sign in the - dur attribute and its performed duration using the num and - numbase attributes.

- -

The following example illustrates an alteration (the second brevis) in - modus minor perfectus and tempus imperfectum. The performed - duration of each note is given as a proportion of a whole note using the num and - numbase:

- - - - - - - - - - -

The following example illustrates an imperfection (the two longae) in - modus minor perfectus and tempus perfectum with the same - longa-brevis-brevis-longa sequence but - with an additional punctus divisionis between the two breves:

- - - - - - - - - - - -
- -
- -
- Mensuration Signs - -

Using the mensural module, mensuration signs can be indicated with the attributes available - on the scoreDef and staffDef elements. Mensuration - signs encoded using attributes on scoreDef are regarded as default - values which may be overridden by values attached to individual staffDef - elements.

- -

The division levels corresponding to modus maior, modus minor, - tempus and prolatio can be encoded in the modusmaior, - modusminor, tempus and prolatio attributes respectively. - Their value must be 3 (perfect) or 2 (imperfect).

- - - -

The mensur signs themselves can be encoded in the sign attribute with a possible - value of "C" or "O". Its orientation can be encoded in the orient attribute, for - example, with the value "reversed" for a flipped C sign. The number of slahes (up to 6) can be - given in the slash attribute. There is also a dot attribute for - indicating the presence of a dot.

- - -

mensur elements can also be used instead of staffDef and its attributes.

- - -
- -
- Proportions - -

Proportions can also be indicated within the staffDef element. The - num and numbase attributes are available for encoding the numerator - and the denominator of the proportion respectively. There is also a proport element that can be used as an alternative.

- -
- -
- Ligatures - -

Ligatures can be encoded using the ligature element. The - form attribute is available for specifying if the ligature is recta or - obliqua.

- -
- Recta and obliqua ligatures - -
- - - - - - - - - - - - - - -

In cases where the ligature contains both recta and obliqua notes, the lig - attribute of the note element can be used to specify the form of the - ligature at the note level.

- -
- Ligature with more than two notes with recta and obliqua - -
- - - - - - - - - - - - -

-
- - -
- Music Data Organization -

The data organization based on measure elements that usually prevails - in MEI is not appropriate for mensural notation because most music until 1600 was written in a - non-measured manner. Even though it is not defined by the mensural module, a more suitable - alternate data organization without measures is available: staff - elements may occur directly within the section element without being - organized into measures first. The organization of events (notes, rests, etc.) within the staff and layer elements remains unchanged.

- - -
- - - - - - - - - - - - -
- - -

This feature may also be used to encode measured music without using the measure element. That is, the same data organization described above may be used, but - with the addition of barlines, indicated by the barLine element, for - those situations where a measure-by-measure organization is not appropriate, for exampe, when - measures are not coincident in all the staves of a score.

- - -
- - - - - - - - - -
-
- Neume Notation -

This chapter describes the elements, model classes, and attribute classes that are part of the - MEI.neumes module.

- -
- - Overview of the Neumes Module -

The module described in this chapter makes available the following components:

-

- - - - -

-
-
- Module Background -

Neume encoding in MEI was initially developed as part of the Hildegard von Bingen project at - the University of Tübingen. MEI was chosen as the basic representation format after a comparison of existing - music encoding formats. The initial work on this module was performed by Gregor - Schräder (Ein - XML-Datenformat zur Repräsentation kritischer Musikedition unter besonderer Berücksichtigung - von Neumennotation), supervised by Prof. Stefan Morent.

-

This module was originally developed against version 1.8 of the MEI DTD, and has subsequently - been translated to the TEI ODD schema.

-
-
- Neume Notation -

Most neume notation is used to set music to an existing text. The syllable is the fundamental - unit of structure, with the neumes themselves serving as a means of "sonifying" the text. A - syllable may be expressed via one or more neumes, with the particular neume shape chosen - depending on the pitch contour that is being employed and the desired interpretation. For - example, two pitches in rising succession might be encoded as a "podatus" (sometimes also - called a "pes"), or it might be encoded as two separate punctums, depending on whether it - should be sung smoothly connected or with a slight amount of space between the notes.

-

There are a limited number of possiblities for the most popular musical contours. In general, - groups of two to four notes are given unique names, assigned depending on their contour. A - "clivis" would be two joined descending notes, while a "podatus" is two joined ascending - notes. Table 1 shows most of the named neume shapes. Neume groups of more than four notes are - simply called "compound" neumes.

-
- Table 1. Variant neume notation. (From Parrish, "The notation of medieval music," - 6) - -
-

As shown in Table 1, it is possible to have many different styles of neume shapes, derived - from local practices of regional groups. In general, these styles are all interpreted in a - similar fashion; however, there is evidence that the performance practice of some styles of - neume notation differed with regard to rhythm and cadence. This version of the MEI neumes - module does not attempt to encode any rhythmic information present in the neume notation. - While it may be possible to encode rhythmic values on note elements, - this practice is highly discouraged and, if present, should be interpreted as a modern - transcription not present in the original sources.

-

Neume notation existed before the invention of the staff. Staffless neume notation - ("adiastemtic", "cheironomic" or "in campo aperto") existed primarily as a mnemonic device, - reminding performers of the contour of the melody but lacking any absolute pitch information. - These neumes were written above the text. With the invention of the staff lines and the clef, - "heightened" or "diastematic" neume notation could be used to provide exact interval - information. In some cases the staff lines are not actually drawn on the page, but their - position relative to an imaginary line and initial clef is consistent.

-

The syllable element is used as the primary organizational element for - neume notation within a layer element. Within syllable, the syl element defined in the MEI.shared module is - used for encoding the textual content, while the nc and nc elements are used to encode the neumes themeselves. Within these - neume module elements, other standard MEI mechanisms are available to accommodate, for - example, editorial or critical markup.

-
-
- Examples -

Some of these examples are excerpts from works of Hildegard von Bingen, with the encoding - performed by Stefan Morent and Gregor Schräder.

-
- Basic Encoding -

The example illustrates the most basic encoding of neume notation. Encoded here is the - opening of Hildegarde's "O Splendidissima Gemma" with the text "O splendidissima". - Information about the staff has been omitted for brevity, but it was originally encoded on a - 5-line staff with two clefs, a "C" and a "F" on lines 5 and 3, respectively.

- - - - - O - - - - - - - - - splen_ - - - - - - - - - - - di_ - - - - - - - - - - - - - - dis_ - - - - - - si_ - - - - - - - - - - - - - - ma - - - - - - - -
-
- Encoding Variants -

Variant readings across sources may be encoded. In this example, source "D" has a punctum - on the syllable "so" that is not present in source "R".

- - - so_ - - - - - - - - - - - - - -
-
- Supplied Notes -

In the case of neume notation where no absolute pitch is indicated, you may use the supplied element to indicate an editorially-added pitch. This element's - source attribute may be used to supply a reference to a source with the - absolute pitch provided.

- - - so_ - - - - - - - -
-
-
-
- Analytical Information -

This chapter describes the use of attributes that capture data which may be useful for - analytical purposes. The analysis module provides attributes that record relationships between - entities found in the encoding. These attributes may be used differently by different users, - depending on the purpose of the analysis. These Guidelines recommend that encoders employ - commonly accepted analytical practices, such as "functional analysis" or "Schenkerian analysis", - and document their use in the encodingDesc described in section . For general information on musical analysis, please - consult Grove Music Online, "Analysis".

-
- General Relationships Between Elements -

The relationships between event elements, such as note, chord, and rest, are the basic - material of musical analysis; the attributes described below ensure a closed network of these - relations and provide the opportunity to record data useful for common analytical tasks. In - the context of a formal analysis, for instance, the attributes presented here can be useful in - the capture information about the structure of a musical work.

-

The analysis module offers several attributes in the att.linking class for the description of basic relationships:

-

- - - -

-

The att.alignment class also contains an attribute for describing - temporal relationships:

-

- - - -

-

These attributes accommodate the encoding of linkages between the element carrying the - attribute and one or more other elements. All of them use URIs to establish the connection. - While the examples below illustrate relationships between musical events, their use is not - restricted to musical events. On the contrary, these attributes can be used to capture - information about relations between any elements.

-

Using these attributes makes it possible to create relationships between events, which are - often widely-spaced in both encoded order and time. The attributes allow a large number of - connections, enhancing the informational content, and therefore the potential usefulness, of - the encoding.

-

The copyof attribute points to an element of which the current element is a copy. - It can be used to repeat a note, for example, without encoding the whole note element again. The copy is a deepone; that is, the - copyof attribute copies all attributes and child elements which belong to the - copied element, such as the dur and oct attributes of a copied note. The value of the copyof attribute must be a URI, which - usually refers to an element in the current document. The following example demonstrates use - of the copyof attribute:

- -
- - - - - - - - - - - - - - -
- -

In this example. the note in the second measure has exactly the same - characteristics as the note in the first measure.

-

Using copyof is not limited to copying events. The copyof attribute can - also be used to copy an entire measure or staff. - When there are many repeated features, the use of the copyof greatly reduces - encoding effort. The image and the following encoding of the beginning of Schubert's - Erlkönig illustrates the benefit of using the copyof - attribute.

-
- First measure of Schubert's Erlkönig - -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

This example can be reduced further by using copyof inside the initial tuplet to - represent the repeated chords:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

While copyof signifies a duplicate copy of an element, the sameas - indicates that the current element represents exactly the same entity as the one referenced in - sameas. Use of sameas is used for describing the same entity from - multiple perspectives, e.g., the same event in two layers. The following example illustrates - the sharing of one note head between two voices in the first full measure of a chorale:

-
- Bach Chorale, Ach Gott, vom Himmel sieh' darein, m. 1-2 - -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

While copyof and sameas have defined semantics, the corresp - may be used to create user-defined relationships between elements. The example below - demonstrates the encoding of a relationship between #note3 and the fermata, even though the - fermata is not placed directly above the note.

- - - - - - - - - - - - -

The corresp attribute only marks the correspondence between the current element - and one or more other entities. To describe the nature of the correspondence, one must use annot.

-

The next and prev attributes point to elements which follow or precede - the current element in some fashion other than that indicated by encoding order. The use of - these attributes helps to avoid confusion in the sequence of events, for example, in voice - leading across layers or staves, when the encoding reflects the physical arrangement of - voices. In the second measure of the following example, the target of the next attribute - occurs after the pointing element in time, but before it in encoding order:

-
- Bach Chorale, Ach Gott, vom Himmel sieh' darein, m. 6-7 - -
- -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -

This attribute may also be useful to clarify a sequence of entites which occurs across some - form of interruption, in this case, notes before and after a system or page break where there - is no custos or direct in the source:

- - - - - - - - - - - - -

A one-to-many relationship between the current element and the entities being referred to can - be expressed by using a list of space-separated URIs in corresp.

-

The synch attribute points to an element that is synchronous with; that is, begins - at the same moment in time, as the current element. It is useful when the encoding order - differs from the order in which entities occur in time.

- - - -

The when attribute may be used to indicate the point of occurrence of the feature - bearing this attribute along a time line. Its value must be the ID of a when element. For more detailed information regarding the use of when, - please see .

- -
-
- Event-Specific Analytical Information -

In addition to the common analytical attributes, the analysis module also offers other, more - specific attributes on certain musical elements:

-

- - - - - - - - -

-
- Melodic Intervals -

Theintm attribute offers several methods for encoding the melodic interval from - a preceding pitch. First, Parsons Code allows for description of the contour of the melody - in very general terms; that is, as up, down, or same note. Parsons Code is helpful for - identifying musical works with clearly defined melodies and analyzing the relationship - between successive notes of monophonic tunes. For more information about the Parsons Code, - please see the "The Directory of Tunes and Musical Themes" by Denys Parsons (2002). The next - example shows interval relationships indicated by the Parsons Code:

- - - - - - - - - - - - - - - -

Alternatively, diatonic interval quality and size may be indicated by a letter signifying - the interval quality (A= augmented, d= diminished, M = major, m = minor, P = perfect) - followed by a number indicating the size of the interval. The interval direction may be - encoded using a leading plus (+) or minus (-) sign:

- - - - - - - - - - - - - -

As a third option, signed integers may be used to record the difference in half steps - between the previous pitch and the current one. Decimal values accommodate the description - of microtonal intervals:

- - - - - - - - - - - - -
-
- Melodic Function -

The mfunc attribute describes melodic function of a note - or neume using the Humdrum **embel syntax. In the following example, the note B is labeled - as a lower neighbor while all other notes are labeled as chord tones:

- -
- - - - - - - - - - - - - - - - - - - - - - - -
- - -
-
- Harmonic Intervals -

- - - -

-

In contrast with intm, which characterizes melodic (sequential) intervals, the - inth attribute is used to encode the harmonic interval between the current note - and other pitches occurring at the same moment in time. The notes of interest may or may not - be marked as a chord. In the markup below, for example, the values of - inth capture the harmonic intervals between notes distributed across multiple - staves and layers.

- - - - - - - - - - - - - - - - - -

Use of the inth permits detailed specification of intervallic information for - every note and its function in relation to other simultaneously-occurring notes and hence - about the harmonic nature of the musical work.

-
-
- Scale Degrees -

- - - -

-

The deg attribute can be used to represent key-dependent scale-degree - information for music in major or minor keys.

-

Scale-degree values are relative to the prevailing major or minor key. In the case of minor - keys, scale degrees are characterized with respect to the harmonic minor scale. For example, - the pitch F in the key of A minor is the submediant (6), but F is the lowered submediant - (6-) in the key of A major.

-

Melodic approach can be indicated by a leading caret (^) or lowercase v, representing - ascending and descending approaches, respectively.

-

Chromatic alteration of the scale degree can be represented using a trailing plus (+) or - minus (-) signs, signifying raised or lowered scale degree, respectively. The actual amount - of chromatic alteration is not indicated.

- - - - - - - - - - - - - - - - -
-
- Pitch Class -

The pclass attribute can be used to encode information about the pitch class to - which a note belongs. The attribute's value must be an integer less than or equal to 11. It - is only allowed on the note element. The pclass attribute - comes from "musical set theory" elaborated first by Howard Hanson and Allen Forte as a new - method for organizing tones. It provides a concept for categorizing musical objects (notes) - and describing their relationships. It is a kind of grouping and combining, mostly developed - in connection with atonal music. However, the concept of set theory is general and can also - be applied to tonal music. A pitch class means the summary of every pitch with specific - characteristics that means a pitch class set is an unordered collection of pitches, e.g., - every pitch with the name C.

-

A pitch class may contain a large number of pitches, because different octaves and - enharmonic spellings of pitch make no difference. The notes C, E, and G would be 0, 4 and 7 - in pitch class notation, for example, regardless of the octave in which they are performed. - The example below contains the same pitch in four different enharmonic spellings, but all - are part of the same pitch class. -

- - - - - - - - -

For further information on pitch class set theory, please consult the following - sources:

- - http://www.mta.ca/faculty/arts-letters/music/pc-set_project/pc-set_new/pages/introduction/toc.html - "Analyzing Atonal Music: Pitch Class Set Theory and its Contexts" by Michael Schuijler - (2008) - Cohen, Allen Laurence (2004). Howard Hanson in Theory and Practice - -
-
- Solmization -

Solmization is a system which associates a syllable with each note of a musical scale. - There are various forms of solmization used throughout the world. In Europe and North - America, solfège is the most common practice. In this system, the seven syllables for a - major scale are do, re, mi, fa, so, la and ti. In the fixed-do system, - the syllable "do" is always associated with the pitch "c", while in the - movable-do system, "do" is associated with the tonic note. The - psolfa attribute is only allowed on note and nc elements. Its value is unconstrained in order to accommodate - various solmization systems.

- - - - - - - - - - - - -
-
-
- Metrical Conformance -

It is often helpful to record whether a given staff, layer, or measure obeys the meter - established for it. The following attributes are provided for this purpose:

-

- - - - -

-

When used on staff or layer elements, the - metcon attribute can be used to indicate if the duration of the contained events - is equal to ("c"), less than ("i"), or greater than ("o") that predicted by the time - signature. When used on the measure element, metcon takes a - boolean value, where "true" indicates conformance by all staff and layer descendants of the - measure.

-

In the first example below, the layer, staff, and measure all match the prevailing meter. In - the second example, however, the first layer does not comply with the meter, making the staff - containing it and measure as a whole non-compliant. When there is a single layer or when all - the layers on a staff agree with each other, metrical compliance can be indicated on the staff element. When, however, not all layers have the same value for - metcon, then it is necessary to omit metcon at the staff level. The - value of metcon on the measure level can usually be computed based on the values of - its layer and staff sub-elements.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-
-
- Common Music Notation Ornaments -

This module includes elements and attributes for the encoding of ornaments typical of - Common Music Notation (CMN). Ornaments are formulae of - embellishment that can be realized by adding supplementary notes to one or more notes of the - melody. In written form, these are usually expressed as symbols written above or below a note, - though some have a more complex written expression, such as those that involve multiple notes - and/or include grace notes.

-

These symbols may have different resolutions depending on a large number of factors, such as - historical context, national boundaries, composer, scribe, etc. The elements described here, - therefore, are not bound to a specific symbol; they are, instead, meant to encode the encoder's - interpretation of a symbol and its position on the staff.

-

Nonetheless, in order to establish common ground, the guidelines suggest commonly accepted - symbols and realizations for the ornaments supported by MEI.

-

The following sections will introduce each element in detail for all types of ornaments - supported.

- -
- Encoding Common To All Ornaments -

When encoding CMN, ornaments should be encoded within a measure, - following the staff elements, and connected to events on the staff via - attributes. The startid attribute is used to refer to the xml:id of the - starting note. Additionally, if the ornament involves more than one events on the staff, the - endid attribute can be used to anchor the ornament to a concluding event.

-

The following example demonstrates the encoding of an inverted mordent over a middle C:

- - - - - - - - - - -

Alternatively, the relationship of an ornament to a note can be expressed in terms of beats - with the attribute tstamp. If the ornament involves more than one event on the - staff, the tstamp2 attribute can be used to indicate the ending time stamp, as is - explained in section . These methods may also be utilized - simultaneously.

- -

The following example shows the use of tstamp for an ornament. Assuming that the - following measure is in 2/2, the ornament (in this case, a mordent) is related to the note on - the second beat.

- - - - - - - - - - - -

The relationship between an ornament and the notes on staff must always be encoded. It is, in - fact, a semantic error not to specify a starting event or time stamp for an ornament.

- -

In their resolution, ornaments will involve auxiliary notes, which typically follow the key - signature or the scale of the current key. When the ornament involves other chromatic - auxiliaries, an accidental is expressed next to or above the ornament sign. The attributes - accidlower and accidupper, available on all ornaments described in - this chapter, can be used to record this accidental. The attribute values - upper and lower indicate whether the accidental is - associated with an upper or lower auxiliary note, not the position of the accidental sign.

- -
- Overriding Default Resolutions -

The symbols and sounded resolutions suggested for each ornament in this chapter are to be - considered defaults. Nevertheless, because of the great historical and geographical variance - in the notation of ornaments, the encoder is given methods to override the default - resolutions.

-

It is possible, for example, to specify in the meiHead a new default - sounded resolution for an ornament. As discussed in the section , the element encodingDesc - holds a description (optional, but recommended) of the methods and editorial principles - which govern the transcription or encoding of the source material. Let us take a trill as an - example. The section regarding trills does not set a - specific number of alternations between the principal and secondary notes; the encoder, - however, may specify an exact number in the encoding description.

- - - -

All trills should be resolved by playing three alternations.

- - - - -

Alternatively, resolutions can be defined on a case-by-case basis by encoding a specific - resolution using the choice element. See the section below for an example of a specific resolution of a - trill.

-
- -
- -
- Mordents -

A mordent is an ornament that involves an auxiliary note a step above or below the principal - note. The presence of a mordent is encoded with the mordent element and - its attributes:

- -

- - - - - -

- -

It is recommended, but not required, to use the attribute form to encode the - typology of mordents. Two common types are supported: those mordents that involve a note lower - than the principal note, and those that involve a note higher than the principal note.

- -

The attribute form accepts the following values:

- - - - usually corresponding to the symbol: . This mordent is - commonly performed as the principal note, followed by its lower neighbor, with a return to - the principal note. - - - usually corresponding to the symbol: . This mordent is - commonly performed as the principal note, followed by its upper neighbor, with a return to - the principal note. - - -

The following example demonstrates the encoding of simple mordents:

-
- Example of simple mordent - -
- - - - - - - - - - - - - - -

Occasionally, mordents can be longer, employing five notes instead of three. The - long attribute can be used to identify mordents of this type. The following - example shows the encoding of a long mordent:

-
- Example of a long mordent - -
- - - - - - - - - - - - - -
- -
- Trills -

Trills are a type of ornament that consists of a rapid alternation of a note with one a - semitone or tone above. A trill is encoded with the trill element and - its attributes:

-

- - - - -

- -

Trills in modern notation are usually expressed with the abbreviation "tr" above a note on - the staff. Often the abbreviation is followed by a wavy line that indicates the length of the - trill.

- -

The following example demonstrates the encoding of simple trills:

-
- Example of simple trills. - -
- - - - - - - - - - - - - - - - - - -

It has been specified earlier that it is a semantic error not to encode a starting event or - time stamp for an ornament. This starting point of a trill can be expressed with the - startid attribute and/or with the tstamp attribute. Specifying the end - point is not required, although the tstamp2 attribute can be used to indicate the - use of a wavy line extender as shown in this example:

-
- Example of trills followed by wavy lines. - -
- - - - - - - -
- - - - - - - - - - - - - - -
- - - -

Chromatic alterations of auxiliary notes are occasionally expressed on the staff using small - notes enclosed in parentheses, as shown in the example below. However, the attribute - accidupper is still to be used to encode the alteration. Display of the auxiliary - note in this cautionary manner is left to down-stream rendering - processes.

-
- Example alterations expressed on the staff. - -
- - - - - - - - - - - -

Some trills may be introduced by a turn or followed by an inverted turn leading to the next - note (see Le garzantine, Musica 2003, p. 911). In such cases, the trill is - encoded as in previous examples and associated with the principal note. Starting or concluding - turns are notated on the staff (in layer) as grace notes.

- -

The following example, from a keyboard sonata by Joseph Haydn, shows a trill with concluding - grace notes:

-
- Haydn, Sonata in D major, Hoboken XVI:33 (Wiener Urtex no. 34), mvmt. 1. - Example of trill introduced and concluded by turns expressed as grace notes. From - Haydn's keyboard sonata in D major. - -
- - - - - - - - - - - - - - - - -
- Special Cases - -

Symbols and abbreviations for trills have changed and evolved considerably throughout - history. Strategies to clarify the encoding and interpretation of ornaments have been - discussed in section above. However, in order to aid - the encoder in making educated choices in the encoding of non-standard trills, this section - shows two examples diverging from modern standard use.

- -

The abbreviation "tr" followed by a wavy line spanning multiple notes is sometimes used to - indicate multiple trills:

-
- Example of multiple trills. - -
-

The encoding of this kind of trill may vary depending on the purpose of the encoding. For - representation of the source, a single trill is sufficient:

- - - - - - - - - - - - - - - -

To support analytical and aural rendering applications, however, each trill may be - explicitly encoded, as the following example demonstrates:

- - - - - - - - - - - - - - - - - - -

However, when it is necessary to support multiple outputs, use of the choice element and appropriate sub-elements is recommended. In this case, the orig and reg elements can be used to represent the - original source and a regularization provided by the editor, respectively:

- - - - - - - - - - - - - - -

Another situation that requires disambiguation of an ornament's name and its potential - rendition is due to the fact that the symbols for trills and mordents have been often used - interchangeably in the past. The following example, taken from Klavierbüchlein für - Wilhelm Friedemann Bach (1720), shows a trill (Trillo) identified by the - symbol associated with a mordent in modern practice. Nonetheless, J.S. Bach's suggested - resolution should be encoded with a variant of the procedure presented above.

-

In the example below, the child elements of choice; that is, orig and reg, represent non-exclusive options; - that is, both may be processed by applications that aim to support both visual and aural - renditions.

-
- Trill transcribed from J.S. Bach's Klavierbüchlein für Wilhelm Friedemann - Bach (1720) - -
- - - - - - - - - - - - - - - - - - - - - - - -

Depending on the purpose of the encoding, it may be more convenient to encode the - regularized text within the stream of events, along with a corresponding choice with regard - to the existence of the trill marking, as in the following example:

- - - - - - - - - - - - - - - - - - - - - - - - - - - -

The orig element contains the single-note-with-trill transcription of - the original text, while the reg element represents the - realization-without-trill version.

-

This approach facilitates substitution of the realization of the trill for the original - written note (as well as the opposite procedure) and is therefore the recommended markup for - applications where exchange of this kind is desirable.

-
- -
- -
- Turns -

A turn is an ornament that typically consists of four notes: the upper neighbor of the - principal note, the principal note, the lower neighbor, and the principal note again.

- -

The presence of a turn is encoded with the turn element and its - attributes:

- -

- - - - -

- -

It is recommended, but not required, to use the attribute form to encode the - typology of the turn.

- -

The attribute form accepts the following values:

-

- - - - usually corresponding to the symbol: . This turn is commonly - performed beginning on a note higher than the principal note. - - - usually corresponding to the symbol: . This turn is commonly - performed beginning on a note lower than the principal note. - -

- -

The following example shows the encoding of a simple turn:

-
- Example of a simple turn. - -
- - - - - - - - - - - - - - -

Turns can sometimes be performed after the principal note (usually on the second half of the - beat, see Read 1979, p. 246) and leading to the following event. To indicate - this, the turn symbol is typically written in between the principal note and the next. These - kind of turns are encoded with the attribute delayed.

- -

The following example from Beethoven's piano sonata no. 1 in F minor, op. 2, no. 1, mvmt. 2 - demonstrates the encoding of turns with the delayed attribute. Note that the - tstamp attribute indicates the actual starting point in time, while - startid points to the principal note.

-
- Delayed turn. - -
- - - - - - - - - - - - - - -
- -
- Other Ornaments -

CMN ornaments that are not mordents, trills, or turns can be encoded with a generic ornam.

-

This element allows the encoder to represent ornaments as textual strings (e.g. with a - Unicode symbol) or with a user defined symbol. Chromatic auxiliaries can be represented with - accidlower and accidupper. The ornam element can - also be a control element. That is, it can be linked via its attributes to other events. The - starting point of the directive may be indicated by either a tstamp, tstamp.ges, tstamp.real - or startid attribute, while the ending point may be recorded by either a tstamp2, dur, dur.ges - or endid attribute. It is a semantic error not to specify a starting point attribute.

-

For example, Johann Sebastian Bach used non-standard ornaments in the Klavierbüchlein - für Wilhelm Friedemann Bach:

-
- Table of ornaments used by Johann Sebastian Bach in the Klavierbüchlein für Wilhelm - Friedemann Bach - -
-

The ornament for (5) doppelt-cadence could be encoded in the following way, by - adopting the Unicode code-points defined by the SMuFL standard:

- -&#xe5c0; - -

A resolution, or expansion of the ornament can be provided as discussed in below.

-
- -
- Ornaments in Combinations -

Particularly in baroque keyboard music, but also in the early classical period, various - combinations of ornaments can be found. Despite being written vertically above the same note, - they are to be performed in sequence.

-

The following example from C.P.E. Bach's sonata W.62/1 shows a turn followed by a inverted - mordent:

-
- Example of multiple ornaments. From C.P.E. Bach's sonata W.62/1. - -
-

When encoding the example above, both ornaments will be positioned above the same note. The - encoded order of the elements, moreover, should correspond to the performed sequence, which in - this example is top to bottom: first the turn, then the mordent.

- - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
-
- Musical Corpora -

The term corpus may refer to any collection of musical data, although it is often - reserved for collections which have been organized or collected with a particular end in view, - generally to illustrate a particular characteristic of, or to demonstrate the variety found in, - a group of related texts. The principal distinguishing characteristic of a corpus is that its - components have been selected or structured according to some conscious set of design - criteria.

-

In MEI, a corpus is regarded as a composite text because, although each discrete document in a - corpus clearly has a claim to be considered as a text in its own right, it is also regarded as a - subdivision of some larger object, if only for convenience of analysis. In corpora, the - component samples are clearly distinct texts, but the systematic collection, standardized - preparation, and common markup of the corpus often make it useful to treat the entire corpus as - a unit, too. Corpora share a number of characteristics with other types of composite texts, - including anthologies and collections. Most notably, different components of composite texts may - exhibit different structural properties, thus potentially requiring elements from different MEI - modules.

-

Aside from these high-level structural differences, and possibly differences of scale, the - encoding of language corpora and the encoding of individual texts present identical sets of - problems. Therefore, any of the encoding techniques and elements presented in other chapters of - these Guidelines may therefore prove relevant to some aspect of corpus encoding and may be used - in corpora.

-
- Corpus Module Overview -

The meiCorpus module defines a single element:

-

- - - -

-

The meiCorpus element is intended for the encoding of corpora, though - it may also be useful in encoding any collection of disparate materials. The individual - samples in the corpus are encoded as separate mei elements, and the - entire corpus is enclosed in an meiCorpus element. Each sample has the - usual structure for a mei document, comprising an meiHead followed by a music element. The corpus, too, has a - corpus-level meiHead element, in which the corpus as a whole, and - encoding practices common to multiple samples may be described. The overall structure of an - MEI-conformant corpus is thus:

- - - - - - - - - - - - - -

This two-level structure allows for metadata to be specified at the corpus level, at the - individual text level, or at both. However, metadata which relates to the whole corpus rather - than to its individual components should be removed from the individual component metadata and - included only in the meiHead element prefixed to the whole.

-

In some cases, the design of a corpus is reflected in its internal structure. For example, a - corpus of musical incipits might be arranged to combine all compositions of one type - (symphonies, songs, chamber music, etc.) into some higher-level grouping, possibly with - sub-groups for date of publication, instrumentation, key, etc. The meiCorpus element provides no support for reflecting such internal structure in the - markup: it treats the corpus as an undifferentiated series of components, each tagged with an - mei element.

-

If it is essential to reflect the organization of a corpus into sub-components, then the - members of the corpus should be encoded as composite texts instead, using the group element described section . The mechanisms - for corpus characterization described in this chapter, however, are designed to reduce the - need to do this. Useful groupings of components may easily be expressed using the - classification and identification elements described in section , and those for associating declarations with corpus components described in section . These mechanisms also allow several different - methods of text grouping to co-exist, each to be used as needed at different times. This helps - minimize the danger of cross-classification and mis-classification of samples, and helps - improve the flexibility with which parts of a corpus may be characterized for different - applications.

-

All composite texts share the characteristic that their different component texts may be of - structurally similar or dissimilar types. If all component texts may all be encoded using the - same module, then no problem arises. If however they require different modules, then the - various modules must all be included in the schema. - -

-
-
- Combining Corpus and Text Headers -

An MEI-conformant document may have more than one header only in the case of a TEI corpus, - which must have a header in its own right, as well as the obligatory header for each text. - Every element specified in a corpus-header is understood as if it appeared within every text - header in the corpus. An element specified in a text header but not in the corpus header - supplements the specification for that text alone. If any element is specified in both corpus - and text headers, the corpus header element is over-ridden for that text alone.

-

The titleStmt for a corpus text is understood to be prefixed by the titleStmt given in the corpus header. All other optional elements of the - fileDesc should be omitted from an individual corpus text header - unless they differ from those specified in the corpus header. All other header elements behave - identically, in the manner documented in chapter . This makes it - possible to state information which is common to the whole of the corpus in the corpus header, - while still allowing for individual texts to vary from this common metadata.

-

For example, the following markup shows the structure of a corpus consisting of three texts, - the first and last of which share the same encoding description. The second one has its own - encoding description.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-
- Recommendations for the Encoding of Large Corpora -

These Guidelines include proposals for the identification and encoding of a far greater - variety of textual features and characteristics than is likely to be either feasible or - desirable in any one corpus, however large and ambitious. For most large-scale corpus - projects, it will therefore be necessary to determine a subset of recommended elements - appropriate to the anticipated needs of the - project; - these mechanisms include the ability to exclude selected element types, add new element types, - and change the names of existing elements.

-

Because of the high cost of identifying and encoding many textual features, and the - difficulty in ensuring consistent practice across very large corpora, encoders may find it - convenient to divide the set of elements to be encoded into the following four categories: - - - - texts included within the corpus will always encode textual features in this - category, should they exist in the text - - - textual features in this category will be encoded wherever economically and - practically feasible; where present but not encoded, a note in the header should be - made. - - - textual features in this category may or may not be encoded; no conclusion about - the absence of such features can be inferred from the absence of the corresponding element - in a given text. - - - textual features in this category are deliberately not encoded; they may be - transcribed as unmarked up text, or represented as gap elements, or - silently omitted, as appropriate. - -

-
- -
-
- Critical Apparatus -

This chapter describes how to encode differences between multiple exemplars of the same musical - work (often referred to in MEI as sources). The mechanisms and elements - described in this chapter are closely related to their counterparts in the TEI guidelines. It is - also important to refer to chapter of these guidelines, especially - concerning the choice element described therein.

-
- General Usage -

The following elements are defined in the critApp Module:

-

- - - - - -

-

An app element always encapsulates the differences between varying - sources. Therefore, it must contain at least two child elements. - Possible child elements are lem and rdg, which use the same model, but have a different - meaning: Whereas lem is used for prioritizing one alternative, a rdg has no such additional meaning and simply indicates a reading as found - in one or more sources. Accordingly, lem is allowed only once in app, whereas rdg may appear as often as - necessary.

- - - - - - - - - - - - - - -

The rdg (and lem) elements use the - source attribute to point to one or more descriptions of the bibliographic - sources containing the material they mark:

- - - - - - - - - - - - - - - - - - - - - - - - - - -

The seq attribute may be used on lem or rdg to record the sequence of a series of readings. In the following example, the - material in source B is marked as sequential to (and perhaps derived from) the reading in - source A:

- - - - - - - - - - - -

If a source has additional content that is not found in other sources, an empty rdg element may be used to indicate the lack of material in the other - sources. In the following example, source 1 includes material that is not found in sources 2 - and 3:

- - - - - - - - - -

When working with a large number of sources, it might seem tedious to provide references for - all sources. However, use of the rdg element without source - is not recommended because such an encoding is not explicit and is therefore difficult to - process.

-
-
- Variants in Musical Content -

The app element may be used to accommodate textual variation at nearly - any point in a musical text. For example, it may be used to indicate minor differences such as - stem directions:

- - - - - - - - - - - - - - - -

or to indicate more significant differences, such as the insertion of extra measures:

- -
- - - - - - - - - - - -
- - - - -

However, the flexibility in the location of app places a burden on the - encoder to ensure that the app, rdg, and lem elements are used correctly; that is, the content of every rdg and lem has to be a valid replacement for its - parent app.

- - -
-
- Variants in Score Definitions -

In addition to its use for differentiation of the musical content of multiple sources, app may also be utilized to describe the layout of different scores, even - when the musical content itself remains the same. An example of this is two sources that have - the same content, but a different ordering of staves on which the content is written. By - definition, the order of staves is derived from the order of staffDef - elements in scoreDef, not from the order of staff - elements within a measure. The staff element in a - measure points to its corresponding staffDef using either 1) the same - value for n on both elements, or 2) a value in def which is an explicit - reference to a particular staffDef using its xml:id - value.

- - -

When using the first of these two approaches, it is possible to point dynamically to the - correct staff definition for a given source. The following example demonstrates how this can - be accomplished for two sources, both presenting a two-staff score, but with differing staff - order. No further app element is necessary within the measure to describe the alternative score order of the sources.

- - - - - - - - - - - - - - - - - - - - - -
- - - - -
- - - -

when unique values for n on layerDef and layer are provided, it is possible to reallocate layers in the same fashion as - staves.

- - - -

This mechanism may also be used to describe not only differing page orientations, formats and - margins, but also clefs and keys.

- - - -
-
- Nesting Apparati -

In some situations, musical sources will agree at one level while differing at a lower level. - For these cases, app elements may be nested to any level necessary. In - the following example, there are three sources, two of which agree on the addition of a - measure, but differ in the content of the added measure:

- -
- - - - - - - - - - - - - - - - - - - - - - - -
- - -

When nesting app elements, it is important that the value(s) in the - child rdg element's source attribute must be a strict subset - of the ancestor rdg element's source value.

- - -
- -
-
- Editorial Markup -

It is often necessary to render an account of any changes made to a musical text during its - creation (and any subsequent editing) and to accommodate editorial comment necessitated by an - editorial process. The elements and attributes described in this chapter may be used to record - such editorial interventions, whether made by the composer, the copyists of the manuscript, the - editor of a earlier edition used as a copy text, or the current encoder/editor.

-

The scope of the elements described herein is therefore the description of features relating to - the genesis, later revision and editorial interpretation of a text. Mechanisms for describing - multiple sources are described in chapter of these Guidelines.

-

The elements described in this chapter may be contained by a wide range of other MEI elements - and, in turn, may contain a variety of elements. The encoder must assume responsibility for the - appropriateness of the markup; that is, a great many combinations of editorial and - transcriptional markup are technically possible, but care must be taken to see that the encoding - does not contravene the rationale of these Guidelines.

-

For most of the elements discussed here, some encoders may wish to indicate both a - responsibility; that is, a coded value indicating the person or agency responsible for making - the editorial intervention in question, and an indication of the degree of certainty which the - encoder wishes to associate with the intervention. Because these requirements are common to many - of the elements discussed in this section, they are provided by an attribute class, att.edit, to which these elements subscribe. Any of the elements - discussed here thus may potentially carry the following optional attributes:

-

- - - - -

- - -

Many of the elements discussed here can be used in two ways. Their primary purpose is to - indicate that their content represents an editorial intervention (or, in some cases, the lack of - intervention) of a specific kind. Sometimes, pairs or other meaningful groupings of such - elements can be recorded, then wrapped within the special purpose choice - element:

-

- - - -

-

Wrapping elements this way enables the encoder to represent, for example, a text in its - original, uncorrected form alongside the same text in one or more - edited forms. Making use of this style of representation, software may - dynamically switch between the Urtext view of the text and one or more - views of the text after the application of the encoded editorial - interventions.

-

Elements which can be combined in this way constitute the model.choicePart class. The default members of this class are sic, corr, reg, orig, - unclear, add, and del; their - functions and usage are described in greater detail below.

-

Three categories of editorial intervention are discussed by the remainder of this chapter:

- - indication or correction of apparent errors; - indication of regularization of variant, irregular, non-standard, or eccentric forms; - and - editorial additions, suppressions, and omissions. - - -
- Abbreviations -

MEI offers methods for marking abbreviations in prose, as in the following example:

- -

... the next passage shall be performed in pno: ...

- -

or abbreviations in the music itself, as in the following example:

- - - - - - - - - -

The type attribute may be used to classify the abbreviation according to a convenient - typology. Sample values include:

- - - the abbreviation provides the first letter(s) of the word or phrase, omitting the - remainder; - - the abbreviation omits some letter(s) in the middle; - - the abbreviation comprises a special symbol or mark; - - the abbreviation includes writing above the line; - - the abbreviation comprises the initial letters of the words of a phrase; - - the abbreviation is for a title of address (Dr, Ms, Mr, ...); - - the abbreviation is for the name of an organization; - - the abbreviation is for a geographic name. - - -

This tag is the mirror image of the expan tag (not to be confused with - the expansion element described in ). - Both abbr and expan allow the encoder to - transcribe an abbreviation and its expansion. In the case of abbr, the - original is transcribed as the content of the element and the expansion as an attribute value, - while expan reverses this. The choice between the two is up to the user. - For example:

- -
- -

... the next passage shall be performed in pno: ...

- -

... the next passage shall be performed in piano ...

-
- - -

The abbr tag is not required; if appropriate, the encoder may - transcribe abbreviations in the source text silently, without tagging them. If abbreviations - are not transcribed directly but expanded silently, then the MEI header should indicate this - is the case. The cert attribute signifies the degree of certainty ascribed to the - expansion of the abbreviation. The expan attribute gives an expansion of the - abbreviation. The resp attribute contains an ID reference to an element containing - the name of the editor or transcriber responsible for supplying the expansion of the - abbreviation.

-

When the content of the abbr or expan attributes requires additional - markup, an attribute cannot be used. In this case, the abbreviated and expanded forms must be - presented within elements. Furthermore, as alternatives to each other, the abbr and expan elements must be wrapped by the choice element, as described above. The previous example, where the 'o:' in 'pno:' is - written as superscript, would be encoded as:

- -

... the next passage shall be performed in - pno: - piano - -

- - -
- Colla Parte Instructions -

Many musical scores make use of various kinds of shorthand notation which omit some parts - of the score that have already been written elsewhere. Typical exampleS for this are symbols - that indicate repetition of the preceding measure or beat. In MEI, these symbols can be - encoded using the mRpt and beatRpt elements - respectively. Often, similar graphical symbols (often one or two slashes, "//") are used to - mean that the current staff should have the same or similar content as another staff.

-

colla parte directives have a less strictly-defined scope than the - Rpt elements (beatRpt, halfmRpt, mRpt, mRpt2, multiRpt). That is, rather than specifying the repetition of content of a particular - duration, like a measure or beat, colla parte instructions can refer to - material of any length. In order to encode such scribal shorthand, MEI offers the cpMark element, which allows filling of blank spaces in the score with - horizontally and/or vertically distant material.

-

- - - -

-

Like any other controlEvent, cpMark is placed in - the score using the staff and tstamp attributes. The end point of the - mark itself, when necessary, may be indicated using the tstamp2 attribute. The - source material, which is intended to be inserted in the space indicated by the copy mark, - can be identified by the attributes origin.tstamp, origin.tstamp2, - origin.staff and origin.layer. While origin.tstamp - provides the relative distance from the beginning of the "gap", origin.tstamp is - relative to the position identified by origin.tstamp. However, - origin.tstamp defaults to the same value as tstamp2 and should only - be provided when necessary. When neither origin.staff nor - origin.tstamp are not provided, they take the same values as the cpMark's - staff and tstamp attributes; that is, they indicate a strict - vertical or horizontal copy.

-
- Copy marks in the first and second violin of C.M.v.Weber's Freischütz, Autograph, Nr.3 - (Walzer), measures 223-231 - -
-

In the example above, there are no less than three different copy instructions, which need - to be encoded with four cpMark elements. First, Weber inserts - characters from "a" to "f" in red ink to identify filled measures. Then, he repeats the same - characters in empty measures, which indicates that the content from the - filled measures should be copied here. While one could try to encode this - with just one cpMark element, it is both clearer and easier to process - when using two elements.

-

The second and third shorthand indications are written in the second violin (lower staff). - Here, Weber writes "unis.[ono]", silently omitting the reference to the first violin. His - next shorthand ("in 8va") additionally instructs the copyist to double the written material - in another octave. This information can be captured using the dis and - dis.place attributes on cpMark.

- -a. b. c. d. e. f. g. -a. b. c. d. e. f. g. -unis: -in 8va - -
- A transcription of the example above with all shorthand resolved and colored - -
-

Text used as a copy mark, like the letters in the Weber example, may be encoded as content - of the cpMark element. In the case of non-text marks, the - altsym, extsym and facs attributes may be used to refer - to a graphical surrogate.

-

Depending on the purpose of the encoding, the omitted parts in the score may be filled with - space and mSpace elements of appropriate - duration or silently overwritten with the content that the cpMark - identifies. Also, these two options may be combined through the use a choice element whose abbr and expan - children explicitly encode a transcription of the original gap (in - abbr) and the result of the insertion of the indicated material (in expan).

-
-
- -
- Apparent Errors -

When the source material to be encoded is manifestly faulty, an encoder or transcriber may - elect simply to correct it without comment, although for scholarly purposes it will often be - more generally useful to record both the correction and the original state of the text. The - elements described here enable all three approaches, and allows the last to be done is such a - way as make it easy for software to present either the original or the correction.

-

- - - - -

-

The following examples show alternative treatment of the same material. The text to be - encoded contains a chord (c4, e4, g4, a4), where c4, e4, and a4 are quarter notes, but g4 is a - half note.

-

An encoder may choose to silently correct the engraver's error:

- - - - - - - - - -

or the correction may be made explicit:

- - - - - - - - - - - -

Alternatively, the encoder may simply record the typographic error without correcting it, - either without comment or with a sic element to indicate the error is - not a transcription error in the encoding:

- - - - - - - - - - - -

If the encoder elects to record the original source text and provide a correction for the - sake of transparency, both sic and corr may be - used, wrapped in a choice element. The order of the sic and corr elements is not significant:

- - - - - - - - - - - - - - - - -

An indication of the person or agency responsible for the emendation can be provided as - follows:

- - - - Johannes Kepper - - - - - - - - - - - - - - - - - -

Here the resp attribute has been used to indicate responsibility for the - correction. Its value (#editTrans.JK) is an example of the pointer - values discussed in section . In this case, the resp - attribute points to a name element within the metadata header, but any - element might be indicated in this way, if the correction has been taken from some other - source. The resp attribute is available for all elements which are members of the - att.responsibility class. The att.edit class makes available a cert attribute,which may be used to - indicate the degree of editorial confidence in a particular correction, as in the following - example:

- - - - - - - - - - - - - - - - -

Where, as here, the correction takes the form of amending information present in the text - being encoded, the encoder should use the corr element. Where the - correction is present in the text being encoded, and consists of some combination of visible - additions and deletions, the elements add or del - should be used. For additional information on the use of add and del, see section below. Where the - correction takes the form of an addition of material not present in the original because of - physical damage or illegibility, the supplied element may be used. Where - the correction is simply a matter of expanding abbreviated notation, the - expan element may be used.

-
- -
- Regularization and Normalization -

When the musical source makes extensive use of unusual symbol shapes or non-standard notation - features, it may be desirable for a number of reasons to regularize it; that is, - provide standard or regularized forms that are - equivalent to the non-standard forms.

-

As with other such changes to the source text, the changes may be made silently (in which - case the MEI header should still specify the types of silent changes made) or may be - explicitly marked using the following elements:

-

- - - - - -

-

Consider this traditional soprano clef appearing somewhere in the course of a musical piece: - -

-

An encoder may choose to preserve this original clef, but flag it as nonstandard from the - perspective of current practice by using the orig element with no - attributes specified, as follows:

- - - - - - -

Alternatively, the encoder may indicate that the clef has been modernized into a G-clef by - using the reg element with no attributes specified, as follows:

- - - - - - -

As another alternative, the encoder may encode both the old and modernized shapes, so that - applications may render both at the reader's will:

- - - - - - - - - - - -

As described above, the resp attribute may be used to specify the agent - responsible for the regularization.

-
- -
- Additions, Deletions, and Omissions -

The following elements are used to indicate when single notational symbols have been omitted - from, added to, or marked for deletion from, a musical text. Like the other editorial elements - described in this chapter, they allow for a wide range of editorial practices:

-

- - - - - - - -

-
- Omissions, Unclear Readings, Damage, and Supplied Readings -

Encoders may choose to omit parts of the source for reasons ranging from illegibility, - (making transcription difficult or impossible), to editorial policy, e.g., systematic - exclusion of poetry or prose from an encoding. The full details of the policy decisions - concerned should be documented in the MEI header (see section ). Each place in the text at which omission has taken - place should be marked with a gap element, optionally with further - information about the reason for the omission, its extent, and the person or agency - responsible for it, as in the following examples:

- - - - - - - -

Note that the extent of the gap may be marked precisely using attributes unit - and quantity, or more descriptively using the extent attribute.

-

Unlike TEI, MEI does not offer a desc element for further description of - the reason for a gap. Instead, an annot may refer to the gap via its - startid, endid, or plist attributes and provide - additional information.

-

The unclear element is used to mark passages in the original which - cannot be read with confidence, or about which the transcriber is uncertain for other - reasons, as for example when transcribing a illegible source. Its reason and - resp attributes are used, as with the gap element, to - indicate the cause of uncertainty and the person responsible for the conjectured - reading.

- - - - - - - - -

Where the difficulty in transcription arises from an identifiable cause, the - agent attribute signifies the causative agent. The cert attribute - signifies the degree of certainty ascribed to the transcription of the text contained within - the unclear element. Where the difficulty in transcription arises from - action (partial deletion, etc.) assignable to an identifiable hand, the hand - attribute may record the hand responsible for the action.

-

When the reason for a gap in the encoding is damage of the document carrier (the paper on - which the document is written, for example), the damage element should - be used instead of the gap element. In the case of damage resulting - from an identifiable cause, the agent attribute signifies the causative agent. - The degree attribute signifies the degree of damage according to a convenient - scale. A damage tag with this attribute should only be used where the - text may be read with some confidence; data supplied from other sources should be tagged as - supplied. The extent attribute indicates approximately - how much text is in the damaged area, in notes, measures, inches, or any appropriate unit, - where this cannot be deduced from the contents of the tag. For example, the damage may span - structural divisions in the text so that the tag must then be empty of content. In the case - of damage (deliberate defacement, etc.) assignable to an identifiable hand, the - hand attribute signifies the hand responsible for the damage.

-

Sometimes the editor provides information not present in the source material. These - conjectures or emendations are marked up in MEI using the supplied - element.

-

The following example demonstrates the use of the supplied element in - combination with gap within subst:

- - - - - - - - - - - - - - - - -

When the presumed loss of text arises from an identifiable cause, agent - signifies the causative agent. When the presumed loss of text arises from action (partial - deletion, etc.) assignable to an identifiable hand, the hand attribute signifies - the hand responsible for the action. The reason attribute indicates why the text - has to be supplied, e.g. 'overbinding', 'faded ink', 'lost folio', 'omitted in original', - etc. The source attribute contains the source of the supplied text. The editor(s) - responsible for supplied material may be recorded in the resp attribute. The - value of resp must point to one or more identifiers declared in the document - header. The cert attribute signifies the degree of certainty ascribed to the - supplied material.

- -
-
- Additions and Deletions -

The add and del elements may be used to record - where material has been added or deleted in the source material.

-

The following example demonstrates the usage of add to mark up a note - being added to an existing chord:

- - - - - - - - - - - -

The next example shows how del may be used to capture the information - that two measures have been cancelled. As seen in this example, the rend - attribute is used to specify the method of deletion.

- -
- - - - - - - -
- - -

Additional information for both elements may be specified using attributes. Whereas the - hand attribute marks responsibility for the textual change, the resp - attribute is used to refer to the editor who identified this textual change as such. The - cert attribute signifies the degree of certainty ascribed to the identification - of the hand of the deletion or addition.

-

The add element should not be used to mark editorial changes, such as - supplying a note omitted by mistake from the source text or a passage present in another - source. In these cases, either the corr or supplied tags should be used instead.

-
-
- Substitutions, Restorations, and Handshifts -

When several interventions to the musical text are to be regarded as a single action, they - may be grouped using the subst element. The most common combination is - a replacement of portions of the musical text using both the add and - del element, as seen in the following example:

- - - - - - - - - - - - - - - - - - -

An intervention closely related to substitution is the restoration of a previously deleted - section. For this purpose MEI offers the restore element, which may - contain a del or other content directly.

-

The following example illustrates an instance where a lyric which was cancelled and later - restored by overwriting it:

- - - - - God - - - - - -

The desc attribute gives a prose description of the means of restoration. The - cert attribute signifies the degree of certainty ascribed to the identification - of the hand of the restoration. The type attribute may be used to indicate the - action cancelled by the restoration. The resp attribute contains an ID reference - to an element containing the name of the editor or transcriber responsible for identifying - the hand of the restoration. The hand attribute signifies the hand of the agent - which made the restoration.

- - - - -

MEI offers a handShift milestone element that can be used to mark a - change of scribe or scribal style.

-

The character attribute describes characteristics of the hand, particularly - those related to the quality of the writing, e.g., 'shaky', 'thick', regular'. A description - of the tint or type of ink, e.g., 'brown' or the writing medium, e.g., 'pencil', may be - placed in the medium attribute.

- - - - - - - - - - -

The new hand may be identified using the new attribute, while the previous hand - may be recorded in the old attribute. The resp attribute contains an - ID reference to an element containing the name of the editor or transcriber responsible for - identifying the change of hand. The cert attribute signifies the degree of - certainty ascribed to the identification of the new hand.

- - -

When using this element within a layer, it is important to ensure that all layers and - staves are considered. Every handShift affects only the content of its - own layer and staff, even in the following measures. Therefore, there must be a separate handShift for every staff and layer. This mechanism allows the description of shifts at timestamps that differ - between each staff. - -

-
- -
-
-
- Facsimiles -

Most often, MEI is used for the preparation of a digital musical text based on an existing - music document, or with the intention of rendering the encoded notation into a document or audio - rendition. MEI can, however, be used to provide a different kind of digital reproduction of a - source document, which relies on the description and provision of digital imagery. Both - approaches may be combined, so that the encoding of the musical content and digital facsimiles - may add different facets to the same MEI document.

-
- Elements of the Facsimile Module -

This module makes available the following elements for encoding facsimiles:

-

- - - - - -

-

These element are used to add a separate subtree to MEI, starting with the facsimile element inside music, as seen in the following - example:

- - - - - - - - - - - - - - - - -

It is possible to have more than one facsimile element in this - location. This is especially useful when multiple sources are encoded in the same file using - the mechanisms described in chapter of these Guidelines. In this - case, the decls (declarations) attribute of facsimile may be - used to refer to a source defined in the document's header, as seen in the following - example:

- - - - - - - - - - - - - - - - - - - -

Within a facsimile element, each page of the source is represented by a - surface element. Each surface may be assigned an identifying string - utilizing the label attribute. In addition, it may encapsulate more detailed - metadata about itself in a figDesc element. The coordinate space of the - surface may be recorded in abstract terms in the ulx, uly, - lrx, and lry attributes. For navigation purposes, surface has a startid attribute that accommodates pointing to the first - object appearing on this particular writing surface.

- - - - - - -

Within surface elements, one may nest one or more graphic elements, each providing a reference to an image file that represents the - writing surface. Multiple graphic elements are permitted in order to - accommodate alternative versions (different resolutions or formats, for instance) of the - surface image. In spite of changes in resolution or format, all images must contain the same - content, i.e., the entire writing surface. A graphic may refer to a - single page within a multi-page document, which is – at least for Adobe PDF documents - – available through a #page=X suffix to the target attribute.

- - - - - - - - - - - - - - - - - - -

The preceding markup will provide the basis for most page-turning applications. Often, - however, it is desirable to focus attention on particular areas of the graphical - representation of the surface. The zone element fulfills this - purpose:

- - - - - - - - - - - - - -

The coordinates of each zone define a space relative to the coordinate space of its - parent surface. Note that this is not necessarily the same coordinate space defined - by the width and height attributes of the graphic that represents the surface. The zone - coordinates in the preceding example do not represent regions within the graphic, but rather - regions of the writing surface.

- -

Because the coordinate space of a zone is defined relative to that of a surface, it is - possible to provide multiple graphic elements and multiple zone elements within a - single surface. In the following example, two different images representing the entire surface - are provided alongside specification of two zones of interest within the surface:

- - - - - - - - - -

A zone element may contain figDesc or graphic elements that provide detailed descriptive information about the - zone and additional images, e.g., at a different/higher resolution, of the rectangle defined - by the zone. The data objects contained within the zone may also be specified through the use - of the data attribute, which contains ID references to one more elements in the - content tree of the MEI file, such as a note, measure, etc.

- - - - - - - - - -

Conversely, an element in the content may refer to the facsimile - subtree using its facs attribute, which is made available by the att.facsimile attribute class. The last example could therefore be - encoded with pointers in the other direction:

- - - - - - - - - -

The pb element defined in the shared module - makes special use of the facs attribute, in that it does not point to a zone, but a surface element instead. A pb marks the beginning of a page, so it can be concluded that all elements - in the content tree which are encoded between any two pb elements encode - musical symbols written on the page (surface) referenced by the first of - these two pb element's facs attribute.

- -
-
-
- Figures and Tables -

Apart from music and text, musical documents, both historical and contemporary, may also - contain material in graphical or tabular format. In such materials, details of layout and - presentation may also be of comparatively greater significance or complexity than they are for - running text. Although some types of graphical material can be represented directly with markup, - it is more common practice to include such information by using a reference to an external - entity (typically a URL) encoded in a suitable graphical format.

-

The module defined by this chapter defines special purpose container - elements that can be used to encapsulate occurrences of such data within an MEI-conformant - document in a portable way. Specific recommendations for the encoding of figures, figure - descriptions and graphics as well as tables with their sub-elements tr, - td and th are provided at the beginnig of this - chapter. As there exists a wide variety of different graphic formats, a short list of formats - that are widely used at the present time, is given in section . - Each one includes a very brief description. The chapter closes with attribute and model classes - which are defined by the module.

-

The module described in this chapter makes available the following components:

- -
- Figures -

The fig element groups elements representing or containing graphic - information such as an illustration or figure. This element is modelled on the figure element - in the Text Encoding Initiative (TEI). The fig element is used to - contain images, captions, and textual descriptions of the pictures. The images themselves are - specified using the graphic element, whose target attribute - provides the location of an image. For example:

- - - - - -

The graphic element may occur multiple times within the markup of the figure in order to - indicate the availablity of different image formats or resolutions:

- - - - - - - -
- Figure Captions and Descriptions -

The element caption may be used to transcribe (or supply) a title or - descriptive heading for the graphic itself, as in the following example:

- - - Grace notes - - - -

The figure description (figDesc) element usually contains a brief - prose description of the appearance or content of a graphic figure, for use when documenting - an image, perhaps without displaying it. This element is intended for use as an alternative - to the content of its parent fig element; for example, for display - when the equipment in use cannot display graphic images. It may also be used for indexing or - documentary purposes, in which case best practice suggests the use of controlled vocabulary - terms.

- - - - Emblemi d'Amore - A pair of naked winged cupids, each holding a flaming torch, in a rural - setting. - - -

Occasionally, a figure description may have a complex structure. In this case, one or more - textual component elements (p [paragraph], table, list, quote, or lg [linegroup]) may be used to model the internal structure of the description:

- - - Grace notes - -

The example shows grace notes within beams ...

-

This illustration was created by ...

- - - - -
-
- Images -

The graphic element indicates the location of an inline graphic, - illustration, or figure. As noted above, there exists a wide variety of different graphics - formats, and the following list is in no way exhaustive. Moreover, inclusion of any format - in this list should not be taken as indicating endorsement by the MEI of this format or any - products associated with it. Some of the formats listed here are proprietary to a greater or - lesser extent and cannot therefore be regarded as standards in any meaningful sense. They - are, however, widely used by many different vendors. The following formats are widely used - at the present time, and are likely to remain supported by more than one vendor's - software:

- - BMP: Microsoft bitmap format - CGM: Computer Graphics Metafile - GIF: Graphics Interchange Format - JPEG: Joint Photographic Expert Group - PBM: Portable Bit Map - PCX: IBM PC raster format - PICT: Macintosh drawing format - PNG: Portable Network Graphics format - Photo-CD: Kodak Photo Compact Disk format - QuickTime: Apple real-time image system - SMIL: Synchronized Multimedia Integration Language format - SVG: Scalable Vector Graphics format - TIFF: Tagged Image File Format - -

Brief descriptions of all the above are given below. Where possible, current addresses or - other contact information are shown for the originator of each format. Many formal - standards, especially those promulgated by the ISO and many related national organizations - (ANSI, DIN, BSI, and many more), are available from those national organizations. Addresses - may be found in any standard organizational directory for the country in question.

- -
- Vector Graphic Formats - - - - This vector graphics format is specified by an ISO standard, ISO 8632:1987, - amended in 1990. It defines binary, character, and plain-text encodings; the non-binary - forms are safer for blind interchange, especially over networks. Documentation is - available from ISO and from its member national bodies, such as AFNOR, ANSI, BSI, DIN, - JIS, etc. - - - SVG is a language for describing two-dimensional vector and mixed vector or - raster graphics in XML. It is defined by the Scalable Vector Graphics (SVG) 1.0 - Specification, W3C Recommendation, 04 September 2001, available at http://www.w3.org/TR/2001/REC-SVG-20010904/. - - - This format is universally supported on Macintosh (tm) systems, and readable by a - limited range of software for other systems. Documentation is available from Apple - Computer, Cupertino, California USA. - -
-
- Raster Graphic Formats - - - - PNG is a non-proprietary raster format currently widely available. It provides an - extensible file format for the losslessly compressed storage of raster images. - Indexed-color, grayscale, and true-color images are supported, plus an optional alpha - channel. Sample depths range from 1 to 16 bits. It is defined by IETF RFC 2083, March - 1997. - - - Currently the most widely supported raster image format, especially for black and - white images, TIFF is also one of the few formats commonly supported on more than one - operating system. The drawback to TIFF is that it actually is a wrapper for several - formats, and some TIFF-supporting software does not support all variants. TIFF files may - use LZW, CCITT Group 4, or PackBits compression methods, or may use no compression at - all. Also, TIFF files may be monochrome, greyscale, or polychromatic. All such options - should be specified in prose at the end of the encodingDesc - section of the MEI header for any document including TIFF images. TIFF is owned by Aldus - Corporation. Documentation on TIFF is available from the owner at Craigcook Castle, - Craigcook Road, Edinburgh EH4 3UH, Scotland, or 411 First Avenue South, Seattle, - Washington 98104 USA. - - - Raster images are widely available in this form, which was created by CompuServe - Information Services, but has by now been implemented for many other systems as well. - Documentation is copyright by, and is available from, CompuServe Incorporated, Graphics - Technology Department, 5000 Arlington Center Boulevard, Columbus, Ohio 43220 USA. - - - PBM files are easy to process, eschewing all compression in favor of transparency - of file format. PBM files can, of course, be compressed by generic file-compression - tools for storage and transfer. Public domain software exists which will convert many - other formats to and from PBM. Documentation of PBM is copyright by Jeff Poskanzer, and - is available widely on the Internet. - - - This format is used by most IBM PC paint programs, and supports both monochrome - and polychromatic images. Documentation is available from ZSoft Corporation, Technical - Support Department, ATTN: Technical Reference Manual, 450 Franklin Rd. Suite 100, - Marietta, GA 30067 USA. - - - This format is the standard raster format for computer using Microsoft Windows - (tm) or Presentation Manager (tm). Documentation is available from Microsoft - Corporation. - -
-
- Photographic and Motion Video Formats - - - - This format is sponsored by CCITT and by ISO. It is ISO/IEC Draft International - Standard 10918-1, and CCITT T.81. It handles monochrome and polychromatic images with a - variety of compression techniques. JPEG per se, like CCITT Group IV, must be - encapsulated before transmission; this can be done via TIFF, or via the JPEG File - Interchange Format (JFIF), as commonly done for Internet delivery. - - - - This format was introduced by Kodak for rasterizing photographs and storing them - on CD-ROMs (about one hundred 35mm file images fit on one disk), for display on - televisions or CD-I systems. Information on Photo-CD is available from Kodak Limited, - Research and Development, Headstone Drive, Harrow, Middlesex HA1 4TY, UK. - - -
-
-
-
- Tables -

The element table contains text displayed in tabular form, i.e., in - rows and columns. A table is the least graphic of the elements discussed - in this chapter. Almost any text structure can be presented as a series of rows and columns: - one might, for example, choose to show a glossary or other form of list in tabular form, - without necessarily regarding it as a table. When tabular presentation is regarded as of less - intrinsic importance, it is correspondingly simpler to encode descriptive or functional - information about the contents of the table, for example to identify one cell as containing a - name and another as containing a date, though the two methods may be combined.

-

The table element may appear both within other components (such as - paragraphs), or between them, provided that the module defined in this chapter has been - enabled. It is to a large extent arbitrary whether a table should be regarded as a series of - rows or as a series of columns. For compatibility with currently available systems, however, - these Guidelines require a row-by-row description of a table.

-

While rows and columns are always encoded in top-to-bottom, left-to-right order, formatting - properties such as those provided by CSS may be used to specify that they should be displayed - differently.

- -
- Rows -

The tr (table row) element is a formatting element that contains one - or more td or th elements (cells) in a table. A cell is the intersection of a row and a column. The precise - rendition of the table and its cells should be specified in a style steet.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Besetzungen der Triosonate und ihrer Nachfolger
TriosonateStandardbes.Triosonate fürOrgel (Bach)Sonate mit obl.Cembalo (Bach)KlaviertrioStreichquartettStreichtrio
1. Oberstimme1. ViolineOrgel r.H.Violine(Flöte, Gambe)Violine1. Violine1. Violine
2. Oberstimme2. ViolineOrgel l.H.Cembalo r.H.Klavier r.H.2. Violine
harmonische FüllungCembalo r.H.BratscheBratsche
Bass-StimmeCelloOrgel PedalCelloCelloCelloCello
- -
-
- Cells -

The td (table data) element designates a table cell that contains - data as opposed to a cell that contains column or row heading information. The - colspan and rowspan attributes provide tabular rendering - information. They indicate that a particular cell or row of a table spans more than one row - or column.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
unmittelbares Schlagenmittelbares Schlagen
GegenschlagAufschlagSchüttelnSchrapen
1. Stäbe1. Stäbe1. Rahmen1. Raspeln
2. Platten2. Röhren2. Gefäße2. Räder
3. Platten3. Reihen
4. Gefäße
- - -

The th (table header) element designates a table cell containing - column or row heading information as opposed to one containing data. The colspan - and rowspan attributes tabular display rendering information. They indicate that - a particular cell or row of a table spans more than one row or column.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Systematische Einteilung der Idiophone
unmittelbares Schlagenmittelbares Schlagen
GegenschlagAufschlagSchüttelnSchrapen
1. Stäbe1. Stäbe1. Rahmen1. Raspeln
2. Platten2. Röhren2. Gefäße2. Räder
3. Platten3. Reihen
4. Gefäße
- -
-
- - - -
-
- Harmony -

This chapter describes the encoding of indications of harmony ocurring within a music text, - e.g., chord names, tablature grids, figured bass, or signs for harmonic analysis, and the - methods by which these indications can be connected with their interpretations. For - encoder-supplied analysis of intervallic content, please see chapter .

- -
- Indications of Harmony -

On the most basic level, chords in the musical text can be encoded using the chord element:

-

- - - -

-

Additional information on the use of the chord element is available in - and .

-

With only this kind of markup, harmonic information is implicit in the notes themselves. The - elements and attributes of this module, however, provide for the encoding of explicit - indications of harmony, such as chord symbols, tablature grids, figured bass signs, and the - symbols of harmonic analysis like Roman numerals and their interpretation.

- -
- Interpreted Chord Data in scoreDef -

An harmonic label, such as "7", may occur many times throughout an MEI instance. Where the - goal is diplomatic transcription, simply recording the uninterpreted label is sufficient. - Recording the precise meaning of such a label requires storing an interpretation. But, - including the interpretation at every point of occurrence of the label would swell the size - of the file and complicate the markup for those users who are not interested in the - interpretation. Therefore, MEI separates the encoding of harmonic labels from the encoding - of the interpretation of those labels.

-

The following elements enable the creation and re-use of interpreted chord data:

-

- - - - - - - - - -

-

The chordTable element is a container for a set of chord definitions, - while the chordDef element defines a single chord. Chord definitions - may be created a priori or as the result of analysis of the pitch content - of the music at hand, for instance, by examination of the notes occurring on the downbeat of - each measure. In this way, the chord definitions serve as a record of the analysis.

-

Even though it is not required by the schema, an xml:id attribute on chordDef is necessary to permit the creation of associations between - harmonic indications in the musical text with the chord defined here. The xml:id - attribute provides a unique identifier for the chord definition that can be referenced by - the harm element's chordref attribute.

-

Individual pitches of a chord are encoded using chordMember. The - inth attribute provides the means for indicating the number of half steps of - the chord note above the bass note.

-

These simple resources allow for the detailed specification and interpretation of harmonic - indications found in the musical text. For example, the harmonic label A can be - equated with a fully spelled-out indication of functional harmony that can be substituted - for the harmonic label, say, in an aural rendition:

- - - - - - - - - - -A - - -

Alternatively, the non-bass chord tones may be indicated, not with pitch names, but with - their intervallic distance above the bass note. Therefore, the example above may also be - encoded:

- - - - - - - - - - -

The preceding encoding possibilities provide the detailed information necessary to create - playable chord annotations. For more generic uses, however, the encoding can be taken one - step further; that is, it can be reduced to its minimum intervallic content by eliminating - octave duplications and expressing all chord members, including the bass note, using - intervals above the bass. Of course, the inth attribute for the bass note itself - should be set to 0. For example:

- - - - - - - -
- -
- Chord Tablature Grids -

The pos attribute on chordDef, the fing and - fret attributes on chordMember, and the barre element child of chordDef are provided in order to - create displayable and performable chord tablature grids for guitar and other fretted string - instruments. The fret at which a finger should be placed is recorded in the fret - attribute, while fing indicates which finger, if any, should be used to play an - individual string. The values x and o are used to indicate muffled and open - strings, respectively.

-

The chordDef element may contain barre - sub-elements when a single finger is used to stop multiple strings. Here the fret - attribute gives the fret position at which the barre should be created, while the - startid and endid attributes are used to indicate the chordMember elements on which the barre starts and finishes.

- -
- -
- Indications of Harmony in the Music Text -

With regard to indications of harmony, MEI attempts to strike a balance between very - precise (interpreted) and very loose (uninterpreted) markup needs. Therefore, various kinds - of harmonic labels are accommodated by the harm element. While some - are more structured than others, in the final analyis they all function as - labels. Therefore, MEI provides only a single element for the capture of - harmonic indications of all kinds:

-

- - - -

-

The harm element can be used to capture chord labels that consist - entirely of text:

- - - Cmaj - ii6 - - -

or labels that are chord tablature grids:

-
- Chord grid without label - -
- - - -

or labels that mix these styles:

-
- Chord grid with label - -
- -A7 - - -

The harm element must define a point of attachment using one of the - following attributes: startid, tstamp, tstamp.ges or - tstamp.real. The most commonly-used of these are startid and - tstamp.

-

The dur attribute encodes the logical and visual duration of the harmony. Please - note that the dur attribute here is not a true duration, but rather a time stamp - for the end point of the harmony.

-

Precise placement of the harmonic label can be controlled through the use of attributes in - the att.harm.vis attribute class.

- -
- Figured Bass -

Figured bass is a specialized form of harmonic indication. In order to support the - capture of the semantics of figured bass, and not just its visual representation, MEI - provides the following elements:

-

- - - - -

- -

Figured bass, consisting as it does of text, can always be represented purely visually. - This is probably how an OMR program or other naive encoder might deal with the markup of - figured bass:

-
- Figured bass - -
- -6 - - -

However, this kind of approach fails to recognize that a figured bass is being used and - not some other system of harmonic indications. To capture this knowledge, the preceding - example can also be marked more explicitly with:

- - - - 6 - - - - -

In order to provide greater control over the individual components of the figured bass, - each component can be treated as a figure. The natural symbol is encoded using the Unicode - MUSIC NATURAL SIGN character.

-
- Figured bass with accidental - -
- - - - 7 - ♮ - - - - -

Encoding order of the component f elements is significant as is the - encoding order of the characters within each component. In the preceding example, the - entire figured bass sign is encoded from top to bottom, in other words, just as the figure - appears on the page. In the following examples, the encoding order of the characters in - f explicitly locates the accidentals:

-
- Figured bass with chromatically altered figure - -
- - - - 7♭ - - - - -
- Figured bass with chromatically altered figures - -
- - - - 6 - 4+ - ♮3 - - - - -

Characters with combining slashes can be handled using the Unicode characters COMBINING - REVERSE SOLIDUS OVERLAY (6⃥) and COMBINING LONG SOLIDUS OVERLAY (6̸). The - combining nature of these Unicode characters indicates very clearly that they "overstrike" - the preceding character. The usual convention for slashes; that is, 6\ and - 6/ for backslash and slash, respectively, may also be followed:

-
- Figured bass with chromatically altered figure - -
- - - - 6⃥ - - 6\ - - - - -

Each component of the figured bass sign may use the extender attribute to - indicate that horizontal lines are used to mark the extent of the figure's harmonic - influence. The altsym attribute can be used to point to a user-defined symbol - that better represents the figure component, for example, the combined "2" and "+" below. - Similar to the slash in the preceding example before, the small curve over the "5" in - example 6 can be represented by the Unicode COMBINING INVERTED BREVE.

-
- Figured bass with alternative sign - -
- - - - - ̑ - 5 - 2+ - - - - - 3 - - - - - -

Because the repertoire of signs is so large, figures which consist entirely of a mark - indicating repetition of the preceding figure, should be represented by the character - appearing in the document. For example, in some notational styles, the repetition sign is - a dash (-), while in others it is a solidus (/). Using characters like this - is also consistent with other existing figured bass encoding schemes.

-
- Figured bass repetition - -
- - - - - - - - - -

Often, the distinction between extending lines and repetition signs is unclear. Treating - what at first appear to be extenders as repetition signs, however, can sometimes help to - simplify the required markup and to make the intent of the signs explicit. For example, in - the following example the dashes on beat 4 and 4.5 are treated as repetition signs:

-
- Extenders and repetition - -
- - - - - ♭3 - 6 - 5 - - - - - - - ♯3 - - - - - 7 - - - - - - - -

Using extender attributes for this example may make it easier to render the - figured bass symbol, but it is less explicit with regard to the intended harmony. For - example, it is difficult to ascertain what harmony should be sounding on beat 4 and its - after-beat.

- - - - - ♭3 - 6 - 5 - - - - - ♯3 - - - - - 7 - - - - - -

The primary goal of fb is not the capture all the visual - idiosyncracies that can be found in printed and manuscript scores throughout the - centuries, but to provide a more-or-less standardized label. The markup below, or any - markup in fact, cannot capture the exact look of the figured bass signs. The - altsym attribute may be used to provide access to a user-defined symbol for - precise rendition. Similarly, the facs attribute may be employed to point to - the symbol as it occurs in the encoding source material.

-
- Figured bass with alternative sign - -
- - - - - - 8 - 6♮ - 4+ - 2 - - - - - 6\ - 4 - 3 - - - - - - - - - 6\ - - - - - - - - 5/ - - - - - - - - 5+ - - - -
-
-
-
-
- Vocal Text -

This chapter describes how to encode words and syllables in vocal notation. This text is - typically written under a staff to indicate the text to be vocally performed. As such, this text - should not be confused with other text on the score, for which see and -

-

These guidelines suggest two methods for encoding text in vocal notation: encoding syllables - under each note and encoding performed text after the notes (and other staff events) either within layer elements or within measure elements when - available (for example in a Common Music Notation context). Each method may be more convenient - depending on the source text and on the textual phenomena that the encoding intends to - record.

- -

Both methods eventually rely on the syl element, which is part of the - shared module and is therefore available in all MEI files. The following - sections will begin by introducing the general use of syl and then show in - detail the two different encoding methods.

- -
- Lyric Syllables -

By lyric syllable, these guidelines mean a word or portion of a word - that is to be performed vocally. Each syllable is encoded with the syl - element, with which it is also possible to specify the position of the syllable in a word, the - type of connectors between syllables, alignment adjustments, and the formatting for each - syllable. These are the key components:

-

- - - - -

- -

The attribute wordpos is used to specify the position of the marked-up lyric - syllable in a word. It allows the following values:

- - - - Indicates that the current syllable's position is initial; that is, at - the beginning of a word; - - - Indicates that the current syllable is in the middle of a word; - - - Indicates that the syllable's position is terminal; that is, at the end - of a word. - - - -

When a syllable is at the beginning or in the middle of a word (in which case it will have - the wordpos attribute set to i or m), it - is recommended to specify the type of connector written between the current and the following - syllable. This is expressed with the con attribute, which takes the following - values:

- - - - A space is used as a connector between syllables; - - - A dash is used as a connector between syllables; - - - An underscore sign (indicating prologation of the syllable) is used as a - connector between syllables; - - - A tilde is used to indicate elision with the following syllable. This is - typically rendered as a small curved line between the syllables. - - -

Occasionally, a word or a final syllable needs to be extended across multiple notes. In this - case an extender is provided. An extender is a continuous line drawn at - the text's baseline from the end of the syllable associated with the first note until the last - note to be sung with the syllable.

- -

The use of syl described in this section is common to CMN and other - notation systems, such as mensural notation. Other uses specific to certain types of notation - and repertoires are addressed in other chapters. See for example .

-
- -
- Vocally Performed Text Encoded Within Notes -

Each lyric syllable can be encoded directly within an associated note, either by using the - syl attribute on note or the verse - element.

-

Using the syl attribute on notes is the simplest way of encoding vocally performed - text and is recommended only for simple situations or for those encodings which do not focus - on vocally performed text.

-

The following example from Handel's Messiah (HWV 56) shows the use of - syl:

-
- Handel, Messiah HWV 56, Halleluja - Example of a simple encoding of sung text - -
- - - - - - - - - - - - - - - - -

When there are multiple lines of vocally performed text, or the encoder wishes to be more - specific about connectors, etc., the use of verse and syl is recommended.

- -

- - - - -

- -

The following example from Handel's Messiah (HWV 56) shows the use of verse:

- - - - - - - Hal - - - - - le - - - - - - lu - - - - - jah, - - - - - - - - - -

As it is common practice in written text, it is assumed that a space separates words. Many - vocal texts, however, introduce elisions and connect two syllables into one unit. For example, - the vocal text from Mozart's Don Giovanni sung by Don Giovanni in Finale II, - Ho fermo il core in petto introduces an elision between the word fermo and - il and between core and in. An elision can be indicated by placing both - syllables within the same note and setting the syl - element's con attribute value to 't':

- - - - re - in - - - - -

When there is more than one line of text, more than one verse element - can be used. The following example from a piano reduction of Wagner's Rheingold - has two lines of text, with an English translation on the second line. Note the use of the - xml:lang attribute to differentiate the two languages:

-
- Example from Wagner's Rheingold with translated text. - -
- - - - - - -
- - - - - - Rei - - - thinks - - - - - fes - - - it - - - - - zu - - - were - - - - - - - - - - - wal - - - wise - - - - - - ten, - - - now - - - - - - -
- - -

Optionally, it is possible to include an lb element within verse to explicitly encode line and line group endings. This is - specifically meant to facilitate karaoke applications.

- -

Finally, the rhythm attribute can be used to specify a rhythm for the syllable - that differs from that of the notes on the staff.

- - -
- -
- Vocally Performed Text Encoded Separately -

Vocally performed text may also be encoded separately from the notes with the lg element. These are the main components:

- -

- - -

- -

Since this element is separated from the encoding of the notes, it must be associated with a - staff that will provide rhythm information when required for automated processing. The - staff attribute gives the associated staff and if there is more than one layer on - that staff, the layer attribute may be used to indicate the layer from which the - rhythm should be taken. If there is any divergence between the rhythm of the vocally performed - text and the notes, the rhythm attribute on verse may be used - to specify the text's rhythm.

- -

The following example from Carl Maria von Weber's Der Freischütz illustrates - this encoding method:

-
- Weber, Der Freischütz - Example of separate vocally performed text encoding - -
- -
- - - - - - - - - - - - - - Sturm - und - - - - - - - - - - - - Nacht! - - - - - - - - - - -
- - -

In this encoding style, a syl element with its con attribute - set to 't' and the following syllable are presumed to be associated with a single note. In the - following example, the first two syllables occur on the first note and the third syllable - occurs on the second note.

- - - - - - - - - - - re - il - pet - - - - -
- -
-
- Musical Instrument Digital Interface (MIDI) -

This chapter describes the MIDI encoding functionality present in MEI. The purpose of this - module is to allow for integrating MIDI data into MEI-encoded notation, to both aid software in - translating MEI to MIDI, and to permit the capture of information in files that have been - translated from MIDI to MEI. The MIDI model in MEI is similar to that of Mup, and the user is - directed to the Mup User Guide for - further reading.

-

The MIDI module defines certain generally-accepted MIDI units that may be used outside of a - MIDI context. For example, the dur.ges attribute accepts MIDI ppq - (Pulses Per Quarter) as a valid measurement of duration. Similarly, the pnum - attribute allows MIDI note numbers for specifying a pitch value.

-
- PPQ in scoreDef and staffDef -

To define the MIDI resolution of a score, the ppq attribute may be used on the scoreDef element. This value can be used to interpret the values found in - the dur.ges attribute on elements in the att.duration.gestural class.

-

- - - - - - - - - - - - - -

-

The ppq attribute is also available on the staffDef element - in order to aid in the conversion to MEI from other representations that allow a different - time base for each staff. However, these independent values for ppq are only - interpretable in terms of a common time base. Therefore, the ppq attribute is - required on scoreDef when the values of ppq on the staff - definitions differ. In the following example, the values of the ppq attributes on - the staffDef elements are all factors of the value of ppq - attached to scoreDef.

-

- - - - - - - - - -

-
-
- Recording General MIDI Instrumentation -

The instrDef element can be used to record MIDI instrument names or - numbers using the midi.instrname and midi.instrnum attributes. The - midi.instrname attribute must contain an instrument name from the list provided - by the data.MIDINAMES data type. By default, data.MIDINAMES contains General MIDI Instrument - designations.

- - - - - - - - - - - - - - - - - - -

The midi.instrnum is provided for those cases when an instrument number is needed. - It must contain valid MIDI values; that is, 0-127. In these cases, a General MIDI Instrument - name is redundant.

- - - - - - - - - - - - - - - - - - -
-
- Recording MIDI Event Data -

MIDI messages are encapsulated in the midi element, which is typically - used in contexts like layer and measure. In - earlier versions of MEI, the noteOn and noteOff - elements were used to record MIDI note on/off events. The use of these elements is now - discouraged in favor of using the note element directly. MIDI duration - should be recorded using the dur.ges attribute, and MIDI pitch information should - be recorded using the pnum attribute. - -

-

MIDI control changes (cc) are encoded using the num and - val attributes. Control change numbers are specified in the General MIDI - documentation. In the example below, the cc elements encode increasing - controller event 7 (volume) values, or in musical terms, a crescendo. Other MIDI event - messages follow this same pattern, using the num and val attributes to - record the raw MIDI data.

- - - - - - - - - - - - - - - - - - - -

In the preceding example, each control change is associated with a time stamp. The - tstamp attribute is required in order to indicate when the MIDI event should take - place. It is often necessary to indicate a time stamp slightly earlier than the affected notes - to compensate for MIDI delay.

- -

For better legibility and error checking, the midi element may be used, - as in the following example, to group MIDI parameter changes. Even so, the tstamp - attribute is required on all parameters in order to associate them with their point of - actuation:

- - - - - - -
- -
- MIDI in Mensural and Neume Notation -

In mensural, neume, and other historical or non-Western repertoires, there is often no - measure-based time stamp with which to associate MIDI controller data. Therefore, in these - notations MIDI controller data is assumed to be associated with the event that immediately - follows in the same layer. Thus, a crescendo in mensural notation may be encoded like so:

- - - - - - - - - - - - - - - - - - - - - - -
- - - -
-
- Names and Dates -

This chapter describes the MEI module used for the encoding of names (names of persons or - corporations/organizations) or descriptive phrases for styles, periods or geographical - indications. In section it was noted that the elements - provided in the core module allow an encoder to specify that a given text segment is a proper - noun. The elements provided by the present module allow the encoder to supply a detailed - sub-structure for such proper nouns, and to distinguish explicitly between persons and - organizations, and between stylistic, periodical or geographical indications.

-

The chapter begins by discussing the elements provided for the encoding of names (name) and dates (date) in general and finishes by - addressing more specific elements for corporate names (corpName), - geographic names (geogName), period names (periodName), personal names (persName) and style names (styleName). In general it is recommended to use standardized forms of proper - nouns and to record the names and web-accessible locations of the controlled vocabularies used. - There are several commonly-referenced authority files, especially for geographical, - organizational and personal names, such as the Gemeinsame Normdatei (GND), the Library of - Congress Authorities, the Getty Thesaurus of Geographic Names (TGN), and the MARC code list for - relators. Recommendations on which standards could be used can be found in the descriptions of - the individual elements.

-
- Basic Elements for Names and Dates -

The basic elements for capturing names and dates are defined in the shared module:

-

- - - - -

-

The name element contains the name of an entity that is difficult to - tag more specifically as a corpName, geogName, persName, or title. In section it was noted that the name element - may be used in place of the more specific elements when it is not known what kind of name is - being described or when a high degree of precision is not necessary. For example, the name element might be used when it is not clear whether the name "Bach" - refers to a person or a geographic feature. When name parts are needed, use name sub-elements. The recommended values for the type attribute are:

- - - - a personal name - - - the name of a corporate entity - - - a geographic name - - - the name of a process or mechanical agent - -

The date sub-element is available within name in order to record any - dates associated with the name, for example, creation and dissolution in the case of a - corporate entity or place or birth and death dates in the case of an individual. The name of - the list from which a controlled value is taken, such as the Library of Congress Name - Authority File (LCNAF), may be recorded using the authority attribute.

-

Examples of the use of the name element:

- -

- Henry VIII, King of England - The Beatles - Orbach - OMR software -

- -

The element date contains a date in any format, including a date range. - A date range may be expressed as textual content or, when intervening punctuation is present, - as a combination of date sub-elements and text.

- -

- 5/3/05 - May 30, 2012 - March 1-21, 1812 - - March 1, 1812 - March 21, 1812 - -

- -

To be more specific about the date, the attributes in the att.datable class can be used:

- - - - contains the starting point of a date range in standard ISO form - - - contains the end point of a date range in standard ISO form - - - contains a lower boundary for an uncertain date - - - contains an upper boundary for an uncertain date - - - gives the value of a textual date in standard ISO form - - - indicates the system or calendar to which a date belongs, for example, Gregorian, - Julian, Roman, Mosaic, Revolutionary, Islamic, etc. - - - signifies the degree of certainty or precision associated with a feature (high, - medium, low, unknown) - -

In the following example, the ambiguous date text "5/3/05" is resolved using the - isodate attribute:

- -

- 5/3/05 - 5/3/05 -

- -
- -
- Specialized Name and Date Elements -

In addition to the generic name and date elements - provided by the shared module, the namesDates module provides for the markup of the - specialized cases described below.

- -
- Corporate Names -

- - - -

-

Corporate names are non-personal names which refer to structured bodies of one or more - persons that act as a single entity. Typical examples include associations, businesses, - projects or institutions (e.g.,. 'the Royal College of Music' or 'the BBC'), but also racial - or ethnic groupings or political factions where these are regarded as forming a single - agency. Organization names typically include some type of indicator or pattern or words that - help identify them as non-personal names.

-

The corpName element is frequently used within the header of an MEI document. It is typically found in the respStmt element:

- - - Library of Congress - - -

It may also be used wherever it is necessary to mark a corporate name, for example when a - corporation is responsible for a certain event in the history of a musical work:

- - - - -

First performance by The Boston Symphony Orchestra, - October 22, 1881.

- - - - - -

When it is necessary to provide structure for a name, the separate parts of the name may be - encoded in corpName sub-elements, for example:

- -Federal Research Division, Library of Congress - - -

Standard designations for corporate bodies can be taken from a controlled vocabulary, such - as the Gemeinsame Normdatei (GND). If a controlled value is used, the list from which it is - taken should be recorded. In this case, the following attributes are particularly - relevant:

- - - - to record the list from which a controlled value is taken, - - - to record the web-accessible location of the controlled vocabulary from which the - value is taken, - - - to record a value which serves as a primary key in an external database. - -
- -
- Geographic Names -

- - - -

-

Geographic names are proper noun designations for places (e.g.,. Baltimore, Maryland), - natural features (e.g.,. Black Forest) or political jurisdictions (e.g.,. Quartier Latin, - Paris).

-

The element can be used, e.g., to label geographical names in titles:

- -<geogName>Bohemia</geogName>: Folk Songs - - -Music in the <geogName>German Democratic Republic</geogName> - - -

Geographic name sub-parts may be encoded in geogName sub-elements. - For example:

- -

- Baltimore, Maryland - French Quarter, New Orleans, - Louisiana -

- -

Alternatively, geographic name sub-parts may be encoded using the following more specific - elements:

-

- - - - - - - - - - - -

-

In contrast to the way addrLine is used to mark the physical - arrangement of the parts of an address, these elements can be used to mark the semantic - components of an address. For example:

- -
- 21 Jump Street - My Town - My Prefecture - My Province - My Country - A123B456C -
- -

They may also be used to identify place name components within textual content:

- - - Holmes and Watson live at 221 Baker St. in - London, England. - - - - - Oh, the places I want to go -
  • London
    • -
  • France
    • -
  • Napa Valley
    • -     -     - -

    To enable localization of an organization, or to specify names of places with identical - names, the use of controlled vocabulary is recommend for names of administrative divisions, - such as cities, states, and countries. In this case, the following attributes are - particularly relevant:

    - - - - records the list from which a controlled value is taken, e.g., the Thesaurus of - Geographic Names (TGN), - - - records the web-accessible location of the controlled vocabulary from which the - value is taken, - - - records a value which serves as a primary key in an external database. - -

    The encoder may use these attributes in combination. In case of the German city of - Frankfurt, for example, a clarification whether Frankfurt am Main or Frankfurt an der Oder - is meant can be achieved by referring to the ID of the TGN entry:

    - - -Frankfurt - - - -Frankfurt - - -

    The names of places given within addresses can be marked with geogName elements, for example:

    - -

    - German Research - Foundation -

    - Kennedyallee 40 - 53175 Bonn - Germany -
    -

    -     -
    - -
    - Time Period Names -

    - - - -

    -

    The periodName element is for names which describe a particular - period of time, for example, those which characterize obvious similarities in style, such as - Baroque or 3rd Style Period:

    - -Baroque - - -

    The date sub-element is available within periodName in order to - record any dates associated with the name that should be captured in the text, for example, - start and end dates of the named period:

    - -Baroque (1600-1750) - -

    Recording start and end points of a certain period using the startdate and - enddate attributes may prove to be better for machine processing:

    - -Baroque - -

    If a controlled value is used, the list from which it is taken should be recorded. In this - case the following attributes are relevant:

    - - - - to record the list from which a controlled value is taken, - - - to record the web-accessible location of the controlled vocabulary from which the - value is taken, - - - to record a value which serves as a primary key in an external database. - - - -
    - -
    - Personal Names -

    - - - -

    -

    Personal names within an MEI document may simply be marked with the persName element containing a proper noun or proper noun phrase referring to an - individual. For example:

    - - - - - Im wunderschönen Monat Mai - - Robert Schumann - - - - - -

    Apart from the composer or originator of a musical work, there could be many other persons - involved in the genesis of a musical work, such as librettists, lyricists, arrangers, - editors, transcribers, printers, publishers, etc. In addition, sometimes a single individual - may have multiple functions with regard to a musical work, e.g. composer and librettist. The - role attribute on persName may be used to capture a - person's responsibility. For example:

    - -Wolfgang Amadeus Mozart - - -Heinrich Heine - -

    -

    The Marc code list for - relators offers a variety of controlled terms that may serve as values for this use - of role.

    - -

    Personal names often consist of several components, such as given names, surnames, - inherited or life-time titles of nobility, honorific or academic prefixes, military ranks, - and other traditional descriptive phrases. These components can be marked using persName sub-elements, the function of which may be indicated using the - type attribute with the following values:

    - - - - contains a forename, given or baptismal name. - - - a family (inherited) name, as opposed to a given, baptismal, or nick name. - - - contains a name component which indicates that the referent has a particular role - or position in society, such as an official title or rank. - - - contains an additional name component, such as a nickname, epithet, or alias, or - any other descriptive phrase used within a personal name. - - - contains a connecting phrase or link used within a name but not regarded as part of - it, such as van der or of. - - - contains a name component used to distinguish otherwise similar names on the basis - of the relative ages or generations of the persons named. - -

    However, the recommended practice is to employ the following sub-elements provided the - namesDates module:

    -

    - - - - - - - - -

    -

    For example,

    - - - Rob - The Bold - Stark - I - of - Winterfell - King in the North - - -

    In the case of individuals with more than one forename, it is often sufficient to place all - given names within a single foreName element:

    - - - Mozart, Johannes Chrysostomus Wolfgangus Theophilus - - -

    However, the advantage of marking names with specific name part elements instead of nested - persName elements, is that it becomes possible to use the type attribute to - distinguish between multiple instances of the same generic name component. The following - example indicates the function of each of the given names of Wolfgang Mozart:

    - - - Mozart, - Johannes - Chrysostomus - Wolfgangus - Theophilus - - - -

    The use of a controlled list, such as the Gemeinsame Normdatei (GND) or the Library of - Congress Name Authorities, is recommended for names, especially those occurring within the - metadata header. When a controlled value is used, information about the the value should be - recorded. The following attributes are provided for this purpose:

    - - authority: records the list from which a controlled value is taken, - authURI (authority URI): indicates the web-accessible location of the - controlled vocabulary from which the value is taken, - codedval (coded value): holds a value which serves as a primary key in an - external database. - -

    For maximal machine-processability, these three attributes may be used in combination. For - example:

    - -Wolfgang Amadeus Mozart - -
    - -
    - Style Names -

    - - - -

    -

    Music can be divided into different styles, genres, and forms. The term style - denotes a mode of expression, or more particularly, the manner in which a work of art is - executed:

    -

    "In the discussion of music, which is orientated towards relationships rather than - meanings, the term raises special difficulties; it may be used to denote music characterized - of an individual composer, of a period, of a geographical area or center, or of a society or - social function. For the aesthetician style concerns surface or appearance, though in music - appearance and essence are ultimately inseparable. For the historian a style is a - distinguishing and ordering concept, both consistent of and denoting generalities; he or she - groups examples of music according to similarities between them." (Source: "Style", Grove - Music Online, accessed: April 27, 2012)

    -

    The name of a musical style can be marked by the styleName element, - for example:

    - -bebop - -

    It may be, e.g., used for recording a style name within a title:

    - -La voix du <styleName>bebop</styleName> - -

    or to record a style of a certain epoch by using the styleName - sub-element:

    - -Modern Jazz - - -

    Musical forms and genres must be distinguished from musical style. Form and genre are - typically indicated using the classification element, described in - chapter .

    -
    -
    -
    -
    - Performances -

    This chapter describes the performance module, which can be used for - organizing audio and video files of performances of a musical work. The elements provided allow - the encoder to group different recordings of the same performance, identify temporal segments - within the recordings, and encode simple alignments with a music text.

    - -
    - Overview -

    The following elements are available to encode information about a recorded performance:

    - -

    - - - - - - - -

    - -

    The performance element begins a subtree of the music element and appears alongside with, or instead of, body - (described in and facsimile - (described in ). A performance element - represents one recorded performance event. As a performance may be recorded in multiple - formats or by different personnel or or using different equipment, the performance element may group one or more recordings of the event.

    - -

    The decls attribute can be used to point to performance medium metadata for the - performed work. See for more details.

    - -

    The recording element identifies a single recording event taking place - within an absolute temporal space. The class att.mediaBounds contains attributes that can be - used to define this space:

    - -

    - - - -

    - -

    The avFile element identifies an external file associated with a - recording act. In the simplest case, the recording element will contain one avFile element identifying a file that represents it. The target attribute - contains the URI of the digital media file. Use of the mimetype attribute is - recommended for the avFile element. Its value should be a valid MIME - media type defined by the Internet Engineering Task Force in RFC 2046. It is also recommended - that all avFile elements have a recording or clip parent which bears the begin, - end, and betype attributes.

    - - - - - - - - - -

    Sometimes, multiple digital files are created in order to provide greater flexibility in - redistribution and playback capabilities. In this case, multiple avFile elements may occur, - each with a different mimetype. Keep in mind, however, that each file still represents the - complete temporal extent of the recording act in spite of the change of file format:

    - - - - - - - - - -

    The clip element identifies a temporal segment of a recording act. In - the following example, the clip begins two minutes into the timeframe of the recording and - ends 20 seconds later:

    - - - - - - -

    Beyond these relatively simple uses, complex situations may occur that require equally - complex markup. For example, a single performance may be represented by multiple digital media - files. Because they have differing durations, the media files must be the result of separate - recording acts, even if these recording acts took place at the same time:

    - - - - - - - - - - - -

    A single performance may also be represented by multiple, sequential digital - files, as when a complete work is recorded in several so-called takes. In - this case, the files may be considered to be parts of a single recording act, the extent of - which is the combined extent of the individual clips. For example, a series of clip elements may be used to identify each movement of a piece and give - start and end times for the movements in relation to the overall temporal space of the - complete work:

    - - - - - - - - - - - - - -

    Similar markup is also applicable when a single file representing the entirety of a recording - act is broken into segments later, as is often done for practical storage and distribution - reasons. The file from which the clips are derived is indicated using an avFile element:

    - - - - - - - - - - - - - - -

    A clip may be used to define any region of interest, such as a cadenza - or a modulation, a song verse, etc. The following example shows the use of clip and its attributes to identify significant sections of a recording:

    - - - - - - - - - - - - - - - -

    The preceding example also demonstrates that media files are not required in order to define - the temporal space of a recording act or clip. This makes it possible to set the boundaries of - these features, then use the content of the performance element as a rudimentary "edit - decision list" to create the matching digital files.

    - -

    If an encoding of the notated text with which the media files are associated is included in - the MEI file, the startid attribute can be used to indicate the first element in - the sequence of events to which the recording corresponds:

    - - - - - - - - - - -
    - - - -
    -     -     - -     - -

    Clips can also be aligned with components of the musical text encoded in the body. The startid attribute can be used to specify the starting element in - the sequence of events to which the clip corresponds. The following example shows the use of - of clip elements to identify the exposition of the first movement from Beethoven's piano - sonata Op. 14, no. 2 and its concluding codetta.

    - - - - - - - - - - - - - - -
    - - - - - - - -
    -     -     - -     - -

    Please note that the begin and end times of clips may overlap. In the preceding example, the - extent of the codetta is contained within that of the exposition. Overlapping beginning and - ending points may also be used to provide additional performance context for a segment or - because there is uncertainty with regard to precise values for these points.

    - - - - - - - - - - - - - -

    A bibliographic description of a recording or metadata explaining how clip boundaries were - determined may be associated with the recording and clip elements via the decls - attribute:

    - - - - - - - - - - - - -

    Associations between a feature of the encoding, such as a note, dynamic mark, or annotation, - and a time point, may be created using when elements and when - attributes.

    -

    The when element identifies a particular point in time during the - playback of a media file, such as an audio recording.

    - - - -

    Time points may be identified in absolute terms as above; that is, in hours, minutes, and - seconds since the beginning of the recording, or in relative terms using the - interval, inttype, and since attributes. In the following - example, the time point of interest happens 48 frames after the occurrence of the point - labelled as "t1".

    - - - -

    Having identified a point of interest, another feature of the encoding may be associated with - this point using its when attribute:

    - - -

    I like this part!

    -     -     -

    One use of the association created between the annotation and the time point is to display - the text of the annotation as the recording or clip is played.

    -

    The when attributes allows only a single value, so only one-to-one relationships - can be created using this mechanism. However, one-to-many relationships are accommodated in - the opposite direction; that is, from a time point to other features of the markup. For - example,

    - - - -

    indicates that the entities identified in data all occur at the same instant.

    -
    - -
    -
    - Pointers and References -

    This chapter describes the use of elements for linking and referencing.

    -
    - Links -

    An element is a link when it has an attribute whose value is a reference - to the ID of one or more other elements. The links discussed in this chapter are the ptr and the ref elements. These elements indicate an - association between themselves (or one of their ancestors) and one or more other entities, - either inside the same document or elsewhere. An association between two elements in the same - document is said to be an internal link, while an association that - involves an entity outside the current document is called an external - link. However, either element can be used for either purpose.

    -

    The two elements share a set of common attributes that are inherited from the att.pointing class:

    - - - - allows the use of one or more previously-undeclared URIs to identify an external - electronic object. - - - in contrast with the role attribute, allows the target resource to be characterized - using any convenient classification scheme or typology. - - - defines whether a link occurs automatically or must be requested by the user. - - - defines how a remote resource is rendered. - - - contains a human-readable description of the entire link. - - - indicates a property of the entire link. The value of the role attribute must be a - URI. - - -

    The target attribute specifies the destination of a pointer or reference using a - method standardized by the W3C consortium, known as the XPointer mechanism. The XPointer - framework is described at http://www.w3.org/TR/xptr-framework/. This mechanism permits a range of complexity, - from the very simple (a reference to the value of the target element's xml:id - attribute) to the more complex usage of a full URI with embedded XPointers:

    - - - - - - - - - - - - - - - - - - -Spider-Man - - -

    The targettype attribute allows the target resource to be characterized using any - convenient classification scheme or typology. This is often useful when the target requires - special processing, e.g., for display purposes. The pointers in the examples below may be - formatted differently, e.g., the bibliographic citation may result in special typography while - the pointer to the audio file may be used to embed an audio player:

    - - - - - - - -

    The xlink:actuate and xlink:show attributes are used in conjunction to - determine the link's behavior. The attribute xlink:actuate defines whether the - resolution of a link occurs automatically or must be requested by the user.

    - -

    The following values are allowed for the xlink:actuate attribute:

    - - - - load the target resource immediately - - - load the target resource upon user request, e.g., after a mouse click - - - traversal behavior is unconstrained; application should look for other markup to - determine appropriate behavior - - - traversal behavior is unconstrained; no other markup is provided to determine - appropriate behavior - - -

    The value "none" may be used to indicate that the link is un-traversable; it may or may not - render the link invisible to the user. When the value of xlink:actuate is "other", - an application must base a determination of appropriate behavior on factors other than the - value of xlink:actuate.

    - -

    The show attribute defines how a remote resource is to be rendered. The following - values are permitted:

    -

    - - - - target of the link appears in a new window - - - target of the link replaces the current resource - - - the content of the target appears at the point of the link - - - traversal behavior is unconstrained; application should look for other markup to - determine appropriate behavior - - - traversal behavior is unconstrained; no other markup is provided to determine - appropriate behavior -

    - -

    When the value of xlink:show is "other", an application must base a determination - of appropriate behavior on factors other than the value of xlink:show. The value - "none" may be used to indicate a link that is not displayed or is not displayable.

    -

    The following example illustrates a pointer that results in the automatic creation of a new - window with the content of the target loaded in it:

    - - - - -

    The xlink:title and xlink:role attributes describe the meaning of - resources within the context of a link. The xlink:title attribute is used to label - or describe a link or resource in a human-readable fashion. The value here is highly dependent - on the kind of processing being done. It may be used, for example, to make link titles - available to applications used by visually impaired users, or to create a table of links, or - to present help text that appears when a user's mouse hovers over the link.

    - - - - -

    The attribute xlink:role serves a similar function to that of - xlink:title. Whereas the value of xlink:title may be any string, the - value of xlink:role must be an absolute URI reference as defined in IETF RFC 3986, - available at http://tools.ietf.org/html/rfc3986. The URI reference identifies a resource that - describes the intended property. When no value is supplied, no particular role value is to be - inferred.

    - - - - - - -

    In the preceding example, the value of the xlink:role attribute may be used to - re-write the value of xlink:title, depending on the target resource role.

    - -

    In addition to the attributes in the att.pointing class, the - mimetype attribute is also available on ptr and ref. The function of the mimetype attribute is similar to that - of targettype in that they both allow classification of the destination. Unlike - targettype, however, mimetype explicitly defines the destination type - using a standard taxonomy. Its value should be a valid MIME (Multimedia Internet Mail - Extension) type defined by the Internet Engineering Task Force in RFC 2046, available at http://www.ietf.org/rfc/rfc2046.txt. The - following are all valid mimetype values:

    - - - - - -

    The mimetype attribute is particularly useful for documenting the nature of the - destination when the value of target does not provide a filename extension or when - the destination is a non-standard file type:

    - - - - - -
    - Difference between Pointers and References -

    The ptr element is an empty linking element that uses only attributes - to provide for movement from one place to another. Unlike the ref - element, it cannot contain text or sub-elements to describe the referenced object. Its - primary function is simply to point to another location. The next example shows targets that - are page numbers; or more precisely, the targets are page break elements bearing these - identifiers:

    - - -
  • - - -
    • -
  • - - -
    • -     -     -

    As shown above, the ptr element can be used to point - to a digital image. However, when the intention is to display a - digital image as part of the rendering of an MEI file, the graphic - element provides a convenient and recommended alternative:

    - - - - -

    While ptr cannot contain other markup, the ref - element can include text and sub-elements that name or describe the destination:

    - - - - ... -
    - -
    - ... -     -     -     - -

    The target attribute is not required in order to mark the textual content as a - cross-reference, as demonstrated in the example below; however, without this attribute the - reference will not be resolvable.

    - -

    See Hankinson, Roland, Fujinaga (2011).

    -     -
    -
    - -
    -
    - Tablature Notation -

    This chapter describes the attribute classes that are part of the MEI.tablature module.

    -
    - - Overview of the Tablature Module -

    The tablature module is used to record basic tablature notation. It is designed primarily for - guitar and similar plucked-string instruments.

    -

    The lines attribute on the staffDef element is used to - define the number of lines, courses, or strings, present in the tablature. The - tab.strings attribute is then used to enumerate the pitches of the open strings. - It is important to note that this is given using the written pitch, not the sounding pitch. - For example, the Western 6-string guitar, in standard tuning, sounds an octave below written - pitch.

    -

    The tab.strings attribute gives the string tuning, ordered from highest to lowest - pitch.

    -

    For standard guitar tuning, the staffDef element might look like - this:

    - - - -

    Chromatic alteration of the open string's pitch may be indicated with the '-' or 'f' (flat), - or the '#' or 's' (sharp). Multiple sharps and flats are not permitted.

    -

    A guitar in E-flat tuning might look like this:

    - - - -

    Some instruments, like the 12-string guitar, have the four lowest strings tuned an octave - above but are still written on a 6-line tablature staff. In this case, you may enumerate the - open string pitches while maintaining 6 lines.

    - - - -

    The note element is used to capture the specific events in the - tablature. The tab.string attribute is used to capture which string the note is to - be played on. String order is the same as that given in the tab.strings attribute. - This attribute takes a positive integer in the range of 1-9.

    - - - -

    In the case of fretted instruments, the fret number may be captured using the - tab.fret attribute. An open string may be indicated using the value "0" - (zero).

    - - - - - - - -
    -
    -
    - Text in MEI -

    This chapter describes methods for encoding textual content with MEI. Textual information on - scores has several different uses, although some text is closer to music notation than other - kinds. For example, tempo marks, directives and lyrics are directly related to the functionality - of the notated music and are, therefore, described in other chapters (see for example and ). This chapter, on the other - hand, focuses on the text that accompanies the score, i.e., paratext (prefatory material, title - pages, back matter, appendices, etc.), titles, prose, poetry, etc.

    -

    Most of the elements described here take inspiration from encoding formats that deal primarily - with text, such as HTML and the Text Encoding Initiative (TEI). These elements are provided to - encode relatively basic textual information. For deeper encoding of text, these Guidelines - recommend consideration of other text-specific encoding formats with embedded MEI markup.

    - -
    - Organizing Text into Divisions -

    Text can be organized in different parts, for example in chapters or sections. The div element is used to encode such structural divisions.

    -

    - - - - -

    -

    For example, printed scores, before the actual notation, can have text that can be organized - in multiple sections (e.g. a preface, a critical report, performance instructions, etc. for - which see the following sections); each of these sections should be identified by a different - div element. Text might also occur in between music sections (see ), for example in a collection of romantic piano works, a few - pieces might be preceded or followed by poetry. Such text should be encoded with the div element, as demonstrated in the following example:

    - - - -
    - -
    -
    - - - L'aspectata vertù, che 'n voi fioriva - quando Amor cominciò darvi bataglia, - - -
    -     -     -     - -

    Textual divisions may have titles or other forms of introductory material, which are encoded - with the head element.

    - -

    - - - -

    - -

    The following example shows the encoding of a preface translated into three different - languages, each with a different heading:

    - - - -
    - Preface - -
    -
    - Vorwort - -
    -
    - Prefazione - -
    -     -     -

    Having said that div identifies any structural organization of text, it - is often helpful to distinguish the typology of division. The attributes type and - subtype can be used for this purpose. It is required that type be - present when subtype is used, though their values can be freely set by the - encoder.

    - -

    The following example shows the use of type to indicate three prefaces in English, - German and Italian are columns on the same page.

    - - -
    - Preface - -
    -
    - Vorwort - -
    -
    - Prefazione - -
    - -     -     -
    - -
    - Paragraphs -

    Paragraphs are fundamental to prose text and typically group one or more sentences that form - a logical passage. A paragraph is usually typographically distinct: The text begins on a new - line and the first letter of the content is often indented, enlarged, or both.

    -

    A paragraph is encoded with the p element:

    -

    - - - -

    -

    Prose text is used for several different purposes within a MEI document, therefore p can occur in many situations. For example, it may be used within - metadata elements (see ):

    - - -

    The encoding contains only the first 5 measures.

    -     -     -

    Alternatively, paragraphs may be part of the document contents (and therefore encoded within - music), either as paratextual - material or within the music notation. In these cases, a paragraph will likely be - contained by a div or other elements containing prose (e.g. annot, figDesc, etc.).

    -

    The following example shows a paragraph in a preface section:

    - - -
    - The PreludesSymphonic Poem No.3 by F. Liszt. -

    What else is our life but a series of preludes to that unknown Hymn, the first and - solemn note of which is intoned by Death?

    -
    -     -     -
    -
    - Lists -

    When a text contains lists, they can be encoded with the following elements:

    -

    - - - - - - -

    -

    The list element can identify any kind of list; the form - attribute can be used to specify whether the list is ordered, unordered etc. Each item in the - list is encoded with the li element. The n can be used to - record a label for a list item, as in the following example:

    - -

    The modulation follows the following steps: -

  • C major
    • -
  • A minor
    • -
  • D major seventh
    • -
  • G major
    • - -

    -     -

    Occasionally, lists have headers or titles, which can be encoded with head:

    - - - Ornaments in different languages -
  • Turn
    • -
  • Gruppetto
    • -
  • Gruppetto
    • -
  • Doppelschlag
    • -     -     -
    -
    - Quotation -

    It is common, in many types of texts, to find quotations. A quotation is typically attributed - to another text other than the one being encoded. Often, the quoted material is - typographically distinct from the surrounding text; i.e., surrounded by so-called - quote marks or rendered as a separate block of text. The quote element is used to mark this function:

    -

    - - - -

    -

    The following examples show the use of quote.

    - -

    Hugh MacDonald has argued that Liszt's Symphonic Poems were meant to display the - traditional logic of symphonic thought.

    -     - - -

    The majority of the works represented in this catalogue were purchased in Paris and London - between 1928 and 1934. After graduating from Harvard in 1924, Mackay-Smith spent several - years in Europe: -

    I bought my first early music from Harold Reeves in London in the summer of 1928 when I - was able to acquire virtually all the 18th century editions, particularly of trio music, - which he then had in stock, going back not only through his current but also through - earlier catalogues, picking out numbers which remained unsold. It is almost a shame - today to think of the prices at which such things were then available, one or two pounds - apiece.

    - -

    -     -
    -
    - Poetry -

    This lg (line group) element is used generically to encode any section - of text that is organized as a group of lines. Following the recommendations of the Text - Encoding Initiative, it is recommended to use it, along with the following elements, for - marking up poetry:

    -

    - - - - - -

    -

    Because lg groups verses, it can be used to encode additional stanzas - not integrated into the music notation. In addition, it is common for a poem to include a - title or a header, as is demonstrated by the following example:

    - - - - -
    - -
    -
    - - - Sonetto 104 - L'aspectata vertù, che 'n voi fioriva - quando Amor cominciò darvi bataglia, - produce or frutto, che quel fiore aguaglia, - et che mia speme fa venire a riva. - - -
    -     -     -     - -
    - -
    - Paratext -

    This section introduces paratextual material, such as title pages, prefaces, indexes and - other text that precedes or follows the actual score.

    - -
    - Front Matter -

    By front matter these Guidelines mean distinct sections of a text - (usually, but not necessarily, a printed one), prefixed to it by way of introduction or - identification as a part of its production. Features such as title pages or prefaces are - clear examples; a less definite case might be the prologue attached to a dramatic work. The - front matter of an encoded text should not be confused with the MEI header described in - chapter , which provides metadata for the entire file.

    -

    An encoder may choose simply to ignore the front matter in a text, if the original - presentation of the work is of no interest. No specific tags are provided for the various - kinds of subdivision which may appear within front matter: instead, generic div (“division”) elements may be used, which should not be confused with mdiv (“musical division”) elements. The following suggested values for - the type attribute may be used to distinguish various kinds of division - characteristic of front matter:

    - - - A foreword or preface addressed to the reader in which the author or publisher - explains the content, purpose, or origin of the text. - - A formal declaration of acknowledgement by the author in which persons and - institutions are thanked for their part in the creation of a text. - - A formal offering or dedication of a text to one or more persons or institutions by - the author. - - A summary of the content of a text as continuous prose. - - A table of contents, specifying the structure of a work and listing its constituents. - The list element should be used to mark its structure. - - A pictorial frontispiece, possibly including some text. - -

    The following extended example demonstrates how various parts of the front matter of a text - may be encoded. The front part begins with a title page, which is presented in section , below. This is followed by a dedication and a preface, each of - which is encoded as a distinct div:

    - - - -
    -

    -
    -
    - Preface -

    -

    - -
    -     -     -

    The front matter concludes with another div element, shown in the - next example, this time containing a table of contents, which contains a list element (as described in chapter ). Note the use of - the ptr element to provide page-references: the implication here is - that the target identifiers (song1, song2, etc.) will correspond with identifiers used for - the mdiv elements containing the individual songs. (For a description - of the ptr element, see chapter .)

    - -
    - Contents - -
  • On Wenlock Edge
    • -
  • From Far, From Eve and Morning
    • -
  • Is My Team Ploughing?
    • -
  • Oh, When I Was In Love With You
    • -
  • Bredon Hill
    • -
  • Clun
    • -     -
    -     -

    Alternatively, the pointers in the table of contents might link to the page breaks at which - a song begins, assuming that these have been included in the markup:

    - - -
  • On Wenlock Edge 1
    • -
  • From Far, From Eve and Morning 15
    • - -     - - - - - - - - - - -     -
    - -
    - Title Pages -

    Detailed analysis of the title page and other preliminaries of older printed books and - manuscripts is of major importance in descriptive bibliography and the cataloging of printed - books; such analysis, however, requires a more detailed approach than the general one - described here. The following elements are suggested as a means of encoding the major - features of most title pages for faithful rendition:

    -

    - - - - - - - - -

    -

    The following example shows the encoding of the title page of Vaughan Williams' On - Wenlock Edge. Note the use of the lb element to mark the - line breaks present in the original.

    - - -

    ON WENLOCK EDGE

    -

    A CYCLE OF SIX SONGS FOR TENOR VOICE ___ WITH ACCOMPANIMENT OF Pianoforte and - String Quartet (ad lib) THE WORDS BY A. E. HOUSMAN (FROM "A SHROPSHIRE - LAD")

    -

    - -

    -

    MUSIC BY R. VAUGHAN WILLIAMS

    - -
  • PRICE $3.75
    • -
  • (COMPLETE WITH SET OF STRING PARTS $5.00
    • -
  • STRING PARTS SEPARATELY $1.00
    • -     -

    Boosey & Hawkes, Inc.

    -

    New York, U.S.A.

    -

    London · Toronto · Sydney · Capetown

    -     -     -

    The physical rendition of title page information is often of considerable importance. One - approach to this requirement would be to use the rend element, - described in chapter to specify the rendition of each - of the components of the title page. Another would be to employ a CSS stylesheet. Finally, a - module customized for the description of typographic entities such as pages, lines, rules, - etc., bearing special-purpose attributes to describe line-height, leading, degree of - kerning, font, etc. could be employed.

    - - -
    - -
    - - - -
    - Back Matter -

    Conventions vary as to which elements are grouped as back matter and which as front. For - example, some books place the table of contents at the front, and others at the back. For this - reason, the content models of the front and back - elements are identical.

    -

    The following suggested values may be used for the type attribute on all division - elements, in order to distinguish various kinds of divisions characteristic of back - matter:

    - - - An ancillary self-contained section of a work, often providing additional but in some - sense extra-canonical text. - - A list of terms associated with definition texts (‘glosses’). - - A section in which textual notes are gathered together. - - A list of bibliographic citations. - - Any form of index to the work. - - A statement appearing at the end of a book describing the conditions of its physical - production. - -

    No additional elements are proposed for the encoding of back matter at present. Some - characteristic examples follow; first, an index (for the case in which a printed index is of - sufficient interest to merit transcription):

    - - -
    - Index - -
  • a2, a3, etc., 175-176
    • -
  • Abbreviations, 3 - -
  • Percussion, 205-213
    • -
  • Strings, 307
    • -     - -
  • Afterbeats, 77
    • - -
    -     -     -

    Note that if the page breaks in the original source have also been explicitly encoded, and - given identifiers, the references to them in the above index can more usefully be recorded as - links. For example, assuming that the encoding of page 77 of the original source starts like - this:

    - - - -

    then the last item above might be encoded more usefully in the following form:

    - -
  • Afterbeats, 77
    • -     -
    - -
    -
    - User-defined Symbols -

    This chapter describes the elements, model classes, and attribute classes that are part of the - MEI.usersymbols module.

    -
    - - Overview of the User Symbols Module -

    The module described in this chapter makes available the following components:

    -
    - Elements -

    - - - - - - - - -

    -
    -
    - Attribute Classes -

    No attribute classes are defined in this module.

    -
    -
    - Model Classes -

    The usersymbols module defines the following model classes:

    -

    - - - - -

    -
    -
    -
    - Uses of the Usersymbols Module -

    The elements provided by the usersymbols module may be used in two ways: - For defining lines, curves and text elements that cannot be represented by a more - specific element. - For defining reusable symbols and special graphical renditions. - For this purpose, it provides three elements as graphic primitives, line, curve and anchoredText. Anywhere - these elements are allowed, the symbol element can be used as well. The - symbol element facilitates the re-use of symbols that were defined by - symbolDef elements.

    -
    - Defining Reusable Symbols -

    The symbolDef element uses SVG markup or the aforementioned graphic - primitives to describe a symbol. A symbol definition may also use symbols defined by other - symbolDef elements by employing the symbol - element.

    -
    - Definition of a triangle percussion symbol using graphic primitives - - - - - - - -
    -
    - Rendition of the triangle defined above - -
    -
    - Symbol composed of the symbol defined above and additional graphics primitives - - - - - - -
    -
    - Rendition of the composite triangle symbol - -
    -
    -
    - Elements Without Semantic Implications -

    The graphics primitives and symbols can be used directly in the music to describe text and - lines on a purely graphical level, without implying a specific logical meaning. If possible, - however, more meaningful elements should be used. This means for example, "a tempo" or "da - capo" should in general not be put inside anchoredText. Instead, tempo and dir should be used. Likewise, slurs and - ties should be encoded using their respective elements, not using curve, and for glissandi, gliss should be used instead of line.

    -

    An example usage for line is the visualization of voice leading, - which is not covered by a specific MEI element.

    -
    - Voice leading visualization as found in an Edition Peters print of Album für - die Jugend by Schumann, No. 35 (Mignon), measure 6. (Unknown date, plate number - is 10478.) - -
    -
    - Encoding of the Schumann example - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    -
    -
    - Defining a Specific Graphical Rendition for a Semantic Element -

    Usersymbols can define the rendition of different elements in two ways. Some elements, for - example dir and tempo, can have user symbol - elements as content. In the following example, the content of dir is - used to provide pictograms of percussion instruments.

    -
    - Indicating percussion instruments using pictograms - -
    -
    - Encoding of above example - -
    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    -     -
    -

    A number of elements can point to an internally-defined symbol for rendering using the - altsym attribute.

    -
    - Different treble clef renditions as written by Charpentier (source: Journal of Seventeenth-Century Music, - Volume 12, No. 1 (2006), figure 3) - -
    -
    - Defining two staffs, each using its own treble clef shape - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    -

    Externally-defined symbols may be referenced using a glyphname or - glyphnum attribute. Both attributes refer to Standard Music Font Layout (SMuFL) - characters. Other character sets must be treated as internally-defined character sets.

    -
    - Use of glyphname and glyphnum attributes - - - -
    -
    -
    -
    - Positioning and Coordinates -
    - Axis Orientation -

    MEI uses the classic axis directions where the x-axis points from left to right and the - y-axis points from bottom up. (This is compatible with PostScript's axis orientation, while - SVG's y-axis points in the opposite direction.)

    -
    -
    - Units -

    There are two types of units used by MEI: Staff units (data.MEASUREMENT) and units of the - output coordinate system. Units of the output coordinate system can be translated to - physical real world distances by means of the vu.height and page.scale - of a scoreDef element. Real world units are multiplied by the value of - page.scale to get the corresponding value in output coordinate units.

    -

    If an element is scaled using the scale attribute, the actual size of the units - changes accordingly.

    -
    -
    - Positioning -

    An element may be positioned using either absolute or relative coordinates. If absolute - start point coordinates are specified using x/y coordinates (or their - relatives x2/y2 for endpoints) they take precedence over relative - positions specified by ho/vo/to (or - startho/startvo/startto). Analogously, - x2/y2 override - endhoendvo/endto.

    -

    If to/startto/endto attributes are used, the start or end - point is x-aligned with the indicated timestamp.

    -

    If relative start coordinates (ho/vo or - startho/startvo) are used, the origin of the coordinate system to be - used for the start point is the first one found by the following search schema:

    - - If startid is present, the origin of the referenced element; - If the element is inside running text (e.g. inside tempo), the - end of the preceding text or element; - Otherwise, the origin of the containing element. - -

    The start point is offset from this origin by the value of the start coordinates - (ho/vo or startho/startvo), using staff - units.

    -

    Analogously, the endpoint is determined using end coordinates - (endho/endvo). If endid is specified, it takes precedence - over startid.

    -

    Examples of origins are:

    - - staff and layer: The horizontal origin is - the starting point of the measure, the vertical one is the bottom staff line; - note: The horizontal origin is the left end of the notehead, the - vertical one the center of the notehead; - clef: The horizontal origin is the left end of the clef, the - vertical one the line specified by clef/line (or - clef.line); - For elements containing text: The left end of the baseline; - symbolDef: As symbol definitions aren't rendered directly, their - coordinate system and origin are considered virtual. When they are referenced by symbol or altsym, the origin of the context, i.e. the - referencing symbol, is used. - -

    If neither absolute nor relative coordinates are specified, determining visually suitable - start and end points for line and curve attributes is left to the - rendering application. A value of 0 is not always assumed for absent relative coordinates. A - typical example where a rendering application may not choose the origins of absent relative - start and end coordinates to be the start point as well is the line connecting two notes in - the above Schumann example.

    -
    -
    - Curve Shape -

    If neither a bezier nor bulge attribute is present, the renderer - determines a suitable shape. However, if curvedir is present, the curve must - respect the curvature direction specified there.

    -

    The attributes bezier and bulge define the shape of a curve in two - different ways. If both are present, a rendering application may choose either one. They - override curvedir.

    -

    bezier defines the inner control points of a cubic Bézier curve, i.e., a Bézier - curve with two inner control points. The coordinates are given by a space separated list, - first x and y offsets for the first control point, then x and y offsets for the second one. - The x and y offsets are given in staff units (or inside the context of symbolDef in abstract units). The offsets for the first inner control point are - relative to the start point, the ones for the second inner control point are relative to the - end point.

    - -

    The bulge attribute allows specification of the curve shape by a number of - interpolation points. The interpolation points are given by their distance from the line - connecting the start and end point. The distance values are stored as a space separated - list.

    -

    The interpolation points are calculated as follows: If bulge provides - n distance values, the connection line is divided into - n+1 subsegments of equal length. The interpolation points are found by - drawing a perpendicular line of the respective length at each subsegment joint. Positive - distance values are drawn to the left of the connection line (left when traveling from start - to end), negative ones to the right.

    -
    - Rendering a bulge attribute with value "-2 1" - -
    -

    The interpolation algorithm used by the rendering application is implementation - dependent.

    -
    -
    - -
    - Line Rendition -

    The form attribute of lines may take the following values:

    - - dashed - dotted - solid - wavy - -

    These attribute values are only qualitative. Actual dash length and dot and dash spacing are - implementation dependent.

    -

    The width attribute may take the following values:

    - - narrow - medium - wide - -

    These values are also qualitative, however, they are also relative. That is, 'narrow' is the - default value, 'medium' is twice as wide as 'narrow', and 'wide' is twice as wide as - 'medium'.

    -

    In addition to these textual values, the width attribute may contain a numeric value and an - optional unit value, "2mm" for example. If the unit value is not provided, staff interline - units are presumed.

    -

    The lstartsym and lendsym attributes name the symbol that may start - and/or end a line, while lstartsymsize and lendsymsize indicate the - relative size of the symbol using a numeric value in the range from 1 to 9.

    -
    -
    - Limitations -

    The usersymbols module does not currently support continuous composite lines or filled areas. - As mentioned above, the rendition of lines is highly implementation dependent. Coordinate - system transforms are restricted to scaling using scale.

    - -
    -
    -
    - Linking and Alignment -

    The linkAlign module makes it possible to align recorded media (audio, video) with elements in - the musical domain. This allows for synchronization between the encoded notation and one or many - media.

    -
    - - Overview of the Linkalign Module -

    The module described in this chapter makes available the following components:

    -
    - Elements -

    - - - -

    -
    - - - -
    -
    - Linking and Alignment Examples - -

    The when element specifies timestamped locations on the referenced - media file. These may be defined using either an absolute time stamp (specified in ISO 24-hour - time format, HH:MM:SS.ss), or using a combination of the interval, - inttype, and since attributes.

    - - - - - - - - - -

    Musical elements can reference specific time points using the when attribute. This - is available on most musical elements, e.g., note, rest, measure, etc.

    - - - - - - - - - - -
    - - - -
    -     -     -     -
    -
    +
    -
    - Data Dictionary Conventions -
    - Elements -

    The "Elements" section of the data dictionary contains descriptions of each of the MEI - elements, arranged alphabetically by their tag names. Each element entry is arranged as shown - in Figures 1 and 2.

    -

    -

    - -
    -

    - - - Short, mnemonic form of the element name that is used in the machine-readable XML - document. The tag name is the first word at the top of the entry. Tag names are always in - so-called "camel" case beginning with a lower case letter. - - The element definition sometimes begins with an expanded version of the tag name that - more fully describes the element's meaning. The full name of the element is usually a word - or phrase that identifies the element's purpose. The definition of the element is typically - drawn from standard reference works, glossaries, basic dictionaries, and data dictionaries, - such as Gardner Read's Music Notation: A Manual of Modern Practice, Elaine - Gould’s Behind Bars, Grove Music Online, Carl Parrish's - Notation of Medieval Music, the Text Encoding Initiative - Guidelines, the Encoded Archival Description Tag Library, - etc. - - Identifies the schema module in which the element is defined. In order to use the - element, this module must be activated. - - Identifies all attributes associated with the element. Each entry in the list of - attributes contains the attribute name, an indication of whether it is required or optional, - a brief description of its purpose and use, and the name of the attribute class in which it - can be found. In order to use the attribute, this class must be activated. - -

    -

    - -
    -

    - - - Lists the model classes in which the element participates. A model class provides a - mechanism for grouping elements that have a similar function and that may appear at the same - point in an encoding. In order to use the element, at least one class must be - activated. - - Identifies other elements in which this element may appear as content. This information - conveys the sense of where and how often an element is available throughout the schema. - Definitions of parent elements may provide additional information about an element's - usage. - - Elements may be empty (e.g., permit no content); or they may contain only text, only - other elements, or a mixture of text and elements. The word "text" indicates that character - content is allowed directly inside the element, but the text cannot include special - characters, such as left angle brackets, that might be interpreted by an XML parser as - action codes. The list of permitted elements, organized according to the name of the module - to which they belong, usually includes more elements than are generally needed because - similar elements share the same content model. This practice eases the task of authoring a - schema and aids machine processing of encoded documents, but it may provide a somewhat - misleading indication of the appropriateness of the usage of some content elements. - - Contains the formal declaration for the element, including its participation in - attribute and model classes and its content model. - - Remarks regarding the history and use of the element appear in this section. The text - here describes how the element is used, differentiates it from similar elements, points out - useful attributes, provides an illustrative example, or directs the reader to related - elements. For more complete best practices guidance, the user is encouraged to consult the - appropriate Guidelines chapters. - - Provides a description of additional rules that apply to the element, its attributes, - and its content that cannot be expressed by a schema. These rules provide a method for - ensuring proper use of the element, as well as its attributes and content, when it appears - in different contexts. It may be, for example, correct to use certain attributes or - attribute values in one situation, but improper in another. - -
    -
    - Model Classes -

    Each model class entry names and describes a group of elements that shares a similar function - and that may therefore occur at similar points within the document. Like an element, a model - class also belongs to a module, which must be activated for the model class to be allowed. The - data dictionary identifies members of the class and provides information regarding their - status; that is, whether they are inherited from another class. In addition, the locations - ("Available in") in which elements from the class may occur are named.

    -

    - -

    -
    -
    - Attribute Classes -

    Grouping attributes simplifies the construction of a schema because it eliminates multiple - declarations for attributes that occur frequently. After the name and description of the - class, an attribute class entry identifies the module to which the class belongs, attributes - in the class, the elements to which attributes from the class can be applied, and any - constraints on the attributes’ values

    -

    - -

    -
    -
    - Datatypes and Macros -

    Datatypes and macros provide reusable declarations. They are used to create MEI-specific - datatypes for attribute values and content declarations for elements, respectively.

    -

    Some datatypes are defined in terms of so-called "built-in" datatypes defined by the World - Wide Web Consortium (W3C), such as "anyURI", "decimal", positiveInteger", "time", etc. For - more information on these and other datatypes defined by the W3C, visit http://books.xmlschemata.org/relaxng/relax-CHP-19.html.

    -

    Figure 4 demonstrates an MEI-specific datatype that defines a range of possible values. The - entry also provides the name of the module in which the datatype is declared, information on - where the datatype is applicable; that is, within the attribute called "intm", and a link to - more information about the class in which the attribute participates.

    -

    - -
    -

    -

    Some datatypes define an enumerated list of values rather than a range. In some cases only - the values in the list are permitted, while in others the value list may be extended by simply - using a value not already on the list. Lists with a fixed set of values are called "closed", - while extensible ones are referred to as "open" lists.

    -
    -
    -
    - +
    + - + Data type definitions. - + Written accidental values. - - - + + + Sharp. - + Flat. - + Double sharp (written as 2 sharps). - + Double sharp (written using croix). - + Double flat. - + Triple sharp (written as a croix followed by a sharp). - + Triple sharp (written as a sharp followed by a croix). - + Triple sharp (written as 3 sharps). - + Triple flat. - + Natural. - + Natural + flat; used to cancel preceding double flat. - + Natural + sharp; used to cancel preceding double sharp. - - + + Sharp note raised by quarter tone (sharp modified by arrow). - + Sharp note lowered by quarter tone (sharp modified by arrow). - + Flat note raised by quarter tone (flat modified by arrow). - + Flat note lowered by quarter tone (flat modified by arrow). - + Natural note raised by quarter tone (natural modified by arrow). - + Natural note lowered by quarter tone (natural modified by arrow). - - + + 1/4-tone flat accidental. - + 3/4-tone flat accidental. - + 1/4-tone sharp accidental. - + 3/4-tone sharp accidental. -

    +

    - + Gestural/performed accidental values. - - - + + + Sharp. - + Flat. - + Double sharp. - + Double flat. - + Natural. - + Three quarter-tones sharp. - + Quarter-tone sharp. - + Quarter-tone flat. - + Three quarter-tones flat. - + The following list of articulations mostly corresponds to symbols from the Western Musical Symbols portion of the Unicode Standard. The dot and stroke values may be used in cases where interpretation is difficult or undesirable. - - - + + + Accent (Unicode 1D17B). - + Staccato (Unicode 1D17C). - + Tenuto (Unicode 1D17D). - + Staccatissimo (Unicode 1D17E). - + Marcato (Unicode 1D17F). - - Marcato + staccato (Unicode 1D180). DEPRECATED; Scheduled for removal after - 2018-05-31. Use individual "marc" and "stacc" values. - - + Spiccato. - + Main note followed by short slide to higher, indeterminate pitch (Unicode 1D185). - + Main note preceded by short slide from lower, indeterminate pitch (Unicode 1D186). - + Main note preceded by long slide from lower, often indeterminate pitch; also known as "squeeze". - + Main note preceded by "slide" from higher, indeterminate pitch. - + Main note followed by short "slide" to lower, indeterminate pitch. - + Main note followed by long "slide" to lower, indeterminate pitch. - + "lip slur" to lower pitch, then return to written pitch. - + Main note followed by quick upward rise, then descent in pitch (Unicode 1D187). - + (Unicode 1D188). - + Alternation between written pitch and next highest overtone (brass instruments) or note minor third higher (woodwinds). - + Down bow (Unicode 1D1AA). - + Up bow (Unicode 1D1AB). - + Harmonic (Unicode 1D1AC). - + Snap pizzicato (Unicode 1D1AD). - + Fingernail (Unicode 1D1B3). - - Tenuto + staccato (Unicode 1D182). DEPRECATED; Scheduled for removal after - 2018-05-31. Use individual "ten" and "stacc" values. - - + Stop harp string from sounding (Unicode 1D1B4). - + Stop all harp strings from sounding (Unicode 1D1B5). - + Full (as opposed to stopped) tone. - + "muffled" tone. - + Double tongue (Unicode 1D18A). - + Triple tongue (Unicode 1D18B). - + Use heel (organ pedal). - + Use toe (organ pedal). - + Percussive effect on guitar string(s). - + Left-hand pizzicato. - + Uninterpreted dot. - + Uninterpreted stroke. - + - + "" contains a deprecated value. - + "" contains a deprecated value. - + Dots attribute values (number of augmentation dots) (Read, 113-119, ex. 8-21). - - + + 4 - - Placement of bar lines. The value 'staff' describes the traditional placement of bar - lines. - - - + + Records where bar lines are drawn. The value 'staff' describes the traditional placement + of bar lines. + + + Between staves only. - + Between and across staves as necessary. - - Short line above staff or through top line. + + Short bar line through a subset of staff lines. - + Renderings of bar lines. Some values correspond to the Western Musical Symbols portion of the Unicode Standard. - - - + + + Dashed line (Unicode 1D104). - + Dotted line. - + (Unicode 1D101). - + Double dashed line. - + Double dotted line. - + (Unicode 1D102). - + Bar line not rendered. - + Repeat start (Unicode 1D106). - + Repeat start and end. - + Repeat end (Unicode 1D107). - + (Unicode 1D100). - + Beam attribute values: initial, medial, terminal. Nested beaming is permitted. - - + + [i|m|t][1-6] - + Location of a beam relative to the events it affects. - - - + + + The beam is above the material it affects. - + The beam is below the material it affects. - + The below is above and below the material it affects. - + A beat location, i.e., [0-9]+(\.?[0-9]*)? The value must fall between 0 and the numerator of the time signature + 1, where 0 represents the left bar line and the upper boundary represents the right bar line. For example, in 12/8 the value must be in the range from 0 to 13. - - + + 0 - + Visual and performance information for a repeated beat symbol. - - + + 1|2|3|4|5 @@ -13139,11 +415,11 @@ - + Either an integer value, a decimal value, or a token. Fractional values are limited to .25, .5, .75, while the token value is restricted to 'full'. - - + + \.25|\.5|\.75 @@ -13156,664 +432,758 @@ - + Boolean attribute values. - - - + + + True. - + False. - + Values for certainty attribute. Certainty may be expressed by one of the values 'high', 'medium', or 'low'. The value 'unknown' should be used in cases where the encoder does not wish to assert an opinion. - - - + + + High certainty. - + Medium certainty. - + Low certainty. - + An unknown level of certainty. - + Clef line attribute values. The value must be in the range between 1 and the number of lines on the staff. The numbering of lines starts with the lowest line of the staff. - - + + - + Clef shape attribute values (Read, p.53-56). Some values correspond to the Unicode Standard. - - - + + + G clef (Unicode 1D11E). - + Double G clef. - + F clef (Unicode 1D122). - + C clef (Unicode 1D121). - + Drum clef (Unicode 1D125 or Unicode 1D126). - + Tablature "clef"; i.e. usually "TAB" rendered vertically. - + Tone-cluster rendition. - - - + + + White keys. - + Black keys. - + Mixed black and white keys. - + Confidence is expressed as a real number between 0 and 1; 0 representing certainly false and 1 representing certainly true. - - + + 0 1 - + List of SVG-recognized color keyword names described at https://www.w3.org/TR/SVG/types.html#ColorKeywords. - - - + + + Hex: #f0f8ff / RGB: 240,248,255 - + Hex: #faebd7 / RGB: 250,235,215 - + Hex: #00ffff / RGB: 0,255,255 - + Hex: #7fffd4 / RGB: 127,255,212 - + Hex: #f0ffff / RGB: 240,255,255 - + Hex: #f5f5dc / RGB: 245,245,220 - + Hex: #ffe4c4 / RGB: 255,228,196 - + Hex: #000000 / RGB: 0,0,0 - + Hex: #ffebcd / RGB: 255,235,205 - + Hex: #0000ff / RGB: 0,0,255 - + Hex: #8a2be2 / RGB: 138,43,226 - + Hex: #a52a2a / RGB: 165,42,42 - + Hex: #deb887 / RGB: 222,184,135 - + Hex: #5f9ea0 / RGB: 95,158,160 - + Hex: #7fff00 / RGB: 127,255,0 - + Hex: #d2691e / RGB: 210,105,30 - + Hex: #ff7f50 / RGB: 255,127,80 - + Hex: #6495ed / RGB: 100,149,237 - + Hex: #fff8dc / RGB: 255,248,220 - + Hex: #dc143c / RGB: 220,20,60 - + Hex: #00ffff / RGB: 0,255,255 - + Hex: #00008b / RGB: 0,0,139 - + Hex: #008b8b / RGB: 0,139,139 - + Hex: #b8860b / RGB: 184,134,11 - + Hex: #a9a9a9 / RGB: 169,169,169 - + Hex: #006400 / RGB: 0,100,0 - + Hex: #a9a9a9 / RGB: 169,169,169 - + Hex: #bdb76b / RGB: 189,183,107 - + Hex: #8b008b / RGB: 139,0,139 - + Hex: #556b2f / RGB: 85,107,47 - + Hex: #ff8c00 / RGB: 255,140,0 - + Hex: #9932cc / RGB: 153,50,204 - + Hex: #8b0000 / RGB: 139,0,0 - + Hex: #e9967a / RGB: 233,150,122 - + Hex: #8fbc8f / RGB: 143,188,143 - + Hex: #483d8b / RGB: 72,61,139 - + Hex: #2f4f4f / RGB: 47,79,79 - + Hex: #2f4f4f / RGB: 47,79,79 - + Hex: #00ced1 / RGB: 0,206,209 - + Hex: #9400d3 / RGB: 148,0,211 - + Hex: #ff1493 / RGB: 255,20,147 - + Hex: #00bfff / RGB: 0,191,255 - + Hex: #696969 / RGB: 105,105,105 - + Hex: #696969 / RGB: 105,105,105 - + Hex: #1e90ff / RGB: 30,144,255 - + Hex: #b22222 / RGB: 178,34,34 - + Hex: #fffaf0 / RGB: 255,250,240 - + Hex: #228b22 / RGB: 34,139,34 - + Hex: #ff00ff / RGB: 255,0,255 - + Hex: #dcdcdc / RGB: 220,220,220 - + Hex: #f8f8ff / RGB: 248,248,255 - + Hex: #ffd700 / RGB: 255,215,0 - + Hex: #daa520 / RGB: 218,165,32 - + Hex: #808080 / RGB: 128,128,128 - + Hex: #008000 / RGB: 0,128,0 - + Hex: #adff2f / RGB: 173,255,47 - + Hex: #808080 / RGB: 128,128,128 - + Hex: #f0fff0 / RGB: 240,255,240 - + Hex: #ff69b4 / RGB: 255,105,180 - + Hex: #cd5c5c / RGB: 205,92,92 - + Hex: #4b0082 / RGB: 75,0,130 - + Hex: #fffff0 / RGB: 255,255,240 - + Hex: #f0e68c / RGB: 240,230,140 - + Hex: #e6e6fa / RGB: 230,230,250 - + Hex: #fff0f5 / RGB: 255,240,245 - + Hex: #7cfc00 / RGB: 124,252,0 - + Hex: #fffacd / RGB: 255,250,205 - + Hex: #add8e6 / RGB: 173,216,230 - + Hex: #f08080 / RGB: 240,128,128 - + Hex: #e0ffff / RGB: 224,255,255 - + Hex: #fafad2 / RGB: 250,250,210 - + Hex: #d3d3d3 / RGB: 211,211,211 - + Hex: #90ee90 / RGB: 144,238,144 - + Hex: #d3d3d3 / RGB: 211,211,211 - + Hex: #ffb6c1 / RGB: 255,182,193 - + Hex: #ffa07a / RGB: 255,160,122 - + Hex: #20b2aa / RGB: 32,178,170 - + Hex: #87cefa / RGB: 135,206,250 - + Hex: #778899 / RGB: 119,136,153 - + Hex: #778899 / RGB: 119,136,153 - + Hex: #b0c4de / RGB: 176,196,222 - + Hex: #ffffe0 / RGB: 255,255,224 - + Hex: #00ff00 / RGB: 0,255,0 - + Hex: #32cd32 / RGB: 50,205,50 - + Hex: #faf0e6 / RGB: 250,240,230 - + Hex: #ff00ff / RGB: 255,0,255 - + Hex: #800000 / RGB: 128,0,0 - + Hex: #66cdaa / RGB: 102,205,170 - + Hex: #0000cd / RGB: 0,0,205 - + Hex: #ba55d3 / RGB: 186,85,211 - + Hex: #9370db / RGB: 147,112,219 - + Hex: #3cb371 / RGB: 60,179,113 - + Hex: #7b68ee / RGB: 123,104,238 - + Hex: #00fa9a / RGB: 0,250,154 - + Hex: #48d1cc / RGB: 72,209,204 - + Hex: #c71585 / RGB: 199,21,133 - + Hex: #191970 / RGB: 25,25,112 - + Hex: #f5fffa / RGB: 245,255,250 - + Hex: #ffe4e1 / RGB: 255,228,225 - + Hex: #ffe4b5 / RGB: 255,228,181 - + Hex: #ffdead / RGB: 255,222,173 - + Hex: #000080 / RGB: 0,0,128 - + Hex: #fdf5e6 / RGB: 253,245,230 - + Hex: #808000 / RGB: 128,128,0 - + Hex: #6b8e23 / RGB: 107,142,35 - + Hex: #ffa500 / RGB: 255,165,0 - + Hex: #ff4500 / RGB: 255,69,0 - + Hex: #da70d6 / RGB: 218,112,214 - + Hex: #eee8aa / RGB: 238,232,170 - + Hex: #98fb98 / RGB: 152,251,152 - + Hex: #afeeee / RGB: 175,238,238 - + Hex: #db7093 / RGB: 219,112,147 - + Hex: #ffefd5 / RGB: 255,239,213 - + Hex: #ffdab9 / RGB: 255,218,185 - + Hex: #cd853f / RGB: 205,133,63 - + Hex: #ffc0cb / RGB: 255,192,203 - + Hex: #dda0dd / RGB: 221,160,221 - + Hex: #b0e0e6 / RGB: 176,224,230 - + Hex: #800080 / RGB: 128,0,128 - + Hex: #ff0000 / RGB: 255,0,0 - + Hex: #bc8f8f / RGB: 188,143,143 - + Hex: #4169e1 / RGB: 65,105,225 - + Hex: #8b4513 / RGB: 139,69,19 - + Hex: #fa8072 / RGB: 250,128,114 - + Hex: #f4a460 / RGB: 244,164,96 - + Hex: #2e8b57 / RGB: 46,139,87 - + Hex: #fff5ee / RGB: 255,245,238 - + Hex: #a0522d / RGB: 160,82,45 - + Hex: #c0c0c0 / RGB: 192,192,192 - + Hex: #87ceeb / RGB: 135,206,235 - + Hex: #6a5acd / RGB: 106,90,205 - + Hex: #708090 / RGB: 112,128,144 - + Hex: #708090 / RGB: 112,128,144 - + Hex: #fffafa / RGB: 255,250,250 - + Hex: #00ff7f / RGB: 0,255,127 - + Hex: #4682b4 / RGB: 70,130,180 - + Hex: #d2b48c / RGB: 210,180,140 - + Hex: #008080 / RGB: 0,128,128 - + Hex: #d8bfd8 / RGB: 216,191,216 - + Hex: #ff6347 / RGB: 255,99,71 - + Hex: #40e0d0 / RGB: 64,224,208 - + Hex: #ee82ee / RGB: 238,130,238 - + Hex: #f5deb3 / RGB: 245,222,179 - + Hex: #ffffff / RGB: 255,255,255 - + Hex: #f5f5f5 / RGB: 245,245,245 - + Hex: #ffff00 / RGB: 255,255,0 - + Hex: #9acd32 / RGB: 154,205,50 - + Parameterized color values - - - + + + #[0-9A-Fa-f]{6,6} - + #[0-9A-Fa-f]{8,8} - + rgb\((\s*(([01]?[0-9]?[0-9])|2[0-4][0-9]|25[0-5])\s*,\s*){2}([01]?[0-9]?[0-9]|2[0-4][0-9]|25[0-5])\s*\) - + rgba\(\s*(([01]?[0-9]?[0-9]|2[0-4][0-9]|25[0-5])\s*,\s*){3}(0(\.\d+)?|1(\.0+)?)\s*\)|rgba\(\s*(((\d{1,2})?%|100%)\s*,\s*){2}(\d{1,2}%|100%)\s*,\s*(0(\.\d+)?|1(\.0+)?)\s*\) - + hsl\(\s*((\d{1,2})|[12]\d{2}|3[0-5]\d|360)\s*,\s*(\d{1,2}%|100%)\s*,\s*(\d{1,2}%|100%)\s*\) - + hsla\(\s*(\d{1,2}|[12]\d{2}|3[0-5]\d|360)\s*,\s*(\d{1,2}%|100%)\s*,\s*(\d{1,2}%|100%)\s*,\s*(0(\.\d+)?|1(\.0+)?)\s*\) - + A value in one of the following forms is expected: 1) hexadecimal RRGGBB, 2) hexadecimal AARRGGBB, 3) CSS RGB, 4) CSS RGBA, 5) HSL, 6) HSLA, or 7) HTML 4.01 color name. - - - - + + + + + + + + + Description of direction with respect to an imaginary compass. + + + + - + + Basic compass directions. + + + + In a northern direction. + + + In an eastern direction. + + + In a southern direction. + + + In a western direction. + + + + + + Additional compass directions. + + + + In a north-eastern direction. + + + In a north-western direction. + + + In a south-eastern direction. + + + In a south-western direction. + + + + + 360th-unit measure of a circle's circumference; optionally signed decimal number between -360 and 360. - - + + 360.0 -360.0 - + Logical, that is, written, duration attribute values. - - + + - + Performed duration attribute values. - - - - - + + + + + - + Enclosures for editorial notes and accidentals. - - - + + + Parentheses: ( and ). - + Square brackets: [ and ]. - + + Location of musical material relative to a symbol on a staff instead of the staff. + + + + + + + + + Location of musical material relative to a symbol other than a staff. + + + + Above. + + + Below. + + + Left. + + + Right. + + + + + + Location of musical material relative to a symbol other than a staff. + + + + Above and left; north-west. + + + Above and right; north-east. + + + Below and left; south-west. + + + Below and right; south-east. + + + + + Describes how a graphical object, such as a note head, should be filled. The relative values — top, bottom, left, and right — indicate these locations *after* rotation is applied. - - - + + + Unfilled - + Filled - + Top half filled - + Bottom half filled - + Left half filled - + Right half filled - + In a guitar chord diagram, a label indicating which finger, if any, should be used to play an individual string. The index, middle, ring, and little fingers are represented by the values 1-4, while 't' is for the thumb. The values 'x' and 'o' indicate stopped and open strings, respectively. - - + + 1 4 @@ -13824,35 +1194,35 @@ - + Font family (for text) attribute values. - - + + - + Font name (for text) attribute values. - - + + - + Font size expressions. - - - - - - + + + + + + - + Font size expressed as numbers; i.e. points or virtual units. - - + + \d*(\.\d+)?(pt|vu) - + (pt|vu) @@ -13871,287 +1241,323 @@ - + Relative size of symbol that may begin/end a line. - - + + 1 9 - + Font size expressed as relative term. - - - + + + Smaller than x-small. - + Smaller than small, larger than xx-small. - + Smaller than normal, larger than x-small. - + Smaller than large, larger than small. - + Smaller than x-large, larger than normal. - + Smaller than xx-large, larger than large. - + Larger than x-large. - + One size smaller than the current size. - + One size larger than the current size. - + Font style (for text) attribute values. - - - + + + Text slants to right. - + Unadorned. - + Text slants to the left. - + Font weight (for text) attribute values. - - - + + + Bold or heavy. - + Not bold. - + In string tablature, the fret number. The value '0' (zero) indicates the open string. - - + + - + In a guitar chord diagram, the fret where the finger should be placed. Since guitar chord diagrams are limited to the range of frets that fall under the hand, the values here are a subset of those available in data.FRETNUMBER. The pos (position) attribute on the chordDef element must be used to indicate at which fret this range begins. - - + + 0 5 - + Analytical glissando attribute values. - - - + + + First note/chord in glissando. - + Note/chord that's neither first nor last in glissando. - + Last note in glissando. - + Do grace notes get time from the current (acc) or previous (unacc) one? - - - + + + Time "stolen" from following note. - + Time "stolen" from previous note. - + No interpretation regarding performed value of grace note. - + Note head shapes. - - - - - - + + + + + + - + Enumerated note head shapes. - - - + + + Filled, rotated oval (Unicode 1D158). - + Unfilled, rotated oval (Unicode 1D157). - + Unfilled, rotated oval (Unicode 1D15D). - + Unfilled backslash (~ reflection of Unicode 1D10D). - + Unfilled circle (Unicode 25CB). - + Plus sign (Unicode 1D144). - + Unfilled diamond (Unicode 1D1B9). - + Unfilled isosceles triangle (Unicode 1D148). - + Unfilled, unrotated oval (Unicode 2B2D). - + Unfilled downward-pointing wedge (Unicode 1D154). - + Unfilled rectangle (Unicode 25AD). - + Unfilled right triangle (Unicode 1D14A). - + Unfilled semi-circle (Unicode 1D152). - + Unfilled slash (~ Unicode 1D10D). - + Unfilled square (Unicode 1D146). - + X (Unicode 1D143). - + Hexadecimal number. - - + + (#x|U\+)[A-F0-9]+ - + Data values for attributes that capture horizontal alignment. - - - + + + Left aligned. - + Right aligned. - + Centered. - + Left and right aligned. - + An ID reference. - - + + - + Interrupted neume forms. - - - - - - - + + + + + + + - + Interrupted neume, i.e. neume written as 2 or more sub-neumes. - - - - - - - - - + + + + + + + + + - + A token indicating diatonic interval quality and size. - - + + [AdMmP][0-9]+ - - A token indicating direction of the interval but not its precise value, an indication of - diatonic interval quality and size, or a decimal value in half steps. Decimal values are - permitted to accommodate micro-tuning. - - - + + A token indicating direction of the interval but not its precise value, a diatonic + interval (with optional direction and quality), or a decimal value in half steps. Decimal + values are permitted to accommodate micro-tuning. + + + + u|d|s|n|sd|su + - u|d|s|n|sh|sl + (\+|\-)?([AdMmP])?[0-9]+ - (\+|\-)?[AdMmP][0-9]+ + (\+|\-)?\d+(\.\d+)?hs -

    u = up, d = down, s = same, n = neutral/unknown, sh = same or higher (but not lower), sl = - same or lower (but not higher)

    +

    + + Interval direction only: + u = up/higher, + d = down/lower, + s = same, + n = neutral/unknown, + sd = same or lower (but not higher), + su = same or higher (but not lower) + +

    +

    + + Interval direction, quality, and size: + optional sign, + + + optional quality indicator: + A = augmented, + d = diminished, + M = major, + m = minor, + P = perfect + + + integer value + +

    +

    + + Interval in half steps: + optional sign, + decimal value + "hs" + +

    - + ISO date formats. - - + + @@ -14166,177 +1572,177 @@ - + ISO 24-hour time format: HH:MM:SS.ss, i.e., [0-9][0-9]:[0-9][0-9]:[0-9][0-9](\.?[0-9]*)?. - - + + - + Indicates the location of the tonic in the circle of fifths. - - + + mixed|0|([1-9]|1[0-2])[f|s] - + Indicates how stems should be drawn when more than one layer is present and stem directions are not indicated on the notes/chords themselves. '1' indicates that there is only a single layer on a staff. '2o' means there are two layers with opposing stems. '2f' indicates two 'free' layers; that is, opposing stems will be drawn unless one of the layers has 'space'. In that case, stem direction in the remaining layer will be determined as if there were only one layer. '3o' and '3f' are analogous to '2o' and '2f' with three layers allowed. - - - + + + Single layer. - + Two layers with opposing stems. - + Two layers with 'floating' stems. - + Three layers with opposing stems. - + Three layers with 'floating' stems. - + Ligature forms. - - - + + + Notes are "squeezed" together. - + Individual notes are replaced by an oblique figure. - + Visual form of a line. - - - + + + Dashed line. - + Dotted line. - + Straight, uninterrupted line. - + Undulating line. - + Symbol that may begin/end a line. - - - + + + 90 degree turn down (similar to Unicode 231D at end of line, 231C at start). - + 90 degree turn up (similar to Unicode 231F at end of line, 231E at start). - + 90 degree turn right (syntactic sugar for "angledown" for vertical or angled lines). - + 90 degree turn left (syntactic sugar for "angleup" for vertical or angled lines). - + Filled, triangular arrowhead (similar to Unicode U+25C0 or SMuFL U+EB78). - + Open triangular arrowhead (similar to Unicode U+02C3 or SMuFL U+EB8A). - + Unfilled, triangular arrowhead (similar to Unicode U+25C1 or SMuFL U+EB82). - + Harpoon-shaped arrowhead left of line (similar to arrowhead of Unicode U+21BD). - + Harpoon-shaped arrowhead right of line (similar to arrowhead of Unicode U+21BC). - + Hauptstimme (Unicode U+1D1A6 or SMuFL U+E860). - + Nebenstimme (Unicode U+1D1A7 or SMuFL U+E861). - + Theme (SMuFL U+E864). - + Theme, retrograde (SMuFL U+E865). - + Theme, retrograde inversion (SMuFL U+E866). - + Theme, inverted (SMuFL U+E867). - + Theme (SMuFL U+E868). - + Theme, inverted (SMuFL U+E869). - + Choralemelodie (SMuFL U+E86A). - + Hauptrhythmus (SMuFL U+E86B). - + No start/end symbol. - + Datatype of line width measurements. - - - - - + + + + + - + Relative width of a line. - - - + + + Default line width. - + Twice as wide as narrow. - + Twice as wide as medium. - + A count of measures plus a beat location, i.e., [0-9]+m *\+ *[0-9]+(\.?[0-9]*)?. The measure count is the number of barlines crossed by the event, while the beat location is a timestamp expressed as a beat with an optional fractional part. For example, "1m+3.5" @@ -14346,13 +1752,13 @@ number must be within the range from 0 (the left barline) to 7 (the right barline). A value with a measure number of "0", such as "0m+2", indicates a point within the current measure. - - + + ([0-9]+m\s*\+\s*)?[0-9]+(\.?[0-9]*)? - + A count of measures plus a beat location, i.e., (\+|-)?[0-9]+m\+[0-9]+(\.?[0-9]*)?. The measure count is the number of barlines crossed by the event, while the beat location is a timestamp expressed as a beat with an optional fractional part. The measure number must be in @@ -14363,1077 +1769,1095 @@ in 6/8 the beat number must be within the range from 0 (the left barline) to 7 (the right barline). A value with a measure number of "0", such as "0m+2", indicates a point within the current measure. - - + + (\+|-)?[0-9]+m\+[0-9]+(\.[0-9]*)? - + Measurement expressed in real-world (e.g., centimeters, millimeters, inches, points, picas, or pixels) or virtual units (vu). 'vu' is the default value. Unlike data.MEASUREMENTREL, which may be used to express relative measures, only positive values are allowed. - - + + (\+)?\d+(\.\d+)?(cm|mm|in|pt|pc|px|vu)? - + Measurement expressed in real-world (e.g., centimeters, millimeters, inches, points, picas, or pixels) or virtual units (vu). 'vu' is the default value. Unlike data.MEASUREMENTABS, in which only positive values are allowed, both positive and negative values are permitted. - - + + (\+|-)?\d+(\.\d+)?(cm|mm|in|pt|pc|px|vu)? - + Indication of melodic function, i.e., anticipation, lower neighbor, escape tone, etc. - - - + + + Accented lower neighbor. - + Anticipation. - + Appogiatura. - + Accented passing tone. - + Arpeggio tone (chordal tone). - + Arpeggio tone (7th added to the chord). - + Accented upper neighbor. - + Changing tone. - + Chromatic lower neighbor. - + Chord tone (i.e., not an embellishment). - + Chord tone (7th added to the chord). - + Chromatic upper neighbor. - + Chromatic unaccented passing tone. - + Escape tone. - + Lower neighbor. - + Pedal tone. - + Repeated tone. - + Retardation. - + 2-3 retardation. - + 7-8 retardation. - + Suspension. - + 4-3 suspension. - + 9-8 suspension. - + 7-6 suspension. - + Upper neighbor. - + Upper neighbor (7th added to the chord). - + Unaccented passing tone. - + Unaccented passing tone (7th added to the chord). - + Mensuration attribute values. - - - + + + Tempus imperfectum. - + Tempus perfectum. - + Meter.sym attribute values for CMN. - - - + + + Common time; i.e. 4/4. - + Cut time; i.e. 2/2. - - MIDI channel numbers. - - - 16 + + MIDI channel number. One-based values must be followed by a lower-case letter "o". + + + 0|([1-9]|1[0-5])o?|16o - + Tempo expressed as "beats" per minute, where "beat" is always defined as a quarter note, *not the numerator of the time signature or the metronomic indication*. - - + + - + Tempo expressed as microseconds per "beat", where "beat" is always defined as a quarter note, *not the numerator of the time signature or the metronomic indication*. - - + + - + General MIDI instrument names. - - - + + + Acoustic Grand Piano Program #0. - + Bright Acoustic Piano Program #1. - + Electric Grand Piano Program #2. - + Honky-tonk Piano Program #3. - + Electric Piano 1 Program #4. - + Electric Piano 2 Program #5. - + Program #6. - + Program #7. - + Program #8. - + Program #9. - + Program #10. - + Program #11. - + Program #12. - + Program #13. - + Tubular Bells Program #14. - + Program #15. - + Drawbar Organ Program #16. - + Percussive Organ Program #17. - + Rock Organ Program #18. - + Church Organ Program #19. - + Reed Organ Program #20. - + Program #21. - + Program #22. - + Tango Accordion Program #23. - + Acoustic Guitar (nylon) Program #24. - + Acoustic Guitar (steel) Program #25. - + Electric Guitar (jazz) Program #26. - + Electric Guitar (clean) Program #27. - + Electric Guitar (muted) Program #28. - + Overdriven Guitar Program #29. - + Distortion Guitar Program #30. - + Guitar harmonics Program #31. - + Acoustic Bass Program #32. - + Electric Bass (finger) Program #33. - + Electric Bass (pick) Program #34. - + Fretless Bass Program #35. - + Slap Bass 1 Program #36. - + Slap Bass 2 Program #37. - + Synth Bass 1 Program #38. - + Synth Bass 2 Program #39. - + Program #40. - + Program #41. - + Program #42. - + Program #43. - + Tremolo Strings Program #44. - + Pizzicato Strings Program #45. - + Orchestral Harp Program #46. - + Program #47. - + String Ensemble 1 Program #48. - + String Ensemble 2 Program #49. - + SynthStrings 1 Program #50. - + SynthStrings 2 Program #51. - + Choir Aahs Program #52. - + Voice Oohs Program #53. - + Synth Voice Program #54. - + Orchestra Hit Program #55. - + Program #56. - + Program #57. - + Program #58. - + Muted Trumpet Program #59. - + French Horn Program #60. - + Brass Section Program #61. - + SynthBrass 1 Program #62. - + SynthBrass 2 Program #63. - + Soprano Sax Program #64. - + Alto Sax Program #65. - + Tenor Sax Program #66. - + Baritone Sax Program #67. - + Program #68. - + English Horn Program #69. - + Program #70. - + Program #71. - + Program #72. - + Program #73. - + Program #74. - + Pan Flute Program #75. - + Blown Bottle Program #76. - + Program #77. - + Program #78. - + Program #79. - + Lead 1 (square) Program #80. - + Lead 2 (sawtooth) Program #81. - + Lead 3 (calliope) Program #82. - + Lead 4 (chiff) Program #83. - + Lead 5 (charang) Program #84. - + Lead 6 (voice) Program #85. - + Lead 7 (fifths) Program #86. - + Lead 8 (bass + lead) Program #87. - + Pad 1 (new age) Program #88. - + Pad 2 (warm) Program #89. - + Pad 3 (polysynth) Program #90. - + Pad 4 (choir) Program #91. - + Pad 5 (bowed) Program #92. - + Pad 6 (metallic) Program #93. - + Pad 7 (halo) Program #94. - + Pad 8 (sweep) Program #95. - + FX 1 (rain) Program #96. - + FX 2 (soundtrack) Program #97. - + FX 3 (crystal) Program #98. - + FX 4 (atmosphere) Program #99. - + FX 5 (brightness) Program #100. - + FX 6 (goblins) Program #101. - + FX 7 (echoes) Program #102. - + FX 8 (sci-fi) Program #103. - + Program #104. - + Program #105. - + Program #106. - + Program #107. - + Program #108. - + Program #109. - + Program #110. - + Program #111. - + Tinkle Bell Program #112. - + Program #113. - + Steel Drums Program #114. - + Program #115. - + Taiko Drum Program #116. - + Melodic Tom Program #117. - + Synth Drum Program #118. - + Reverse Cymbal Program #119. - + Guitar Fret Noise Program #120. - + Breath Noise Program #121. - + Program #122. - + Bird Tweet Program #123. - + Telephone Ring Program #124. - + Program #125. - + Program #126. - + Program #127. - + Acoustic Bass Drum Key #35. - + Bass Drum 1 Key #36. - + Side Stick Key #37. - + Acoustic Snare Key #38. - + Hand Clap Key #39. - + Electric Snare Key #40. - + Low Floor Tom Key #41. - + Closed Hi Hat Key #42. - + High Floor Tom Key #43. - + Pedal Hi-Hat Key #44. - + Low Tom Key #45. - + Open Hi-Hat Key #46. - + Low-Mid Tom Key #47. - + Hi-Mid Tom Key #48. - + Crash Cymbal 1 Key #49. - + High Tom Key #50. - + Ride Cymbal 1 Key #51. - + Chinese Cymbal Key #52. - + Ride Bell Key #53. - + Key #54. - + Splash Cymbal Key #55. - + Key #56. - + Crash Cymbal 2 Key #57. - + Key #58. - + Ride Cymbal 2 Key #59. - + Hi Bongo Key #60. - + Low Bongo Key #61. - + Mute Hi Conga Key #62. - + Open Hi Conga Key #63. - + Low Conga Key #64. - + High Timbale Key #65. - + Low Timbale Key #66. - + High Agogo Key #67. - + Low Agogo Key #68. - + Key #69. - + Key #70. - + Short Whistle Key #71. - + Long Whistle Key #72. - + Short Guiro Key #73. - + Long Guiro Key #74. - + Key #75. - + Hi Wood Block Key #76. - + Low Wood Block Key #77. - + Mute Cuica Key #78. - + Open Cuica Key #79. - + Mute Triangle Key #80. - + Open Triangle Key #81. -

    Instrument names are taken from the list at http://www.midi.org/techspecs/gm1sound.php.

    -

    MEI uses 0-based program numbers.

    -

    Percussion sounds are available when the MIDI channel is set to "10".

    +

    Instrument names are taken from the list at http://www.midi.org/techspecs/gm1sound.php.

    +

    MEI uses 0-based program numbers.

    +

    Percussion sounds are available when the MIDI channel is set to "10".

         - - MIDI values in the following range. - - - 127 + + Generic MIDI value. One-based values must be followed by a lower-case letter "o". + + + 0|([1-9]|[1-9][0-9]|1([0-1][0-9]|2[0-7]))o?|128o - + + data.MIDIVALUE or data.NCName values. + + + + + + + + + data.MIDIVALUE or data.PERCENT.LIMITED values. + + + + + + + + Modes. - - - + + + Major mode. - + Minor mode. - + Dorian mode. - + Phrygian mode. - + Lydian mode. - + Mixolydian mode. - + Aeolian mode. - + Locrian mode. - + Bibliographic relationship values based on MODS version 3.4. - - - + + + Temporal predecessor of the resource. - + Temporal successor to the resource. - + Original form of the resource. - + Parent containing the resource. - + Intellectual or physical component of the resource. - + Version of the resource's intellectual content not changed enough to be a different work. - + Version of the resource in a different physical format. - + Published bibliographic description, review, abstract, or index of the resource's content. - + Cited or referred to in the resource. - + Maxima-long relationship values. - - + + 2 3 - + Long-breve relationship values. - - + + 2 3 - + Music font family. - - + + + + + + "Convenience" datatype that permits combining enumerated values with a user-supplied + name. + + - + "Convenience" datatype that permits combining enumerated values with user-supplied values. - - + + - + Non-staff location. - - - + + + At the foot of the page. - + At the top of the page. - + At the left of the page. - + At the right of the page. - + On the opposite, i.e. facing, page. - + On the other side of the leaf. - + At the end of this division; e.g., chapter, volume, etc. - + Within a line text; i.e., an insertion. - + Between the lines of text, less exact than "sub" or "super". - + Above a line of text, more exact than "intra(linear)". Do not confuse with superscript rendition. - + Below a line of text, more exact than "intra(linear)". Do not confuse with subscript rendition. - + In a predefined space; i.e., that left by an earlier scribe. - + Obscures original text; e.g., via overstrike, addition of new writing surface material, etc. - + Notation type and subtype - - - + + + Common Music Notation. - + Mensural notation. - + Black mensural notation. - + White mensural notation. - + Neumatic notation. - - + + Tablature notation. - + Captures any notehead "modifiers"; that is, symbols added to the notehead, such as slashes, lines, text, and enclosures, etc. - - - - - + + + + + - + Enumerated note head modifier values. - - - + + + Slash (upper right to lower left). - + Backslash (upper left to lower right). - + Vertical line. - + Horizontal line. - + Center dot. - + Enclosing parentheses. - + Enclosing square brackets. - + Enclosing box. - + Enclosing circle. - + Enclosing "fences". - + Captures text rendered in the center of the notehead. - - + + centertext\((A|B|C|D|E|F|G)(f|♭|n|♮|s|♯)?\) @@ -15443,207 +2867,223 @@ - + Oct attribute values. The default values conform to Acoustical Society of America representation. Read, p. 44. - - + + 9 - + The amount of octave displacement; that is, '8' (as in '8va' for 1 octave), '15' (for 2 octaves), or rarely '22' (for 3 octaves). - - + + 8|15|22 - + Rotation or reflection of base symbol values. - - + + reversed|90CW|90CCW - + For musical material designated to appear on another staff, the location of the staff relative to the current one; i.e., the staff above or the staff below. - - - + + + The staff immediately above. - + The staff immediately below. - + The number of panels per page. - - + + 1 2 - + Positive decimal number plus '%', i.e., [0-9]+(\.?[0-9]*)?\%. - - + + [0-9]+(\.?[0-9]*)?% - + + Positive decimal number between 0 and 100, followed by a percent sign "%". + + + (([0-9]|[1-9][0-9])(\.[0-9]+)?|100)% + + + + + Positive decimal number between -100 and 100, followed by a percent sign "%". + + + (\+|-)?(([0-9]|[1-9][0-9])(\.[0-9]+)?|100)% + + + + Page scale factor; a percentage of the values in page.height and page.width. - - + + - + Pclass (pitch class) attribute values. - - + + 11 - + The pitch names (gamut) used within a single octave. The default values conform to Acoustical Society of America representation. - - + + [a-g] - + Gestural pitch names need an additional value for when the notated pitch is not to be sounded. - - + + [a-g]|none - + Pnum (pitch number, e.g. MIDI) attribute values. - - + + - + Location information. - - - - - - + + + + + + - + - - Other values not permitted when 'above', 'below', 'between' or 'within' is + + Other values not permitted when 'above', 'below', 'between' or 'within' is present. - + Semibreve-minim relationship values. - - + + 2 3 - + A ratio, i.e., [0-9]+(\.?[0-9]*)?:[0-9]+(\.?[0-9]*)? For example, "40:7.2319". - - + + [0-9]+(\.?[0-9]*)?:[0-9]+(\.?[0-9]*)? - + General-purpose relationships - - - - - - + + + + + + - + Rotation. - - - - - + + + + + - + Rotation term. - - - + + + No rotation. - + Rotated 180 degrees. - + Rotated 270 degrees clockwise. - + Rotated 45 degrees clockwise. - + Rotated 315 degrees clockwise. - + Rotated 135 degrees clockwise. - + Rotated 225 degrees clockwise. - + Scale degree values. - - + + (\^|v)?[1-7](\+|\-)? - + The number of slashes to be rendered for tremolandi. - - + + 1 6 - + i=initial, m=medial, t=terminal. Number is used to match endpoints of the slur when slurs are nested or overlap. - - + + [i|m|t][1-6] @@ -15655,352 +3095,352 @@ - + Items that may be printed above, below, or between staves. - - - - - - - + + + + + + + - + Items in all repertoires that may be printed near a staff. - - - + + + Accidentals. - + Annotations. - + Articulations. - + Directives. - + Dynamics. - + Harmony indications. - + Ornaments. - - - + + + Spoken text. - + Stage directions. - + Tempo markings. - + Staff location. The value '0' indicates the bottom line of the current staff; positive values are used for positions above the bottom line and negative values for the positions below. For example, in treble clef, 1 = F4, 2 = G4, 3 = A4, etc. and -1 = D4, -2 = C4, and so on. - - + + - + Location of musical material relative to a staff. - - - - - + + + + + - + - + The @staff attribute must contain 2 numerically-adjacent integer values. Staves and - are not adjacent. + are not adjacent. - + Location of symbol relative to a staff. - - - + + + Above the staff. - + Below the staff. - + Location of symbol relative to a staff. - - - + + + Between staves. - + Within/on the staff. - + Stem direction. - - - - - + + + + + - + Common stem directions. - - - + + + Stem points upwards. - + Stem points downwards. - + Additional stem directions. - - - + + + Stem points left. - + Stem points right. - + Stem points up and right. - + Stem points down and right. - + Stem points up and left. - + Stem points down and left. - + Stem modification. - - - + + + No modifications to stem. - + 1 slash through stem. - + 2 slashes through stem. - + 3 slashes through stem. - + 4 slashes through stem. - + 5 slashes through stem. - + 6 slashes through stem. - + X placed on stem. - + Z placed on stem. - + Position of a note's stem relative to the head of the note. - - - + + + Stem attached to left side of note head. - + Stem attached to right side of note head. - + Stem is originates from center of note head. - + In string tablature, the number of the string to be played, i.e., [1-9]+. - - + + - + Temperament or tuning system. - - - + + + Equal or 12-tone temperament. - + Just intonation. - + Meantone intonation. - + Pythagorean tuning. - + Beats (meter signature denominator) per minute, e.g. 120. - - + + - + Breve-semibreve relationship values. - - + + 2 3 - + Closed list of text rendition values. - - - + + + Surrounded by single quotes. - + Surrounded by double quotes. - + Italicized (slanted to right). - + Oblique (slanted to left). - + Small capitals. - + Relative font weight. - + Relative font weight. - + Relative font weight. - + Enclosed in box. - + Enclosed in ellipse/circle. - + Enclosed in diamond. - + Enclosed in triangle. - + Struck through by '\' (back slash). - + Struck through by '/' (forward slash). - + Struck through by '-'; may be qualified to indicate multiple parallel lines, e.g. line-through(2). - + Not rendered, invisible. - + Line above the text; may be qualified to indicate multiple parallel lines, e.g. overline(3). - + Use for deleted text fully or partially obscured by other text (such as 'XXXXX') or musical symbols (such as notes, rests, etc.). - + Struck through by '-'; equivalent to line-through; may be qualified to indicate multiple parallel lines, e.g. strike(3). - + Subscript. - + Superscript. - + Use for added text or musical symbols that fully or partially obscure text from an earlier writing stage. - + Underlined; may be qualified to indicate multiple parallel lines, e.g. underline(2). - + Crossed-out; equivalent to 'bslash' (\) plus 'fslash' (/); that is, a hand-written 'X'; may be qualified to indicate multiple parallel lines, e.g. x-through(2). - + Left-to-right (BIDI embed). - + Right-to-left (BIDI embed). - + Left-to-right (BIDI override). - + Right-to-left (BIDI override). - + Parameterized text rendition values. - - + + (underline|overline|line-through|strike|x-through)\(\d+\) @@ -16010,125 +3450,125 @@ - + Text rendition values. - - - - - + + + + + - + Tie attribute values: initial, medial, terminal. - - + + [i|m|t] - + A positive or negative offset from the value given in the tstamp attribute in terms of musical time, i.e., beats[.fractional beat part]. - - + + - + Tuplet attribute values: initial, medial, terminal. - - + + [i|m|t][1-6] - + Basic, i.e., single, uninterrupted, neume forms. - - - - - - - - - + + + + + + + + + - + Basic, i.e., single, uninterrupted, neume names. - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + - + A Uniform Resource Identifier, see [RFC2396]. - - + + - + Data values for attributes that capture vertical alignment. - - - + + + Top aligned. - + Middle aligned. - + Bottom aligned. - + Baseline aligned. - + A single "word" that contains only letters, digits, punctuation characters, or symbols. It cannot contain whitespace. - - + + (\p{L}|\p{N}|\p{P}|\p{S})* - + Attributes that provide for classification of notation. - - + + Contains classification of the notation contained or described by the element bearing this attribute. - - + + - + Provides any sub-classification of the notation contained or described by the element, additional to that given by its notationtype attribute. - - + + - + - + An element with a notationsubtype attribute must have a notationtype attribute. @@ -16139,140 +3579,143 @@     - + Analytical component declarations. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - - + + - + Analytical domain attributes. - + Analytical domain attributes. - - + + - + + Analytical domain attributes. + + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - - + + - - + + Indicates to what degree the harmonic label is supported by the notation. - - + + The notation contains all the notes necessary for the harmonic label, e.g., the notes "D F♯ A" for the harmonic label "D". - + The harmonic label relies on notes implied, but not actually present, in the notation, e.g., the notes "D F♯ C" for the harmonic label "D7". The note "A" is missing from the notation, but can be implied. @@ -16281,514 +3724,516 @@ - + Attributes describing the harmonic function of a single pitch. - - + + Captures scale degree information using Humdrum **deg syntax -- an optional indicator of melodic approach (^ = ascending approach, v = descending approach), a scale degree value (1 = tonic ... 7 = leading tone), and an optional indication of chromatic alteration, "1", "v7", "^1", or "v5+", for example. The amount of chromatic alternation is not indicated. - - + + - + + Analytical domain attributes. + + Analytical domain attributes. - + Analytical domain attributes. - + Attributes that describe harmonic intervals. - - + + Encodes the harmonic interval between pitches occurring at the same time. - - + + - + Attributes that provide for description of intervallic content. - - + + Encodes the melodic interval from the previous pitch. The value may be a general directional indication (u, d, s, etc.), an indication of diatonic interval direction, quality, and size, or a precise numeric value in half steps. - - + + - - - - - The @intm attribute is not allowed on the - first component of a neume. - - - - + Attributes that provide for description of intervallic content. - - - + + + - + Analytical domain attributes. - + Analytical domain attributes. - - - + + + - - + + Indicates major, minor, or other tonality. - - + + - + Used by staffDef and scoreDef to provide default values for attributes in the analytical domain that are related to key signatures. - - + + Contains an accidental for the tonic key, if one is required, e.g., if key.pname equals 'c' and key.accid equals 's', then a tonic of C# is indicated. - - + + - + Indicates major, minor, or other tonality. - - + + - + Holds the pitch name of the tonic key, e.g. 'c' for the key of C. - - + + - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - - + + - + Attributes describing melodic function. - - + + Describes melodic function using Humdrum **embel syntax. - - + + - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes in the CMN repertoire. - - + + - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes in the CMN repertoire. Use the n attribute to explicitly encode this measure's position in a string of measures containing only mRest elements. - - + + - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - - - - - - - + + + + + + - + Analytical domain attributes. - - - - - - - + Analytical domain attributes. - - - - - - - - - - - - - + + + Analytical domain attributes. + + + + + + + + + + + + + + Analytical domain attributes. + + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - - + + - + Attributes that describe pitch class. - - + + Holds pitch class information. - - + + - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - - + + + Analytical domain attributes. + + - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - - + + - + Analytical domain attributes. - + Analytical domain attributes. - - + + - + + Analytical domain attributes. + + Attributes that specify pitch using sol-fa. - - + + Contains sol-fa designation, e.g., do, re, mi, etc., in either a fixed or movable Do system. - - + + - + Analytical domain attributes. - + Analytical domain attributes. - - + + - + Analytical domain attributes. - + Analytical domain attributes. - - + + - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - - + + + Analytical domain attributes. + + - + Analytical domain attributes. - + Analytical domain attributes. - + Analytical domain attributes. - + Common Music Notation (CMN) repertoire component declarations. - + Logical, that is, written, duration attribute values for the CMN repertoire. - - - + + + Quadruple whole note. - + Double whole note. - + Whole note. - + Half note. - + Quarter note. - + 8th note. - + 16th note. - + 32nd note. - + 64th note. - + 128th note. - + 256th note. - + 512th note. - + 1024th note. - + 2048th note. - + Items in the CMN repertoire that may be printed near a staff. - - - + + + Beams. - - - + + + Bend indications. - + + Brackets, e.g., for transcribed ligatures. + + Breath marks. - + Copy marks. - + Fermatas. - + Fingerings. - - - - Hairpins. + + + + Hairpin dynamics. - + Harp pedals. - - Ligature indicators. - - - Laissez vibrer/open tie marks. + + Laissez vibrer indications, sometimes called "open ties". - + Mordents. - + Octaviation marks. - - Piano pedals. + + Piano pedal marks. - + Rehearsal marks. - - - + + + Ties. - + Trills. - + Tuplets. - - - + + + Turns. - + Logical domain attributes. - - - + + + - - + + Describes the direction in which an arpeggio is to be performed. - - + + Lowest to highest pitch. - + Highest to lowest pitch. - + Non-arpeggiated style (usually rendered with a preceding bracket instead of a wavy line). @@ -16796,585 +4241,576 @@ - + Logical domain attributes. - - - + + + - + Attributes indicating cross-staff beaming. - - + + In the case of cross-staff beams, the beam.with attribute is used to indicate which staff the beam is connected to; that is, the staff above or the staff below. - - + + - + Used by layerDef, staffDef, and scoreDef to provide default values for attributes in the logical domain related to beaming. - - + + Provides an example of how automated beaming (including secondary beams) is to be performed. - - + + - + Indicates whether automatically-drawn beams should include rests shorter than a quarter note duration. - - + + -

    The beam.group attribute can be used to set a default beaming pattern to be used - when no beaming is indicated at the event level. beam.group must contain a +

    The beam.group attribute can be used to set a default beaming pattern to be used + when no beaming is indicated at the event level. beam.group must contain a comma-separated list of time values that add up to a measure, e.g., in 4/4 time '4,4,4,4' indicates each quarter note worth of shorter notes would be beamed together. Parentheses can be used to indicate sub-groupings of secondary beams. For example, '(4.,4.,4.)' in 9/8 meter indicates one outer beam per measure with secondary beams broken at each dotted quarter - duration, while a measure of 16th notes in 4/4 with beam.group equal to + duration, while a measure of 16th notes in 4/4 with beam.group equal to '(4,4),(4,4)' will result in a primary beam covering all the notes and secondary beams for each group of 4 notes. This beaming "directive" can be overridden by using beam elements. If neither beam elements or the - beam.group attribute is used, then no beaming is rendered. Beaming can be - explicitly 'turned off' by setting beam.group to an empty string.

    + beam.group attribute is used, then no beaming is rendered. Beaming can be + explicitly 'turned off' by setting beam.group to an empty string.

         - + Attributes that indicate whether an event lies under a beam. - - + + Indicates that this event is "under a beam". - - + + - + Attributes that record the visual rendition of beams. - - + + Captures whether a beam is "feathered" and in which direction. - - + + (accelerando) indicates that the secondary beams get progressively closer together toward the end of the beam. - + (mixed acc and rit) for beams that are "feathered" in both directions. - + (ritardando) means that the secondary beams become progressively more distant toward the end of the beam. - + (normal) indicates that the secondary beams are equidistant along the course of the beam. - + Records the placement of the beam relative to the events it affects. - - + + - + - + Stem direction must be specified for all notes and chords under the beam. Opposing stem directions are required for a beam with @place="mixed". - + Opposing stem directions are required for a beam with @place="mixed". - + Indicates presence of slash through the beam. - - + + - + Records the slope of the beam. - - + + - + Attributes that capture information about secondary beaming. - - + + Presence of this attribute indicates that the secondary beam should be broken following this note/chord. The value of the attribute records the number of beams which should remain unbroken. - - + + - + Logical domain attributes. - - - - - - + + + + + + - + Logical domain attributes. - - + + - - + + Indicates the performed duration represented by the beatRpt symbol; expressed in time signature denominator units. - - + + \d+(\.\d+)? - + Logical domain attributes. - - - - - + + + + + - + Logical domain attributes. - - - - - + + + + + - + Logical domain attributes. - - - - - - - + + + + + + + - + Logical domain attributes. - - - - - - - - + + + + + + + + Indicates whether the tremolo is measured or unmeasured. - - + + Measured tremolo. - + Unmeasured tremolo. - + Analytical domain attributes in the CMN repertoire. - - - - - - - - + + + + + + + + - + Gestural domain attributes for CMN features. - + Logical domain attributes in the CMN repertoire. - - + + - + Visual domain attributes for chord. The slur, slur.dir, slur.rend, tie, tie.dir, and tie.rend attributes here are "syntactic sugar" for these attributes on each of the chord's individual notes. The values here apply to all the notes in the chord. If some notes are slurred or tied while others aren't, then the individual note attributes must be used. - - + + - + Attributes that indicate how to render the staff lines of the measure containing an element belonging to this attribute class. - - + + "Cut-out" style. - - + + The staff lines should not be drawn. - + Analytical domain attributes. - + Gestural domain attributes. - + Logical domain attributes. - + Visual domain attributes. - - - - - - + + + + + + - + Attributes that indicate whether to render a repeat symbol or the source material to which it refers. - - + + Indicates whether to render a repeat symbol or the source material to which it refers. A value of 'true' renders the source material, while 'false' displays the repeat symbol. - - + + - + Logical domain attributes. - - - + + + - + Logical domain attributes. - - - - + + + + - - + + Describes the style of the tremolo. - - + + Measured tremolo. - + Unmeasured tremolo. - + Attributes that indicate whether an event participates in a glissando. - - + + Indicates that this element participates in a glissando. If visual information about the glissando needs to be recorded, then a gliss element should be employed instead. - - + + - + Logical domain attributes. - - - - - + + + + + - + Attributes that mark a note or chord as a "grace", how it should "steal" time, and how much time should be allotted to the grace note/chord. - - + + Marks a note or chord as a "grace" (without a definite performed duration) and records from which other note/chord it should "steal" time. - - + + - + Records the amount of time to be "stolen" from a non-grace note/chord. - - + + - + Analytical domain attributes. - + Gestural domain attributes. - + Logical domain attributes. - - - + + + - - + + Records whether the grace note group is attached to the following event or to the preceding one. The usual name for the latter is "Nachschlag". - - + + Attached to the preceding event. - + Attached to the following event. - + Attachment is ambiguous. - + Visual domain attributes. - - + + - + Logical domain attributes. - - - - - - - - + + + + + + + + Captures the visual rendition and function of the hairpin; that is, whether it indicates an increase or a decrease in volume. - - + + Crescendo; i.e., louder. - + Diminuendo; i.e., softer. - + Indicates that the hairpin starts from or ends in silence. Often rendered as a small circle attached to the closed end of the hairpin. See Gould, p. 108. - - + + - + Logical domain attributes. - - - + + + - + Logical domain attributes. The pedal setting, i.e., flat, natural, or sharp, for each diatonic pitch name is indicated by the seven letter-named attributes. - - - + + + - - + + Indicates the pedal setting for the harp's C strings. n - - + + Flat. - + Natural. - + Sharp. - + Indicates the pedal setting for the harp's D strings. n - - + + Flat. - + Natural. - + Sharp. - + Indicates the pedal setting for the harp's E strings. n - - + + Flat. - + Natural. - + Sharp. - + Indicates the pedal setting for the harp's F strings. n - - + + Flat. - + Natural. - + Sharp. - + Indicates the pedal setting for the harp's G strings. n - - + + Flat. - + Natural. - + Sharp. - + Indicates the pedal setting for the harp's A strings. n - - + + Flat. - + Natural. - + Sharp. - + Indicates the pedal setting for the harp's B strings. n - - + + Flat. - + Natural. - + Sharp. - + Logical domain attributes. - - + + - + Logical domain attributes. - - - - - + + + + - - Logical domain attributes. - - - - - - - + Attributes that indicate the presence of an l.v. (laissez vibrer) marking attached to a feature. If visual information about the lv sign needs to be recorded, then an lv element should be employed. - - + + Indicates the attachment of an l.v. (laissez vibrer) sign to this element. - - + + - + Logical domain attributes. The n attribute contains a name or number associated with the measure (Read, p. 445). Often, this is an integer, but not always. For example, some measures, especially incomplete measures or those under an ending mark, may have labels that contain an @@ -17383,40 +4819,40 @@ machine-generated instead of encoding them in the markup. However, an explicit measure number should restart numbering with the given value. The join attribute may be used to indicate another measure which metrically completes the current, incomplete one. - - - + + + - - + + Indicates the visual rendition of the left bar line. It is present here only for facilitation of translation from legacy encodings which use it. Usually, it can be safely ignored. - - + + - + Indicates the function of the right bar line and is structurally important. - - + + - + Logical domain attributes. - - + + Function of the meter signature group. - - - Meter signatures appear in alternating measures. + + + Meter signatures apply to alternating measures. - + Meter signatures are interchangeable, e.g. 3/4 and 6/8. - + Meter signatures with different unit values are used to express a complex metrical pattern that is not expressible using traditional means, such as 2/4+1/8. @@ -17424,176 +4860,176 @@ - + Logical domain attributes. - - - - + + + + - + Logical domain attributes. - - + + - + Logical domain attributes. - - + + - + Logical domain attributes in the CMN repertoire. - - - + + + - + Logical domain attributes. - - - + + + - + Logical domain attributes. - - - + + + - + Analytical domain attributes in the CMN repertoire. - - - - - - - - - - - - - + + + + + + + + + + + + + Logical domain attributes. - - + + - + Visual domain attributes. - - + + - + Attributes that record numbers to be displayed with a feature. - - + + Records a number or count accompanying a notational feature. - - + + - + Attributes that record the placement and visibility of numbers that accompany a bowed tremolo or tuplet. - - + + States where the tuplet number will be placed in relation to the note heads. - - + + - + Determines if the tuplet number is visible. - - + + - + Logical domain attributes. - - - - - - - - - + + + + + + + + + Indicates whether the octave displacement should be performed simultaneously with the written notes, i.e., "coll' ottava". Unlike other octave signs which are indicated by broken lines, coll' ottava typically uses an unbroken line or a series of longer broken lines, ending with a short vertical stroke. See Read, p. 47-48. - - + + Coll' ottava (with the octave). - + Logical domain attributes. - + Logical domain attributes. - - - - + + + + - - + + Records the position of the piano damper pedal. - - + + Depress the pedal. - + Release the pedal. - + Half pedal. - + Release then immediately depress the pedal. - + Indicates the function of the depressed pedal, but not necessarily the text associated - with its use. Use the dir element for such text. - - + with its use. Use the dir element for such text. + + - - + + The sustain pedal, also referred to as the "damper" pedal, allows the piano strings to vibrate sympathetically with the struck strings. It is the right-most and the most frequently used pedal on modern pianos. - + The soft pedal, sometimes called the "una corda", "piano", or "half-blow" pedal, reduces the volume and modifies the timbre of the piano. On the modern piano, it is the left-most pedal. - + The sostenuto or tone-sustaining pedal allows notes already undamped to continue to ring while other notes are damped normally; that is, on their release by the fingers. This is usually the center pedal of the modern piano. - + The silent or practice pedal mutes the volume of the piano so that one may practice quietly. It is sometimes a replacement for the sostenuto pedal, especially on an upright or vertical instrument. @@ -17602,29 +5038,29 @@ - + Visual domain attributes. - - - + + + - + Used by scoreDef and staffDef to provide default description of piano pedal rendition. - - + + Determines whether piano pedal marks should be rendered as lines or as terms. - - + + Continuous line with start and end positions rendered by vertical bars and bounces shown by upward-pointing "blips". - + Pedal down and half pedal rendered with "Ped.", pedal up rendered by "*", pedal "bounce" rendered with "* Ped.". - + Pedal up and down indications same as with "pedstar", but bounce is rendered with "Ped." only. @@ -17632,290 +5068,290 @@ - + Logical domain attributes. - - - - - - - + + + + + + + - + Attributes used by scoreDef and staffDef to provide default information about rehearsal numbers/letters. - - + + Describes the enclosing shape for rehearsal marks. - - + + Enclosed by box. - + Enclosed by circle. - + No enclosing shape. - + Analytical domain attributes in the CMN repertoire. - - - - + + + + - + Logical domain attributes in the CMN repertoire. - + Visual domain attributes. - - + + - + Logical domain attributes. - - + + - + Visual domain attributes. - - - - - - - - - + + + + + + + + + Determines whether to display guitar chord grids. - - + + - + Logical domain attributes. - - - - - + + + + + - + Attributes that describe the rendition of slurs. - - - - + + + + - - - + + + - + Analytical domain attributes in the CMN repertoire. - - - - + + + + - + Logical domain attributes in the CMN repertoire. - + Logical domain attributes for staffDef in the CMN repertoire. - - + + - + Visual domain attributes for staffDef in the CMN repertoire. - - - - - - + + + + + + - + Attributes that describe the properties of stemmed features; that is, chords and notes. - - + + Contains an indication of which staff a note or chord that logically belongs to the current staff should be visually placed on; that is, the one above or the one below. - - + + - + Logical domain attributes. - - - - + + + + - + Attributes that describe the rendition of ties. - - - - + + + + - - - + + + - + Attributes that describe measured tremolandi. - - + + The performed duration of an individual note in a measured tremolo. - - + + - + Logical domain attributes. - - - - - - + + + + + + - + Logical domain attributes. - - - - - - - + + + + + + + - + Groups control events that appear in CMN. - - - - + + + + - + Groups events that appear in CMN. - - + + - + Groups events that completely fill a CMN measure. - - + + - + Groups notated events that may appear at the layer level in CMN. - - + + - + Groups CMN measure-like elements. - - + + - + Groups elements that may appear within a CMN measure. - + Groups elements that function like ossia. - - - + + + - + Groups elements that may appear as part of a section. - - + + - + (arpeggiation) – Indicates that the notes of a chord are to be performed successively rather than simultaneously, usually from lowest to highest. Sometimes called a "roll". - - - - - - - - + + + + + + + + - - + + -

    The modern arpeggiation symbol is a vertical wavy line preceding the chord. When the notes +

    The modern arpeggiation symbol is a vertical wavy line preceding the chord. When the notes of the chord are to be performed from highest to lowest, an arrowhead may be added to the lower end of the line. Even though it is redundant, an arrowhead is sometimes added to the upper end of the line for the sake of consistency or when the direction of successive arpeggios alternates. In music for keyboard instruments, sometimes a distinction is made between a single arpeggio in which both hands play successively and simultaneous arpeggios in two hands. In the case of the former, multiple values may be required in the - staff and layer attributes. Arpeggios that do not cross staves, but - still involve more than one layer require multiple values for the layer + staff and layer attributes. Arpeggios that do not cross staves, but + still involve more than one layer require multiple values for the layer attribute.

         - + An instruction to begin the next section or movement of a composition without pause. - - - - - - - - - - - - - + + + + + + + + + + + + + @@ -17925,38 +5361,38 @@ - + - + Must have one of the attributes: startid, tstamp, tstamp.ges or tstamp.real. -

    As a specialized directive, attacca is a control element. That is, it +

    As a specialized directive, attacca is a control element. That is, it can be linked via its attributes to other events. The starting point of the attacca - directive may be indicated by either a startid, tstamp, - tstamp.ges, or tstamp.real attribute, while the ending point may be - recorded by either a dur, dur.ges, endid, or - tstamp2 attribute. It is a semantic error not to specify a starting point + directive may be indicated by either a startid, tstamp, + tstamp.ges, or tstamp.real attribute, while the ending point may be + recorded by either a dur, dur.ges, endid, or + tstamp2 attribute. It is a semantic error not to specify a starting point attribute.

         - + A container for a series of explicitly beamed events that begins and ends entirely within a measure. - - - - - - - - - - - + + + + + + + + + + + @@ -17966,40 +5402,40 @@ - + - + A beam without a copyof attribute must have at least 2 note, rest, chord, or space descendants. -

    For beams that cross the bar line, use the beamSpan element. - Secondary beams may be broken explicitly using the breaksec attribute on the +

    For beams that cross the bar line, use the beamSpan element. + Secondary beams may be broken explicitly using the breaksec attribute on the notes or chords under the beam. Automated beaming, as opposed to explicitly marked beams, - may be indicated for an entire score, part or section by using the beam.group and - beam.rests attributes on these elements.

    + may be indicated for an entire score, part or section by using the beam.group and + beam.rests attributes on these elements.

         - + (beam span) – Alternative element for explicitly encoding beams, particularly those which extend across bar lines. - - - - - - - - - - - - - + + + + + + + + + + + + + - + Must have one of the attributes: startid, tstamp, tstamp.ges or tstamp.real. Must have one of the attributes: @@ -18008,55 +5444,54 @@ -

    The starting point of the beam may be indicated by either a startid, - tstamp, tstamp.ges, or tstamp.real attribute, while the - ending point may be recorded by either a dur, dur.ges, - endid, or tstamp2 attribute. It is a semantic error not to specify - one starting and one ending type of attribute.

    +

    The starting point of the beam may be indicated by either a startid, + tstamp, tstamp.ges, or tstamp.real attribute, while the + ending point may be recorded by either a dur, dur.ges, + endid, or tstamp2 attribute. It is a semantic error not to specify one + starting and one ending type of attribute.

         - + (beat repeat) – An indication that material on a preceding beat should be repeated. - - - - - - - - - - - - - - - -

    - beatRpt may also be used in guitar or rhythm parts to indicate where + + + + + + + + + + + + + + + +

    beatRpt may also be used in guitar or rhythm parts to indicate where chord changes occur. When these parts require durations longer or shorter than a beat; however, note elements with appropriately-shaped note heads should be employed.

         - + A variation in pitch (often micro-tonal) upwards or downwards during the course of a note. - - - - - - - - - - - - - + + + + + + + + + + + + + - + Must have one of the attributes: startid, tstamp, tstamp.ges or tstamp.real. Must have one of the attributes: @@ -18065,28 +5500,28 @@ - + Marks a sequence of notational events grouped by a bracket. - - - - - - - - - - - + + + + + + + + + + + - + - + Must have one of the attributes: startid, tstamp, tstamp.ges or tstamp.real. Must have one of the attributes: @@ -18094,136 +5529,136 @@ - - + + Describes the function of the bracketed event sequence. - - + + - - + + Represents coloration in the mensural notation source material. - + Marks a sequence which does not match the current meter. - + Represents a ligature in the mensural notation source material. -

    Text that interrupts the bracket used to mark the event group may be captured as the +

    Text that interrupts the bracket used to mark the event group may be captured as the content of bracketSpan. The starting point of the group/bracket may be - indicated by either a startid, tstamp, tstamp.ges, or - tstamp.real attribute, while the ending point may be recorded by either a - dur, dur.ges, endid, or tstamp2 attribute. It - is a semantic error not to specify one starting and one ending type of attribute.

    + indicated by either a startid, tstamp, tstamp.ges, or + tstamp.real attribute, while the ending point may be recorded by either a + dur, dur.ges, endid, or tstamp2 attribute. It is + a semantic error not to specify one starting and one ending type of attribute.

         - + (breath mark) – An indication of a point at which the performer on an instrument requiring breath (including the voice) may breathe. - - - - - - - - - - - - - + + + + + + + + + + + + + - + Must have one of the attributes: startid, tstamp, tstamp.ges or tstamp.real. -

    This element may also indicate a short pause or break for instruments *not* requiring +

    This element may also indicate a short pause or break for instruments *not* requiring breath. In such cases, it functions as a guide to phrasing. The starting point of the breath - mark may be indicated by either a startid, tstamp, - tstamp.ges, or tstamp.real attribute. It is a semantic error not to + mark may be indicated by either a startid, tstamp, + tstamp.ges, or tstamp.real attribute. It is a semantic error not to specify a starting point attribute.

    -

    Since the breath mark does not disrupt the normal tempo of a performance, it has no +

    Since the breath mark does not disrupt the normal tempo of a performance, it has no directly encode-able duration.

    -

    The default value for place for a breath mark is "above". Unless indicated by +

    The default value for place for a breath mark is "above". Unless indicated by other attributes, a breath mark will be rendered as a comma-like symbol above the top line of the staff.

         - + (bowed tremolo) – A rapid alternation on a single pitch or chord. - - - - - - - - - - - + + + + + + + + + + + - + 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'. - - - - - - - - - - - - - + + + + + + + + + + + + + - + Must have one of the attributes: startid, tstamp, tstamp.ges or tstamp.real. -

    The shape attribute may be used to record whether the fermata is curved, square, - or triangular, while form may be used to capture whether the fermata is +

    The shape attribute may be used to record whether the fermata is curved, square, + or triangular, while form may be used to capture whether the fermata is "upright", i.e., has the curve or bracket above the dot, or inverted, i.e., has the curve or bracket below the dot. Other visual forms of a fermata may be indicated via the - altsym attribute. The starting point of the fermata may be indicated by either - a startid, tstamp, tstamp.ges, or tstamp.real + altsym attribute. The starting point of the fermata may be indicated by either a + startid, tstamp, tstamp.ges, or tstamp.real attribute. It is a semantic error not to specify a starting point attribute.

         - + (fingered tremolo) – A rapid alternation between a pair of notes (or chords or perhaps between a note and a chord) that are (usually) farther apart than a major second. - - - - - - - - - - - + + + + + + + + + + + @@ -18241,29 +5676,29 @@ - + (glissando) – A continuous or sliding movement from one pitch to another, usually indicated by a straight or wavy line. - - - - - - - - - - - + + + + + + + + + + + - + - + Must have one of the attributes: startid, tstamp, tstamp.ges or tstamp.real. Must have one of the attributes: @@ -18272,30 +5707,30 @@ -

    Commonly also called a 'slide'. The term 'glissando' is frequently used to indicate both +

    Commonly also called a 'slide'. The term 'glissando' is frequently used to indicate both the case where distinct intermediate pitches are produced (as on the piano) and the case where they are not (as on the trombone), though the latter is sometimes referred to as 'portamento'. The visual appearance of the indicating line may be recorded in the - lform and lwidth attributes. The starting point of the glissando may - be indicated by either a startid, tstamp, tstamp.ges, or - tstamp.real attribute, while the ending point may be recorded by either a - dur, dur.ges, endid, or tstamp2 attribute. It - is a semantic error not to specify one starting and one ending type of attribute.

    + lform and lwidth attributes. The starting point of the glissando may + be indicated by either a startid, tstamp, tstamp.ges, or + tstamp.real attribute, while the ending point may be recorded by either a + dur, dur.ges, endid, or tstamp2 attribute. It is + a semantic error not to specify one starting and one ending type of attribute.

         - + A container for a sequence of grace notes. - - - - - - - - - - - + + + + + + + + + + + @@ -18305,41 +5740,41 @@ - + - + A graceGrp without a copyof attribute must have at least 2 note, rest, chord, or space descendants. - + - + The grace attribute is not allowed on descendants of a graceGrp with a grace attribute. - + Indicates continuous dynamics expressed on the score as wedge-shaped graphics, e.g. < and >. - - - - - - - - - - - - - + + + + + + + + + + + + + - + Must have one of the attributes: startid, tstamp, tstamp.ges or tstamp.real. Must have one of the attributes: @@ -18348,79 +5783,79 @@ -

    The hairpin element is used for graphical, i.e., +

    The hairpin element is used for graphical, i.e., crescendo and diminuendo, dynamic markings. For instantaneous or continuous - textual dynamics, such as 'p', 'mf', or 'cres. poco a poco', the dynam element should be used. The starting point of the hairpin marking - may be indicated by either a startid, tstamp, tstamp.ges, - or tstamp.real attribute, while the ending point may be recorded by either a - dur, dur.ges, endid, or tstamp2 attribute. It - is a semantic error not to specify one starting and one ending type of attribute. MIDI - values associated with the graphical dynamic sign may be recorded in the val and - val2 attributes.

    + textual dynamics, such as 'p', 'mf', or 'cres. poco a poco', the dynam element should be used. The starting point of the hairpin marking + may be indicated by either a startid, tstamp, tstamp.ges, + or tstamp.real attribute, while the ending point may be recorded by either a + dur, dur.ges, endid, or tstamp2 attribute. It is + a semantic error not to specify one starting and one ending type of attribute. MIDI values + associated with the graphical dynamic sign may be recorded in the val and + val2 attributes.

         - + (half-measure repeat) – A half-measure repeat in any meter. - - - - - - - - + + + + + + + + - - + + - + (harp pedal) – Harp pedal diagram. - - - - - - - - - - - - - + + + + + + + + + + + + + - + Must have one of the attributes: startid, tstamp, tstamp.ges or tstamp.real. -

    The starting point of the harp pedal diagram may be indicated by either a - tstamp, tstamp.ges, tstamp.real or startid +

    The starting point of the harp pedal diagram may be indicated by either a + tstamp, tstamp.ges, tstamp.real or startid attribute. It is a semantic error not to specify a starting point attribute.

         - + A "tie-like" indication that a note should ring beyond its written duration. - - - - - - - - - - - + + + + + + + + + + + - + - + Must have one of the attributes: startid, tstamp, tstamp.ges or tstamp.real. Must have one of the attributes: @@ -18428,9 +5863,9 @@ - + - + The visual attributes of the lv element (@bezier, @bulge, @curvedir, @lform, @lwidth, @ho, @startho, @endho, @to, @startto, @endto, @vo, @startvo, @endvo, @x, @y, @x2, and @y2) will be overridden by visual attributes of the contained curve @@ -18439,30 +5874,30 @@ -

    The lv element captures the graphical, "tie-like" symbol. Any associated text, such as +

    The lv element captures the graphical, "tie-like" symbol. Any associated text, such as "l.v.", must be captured using a dir element.

         - + Unit of musical time consisting of a fixed number of note values of a given type, as determined by the prevailing meter, and delimited in musical notation by bar lines. - - - - - - - - - - - - - - + + + + + + + + + + + + + + - + @@ -18477,69 +5912,69 @@ -

    In MEI, the measure element is a grouping mechanism for events and +

    In MEI, the measure element is a grouping mechanism for events and control events. Pointing attributes make it possible to connect this element to other - internal or external entities, such as media objects or annotations. The width + internal or external entities, such as media objects or annotations. The width attribute may be used to capture the width of the measure for interchange with music printing systems that utilize this information for printing.

         - + (meter signature) – Written meter signature. - - - - - - - - + + + + + + + + - - + + - + (meter signature group) – Used to capture alternating, interchanging, and mixed meter signatures. - - - - - - - - - - - + + + + + + + + + + + - + - + meterSigGrp must have at least 2 child meterSig elements. - + (measure number) – Designation, name, or label for a measure, often but not always - consisting of digits. Use this element when the n attribute on measure does not adequately capture the appearance or placement of the measure + consisting of digits. Use this element when the n attribute on measure does not adequately capture the appearance or placement of the measure number/label. - - - - - - - - - - - + + + + + + + + + + + @@ -18548,146 +5983,143 @@ -

    - mNum uses a subset of model.textPhraseLike.limited.

    +

    mNum uses a subset of model.textPhraseLike.limited.

         - - (measure rest) – Complete measure rest in any meter. - - - - - - - - - + + (measure rest) – Complete measure rest in any meter. + + + + + + + + - - + + -

    Automatically-generated numbering of consecutive measures of rest may be controlled via the - multi.number attribute on the scoreDef or staffDef elements.

    +

    Automatically-generated numbering of consecutive measures of rest may be controlled via the + multi.number attribute on the scoreDef or staffDef elements.

         - + (measure repeat) – An indication that the previous measure should be repeated. - - - - - - - - + + + + + + + + - - + + -

    The automated numbering of consecutive measures of rest may be controlled via the - multi.number attribute on the scoreDef or staffDef elements.

    +

    The automated numbering of consecutive measures of rest may be controlled via the + multi.number attribute on the scoreDef or staffDef elements.

         - + (2-measure repeat) – An indication that the previous two measures should be repeated. - - - - - - - - + + + + + + + + - - + + - + (measure space) – A measure containing only empty space in any meter. - - - - - - - - + + + + + + + + - - + + -

    The automated numbering of consecutive measures of space may be controlled via the - multi.number attribute on the scoreDef or staffDef elements.

    +

    The automated numbering of consecutive measures of space may be controlled via the + multi.number attribute on the scoreDef or staffDef elements.

         - + (multiple rest) – Multiple measures of rest compressed into a single symbol, frequently found in performer parts. - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + (multiple repeat) – Multiple repeated measures. - - - - - - - - + + + + + + + + - - + + -

    In modern publishing practice, repeats of more than two measures should be written out +

    In modern publishing practice, repeats of more than two measures should be written out using repeat signs. This element, however, is provided for handling non-standard practices - often found in manuscript. The num attribute records the number of measures to be + often found in manuscript. The num attribute records the number of measures to be repeated.

         - + An indication that a passage should be performed one or more octaves above or below its written pitch. - - - - - - - - - - - + + + + + + + + + + + - + - + Must have one of the attributes: startid, tstamp, tstamp.ges or tstamp.real. Must have one of the attributes: @@ -18696,34 +6128,35 @@ -

    The dis and dis.place attributes record the amount and direction of - displacement, respectively. The lform and lwidth attributes capture +

    The dis and dis.place attributes record the amount and direction of + displacement, respectively. The lform and lwidth attributes capture the appearance of the continuation line associated with the octave displacement. The - starting point of the octave displacement may be indicated by either a startid, - tstamp, tstamp.ges, or tstamp.real attribute, while the - ending point may be recorded by either a dur, dur.ges, - endid, or tstamp2 attribute. It is a semantic error not to specify - one starting and one ending type of attribute. Also, note that the dur attribute - is not required because the octave displacement can be visually instantaneous.

    + starting point of the octave displacement may be indicated by either a startid, + tstamp, tstamp.ges, or tstamp.real attribute, while the + ending point may be recorded by either a dur, dur.ges, + endid, or tstamp2 attribute. It is a semantic error not to specify one + starting and one ending type of attribute. Also, note that the dur attribute is + not required because the octave displacement can be visually instantaneous.

         - + (ossia layer) – A layer that contains an alternative to material in another layer. - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + @@ -18736,20 +6169,20 @@ - + Captures original notation and a differently notated version *present in - the source being transcribed*. - - - - - - - - - - - + the source being transcribed*. + + + + + + + + + + + @@ -18768,9 +6201,9 @@ - + - + In a measure, ossia may only contain staff and oStaff elements. @@ -18783,7 +6216,7 @@ -

    The alternative material in an ossia often provides a simpler, easier-to-perform option, +

    The alternative material in an ossia often provides a simpler, easier-to-perform option, while at other times the alternate material provides indications of performance practice, such as ornamentation. Often an ossia is rendered above the main staff on a reduced-size staff. Sometimes the alternate material occurs on the same staff as the primary text, but in @@ -18791,24 +6224,25 @@ notation.

         - + (ossia staff) – A staff that holds an alternative passage which may be played instead of the original material. - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + @@ -18823,49 +6257,49 @@ - + Piano pedal mark. - - - - - - - - - - - - - + + + + + + + + + + + + + - + Must have one of the attributes: startid, tstamp, tstamp.ges or tstamp.real. -

    The starting point of the pedal mark may be indicated by either a startid, - tstamp, tstamp.ges, or tstamp.real attribute. It is a +

    The starting point of the pedal mark may be indicated by either a startid, + tstamp, tstamp.ges, or tstamp.real attribute. It is a semantic error not to specify one of these attributes.

         - + (rehearsal mark) – In an orchestral score and its corresponding parts, a mark indicating a convenient point from which to resume rehearsal after a break. - - - - - - - - - - - - + + + + + + + + + + + + @@ -18874,30 +6308,30 @@ -

    It may also be called a "rehearsal figure", or when numbers are used instead of letters, a +

    It may also be called a "rehearsal figure", or when numbers are used instead of letters, a "rehearsal number". See Read, p. 443. reh uses a subset of model.textPhraseLike.limited.

         - + Indication of 1) a "unified melodic idea" or 2) performance technique. - - - - - - - - - - - + + + + + + + + + + + - + - + Must have one of the attributes: startid, tstamp, tstamp.ges or tstamp.real. Must have one of the attributes: @@ -18905,9 +6339,9 @@ - + - + The visual attributes of the slur (@bezier, @bulge, @curvedir, @lform, @lwidth, @ho, @startho, @endho, @to, @startto, @endto, @vo, @startvo, @endvo, @x, @y, @x2, and @y2) will be overridden by visual attributes of the contained curve @@ -18916,43 +6350,42 @@ -

    Historically, the term "slur" indicated two notes performed legato, while the term "phrase" +

    Historically, the term "slur" indicated two notes performed legato, while the term "phrase" was used for a "unified melodic idea". Nowadays, however, "slur" often has the same meaning as "phrase" (See Read, p. 265-266), since the visual rendition of the two concepts is the same. MEI provides two distinct elements so that those users wishing to maintain a distinction for historical reasons may do so. If the user does not want to maintain the distinction, then the more generic slur element should be employed. - The starting point of the phrase/slur may be indicated by either a startid, - tstamp, tstamp.ges, or tstamp.real attribute, while the - ending point may be recorded by either a dur, dur.ges, - endid, or tstamp2 attribute. It is a semantic error not to specify - one starting and one ending type of attribute. Either place, bulge, or - bezier attributes may be used to record the curvature of the phrase/slur. The - slur and tie elements may be used instead of - the slur.* and tie.* attributes provided on chord and note elements when 1) they are required by software, or 2) multiple, alternative - slurs are needed.

    -     -     - + The starting point of the phrase/slur may be indicated by either a startid, + tstamp, tstamp.ges, or tstamp.real attribute, while the + ending point may be recorded by either a dur, dur.ges, + endid, or tstamp2 attribute. It is a semantic error not to specify one + starting and one ending type of attribute. Either place, bulge, or + bezier attributes may be used to record the curvature of the phrase/slur. The slur and tie elements may be used instead of the + slur.* and tie.* attributes provided on chord and note elements when 1) they are required by software, or 2) multiple, alternative slurs + are needed.

    + +     + An indication that two notes of the same pitch form a single note with their combined rhythmic values. - - - - - - - - - - - + + + + + + + + + + + - + - + Must have one of the attributes: startid, tstamp, tstamp.ges or tstamp.real. Must have one of the attributes: @@ -18960,9 +6393,9 @@ - + - + The visual attributes of the tie (@bezier, @bulge, @curvedir, @lform, @lwidth, @ho, @startho, @endho, @to, @startto, @endto, @vo, @startvo, @endvo, @x, @y, @x2, and @y2) will be overridden by visual attributes of the contained curve @@ -18971,24 +6404,24 @@ -

    Most often, a tie is rendered as a curved line connecting the two notes. See Read, p. +

    Most often, a tie is rendered as a curved line connecting the two notes. See Read, p. 110-111, 122.

         - + A group of notes with "irregular" (sometimes called "irrational") rhythmic values, for example, three notes in the time normally occupied by two or nine in the time of five. - - - - - - - - - - - + + + + + + + + + + + @@ -18998,47 +6431,47 @@ - + - + A tuplet without a copyof attribute must have at least 2 note, rest, or chord descendants. -

    The beam sub-element is allowed so that custom beaming may be +

    The beam sub-element is allowed so that custom beaming may be indicated, e.g., a septuplet may be divided into a group of three plus a group of four notes. See Read, p. 187-215. The tuplet element may also used for bowed tremolo (Read, p. 394) and double, triple, or flutter tonguing (Read, p. 348-349); that is, for repetition of the same pitch. In the case of irrational durations, such as such as two quarter notes in the time of five 8th notes in a measure of 5/8 time, decimal values - may be used in the dur.ges attribute. For example, the dur.ges - attribute would take the value "2.5" if the midi.div attribute's value was "1". - The num and numbase attributes may be used for explicit labelling of a + may be used in the dur.ges attribute. For example, the dur.ges + attribute would take the value "2.5" if the midi.div attribute's value was "1". + The num and numbase attributes may be used for explicit labelling of a tuplet, such as, '3' with an 8th-note triplet, '3:2' over a quarter-note triplet, etc. The - rendering of the ratio, however, is dependent on the num.format attribute found + rendering of the ratio, however, is dependent on the num.format attribute found in the att.vis.tuplet attribute class.

         - + (tuplet span) – Alternative element for encoding tuplets, especially useful for tuplets that extend across bar lines. - - - - - - - - - - - - - + + + + + + + + + + + + + - + Must have one of the attributes: startid, tstamp, tstamp.ges or tstamp.real. Must have one of the attributes: @@ -19047,256 +6480,256 @@ -

    The starting point of the tuplet may be indicated by either a startid, - tstamp, tstamp.ges, or tstamp.real attribute, while the - ending point may be recorded by either a dur, dur.ges, - endid, or tstamp2 attribute. It is a semantic error not to specify - one starting and one ending type of attribute.

    +

    The starting point of the tuplet may be indicated by either a startid, + tstamp, tstamp.ges, or tstamp.real attribute, while the + ending point may be recorded by either a dur, dur.ges, + endid, or tstamp2 attribute. It is a semantic error not to specify one + starting and one ending type of attribute.

         - + CMN ornament component declarations. - + CMN ornam attribute values: A = appogiatura (upper neighbor); a = acciaccatura (lower neighbor); b = bebung; I = ascending slide; i = descending slide; k = delayed turn; K = 5-note turn; m = mordent (alternation with lower neighbor); M = inverted mordent (alternation with upper neighbor); N = Nachschlag (upper neighbor); n = Nachschlag (lower neighbor); S = turn; s = inverted turn; t = trill commencing on auxiliary note; T = trill commencing on principal note; O = generic / unspecified ornament. - - + + [A|a|b|I|i|K|k|M|m|N|n|S|s|T|t|O]|(A|a|S|s|K|k)?(T|t|M|m)(I|i|S|s)? - + Logical domain attributes. - - - - + + + + - - + + Records semantic meaning, i.e., intended performance, of the mordent. The - altsym, glyph.name, or glyph.num attributes may be used + altsym, glyph.name, or glyph.num attributes may be used to specify the appropriate symbol. - - + + Starts with the written note, followed by its lower neighbor, with a return to the written note. In modern practice, this is called an "inverted mordent" and indicated by a short wavy line with a vertical line through it. - + Starts with the written note, followed by its upper neighbor, with a return to the principal note. In modern practice, the symbol lacks the vertical line used for the inverted form. - + When set to 'true', a double or long mordent, sometimes called a "pincé double", consisting of 5 notes, is indicated. - - + + - + Accidentals associated with ornaments. - - + + Records the written accidental associated with an upper neighboring note. - - + + - + Records the written accidental associated with a lower neighboring note. - - + + - + Attributes for marking the presence of an ornament. - - + + Indicates that this element has an attached ornament. If visual information about the ornament is needed, then one of the elements that represents an ornament (mordent, trill, or turn) should be employed. - - + + - + Logical domain attributes. - - - - - - + + + + + + - + Logical domain attributes. - - - - + + + + - - + + When set to 'true', the turn begins on the second half of the beat. - - + + - - Records meaning; i.e., intended performance, of the turn. The altsym, - glyph.name, or glyph.num attributes may be used to specify the + + Records meaning; i.e., intended performance, of the turn. The altsym, + glyph.name, or glyph.num attributes may be used to specify the appropriate symbol. - - + + Begins on the note below the written note. - + Begins on the note above the written note. - + Groups CMN ornament elements. - - + + - + An ornament indicating rapid alternation of the main note with a secondary note, usually a - step below, but sometimes a step above. + step below, but sometimes a step above. - - - - - - - - - - - - - + + + + + + + + + + + + + - + Must have one of the attributes: startid, tstamp, tstamp.ges or tstamp.real. -

    The starting point of the mordent may be indicated by either a startid, - tstamp, tstamp.ges, or tstamp.real attribute. It is a +

    The starting point of the mordent may be indicated by either a startid, + tstamp, tstamp.ges, or tstamp.real attribute. It is a semantic error not to specify one of these attributes.

         - + Rapid alternation of a note with another (usually at the interval of a second above). - - - - - - - - - - - - - + + + + + + + + + + + + + - + Must have one of the attributes: startid, tstamp, tstamp.ges or tstamp.real. -

    The interval between the main and auxiliary notes is usually understood to be diatonic +

    The interval between the main and auxiliary notes is usually understood to be diatonic unless altered by an accidental. The starting note of the trill; i.e., the written one or the ornamenting one, and the speed of alternation depends on performance practice. The - starting point of the trill may be indicated by either a startid, - tstamp, tstamp.ges, or tstamp.real attribute, while the - ending point may be recorded by either a dur, dur.ges, - endid, or tstamp2 attribute. It is a semantic error not to specify a + starting point of the trill may be indicated by either a startid, + tstamp, tstamp.ges, or tstamp.real attribute, while the + ending point may be recorded by either a dur, dur.ges, + endid, or tstamp2 attribute. It is a semantic error not to specify a starting point attribute.

         - + An ornament consisting of four notes — the upper neighbor of the written note, the written note, the lower neighbor, and the written note. - - - - - - - - - - - - - + + + + + + + + + + + + + - + Must have one of the attributes: startid, tstamp, tstamp.ges or tstamp.real. -

    See Read, p. 246-247. Whether the turn is accented or unaccented may be inferred from the +

    See Read, p. 246-247. Whether the turn is accented or unaccented may be inferred from the timestamp — accented turns occur directly on the affected beat, unaccented ones do not.

         - + Corpus component declarations. - + Groups elements that may be document elements when the corpus module is invoked. - + (MEI corpus) – A group of related MEI documents, consisting of a header for the group, and one or more mei elements, each with its own complete header. - - - - - - - - + + + + + + + + -

    This element is modelled on the teiCorpus element in the Text Encoding Initiative (TEI) +

    This element is modelled on the teiCorpus element in the Text Encoding Initiative (TEI) standard. The MEI instances making up the corpus may be related in a number of ways, for example, by composer, by similar instrumentation, by holding institution, etc. This element's name should not be changed in order to assure an absolute minimum level of MEI @@ -19305,112 +6738,88 @@ - + Critical apparatus component declarations. - + Attributes common to all elements representing variant readings. - - - - - - - - + + + + + + + Classifies the cause for the variant reading, according to any appropriate typology of possible origins. - - + + - + Logical domain attributes. - - Attributes common to elements that may refer to a source. - - - Contains a list of one or more pointers indicating the sources which attest to a given - reading. Each value should correspond to the ID of a source element - located in the document header. - - - - - - - @source attribute - should have content. - Each value in @source should correspond to the @xml:id attribute of a source - element. - - - - - - - + Groups elements that contain a critical apparatus entry. - + Groups elements that may appear as part of a textual or musical variant. - + Groups elements that may appear as part of a musical variant. - - + + - + Groups elements that may appear as part of a textual variant. - - + + - + (apparatus) – Contains one or more alternative encodings. - - - + + + - - + + - - + + -

    The alternatives provided in lem and/or rdg - sub-elements may be thought of as exclusive or as parallel. The type attribute +

    The alternatives provided in lem and/or rdg + sub-elements may be thought of as exclusive or as parallel. The type attribute may contain any convenient descriptive word, describing the extent of the variation (e.g. note, phrase, measure, etc.), its text-critical significance (e.g. significant, accidental, unclear), or the nature of the variation or the principles required to understand it (e.g. lectio difficilior, usus auctoris, etc.).

     -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (lemma) – Contains the lemma, or base text, of a textual variation. - - - - - - - - - - - - + + + + + + + + + + + + @@ -19420,6 +6829,9 @@ + + + @@ -19429,36 +6841,36 @@ -

    The lem element may also be used, under some circumstances, to record +

    The lem element may also be used, under some circumstances, to record the base text of the source edition, to mark the readings of a base witness, to indicate the preference of an editor or encoder for a particular reading, or to make clear, in cases of ambiguity, precisely which portion of the main text the variation applies to. Those who prefer to work without the notion of a base text may prefer not to use it at all. An integer indicating the position of this reading in a sequence, when there is reason to presume a - sequence of the variant readings, may be captured in the seq attribute.

    -

    In no case should lem contain elements that would not otherwise be + sequence of the variant readings, may be captured in the seq attribute.

    +

    In no case should lem contain elements that would not otherwise be permitted to occur within the parent of its own app ancestor. For example, when used as a descendent of verse, lem should only contain those elements allowed within verse.

     -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (reading) – Contains a single reading within a textual variation. - - - - - - - - - - - - + + + + + + + + + + + + @@ -19468,6 +6880,9 @@ + + + @@ -19477,82 +6892,82 @@ -

    Since a reading can be a multi-measure section, the scoreDef element +

    Since a reading can be a multi-measure section, the scoreDef element is allowed so that a reading may have its own meta-data without incurring the overhead of child section elements. The app sub-element is permitted in order to allow nested sub-variants.

     -

    In no case should rdg contain elements that would not otherwise be +

    In no case should rdg contain elements that would not otherwise be permitted to occur within the parent of its own app ancestor. For example, when used as a descendent of verse, rdg should only contain those elements allowed within verse.

     -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Dramatic text component declarations. - + Logical domain attributes. - - - - + + + + - + Logical domain attributes. - - - - + + + + - + Groups elements containing stage directions in performance texts. - - - + + + - + (speech) – Contains an individual speech in a performance text. - - - - - - - - - - - - + + + + + + + + + + + + - + - + - + - + @@ -19562,26 +6977,26 @@ - + - + - + - + Must have one of the attributes: startid, tstamp, tstamp.ges or tstamp.real. - + - + Must not have any of the attributes: startid, endid, tstamp, tstamp2, tstamp.ges, tstamp.real, startho, endho, to, startto, endto, staff, layer, place, or plist. @@ -19589,29 +7004,29 @@ -

    In a musical context sp must have a start-type attribute when it's +

    In a musical context sp must have a start-type attribute when it's not a descendant of sp. In a textual content sp must NOT have any musical attributes.

     -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (stage direction) – Contains any kind of stage direction within a dramatic text or fragment. - - - - - - - - - - - - + + + + + + + + + + + + @@ -19620,17 +7035,17 @@ - + - + Must have one of the attributes: startid, tstamp, tstamp.ges or tstamp.real. - + - + Must not have any of the attributes: startid, endid, tstamp, tstamp2, tstamp.ges, tstamp.real, startho, endho, to, startto, endto, staff, layer, place, or plist. @@ -19638,119 +7053,145 @@ -

    In a musical context stageDir must have a start-type attribute when +

    In a musical context stageDir must have a start-type attribute when it's not a descendant of sp. In a textual content stageDir must NOT have any musical attributes.

     -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Editorial and transcriptional component declarations. - + Attributes for the identification of a causative agent. - - + + Signifies the causative agent of damage, illegibility, or other loss of original text. - - + + - + Logical domain attributes. - - - - - - - - - - - - + + + + + + + + + + + + Attributes describing the nature of an encoded scholarly intervention or interpretation. - - - - + + + + + + + Analytical domain attributes. + + + Gestural domain attributes. + + + + + + Logical domain attributes. + + + + + + + + + + Visual domain attributes. + + - + Attributes that identify the reason why an editorial feature is used. - - + + Holds a short phrase describing the reason for missing textual material (gap), why material is supplied (supplied), or why transcription is difficult (unclear). - - + + - + Attributes for elements encoding authorial or scribal intervention when transcribing manuscript or similar sources. - - - + + + + + - + Groups elements that may appear as part of the content of a choice element. - + Groups elements for editorial interventions that may be useful both in transcribing and in authoring processes. - - - + + + - + Groups elements that may appear as part of editorial and transcription elements. - + Groups elements that may appear as part of editorial and transcription elements in music notation. - - + + - + Groups elements that may appear as part of editorial and transcription elements in prose. - - + + - + Groups elements used for editorial transcription of pre-existing source materials. - - + + - + (abbreviation) – A generic element for 1) a shortened form of a word, including an acronym or 2) a shorthand notation. - - - - - - - - - - + + + + + + + + + + @@ -19760,43 +7201,46 @@ + + + - - + + Records the expansion of a text abbreviation. - - + + -

    In no case should abbr contain elements that would not otherwise be +

    In no case should abbr contain elements that would not otherwise be permitted to occur within the parent of its own app ancestor. For example, when used as a descendent of verse, abbr should only contain those elements allowed within verse.

     -

    This element is modelled on an element in the Text Encoding Initiative (TEI) and Encoded +

    This element is modelled on an element in the Text Encoding Initiative (TEI) and Encoded Archival Description (EAD) standards.

         - + (addition) – Marks an addition to the text. - - - - - - - - - - - + + + + + + + + + + + @@ -19813,69 +7257,69 @@ - - + + Location of the addition. - - + + -

    The add element contains material inserted by an author, scribe, +

    The add element contains material inserted by an author, scribe, annotator, or corrector. The agent responsible for the addition may be encoded using the - hand attribute, while the resp attribute records the editor or - transcriber responsible for identifying the hand of the addition. The cert + hand attribute, while the resp attribute records the editor or + transcriber responsible for identifying the hand of the addition. The cert attribute signifies the degree of certainty ascribed to the identification of the hand of the addition. The editor(s) responsible for asserting this particular reading may be - recorded in the resp attribute. The value of resp must point to one or more + recorded in the resp attribute. The value of resp must point to one or more identifiers declared in the document header.

    -

    In no case should add contain elements that would not otherwise be +

    In no case should add contain elements that would not otherwise be permitted to occur within the parent of its own app ancestor. For example, when used as a descendent of verse, add should only contain those elements allowed within verse.

     -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Groups a number of alternative encodings for the same point in a text. - - - + + + - - + + -

    Because the children of a choice element all represent alternative +

    Because the children of a choice element all represent alternative ways of encoding the same sequence, it is natural to think of them as mutually exclusive. However, there may be cases where a full representation of a text requires the alternative encodings to be considered as parallel. Note also that choice elements may be recursively nested.

     -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (correction) – Contains the correct form of an apparent erroneous passage. - - - - - - - - - - - + + + + + + + + + + + @@ -19886,6 +7330,9 @@ + + + @@ -19893,34 +7340,34 @@ -

    The cert attribute signifies the degree of certainty ascribed to correction. The - resp attribute contains an ID reference to an element containing the name of - the editor or transcriber responsible for suggesting the correction held as the content of - the corr element. If the correction was made in the source, resp - should be used to identify the hand of the corrector. The value of resp must point to one or - more identifiers declared in the document header.

    -

    In no case should corr contain elements that would not otherwise be +

    The cert attribute signifies the degree of certainty ascribed to correction. The + resp attribute contains an ID reference to an element containing the name of the + editor or transcriber responsible for suggesting the correction held as the content of the + corr element. If the correction was made in the source, resp should be + used to identify the hand of the corrector. The value of resp must point to one or more + identifiers declared in the document header.

    +

    In no case should corr contain elements that would not otherwise be permitted to occur within the parent of its own app ancestor. For example, when used as a descendent of verse, corr should only contain those elements allowed within verse.

     -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (copy/colla parte mark) – A verbal or graphical indication to copy musical material written elsewhere. - - - - - - - - - - - + + + + + + + + + + + @@ -19929,9 +7376,9 @@ - + - + Must have one of the attributes: startid, tstamp, tstamp.ges or tstamp.real Must have one of the attributes: @@ -19940,53 +7387,52 @@ - + a. b. c. d. e. f. g. - + unis: - + in 8va -

    Typical examples are colla parte instructions (such as "col Basso") or +

    Typical examples are colla parte instructions (such as "col Basso") or other indications intended to result in filling gaps in the score with material written elsewhere. It is recommended to capture the position of the indication itself with the - attributes tstamp and staff. The area to be filled should contain space or mSpace elements. The material to be used - to fill the gap can be identified by the attributes origin.tstamp, - origin.tstamp2, origin.staff, and origin.layer. If - origin.tstamp2 is not provided, a duration similar to that of the local - omission (as encoded in the combination of tstamp and tstamp2) is - assumed. Any missing @origin.* attributes are assumed to take the same values as information - associated with the cpMark. For example, when only the origin.staff attribute is - provided, it is assumed that the referenced part comes from a different staff in the same - measure. If a different measure is provided by origin.tstamp, but no - origin.staff is given, then it is assumed that the material is to be taken from - the same staff.

    -

    Textual instructions are encoded as text content of the cpMark, while graphical - instructions may use the altsym, facs, or extsym + attributes tstamp and staff. The area to be filled should contain space or mSpace elements. The material to be used to + fill the gap can be identified by the attributes origin.tstamp, + origin.tstamp2, origin.staff, and origin.layer. If + origin.tstamp2 is not provided, a duration similar to that of the local omission + (as encoded in the combination of tstamp and tstamp2) is assumed. Any + missing @origin.* attributes are assumed to take the same values as information associated + with the cpMark. For example, when only the origin.staff attribute is provided, + it is assumed that the referenced part comes from a different staff in the same measure. If + a different measure is provided by origin.tstamp, but no origin.staff + is given, then it is assumed that the material is to be taken from the same staff.

    +

    Textual instructions are encoded as text content of the cpMark, while graphical + instructions may use the altsym, facs, or extsym attributes.

         - + Contains an area of damage to the physical medium. - - - - - - - - - - - + + + + + + + + + + + @@ -19997,44 +7443,47 @@ + + + - - + + Records the degree of damage. - - + + -

    In no case should damage contain elements that would not otherwise be +

    In no case should damage contain elements that would not otherwise be permitted to occur within the parent of its own app ancestor. For example, when used as a descendent of verse, damage should only contain those elements allowed within verse.

     -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (deletion) – Contains information deleted, marked as deleted, or otherwise indicated as superfluous or spurious in the copy text by an author, scribe, annotator, or corrector. - - - - - - - - - - - - + + + + + + + + + + + + @@ -20045,6 +7494,9 @@ + + + @@ -20052,35 +7504,35 @@ -

    The resp attribute contains an ID reference to an element containing the name of +

    The resp attribute contains an ID reference to an element containing the name of the editor or transcriber responsible for identifying the hand of the deletion. The - cert attribute signifies the degree of certainty ascribed to the identification + cert attribute signifies the degree of certainty ascribed to the identification of the hand of the deletion. The hand of the agent which made the deletion should be pointed - to using the hand attribute. The rend attribute may be used to record + to using the hand attribute. The rend attribute may be used to record the method used to make the deletion (overstrike, strike[through], etc.).

    -

    In no case should del contain elements that would not otherwise be +

    In no case should del contain elements that would not otherwise be permitted to occur within the parent of its own app ancestor. For example, when used as a descendent of verse, del should only contain those elements allowed within verse.

     -

    This element is modelled on elements in the Text Encoding Initiative (TEI) and Encoded +

    This element is modelled on elements in the Text Encoding Initiative (TEI) and Encoded Archival Description (EAD) standards.

         - + (expansion) – Contains the expansion of an abbreviation. - - - - - - - - - - - + + + + + + + + + + + @@ -20090,94 +7542,96 @@ + + + - - + + Captures the abbreviated form of the text. - - + + -

    In no case should expan contain elements that would not otherwise be +

    In no case should expan contain elements that would not otherwise be permitted to occur within the parent of its own app ancestor. For example, when used as a descendent of verse, expan should only contain those elements allowed within verse.

     -

    This element is modelled on elements in the Text Encoding Initiative (TEI) and Encoded +

    This element is modelled on elements in the Text Encoding Initiative (TEI) and Encoded Archival Description (EAD) standards.

         - + Indicates a point where material has been omitted in a transcription, whether as part of sampling practice or for editorial reasons described in the MEI header. - - - - - - - + + + + + + + - - + + -

    When material is omitted because it is illegible or inaudible, unclear should be used instead. Similarly, use damage if the +

    When material is omitted because it is illegible or inaudible, unclear should be used instead. Similarly, use damage if the omission is due to damage and del if the omission is because the material is marked as deleted, or otherwise indicated as superfluous or spurious in the copy text by an author, scribe, annotator, or corrector. An indication of how much material has - been omitted from the transcription may be recorded in the extent attribute. The - unit attribute names the unit used for describing the extent of the gap. The - reason attribute gives the reason for omission. Sample values include - 'sampling', 'irrelevant', 'cancelled'. The resp attribute contains an ID - reference to an element containing the name of the editor, transcriber or encoder - responsible for the decision not to provide any transcription of the material and hence the - application of the gap tag. The hand attribute signifies - the hand which made the deletion in the case of text omitted from the transcription because - of deliberate deletion by an identifiable hand. The cert attribute signifies the - degree of certainty ascribed to the identification of the extent of the missing - material.

    + been omitted from the transcription may be recorded in the extent attribute. The + unit attribute names the unit used for describing the extent of the gap. The + reason attribute gives the reason for omission. Sample values include 'sampling', + 'irrelevant', 'cancelled'. The resp attribute contains an ID reference to an + element containing the name of the editor, transcriber or encoder responsible for the + decision not to provide any transcription of the material and hence the application of the + gap tag. The hand attribute signifies the hand which made + the deletion in the case of text omitted from the transcription because of deliberate + deletion by an identifiable hand. The cert attribute signifies the degree of + certainty ascribed to the identification of the extent of the missing material.

     -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Marks the beginning of a passage written in a new hand, or of a change in the scribe, writing style, ink or character of the document hand. - - - - - - - - - - - - + + + + + + + + + + + + Describes the character of the new hand. - - + + - + Identifies the new hand. The value must contain the ID of a hand element given elsewhere in the document. - - + + - + - + @new attribute should have content. The value in @new should correspond to the @xml:id attribute of a hand @@ -20186,15 +7640,15 @@ - + Identifies the old hand. The value must contain the ID of a hand element given elsewhere in the document. - - + + - + - + @old attribute should have content. The value in @old should correspond to the @xml:id attribute of a hand @@ -20205,34 +7659,114 @@ -

    The character attribute describes characteristics of the hand, particularly +

    The character attribute describes characteristics of the hand, particularly those related to the quality of the writing, e.g., 'shaky', 'thick', regular'. A description of the tint or type of ink, e.g. 'brown' or the writing medium, e.g. 'pencil', may be placed - in the medium attribute. The new hand may be identified using the new - attribute, while the previous hand may be recorded in the old attribute. The - resp attribute contains an ID reference to an element containing the name of - the editor or transcriber responsible for identifying the change of hand. The - cert attribute signifies the degree of certainty ascribed to the identification - of the new hand.

    -     + in the medium attribute. The new hand may be identified using the new + attribute, while the previous hand may be recorded in the old attribute. The + resp attribute contains an ID reference to an element containing the name of the + editor or transcriber responsible for identifying the change of hand. The cert + attribute signifies the degree of certainty ascribed to the identification of the new + hand.

    + + +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +     +     + + 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. + + + + + + + + + + + + + + + + + + + + + + + + + + Must have one of the + attributes: startid, tstamp, tstamp.ges or tstamp.real + + + + + + Describes the purpose of the metaMark. + + + + + + confirmation of a previous textual decision; i.e., cancellation of a deleted + passage in a different writing medium. + + + denoted material is to be inserted in the musical text. + + + denoted material is no longer part of the musical text. + + + denoted material is replaced, either by the musical text pointed at with the + @target attribute or the musical content of the metaMark element itself. + + + attempt to clarify a potentially illegible or otherwise unclear part of the + musical text. + + + marks a section of the musical text which is to be considered further. + + + marks a section of the musical text as an investigation of the consequences of + certain compositional decisions or potential alternatives. + + + declares a formerly cancelled part of the musical text as valid again. + + + clarification of the reading order of the musical text. + + + + -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is used to encode explicit metatexts as + defined by the Beethovens Werkstatt project.

         - + (original) – Contains material which is marked as following the original, rather than being normalized or corrected. - - - - - - - - - - - + + + + + + + + + + + @@ -20243,6 +7777,9 @@ + + + @@ -20250,33 +7787,33 @@ -

    This element will often be combined with a regularized form within a choice element. The +

    This element will often be combined with a regularized form within a choice element. The editor(s) responsible for asserting that the material is original may be recorded in the - resp attribute. The value of resp must point to one or more identifiers - declared in the document header. The cert attribute signifies the degree of - certainty ascribed to the transcription of the original text.

    -

    In no case should orig contain elements that would not otherwise be + resp attribute. The value of resp must point to one or more identifiers declared + in the document header. The cert attribute signifies the degree of certainty + ascribed to the transcription of the original text.

    +

    In no case should orig contain elements that would not otherwise be permitted to occur within the parent of its own app ancestor. For example, when used as a descendent of verse, orig should only contain those elements allowed within verse.

     -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (regularization) – Contains material which has been regularized or normalized in some sense. - - - - - - - - - - - + + + + + + + + + + + @@ -20287,6 +7824,9 @@ + + + @@ -20294,35 +7834,35 @@ -

    It is possible to identify the individual responsible for the regularization, and, using +

    It is possible to identify the individual responsible for the regularization, and, using the choice and orig elements, to provide both original and regularized readings. The editor(s) responsible for asserting the regularized - material may be recorded in the resp attribute. The value of resp must - point to one or more identifiers declared in the document header. The cert + material may be recorded in the resp attribute. The value of resp must + point to one or more identifiers declared in the document header. The cert attribute signifies the degree of certainty ascribed to the regularized reading.

    -

    In no case should reg contain elements that would not otherwise be +

    In no case should reg contain elements that would not otherwise be permitted to occur within the parent of its own app ancestor. For example, when used as a descendent of verse, reg should only contain those elements allowed within verse.

     -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Indicates restoration of material to an earlier state by cancellation of an editorial or authorial marking or instruction. - - - - - - - - - - - + + + + + + + + + + + @@ -20333,43 +7873,46 @@ + + + - - + + Provides a description of the means of restoration, 'stet' or 'strike-down', for example. - - + + -

    In no case should restore contain elements that would not otherwise +

    In no case should restore contain elements that would not otherwise be permitted to occur within the parent of its own app ancestor. For example, when used as a descendent of verse, restore should only contain those elements allowed within verse.

     -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Contains apparently incorrect or inaccurate material. - - - - - - - - - - - + + + + + + + + + + + @@ -20380,6 +7923,9 @@ + + + @@ -20387,49 +7933,49 @@ -

    A correction for the apparent error may be given in an accompanying child or sibling corr element.

    -

    In no case should sic contain elements that would not otherwise be +

    A correction for the apparent error may be given in an accompanying child or sibling corr element.

    +

    In no case should sic contain elements that would not otherwise be permitted to occur within the parent of its own app ancestor. For example, when used as a descendent of verse, sic should only contain those elements allowed within verse.

     -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (substitution) – Groups transcriptional elements when the combination is to be regarded as a single intervention in the text. - - - - - - - - - + + + + + + + + + -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Contains material supplied by the transcriber or editor for any reason. - - - - - - - - - - - - + + + + + + + + + + + + @@ -20440,6 +7986,9 @@ + + + @@ -20447,41 +7996,41 @@ -

    When the presumed loss of text arises from an identifiable cause, agent signifies the +

    When the presumed loss of text arises from an identifiable cause, agent signifies the causative agent. When the presumed loss of text arises from action (partial deletion, etc.) - assignable to an identifiable hand, the hand attribute signifies the hand - responsible for the action. The reason attribute indicates why the text has to be + assignable to an identifiable hand, the hand attribute signifies the hand + responsible for the action. The reason attribute indicates why the text has to be supplied, e.g. 'overbinding', 'faded ink', 'lost folio', 'omitted in original', etc. The - source attribute contains the source of the supplied text. The editor(s) - responsible for supplied material may be recorded in the resp attribute. The + source attribute contains the source of the supplied text. The editor(s) + responsible for supplied material may be recorded in the resp attribute. The value of resp must point to one or more identifiers declared in the document header. The - cert attribute signifies the degree of certainty ascribed to the supplied + cert attribute signifies the degree of certainty ascribed to the supplied material.

    -

    In no case should supplied contain elements that would not otherwise +

    In no case should supplied contain elements that would not otherwise be permitted to occur within the parent of its own app ancestor. For example, when used as a descendent of verse, supplied should only contain those elements allowed within verse.

     -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Contains material that cannot be transcribed with certainty because it is illegible or inaudible in the source. - - - - - - - - - - - - - - + + + + + + + + + + + + + + @@ -20492,6 +8041,9 @@ + + + @@ -20499,99 +8051,99 @@ -

    Where the difficulty in transcription arises from an identifiable cause, the - agent attribute signifies the causative agent. The cert attribute +

    Where the difficulty in transcription arises from an identifiable cause, the + agent attribute signifies the causative agent. The cert attribute signifies the degree of certainty ascribed to the transcription of the text contained within the unclear element. Where the difficulty in transcription arises from - action (partial deletion, etc.) assignable to an identifiable hand, the hand - attribute signifies the hand responsible for the action. The reason attribute - indicates why the material is difficult to transcribe. The resp attribute + action (partial deletion, etc.) assignable to an identifiable hand, the hand + attribute signifies the hand responsible for the action. The reason attribute + indicates why the material is difficult to transcribe. The resp attribute indicates the individual responsible for the transcription of the word, phrase, or passage - contained with the unclear element. The value of resp must + contained with the unclear element. The value of resp must point to one or more identifiers declared in the document header.

    -

    In no case should unclear contain elements that would not otherwise +

    In no case should unclear contain elements that would not otherwise be permitted to occur within the parent of its own app ancestor. For example, when used as a descendent of verse, unclear should only contain those elements allowed within verse.

     -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + External symbols component declarations. - + Attributes used to associate MEI features with corresponding glyphs in an externally-defined standard such as SMuFL. - - + + A name or label associated with the controlled vocabulary from which the value of - glyph.name or glyph.num is taken. - - + glyph.name or glyph.num is taken. + + - - + + Standard Music Font Layout. - + Glyph name. - - + + - + - + @glyph.name attribute should have content. - + Numeric glyph reference in hexadecimal notation, e.g. "#xE000" or "U+E000". N.B. SMuFL version 1.18 uses the range U+E000 - U+ECBF. - - + + - + - + SMuFL version 1.18 uses the range U+E000 - U+ECBF. - + The web-accessible location of the controlled vocabulary from which the value of - glyph.name or glyph.num is taken. - - + glyph.name or glyph.num is taken. + + - + Facsimile component declarations. - + Attributes that associate a feature corresponding with all or part of an image. - - + + Permits the current element to reference a facsimile surface or image zone which corresponds to it. - - + + - + - + @facs attribute should have content. Each value in @facs should correspond to the @xml:id attribute of a surface or zone @@ -20602,145 +8154,145 @@ - + Contains a representation of a written source in the form of a set of images rather than as transcribed or encoded text. - - - - + + + + - - + + - + -

    The graphic element is provided within facsimile for association of +

    The graphic element is provided within facsimile for association of the facsimile with graphic files capable of representing multiple pages, such as TIFF or PDF formats. When more than one graphic element is used, each must represent the same material. When each page is represented by a different graphic, use a surface element for each page.

    -

    The decls attribute may be used to link the collection of images with a +

    The decls attribute may be used to link the collection of images with a particular source described in the header.

     -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Defines a writing surface in terms of a rectangular coordinate space, optionally grouping one or more graphic representations of that space, and rectangular zones of interest within it. - - - - - - - - - + + + + + + + + + - + - + -

    Scalable Vector Graphics (SVG) markup may be used when allowed by the graphicLike +

    Scalable Vector Graphics (SVG) markup may be used when allowed by the graphicLike model.

    -

    The startid attribute may be used to hold a reference to the first feature +

    The startid attribute may be used to hold a reference to the first feature occurring on this surface.

     -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Defines an area of interest within a surface or graphic file. - - - - + + + + - - + + - + -

    Scalable Vector Graphics (SVG) markup may be used when allowed by the graphicLike +

    Scalable Vector Graphics (SVG) markup may be used when allowed by the graphicLike model.

    -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Figures and tables component declarations. - + Attributes shared by table cells. - - + + The number of columns spanned by this cell. - - + + - + The number of rows spanned by this cell. - - + + - + Groups elements that provide a brief prose description of the appearance or content of a graphic figure. - + Groups elements representing or containing graphic information such as an illustration or figure. - - + + - + Groups elements that indicate the location of an inline graphic, illustration, or figure. - + Groups table-like elements. - - - + + + - + (figure) – Groups elements representing or containing graphic information such as an illustration or figure. - - - - - - - - - - + + + + + + + + + + @@ -20750,20 +8302,20 @@ -

    This element is modelled on the figure element in the Text Encoding Initiative (TEI) +

    This element is modelled on the figure element in the Text Encoding Initiative (TEI) standard.

         - + (figure description) – Contains a brief prose description of the appearance or content of a graphic figure, for use when documenting an image without displaying it. - - - - + + + + - - + + @@ -20778,43 +8330,43 @@ -

    Best practice suggests the use of controlled vocabulary for figure descriptions. Don't +

    Best practice suggests the use of controlled vocabulary for figure descriptions. Don't confuse this entity with a figure caption. A caption is text primarily intended for display with an illustration. It may or may not function as a description of the illustration.

     -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Indicates the location of an inline graphic. - - - - - - - - - - - - - + + + + + + + + + + + + + - + - + Graphic child of zone should not have children. - + Graphic should have either a startid attribute or ulx and uly attributes. - + Graphic should not have @ulx or @uly attributes. Graphic should not have @ho or @vo @@ -20822,61 +8374,61 @@ - - + + Indicates the upper-left corner x coordinate. - - + + - + Indicates the upper-left corner y coordinate. - - + + -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Contains text displayed in tabular form. - - - - - - - - - + + + + + + + + + - + - + -

    This element is modelled on elements in the Encoded Archival Description (EAD), Text +

    This element is modelled on elements in the Encoded Archival Description (EAD), Text Encoding Initiative (TEI), and HTML standards.

         - + (table data) – Designates a table cell that contains data as opposed to a cell that contains column or row heading information. - - - - - - - - - + + + + + + + + + @@ -20887,25 +8439,25 @@ -

    The colspan and rowspan attributes record tabular display rendering +

    The colspan and rowspan attributes record tabular display rendering information.

     -

    This element is modelled on an element in the HTML standard.

    +

    This element is modelled on an element in the HTML standard.

         - + (table header) – Designates a table cell containing column or row heading information as opposed to one containing data. - - - - - - - - - + + + + + + + + + @@ -20916,24 +8468,24 @@ -

    The colspan and rowspan attributes record tabular display rendering +

    The colspan and rowspan attributes record tabular display rendering information.

     -

    This element is modelled on an element in the HTML standard.

    +

    This element is modelled on an element in the HTML standard.

         - + (table row) – A formatting element that contains one or more cells (intersection of a row and a column) in a table. - - - - - - - - + + + + + + + + @@ -20941,70 +8493,70 @@ -

    More precise rendition of the table and its cells can be specified in a style sheet.

    +

    More precise rendition of the table and its cells can be specified in a style sheet.

     -

    This element is modelled on an element in the HTML standard.

    +

    This element is modelled on an element in the HTML standard.

         - + Fingering component declarations. - + Logical domain attributes. - - - - - + + + + + - + Logical domain attributes. - - - - - - - - - - + + + + + + + + + + alternation of fingers. - + combination of fingers. - + substitution of fingers. - + Groups elements that capture performance instructions regarding the use of the fingers of the hand (or a subset of them). - - + + - + finger – An individual finger in a fingering indication. - - - - - - - - - - - + + + + + + + + + + + @@ -21013,37 +8565,37 @@ - + - + Must have one of the attributes: startid, tstamp, tstamp.ges or tstamp.real. - - + + - + The stack element is not allowed as a descendant of fing. - + (finger group)– A group of individual fingers in a fingering indication. - - - - - - - - - - - + + + + + + + + + + + @@ -21051,17 +8603,17 @@ - + - + At least 2 fing or fingGrp elements are required. - + - + When @tstamp or @startid is present on fingGrp, its child elements cannot have a @tstamp or @startid @@ -21077,159 +8629,159 @@ - + FRBR (Functional Requirements for Bibliographic Records) declarations. - + Relationships between FRBR entities. - - - + + + Target is an abridgement, condensation, or expurgation of the current entity. - + Reciprocal relationship of hasAbridgement. - + Target is an adaptation, paraphrase, free translation, variation (music), harmonization (music), or fantasy (music) of the current entity. - + Reciprocal relationship of hasAdaptation. - + Target is an alternate format or simultaneously released edition of the current entity. - + Reciprocal relationship of hasAlternate. - + Target is an arrangement (music) of the current entity. - + Reciprocal relationship of hasArrangement. - + Target is a cadenza, libretto, choreography, ending for unfinished work, incidental music, or musical setting of a text of the current entity. - + Reciprocal relationship of hasComplement. - + Target is a physical embodiment of the current abstract entity; describes the expression-to-manifestation relationship. - + Reciprocal relationship of hasEmbodiment. - + Target is an exemplar of the class of things represented by the current entity; describes the manifestation-to-item relationship. - + Reciprocal relationship of hasExamplar. - + Target is a parody, imitation, or travesty of the current entity. - + Reciprocal relationship of hasImitation. - + Target is a chapter, section, part, etc.; volume of a multivolume manifestation; volume/issue of serial; intellectual part of a multi-part work; illustration for a text; sound aspect of a film; soundtrack for a film on separate medium; soundtrack for a film embedded in film; monograph in a series; physical component of a particular copy; the binding of a book of the current entity. - + Reciprocal relationship of hasPart. - + Target is a realization of the current entity; describes the work-to-expression relationship. - + Reciprocal relationship of hasRealization. - + Target has been reconfigured: bound with, split into, extracted from the current entity. - + Reciprocal relationship of hasReconfiguration. - + Target is a reproduction, microreproduction, macroreproduction, reprint, photo-offset reprint, or facsimile of the current entity. - + Reciprocal relationship of hasReproduction. - + Target is a revised edition, enlarged edition, or new state (graphic) of the current entity. - + Reciprocal relationship of hasRevision. - + Target is a sequel or succeeding work of the current entity. - + Reciprocal relationship of hasSuccessor. - + Target is a digest or abstract of the current entity. - + Reciprocal relationship of hasSummarization. - + Target is an index, concordance, teacher's guide, gloss, supplement, or appendix of the current entity. - + Reciprocal relationship of hasSupplement. - + Target is a dramatization, novelization, versification, or screenplay of the current entity. - + Reciprocal relationship of hasTransformation. - + Target is a literal translation or transcription (music) of the current entity. - + Reciprocal relationship of hasTranslation. - + Collects FRBR expression-like elements. - + Collects FRBR item-like elements. - + Collects FRBR manifestation-like elements. - + Container for intellectual or physical component parts of a bibliographic entity. - - + + - - + + - + @@ -21248,17 +8800,17 @@ - + - + Only child elements of the same name as the parent of the componentList are allowed. - + - + When any child element has a comptype attribute, it is recommended that comptype appear on all child elements. @@ -21266,7 +8818,7 @@ -

    The child elements of this element are treated as components of the bibliographic entity +

    The child elements of this element are treated as components of the bibliographic entity containing the componentList. Although this is an implicit way of expressing FRBR's hasPart and isPartOf relationships, it avoids this terminology in order to prevent confusion with musical terminology. Work, expression, and item components must be @@ -21277,183 +8829,380 @@ (those made up of several physical items.

         - + Intellectual or artistic realization of a work. - - - - - - - - - + + + + + + + + + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + -

    The perfDuration element captures the intended duration +

    The perfDuration element captures the intended duration of the expression, while extent records scope of the expression in other terms, such as number of pages, measures, etc.

         - + Gathers bibliographic expression entities. - - + + - - + + - + - + Single instance or exemplar of a source/manifestation. - - - - - - - - - - - + + + + + + + + + + + - + - + - + - + - + - + - + - + - + - + - + Gathers bibliographic item entities. - - + + - - + + - + + + A bibliographic description of a physical embodiment of an expression of a work. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Item children are not permitted when @singleton + equals "true". + + + + + + + + + + + + + A container for the descriptions of physical embodiments of an expression of a + work. + + + + + + + + + + + + +     + + + Genetic encoding component declarations. + + + Attributes that pertain to a genetic state. + + + + @state attribute should + have content. + The value in @state should correspond to the @xml:id attribute of a genState + element. + + + + + + The @instant attribute is syntactic sugar for classifying a scribal intervention as an + ad-hoc modification; that is, one which does not interrupt the writing process. + + + + unknown + + + + + Points to the genetic state that results from this modification. + + + + + + + + (genetic description) - Bundles information about the textual development of a + work. + + + + + + + + + + + + + + + + When set to "true" the child elements are known to be in chronological order. When set + to "false" or when not provided, the order of child elements is unknown. + + + + + + +

    The development of a work can be traced in one or more sources.

    +

    When the genDesc element is nested, the inner element describes a + group of processes with unknown chronological order inside a larger set of processes with + known order, or vice versa.

    +

    The decls attribute may be used to link the genetic description with a + particular work described in the header.

    +     +     + + Describes a distinctive state in the textual development of a work. + + + + + + + + + + + + + + + + + + + + +

    Any scribal modifications encoded with elements, such as add, del, etc., which refer to a genState element, are regarded as the + operations that need to be implemented to reach this state; that is, they precede this + state.

    +

    When nested inside a genDesc element with ordered set to + "false", information regarding the chronological order of states may be provided using the + next, prev, follows and precedes attributes.

    +

    The date can be used to identify when the current state was + achieved.

    +     +     - + Gestural component declarations. - + Gestural domain attributes. - - + + - + Attributes for capturing momentary pitch inflection in the gestural domain. - - + + Records the performed pitch inflection. - - + + - + - + The value of @accid.ges should not duplicate the value of @accid. @@ -21462,526 +9211,575 @@ - + Gestural domain attributes. - + Gestural domain attributes. - - - - + + + + - + Gestural domain attributes. - + Gestural domain attributes. - - + + - + Attributes describing the method of performance. - - + + Records performed articulation that differs from the written value. - - + + - + Gestural domain attributes. - - + + - + Gestural domain attributes. - + Gestural domain attributes. - + Gestural domain attributes. - - - + + + - + Gestural domain attributes. - + Gestural domain attributes. - - + + - - + + Records the amount of detuning. The decimal values should be rendered as a fraction (or an integer plus a fraction) along with the bend symbol. - - + + - + Gestural domain attributes. - - - + + + - + Gestural domain attributes. - - + + - + Gestural domain attributes. - - + + - + Gestural domain attributes. - - - + + + - + Gestural domain attributes. - - - - - + + + + + - + Gestural domain attributes. - + Gestural domain attributes. - - + + - + Gestural domain attributes. - + Gestural domain attributes. - + Gestural domain attributes. - - - + + + - + Gestural domain attributes. - + Gestural domain attributes. - + Gestural domain attributes. - - + + Indicates that the performance of the next musical division should begin immediately following this one. - - + + - + Gestural domain attributes. - - - + + + - + Gestural domain attributes. - + Attributes that record performed duration that differs from a feature's written duration. - - + + Records performed duration information that differs from the written duration. - - + + - + Number of dots required for a gestural duration when different from that of the written duration. - - + + - + Duration as a count of units provided in the time signature denominator. - - + + \d+(\.\d+)? - + Duration recorded as pulses-per-quarter note, e.g. MIDI clicks or MusicXML divisions. - - + + - + Duration in seconds, e.g. '1.732'. - - + + \d+(\.\d+)? - + Duration as an optionally dotted Humdrum *recip value. - - + + \d+(\.)* - + Gestural domain attributes. - - - - - + + + + + - + Gestural domain attributes. - + Gestural domain attributes. - - - + + - + Gestural domain attributes. - - + + + - + Gestural domain attributes. - - - + + - + Gestural domain attributes. - - - + + + - + Gestural domain attributes. - - + + + - + Gestural domain attributes. - - - + + - + Gestural domain attributes. + + + + - + Gestural domain attributes. - - - - - - - + Gestural domain attributes. - - + + + + + - + Gestural domain attributes. - - - + + - + Gestural domain attributes. - - + + + - + Gestural domain attributes. - - - + + - + Gestural domain attributes. - + Gestural domain attributes. + + + + + - + Gestural domain attributes. - + Gestural domain attributes. - - - - + Gestural domain attributes. - + Gestural domain attributes. - - - + + - + + Gestural domain attributes. + + Attributes for describing the performed components of a line. - - - + + + - + Gestural domain attributes. - - + + + Gestural domain attributes. + + - + Gestural domain attributes. - + Gestural domain attributes. The tstamp.ges and tstamp.real attributes encode the onset time of the measure. In reality, this is usually the same as the onset time of the first event in the measure. - - + + - + Gestural domain attributes. - + Gestural domain attributes. - + Gestural domain attributes. - + Gestural domain attributes. - + Gestural domain attributes. - + Gestural domain attributes. - - - + + + - + Gestural domain attributes. - + Gestural domain attributes. - + Gestural domain attributes. - - - + + + - + Gestural domain attributes. - - - + + + - + + Gestural domain attributes. + + Gestural domain attributes. + + + + + + + + + + + Records performed octave information that differs from the written value. + + + + + + Contains a performed pitch name that differs from the written value. + + + + + + Holds a pitch-to-number mapping, a base-40 or MIDI note number, for example. + + + + + - + Gestural domain attributes. + + + - + Gestural domain attributes. + + + - + Gestural domain attributes. - - - - - - - - - - + + + + + + + + + + - + When the @extremis attribute is used, the @pname.ges and @oct.ges attributes are not allowed. - - + + Indicates an extreme, indefinite performed pitch. - - + + Highest note the performer can play. - + Lowest note the performer can play. -

    On a wind instrument, the "highest note possible" depends on the player's abilities. On +

    On a wind instrument, the "highest note possible" depends on the player's abilities. On a string instrument, the "lowest note possible" depends on how much a string is - de-tuned; that is, loosened using the tuning peg. Use of the pname and - oct or ploc and oloc or loc attributes is + de-tuned; that is, loosened using the tuning peg. Use of the pname and + oct or ploc and oloc or loc attributes is necessary to record the written pitch and octave of the symbol for this note.

         - + Records performed octave information that differs from the written value. - - + + - + Contains a performed pitch name that differs from the written value. - - + + - + Holds a pitch-to-number mapping, a base-40 or MIDI note number, for example. - - + +     - + Gestural domain attributes. - - - + + + - + Gestural domain attributes. - - - + + + Gestural domain attributes. + + + - + Gestural domain attributes. - + Gestural domain attributes. - + Gestural domain attributes. - + Gestural domain attributes. - + Gestural domain attributes. - + Gestural domain attributes. - - + + - + Gestural domain attributes. - - - + + + - + + Gestural domain attributes. + + Gestural domain attributes. - + Gestural domain attributes. - + Gestural domain attributes. - + Gestural domain attributes. - + Gestural domain attributes. - - - - + + + + - + Gestural domain attributes. - + Gestural domain attributes. - + Gestural domain attributes for scoreDef. The values set in these attributes act as score-wide defaults for attributes that are not set in descendant elements. For example, the grace attribute value here applies to all the grace attribute values in the score (or, more @@ -21989,246 +9787,251 @@ individually set each note's grace attribute value. The midi.* attributes function as default values when creating sounding output. The tune.* attributes provide the capability of recording a tuning reference pitch. - - - - - - - - + + + + + + + + Holds the pitch name of a tuning reference pitch. - - + + - + Holds a value for cycles per second, i.e., Hertz, for a tuning reference pitch. - - + + - + Provides an indication of the tuning system, 'just', for example. - - + + - + Gestural domain attributes. - - + + Indicates that the performance of the next section should begin immediately following this one. - - + + - + Gestural domain attributes. - - - + + + Gestural domain attributes. + + + - + + Attributes that locate a sound source within 3-D space. + + + The lateral or left-to-right plane. + + + + +

    A value of 0, 360, or -360 is directly in front of the listener, while a value of 180 + or -180 is directly behind.

    +     +     + + The above-to-below axis. + + + + +

    A value of 0, 360, or -360 is directly above the listener, while a value of 180 or -180 + is directly below.

    +     +     +     +     + Gestural domain attributes. - - + + - + Gestural domain attributes. - - + + - + Gestural domain attributes. - + Gestural domain attributes for staffDef in the CMN repertoire. - - - - + + + + - + Gestural domain attributes. - - + + - + Gestural domain attributes. - - + + - + Gestural domain attributes. - + Gestural domain attributes. - + Gestural domain attributes. - + Gestural domain attributes. - - + + + Gestural domain attributes. + + - + Gestural domain attributes. - - + + - + Attributes that record a performed (as opposed to notated) time stamp. - - + + Encodes the onset time in terms of musical time, i.e., beats[.fractional beat part], as expressed in the written time signature. - - + + - + Records the onset time in terms of ISO time. - - + + - + Attributes that record a performed (as opposed to notated) time stamp for the end of an event. - - + + Encodes the ending point of an event, i.e., a count of measures plus a beat location in the ending measure. - - + + - + Records the ending point of an event in terms of ISO time. - - + + - + Gestural domain attributes. - - - + + + - + Gestural domain attributes. - - + + - + Gestural domain attributes. - - - + + + - + Gestural domain attributes. - + Gestural domain attributes. - + Gestural domain attributes.     - + Harmony component declarations. - + Logical domain attributes. - - - Records the fret position at which the chord tablature is to be played. - - - - - + + + + - + Logical domain attributes. - - + + + - - - Holds the number of the string to be played. - - - - - - Records the location at which a string should be stopped against a fret. - - - - - - Indicates which finger, if any, should be used to play an individual string. The - index, middle, ring, and little fingers are represented by the values 1-4, while 't' is - for the thumb. The values 'x' and 'o' indicate muffled and open strings, - respectively. - - - - - - + Logical domain attributes. - - - - - + + + + + - + Logical domain attributes. - - - - - - - - + + + + + + + + Contains a reference to a chordDef element elsewhere in the document. - - + + - + - + @chordref attribute should have content. The value in @chordref should correspond to the @xml:id attribute of a chordDef @@ -22239,130 +10042,102 @@ - + Groups elements that group playable chord definitions. - + Groups harmonic elements that function as control events; that is, those events that modify or otherwise depend on the existence of notated events. - - + + - + Groups elements that record figured bass. - + Groups elements that represent single figured bass elements. - + Groups elements that record indications of harmony. - - + + - - A barre in a chord tablature grid. - - - - - - - - - - Records the location at which the strings should be stopped against a fret in a - fretboard diagram. This may or may not be the same as the actual location on the fretboard - of the instrument in performance. - - - 1 - 5 - - - - - -

    The startid and endid attributes are used to indicate the chordMember elements on which the barre starts and finishes - respectively. The fret at which the barre should be created is recorded by the - fret attribute.

    -     -     - + (chord definition) – Chord tablature definition. - - - - - - - - - + + + + + + + + + - + -

    An xml:id attribute, while not required by the schema, is needed so that harm elements can reference a particular chord definition. The - pos (position) attribute is provided in order to create displayable chord +

    An xml:id attribute, while not required by the schema, is needed so that harm elements can reference a particular chord definition. The + pos (position) attribute is provided in order to create displayable chord tablature grids. chordMember sub-elements record the individual pitches of the chord. barre sub-elements may be used when a single finger is used to stop multiple strings.

         - + An individual pitch in a chord defined by a chordDef element. - - - - - - + + + + + + - - + + -

    The string, fret, and fing attributes are provided in - order to create displayable chord tablature grids. The inth (harmonic interval) +

    The string, fret, and fing attributes are provided in + order to create displayable chord tablature grids. The inth (harmonic interval) attribute may be used to facilitate automated performance of a chord. It gives the number of - 1/2 steps above the bass. Of course, for the bass note itself, inth should be set + 1/2 steps above the bass. Of course, for the bass note itself, inth should be set to '0'.

         - + Chord/tablature look-up table. - - - + + + - - + + -

    A chordTable may be shared between MEI instances through the use of an external parsed +

    A chordTable may be shared between MEI instances through the use of an external parsed entity containing the look-up table to be shared.

         - + (figure) – Single element of a figured bass indication. - - - - - - - - - - - + + + + + + + + + + + @@ -22372,16 +10147,16 @@ - + (figured bass) – Symbols added to a bass line that indicate harmony. Used to improvise a chordal accompaniment. Sometimes called Generalbass, thoroughbass, or basso continuo. - - - - + + + + - - + + @@ -22390,20 +10165,20 @@ - + (harmony) – An indication of harmony, e.g., chord names, tablature grids, harmonic analysis, figured bass. - - - - - - - - - - - + + + + + + + + + + + @@ -22414,9 +10189,9 @@ - + - + Must have one of the attributes: startid, tstamp, tstamp.ges or tstamp.real. @@ -22425,14 +10200,14 @@     - + Metadata header component declarations. - + Groups elements that may appear as part of a description of the availability of and access to a bibliographic item. - - + + @@ -22454,82 +10229,135 @@ - + Groups manifestation- and item-specific elements that may appear as part of a bibliographic description. - - + + - + - + - + - + - + + Attributes that link a bifolium element with a surface + element. + + + A reference to a surface element positioned on the outer recto + side of a (folded) sheet. + + + + + + A reference to a surface element positioned on the inner verso + side of a (folded) sheet. + + + + + + A reference to a surface element positioned on the inner recto + side of a (folded) sheet. + + + + + + A reference to a surface element positioned on the outer verso + side of a (folded) sheet. + + + + + + + + Attributes that link a folium element with a surface element. + + + A reference to a surface element positioned on the recto side of + the sheet. + + + + + + A reference to a surface element positioned on the verso side of + the sheet. + + + + + + + Attributes that define the characteristics and components of the bibliographic description. - - - - + + + + Language material. - + Notated music. - + Manuscript notated music. - + Non-manuscript cartographic material. - + Manuscript cartographic material. - + Projected medium. - + Nonmusical sound recording. - + Musical sound recording. - + Two-dimensional nonprojectable graphic. - + Computer file. - + Kit. - + Mixed materials. - + Three-dimensional artifact or naturally occurring object. - + Manuscript language material. -

    The recordtype attribute may be used to determine the appropriateness and +

    The recordtype attribute may be used to determine the appropriateness and validity of certain data elements in the description.

    -

    +

    Code Descriptions @@ -22595,107 +10423,115 @@

    - + Attributes that describe correction and normalization methods. - - + + Indicates the method employed to mark corrections and normalizations. - - + + Corrections and normalizations made silently. - + Corrections and normalizations indicated using elements. - + + Collects bifoliumlike elements. + + Groups elements that may appear as part of a description of the editorial process applied to the encoding of notation. - + Groups elements that may appear as part of the description of the encoding process. - + Groups elements that may be used to provide a structured description of an event. - + + Collects foliumlike elements. + + Groups elements that may appear as part of auxiliary material preceding or following the text proper. - + Groups elements that may appear as part of the MEI metadata header. - + + Groups elements dealing with modifications of document pages. + + Groups elements that may appear as part of the physical description of a bibliographic item. - + Groups elements that may appear as part of the publication statement for a bibliographic item. - + Groups elements that may be document elements when the header module is invoked. - + Groups elements that assist in the identification of a work. - + Collects work-like elements. - + (access restriction) – Describes the conditions that affect the accessibility of material. - - - - - - + + + + + + - - + + -

    May indicate the nature of restrictions or the lack of restrictions. Do not confuse this +

    May indicate the nature of restrictions or the lack of restrictions. Do not confuse this element with useRestrict (usage restrictions), which captures information about limitations on the use of material, such as those afforded by copyright.

     -

    This element is modelled on an element in the Encoded Archival Description (EAD) +

    This element is modelled on an element in the Encoded Archival Description (EAD) standard.

         - + Records information concerning the process by which an item was acquired by the holding institution. - - - - - - + + + + + - - + + -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (alternative identifier) – May contain a bibliographic identifier that does not fit within the meiHead element's id attribute, for example because the identifier does not fit the definition of an XML id or because multiple identifiers are needed. - - - + + + - - + + @@ -22704,40 +10540,40 @@ -

    One or the other of altId or the id attribute on mei is required when applicable.

    +

    One or the other of altId or the id attribute on mei is required when applicable.

         - + (application information) – Groups information about applications which have acted upon the MEI file. - - - + + + - - + + - + -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Provides information about an application which has acted upon the current document. - - - + + + - - + + - + @@ -22746,100 +10582,124 @@ - - + + Supplies a version number for an application, independent of its identifier or display name. - - + + -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Documents the usage of a specific attribute of the element. - - - + + + - - + + - + - + @context attribute should contain an XPath expression. - - + + Name of the attribute. - - + + - + Circumstances in which the element appears, an XPath expression. - - + + - + Defines the class of user for which the work is intended, as defined by age group (e.g., children, young adults, adults, etc.), educational level (e.g., primary, secondary, etc.), or other categorization. - - - - - + + + + + - - + + - + Groups elements that describe the availability of and access to a bibliographic item, including an MEI-encoded document. - - - - - - + + + + + + - - + + -

    When used within the fileDesc element, availability indicates access to the MEI-encoded document itself.

    +

    When used within the fileDesc element, availability indicates access to the MEI-encoded document itself.

     -

    This element is modelled on elements in the Text Encoding Initiative (TEI) and Encoded +

    This element is modelled on elements in the Text Encoding Initiative (TEI) and Encoded Archival Description (EAD) standards.

         - + + Describes a folded sheet of paper. + + + + + + + + + + + + + + + + + + + + + + + Contains the primary statement of responsibility given for a work on its title page. - - - - - - - - - + + + + + + + + + @@ -22848,106 +10708,107 @@ - + (capture mode) – The means used to record notation, sound, or images in the production of a source/manifestation (e.g., analogue, acoustic, electric, digital, optical etc.). - - - - - - + + + + + + - - + + - + (carrier form) – The specific class of material to which the physical carrier of the source/manifestation belongs (e.g., sound cassette, videodisc, microfilm cartridge, transparency, etc.). The carrier for a manifestation comprising multiple physical components may include more than one form (e.g., a filmstrip with an accompanying booklet, a separate sound disc carrying the sound track for a film, etc.). - - - - - - + + + + + + - - + + - + Contains an individual descriptive category in a user-defined taxonomy, possibly nested within a superordinate category. - - - - - - - - + + + + + + + + - + - + - + - + - + - + To be addressable, the category element must have an xml:id attribute. - + (category relationship) – Contains the name of a related category. - - - - - - - - - - + + + + + + + + + + + - + - - + + Provides a description of the relationship between the current and the target categories. - - + + Category to which the current category is hierarchically subordinate. - + Category which is hierarchically subordinate to the current category. - + Category that is associatively but not hierarchically linked to the current category. - + Non-preferred category; often a synonym or near-synonym for the preferred category label. @@ -22955,26 +10816,25 @@ - + Individual change within the revision description. - - - - - - - - + + + + + + + - - + + - + - + The date of the change must be recorded in an isodate attribute or date element. It is recommended that the agent responsible for the change be recorded @@ -22984,109 +10844,109 @@ -

    Additions, deletions, and significant recoding should be noted, but not correction of minor +

    Additions, deletions, and significant recoding should be noted, but not correction of minor typographical errors. It is recommended that revisions should be entered in reverse chronological order, with the most recent change first. The - resp attribute contains a pointer to an element containing info about the + resp attribute contains a pointer to an element containing info about the person/entity responsible for change. The edition element can be used to designate an MEI encoding that has been so substantively changed that it constitutes a new version that supersedes earlier versions.

     -

    This element is modelled on an element in the Encoded Archival Description (EAD) +

    This element is modelled on an element in the Encoded Archival Description (EAD) standard.

         - + (change description) – Description of a revision of the MEI file. - - - - + + + + - - + + - + Groups information which describes the nature or topic of an entity. - - - + + + - - + + - + -

    Although the use of names and terms from locally controlled vocabularies is possible, best +

    Although the use of names and terms from locally controlled vocabularies is possible, best practice suggests that terms should come from standard national or international vocabularies whenever they are available in order to enable searches in systems that include multiple MEI documents, or MEI documents and bibliographic records from many institutions.

         - + Groups information which describes the nature or topic of an entity. - - - - + + + + - - + + - + -

    Although the use of names and terms from locally controlled vocabularies is possible, best +

    Although the use of names and terms from locally controlled vocabularies is possible, best practice suggests that terms should come from standard national or international vocabularies whenever they are available in order to enable searches in systems that include multiple MEI documents, or MEI documents and bibliographic records from many institutions.

         - + The physical condition of an item, particularly any variances between the physical make-up of the item and that of other copies of the same item (e.g., missing pages or plates, brittleness, faded images, etc.). - - - - - + + + + + - - + + -

    This element is modelled on an element in the Encoded Archival Description (EAD) +

    This element is modelled on an element in the Encoded Archival Description (EAD) standard.

         - + Contains a single entry within a content description element. - - - - + + + + - - + + - + @@ -23094,19 +10954,19 @@ - + List of the material contained within a resource. - - - - - - - - + + + + + + + + - + @@ -23118,16 +10978,16 @@ - + - + When labels are used, usually each content item has one. - +

    A suitable tone ; Left hand colouring ; Rhythm and accent ; Tempo ; Flexibility ; Ornaments

    @@ -23135,7 +10995,7 @@     - + Contents Sonata in D major, op. V, no. 1 / @@ -23148,84 +11008,160 @@ - + -

    Use this element to provide an enumeration of the contents of a bibliographic entity, like +

    Use this element to provide an enumeration of the contents of a bibliographic entity, like that often found in a table of contents. When a detailed bibliographic description of included material is desired, use the componentList element instead.

         - + The historical, social, intellectual, artistic, or other context within which the work was originally conceived (e.g., the 17th century restoration of the monarchy in England, the aesthetic movement of the late 19th century, etc.) or the historical, social, intellectual, artistic, or other context within which the expression was realized. - - - - - + + + + + - - + + - + States how and under what circumstances corrections have been made in the text. - - - - - - - - - - + + + + + + + + + + - + - - + + Indicates the degree of correction applied to the text. - - + + The text has been thoroughly checked and proofread. - + The text has been checked at least once. - + The text has not been checked. - + The correction status of the text is unknown. -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +     +     + + A cutout is a section of a document sheet that has been removed and is now missing. + + + + + + + + + + + + + + + + + + + + Describes the position of the cutout on the parent folium / bifolium. + + + removed from outer recto side of bifolium. + + + removed from inner verso side of bifolium. + + + removed from inner recto side of bifolium. + + + removed from outer verso side of bifolium. + + + removed from recto side of folium. + + + removed from verso side of folium. + + + + + Describes the method of removing the cutout. + + + + + + section is cleanly cut by a knife, scissor or other sharp blade. + + + section is ripped off the page, leaving a rough edge. + + + + + +

    The dimensions (@width, @height) of the parent element (e.g. folium) + indicate the size of the bounding box of the remaining part of the page. That is, if the + complete lower half of a page has been cut, the @width and @height attributes describe the + remaining upper half. If, in contrast, only the lower right quarter of the page has been + cut, these attributes still indicate the size of the full page (assuming that the removed + section was a regular rectangle).

    +     + +

    The dimensions (@width, @height) on cutout itself are only to be used + when there is a "gap" in the manuscript that allows to specify the dimensions of that + missing part. In this case, the bounding box dimensions are given, together with @x and @y + to indicate the upper left point on the original page. If, however, the removed section is + available by itself, then a corresponding folium (or bifolium) should be placed inside the cutout element, and should + provide it's own dimensions using @width and @height there. In this case, @width and @height + on cutout is expendable.

         - + Contains a dedicatory statement. - - - - - - - - - + + + + + + + + + @@ -23243,47 +11179,47 @@ -

    This element uses a variant of the content model provided by +

    This element uses a variant of the content model provided by macro.struc-unstrucContent.

         - + (domains declaration) – Indicates which domains are included in the encoding. - - - + + + - - - - + + + + - - - + + + - - - + + + - + (edition statement) – Container for meta-data pertaining to a particular edition of the material being described. - - - - + + + + - - + + - + @@ -23294,25 +11230,25 @@ -

    This element is modelled on elements in the Text Encoding Initiative (TEI) and Encoded +

    This element is modelled on elements in the Text Encoding Initiative (TEI) and Encoded Archival Description (EAD) standards.

         - + (editorial declaration) – Used to provide details of editorial principles and practices applied during the encoding of musical text. - - - - - - - - - + + + + + + + + + - + @@ -23327,74 +11263,74 @@ -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (encoding description) – Documents the relationship between an electronic file and the source or sources from which it was derived as well as applications used in the encoding/editing process. - - - - + + + + - - + + - + - + - + - + - + - + - + -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (exhibition history) – A record of public exhibitions, including dates, venues, etc. - - - - - + + + + + - - + + -

    This element is modelled on an element in the Encoded Archival Description (EAD) +

    This element is modelled on an element in the Encoded Archival Description (EAD) standard.

         - + (extended metadata) – Provides a container element for non-MEI metadata formats. - - - - + + + + - - + + @@ -23404,150 +11340,193 @@ - + (file characteristics) – Standards or schemes used to encode the file (e.g., ASCII, SGML, etc.), physical characteristics of the file (e.g., recording density, parity, blocking, etc.), and other characteristics that have a bearing on how the file can be processed. - - - - - + + + + + - - + + - + (file description) – Contains a full bibliographic description of the MEI file. - - - + + + - - - + + + - + - - + + - + - + -

    Extent in this context represents file size.

    +

    Extent in this context represents file size.

     -

    This element is modelled on elements in the Text Encoding Initiative (TEI) and Encoded +

    This element is modelled on elements in the Text Encoding Initiative (TEI) and Encoded Archival Description (EAD) standards.

         - + Contains a string that uniquely identifies an item, such as those constructed by combining groups of characters transcribed from specified pages of a printed item or a file's checksum. - - - - - - - + + + + + + + + + + + + + Describes the order of folia and bifolia making up the text block of a manuscript or + print. + + + + + + + + + + + + + + + + + + +

    The purpose of foliaDesc is to transcribe the addition and removal of + pages as part of physical modifications to a document. Missing pages may be indicated using + the gap element. The folium and bifolium children describe the physical order of surface + elements provided elsewhere.

    +     +     + + Describes a single leaf of paper. + + + + + + - - + + + + + +

    When the exact folium setup can't be identified, it is advised to use folium elements only (and not guess about the presence of bifoliums in the document).

    +     - + Defines a distinct scribe or handwriting style. - - - - - - - - - + + + + + + + + + - - + + Marks this hand as the first one of the document. - - + + -

    The initial attribute indicates whether this is the first or main scribe of the - document. The medium attribute describes the writing medium, e.g., 'pencil', or - the tint or type of ink, e.g. 'brown'. The resp attribute contains an ID +

    The initial attribute indicates whether this is the first or main hand of the + document. The medium attribute describes the writing medium, e.g., 'pencil', or + the tint or type of ink, e.g. 'brown'. The resp attribute contains an ID reference to an element containing the name of the editor or transcriber responsible for identifying the hand. The characteristics of the hand, particularly those related to the quality of the writing, such as 'shaky', 'thick', etc. may be described within the content of the hand element.

    -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Container for one or more hand elements. - - - - + + + + - - + + - + - + - + When labels are used, usually each hand has one. -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Provides a container for information about the history of a resource other than the circumstances of its creation. - - - - + + + - - + + - + @@ -23556,74 +11535,74 @@ - + - + The acquisition and provenance elements are not permitted in the work or expression context. -

    To facilitate efficient data interchange, basic information about the circumstances +

    To facilitate efficient data interchange, basic information about the circumstances surrounding the creation of bibliographic resources should be recorded within the creation element, while the record of ownership and custody should be captured within the history element.

         - + Incipit coded in a non-XML, plain text format, such as Plaine & Easie Code. - - - - - - + + + + + + - - + + - + - + incipCode must have a form or mimetype attribute. - - + + Form of the encoded incipit. - - + + - - + + Plaine & Easie Code. - + Humdrum Kern format. - + Parsons code. - + Opening words of a musical composition. - - - - - - - - - + + + + + + + + + - + @@ -23631,77 +11610,77 @@ - + An inscription added to an item, such as a bookplate, a note designating the item as a gift, and/or the author's signature. - - - - - + + + + + - - + + - + Describes the scope of any analytic or interpretive information added to the transcription of the music. - - - - - - - - - + + + + + + + + + - + -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Key captures information about tonal center and mode. - - - - - - - - - - - - + + + + + + + + + + + + Indicates major, minor, or other tonality. - - + + -

    This element is used exclusively within bibliographic descriptions. Do not confuse this +

    This element is used exclusively within bibliographic descriptions. Do not confuse this element with keySig, which is used within the body of an MEI file to record this data.

         - + Description of a language used in the document. - - - - - - - - + + + + + + + + @@ -23709,94 +11688,98 @@ -

    A textual element may be related to this element by setting its xml:lang +

    A textual element may be related to this element by setting its xml:lang attribute, which normally takes the form of a code drawn from a coded list, such as ISO639-2b, to the same value as this element's codedval attribute. The name and web location - of the authorizing list may be encoded in the auth attribute and the - auth.uri attribute, respectively.

    + of the authorizing list may be encoded in the auth attribute and the + auth.uri attribute, respectively.

     -

    This element is modelled on elements in the Text Encoding Initiative (TEI) and Encoded +

    This element is modelled on elements in the Text Encoding Initiative (TEI) and Encoded Archival Description (EAD) standards.

         - + (language usage) – Groups elements describing the languages, sub-languages, dialects, etc., represented within the encoded resource. - - - - + + + + - - + + - + -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (MEI header) – Supplies the descriptive and declarative metadata prefixed to every MEI-conformant text. - - - - - - - - - - + + + + + + + + + + + - - + + - - + + + + + - + - + - + - + The meiHead type attribute can have the value 'music' only when the document element is "mei". - + The meiHead type attribute can have the value 'corpus' only when the document element is "meiCorpus". - + The meiHead type attribute can have the value 'independent' only when the document element is "meiHead". - - + + Specifies the kind of document to which the header is attached, for example whether it is a corpus or individual text. - - + + Header is attached to a music document. - + Header is attached to a corpus. - + Header is independent; i.e., not attached to either a music or a corpus document. @@ -23804,59 +11787,59 @@ -

    In order to encourage uniformity in the provision of metadata across document types, this +

    In order to encourage uniformity in the provision of metadata across document types, this element is modelled on an element in the Text Encoding Initiative (TEI) standard. This information is often essential in a machine-readable environment. Five sub-elements must be - encoded in the following order: altId(optional), fileDesc(required), encodingDesc(optional), workDesc(optional), and revisionDesc(optional). These elements + encoded in the following order: altId(optional), fileDesc(required), encodingDesc(optional), workList(optional), and revisionDesc(optional). These elements and their sub-elements provide: a unique identifier for the MEI file, bibliographic information about the MEI file and its sources, information about the encoding process, information about the creation of the work being encoded, and statements regarding - significant revisions of the file. The xml:lang attribute may be used to indicate + significant revisions of the file. The xml:lang attribute may be used to indicate the language in which the metadata content of the header is provided.

         - + Captures information about mensuration within bibliographic descriptions. - - - - - - + + + + + + - - + + - + Captures information about the time signature within bibliographic descriptions. - - - - - - + + + + + + - - + + -

    This element is used exclusively within bibliographic descriptions. Do not confuse meter with the meterSig or meterSigGrp or attributes used by staffDef and scoreDef to record this data within - the body of an MEI file.

    +

    This element is used exclusively within bibliographic descriptions. Do not confuse meter with the meterSig or meterSigGrp or attributes used by staffDef and scoreDef to record this data within the + body of an MEI file.

         - + Supplies the formal name of the namespace to which the elements documented by its children belong. - - - + + + - - + + - + @@ -23865,145 +11848,225 @@ - - + + Formal namespace identifier; that is, a uniform resource identifier (URI). - - + + - + Prefix associated with the formal identifier. - - + + -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Indicates the extent of normalization or regularization of the original source carried out in converting it to electronic form. - - - - - - - - - - + + + + + + + + + + - + -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (notes statement)– Collects any notes providing information about a text additional to that recorded in other parts of the bibliographic description. - - - + + + - - + + - + -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (other distinguishing characteristic) – Any characteristic that serves to differentiate a work or expression from another. - - - - - - - + + + + + + + + + + + Describes a physical writing surface attached to the original document. + + + + + + + + + + + + + + + + + The allowed positions of a patch depend on its parent element. + A patch element must contain either a folium + or a bifolium element. + + + + + + Describes the position of the patch on the parent folium / bifolium. + + + patch attached to outer recto side of bifolium. + + + patch attached to inner verso side of bifolium. + + + patch attached to inner recto side of bifolium. + + + patch attached to outer verso side of bifolium. + + + patch attached to recto side of folium. + + + patch attached to verso side of folium. + + + + + Describes the method of attachment of the patch. + + + + + + patch is glued on surface beneath. + + + patch is sewn on surface beneath. + + + patch is pinned to the surface beneath. + + + patch is taped on surface beneath using an adhesive strip. + + + patch is attached on surface beneath using a staple. + + + + + +

    A patch must always contain a folium or bifolium element. The @x and @y attributes are used to position the patch on its + parent surface by indicating the upper left corner of the patch. The size of the patch is + encoded using the @height and @width attributes on the child folium (or bifolium).

    +     +     - + (performance duration) – Used to express the duration of performance of printed or manuscript music or the playing time for a sound recording, videorecording, etc. - - - - - - - - - - - - - - + + + + + + + + + + + + + + Holds a W3C duration value, e.g., "PT2H34M45.67S". - - + + -

    +

    - + (performance medium) – Indicates the number and character of the performing forces used in a musical composition. - - - - - - - - + + + + + + + + - + - + - + -

    Arrangements are coded for the medium of the work being described, not for the original +

    Arrangements are coded for the medium of the work being described, not for the original medium.

         - + (performance resource) – Name of an instrument on which a performer plays, a performer's voice range, or a standard performing ensemble designation. - - - - - - - - - + + + + + + + + + @@ -24011,36 +12074,36 @@ - - + + Indicates the number of performers. - - + + - + Marks this instrument or vocal part as a soloist. Do not use this attribute for a solo instrument which is not accompanied. - - + + - + Several instrumental or vocal resources treated as a group. - - - - - - - - - + + + + + + + + + - + @@ -24048,221 +12111,178 @@ - - + + Indicates the number of performers. - - + + -

    The function of instrumentalists or vocalists is represented by the choice of perfRes and perfResList child elements. - Arrangements are coded for the medium of the work being described, not for the original - medium.

    +

    The function of instrumentalists or vocalists is represented by the choice of perfRes and perfResList child elements. Arrangements + are coded for the medium of the work being described, not for the original medium.

         - + (physical description) – Container for information about the appearance, construction, or handling of physical materials, such as their dimension, quantity, color, style, and technique of creation. - - - + + + - - + + - + - + -

    Dedicatory text and title page features may also be encoded here when they are not +

    Dedicatory text and title page features may also be encoded here when they are not transcribed as part of the front or back matter; i.e., when they are considered to be meta-data rather than a transcription.

     -

    This element is modelled on an element in the Encoded Archival Description (EAD) +

    This element is modelled on an element in the Encoded Archival Description (EAD) standard.

         - + (physical medium) – Records the physical materials used in the source, such as ink and paper. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + -

    All materials may be described in a single physMedium element or +

    All materials may be described in a single physMedium element or multiple elements may be used, one for each medium.

     -

    This element is modelled on elements in the Encoded Archival Description (EAD) +

    This element is modelled on elements in the Encoded Archival Description (EAD) standard. It + has the same function as the material element in the Text Encoding Initiative (TEI) standard.

         - + (plate number) – Designation assigned to a resource by a music publisher, usually printed at the bottom of each page, and sometimes appearing also on the title page. - - - - - - - + + + + + + + - - + + -

    While it is often called a "plate number", it does not always contain numbers. The - facs attribute may be used to record the location of the plate number in a +

    While it is often called a "plate number", it does not always contain numbers. The + facs attribute may be used to record the location of the plate number in a facsimile image.

         - + Playing speed for a sound recording is the speed at which the carrier must be operated to produce the sound intended (e.g., 33 1/3 rpm, 19 cm/s, etc.). - - - - - + + + + + - - + + - + The cost of access to a bibliographic item. - - - - - - - - + + + + + + + + - + - - + + Numeric value capturing a cost. Can only be interpreted in combination with the currency attribute. - - + + [0-9]+\.[0-9]{2} - + Monetary unit. - - + + -

    Best practice suggests the use of controlled vocabulary for the currency attribute, such as +

    Best practice suggests the use of controlled vocabulary for the currency attribute, such as the ISO 4217 list of currency designators.

         - + (project description) – Project-level meta-data describing the aim or purpose for which the electronic file was encoded, funding agencies, etc. together with any other relevant information concerning the process by which it was assembled or collected. - - - - - - - - - + + + + + + + + + - + -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + The record of ownership or custodianship of an item. - - - - - - - - + + + + + + + + @@ -24283,23 +12303,23 @@ -

    This element is modelled on elements in the Encoded Archival Description (EAD) and Text +

    This element is modelled on elements in the Encoded Archival Description (EAD) and Text Encoding Initiative (TEI) standards.

         - + (publication statement) – Container for information regarding the publication or distribution of a bibliographic item, including the publisher's name and address, the date of publication, and other relevant details. - - - + + + - - + + - + @@ -24309,114 +12329,114 @@ -

    When an item is unpublished, use only the unpub sub-element.

    +

    When an item is unpublished, use only the unpub sub-element.

     -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (revision description) – Container for information about alterations that have been made to an MEI file. - - - + + + - - + + - + -

    It is recommended that changes be recorded in reverse chronological order, with the most +

    It is recommended that changes be recorded in reverse chronological order, with the most recent alteration first.

     -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (sampling declaration) – Contains a prose description of the rationale and methods used in sampling texts in the creation of a corpus or collection. - - - - - - - - - + + + + + + + + + - + -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Describes the type of score used to represent a musical composition (e.g., short score, full score, condensed score, close score, etc.). - - - - - - + + + + + + - - + + - + Describes the principles according to which the musical text has been segmented, for example into movements, sections, etc. - - - - - - - - - + + + + + + + + + - + -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (series statement) – Groups information about the series, if any, to which a publication belongs. - - - + + + - - + + - + - + - + @@ -24426,296 +12446,259 @@ -

    The title sub-element records the series title, the respStmt element records the person or group responsible for the series, and the identifier element contains a series identifier. The contents element should be used when it is necessary to enumerate the content of the +

    The title sub-element records the series title, the respStmt element records the person or group responsible for the series, and the identifier element contains a series identifier. The contents element should be used when it is necessary to enumerate the content of the series, but not describe each component. The seriesStmt element is provided within seriesStmt for the description of a sub-series.

     -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (sound channels) – Reflects the number of apparent sound channels in the playback of a recording (monaural, stereophonic, quadraphonic, etc.). - - - - - - - - - + + + + + + + + + - - + + Records the channel configuration in numeric form. - - + + -

    The number of apparent playback channels can differ from the number of physical channels of +

    The number of apparent playback channels can differ from the number of physical channels of the recording medium, i.e., 2-track monophonic recordings. In this example, the soundChan element should record the fact that there is a single output channel, while the trackConfig element should capture the existence of two physical tracks. This element is analogous to MARC field 344 subfield g.

         - - A bibliographic description of a source used in the creation of the electronic file or the - physical embodiment of an expression of a work. - - - - - - - - - - - - - + + A bibliographic description of a source used in the creation of the electronic + file. + + + + + + + + + + + + - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + - + - + @target attribute should have content. - The value in @target should correspond to the @xml:id attribute of a source - element. + Each value in @target should correspond to the @xml:id attribute of a source or + manifestation element or be an external URI. -

    In the file description context, this element contains, or references via its - target attribute, a description of a source used in the creation of the - electronic file. In the context of a work or expression description, it contains, or - references, a description of a physical embodiment of an expression of a work; i.e., a - manifestation.

    -

    The data attribute may be used to reference one or more musical features found +

    This element contains, or references via its target attribute, a description of + a source used in the creation of the electronic file. For description of a physical + embodiment of an expression of a work use the manifestation + element.

    +

    The data attribute may be used to reference one or more musical features found in the content of this particular source.

     -

    This element is modelled on elements in the Text Encoding Initiative (TEI) and Encoded +

    This element is modelled on elements in the Text Encoding Initiative (TEI) and Encoded Archival Description (EAD) standards.

         - + (source description) – A container for the descriptions of the source(s) used in the creation of the electronic file. - - + + - - + + - + -

    This element is recommended where the MEI file is a transcription of existing music, but is +

    This element is recommended where the MEI file is a transcription of existing music, but is not required when the data is originally created in MEI form.

         - + (special reproduction characteristic) – The equalization system, noise reduction system, etc. used in making the recording (e.g., NAB, DBX, Dolby, etc.). - - - - - - + + + + + + - - + + - + (standard values) – Specifies the format used when standardized date or number values are supplied. - - - - - - - - - + + + + + + + + + - + -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (system requirements) – System requirements for using the electronic item. - - - - - + + + + + - - + + - + (tagging declaration) – Provides detailed information about the tagging applied to a document. - - - + + + - - + + - + - + -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Documents the usage of a specific element within the document. - - - + + + - - + + - + - + - + @context attribute should contain an XPath expression. - - + + Name of the element. - - + + - + Circumstances in which the element appears, an XPath expression. - - + + - + Number of occurrences in the defined context. - - + + - - Number of occurrences in the defined context that have an xml:id + + Number of occurrences in the defined context that have an xml:id attribute. - - + + -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Defines a typology either implicitly, by means of a bibliographic citation, or explicitly by a structured taxonomy. - - - + + + - - + + - + - + - + @@ -24723,83 +12706,83 @@ - + Collection of text phrases which describe a resource. - - - - + + + + - - + + - + - + - + When labels are used, usually each term has one. -

    An external taxonomy from which all the descendant term elements are - drawn may be referred to using the target attribute.

    +

    An external taxonomy from which all the descendant term elements are + drawn may be referred to using the target attribute.

         - + (title statement) – Container for title and responsibility meta-data. - - - + + + - - + + - + - + -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (track configuration) – Number of physical/input tracks on a sound medium (e.g., eight track, twelve track). - - - - - - - - - - - - + + + + + + + + + + + + Records the track configuration in numeric form. - - + + -

    The number of apparent playback channels can differ from the number of physical channels of +

    The number of apparent playback channels can differ from the number of physical channels of the recording medium, i.e., 2-track monophonic recordings. In this example, the trackConfig element should record the fact that there are two physical tracks on the sound medium, while the soundChan element should be used to state that there is a single @@ -24807,255 +12790,254 @@ appropriate.

         - + (treatment history) – A record of the treatment the item has undergone (e.g., de-acidification, restoration, etc.). - - - - - + + + + + - - + + -

    Treatment history may also comprise details of the treatment process (e.g., chemical +

    Treatment history may also comprise details of the treatment process (e.g., chemical solutions used, techniques applied, etc.), the date the treatment was applied, etc.

     -

    This element is modelled on an element in the Encoded Archival Description (EAD) +

    This element is modelled on an element in the Encoded Archival Description (EAD) standard.

         - + (treatment scheduled) – Scheduled treatment, e.g. de-acidification, restoration, etc., for an item. - - - - - + + + + + - - + + -

    This element is modelled on an element in the Encoded Archival Description (EAD) +

    This element is modelled on an element in the Encoded Archival Description (EAD) standard.

         - + (unpublished) – Used to explicitly indicate that a bibliographic resource is unpublished. - - - - + + + + - - + + -

    A short phrase indicating the nature of or the reason for the unpublished status may be +

    A short phrase indicating the nature of or the reason for the unpublished status may be given as the element's content.

         - + (usage restrictions) – Container for information about the conditions that affect use of a bibliographic item after access has been granted. - - - - - - + + + + + + - - + + -

    - useRestrict may indicate limitations imposed by an owner, repository, - or legal statute (for example, copyright law) regarding the reproduction, publication, or - quotation of the item. It may also indicate the absence of restrictions, such as when rights - have been ceded to the public domain. Do not confuse this element with the accessRestrict element, which holds information about conditions affecting the - availability of the material.

    +

    useRestrict may indicate limitations imposed by an owner, + repository, or legal statute (for example, copyright law) regarding the reproduction, + publication, or quotation of the item. It may also indicate the absence of restrictions, + such as when rights have been ceded to the public domain. Do not confuse this element with + the accessRestrict element, which holds information about conditions + affecting the availability of the material.

     -

    This element is modelled on an element in the Encoded Archival Description (EAD) +

    This element is modelled on an element in the Encoded Archival Description (EAD) standard.

         - + Contains a description of a watermark or similar device. - - - - - - - - + + + + + + + - - + + -

    The facs attribute may be used to record the location of the watermark in a +

    The facs attribute may be used to record the location of the watermark in a facsimile image.

     -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Provides a detailed description of a work — a distinct intellectual or artistic creation — specifically its history, language use, and high-level musical attributes (e.g., key, tempo, meter, medium of performance, and intended duration). - - - - - - - - - - - + + + + + + + + + + + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + -

    The perfDuration element captures the intended duration +

    The perfDuration element captures the intended duration of the work.

         - - (work description) – Grouping mechanism for information describing non-bibliographic - aspects of a text. - - - + + (work list) – Grouping mechanism for information describing non-bibliographic aspects of a + text. + + + - - + + - +     - + Lyrics component declarations. - + Logical domain attributes. - - - - + + + + - + Logical domain attributes. The n attribute should be used for verse numbers. Numbers need not be consecutive; they may also be expressed as ranges, e.g. 2-3,6. - + Logical domain attributes. The n attribute should be used for verse numbers. Numbers need not be consecutive; they may also be expressed as ranges, e.g. 2-3,6. - + Logical domain attributes. The n attribute should be used for repetition numbers. Numbers need not be consecutive; they may also be expressed as ranges, e.g. 2-3,6. - + Groups elements that contain a lyric verse. - - - - + + + + - + Recurring lyrics, especially at the end of each verse or stanza of a poem or song lyrics; a chorus. - - - - - - - - - - - - + + + + + + + + + + + + @@ -25063,38 +13045,44 @@ - + - + -

    The lb element is allowed here in order to facilitate karaoke - applications. The func attribute on lb may be used to +

    The lb element is allowed here in order to facilitate karaoke + applications. The func attribute on lb may be used to distinguish true line endings from those of line groups for these applications.

         - + Division of a poem or song lyrics, sometimes having a fixed length, meter or rhyme scheme; a stanza. - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + @@ -25102,38 +13090,38 @@ - + - + -

    The lb element is allowed here in order to facilitate karaoke - applications. The func attribute on lb may be used to +

    The lb element is allowed here in order to facilitate karaoke + applications. The func attribute on lb may be used to distinguish true line endings from those of line groups for these applications.

         - - - - - - - - - - - - - - - + + Sung text for a specific iteration of a repeated section of music. + + + + + + + + + + + + + @@ -25141,75 +13129,79 @@ - + - + + +

    The volta element is intended for those cases where the musical notation is repeated, but + the accompanying lyrics are not.

    +     - + Mensural repertoire component declarations. - + Logical, that is, written, duration attribute values for the mensural repertoire. - - - + + + Two or three times as long as a longa. - + Two or three times as long as a brevis. - + Two times as long as a semibreve. - + Half or one-third as long as a breve/brevis. - + Half or one-third as long as a semibreve/semibrevis. - + Half or one-third as long as a minima. - + Half or one-third as long as a semiminima. - + Half or one-third as long as a fusa. - + Items in the Mensural repertoire that may be printed near a staff. - - - + + + Ligatures. - + Logical domain attributes. - - + + Provides an indication of the function of the ligature. - - + + - + Used by staffDef and scoreDef to provide default values for attributes in the logical domain related to mensuration. The tempus, prolatio, modusmaior, and modusminor attributes (from the att.mensural.shared class) specify the relationship between the four principle @@ -25218,192 +13210,192 @@ and prolatio the semibreve-minim relationship, respectively. Modusmaior is for the maxima-long relationship. The proport.* attributes describe augmentation or diminution of the normal value of the notes in mensural notation. - - + + - - + + Determines if a dot is to be added to the base symbol. - - + + - + The base symbol in the mensuration sign/time signature of mensural notation. - - + + - + Indicates the number lines added to the mensuration sign. For example, one slash is added for what we now call 'alla breve'. - - + + - + Together, proport.num and proport.numbase specify a proportional change as a ratio, e.g., 1:3. Proport.num is for the first value in the ratio. - - + + - + Together, proport.num and proport.numbase specify a proportional change as a ratio, e.g., 1:3. Proport.numbase is for the second value in the ratio. - - + + - + Shared attributes in the mensural repertoire. - - + + Describes the maxima-long relationship. - - + + - + Describes the long-breve relationship. - - + + - + Describes the semibreve-minim relationship. - - + + - + Describes the breve-semibreve relationship. - - + + - + Analytical domain attributes in the Mensural repertoire. - - + + Indicates this element's participation in a ligature. - - - + + + - + Gestural domain attributes. - - + + - + Logical domain attributes in the Mensural repertoire. - + Logical domain attributes. These attributes describe augmentation or diminution of the normal value of the notes in mensural notation as a ratio. - - + + - + Gestural domain attributes. - - + + - + Visual domain attributes. - - + + States how many spaces are covered by the rest. - - + + - + Logical domain attributes for a score in the mensural repertoire. The values set in these attributes act as score-wide defaults for attributes that are not set in descendant elements. - - + + - + Visual domain attributes for scoreDef in the mensural repertoire. - - + + - + Logical domain attributes for staffDef in the mensural repertoire. - - + + - + Visual domain attributes for the mensural repertoire. - - + + - + Groups event elements that occur in the mensural repertoire. - - + + - + Groups notated events that may appear at the layer level in the mensural repertoire. - - + + - + Groups elements that may appear as part of a score in the mensural repertoire. - + Groups elements that may appear as part of a section in the mensural repertoire. - - + + - + Groups elements that may appear in the declaration of staff features. - - + + - + Groups elements that are components of a staff in the mensural repertoire. - - + + - + A mensural notation symbol that combines two or more notes into a single sign. - - - - - - - - - - - + + + + + + + + + + + @@ -25415,53 +13407,53 @@ -

    The rhythmic meaning of the components of a ligature is typically contextual, not absolute; +

    The rhythmic meaning of the components of a ligature is typically contextual, not absolute; therefore, an interpretative duration may be encoded on each of the components using either - the dur.ges attribute or the num and numbase attribute + the dur.ges attribute or the num and numbase attribute pair. The ligature element should not be used for brackets in modern notation that indicate notes that were part of a ligature in the original source.

         - + (mensuration) – Collects information about the metrical relationship between a note value and the next smaller value; that is, either triple or duple. - - - - - - - - - - - - - - -

    The mensur element is provided for the encoding of mensural notation. - The slash attribute indicates the number lines added to the mensuration sign. For + + + + + + + + + + + + + + +

    The mensur element is provided for the encoding of mensural notation. + The slash attribute indicates the number lines added to the mensuration sign. For example, one slash is added for what we now call 'alla breve'.

         - + (proportion) – Description of note duration as arithmetic ratio. - - - - - - - - - + + + + + + + + + - - + + -

    The proport element is provided for the encoding of mensural notation. It allows the +

    The proport element is provided for the encoding of mensural notation. It allows the description of note durations as arithmetic ratios. While mensuration refers to the normal relationships between note durations, proportion affects the relations of the note durations to the tactus.

    @@ -25469,53 +13461,53 @@     - + MIDI component declarations. - + Attributes that record MIDI channel information. - - + + Records a MIDI channel value. - - + + - + Specifies the 'on' part of the duty cycle as a percentage of a note's duration. - - + + - + Sets the MIDI port value. - - + + - + Sets the MIDI track. - - + + - + Logical domain attributes. - + Attributes which identify a MIDI instrument. - - + + Provides a way of pointing to a MIDI instrument definition. It must contain the ID of an instrDef element elsewhere in the document. - - + + - + - + @instr attribute should have content. The value in @instr should correspond to the @xml:id attribute of an instrDef @@ -25526,305 +13518,307 @@ - + Attributes common to MIDI events. - - - - - - + + + + + + - + Logical domain attributes. - - - - + + + + - + Attributes that record MIDI instrument information. - + - + Only one of @midi.instrname and @midi.instrnum allowed. - + - + Only one of @midi.patchname and @midi.patchnum allowed. - - - Captures the General MIDI instrument number. - - + + + Captures the General MIDI instrument number. Use an integer for a 0-based value. An + integer preceded by "in" indicates a 1-based value. + + - + Provides a General MIDI label for the MIDI instrument. - - + + - - Sets the instrument's position in a stereo field. Values of 0 and 1 both pan left, 127 - pans right, and 64 pans to the center. - - + + Sets the instrument's position in a stereo field. MIDI values of 0 and 1 both pan + left, 127 or 128 pans right, and 63 or 64 pans to the center. Positve percentage values + pan to the right, negative ones to the left. 0% is centered. + + - + Records a non-General MIDI patch/instrument name. - - + + - + Records a non-General MIDI patch/instrument number. - - + + - + Sets the instrument's volume. - - + + - + Attributes that record MIDI numbers. - - + + MIDI number in the range set by data.MIDIVALUE. - - + + - + Attributes that record MIDI tempo information. - - + + Captures the number of *quarter notes* per minute. In MIDI, a beat is always defined as a quarter note, *not the numerator of the time signature or the metronomic indication*. - - + + - + Records the number of microseconds per *quarter note*. In MIDI, a beat is always defined as a quarter note, *not the numerator of the time signature or the metronomic indication*. At 120 quarter notes per minute, each quarter note will last 500,000 microseconds. - - + + - + Attributes that record MIDI values. - - + + MIDI number. - - + + - + Attributes that record terminal MIDI values. - - + + MIDI number. - - + + - + MIDI attributes pertaining to key velocity. - - + + MIDI Note-on/off velocity. - - + + - + Attributes that record time-base information. - - + + Indicates the number of pulses (sometimes referred to as ticks or divisions) per quarter note. Unlike MIDI, MEI permits different values for a score and individual staves. - - + + - + Groups elements which group MIDI-like elements. - - - - + + + + - + (control change) – MIDI parameter/control change. - - - - - + + + + + - - + + -

    The num attribute specifies a MIDI parameter number, while val +

    The num attribute specifies a MIDI parameter number, while val contains the parameter value. Each must fall in the range 0-127.

         - + (channel) – MIDI channel assignment. - - - + + + - - + + - - + + MIDI number in the range set by data.MIDICHANNEL. - - + + - + (channel pressure) – MIDI channel pressure/after touch. - - - - + + + + - - + + -

    The value of the num attribute must be in the range 0-127.

    +

    The value of the num attribute must be in the range 0-127.

         - + MIDI cue point. - - - - + + + + - - + + - + Arbitrary MIDI data in hexadecimal form. - - - + + + - - + + -

    The element's content must be wrapped in a CDATA section to avoid parsing errors.

    +

    The element's content must be wrapped in a CDATA section to avoid parsing errors.

         - + (instrument definition) – MIDI instrument declaration. - - - - - - - + + + + + + + - - + + -

    This element provides a starting or default instrument declaration for a staff, a group of +

    This element provides a starting or default instrument declaration for a staff, a group of staves, or a layer. Following scoreDef, staffDef, layerDef, or MIDI prog elements may then change the instrument as necessary.

         - + (instrument group) – Collects MIDI instrument definitions. - - + + - - + + - + MIDI marker meta-event. - - - - + + + + - - + + - + MIDI text meta-event. - - - - + + + + - - + + - + Container for elements that contain information useful when generating MIDI output. - - - - - - - - - - + + + + + + + + + + @@ -25844,103 +13838,103 @@ -

    The label attribute can be used to differentiate between multiple MIDI data +

    The label attribute can be used to differentiate between multiple MIDI data streams, e.g. quantized/unquantized, straight/swing, ornamented/as notated, etc.

         - + MIDI note-off event. - - - - + + + + - - + + - + MIDI note-on event. - - - - + + + + - - + + - + MIDI port. - - - - + + + + - - + + - + (program) – MIDI program change. - - - - + + + + - - + + - + (sequence number) – MIDI sequence number. - - - + + + - - + + - - + + Number in the range 0-65535. - - + + 65535 - + (track name) – MIDI track/sequence name. - - - - + + + + - - + + - + (velocity) – MIDI Note-on/off velocity. - - - - + + + + - - + + - - + + Indicates whether this is note-on or note-off velocity data. - - + + Note-on velocity. - + Note-off velocity. @@ -25948,147 +13942,134 @@     - - - Metadata header component declarations. + + + Manuscript description component declarations. - + Attributes that express the relationship between a component and its host. - - - + + + - + The comptype attribute may occur on - only when it is a descendant of a + only when it is a descendant of a componentList. - - + + A physical and logical part of entity. - + A physical, but not logical component of the entity, usually included as part of the binding process. - + A logical component of the entity physically held elsewhere. - + Groups elements that may appear inline when the msdesc module is active. - - + + - + Holds a description of any additional material bound with an item, such as non-contemporaneous documents or fragments. - - - - - - + + + + + - - + + -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (addition description) – Provides a description of significant additions found within an item, such as marginalia or other annotations. - - - - - + + + + + - - + + -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (binding) – Contains a description of one binding, i.e. type of covering, boards, etc. applied to an item. - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + - - - - + + + + -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (binding description) – Describes the present and former bindings of an item. - - - - - - - - + + + + + + + + + + + - + + + + + + + + - - - - - - - - - - - - @@ -26099,71 +14080,68 @@ -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Describes the system used to ensure correct ordering of the quires making up an item, typically by means of annotations at the foot of the page. - - - - - - - + + + + + + - - + + -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Records a description of how the leaves or bifolia of an item are physically arranged. - - - - - + + + + - - + + -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Contains a statement providing information regarding the date, place, agency, or reason for production of the item. - - - - - - - + + + + + + - - + + -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (decoration description) – Contains a description of the decoration of an item. - - - - - - - - + + + + + + + + @@ -26185,20 +14163,19 @@ -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (decoration note) – Contains a description of one or more decorative features of an item. - - - - - - - - + + + + + + + @@ -26220,204 +14197,174 @@ -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Contains the explicit of a manuscript item; that is, the closing words of the text proper, exclusive of any rubric or colophon which might follow it. - - - - - - - + + + + + + - - + + -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Describes the numbering system or systems used to count the leaves or pages in a codex. - - - - - + + + + - - + + -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Contains a heraldic formula or phrase, typically found as part of a blazon, coat of arms, etc. - - - - - - - - + + + + + + + - - + + -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - - Contains the opening words of the text proper, exclusive of any rubric which might precede - it, of sufficient length to identify the work uniquely. - - - - - - - - - - - - -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    -

    Incipits were, in former times, frequently used as a means of reference to a work, in place - of a title.

    -     -     - + Describes how text is laid out on the page, including information about any ruling, pricking, or other evidence of page-preparation techniques. - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + - - + + Specifies the number of columns per page. - + -

    A single number indicates that all pages have this number of columns. Two numbers mean +

    A single number indicates that all pages have this number of columns. Two numbers mean that the number of columns per page varies between the values supplied.

         - + Specifies the number of ruled text lines per column. - + -

    A single number indicates that all columns have this number of ruled lines. Two +

    A single number indicates that all columns have this number of ruled lines. Two numbers mean that the number of text lines per column varies between the values supplied.

         - + Specifies the number of written text lines per column. - + -

    A single number indicates that all columns have this number of written text lines. Two +

    A single number indicates that all columns have this number of written text lines. Two numbers mean that the number of text lines per column varies between the values supplied.

         - + Specifies the number of ruled staves per column. - + -

    A single number indicates that all columns have this number of ruled staves. Two +

    A single number indicates that all columns have this number of ruled staves. Two numbers mean that the number of ruled staves per column varies between the values supplied.

         - + Specifies the number of written staves per column. - + -

    A single number indicates that all columns have this number of written staves. Two +

    A single number indicates that all columns have this number of written staves. Two numbers mean that the number of written staves per column varies between the values supplied.

         -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (layout description) – Collects layout descriptions. - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Defines a location within a manuscript or manuscript component, usually as a (possibly discontinuous) sequence of folio references. - - - - - - - - - + + + + + + + + @@ -26426,121 +14373,102 @@ - - + + Identifies the foliation scheme in terms of which the location is being specified by pointing to some foliation element defining it, or to some other equivalent resource. - - + + - + Specifies the starting point of the location in a normalized form. - - + + - + Specifies the end-point of the location in a normalized form. - - + + -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (locus group) – Groups locations which together form a distinct but discontinuous item within a manuscript or manuscript part, according to a specific foliation. - - - - - - - - - + + + + + + + + - - + + Identifies the foliation scheme in terms of which the location is being specified by pointing to some foliation element defining it, or to some other equivalent resource. - - + + -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    -     -     - - Contains a word or phrase describing the material of which the object being described is - composed. - - - - - - - - - - - -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Contains a string of words through which a manuscript signals the beginning or end of a text division, often with an assertion as to its author and title, which is in some way set off from the text itself, usually in red ink, or by use of different size or type of script, or some other such visual device. - - - - - - - - - - - - - - - + + + + + + + + + + + + + + Signals beginning of a text division. - + Makrs the end of a text division. -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (script description) – Contains a description of the letters or characters used in an autographic item. - - - - - - - - + + + + + + + + @@ -26561,36 +14489,34 @@ -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (script note) – Describes a particular script distinguished within the description of an autographic item. - - - - - + + + + - - + + -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + A single seal or similar attachment. - - - - - - - - - + + + + + + + + @@ -26611,42 +14537,44 @@ - - - - + + + + -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (seal description) – Describes the seals or similar external attachments applied to an item. - - - - - - - - + + + + + + + + - - - - - - - + + - - + + + + + + + + + @@ -26657,110 +14585,97 @@ -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (second folio) – Marks the word or words taken from a fixed point in a codex (typically the beginning of the second leaf) in order to provide a unique identifier for the item. - - - - - - - - + + + + + + + - - + + -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Provides a description of the leaf or quire signatures found within a codex. - - - - - - - + + + + + + - - + + -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Contains a word or phrase describing an official mark indicating ownership, genuineness, validity, etc. - - - - - - - - - + + + + + + + + - - + + -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Provides a description of the physical support material of a written item. - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (support description) – Groups elements describing the physical support material of an item. - - - - - - - - + + + + + + + + @@ -26793,41 +14708,41 @@ - - + + Short, project-defined name for the material composing the majority of the support. - - + + - - - Paper + + + Paper. - + Parchment. - + Mixed materials. -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (type description) – Contains a description of the typefaces or other aspects of the printing of a printed source. - - - - - - - - + + + + + + + + @@ -26848,37 +14763,36 @@ -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (type note) – Describes a particular font or other significant typographic feature of a printed resource. - - - - - + + + + - - + + -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + - + The element may only appear as a descendant of the physDesc element. - + - - The element may only appear as a descendant of a physDesc element, a + + The element may only appear as a descendant of a physDesc element, a contentItem element, or a source element that is a component of another source or work. @@ -26886,64 +14800,64 @@     - + Names and dates component declarations. - + Groups elements used as part of a physical address. - - + + - + Groups elements which form part of a geographic name. - - + + - + Groups elements which contain names of individuals or corporate bodies. - - - + + + - + Groups geographic name elements. - - - + + + - + Groups elements that serve as stylistic labels. - - + + - + Groups place name elements. - - + + - + Groups elements which form part of a personal name. - + (additional name) – Contains an additional name component, such as a nickname, epithet, or alias, or any other descriptive phrase used within a personal name. - - - - - - - - - - - + + + + + + + + + + + @@ -26953,23 +14867,23 @@ -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Contains the name of a geopolitical unit consisting of two or more nation states or countries. - - - - - - - - - - - + + + + + + + + + + + @@ -26979,23 +14893,23 @@ -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (corporate name) – Identifies an organization or group of people that acts as a single entity. - - - - - - - - - - - + + + + + + + + + + + @@ -27005,33 +14919,33 @@ -

    Examples of corporate entities include names of associations, institutions, business firms, +

    Examples of corporate entities include names of associations, institutions, business firms, non-profit enterprises, governments, government agencies, projects, programs, religious bodies, churches, conferences, athletic contests, exhibitions, expeditions, fairs, and ships. Usually, secondary name parts are encoded in corpName sub-elements. The name of the list from which a controlled value is taken may be recorded - using the auth attribute.

    + using the auth attribute.

     -

    This element is modelled on an element in the Encoded Archival Description (EAD) +

    This element is modelled on an element in the Encoded Archival Description (EAD) standard.

         - + Contains the name of a geopolitical unit, such as a nation, country, colony, or commonwealth, larger than or administratively superior to a region and smaller than a bloc. - - - - - - - - - - - + + + + + + + + + + + @@ -27041,23 +14955,23 @@ -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Contains the name of any kind of subdivision of a settlement, such as a parish, ward, or other administrative or geographic unit. - - - - - - - - - - - + + + + + + + + + + + @@ -27067,23 +14981,23 @@ -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (family name) – Contains a family (inherited) name, as opposed to a given, baptismal, or nick name. - - - - - - - - - - - + + + + + + + + + + + @@ -27094,19 +15008,19 @@ - + Contains a forename, given or baptismal name. - - - - - - - - - - - + + + + + + + + + + + @@ -27116,23 +15030,23 @@ -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (generational name component) – Contains a name component used to distinguish otherwise similar names on the basis of the relative ages or generations of the persons named. - - - - - - - - - - - + + + + + + + + + + + @@ -27142,23 +15056,23 @@ -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (geographical feature name) – Contains a common noun identifying a geographical feature. - - - - - - - - - - - + + + + + + + + + + + @@ -27168,23 +15082,23 @@ -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (geographic name) – The proper noun designation for a place, natural feature, or political jurisdiction. - - - - - - - - - - - + + + + + + + + + + + @@ -27194,32 +15108,33 @@ -

    Examples include Black Forest; Baltimore, Maryland; and Quartier Latin, Paris. Geographic +

    Examples include Black Forest; Baltimore, Maryland; and Quartier Latin, Paris. Geographic name parts can be encoded using geogName sub-elements. For greater specificity, however, use district, settlement, - region, country, and bloc sub-elements. The name of the list from which a controlled value is taken, such - as the Thesaurus of Geographic Names (TGN), may be recorded using the auth + region, country, and bloc + sub-elements. The name of the list from which a controlled value is taken, such as the + Thesaurus of Geographic Names (TGN), may be recorded using the auth attribute.

     -

    This element is modelled on an element in the Encoded Archival Description (EAD) +

    This element is modelled on an element in the Encoded Archival Description (EAD) standard.

         - + (name link) – Contains a connecting phrase or link used within a name but not regarded as part of it, such as "van der" or "of", "from", etc. - - - - - - - - - - - + + + + + + + + + + + @@ -27229,23 +15144,23 @@ -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (period name) – A label that describes a period of time, such as 'Baroque' or '3rd Style period'. - - - - - - - - - - - + + + + + + + + + + + @@ -27255,24 +15170,24 @@ -

    The name of the list from which a controlled value is taken may be recorded using the - auth attribute.

    +

    The name of the list from which a controlled value is taken may be recorded using the + auth attribute.

         - + (personal name) – Designation for an individual, including any or all of that individual's forenames, surnames, honorific titles, and added names. - - - - - - - - - - - + + + + + + + + + + + @@ -27283,27 +15198,27 @@ -

    Parts of a personal name may be captured using persName sub-elements. +

    Parts of a personal name may be captured using persName sub-elements. For greater specificity, however, use foreName, famName, genName, addName, genName, nameLink, and roleName elements. The name of the list from which a controlled value for - persName is taken may be recorded using the auth attribute.

    + persName is taken may be recorded using the auth attribute.

     -

    This element is modelled on an element in the Encoded Archival Description (EAD) +

    This element is modelled on an element in the Encoded Archival Description (EAD) standard.

         - + (postal box or post office box) contains a number or other identifier for some postal delivery point other than a street address. - - - - - - - - + + + + + + + + @@ -27312,20 +15227,20 @@ -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (postal code) contains a numerical or alphanumeric code used as part of a postal address to simplify sorting or delivery of mail. - - - - - - - - + + + + + + + + @@ -27334,23 +15249,23 @@ -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Contains the name of an administrative unit such as a state, province, or county, larger than a settlement, but smaller than a country. - - - - - - - - - - - + + + + + + + + + + + @@ -27360,23 +15275,23 @@ -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (role name) – Contains a name component which indicates that the referent has a particular role or position in society, such as an official title or rank. - - - - - - - - - - - + + + + + + + + + + + @@ -27386,23 +15301,23 @@ -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Contains the name of a settlement such as a city, town, or village identified as a single geopolitical or administrative unit. - - - - - - - - - - - + + + + + + + + + + + @@ -27412,20 +15327,20 @@ -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + full street address including any name or number identifying a building as well as the name of the street or route on which it is located. - - - - - - - - + + + + + + + + @@ -27435,23 +15350,23 @@ -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (style name) – A label for a characteristic style of writing or performance, such as 'bebop' or 'rock-n-roll'. - - - - - - - - - - - + + + + + + + + + + + @@ -27461,133 +15376,506 @@ -

    Do not confuse this element with the periodName element. The name of - the list from which a controlled value is taken may be recorded using the auth +

    Do not confuse this element with the periodName element. The name of + the list from which a controlled value is taken may be recorded using the auth attribute.

         - + Neume repertoire component declarations. - - Groups elements that modify neume-like features. - - - - - + Items in the Neume repertoire that may be printed near a staff. - + + Logical domain attributes. + + + + + + + + + + + + Logical domain attributes. + + + + + + + + + + + + Logical domain attributes. + + + Logical domain attributes. + + + + + + + + + + Captures written octave information. + + + + 9 + + + unknown + + + + + + Contains a written pitch name. + + + [a-g]|unknown + + + + + + + Attributes that record visual details of neume notation. + + + + + + + + + Connection to the previous component within the same neume; this attribute should not + be used for the first component of a neume. + + + Gapped; not connected. + + + Looped. + + + Extended. + + + + + Records direction of curvature. + + + Anti-clockwise curvature. + + + Clockwise curvature. + + + + + Pen stroke has an extension; specific to Hispanic notation. + + + + + + Indicates participation in a ligature. + + + + + + Length of the pen stroke relative to the previous component within the same neume; + this attribute should not be used for the first component of a neume. + + + Longer. + + + Shorter. + + + + + Direction of the initial direction for an s-shaped pen stroke; i.e., "w" for the + standard letter S, "e" for its mirror image, "s" for the letter S turned 90-degrees + anti-clockwise, and "n" for its mirror image. + + + + + + Direction of the pen stroke. + + + + + + + Logical domain attributes. - - + + + + + + - + + Logical domain attributes. + + + + + + + + + + Logical domain attributes. + + + Logical domain attributes. + + Logical domain attributes. - - - + + + + + + + + - + + Logical domain attributes. + + Logical domain attributes. - - + + - + Groups event elements that occur in the neume repertoire. - - - + + + - + Groups notated events that may appear at the layer level in the neume repertoire. - - + + - + + Groups elements that modify neume components. + + + Groups elements that modify neume-like features. + + + Groups elements that may occur within a neume. + + Groups elements that may appear as part of a score in the neume repertoire. - + Groups elements that may appear as part of a section in the neume repertoire. - - + + - + Groups elements that are components of a staff in the neume repertoire. - - + + - + Groups elements that accommodate neumed text. - - + + - + Groups elements that may appear as part of the content of a syllable. - + + Episema. + + + + + + + + + + + + Hispanic tick. + + + + + + + + + + + + + + + Liquescent. + + + + + + + + + + + Sign representing a single pitched event, although the exact pitch may not be known. - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + Designation which characterizes the element in some sense, using any convenient + classification scheme or typology that employs single-token labels. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Collection of one or more neume components. + + + + + + + + - - + + + + + + + + + + + - + Sign representing one or more musical pitches. - - - - - - - - - - - + + + + + + + + + + + + + + + + - - + + + + + + + + + Designation which characterizes the element in some sense, using any convenient + classification scheme or typology that employs single-token labels. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Oriscus. + + + + + + + + + + + + Quilisma. + + + + + + + + + + + + Significantive letter(s). + + + + + + + + + + + + + + + + - - + + Strophicus. + + + + + + + + + + + Neume notation can be thought of as "neumed text". Therefore, the syllable element provides high-level organization in this repertoire. - - - - - - - - - - + + + + + + + + + + + @@ -27595,7 +15883,7 @@ - + @@ -27607,14 +15895,14 @@ - + Performance component declarations. - + Temporal alignment attributes. - + - + @when attribute should have content. A @@ -27623,175 +15911,175 @@ - - + + Indicates the point of occurrence of this feature along a time line. Its value must be the ID of a when element elsewhere in the document. - - + + - + (audio/video file) – References an external digital audio or video file. - - - - - - - - - - + + + + + + + + + + - + - + An avFile child of clip cannot have children. -

    This element is analogous to the graphic element in the figtable +

    This element is analogous to the graphic element in the figtable module.

         - + Defines a time segment of interest within a recording or within a digital audio or video file. - - - - - - - - - + + + + + + + + + - + - + - + When @begin or @end is used, @betype should appear on clip or one of its ancestors. -

    This element is analogous to the zone element in the facsimile +

    This element is analogous to the zone element in the facsimile module.

         - + A presentation of one or more musical works. - - - - + + + + - - + + -

    The decls attribute may be used to link the collection with a particular source +

    The decls attribute may be used to link the collection with a particular source described in the header. This element is analogous to the facsimile element in the facsimile module.

         - + A recorded performance. - - - - - - - - - + + + + + + + + + - + - + - + - + When @begin or @end is used, @betype should be present. -

    The startid attribute may be used to hold a reference to the first feature +

    The startid attribute may be used to hold a reference to the first feature occurring in this performance. This element is analogous to the surface element in the facsimile module.

         - + Indicates a point in time either absolutely (using the absolute attribute), or relative to another when element (using the since, interval and inttype attributes). - - - + + + - - + + - + - + @since must be present when @interval is used. The value in @since should correspond to the @xml:id attribute of a when element. - + When @interval contains an integer value, @inttype cannot be 'time'. - + When @interval contains a time value, @inttype must be 'time'. - + - + When @absolute is present, @abstype should be present or @betype should be present on an ancestor. - - + + Provides an absolute value for the time point. - - + + - + Specifies the time interval between this time point and the one designated by the since attribute. This attribute can only be interpreted meaningfully in conjunction with the inttype attribute. - - + + 1 @@ -27799,30 +16087,30 @@ - + Specifies the kind of values used in the absolute attribute. - - + + - + Specifies the kind of values used in the interval attribute. - - + + - + Identifies the reference point for determining the time of the current when element, which is obtained by adding the interval to the time of the reference point. The value should be the ID of another when element within the same parent element. If the since attribute is omitted and the absolute attribute is not specified, then the reference point is understood to be the immediately preceding when element. - - + + - + - + @since attribute should have content. The value in @since should correspond to the @xml:id attribute of a when @@ -27833,61 +16121,61 @@ -

    The data attribute may be used to reference one or more features that occur at +

    The data attribute may be used to reference one or more features that occur at this point in time.

     -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Pointer and reference component declarations. - + Groups elements used for purposes of location and reference. - - + + - + (pointer) – Defines a traversible pointer to another location, using only attributes to describe the destination. - - - - - - - + + + + + + + - - + + -

    Unlike the ref element, ptr cannot contain text +

    Unlike the ref element, ptr cannot contain text or sub-elements to describe the referenced object.

     -

    This element is modelled on elements in the Encoded Archival Description (EAD) and Text +

    This element is modelled on elements in the Encoded Archival Description (EAD) and Text Encoding Initiative (TEI) standards.

         - + (reference) – Defines a traversible reference to another location. May contain text and sub-elements that describe the destination. - - - - - - - - - - - + + + + + + + + + + + @@ -27895,23 +16183,23 @@ -

    Unlike the ptr element, ref may contain text +

    Unlike the ptr element, ref may contain text and sub-elements to describe the destination.

     -

    This element is modelled on elements in the Encoded Archival Description (EAD) and TEI +

    This element is modelled on elements in the Encoded Archival Description (EAD) and TEI standards.

         - + Component declarations that are shared between two or more modules. - + Permits any XML elements except those from the MEI or SVG namespace. - - + + @@ -27932,41 +16220,41 @@ - + Groups elements that contain meta-data about a single page. - - + + - + - + - + Groups elements that may appear as part of the music element. - - + + - + - + - + Provides a choice between structured and unstructured/mixed content. - - + + @@ -27984,10 +16272,10 @@ - + Groups elements that may appear as part of a bibliographic title. - - + + @@ -28009,175 +16297,173 @@ - + Datatypes for values in begin, end, abstype and inttype attributes. - - - + + + Bytes. - + Synchronized Multimedia Integration Language. - + MIDI clicks. - + MIDI machine code. - + MIDI time code. - + SMPTE 25 EBU. - + SMPTE 24 Film Sync. - + SMPTE 30 Drop. - + SMPTE 30 Non-Drop. - + SMPTE 29.97 Drop. - + SMPTE 29.97 Non-Drop. - + AES Time-code character format. - + ISO 24-hour time format: HH:MM:SS.ss. - + Logical domain attributes. - - - + + + - - + + Records the function of an accidental. - - + + Cautionary accidental. - + Editorial accidental. - + Attributes for capturing momentary pitch inflection. - - + + Captures a written accidental. - - + + - + Analytical domain attributes. - - + + - + Gestural domain attributes. - + Logical domain attributes. - + Visual domain attributes. - + Logical domain attributes. - - - - - + + + + + - + Analytical domain attributes. - + Gestural domain attributes. - + Visual domain attributes. - - - + + + - + Logical domain attributes for annot. Values for the type attribute can be taken from any convenient typology of annotation suitable to the work in hand; e.g. annotation, gloss, citation, digression, preliminary, temporary, etc. - - - - - - - - - - - - - + + + + + + + + + + + + + Logical domain attributes. - - - + + + - + Attributes for capturing the written signs that describe the method of performance. - - + + Encodes the written articulation(s). Articulations are normally encoded in order from the note head outward; that is, away from the stem. See additional notes at att.vis.note. Only articulations should be encoded in the artic attribute; for example, fingerings should be encoded using the fing element. - - + + - + Logical domain attributes. - - - - + + + + - - + + Indicates the next section or movement to be performed. - - + + - + - + @target attribute should have content. The value in @target should correspond to the @xml:id attribute of a section or @@ -28188,33 +16474,33 @@ - + Attributes that describe the intended audience. - - + + The intended audience. - - + + Internal use only. - + Available to all audiences. - + Attributes that record the number of dots of augmentation. - - + + Records the number of augmentation dots required by a written dotted duration. - - + + - + - + An element with a dots attribute must also have a dur attribute. @@ -28223,375 +16509,389 @@ -

    The dots attribute records the number of augmentation dots necessary to +

    The dots attribute records the number of augmentation dots necessary to represent a non-power-of-two duration. This is usually, but not always, the number of dots displayed. For example, a note with this attribute will result in displayed dots, while a glissando will not.

         - + Attributes that describe the source of a controlled value. - - + + - - + + A name or label associated with a controlled vocabulary or other authoritative source for this element or its content. - - + + - + A web-accessible location of the controlled vocabulary or other authoritative source - for this element or its content. - - + of identification or definition for this element or its content. This attribute may + contain a complete URI or a partial URI which is completed by the value of the codedval + attribute. + + - + Logical domain attributes. - - + + - - + + Records the appearance and usually the function of the bar line. - - + + - + Attributes that capture the placement of bar lines. - - - States the length of a barline. Must be greater than 0 and less than or equal to (2 - times number of staff lines) + 2, e.g., between 0 and 12 for a 5-line staff. - - + + + States the length of barlines in virtual units. The value must be greater than 0 and + is typically equal to 2 times (the number of staff lines - 1); e.g., a value of '8' for a + 5-line staff. + + 0 -

    The value of barlinelen must be greater than 0 and less than or equal to (2 times - number of staff lines) + 2; e.g., 12 on a 5-line staff.

    +

    This attribute is ignored if the value of the bar.style attribute is "mensur".

         - - Records the location of a bar line. - - + + Records the method of barring. + + + + + + "mensur" not allowed in this + context. + + + - - If takt bar lines are to be used, then the taktplace attribute may be used to denote - the staff location of the shortened bar line. The location may include staff lines, - spaces, and the spaces directly above and below the staff. The value ranges between 0 - (just below the staff) to 2 * number of staff lines (directly above the staff). For - example, on a 5-line staff the lines would be numbered 1,3,5,7, and 9 while the spaces - would be numbered 0,2,4,6,8,10. For example, a value of '9' puts the bar line through the - top line of a 5-line staff. - - + + Denotes the staff location of bar lines, if the length is non-standard; that is, not + equal to 2 times (the number of staff lines - 1). + + + +

    The location may include staff lines, the spaces between the lines, and the spaces + directly above and below the staff. The value ranges between 0 (just below the staff) to + 2 * number of staff lines (directly above the staff). For example, on a 5-line staff the + lines would be numbered 1, 3, 5, 7, and 9 while the spaces would be numbered 0, 2, 4, 6, + 8, and 10. So, a value of '9' puts the bar line through the top line of the staff.

    +

    This attribute is ignored if the value of the bar.style attribute is "mensur".

    +     - + Attributes that form the basis of the att.common class. - - + + - - - + + + Provides a base URI reference with which applications can resolve relative URI references into absolute URI references. - - + + - + Bibliographic attributes. - - + + Contains a reference to a field or element in another descriptive encoding system to which this MEI element is comparable. - - + + -

    Mapping elements from one system to another via analog may help a repository +

    Mapping elements from one system to another via analog may help a repository harvest selected data from the MEI file to build a basic catalog record. The encoding system from which fields are taken must be specified. When possible, subfields as well as fields should be specified, e.g., subfields within MARC fields.

         - + Logical domain attributes. - - - - - - + + + + + + - + Attributes that indicate the calendar system of a date or other datable element. - - + + Indicates the calendar system to which a date belongs, for example, Gregorian, Julian, Roman, Mosaic, Revolutionary, Islamic, etc. - - + + - + Attributes that can be used to associate a representation such as a name or title with canonical information about the object being named or referenced. - - + + A value that represents or identifies other data. Often, it is a primary key in the - database or a unique value in the coded list identified by the auth or - auth.uri attributes. - - + database or a unique value in the coded list identified by the auth or + auth.uri attributes. + + - + Logical domain attributes for chord. The artic, dots, and dur attributes encode the written articulations, augmentation dots, and duration values. The beam, fermata, lv, slur, syl, tie, and tuplet attributes may be used to indicate the attachment of these things to this chord. If visual information about these things needs to be recorded, then either the elements corresponding to these attributes or the attributes available in the att.vis.chord class should be employed. - - - - - - - - + + + + + + + + - + Attributes which can be used to classify features. - - + + Contains one or more URIs which denote classification terms that apply to the entity bearing this attribute. - - + + - + - + The value in @class must either correspond to the @xml:id attribute of a category - element or be an absolute external URL. + element or be an external URL. - + Logical domain attributes. - - - - - - - - + + + + + + + + Records the function of the clef. A "cautionary" clef does not change the following pitches. - - + + - + Used by staffDef and scoreDef to provide default values for attributes in the logical domain related to clefs. - + - + An 'F', 'C', or 'G' clef requires that its position be specified. - + A TAB or percussion clef requires that the number of lines be specified. - - + + Encodes a value for the clef symbol. - - + + - + Contains a default value for the position of the clef. The value must be in the range between 1 and the number of lines on the staff. The numbering of lines starts with the lowest line of the staff. - - + + - + Records the amount of octave displacement to be applied to the clef. - - + + - + Records the direction of octave displacement to be applied to the clef. - - + + - + Logical domain attributes. - + Attributes that record the shape of a clef. - + - + When @shape is present, @line must also be specified. - - + + Describes a clef's shape. - - + + - + Visual color attributes. - - + + Used to indicate visual appearance. Do not confuse this with the musical term 'color' as used in pre-CMN notation. - - + + - + Indication of coloration. - - + + Indicates this feature is 'colored'; that is, it is a participant in a change in rhythmic values. In mensural notation, coloration is indicated by colored notes (red, black, etc.) where void notes would otherwise occur. In CMN, coloration is indicated by an inverse color; that is, the note head is void when it would otherwise be filled and vice versa. - - + + - + Attributes common to many elements. - - - - - - + + + + + + + - + Attributes shared by events which rely on other events for their existence. For example, a slur/phrase marking must be drawn between or over a group of notes. The slur is therefore a control event. - - - - - - - - - - - - + + + + + + + + + + + + This attribute class records the position of a feature within a two-dimensional coordinate system. - - + + Indicates the upper-left corner x coordinate. - - + + - + Indicates the upper-left corner y coordinate. - - + + - + Indicates the lower-right corner x coordinate. - - + + - + Indicates the lower-left corner x coordinate. - - + + - + Attributes that describe "cue-ness". - - - - + + + + - + Attributes that describe curvature. - - + + Records the placement of Bezier control points as a series of pairs of space-separated values; e.g., 19 45 -32 118. - - + + @@ -28599,15 +16899,15 @@ - + Describes a curve as one or more pairs of values with respect to an imaginary line connecting the starting and ending points of the curve. The first value captures a distance to the left (positive value) or right (negative value) of the line, expressed in virtual units. The second value of each pair represents a point along the line, expressed as a percentage of the line's length. N.B. An MEI virtual unit (VU) is half the distance between adjacent staff lines. - - + + @@ -28615,54 +16915,54 @@ - + Describes a curve with a generic term indicating the direction of curvature. - - + + Upward curve. - + Downward curve. - + A "meandering" curve, both above and below the items it pertains to. - + Attributes that record the visual rendition of curves. - - + + Describes the line style of a curve. - - + + - + Width of a curved line. - - + + - + Logical domain attributes. - - + + - - + + Encodes the target note when its pitch differs from the pitch at which the custos appears. - - + + - + - + @target attribute should have content. The value in @target should correspond to the @xml:id attribute of a note @@ -28673,52 +16973,52 @@ - + Attributes common to dates. - - + + Contains the end point of a date range in standard ISO form. - - + + - + Provides the value of a textual date in standard ISO form. - - + + - + Contains an upper boundary for an uncertain date in standard ISO form. - - + + - + Contains a lower boundary, in standard ISO form, for an uncertain date. - - + + - + Contains the starting point of a date range in standard ISO form. - - + + - + Attributes for linking metadata to data. - - + + Used to link metadata elements to one or more data-containing elements. - - + + - + - + @data attribute should have content. The value in @data should correspond to the @xml:id attribute of a descendant of @@ -28729,26 +17029,26 @@ - + Logical domain attributes. - - + + - + Provides attributes for elements which may be associated with particular contextual elements within the header. - - + + Identifies one or more metadata elements (other than classification terms) within the header, which are understood to apply to the element bearing this attribute and its content. - - + + - + - + @decls attribute should have content. Each value in @decls should correspond to the @xml:id attribute of an element @@ -28761,215 +17061,215 @@ - + Attributes that capture the dimensions of an entity. - - - + + + - + Logical domain attributes. - - - - - + + + + + - + Attributes that describe distance from the staff. - - + + Records the default distance from the staff for dynamic marks. - - + + - + Records the default distance from the staff of harmonic indications, such as guitar chord grids or functional labels. - - + + - + Determines how far from the staff to render text elements. - - + + - + Logical domain attributes. - - + + - - + + Records the function of the dot. - - + + Augmentation dot. - + Dot of division. - + Attributes that permit total duration to be represented by multiple values. - - + + When a duration cannot be represented as a single power-of-two value, multiple space-separated values that add up to the total duration may be used. - - + + - + Attributes that provide a durational default value. - - + + Contains a default duration in those situations when the first note, rest, chord, etc. in a measure does not have a duration specified. - - + + - + Along with numbase.default, describes the default duration as a ratio. num.default is the first value in the ratio. - - + + - + Along with num.default, describes the default duration as a ratio. numbase.default is the second value in the ratio. - - + + - + Attributes that express duration in musical terms. - - + + Records the duration of a feature using the relative durational values provided by the data.DURATION datatype. - - + + - + Attributes that describe duration as a ratio. - - + + Along with numbase, describes duration as a ratio. num is the first value in the ratio, while numbase is the second. - - + + - + Along with num, describes duration as a ratio. num is the first value in the ratio, while numbase is the second. - - + + - + Logical domain attributes. - - - - - + + + + + - + Attributes that capture characters used to enclose symbols having a cautionary or editorial function. - - + + Records the characters often used to mark accidentals, articulations, and sometimes notes as having a cautionary or editorial function. For an example of cautionary accidentals enclosed in parentheses, see Read, p. 131, ex. 9-14. - - + + - + Logical domain attributes. - - + + - + Attributes that record ending style information - - + + Describes where ending marks should be displayed. - - + + Ending rendered only above top staff. - + Ending rendered above staves that have bar lines drawn across them. - + Endings rendered above staff groups. - + Attributes that apply to all written events, e.g., note, chord, rest, etc. - - - - - - + + + + + + - + Attributes describing the support for and the certainty of an assertion. - - + + Signifies the degree of certainty or precision associated with a feature. - - + + - + Indicates the nature of the evidence supporting the reliability or accuracy of the intervention or interpretation. - - + + - - + + There is evidence within the document to support the intervention. - + There is evidence outside the document to support the intervention. - + The assertion has been made by the editor, cataloguer, or scholar on the basis of their expertise. @@ -28977,41 +17277,41 @@ - + Attributes that describe extension symbols, typically lines. Members of this class are also typically members of the att.lineRend class. - - + + - - + + Indicates the presence of an extension symbol, typically a line. - - + + - + Provides attributes for describing the size of an entity. - - - + + + - - + + Captures a measurement, count, or description. When extent contains a numeric value, use the unit attribute to indicate the measurement unit. - - + + - + - + The @unit attribute is recommended. - + Separation into value (@extent) and unit (@unit) is recommended. @@ -29020,57 +17320,57 @@ - + Attributes indicating the attachment of a fermata to the feature. - - + + Indicates the attachment of a fermata to this element. If visual information about the fermata needs to be recorded, then a fermata element should be employed instead. - - + + - + Attributes that deal with string filing characteristics. - - + + Holds the number of initial characters (such as those constituting an article or preposition) that should not be used for sorting a title or name. - - + + - + Logical domain attributes. - - - + + + - - + + Indicates the nesting level of staff grouping symbols. - - + + - + Attributes which identify a document hand. - - + + Signifies the hand responsible for an action. The value must be the ID of a hand element declared in the header. - - + + - + - + @hand attribute should have content. Each value in @hand should correspond to the @xml:id attribute of a hand @@ -29081,70 +17381,70 @@ - + Attributes that describe vertical size. - - + + Measurement of the vertical dimension of an entity. - - + + - + Attributes that record horizontal alignment. - - + + Records horizontal alignment. - - + + - + Attributes that uniquely identify an element. - - - + + + Regularizes the naming of an element and thus facilitates building links between it and other resources. Each id attribute within a document must have a unique value. - - + + - + Attributes which record the type of an electronic resource. - - + + Specifies the applicable MIME (multimedia internet mail extension) type. The value should be a valid MIME media type defined by the Internet Engineering Task Force in RFC 2046. - - + + - + Attributes indicating that elements are semantically linked; that is, while the parts are encoded separately, together they may be thought of as a single intellectual object. - - + + Used for linking visually separate entities that form a single logical entity, for example, multiple slurs broken across a system break that form a single musical phrase. Also used to indicate a measure which metrically completes the current one. Record the identifiers of the separately encoded components, excluding the one carrying the attribute. - - + + - + - + @join attribute should have content. Each @@ -29156,110 +17456,109 @@ - + Logical domain attributes. - - - + + + - + Logical domain attributes. - - + + Written key signature. - - + + -

    Mixed key signatures, e.g. those consisting of a mixture of flats and sharps (Read, p. 143, +

    Mixed key signatures, e.g. those consisting of a mixture of flats and sharps (Read, p. 143, ex. 9-39), and key signatures with unorthodox placement of the accidentals (Read, p. 141) can be encoded using the keySig element.

         - + Used by staffDef and scoreDef to provide default values for attributes in the logical domain that are related to key signatures. - - + + Written key signature. - - + + -

    Mixed key signatures, e.g. those consisting of a mixture of flats and sharps (Read, p. 143, +

    Mixed key signatures, e.g. those consisting of a mixture of flats and sharps (Read, p. 143, ex. 9-39), and key signatures with unorthodox placement of the accidentals (Read, p. 141) can be encoded using the keySig element.

         - - - + + + Captures text to be used to generate a label for the element to which it's attached, a "tool tip" or prefatory text, for example. Should not be used to record document content. - - + + -

    - label is used to provide a display label for an element's contents, for +

    label is used to provide a display label for an element's contents, for example in the form of a "tool tip" or as the "name" when the element's contents are - treated as the "value" in a "name-value pair". Unlike n, label may + treated as the "value" in a "name-value pair". Unlike n, label may contain space characters.

    -

    Don't confuse this attribute with the label element, which +

    Don't confuse this attribute with the label element, which records document content.

         - + Language attributes common to text elements. - - - + + + Identifies the language of the element's content. The values for this attribute are language 'tags' as defined in BCP 47. All language tags that make use of private use sub-tags must be documented in a corresponding language element in the MEI header whose id attribute is the same as the language tag's value. - - + + - + Specifies the transliteration technique used. - - + + -

    There is no standard list of transliteration schemes.

    +

    There is no standard list of transliteration schemes.

         -

    BCP 47 is described at https://tools.ietf.org/html/bcp47. The IANA Subtag Registry, from which BCP 47 +

    BCP 47 is described at https://tools.ietf.org/html/bcp47. The IANA Subtag Registry, from which BCP 47 language tags are constructed, may be found at www.iana.org/assignments/language-subtag-registry. A tool for locating subtags and validating language tags is available at https://r12a.github.io/apps/subtags.

         - + Logical domain attributes. - - + + - - + + Provides a mechanism for linking the layer to a layerDef element. - - + + - + - + @def attribute should have content. The value in @def should correspond to the @xml:id attribute of a layerDef @@ -29270,131 +17569,131 @@ - + Logical domain attributes. - - - - - + + + + + - + Attributes that identify the layer to which a feature applies. - - + + Identifies the layer to which a feature applies. - - + + - + Attributes for identifying the staff line with which a feature is associated. - - + + Indicates the line upon which a feature stands. The value must be in the range between 1 and the number of lines on the staff. The numbering of lines starts with the lowest line of the staff. - - + + - + Attributes that record the visual rendition of lines. - - + + - - - + + + Symbol rendered at end of line. - - + + - + Holds the relative size of the line-end symbol. - - - - - - + + + + + Symbol rendered at start of line. - - + + - + Holds the relative size of the line-start symbol. - - + + - - + Attributes that record the basic visual rendition of lines. - - + + Describes the line style of a line. - - + + + + + + + Describes the number of segments into which a dashed or dotted line may be divided, or + the number of "peaks" of a wavy line; a pair of space-separated values (minimum and + maximum, respectively) provides a range between which a rendering system-supplied value + may fall, while a single value indicates a fixed amount of space; that is, the minimum and + maximum values are equal. + + + 2 + + + + + @lform attribute + matching "dashed", "dotted", or "wavy" required. + + + - - + Width of a line. - - + + + - + Attributes that specify element-to-element relationships. - - + + Points to an element of which the current element is a copy. - - + + - + - + An element with a copyof attribute can only have comment or processing instruction descendents. - + - + @copyof attribute should have content. The @@ -29404,15 +17703,15 @@ - + Used to point to other elements that correspond to this one in a generic fashion. - - + + - + - + @corresp attribute should have content. Each @@ -29422,31 +17721,67 @@ - + + points to one or more events in a user-defined collection that are known to be + predecessors of the current element. + + + + + + + @follows attribute + should have content. + Each + value in @follows must correspond to the @xml:id attribute of an + element. + + + + + Used to point to the next event(s) in a user-defined collection. - - + + - + - + @next attribute should have content. Each - value in @next should correspond to the @xml:id attribute of an + value in @next should correspond to the @xml:id attribute of an + element. + + + + + + Points to one or more events in a user-defined collection that are known to be + successors of the current element. + + + + + + + @precedes attribute + should have content. + Each + value in @precedes must correspond to the @xml:id attribute of an element. - + Points to the previous event(s) in a user-defined collection. - - + + - + - + @prev attribute should have content. Each @@ -29456,15 +17791,15 @@ - + Points to an element that is the same as the current element but is not a literal copy of the current element. - - + + - + - + @sameas attribute should have content. Each @@ -29474,14 +17809,14 @@ - + Points to elements that are synchronous with the current element. - - + + - + - + @synch attribute should have content. Each @@ -29493,354 +17828,354 @@ - + Attributes that describe default typography of lyrics. - - + + Describes the alignment of lyric syllables associated with a note or chord. - - + + - + Sets the font family default value for lyrics. - - + + - + Sets the font name default value for lyrics. - - + + - + Sets the default font size value for lyrics. - - + + - + Sets the default font style value for lyrics. - - + + - + Sets the default font weight value for lyrics. - - + + - + Attributes that record the unit of measurement in which a value is expressed. - - + + Indicates the unit of measurement. - - + + - - + + Byte. - + Character. - + Centimeter. - + Degree. - + Inch. - + Serial issue. - + Foot. - + Meter. - + Millimeter. - + Page. - + Pica. - + Point. - + Pixel. - + Radian. - + Record. - + Serial volume. - + MEI virtual unit. - + Attributes pertaining to measure numbers - - + + Indicates whether measure numbers should be displayed. - - + + - + Attributes that establish the boundaries of a media object. - - + + Specifies a point where the relevant content begins. A numerical value must be less and a time value must be earlier than that given by the end attribute. - - + + - + Specifies a point where the relevant content ends. If not specified, the end of the content is assumed to be the end point. A numerical value must be greater and a time value must be later than that given by the begin attribute. - - + + - + Type of values used in the begin/end attributes. The begin and end attributes can only be interpreted meaningfully in conjunction with this attribute. - - + + - + Attributes describing a writing medium, such as pencil or ink. - - + + Describes the writing medium. - - + + - + Attributes that record the version of MEI in use. - - + + Specifies a generic MEI version label. 4.0.0 - - + + This version of MEI. - + Logical domain attributes. - - - - + + + + - - + + Specifies whether a dot is to be added to the base symbol. - - + + - + The base symbol in the mensuration sign/time signature of mensural notation. - - + + - + Attributes that provide information about a structure's conformance to the prevailing meter. - - + + Indicates the relationship between the content of a staff or layer and the prevailing meter. - - + + Complete; i.e., conformant with the prevailing meter. - + Incomplete; i.e., not enough beats. - + Overfull; i.e., too many beats. - + Attributes that provide information about a measure's conformance to the prevailing meter. - - + + Indicates the relationship between the content of a measure and the prevailing meter. - - + + - + Indicates whether or not a bar line is "controlling"; that is, if it indicates a point of alignment across all the parts. Bar lines within a score are usually controlling; that is, they "line up". Bar lines within parts may or may not be controlling. When applied to - measure, this attribute indicates the nature of the right barline + measure, this attribute indicates the nature of the right barline but not the left. - - + + - + Logical domain attributes. - - + + Captures the number of beats in a measure, that is, the top number of the meter signature. It must contain a decimal number or an additive expression that evaluates to a decimal number, such as 2+3. - - + + \d+(\.\d+)?(\s*\+\s*\d+(\.\d+)?)* - + Indicates the use of a meter symbol instead of a numeric meter signature, that is, 'C' for common time or 'C' with a slash for cut time. - - + + - + Contains the number indicating the beat unit, that is, the bottom number of the meter signature. - - + + - + Used by staffDef and scoreDef to provide default values for attributes in the logical domain related to meter signature. - - + + Captures the number of beats in a measure, that is, the top number of the meter signature. It must contain a decimal number or an additive expression that evaluates to a decimal number, such as 2+3. - - + + \d+(\.\d+)?(\s*\+\s*\d+(\.\d+)?)* - + Contains the number indicating the beat unit, that is, the bottom number of the meter signature. - - + + - + Indicates the use of a meter symbol instead of a numeric meter signature, that is, 'C' for common time or 'C' with a slash for cut time. - - + + - + Attributes that record tempo in terms of beats per minute. - - + + Used to describe tempo in terms of beats (often the meter signature denominator) per minute, ala M.M. (Maezel's Metronome). Do not confuse this attribute with midi.bpm or midi.mspb. In MIDI, a beat is always defined as a quarter note, *not the numerator of the time signature or the metronomic indication*. - - + + - + Captures the metronomic unit. - - + + - + Records the number of augmentation dots required by a dotted metronome unit. - - + + - + Attributes that indicate programmatic numbering. - - + + Indicates whether programmatically calculated counts of multiple measures of rest (mRest) and whole measure repeats (mRpt) in parts should be rendered. - - + + - + Attributes shared by names. - - - - + + + + - - + + Used to record a pointer to the regularized form of the name elsewhere in the document. - - + + - + - + @nymref attribute should have content. The @@ -29850,85 +18185,85 @@ - + Used to specify further information about the entity referenced by this name, for example, the occupation of a person or the status of a place. - - + + -

    When applicable, values from the MARC relator term list (http://www.loc.gov/marc/relators/relaterm.html) or code list (http://www.loc.gov/marc/relators/relacode.html) are recommended for - role.

    +

    When applicable, values from the MARC relator term list (http://www.loc.gov/marc/relators/relaterm.html) or code list (http://www.loc.gov/marc/relators/relacode.html) are recommended for + role.

         - + Attributes used to supply an integer number designation for an element. - - + + Provides a numeric designation that indicates an element's position in a sequence of similar elements. Its value must be a non-negative integer. - - + + - + Attributes used to supply a number-like designation for an element. - - + + Provides a number-like designation that indicates an element's position in a sequence of similar elements. May not contain space characters. - - + + - + Attributes that capture music font name and size. - - + + Sets the default music font name. - - + + - + Sets the default music font size. - - + + - + Logical domain attributes. - - - - - - - - - - - - + + + + + + + + + + + + Attributes pertaining to the notehead part of a note. - - + + Provides a way of pointing to a user-defined symbol. It must contain a reference to an ID of a symbolDef element elsewhere in the document. - - + + - + - + @head.altsym attribute should have content. The value in @head.altsym should correspond to the @xml:id attribute of a symbolDef @@ -29937,153 +18272,153 @@ - + A name or label associated with the controlled vocabulary from which a numerical value - of head.shape is taken. - - + of head.shape is taken. + + - + - + When @head.auth matches 'smufl', @head.shape must contain a numeric glyph reference in hexadecimal notation, e.g. "#xE000" or "U+E000". - - + + Standard Music Font Layout. - + Captures the overall color of a notehead. - - + + - + Describes how/if the notehead is filled. - - + + - + Captures the fill color of a notehead if different from the overall note color. - - + + - + Records any additional symbols applied to the notehead. - - + + - + Describes rotation applied to the basic notehead shape. A positive value rotates the notehead in a counter-clockwise fashion, while negative values produce clockwise rotation. - - + + - + Used to override the head shape normally used for the given duration. - - + + - + - + SMuFL version 1.18 uses the range U+E000 - U+ECBF. - + Indicates if a feature should be rendered when the notation is presented graphically or sounded when it is presented in an aural form. - - + + - + Attributes that record written octave. - - + + Captures written octave information. - - + + - + Attributes that record a default value for octave. - - + + Contains a default octave specification for use when the first note, rest, chord, etc. in a measure does not have an octave value specified. - - + + - + Attributes describing the amount and direction of octave displacement. - - + + Records the amount of octave displacement. - - + + - + Records the direction of octave displacement. - - + + - + Attributes that record placement of notes on a single-line staff. - - + + Determines the placement of notes on a 1-line staff. A value of 'true' places all notes on the line, while a value of 'false' places stems-up notes above the line and stems-down notes below the line. - - + + - + Attributes pertaining to layout optimization. - - + + Indicates whether staves without notes, rests, etc. should be displayed. When the value is 'true', empty staves are displayed. - - + + - + Attributes that identify the layer associated with a distant feature. - - + + identifies the layer on which referenced notation occurs. - - + + @@ -30092,14 +18427,14 @@ - + Attributes for identifying the staff associated with a distant feature. - - + + signifies the staff on which referenced notation occurs. Defaults to the same value as the local staff. Mandatory when applicable. - - + + @@ -30108,44 +18443,44 @@ - + Attributes recording the identifiers of the first and last elements of a sequence of distant elements. - - + + indicates the first element in a sequence of events. - - + + - + indicates the final element in a sequence of events. - - + + - + Attributes that identify a musical range in terms of musical time. - - + + encodes the starting point of musical material in terms of musical time, i.e., a (potentially negative) count of measures plus a beat location. - - + + - + encodes the ending point of musical material in terms of musical time, i.e., a count of measures plus a beat location. The values are relative to the measure identified by - origin.tstamp. - - + origin.tstamp. + + - + - + When @origin.tstamp2 is used @origin.tstamp must also be present. @@ -30154,112 +18489,112 @@ - + Logical domain attributes. - - - - - - + + + + + + - + Logical domain attributes. - - - + + + - + Attributes that record page-level layout information. - - + + Specifies the height of the page; may be expressed in real-world units or staff steps. - - + + - + Describes the width of the page; may be expressed in real-world units or staff steps. - - + + - + Indicates the amount of whitespace at the top of a page. - - + + - + Indicates the amount of whitespace at the bottom of a page. - - + + - + Indicates the amount of whitespace at the left side of a page. - - + + - + Indicates the amount of whitespace at the right side of a page. - - + + - + Indicates the number of logical pages to be rendered on a single physical page. - - + + - + Indicates how the page should be scaled when rendered. - - + + - + Logical domain attributes. - + Attributes for identifying the part in which the current feature appears. - - + + Indicates the part in which the current feature should appear. Use '%all' when the feature should occur in every part. - - + + (%all|#[\i][\c]+) - + - + '%all' cannot be mixed with other values. - + Signifies the part staff on which a notated feature occurs. Use '%all' when the feature should occur on every staff. - - - (%all|\d+(-\d+)?(,\d+(-\d+)?)*) + + + (%all|\d+(-\d+)?) - + - + '%all' cannot be mixed with other values. @@ -30268,68 +18603,68 @@ - + Logical domain attributes. - + Logical domain attributes. - - + + - + Logical domain attributes. - - - - - + + + + + - + Attributes that record written pitch name. - - + + Contains a written pitch name. - - + + - + Attributes that record written pitch name and octave number. - - - + + + - + Attributes capturing placement information. - - + + Captures the placement of the item with respect to the staff with which it is associated. - - + + - + Attributes listing the active participants in a user-defined collection. - - + + 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. - - + + - + - + @plist attribute should have content. Each @@ -30341,137 +18676,132 @@ - + Attributes common to all pointing/linking elements. - - - + + + Defines whether a link occurs automatically or must be requested by the user. - - + + Load the target resource(s) immediately. - + Load the target resource(s) upon user request. - + Do not permit loading of the target resource(s). - + Behavior other than allowed by the other values of this attribute. - - + + Characterization of the relationship between resources. The value of the role attribute must be a URI. - - + + - - + + Defines how a remote resource is rendered. - - + + Open in a new window. - + Load the referenced resource in the same window. - + Embed the referenced resource at the point of the link. - + Do not permit traversal to the referenced resource. - + Behavior other than permitted by the other values of this attribute. - + Identifies passive participants in a relationship; that is, the entities pointed "to". - - + + - + Characterization of target resource(s) using any convenient classification scheme or typology. - - + + - - - + + + - + Attributes that specify a measurement in numerical terms. - - - + + + - - + + Numeric value capturing a measurement or count. Can only be interpreted in combination with the unit attribute. - - + + 0 - + Groups attributes that describe a numerical range. - - + + Gives a minimum estimated value for an approximate measurement. - - + + - + Gives a maximum estimated value for an approximate measurement. - - + + - + Where the measurement summarizes more than one observation or a range of values, supplies the minimum value observed. - - + + - + Where the measurement summarizes more than one observation or a range of values, supplies the maximum value observed. - - + + - + Specifies the degree of statistical confidence (between zero and one) that a value falls within the range specified by min and max, or the proportion of observed values that fall within that range. - - + + - + - + The attributes @min and @max are required when @confidence is present. @@ -30480,31 +18810,31 @@ - + Attributes that hold a controlled value. - - + + Provides a regularized, authorized value. - - + + - + Attributes capturing information regarding responsibility for some aspect of the text's creation, transcription, editing, or encoding. - - - Indicates the agent(s) responsible for some aspect of the text's creation, - transcription, editing, or encoding. Its value must point to one or more identifiers - declared in the document header. - - - - + + + Indicates the agent(s) responsible for some aspect of the text's transcription, + editing, or encoding. Its value must point to one or more identifiers declared in the + document header. + + + + - + @resp attribute should have content. The value in @resp should correspond to the @xml:id attribute of an element within @@ -30515,149 +18845,171 @@ - + Logical domain attributes. - - - - - - + + + + + + - + Logical domain attributes. - - + + - + Attributes that describe relative size. - - + + Scale factor to be applied to the feature to make it the desired display size. - - + + - + Logical domain attributes. - + Logical domain attributes for scoreDef in the CMN repertoire. The values set in these attributes act as score-wide defaults for attributes that are not set in descendant elements. - - - - - - - - - - - - + + + + + + + + + + + + Logical domain attributes. - - + + - + Attributes that describe order within a collection of features. - - + + Used to assign a sequence number related to the order in which the encoded features carrying this attribute are believed to have occurred. - - + + - + Attributes for recording the number of slashes that accompany a feature. - - + + Indicates the number of slashes present. - - + + - + Attributes for marking the presence of a slur. - - + + Indicates that this element participates in a slur. If visual information about the slur needs to be recorded, then a slur element should be employed. - - + + + + + + + + Attributes common to elements that may refer to a source. + + + Contains a list of one or more pointers indicating the sources which attest to a given + reading. Each value should correspond to the ID of a source or manifestationelement located in the document header. + + + + + + @source attribute + should have content. + Each value in @source should correspond to the @xml:id attribute of a source or + manifestation element. + + + - + Logical domain attributes. - - - - + + + + - + Attributes that capture notation spacing information. - - + + Describes a note's spacing relative to its time value. - - + + - + Describes the note spacing of output. - - + + - + Specifies the minimum amount of space between adjacent staves in the same system; measured from the bottom line of the staff above to the top line of the staff below. - - + + - + Describes the space between adjacent systems; a pair of space-separated values (minimum and maximum, respectively) provides a range between which a rendering system-supplied value may fall, while a single value indicates a fixed amount of space; that is, the minimum and maximum values are equal. - + - + Logical domain attributes. - - + + - - + + Provides a mechanism for linking the staff to a staffDef element. - - + + - + - + @def attribute should have content. The value in @def should correspond to the @xml:id attribute of a staffDef @@ -30668,138 +19020,138 @@ - + Logical domain attributes for staffDef. - - - - - - - - - - - - - + + + + + + + + + + + + + Indicates the number of staff lines. - - + + - + Attributes that describe the symbol used to group a set of staves. - - + + Specifies the symbol used to group a set of staves. - - + + Curved symbol, i.e., {. - + Square symbol, i.e., [, but with curved/angled top and bottom segments. - + Square symbol, i.e., [, with horizontal top and bottom segments. - + Line symbol, i.e., |, (wide) line without top and bottom curved/horizontal segments. - + Grouping symbol missing. - + Logical domain attributes. - + Attributes for identifying the staff associated with the current feature. - - + + Signifies the staff on which a notated event occurs or to which a control event applies. Mandatory when applicable. - - + + - + Attributes that describe items printed near (above, below, or between) staves - - + + Describes vertical order of items printed above a staff, from closest to farthest away from the staff. - - + + - + Describes vertical order of items printed below a staff, from closest to farthest away from the staff. - - + + - + Describes vertical order of items printed between staves, from top to bottom. - - + + - + Attributes that identify location on a staff in terms of lines and spaces. - - + + Holds the staff location of the feature. - - + + - + Attributes that identify location on a staff in terms of pitch and octave. - - + + Captures staff location in terms of written pitch name. - - + + - + Records staff location in terms of written octave. - - + + - + Attributes recording the identifiers of the first and last elements of a sequence of elements to which the current element is associated. - - + + - - + + Indicates the final element in a sequence of events to which the feature applies. - - + + - + - + @endid attribute should have content. The @@ -30811,18 +19163,18 @@ - + Attributes that identify a relative starting point. - - + + Holds a reference to the first element in a sequence of events to which the feature applies. - - + + - + - + @startid attribute should have content. The @@ -30834,209 +19186,209 @@ - + Attributes that describe the properties of stemmed features; that is, chords and notes. - - + + - - + + Describes the direction of a stem. - - + + - + Encodes the stem length. - - + + - + Encodes any stem "modifiers"; that is, symbols rendered on the stem, such as tremolo or Sprechstimme indicators. - - + + - + Records the position of the stem in relation to the note head(s). - - + + - + Determines whether a stem should be displayed. - - + + - + Records the output x coordinate of the stem's attachment point. - - + + - + Records the output y coordinate of the stem's attachment point. - - + + - + Logical domain attributes. - - + + Describes the symbols typically used to indicate breaks between syllables and their functions. - - + + Space (word separator). - + Dash (syllable separator). - + Underscore (syllable extension). - + Tilde (syllable elision). - + Circumflex [angled line above] (syllable elision). - + Caron [angled line below] (syllable elision). - + Inverted breve [curved line above] (syllable elision). - + Breve [curved line below] (syllable elision). - + Records the position of a syllable within a word. - - + + (initial) first syllable. - + (medial) neither first nor last syllable. - + (terminal) last syllable. - + Attributes that hold associated sung text syllables. - - + + Holds an associated sung text syllable. - - + + - + Logical domain attributes. - - + + - + Attributes that capture system layout information. - - + + Indicates whether the staves are joined at the left by a continuous line. The default value is "true". Do not confuse this with the heavy vertical line used as a grouping symbol. - - + + - + Describes the amount of whitespace at the left system margin relative to page.leftmar. - - + + - + Describes the amount of whitespace at the right system margin relative to page.rightmar. - - + + - + Describes the distance from page's top edge to the first system; used for first page only. - - + + - + Attributes that deal with resolution of values in plist or target attributes. - - + + Specifies the intended meaning when a participant in a relationship is itself a pointer. - - + + If an element pointed to is itself a pointer, then the target of that pointer will be taken, and so on, until an element is found which is not a pointer. - + If an element pointed to is itself a pointer, then its target (whether a pointer or not) is taken as the target of this pointer. - + No further evaluation of targets is carried out beyond that needed to find the element(s) specified in plist or target attribute. -

    If no value is given, the application program is responsible for deciding (possibly on +

    If no value is given, the application program is responsible for deciding (possibly on the basis of user input) how far to trace a chain of pointers.

         - + Logical domain attributes. - - - - + + + + - - + + Records the function of a tempo indication. - - + + Marks a gradual change of tempo, such as "accel." or "rit." - + Represents a static tempo instruction, such as a textual term like "Adagio", a metronome marking like "♩=70", or a combination of text and metronome indication. - + Captures a change in pulse rate (tempo) and/or pulse grouping (subdivision) in an "equation" of the form [tempo before change] = [tempo after change]. - + Indicates a change in pulse rate (tempo) and/or pulse grouping (subdivision) in an "equation" of the form [tempo after change] = [tempo before change]. The term "precedente" often appears following the "equation" to distinguish this kind of @@ -31046,388 +19398,388 @@ - + Attributes that record renditional characteristics. - - + + Used to extend the values of the rend attribute. - - + + - + Captures the appearance of the element's contents using MEI-defined descriptors. - - + + - + Attributes that describe default text typography. - - + + Provides a default value for the font family name of text (other than lyrics) when this information is not provided on the individual elements. - - + + - + Provides a default value for the font name of text (other than lyrics) when this information is not provided on the individual elements. - - + + - + Provides a default value for the font size of text (other than lyrics) when this information is not provided on the individual elements. - - + + - + Provides a default value for the font style of text (other than lyrics) when this information is not provided on the individual elements. - - + + - + Provides a default value for the font weight for text (other than lyrics) when this information is not provided on the individual elements. - - + + - + Attributes that indicate the presence of a tie. - - + + Indicates that this element participates in a tie. If visual information about the tie needs to be recorded, then a tie element should be employed. - - + + - + Attributes that record a time stamp in terms of musical time, i.e., beats[.fractional beat part]. - - + + Encodes the onset time in terms of musical time, i.e., beats[.fractional beat part], as expressed in the written time signature. - - + + - + Attributes that record a time stamp for the end of an event in terms of musical time. - - + + Encodes the ending point of an event, i.e., a count of measures plus a beat location in the ending measure. - - + + - + Attributes that describe transposition. - - + + Records the amount of diatonic pitch shift, e.g., C to C♯ = 0, C to D♭ = 1, necessary to calculate the sounded pitch from the written one. - - + + - + Records the amount of pitch shift in semitones, e.g., C to C♯ = 1, C to D♭ = 1, necessary to calculate the sounded pitch from the written one. - - + + -

    Diatonic transposition requires both trans.diat and trans.semi +

    Diatonic transposition requires both trans.diat and trans.semi attributes in order to distinguish the difference, for example, between a transposition from C to C♯ and one from C to D♭.

         - + Attributes for indicating the presence of a tuplet. - - + + Indicates that this feature participates in a tuplet. If visual information about the tuplet needs to be recorded, then a tuplet element should be employed. - - + + - + Attributes which can be used to classify features. - - + + - - + + Designation which characterizes the element in some sense, using any convenient classification scheme or typology that employs single-token labels. - - + + -

    When appropriate, values from an established typology should be used.

    +

    When appropriate, values from an established typology should be used.

         - + Typographical attributes. - - + + Contains the name of a font-family. - - + + - + Holds the name of a font. - - + + - + Indicates the size of a font expressed in printers' points, i.e., 1/72nd of an inch, relative terms, e.g., "small", "larger", etc., or percentage values relative to "normal" size, e.g., "125%". - - + + - + Records the style of a font, i.e, italic, oblique, or normal. - - + + - + Used to indicate bold type. - - + + - + Attributes that record vertical alignment. - - + + Records vertical alignment. - - + + - + Attributes that record grouping of vertically aligned elements. - - + + Provides a label for members of a vertically aligned group. - - + + - + Attributes describing whether a feature should be displayed. - - + + Indicates if a feature should be rendered when the notation is presented graphically or sounded when it is presented in an aural form. - - + + - + Visual offset attributes. Some items may have their location recorded in terms of offsets from their programmatically-determined location. The ho attribute records the horizontal offset while vo records the vertical. The to attribute holds a timestamp offset, the most common use of which is as an alternative to the ho attribute. - - - - + + + + - + Horizontal offset attributes. - - + + Records a horizontal adjustment to a feature's programmatically-determined location in terms of staff interline distance; that is, in units of 1/2 the distance between adjacent staff lines. - - + + - + Horizontal offset attributes specified in terms of time. - - + + Records a timestamp adjustment of a feature's programmatically-determined location in terms of musical time; that is, beats. - - + + - + Vertical offset attributes. - - + + Records the vertical adjustment of a feature's programmatically-determined location in terms of staff interline distance; that is, in units of 1/2 the distance between adjacent staff lines. - - + + - + Visual offset attributes. Some items may have their location recorded in terms of pairs of offsets from their programmatically-determined location. The startho and endho attributes record the horizontal offsets of the start and end points of the item, respectively. Similarly, the startvo and endvo attributes record the vertical offsets of the start and end points of the item. The startto and endto attributes hold timestamp offsets, the most common use of which is as alternatives to the ho attributes. - - - - + + + + - + Horizontal offset requiring a pair of attributes. - - + + Records the horizontal adjustment of a feature's programmatically-determined start point. - - + + - + Records the horizontal adjustment of a feature's programmatically-determined end point. - - + + - + Horizontal offset attributes requiring a pair of attributes specified in terms of time. - - + + Records a timestamp adjustment of a feature's programmatically-determined start point. - - + + - + Records a timestamp adjustment of a feature's programmatically-determined end point. - - + + - + Vertical offset attributes requiring a pair of attributes. - - + + Records a vertical adjustment of a feature's programmatically-determined start point. - - + + - + Records a vertical adjustment of a feature's programmatically-determined end point. - - + + - + Attributes that describe the symbol used to group volta elements. - - + + Specifies the symbol used to group lyrics. - - + + Curved symbol, i.e., {. - + Square symbol, i.e., [, but with curved/angled top and bottom segments. - + Square symbol, i.e., [, with horizontal top and bottom segments. - + Line symbol, i.e., |, (wide) line without top and bottom curved/horizontal segments. - + Grouping symbol missing. - + Attributes that address whitespace processing. - - - + + + Allows one to signal to an application whether an element's white space is "significant". The behavior of xml:space cascades to all descendant elements, but it can be turned off locally by setting the xml:space attribute to the value "default". - - + + Allows the application to handle white space as necessary. Not including an xml:space attribute produces the same result as using the default value. - + Instructs the application to maintain white space "as-is", suggesting that it might have meaning. @@ -31435,457 +19787,459 @@ - + Attributes that describe horizontal size. - - + + Measurement of the horizontal dimension of an entity. - - + + -

    The width attribute may be used to capture measure width data for interchange with music +

    The width attribute may be used to capture measure width data for interchange with music printing systems that utilize this information for printing. On <barLine> the width attribute captures the width of the preceding measure.

         - + Output coordinate attributes. Some elements may have their exact rendered *output* coordinates recorded. x and y attributes indicate where to place the rendered output. Recording the coordinates of a feature in a facsimile requires the use of the facs attribute. - - + + Encodes an x coordinate for a feature in an output coordinate system. When it is necessary to record the placement of a feature in a facsimile image, use the facs attribute. - - + + - + Encodes a y coordinate for a feature in an output coordinate system. When it is necessary to record the placement of a feature in a facsimile image, use the facs attribute. - - + + - + Output coordinate attributes. Some elements may need 2 coordinate pairs to record their rendered *output* coordinates. The attributes indicate where to place the rendered output. Recording the coordinates of a feature in a facsimile requires the use of the facs attribute. - - + + Encodes the optional 2nd x coordinate. - - + + - + Encodes the optional 2nd y coordinate. - - + + - + Groups elements used to represent a postal address. - - - - + + + + - + Groups annotation-like elements. - - + + - + Groups elements containing a bibliographic description. - - + + - + Groups elements that may appear as part of a bibliographic description. - + Groups elements that contain the text of a caption or other text displayed along with a figure. - + Groups elements that may appear as part of the content of a chord element. - + Groups elements, such as dynamics, ties, phrase marks, pedal marks, etc., which depend upon other events, such as notes or rests, for their existence. - - - - - - + + + + + + - + Groups elements containing date expressions. - - - - - + + + + + - + Groups elements which provide a description of their parent entity. - + Groups elements which describe a measurement forming part of the physical dimensions of an object. - - + + - + Groups elements containing bibliographic edition information. - - - + + + - + Groups editorial intervention elements. - - - + + + - + Groups elements that represent alternative endings. - - - + + + - + Groups event elements that occur in all notational repertoires. - - - + + + - + Groups elements used to provide a heading at the start of a text division or other markup component. - + Groups identifier-like elements. - - - - + + + + - + Groups elements that may appear as part of a bibliographic imprint. - + Groups elements used to represent a textual or musical incipit. - - + + + - + Groups elements used to declare a MIDI instrument. - + Groups elements that represent accidentals in a key signature. - + Groups elements that have the same function as a key signature. - - - + + + - + Groups elements used to assign a label to other parts of a document. - + Groups elements that permit declaration of layer properties. - + Groups elements that function as notational layers within a staff. - - - - + + + + - + Groups notated events that may appear at the layer level in all repertoires. - + Groups notated events at the layer level that are shared by the mensural and neume repertoires. - - + + - - Groups elements that function like line breaks. - - - + + Groups elements that function like line beginnings. + + + - + Groups elements used to represent generic structural divisions of music notation. - + Groups elements that represent a measurement. - - + + - + Groups elements that represent a meter signature. - - - + + + - + Groups milestone-style elements found in music notation. - + Groups milestone-style elements found in text. - + Groups elements that contain names. - - + + - + Groups elements that modify note-like features. - - + + + - + Groups elements that denote a number or a quantity. - - + + - + Groups elements which may appear as part of the paragraph content model. A paragraph may contain inline elements and all other block-level elements except itself. - + Groups elements that represent a separate performer part. - + Groups elements that collect separate performer parts. - - Groups page break-like elements. - - - - + + Groups page beginning-like elements. + + + + - + Groups paragraph-like elements. - - + + - + Collects elements that express a relationship. - - + + - + Groups elements that mark typographical features. - - + + - + Groups elements that denote a corporate entity that holds a bibliographic item. - - + + - + Groups non-text components that represent the content of the musical text. - + Groups elements that are used to indicate intellectual or other significant responsibility, for example within a bibliographic citation. - - + + - + Groups elements that delineate particular responsibilities as opposed to the respStmt element that provides for generic statements of responsibility. - - - + + + - + Groups elements that provide score meta-information. - - + + - + Groups elements that represent a score. - + Groups elements that may appear as part of a score. - + Groups elements that may appear as part of a score in the mensural and neumes repertoires. - - + + - + Groups elements that represent a segment of music notation. - - - + + + - + Groups elements that may appear as part of a section. - + Groups elements that may appear as part of a section in the mensural and neume repertoires. - - + + - + Groups elements that permit declaration of staff properties. - - + + - + Groups elements that may appear in the declaration of staff features. - + Groups elements that permit declaration of staff group properties. - + Groups elements that function like staves. - - - + + + - + Groups elements that are components of a staff. - + Groups elements that are components of a staff in the mensural and neume repertoires. - - + + - + Groups elements that contain a lyric syllable. - - - - + + + + - + Groups block-level text elements. - - - + + + - + Groups textual elements that occur at the level of individual words or phrases. - - + + - + Groups textual elements that occur at the level of individual words or phrases. This class is equivalent to the model.textPhraseLike class without the pb element. - - - - + + + + - + Groups elements that denote the name of a bibliographic item. - - - + + + - + Groups elements that may appear as part of a title page transcription. - + (accidental) – Records a temporary alteration to the pitch of a note. - - - - - - - - + + + + + + + + - - + + -

    An accidental may raise a pitch by one or two semitones or it may cancel a previous +

    An accidental may raise a pitch by one or two semitones or it may cancel a previous accidental or part of a key signature. This element provides an alternative to the - accid and accid.ges attributes on the note + accid and accid.ges attributes on the note element. The element may be used when specific display info, such as size or color, needs to be recorded for the accidental or when multiple accidentals occur on a single note. The - func attribute can be used to differentiate between the accidental's functions, + func attribute can be used to differentiate between the accidental's functions, such as 'cautionary' or 'editorial'.

         - + Name of an actor appearing within a cast list. - - - - + + + + - - + + @@ -31893,20 +20247,20 @@ -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Contains a postal address, for example of a publisher, an organization, or an individual. - - - - - - - - + + + + + + + + @@ -31918,19 +20272,19 @@ -

    This element is modelled on an element in the Text Encoding Initiative (TEI) and Encoded +

    This element is modelled on an element in the Text Encoding Initiative (TEI) and Encoded Archival Description (EAD) standards.

         - + (address line) – Single line of a postal address. - - - - + + + + - - + + @@ -31940,67 +20294,93 @@ -

    - addrLine may be repeated as many times as necessary to enter all lines - of an address.

    +

    addrLine may be repeated as many times as necessary to enter all + lines of an address.

     -

    This element is modelled on an element in the Text Encoding Initiative (TEI) and Encoded +

    This element is modelled on an element in the Text Encoding Initiative (TEI) and Encoded Archival Description (EAD) standards.

         - + Range of a voice, instrument or piece. - - - - - - - - + + + + + + + + - - - + + + - + Highest or lowest pitch in a score, staff, or layer. - - - - - - - - - - + + + + + + + + + + + + + + (analytic level) – Contains bibliographic elements describing an item (e.g. an article or + poem) published within a monograph or journal and not as an independent publication. + + + + + + + + + + + + + + + + + + + + + + + - + (annotation) – Provides a statement explaining the text or indicating the basis for an assertion. - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + @@ -32019,42 +20399,42 @@ - + - + The @data attribute may only occur on an annotation within the notesStmt element. -

    The annot element can be used for both general comments and for +

    The annot element can be used for both general comments and for annotations of the musical text. It provides a way to group participating *events* and/or *control events*, for example, the notes that form a descending bass line, and provide a label for and comment regarding the group. Participating entities may be identified in the - plist attribute. An editorial or analytical comment or observation may be + plist attribute. An editorial or analytical comment or observation may be included directly within the annot element. The starting point of the - annotation may be indicated by either a tstamp, tstamp.ges, - tstamp.real or startid attribute, while the ending point may be - recorded by either a dur, dur.ges or endid attribute. The - resp attribute records the editor(s) responsible for identifying or creating - the annotation.

    + annotation may be indicated by either a tstamp, tstamp.ges, + tstamp.real or startid attribute, while the ending point may be + recorded by either a dur, dur.ges or endid attribute. The + resp attribute records the editor(s) responsible for identifying or creating the + annotation.

         - + A person or organization who transcribes a musical composition, usually for a different medium from that of the original; in an arrangement the musical substance remains essentially unchanged. - - - - - - - - - - + + + + + + + + + + @@ -32062,42 +20442,42 @@ - + (articulation) – An indication of how to play a note or chord. - - - - - - - - - - - - - - -

    Articulations typically affect duration, such as staccato marks, or the force of attack, - such as accents. This element provides an alternative to the artic attribute on + + + + + + + + + + + + + + +

    Articulations typically affect duration, such as staccato marks, or the force of attack, + such as accents. This element provides an alternative to the artic attribute on the note and chord elements. It may be used when specific display info, such as size or color, needs to be recorded for the articulation or when multiple articulation marks occur on a single note or chord.

         - + The name of the creator of the intellectual content of a non-musical, literary work. - - - - - - - - - - + + + + + + + + + + @@ -32105,30 +20485,30 @@ -

    This element is modelled on elements in the Text Encoding Initiative (TEI) and Encoded +

    This element is modelled on elements in the Text Encoding Initiative (TEI) and Encoded Archival Description (EAD) standards.

         - + Vertical line drawn through one or more staves that divides musical notation into metrical units. - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + - + The value of @taktplace must be less than or equal to two times the number of staff @@ -32137,26 +20517,26 @@ -

    This element is provided for repertoires, such as mensural notation, that lack measures. +

    This element is provided for repertoires, such as mensural notation, that lack measures. Because the barLine element's attributes, from which the logical and visual characteristics of the bar line can be discerned, largely duplicate those of measure, the use of barLine is not necessary within measure elements in CMN.

         - + (bibliographic reference) – Provides a loosely-structured bibliographic citation in which the sub-components may or may not be explicitly marked. - - - - - - - - - - + + + + + + + + + + @@ -32165,46 +20545,33 @@ - - + + -

    - bibl may contain a mix of text and more specific elements such as title, edition, persName, +

    bibl may contain a mix of text and more specific elements such as + title, edition, persName, and corpName. This element may also function as a hypertext reference to an external electronic resource. Do not confuse this element with ref, which does not provide special bibliographic sub-elements.

     -

    This element is modelled on elements in the Text Encoding Initiative (TEI) and Encoded +

    This element is modelled on elements in the Text Encoding Initiative (TEI) and Encoded Archival Description (EAD) standards.

         - + List of bibliographic references. - - - - - - - - - + + + + + + + + + - + @@ -32216,64 +20583,98 @@ - + - + When labels are used, usually each bibliographic item has one. -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (scope of citation) – Defines the scope of a bibliographic reference, for example as a list of page numbers, or a named subdivision of a larger work. - - - - - - - - - - + + + + + + + + + + - - - - + + + + - - - + + + -

    Use the from and to attributes to regularize the beginning and ending +

    Use the from and to attributes to regularize the beginning and ending values provided in the element content.

    -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    -     +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    + +     + + (structured bibliographic citation) – Contains a bibliographic citation in which + bibliographic sub-elements must appear in a specified order. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - + Contains the whole of a single musical text, excluding any front or back matter. - - - - + + + + - - + + @@ -32281,64 +20682,64 @@ -

    When the music can be broken into high-level, discrete, linear segments, such as movements +

    When the music can be broken into high-level, discrete, linear segments, such as movements of a symphony, there may be multiple mdiv elements within body. This is the highest level indication of the structure of the music.

    -

    The content model of body also allows blocks of text and music +

    The content model of body also allows blocks of text and music notation to be interleaved. This permits the encoding of a wide range of musical documents, including those that are primarily textual with only occasional musical material or even those which completely lack music notation.

         - + Break, pause, or interruption in the normal tempo of a composition. Typically indicated by "railroad tracks", i.e., two diagonal slashes. - - - - - - - - - - - - - + + + + + + + + + + + + + - + Must have one of the attributes: startid, tstamp, tstamp.ges or tstamp.real. -

    The caesura often indicates an abrupt interruption in the performance followed by an +

    The caesura often indicates an abrupt interruption in the performance followed by an equally sudden resumption. Its duration is typically shorter than a grand pause (G.P.) or long pause (L.P.), but longer than that indicated by a breath mark. When combined with a fermata a longer silence is usually implied. The - starting point of the caesura may be indicated by either a startid, - tstamp, tstamp.ges, or tstamp.real attribute. It is a + starting point of the caesura may be indicated by either a startid, + tstamp, tstamp.ges, or tstamp.real attribute. It is a semantic error not to specify a starting point attribute.

    -

    Unlike the breath mark, a caesura may have a performed duration. - Also, while the default value for place on the breath mark is "above", the - default value for place for a caesura is "within". Unless indicated by other +

    Unlike the breath mark, a caesura may have a performed duration. + Also, while the default value for place on the breath mark is "above", the + default value for place for a caesura is "within". Unless indicated by other attributes, a caesura will be rendered as a pair of slanted lines through the top line of the staff.

    -

    +

    - + A label which accompanies an illustration or a table. - - - - - - - - + + + + + + + + @@ -32348,15 +20749,15 @@ - + (cast group) – Groups one or more individual castItem elements within a cast list. - - - - + + + + - - + + @@ -32365,20 +20766,20 @@ -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Contains a single entry within a cast list, describing either a single role or a list of non-speaking roles. - - - - - - - - + + + + + + + + @@ -32389,23 +20790,23 @@ -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Contains a single cast list or dramatis personae. - - - - - - - - - + + + + + + + + + - + @@ -32413,36 +20814,37 @@ -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - - (column break) – An empty formatting element that forces text to begin in a new + + (column beginning) – An empty formatting element that forces text to begin in a new column. - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + Records the column number. - - + + - + - + - Column break must be preceded by a + Column beginning must be preceded by a colLayout element. The value of @n should be less than or equal to the value of @cols () of the preceding @@ -32453,23 +20855,23 @@ -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + A simultaneous sounding of two or more notes in the same layer *with the same duration*. - - - - - - - - - - - + + + + + + + + + + + @@ -32481,35 +20883,35 @@ - + Indication of the exact location of a particular note on the staff and, therefore, the other notes as well. - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + - + The clef position must be less than or equal to the number of lines of an ancestor staff. - + - + The clef position must be less than or equal to the number of lines of a preceding staff. @@ -32517,65 +20919,65 @@ -

    This element can be used as an alternative to the staff element's +

    This element can be used as an alternative to the staff element's clef.* attributes. It should be used when specific display info, such as size or color, needs to be recorded for the clef or when multiple, simultaneous clefs occur on a single staff. This element may also be used within the staff context to indicate changes of clef.

         - + (clef group) – A set of simultaneously-occurring clefs. - - - - - - - - - - - - - + + + + + + + + + + + + + - + (column layout) – An empty formatting element that signals the start of columnar layout. - - - - - + + + + + - - + + - - + + Records the number of columns. - - + + - + The name of the creator of the intellectual content of a musical work. - - - - - - - - - - + + + + + + + + + + @@ -32583,64 +20985,64 @@ - + Names of individuals, institutions, or organizations responsible for contributions to the intellectual content of a work, where the specialized elements for authors, editors, etc. do not suffice or do not apply. - - - - - - - - - - + + + + + + + + + + - + - + The value of @role must not contain the name of another element available in this context. - - + + Used to specify the contributor's function. - - + + -

    When applicable, values from the MARC relator term list (http://www.loc.gov/marc/relators/relaterm.html) or code list (http://www.loc.gov/marc/relators/relacode.html) are recommended for - role.

    +

    When applicable, values from the MARC relator term list (http://www.loc.gov/marc/relators/relaterm.html) or code list (http://www.loc.gov/marc/relators/relacode.html) are recommended for + role.

         - + Non-bibliographic details of the creation of an intellectual entity, in narrative form, such as the date, place, and circumstances of its composition. More detailed information may be captured within the history element. - - - - - - - - - - + + + + + + + + + + - + @@ -32649,45 +21051,45 @@ -

    This element is modelled on an element in the Text Encoding Initiative (TEI).

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI).

         - + Symbol placed at the end of a line of music to indicate the first note of the next line. Sometimes called a "direct". - - - - - - - - - + + + + + + + + + - - + + -

    The most common visual form is a sign resembling a mordent. Other graphical forms may be - indicated by the altsym attribute. Together the pname and - oct attributes identify the location where the custos appears.

    +

    The most common visual form is a sign resembling a mordent. Other graphical forms may be + indicated by the altsym attribute. Together the pname and + oct attributes identify the location where the custos appears.

         - + A string identifying a point in time or the time period between two such points. - - - - - - - - - - - - + + + + + + + + + + + + @@ -32695,47 +21097,47 @@ -

    This element is modelled on elements in the Text Encoding Initiative (TEI) and Encoded +

    This element is modelled on elements in the Text Encoding Initiative (TEI) and Encoded Archival Description (EAD) standards.

         - + Entity to whom a creative work is formally offered. - - - - - - - - - + + + + + + + + + - + - + The dedicatee element may not be recursively nested. - + Description of a measurement taken through a three-dimensional object. - - - - - - - - - + + + + + + + + + @@ -32743,19 +21145,19 @@ - + (description) – Container for text that briefly describes the feature to which it is attached, including its intended usage, purpose, or application as appropriate. - - - - - - - - - - + + + + + + + + + + @@ -32765,97 +21167,97 @@ -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (dimension) – Any single dimensional specification. - - - - - - - - - + + + + + + + + + - - + + Aspect of the object being measured. - - + + - - + + Altitude. Refers to the distance above a given level, commonly mean sea level. - + Angle. Amount of rotation needed to bring one line or plane into coincidence with another. - + Circumference of a circular area. - + Dimension taken through an object or body of material, usually downward from an upper surface, horizontally inward from an outer surface, or from top to bottom of something regarded as one of several layers. - + Length of a straight line passing through the center of a circle or sphere and meeting the circumference or surface at each end. - + Distance to which something has been raised or uplifted above a level, e.g. a hill's elevation above the surrounding country. - + Denotes extent upward (as from foot to head) as well as any measurable distance above a given level. - + Measure of the greatest dimension of a plane or solid figure. - + Half the diameter of a circular, spherical, or cylindrical object. - + Projection of a figure or part from the plane on which it is formed. - + Extent from side to side; breadth. -

    The height, width, and depth elements are preferred when appropriate.

    +

    The height, width, and depth elements are preferred when appropriate.

         - + Information about the physical size of an entity; usually includes numerical data. - - - - - - - - - - - - - + + + + + + + + + + + + + - + The depth element may only appear once. The height element may only appear @@ -32866,33 +21268,32 @@ -

    The elements height, width, depth, and dim are available for circumstances that require - the capture of the individual dimensions of an object. Do not confuse this element with the - extent element, which is used to indicate the quantity of described +

    The elements height, width, depth, and dim are available for circumstances that require the + capture of the individual dimensions of an object. Do not confuse this element with the extent element, which is used to indicate the quantity of described materials.

     -

    This element is modelled on elements in the Text Encoding Initiative (TEI) and Encoded +

    This element is modelled on elements in the Text Encoding Initiative (TEI) and Encoded Archival Description (EAD) standards.

         - + (directive) – An instruction expressed as a combination of text and symbols — such as segno and coda symbols, fermatas over a bar line, etc., typically above, below, or between staves, but not on the staff — that is not encoded elsewhere in more specific elements, like - tempo or dynam. - - - - - - - - - - - - + tempo or dynam.     + + + + + + + + + + + + @@ -32902,37 +21303,37 @@ - + - + Must have one of the attributes: startid, tstamp, tstamp.ges or tstamp.real. -

    Examples include text strings, such as 'affettuoso', and music symbols, such as segno and +

    Examples include text strings, such as 'affettuoso', and music symbols, such as segno and coda symbols, fermatas over a bar line, etc. Directives can be control elements. That is, they can be linked via their attributes to other events. The starting point of the directive - may be indicated by either a startid, tstamp, tstamp.ges, - or tstamp.real attribute, while the ending point may be recorded by either a - dur, dur.ges, endid, or tstamp2 attribute. It - is a semantic error not to specify a starting point attribute.

    + may be indicated by either a startid, tstamp, tstamp.ges, + or tstamp.real attribute, while the ending point may be recorded by either a + dur, dur.ges, endid, or tstamp2 attribute. It is + a semantic error not to specify a starting point attribute.

         - + Person or agency, other than a publisher, from which access (including electronic access) to a bibliographic entity may be obtained. - - - - - - - - - - + + + + + + + + + + @@ -32940,31 +21341,32 @@ -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (division) – Major structural division of text, such as a preface, chapter or section. - - - - - - - - - - - - - + + + + + + + + + + + + + + - + @@ -32976,57 +21378,57 @@ - - + + Characterizes the textual division in some sense, using any convenient classification scheme or typology that employs single-token labels. - - + + - - + + A summary of the content of a text as continuous prose. - + A formal declaration of acknowledgment by the author in which persons and institutions are thanked for their part in the creation of a text. - + An ancillary self-contained section of a work, often providing additional but in some sense extra-canonical text. - + A list of bibliographic citations. - + A statement appearing at the end of a book describing the conditions of its physical production. - + A table of contents, specifying the structure of a work and listing its constituents. The list element should be used to mark its structure. - + A formal offering or dedication of a text to one or more persons or institutions by the author. - + A pictorial frontispiece, possibly including some text. - + A list of terms associated with definition texts (‘glosses’). - + A page containing only the title of a book — as opposed to the title page, which also lists subtitle, author, imprint and similar data. - + Any form of index to the work. - + A section in which annotations on the text are gathered together. - + A foreword or preface addressed to the reader in which the author or publisher explains the content, purpose, or origin of the text. @@ -33034,44 +21436,44 @@ -

    Often, the head sub-element identifies the div's purpose. This element is modelled on an element in the Text Encoding Initiative +

    Often, the head sub-element identifies the div's purpose. This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Dot of augmentation or division. - - - - - - - - + + + + + + + + - - + + -

    This element provides an alternative to the dots attribute on note and rest elements. It should be used when specific - display info, such as size or color, needs to be recorded for the dot. This element may also - be used for dots of division in the mensural repertoire.

    +

    This element provides an alternative to the dots attribute on note and rest elements. It should be used when specific display + info, such as size or color, needs to be recorded for the dot. This element may also be used + for dots of division in the mensural repertoire.

         - + (dynamic) – Indication of the volume of a note, phrase, or section of music. - - - - - - - - - - - - + + + + + + + + + + + + @@ -33080,48 +21482,48 @@ - + - + Must have one of the attributes: startid, tstamp, tstamp.ges or tstamp.real. - + - + When @val2 is present, either @dur, @dur.ges, @endid, or @tstamp2 must also be present. -

    This element may be used for instantaneous or continuous textual dynamics, +

    This element may be used for instantaneous or continuous textual dynamics, e.g. 'p', 'mf', or 'cresc. poco a poco'. The hairpin element should be used for graphical, i.e., crescendo and diminuendo, dynamic markings. The - starting point of the dynamic marking may be indicated by either a startid, - tstamp, tstamp.ges, or tstamp.real attribute, while the - ending point may be recorded by either a dur, dur.ges, - endid, or tstamp2 attribute. It is a semantic error not to specify a + starting point of the dynamic marking may be indicated by either a startid, + tstamp, tstamp.ges, or tstamp.real attribute, while the + ending point may be recorded by either a dur, dur.ges, + endid, or tstamp2 attribute. It is a semantic error not to specify a starting point attribute. MIDI values associated with the graphical dynamic sign may be - recorded in the val and val2 attributes.

    + recorded in the val and val2 attributes.

         - + (edition designation) – A word or text phrase that indicates a difference in either content or form between the item being described and a related item previously issued by the same publisher/distributor (e.g. 2nd edition, version 2.0, etc.), or simultaneously issued by either the same publisher/distributor or another publisher/distributor (e.g. large print edition, British edition, etc.). - - - - - - - - + + + + + + + + @@ -33132,23 +21534,23 @@ -

    This element is modelled on elements in the Text Encoding Initiative (TEI) and Encoded +

    This element is modelled on elements in the Text Encoding Initiative (TEI) and Encoded Archival Description (EAD) standards.

         - + The name of the individual(s), institution(s) or organization(s) acting in an editorial capacity. - - - - - - - - - - + + + + + + + + + + @@ -33156,28 +21558,28 @@ -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Alternative ending for a repeated passage of music; i.e., prima volta, seconda volta, etc. - - - - - - - - - - - - - + + + + + + + + + + + + + - + @@ -33195,30 +21597,30 @@ -

    The scoreDef element is allowed as a sub-element so that an ending +

    The scoreDef element is allowed as a sub-element so that an ending may have its own meta-data without the overhead of child section elements. div sub-elements are not allowed within ending. They may, however, be contained by the children of ending, e.g., measures. Endings may not contain other ending elements.

         - + Contains a free-text event description. - - - - - - - - - - - + + + + + + + + + + + - - + + @@ -33226,38 +21628,37 @@ - + - + - - + + - + Contains historical information given as a sequence of significant past events. - - - - - - - - + + + + + + + + - + - + @@ -33267,62 +21668,62 @@ - + - - + + -

    An eventList contains event elements that +

    An eventList contains event elements that capture a brief description of the associated event, including dates and locations where the event took place. An eventList describes events associated with a work - when it appears in the workDesc element or events associated with the + when it appears in the workList element or events associated with the custodial history of a given copy of a source for the encoding when it appears within the - source or relatedItem elements. The - type attribute may be used to distinguish between event lists with different + sourceDesc or relatedItem elements. The + type attribute may be used to distinguish between event lists with different functions, such as a list of events in the compositional process and a list of performance dates.

         - + Indicates how a section may be programmatically expanded into its 'through-composed' form. - - - - - + + + + + - - + + -

    The plist attribute contains an ordered list of identifiers of descendant section, ending, lem, or rdg elements. For example, the sequence "#A #End1 #A #End2" indicates - that the section labelled 'A' comes first, then the ending labelled 'End1', followed by the - 'A' section again, and finally the ending labelled 'End2'.

    +

    The plist attribute contains an ordered list of identifiers of descendant section, ending, lem, or rdg elements. For example, the sequence "#A #End1 #A #End2" indicates that + the section labelled 'A' comes first, then the ending labelled 'End1', followed by the 'A' + section again, and finally the ending labelled 'End2'.

         - + Used to express size in terms other than physical dimensions, such as number of pages, records, bytes, physical components, etc. - - - - - - - - - - - + + + + + + + + + + + @@ -33330,28 +21731,28 @@ -

    Use the dimensions element when it is necessary to specify the physical size of materials being described, for example, height and +

    Use the dimensions element when it is necessary to specify the physical size of materials being described, for example, height and width.

     -

    This element is modelled on elements in the Text Encoding Initiative (TEI) and Encoded +

    This element is modelled on elements in the Text Encoding Initiative (TEI) and Encoded Archival Description (EAD) standards.

         - + Names of individuals, institutions, or organizations responsible for funding. Funders provide financial support for a project; they are distinct from sponsors, who provide intellectual support and authority. - - - - - - - - - - + + + + + + + + + + @@ -33359,22 +21760,22 @@ -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Term or terms that designate a category characterizing a particular style, form, or content. - - - - - - - - - - + + + + + + + + + + @@ -33382,21 +21783,21 @@ - + Contains a composite musical text, grouping together a sequence of distinct musical texts (or groups of such musical texts) which are regarded as a unit for some purpose, for example, the collected works of a composer. - - - - + + + + - - + + - + @@ -33404,63 +21805,63 @@ -

    Because its model contains the music element, each of the subordinate MEI documents can +

    Because its model contains the music element, each of the subordinate MEI documents can have its own front and back matter.

     -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (group symbol) – A brace or bracket used to group two or more staves of a score or part. - - - - - - - - - - + + + + + + + + + + - + - + In scoreDef, grpSym must have startid, endid, and level attributes. - + - + In staffGrp, grpSym must not have startid, endid, or level attributes. -

    This element provides an alternative to the staffGrp element's - symbol attribute. It may be used when exact placement or editorial details for +

    This element provides an alternative to the staffGrp element's + symbol attribute. It may be used when exact placement or editorial details for the grouping symbol must be recorded.

         - + (heading) – Contains any heading, for example, the title of a section of text, or the heading of a list. - - - - - - - - - + + + + + + + + + @@ -33470,25 +21871,25 @@ -

    One or more head elements usually identify the parent element and/or +

    One or more head elements usually identify the parent element and/or its purpose.

     -

    This element is modelled on elements in Encoded Archival Description (EAD), Text Encoding +

    This element is modelled on elements in Encoded Archival Description (EAD), Text Encoding Initiative (TEI), and HTML standards.

         - + Description of the vertical size of an object. - - - - - - - - - + + + + + + + + + @@ -33496,17 +21897,17 @@ - + An alpha-numeric string that establishes the identity of the described material. - - - - - - - - - + + + + + + + + + @@ -33516,23 +21917,23 @@ -

    Examples include an International Standard Book/Music Number, Library of Congress Control +

    Examples include an International Standard Book/Music Number, Library of Congress Control Number, publisher's number, a personal identification number, an entry in a bibliography or - catalog, etc. The type attribute may be used to indicate the system from which + catalog, etc. The type attribute may be used to indicate the system from which the identifier was derived.

         - + Information relating to the publication or distribution of a bibliographic item. - - - - - - - - - + + + + + + + + + @@ -33543,52 +21944,50 @@ -

    This element is modelled on an element in the Text Encoding Initiative (TEI) and Encoded +

    This element is modelled on an element in the Text Encoding Initiative (TEI) and Encoded Archival Description (EAD) standards.

         - - (incipit) – The opening music and/or words of a composition. - - - - + + (incipit) – The opening music and/or words of a musical or textual work. + + + + - - - + + + - + - + - + - + - + - + - + - + @@ -33599,104 +21998,104 @@ -

    The incipText element may be used to capture a text incipit, while - score is available to provide an MEI-encoded musical incipit. Images +

    The incipText element may be used to capture a text incipit, while + score is available to provide an MEI-encoded musical incipit. Images of an incipit may be referenced using the graphic element. An incipit encoded in a text format other than MEI may be placed in the incipCode element.

         - + (key accidental) – Accidental in a key signature. - - - - - - - - - - - - - + + + + + + + + + + + + + - + One of the following is required: @x and @y attribute pair, @pname attribute, or @loc attribute. - - + + Specifies whether enharmonic (written) values or implicit ("perform-able") values are allowed. - - + + Only performed values (sharp, flat, natural) allowed. - + All enharmonic (written) values allowed. -

    It is a semantic error not to provide one of the following: the x and - y pair of attributes, the pname and oct pair of - attributes, or the loc attribute.

    +

    It is a semantic error not to provide one of the following: the x and + y pair of attributes, the pname and oct pair of attributes, + or the loc attribute.

         - + (key signature) – Written key signature. - - - - - - - - - - - + + + + + + + + + + + - + - + If the @oct attribute appears on any keyAccid element, it must be provided on all keyAccid elements. - + - + Only keyAccid elements are allowed here. - + A container for document text that identifies the feature to which it is attached. For a - "tool tip" or other generated label, use the label attribute. - - - - - - - - - + "tool tip" or other generated label, use the label attribute. + + + + + + + + + @@ -33706,24 +22105,24 @@ -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    -

    Don't confuse this element, which is used to capture labelling text appearing in the - document, with the label attribute, which records text to be used to generate a +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    Don't confuse this element, which is used to capture labelling text appearing in the + document, with the label attribute, which records text to be used to generate a designation for the element to which it's attached, a "tool tip" or prefatory text, for example.

         - + A label on the pages following the first. - - - - - - - - - + + + + + + + + + @@ -33733,24 +22132,25 @@ - + An independent stream of events on a staff. - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + @@ -33763,103 +22163,92 @@ -

    The term 'layer' is used instead of 'voice' in order to avoid confusion between 'voice' and - 'voice leading' and 'voicing'. The def attribute may be used to create a +

    The term 'layer' is used instead of 'voice' in order to avoid confusion between 'voice' and + 'voice leading' and 'voicing'. The def attribute may be used to create a connection with a layerDef element where logical and visual - information about the layer is recorded. Alternatively, the n attribute may be + information about the layer is recorded. Alternatively, the n attribute may be used as a reference to a layerDef element with the same value in its - n attribute. If neither def nor n attributes are present, + n attribute. If neither def nor n attributes are present, then encoding order of the layers is presumed to match the encoding order of the layer definitions.

         - + (layer definition) – Container for layer meta-information. - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + - + - + - - (line break) – An empty formatting element that forces text to begin on a new line. - - - - - + + (line beginning) – An empty formatting element that forces text to begin on a new + line. + + + + + - - + + - - - States whether the line break follows a single line or a line group. - - - Follows a verse line. - - - Follows a group of verse lines. - - - - -

    The n attribute should be used to record a number associated with this textual - line. See comment on verse element for description of func +

    The n attribute should be used to record a number associated with this textual + line. See comment on verse element for description of func attribute. Do not confuse this element with the sb element, which performs a similar function for musical notation.

     -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (line group) – May be used for any section of text that is organized as a group of lines; however, it is most often used for a group of verse lines functioning as a formal unit, e.g. a stanza, refrain, verse paragraph, etc. - - - - - - - - - - - - - + + + + + + + + + + + + + - + - + @@ -33867,21 +22256,21 @@ -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Person or organization who is a writer of the text of an opera, oratorio, etc. - - - - - - - - - - + + + + + + + + + + @@ -33889,18 +22278,18 @@ - + Person or organization who is a writer of the text of a song. - - - - - - - - - - + + + + + + + + + + @@ -33908,20 +22297,20 @@ - + (musical division) – Contains a subdivision of the body of a musical text. - - - - - - - - - - - - + + + + + + + + + + + + @@ -33936,77 +22325,157 @@ -

    The mdiv element may contain one or both of 2 possible views of the +

    The mdiv element may contain one or both of 2 possible views of the music. The score view is the traditional full and open score while the parts view contains each performer's view of the score; that is, his part. These 2 views are necessary because - it is not always possible or desirable to generate one from the other. The score and parts elements are placed here and not directly - within the body element because score and part characteristics may - change from mdiv to mdiv. For example, the 2nd - movement of a symphony may require different performing forces (and therefore different - score and part layout) than the other movements. The mdiv element may - be recursively nested in order to represent music which exhibits this kind of structure. For + it is not always possible or desirable to generate one from the other. The score and parts elements are placed here and not directly within + the body element because score and part characteristics may change + from mdiv to mdiv. For example, the 2nd movement + of a symphony may require different performing forces (and therefore different score and + part layout) than the other movements. The mdiv element may be + recursively nested in order to represent music which exhibits this kind of structure. For example, an opera is normally divided into acts, which are in turn divided into scenes.

         - + Contains a single MEI-conformant document, consisting of an MEI header and a musical text, either in isolation or as part of an meiCorpus element. - - - + + + + - - - + + + - + - + The values in @staff must correspond to @n attribute of a staffDef element. -

    The mei element defines an instance of a document encoded with the +

    The mei element defines an instance of a document encoded with the MEI schema. It is the document element for a single document containing a header and data. The name of this element should not be changed by any customization in order to assure an absolute minimum level of MEI compliance.

         - + + (monograph level) – Contains bibliographic elements describing an item, for example, a + published book or journal, score, recording, or an unpublished manuscript. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Contains a single musical text of any kind, whether unitary or composite, for example, an etude, opera, song cycle, symphony, or anthology of piano solos. - - - - + + + + - - + + - + - + Proper noun or noun phrase. - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + @@ -34015,81 +22484,80 @@ - + - + Recommended practice is to use name elements to capture sub-parts of a generic name. - - + + Characterizes the name in some sense, using any convenient classification scheme or typology that employs single-token labels. - - + + - - + + A personal name. - + Name of a corporate body. - + Name of a location. - + Name of a process or software application. - + Name of a musical style; i.e., form, genre, technique, etc. - + Name of a period of time. -

    Contains the name of an entity that is difficult to tag more specifically, for example, as +

    Contains the name of an entity that is difficult to tag more specifically, for example, as a corpName, geogName, persName, or title. The name element may be used in place of the more specific elements when it is not known what kind of name is being described or when a high degree of precision is not necessary. For example, the name element might be used when it is not clear whether the name "Bach" refers to a person or a geographic feature. The name element may be used for an individual, such as 'Henry VIII, King of England'; a corporate body, such as 'The Beatles'; a geographical place; an expanse of time, such as 'The Romantic Era'; or a - mechanical (often generative) process. When name parts are needed, name sub-elements are recommended. The recommended values for the type + mechanical (often generative) process. When name parts are needed, name sub-elements are recommended. The recommended values for the type attribute are: person, corporation, location, period, and process. Dates associated with - the name (not necessarily the same as those pertaining to the entity - described by the name) may be recorded using startdate, - enddate, notbefore, notafter, and isodate + the name (not necessarily the same as those pertaining to the entity + described by the name) may be recorded using startdate, + enddate, notbefore, notafter, and isodate attributes. The name of the list from which a controlled value is taken, such as the Thesaurus of Geographic Names (TGN) or Library of Congress Name Authority File (LCNAF), and - its electronically-available location may be recorded using the auth and - auth.uri attributes.

    + its electronically-available location may be recorded using the auth and + auth.uri attributes.

     -

    This element is modelled on an element in the Encoded Archival Description (EAD) +

    This element is modelled on an element in the Encoded Archival Description (EAD) standard.

         - - A single pitched event. - - - - - - - - - - - - - + + A single pitched event. + + + + + + + + + + + + @@ -34101,30 +22569,30 @@ -

    The accid and artic sub-elements may be used +

    The accid and artic sub-elements may be used instead of the note element's attributes when accid and artic represent first-class objects, - e.g., when they require attributes, such as x and y location + e.g., when they require attributes, such as x and y location attributes. Similarly, the syl sub-element may be used instead of the - syl attribute. The verse sub-element may be used to group text syllables by - verse. The colored attribute may be used to indicate coloration. In the mensural + syl attribute. The verse sub-element may be used to group text syllables by + verse. The colored attribute may be used to indicate coloration. In the mensural repertoire, coloration is a temporary change in the underlying mensuration from perfect to imperfect. In the CMN repertoire, coloration is an inversion of the note head's normal rendition, that is, the note head is void when it would otherwise be filled and vice versa. Do not confuse this with visual color.

         - + (number) – Numeric information in any form. - - - - - - - - - - + + + + + + + + + + @@ -34133,33 +22601,33 @@ - - + + Numeric value capturing a measurement or count. Can only be interpreted in combination with the unit attribute. - - + + -

    Use this element only when it is necessary to display a number in a special way or to - identify it with a type attribute.

    +

    Use this element only when it is necessary to display a number in a special way or to + identify it with a type attribute.

         - + An element indicating an ornament that is not a mordent, turn, or trill. - - - - - - - - - - - + + + + + + + + + + + @@ -34169,34 +22637,34 @@ - + - + Must have one of the attributes: startid, tstamp, tstamp.ges or tstamp.real. -

    The glyph of the ornament may be indicated with the altsym attribute, and it is - recommended to provide an expansion of the ornament on the staff content. The starting point - of the ornament may be indicated by either a startid, tstamp, - tstamp.ges, or tstamp.real attribute. It is a semantic error not to - specify one of these attributes.

    +

    If it is not textual, the glyph of the ornament may be indicated with the altsym + attribute, and it is recommended to provide an expansion of the ornament on the staff content. + The starting point of the ornament may be indicated by either a startid, + tstamp, tstamp.ges, or tstamp.real attribute. It is a semantic + error not to specify one of these attributes.

         - + (paragraph) – One or more text phrases that form a logical prose passage. - - - - - - - - - - + + + + + + + + + + @@ -34204,42 +22672,42 @@ -

    A paragraph is usually typographically distinct: The text usually begins on a new line and +

    A paragraph is usually typographically distinct: The text usually begins on a new line and the first letter of the content is often indented, enlarged, or both.

     -

    This element is modelled on elements in the Encoded Archival Description, Text Encoding +

    This element is modelled on elements in the Encoded Archival Description, Text Encoding Initiative (TEI), and HTML standards.

         - + (padding) – An indication of extra visual space between notational elements. - - - - - - - + + + + + + + - - + + - + An alternative visual rendition of the score from the point of view of a particular performer (or group of performers). - - - - - - - - - - - + + + + + + + + + + + @@ -34255,9 +22723,8 @@ -

    - part elements are not used in MEI to indicate voice leading. - next attributes on event elements should be used for this purpose. part elements are useful for encoding individual parts when there is no +

    part elements are not used in MEI to indicate voice leading. + next attributes on event elements should be used for this purpose. part elements are useful for encoding individual parts when there is no score, such as early music part books, when the music has non-aligning bar lines, when different layout, such as page turns, are needed for the score and parts, or for accommodating software that requires part-by-part encoding. When assembly of the parts into @@ -34266,59 +22733,60 @@ be marked as 'non-controlling'.

         - + Provides a container for performers' parts. - - - - - - - - - - - + + + + + + + + + + + - - (page break) – An empty formatting element that forces text to begin on a new page. - - - - - - - - - - - - - - - -

    The n attribute should be used to record the page number displayed in the + + (page beginning) – An empty formatting element that forces text to begin on a new + page. + + + + + + + + + + + + + + + +

    The n attribute should be used to record the page number displayed in the source. It need not be an integer, e.g., 'iv', or 'p17-3'. The logical page number can be calculated by counting previous pb ancestor elements. When used in a - score context, a page break implies an accompanying system break.

    + score context, a page beginning implies an accompanying system beginning.

     -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (page description) – Contains a brief prose description of the appearance or description of the content of a physical page. - - - - + + + + - - + + @@ -34329,21 +22797,21 @@ -

    Best practice suggests the use of controlled vocabulary. Don't confuse this element with a +

    Best practice suggests the use of controlled vocabulary. Don't confuse this element with a figure caption. A caption is text primarily intended for display with an illustration. It may or may not function as a description of the illustration.

         - + (page footer) – A running footer on the first page. Also, used to temporarily override a running footer on individual pages. - - - - + + + + - - + + @@ -34355,31 +22823,31 @@ - - + + Records horizontal alignment of the page footer. - - + + -

    This element is used to capture the textual data that often appears on the first page of +

    This element is used to capture the textual data that often appears on the first page of printed music. It may also be used for similarly formatted material in manuscripts. When used within pb, it records a temporary suspension of the pattern of page footers established by the use of pgFoot within a previous scoreDef. Auto-generated page numbers may be indicated with a processing instruction. The pgHead, pgHead2, pgFoot, and pgFoot2 elements should *not* be used to encode textual notes/annotations.

         - + (page footer 2) – A running footer on the pages following the first. - - - - + + + + - - + + @@ -34391,33 +22859,33 @@ - - + + Records horizontal alignment of the page footer. Use multiple values to capture an alternating pattern. - - + + -

    This element is used to capture the textual data that often appears on the second and +

    This element is used to capture the textual data that often appears on the second and succeeding pages of printed music. It may also be used for similarly formatted material in manuscripts. Auto-generated page numbers may be indicated with a processing instruction. The pgHead, pgHead2, pgFoot, and pgFoot2 elements should *not* be used to encode textual notes/annotations.

         - + (page header) – A running header on the first page. Also, used to temporarily override a running header on individual pages. - - - - + + + + - - + + @@ -34429,31 +22897,31 @@ - - + + Records horizontal alignment of the page header. - - + + -

    This element is used to capture the textual data that often appears on the first page of +

    This element is used to capture the textual data that often appears on the first page of printed music. It may also be used for similarly formatted material in manuscripts. When used within pb, it records a temporary suspension of the pattern of page headers established by the use of pgHead within a previous scoreDef. Auto-generated page numbers may be indicated with a processing instruction. The pgHead, pgHead2, pgFoot, and pgFoot2 elements should *not* be used to encode textual notes/annotations.

         - + (page header 2) – A running header on the pages following the first. - - - - + + + + - - + + @@ -34465,41 +22933,41 @@ - - + + Records horizontal alignment of the page header. Use multiple values to capture an alternating pattern. - - + + -

    This element is used to capture the textual data that often appears at the top of the +

    This element is used to capture the textual data that often appears at the top of the second and succeeding pages of printed music. It may also be used for similarly formatted material in manuscripts. Auto-generated page numbers may be indicated with a processing instruction. The pgHead, pgHead2, pgFoot, and pgFoot2 elements should *not* be used to encode textual notes/annotations.

         - + Indication of 1) a "unified melodic idea" or 2) performance technique. - - - - - - - - - - - + + + + + + + + + + + - + - + Must have one of the attributes: startid, tstamp, tstamp.ges or tstamp.real. Must have one of the attributes: @@ -34507,9 +22975,9 @@ - + - + The visual attributes of the phrase (@bezier, @bulge, @curvedir, @lform, @lwidth, @ho, @startho, @endho, @to, @startto, @endto, @vo, @startvo, @endvo, @x, @y, @x2, and @y2) will be overridden by visual attributes of the contained curve @@ -34518,38 +22986,37 @@ -

    Historically, the term "slur" indicated two notes performed legato, while the term "phrase" +

    Historically, the term "slur" indicated two notes performed legato, while the term "phrase" was used for a "unified melodic idea". Nowadays, however, "slur" often has the same meaning as "phrase" (See Read, p. 265-266), since the visual rendition of the two concepts is the same. MEI provides two distinct elements so that those users wishing to maintain a distinction for historical reasons may do so. If the user does not want to maintain the distinction, then the more generic slur element should be employed. - The starting point of the phrase/slur may be indicated by either a startid, - tstamp, tstamp.ges, or tstamp.real attribute, while the - ending point may be recorded by either a dur, dur.ges, - endid, or tstamp2 attribute. It is a semantic error not to specify - one starting and one ending type of attribute. Either place, bulge, or - bezier attributes may be used to record the curvature of the phrase/slur. The - slur and tie elements may be used instead of - the slur.* and tie.* attributes provided on chord and note elements when 1) they are required by software, or 2) multiple, alternative - slurs are needed.

    -     -     - + The starting point of the phrase/slur may be indicated by either a startid, + tstamp, tstamp.ges, or tstamp.real attribute, while the + ending point may be recorded by either a dur, dur.ges, + endid, or tstamp2 attribute. It is a semantic error not to specify one + starting and one ending type of attribute. Either place, bulge, or + bezier attributes may be used to record the curvature of the phrase/slur. The slur and tie elements may be used instead of the + slur.* and tie.* attributes provided on chord and note elements when 1) they are required by software, or 2) multiple, alternative slurs + are needed.

    + +     + (physical location) – Groups information about the current physical location of a bibliographic item, such as the repository in which it is located and its shelf mark(s), and its previous locations. - - - - - - - - + + + + + + + + - + @@ -34557,27 +23024,27 @@ - + -

    This element is modelled on an element in the Encoded Archival Description (EAD) +

    This element is modelled on an element in the Encoded Archival Description (EAD) standard.

         - + Name of the organization responsible for the publication of a bibliographic item. - - - - - - - - - - + + + + + + + + + + @@ -34585,21 +23052,21 @@ -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (publication place) – Name of the place where a bibliographic item was published. - - - - - - - - - - + + + + + + + + + + @@ -34607,21 +23074,21 @@ -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + The name of the individual(s), institution(s) or organization(s) receiving correspondence. - - - - - - - - - + + + + + + + + + @@ -34629,56 +23096,55 @@ - + (related item) – Contains or references another bibliographic item which is related to the present one. - - - - - - - - - - - + + + + + + + + + + + - + - - + + Describes the relationship between the entity identified by the relatedItem element and the resource described in the parent element, i.e., bibl, source or relatedItem. - - + + - + Describes a relationship or linkage amongst entities. - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + - - + + Within work, expression, source, or item, the value of the rel attribute must match one of the following: hasAbridgement, isAbridgementOf, hasAdaptation, isAdaptationOf, hasAlternate, isAlternateOf, hasArrangement, isArrangementOf, hasComplement, @@ -34693,57 +23159,57 @@ - - + + Describes the relationship between the entities identified by the plist and target attributes. - - + + -

    The plist and target attributes identify the participants in a - relationship, while the rel attribute describes the nature of their relationship. - A mutual relationship can be described using only the plist attribute – the - target attribute is not necessary. In a non-mutual relationship, - plist identifies the entities pointed "from", while target specifies - the entities pointed "to". If the target attribute is present, but the - plist is not, the relationship is presumed to exist between the parent of the - current relation element and the entities identified by target.

    +

    The plist and target attributes identify the participants in a + relationship, while the rel attribute describes the nature of their relationship. + A mutual relationship can be described using only the plist attribute – the + target attribute is not necessary. In a non-mutual relationship, plist + identifies the entities pointed "from", while target specifies the entities + pointed "to". If the target attribute is present, but the plist is + not, the relationship is presumed to exist between the parent of the current relation + element and the entities identified by target.

         - + Gathers relation elements. - - - + + + - - + + - + - + (render) – A formatting element indicating special visual rendering, e.g., bold or italicized, of a text word or phrase. - - - - - - - - - - - - - + + + + + + + + + + + + + @@ -34752,32 +23218,32 @@ - - + + A positive value for rotation rotates the text in a counter-clockwise fashion, while negative values produce clockwise rotation. - - + + -

    When an entire element should be rendered in a special way, a style sheet function should +

    When an entire element should be rendered in a special way, a style sheet function should be used instead of the rend element.

         - + Institution, agency, or individual which holds a bibliographic item. - - - - - - - - - - + + + + + + + + + + @@ -34785,27 +23251,27 @@ -

    Sub-units of the holding institution may be marked with repository +

    Sub-units of the holding institution may be marked with repository sub-elements. The name of the list from which a controlled value is taken may be recorded - using the auth attribute.

    + using the auth attribute.

     -

    This element is modelled on an element in the Encoded Archival Description (EAD) +

    This element is modelled on an element in the Encoded Archival Description (EAD) standard.

         - + (responsibility) – A phrase describing the nature of intellectual responsibility. - - - - - - - - - - + + + + + + + + + + @@ -34813,29 +23279,29 @@ -

    The name of the list from which a controlled value is taken may be recorded using the - auth attribute.

    +

    The name of the list from which a controlled value is taken may be recorded using the + auth attribute.

     -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (responsibility statement) – Transcription of text that names one or more individuals, groups, or in rare cases, mechanical processes, responsible for creation, realization, production, funding, or distribution of the intellectual or artistic content. - - - - - - - - - + + + + + + + + + - + @@ -34843,31 +23309,32 @@ - + - + At least one element pair (a resp element and a name-like element) is recommended. Alternatively, each name-like element may have a @role - attribute. + attribute. + -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + A non-sounding event found in the source being transcribed. - - - - - - - - - - - + + + + + + + + + + + @@ -34876,9 +23343,9 @@ - + - + The value of @line must be less than or equal to the number of lines on the staff. @@ -34886,19 +23353,19 @@ -

    See (Read, p. 96-102). Do not confuse this element with the space +

    See (Read, p. 96-102). Do not confuse this element with the space element, which is used as an aid for visual alignment.

         - + Name of a dramatic role, as given in a cast list. - - - - + + + + - - + + @@ -34906,18 +23373,18 @@ -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (role description) – Describes a character's role in a drama. - - - - + + + + - - + + @@ -34925,45 +23392,45 @@ -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - - (system break) – An empty formatting element that forces musical notation to begin on a - new line. - - - - - - - - - + + (system beginning) – An empty formatting element that forces musical notation to begin on + a new line. + + + + + + + + + - - + + -

    Do not confuse this element with the lb element, which performs a +

    Do not confuse this element with the lb element, which performs a similar function in prose.

         - + Full score view of the musical content. - - - - - - - - - - - + + + + + + + + + + + @@ -34980,82 +23447,82 @@ -

    Since the measure element is optional, a score may consist entirely - of page breaks, each of which points to a page image. div elements are - allowed preceding and following sections of music data in order to accommodate blocks of +

    Since the measure element is optional, a score may consist entirely + of page beginnings, each of which points to a page image. div elements + are allowed preceding and following sections of music data in order to accommodate blocks of explanatory text.

         - + (score definition) – Container for score meta-information. - - - - - - - - - - + + + + + + + + + + - + - + - + - + - + - + - + - + - + - + - + - + Segment of music data. - - - - - - - - - - - - - - + + + + + + + + + + + + + + - + @@ -35069,9 +23536,9 @@ - + - + A section containing an expansion element must have descendant section, ending, or rdg elements. @@ -35079,24 +23546,24 @@ -

    This element functions as a container for actual music data. Pointing attributes make it +

    This element functions as a container for actual music data. Pointing attributes make it possible to connect this element to other internal or external entities, such as media objects or annotations.

         - + Contains information about the serial publication in which a bibliographic item has appeared. - - - - - - - - - - + + + + + + + + + + @@ -35111,35 +23578,35 @@ -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + A placeholder used to fill an incomplete measure, layer, etc. most often so that the combined duration of the events equals the number of beats in the measure. - - - - - - - - + + + + + + + + - - + + - + Contains a specialized form of heading or label, giving the name of one or more speakers in a dramatic text or fragment. - - - - + + + + - - + + @@ -35149,23 +23616,23 @@ -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Names of sponsoring individuals, organizations or institutions. Sponsors give their intellectual authority to a project; they are to be distinguished from funders, who provide the funding but do not necessarily take intellectual responsibility. - - - - - - - - - - + + + + + + + + + + @@ -35173,74 +23640,75 @@ -

    This element is modelled on elements in the Text Encoding Initiative (TEI) and Encoded +

    This element is modelled on elements in the Text Encoding Initiative (TEI) and Encoded Archival Description (EAD) standards.

         - + (stacked text) – An inline table with a single column. - - - - - - - - + + + + + + + + - - + + Indicates the delimiter used to mark the portions of text that are to be stacked. - - + + - + Specifies how the stacked text components should be aligned. - - + + Left justified. - + Right justified. - + Centered. - + Aligned on right-most digit. - + A group of equidistant horizontal lines on which notes are placed in order to represent pitch or a grouping element for individual 'strands' of notes, rests, etc. that may or may not actually be rendered on staff lines; that is, both diastematic and non-diastematic signs. - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + @@ -35254,19 +23722,10 @@ - - + + - + There must be a preceding staffDef with a matching value of @n, a preceding staff with a matching @n value containing a staffDef, or a staffDef child element. @@ -35274,48 +23733,49 @@ -

    The def attribute may be used to create a connection with a staffDef element where logical and visual information about the staff is recorded. - Alternatively, the n attribute may be used as a reference to a staffDef element with the same value in its n attribute or the staff may - contain a staffDef element that defines it. If neither def nor n +

    The def attribute may be used to create a connection with a staffDef element where logical and visual information about the staff is recorded. + Alternatively, the n attribute may be used as a reference to a staffDef element with the same value in its n attribute or the staff may + contain a staffDef element that defines it. If neither def nor n attributes are present, then the encoding order of the staves is presumed to match the encoding order of the staff definitions.

         - + (staff definition) – Container for staff meta-information. - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + - + - + - + - + StaffDef must have an n attribute. Either @@ -35326,18 +23786,18 @@ - + - + @n must have the same value as the current staff. - + - + Either @lines must be present or a preceding staffDef with matching @n value and @lines must @@ -35345,17 +23805,17 @@ - + - + The clef position must be less than or equal to the number of lines on the staff. - + - + The clef position must be @@ -35363,18 +23823,18 @@ - + - + The tab.strings attribute must have the same number of values as there are staff lines. - + - + The @@ -35383,9 +23843,9 @@ - + - + The lines.color attribute @@ -35401,9 +23861,9 @@ - + - + @@ -35413,9 +23873,9 @@ - + - + @@ -35426,43 +23886,43 @@ - + (staff group) – A group of bracketed or braced staves. - - - - - - - - - - - - + + + + + + + + + + + + - + - + - + - + - + - + Each staffDef must have a unique value @@ -35471,25 +23931,25 @@ -

    System is the more proper name for this concept (Read, p. 37-38). Bracketed staff groups +

    System is the more proper name for this concept (Read, p. 37-38). Bracketed staff groups may contain other bracketed or braced staff groups or single staves. See Read, p. 35-38, examples p. 434, 438.

         - + (syllable) – Individual lyric syllable. - - - - - - - - - - - - + + + + + + + + + + + + @@ -35499,27 +23959,27 @@ -

    Do not confuse this element with the syllable element, which is used +

    Do not confuse this element with the syllable element, which is used to organize neume notation.

         - + A reference to a previously defined symbol. - - - - - - - - - - - - - + + + + + + + + + + + + + - + In the symbolDef context, symbol must have either a startid attribute or x and y attributes. In the symbolDef context, symbol @@ -35529,32 +23989,32 @@ -

    The starting point, e.g. "hotspot", of the symbol may be identified in absolute output - coordinate terms using the x and y attributes or relative to another - element using the startid attribute. Attributes in the att.visualOffset class may +

    The starting point, e.g. "hotspot", of the symbol may be identified in absolute output + coordinate terms using the x and y attributes or relative to another + element using the startid attribute. Attributes in the att.visualOffset class may be used to record horizontal, vertical, or time offsets from the absolute coordinates or - from the location of the referenced element. The ref attribute must contain the - id of a symbolDef element. The scale attribute indicates + from the location of the referenced element. The ref attribute must contain the + id of a symbolDef element. The scale attribute indicates that the printed output must be scaled by the specified percentage.

         - + Text and symbols descriptive of tempo, mood, or style, e.g., "allarg.", "a tempo", "cantabile", "Moderato", "♩=60", "Moderato ♩ =60"). - - - - - - - - - - - - - - + + + + + + + + + + + + + + @@ -35564,114 +24024,115 @@ - + - + Only analog, class, label, mm, mm.dots, mm.unit, n, translit, type, xml:base, xml:id, and xml:lang attributes are allowed when tempo is not a descendant of a score or part. - + - + Must have one of the attributes: startid, tstamp, tstamp.ges or tstamp.real. - + Keyword or phrase which describes a resource. - - - - - - - - - + + + + + + + + + - + - + The @data attribute may only occur on a term which is a descendant of a classification element. -

    The term element may include other term +

    The term element may include other term elements in order to allow the creation of coordinated terms; i.e., terms created from a combination of other, independent terms.

    -

    To associate a term with a taxonomy category defined in the MEI metadata header, the value - of class must contain a fragment identifier corresponding to the appropriate term element. To associate a term with category in an externally-defined - taxonomy, class must contain an absolute URI, which may include the fragment +

    To associate a term with a taxonomy category defined in the MEI metadata header, the value + of class must contain a fragment identifier corresponding to the appropriate term element. To associate a term with category in an externally-defined + taxonomy, class must contain an absolute URI, which may include the fragment identifier of the element containing the category label.

     -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + (text language) – Identifies the languages and writing systems within the work described by a bibliographic description, not the language of the description. - - - - - - - - - + + + + + + + + + - - + + (main language) supplies a code which identifies the chief language used in the bibliographic work. - - + + - + (other languages) one or more codes identifying any other languages used in the bibliographic work. - - + + - + Title of a bibliographic entity. - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + @@ -35681,104 +24142,104 @@ - - + + Indicates the bibliographic level of the title. - - + + Analyzed component, such as an article or chapter, within a larger bibliographic entity. - + Collection. A group of items that were not originally published, distributed, or produced together. - + Subunit of a collection, e.g. item, folder, box, archival series, subgroup, or subcollection. - + Integrating resource, such as a continuously updated loose-leaf service or Web site. - + Monograph. - + Journal. - + Series. - + Unpublished (including theses and dissertations unless published by a commercial press). - + Characterizes the title in some sense, using any convenient classification scheme or typology that employs single-token labels. - - + + - - + + Main title. - + Subtitle or title of part. - + Abbreviated form of title. - + Alternate title by which the item is also known. - + Translated form of title. - + Collective title. - + Descriptive paraphrase of the work. -

    The type attribute may be used to classify the title according to some +

    The type attribute may be used to classify the title according to some convenient typology. Sample values include: main (main title), subordinate (subtitle, title of part), abbreviated (abbreviated form of title), alternative (alternate title by which the work is also known), translated (translated form of title), uniform (collective title), and - desc (descriptive title). The type attribute is provided for convenience in + desc (descriptive title). The type attribute is provided for convenience in analysing titles and processing them according to their type; where such specialized processing is not necessary, there is no need for such analysis, and the entire title, including subtitles and any parallel titles, may be enclosed within a single title element. Title parts may be encoded in titlePart sub-elements. The name of the list from which a controlled value is taken - may be recorded using the auth attribute. The number of initial characters (such + may be recorded using the auth attribute. The number of initial characters (such as those constituting an article or preposition) that should not be used for sorting a title - or name may be indicated in the nonfiling attribute.

    + or name may be indicated in the nonfiling attribute.

     -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Contains a transcription of the title page of a text. - - - - - - - - - - + + + + + + + + + + - + @@ -35790,30 +24251,31 @@ -

    This element may be used within the physDesc element when no other +

    This element may be used within the physDesc element when no other transcription is provided.

     -

    This element is modelled on an element in Encoded Archival Description (EAD) standard.

    +

    This element is modelled on an element in Encoded Archival Description (EAD) standard.

         - + Contains a subsection or division of the title of a bibliographic entity. - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + @@ -35823,78 +24285,78 @@ - - + + Characterizes this title component in some sense, using any convenient classification scheme or typology that employs single-token labels. - - + + - - + + Alternate title by which the item is also known. - + Arranged statement for music. Analogous to MARC 240 subfield o. - + Medium of the carrier. Analogous to MARC 240 subfield h. - + Publication/creation date(s) of work. Analogous to MARC 240 subfield f. - + Descriptive paraphrase of the work. - + Form subheading. Analogous to MARC 240 subfield k. - + Key for music. Analogous to MARC 240 subfield r. - + Language of a work. Analogous to MARC 240 subfield l (el). - + Main title. - + Name of a part or section of a work. Analogous to MARC 240 subfield p. - + Standard number designation of a work or of a part or section of a work. Analogous to MARC 240 subfield n. - + Performance medium. Analogous to MARC 240 subfield m. - + Subtitle. - + Translated form of title. - + Version. Analogous to MARC 240 subfield s. -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + Description of the horizontal size of an object. - - - - - - - - - + + + + + + + + + @@ -35903,35 +24365,55 @@     - - + + Tablature component declarations. - - Gestural domain attributes. - - - Records the fret at which a string should be stopped. - - + + String tablature string and fret information. + + + Indicates which finger, if any, should be used to play an individual string. The + index, middle, ring, and little fingers are represented by the values 1-4, while 't' is + for the thumb. The values 'x' and 'o' indicate muffled and open strings, + respectively. + + + + + + Records the location at which a string should be stopped against a fret. + + - + Records which string is to be played. - - + + + + + + + + String tablature position information. + + + Records fret position. + + - - Gestural domain attributes for staffDef in tablature. - - + + String tablature tuning information. + + Provides a *written* pitch and octave for each open string or course of strings. - - + + [a-g][0-9](s|f|ss|x|ff|xs|sx|ts|tf|n|nf|ns|su|sd|fu|fd|nu|nd|1qf|3qf|1qs|3qs)?([a-g][0-9](s|f|ss|x|ff|xs|sx|ts|tf|n|nf|ns|su|sd|fu|fd|nu|nd|1qf|3qf|1qs|3qs)?)* @@ -35942,73 +24424,101 @@ + + A barre in a chord tablature grid. + + + + + + + + + + Records the location at which the strings should be stopped against a fret in a + fretboard diagram. This may or may not be the same as the actual location on the fretboard + of the instrument in performance. + + + 1 + 5 + + + + + +

    The startid and endid attributes are used to indicate the chordMember elements on which the barre starts and finishes respectively. + The fret at which the barre should be created is recorded by the fret + attribute.

    +     +     - + Text component declarations. - + Groups elements that may contain back matter. - - + + - + Groups elements used to represent generic structural divisions of text. - + Groups elements that may contain front matter. - - + + - + Groups elements that have a line-grouping function. - - - + + + - + Groups list-like elements. - - - + + + - + Groups elements representing metrical components such as verse lines. - + Groups elements related to highlighting which can appear at the phrase-level. - - + + - + Groups elements used to directly contain quotations. - - - + + + - + Contains a formal list or prose description of topics addressed. - - - - - - - - - + + + + + + + + + - + @@ -36020,21 +24530,21 @@ -

    This element is modelled on elements in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on elements in the Text Encoding Initiative (TEI) standard.

         - + (back matter) – Contains any appendixes, advertisements, indexes, etc. following the main body of a musical text. - - - - - - - - - + + + + + + + + + @@ -36044,21 +24554,21 @@ -

    This element is modelled on elements in the Text Encoding Initiative (TEI) and Encoded +

    This element is modelled on elements in the Text Encoding Initiative (TEI) and Encoded Archival Description (EAD) standards.

         - + Contains a quotation, anonymous or attributed, appearing on a title page. - - - - - - - - - + + + + + + + + + @@ -36067,20 +24577,20 @@ -

    This element is modelled on elements in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on elements in the Text Encoding Initiative (TEI) standard.

         - + (front matter) – Bundles prefatory text found before the start of the musical text. - - - - - - - - - + + + + + + + + + @@ -36090,29 +24600,28 @@ -

    - titlePage may be used to transcribe the item's title page. Other front - matter structures, such as a preface, dedication, or table of contents, may be encoded as - textual divisions; that is, as div elements, with an optional head sub-element describing the nature of the division. The pb element is allowed here in order to accommodate page images, e.g. +

    titlePage may be used to transcribe the item's title page. Other + front matter structures, such as a preface, dedication, or table of contents, may be encoded + as textual divisions; that is, as div elements, with an optional head sub-element describing the nature of the division. The pb element is allowed here in order to accommodate page images, e.g. cover, endpapers, etc. before and after the actual textual matter.

     -

    This element is modelled on elements in the Text Encoding Initiative (TEI) and Encoded +

    This element is modelled on elements in the Text Encoding Initiative (TEI) and Encoded Archival Description (EAD) standards.

         - + Contains a formal statement authorizing the publication of a work, sometimes required to appear on a title page or its verso. - - - - - - - - - + + + + + + + + + @@ -36120,19 +24629,19 @@ -

    This element is modelled on elements in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on elements in the Text Encoding Initiative (TEI) standard.

         - + (line of text) – Contains a single line of text within a line group. - - - - - - - - + + + + + + + + @@ -36144,32 +24653,32 @@ - - + + Used to specify a rhythm for the lyric syllables that differs from that of the notes on the staff, e.g., '4,4,4,4' when the rhythm of the notes is '4.,8,4.,8'. - - + + -

    Do not confuse this element with the line element, which is used for +

    Do not confuse this element with the line element, which is used for graphical lines that occur in music notation.

     -

    This element is modelled on elements in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on elements in the Text Encoding Initiative (TEI) standard.

         - + (list item) – Single item in a list. - - - - + + + + - - + + @@ -36180,180 +24689,182 @@ -

    This element is modelled on elements in the Encoded Archival Description (EAD), Text +

    This element is modelled on elements in the Encoded Archival Description (EAD), Text Encoding Initiative (TEI), and HTML standards.

         - + A formatting element that contains a series of items separated from one another and arranged in a linear, often vertical, sequence. - - - - - - - - - - - - - + + + + + + + + + + + + + + - + - + - + In a list of type "gloss" all items must be immediately preceded by a label. - - + + Used to indicate the format of a list. In a "simple" list, li elements are not numbered or bulleted. In a "marked" list, the sequence of the list items is not critical, and a bullet, box, dash, or other character is displayed at the start of each item. In an "ordered" list, the sequence of the items is important, and each li is lettered or numbered. Style sheet functions should be used to specify the mark or numeration system for each li. - - + + Items are not numbered or bulleted. - + Bullet, box, dash, or other character is displayed before each item. - + Each item is numbered or lettered. - + Captures the nature of the content of a list. - - + + - - + + Each list item glosses some term or concept, which is given by a label element preceding the list item. - + Each list item is an entry in an index such as the alphabetical topical index at the back of a print volume. - + Each list item is a step in a sequence of instructions, as in a recipe. - + Each list item is one of a sequence of petitions, supplications or invocations, typically in a religious ritual. - + Each list item is part of an argument consisting of two or more propositions and a final conclusion derived from them. -

    In a list of type "gloss" it is a semantic error not to precede each list item with a +

    In a list of type "gloss" it is a semantic error not to precede each list item with a label.

         -

    This element is modelled on elements in Encoded Archival Description (EAD), Text Encoding +

    This element is modelled on elements in Encoded Archival Description (EAD), Text Encoding Initiative (TEI), and HTML standards.

         - + (quoted) – Contains material which is distinguished from the surrounding phrase-level text using quotation marks or a similar method. Use quote for block-level quotations. - - - - - - - - - - - + + + + + + + + + + + + - - - - + + + + - - + + Representation of speech. - + Representation of thought, e.g. internal monologue. - + Quotation from a written source. - + Authorial distance. - + Linguistically distinct. - + Linguistically distinct. - + Technical term. - + Rhetorically emphasized. - + Refering to itself, not its normal referent. -

    This element may be used for a variety of reasons including, but not limited to: direct +

    This element may be used for a variety of reasons including, but not limited to: direct speech or thought, technical terms or jargon, authorial distance, quotations from elsewhere, and passages that are mentioned but not used.

    -

    Do not confuse this element, used to capture phrase-level quotations, and quote, intended for block quotations.

    +

    Do not confuse this element, used to capture phrase-level quotations, and quote, intended for block quotations.

     -

    This element is modelled on elements found in HTML, TEI, and EAD standards.

    +

    This element is modelled on elements found in HTML, TEI, and EAD standards.

         - + (quoted material) – Contains a paragraph-like block of text attributed to an external source, normally set off from the surrounding text by spacing or other typographic distinction. - - - - - - - - - + + + + + + + + + @@ -36363,24 +24874,24 @@ -

    The source for the quote may be included in a bibl sub-element.

    -

    Do not confuse this element, used to capture block-level quotations, and q, intended for inline quotations.

    +

    The source for the quote may be included in a bibl sub-element.

    +

    Do not confuse this element, used to capture block-level quotations, and q, intended for inline quotations.

     -

    This element is modelled on elements found in HTML, TEI, and EAD standards.

    +

    This element is modelled on elements found in HTML, TEI, and EAD standards.

         - + (arbitrary segment) represents any segmentation of text below the "text component" level. - - - - - - - - + + + + + + + + @@ -36391,26 +24902,26 @@ -

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

    +

    This element is modelled on an element in the Text Encoding Initiative (TEI) standard.

         - + User-defined symbols component declarations. - + Attributes supplying pointers to user-defined symbols. - - + + Provides a way of pointing to a user-defined symbol. It must contain a reference to an ID of a symbolDef element elsewhere in the document. - - + + - + - + @altsym attribute should have content. The value in @altsym should correspond to the @xml:id attribute of a symbolDef @@ -36424,95 +24935,95 @@ - + Logical domain attributes. - - + + - - + + Indicates the function of the text. - - + + - - + + The function of the text is unknown. - + Logical domain attributes. - - + + - - + + Indicates the function of the curve. - - + + - - + + The function of the curve is unknown. - + Attributes for describing the logical behavior of a line. - - - - - - - - + + + + + + + + Indicates the function of the line. - - + + - - + + Indicates coloration in material transcribed from a source originally in mensural notation. - + Marks a ligature in material transcribed from a source originally in mensural notation. - + The function of the line is unknown. - + Groups elements that function as drawing primitives. - + Groups elements that group symbol definitions. - + Container for text that is fixed to a particular page location, regardless of changes made to the layout of the measures around it. - - - - - - - - - - - - + + + + + + + + + + + + @@ -36522,34 +25033,34 @@ -

    This element may be used where semantic markup of the text is neither possible nor +

    This element may be used where semantic markup of the text is neither possible nor desirable, such as in optical music recognition (OMR) applications. The content model here is similar to paragraph without model.textcomponent and pb sub-elements. The starting point of the text may be identified in absolute output coordinate - terms using the x and y attributes or relative to the location of - another element using the startid attribute. The attributes in the + terms using the x and y attributes or relative to the location of + another element using the startid attribute. The attributes in the att.visualOffset class may be used to record horizontal, vertical, or time offsets from the absolute coordinates or from the location of the referenced element.

         - + A curved line that cannot be represented by a more specific element, such as a slur. - - - - - - - - - - - - - + + + + + + + + + + + + + - + In the symbolDef context, curve must have either a startid attribute or x and y attributes. In the symbolDef context, curve must have @@ -36560,48 +25071,48 @@ -

    The starting point of the curve may be identified in absolute output coordinate terms using - the x and y attributes or relative to the location of another element - using the startid attribute. The attributes in the att.visualOffset class may be +

    The starting point of the curve may be identified in absolute output coordinate terms using + the x and y attributes or relative to the location of another element + using the startid attribute. The attributes in the att.visualOffset class may be used to record horizontal, vertical, or time offsets from the absolute coordinates or from the location of the referenced element. Similarly, the terminal point of the curve may be - recorded using either the x2 and y2 coordinates or in relation to the - location of another element using the endid attribute. Attributes in the + recorded using either the x2 and y2 coordinates or in relation to the + location of another element using the endid attribute. Attributes in the att.visualOffset2 class maybe used to record the offsets of the ending point. The - bulge attribute or, alternatively, the bezier attribute, describe - the shape of the curve and the lform and lwidth attributes capture its + bulge attribute or, alternatively, the bezier attribute, describe the + shape of the curve and the lform and lwidth attributes capture its appearance.

         - + A visual line that cannot be represented by a more specific; i.e., semantic, element. - - - - - - - - - - - + + + + + + + + + + + - + - + When used in the symbolDef context, must have either a startid attribute or x and y attributes. When used in the symbolDef context, must have either an endid attribute or both x2 and y2 attributes. - + When used in the score context, must have a startid, tstamp, tstamp.ges or tstamp.real attribute or both x and y attributes. @@ -36612,26 +25123,25 @@ -

    The starting point of the line may be identified in absolute output coordinate terms using - the x and y attributes. The attributes in the att.visualOffset class +

    The starting point of the line may be identified in absolute output coordinate terms using + the x and y attributes. The attributes in the att.visualOffset class may be used to record horizontal, vertical, or time offsets from these absolute coordinates - or from the location of the element reference in the startid attribute. - Similarly, the terminal point of the line may be recorded using the x2 and - y2 attributes. Attributes in the att.visualOffset2 class maybe used to record - the offsets of the ending point. Textual content of the line element, - e.g. 'gliss.', may be rendered with the line. The appearance of the line is captured in the - color, form and width attributes.

    + or from the location of the element reference in the startid attribute. + Similarly, the terminal point of the line may be recorded using the x2 and + y2 attributes. Attributes in the att.visualOffset2 class maybe used to record the + offsets of the ending point. Textual content of the line element, e.g. + 'gliss.', may be rendered with the line. The appearance of the line is captured in the + color, form and width attributes.

         - + One or more characters which are related to the parent symbol in some respect, as specified by the type attribute. - - - + + - - + + @@ -36639,58 +25149,59 @@ - + (property name) – Name of a property of the symbol. - - - - - - - - - - - + + + + + + + + + + + + Characterizes the property name. - - + + A registered Unicode normative or informative property name. - + A locally defined name. - + (property value) – A single property value. - - + + - - + + - + (symbol definition) – Declaration of an individual symbol in a symbolTable. - - - + + + - - + + - + - + - - + + @@ -36702,618 +25213,688 @@ - + -

    Like a chord table, a symbolTable may be shared between MEI instances through the use of an +

    Like a chord table, a symbolTable may be shared between MEI instances through the use of an external parsed entity containing the symbolTable to be shared.

         - + (symbol name) – Contains the name of a symbol, expressed following Unicode conventions. - - + + - - + + - + (symbol property) – Provides a name and value for some property of the parent symbol. - - + + - - - + + + - + Contains a set of user-defined symbols. - - - + + + - - + + -

    Like a chord table, a symbolTable may be shared between mei instances through the use of an +

    Like a chord table, a symbolTable may be shared between mei instances through the use of an external parsed entity containing the symbolTable to be shared.

         - + Visual component declarations. - + Visual domain attributes. - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + Visual domain attributes. - - - - - - - + + + + + + + - + Visual domain attributes. - - + + Location of the annotation. - - + + - + Visual domain attributes. - - - - - - - - - - + + + + + + + + + + Indicates if an arrowhead is to be drawn as part of the arpeggiation symbol. - - + + - + Symbol rendered at end of the line. - - + + - + Holds the relative size of the arrow symbol. - - + + - + Captures the overall color of the arrow. - - + + - + Captures the fill color of the arrow if different from the line color. - - + + - + Visual form of the line. - - + + - + Width of the line. - - + + - + Visual domain attributes. - - - - - - - - - - - - - - + + + + + + + + + + + + + + Visual domain attributes. - - - - - - - - + + + + + + + + - + Visual domain attributes. - - - - - - - - + + + + + + + + + + States the length of barlines in virtual units. The value must be greater than 0 and + is typically equal to 2 times (the number of staff lines - 1); e.g., a value of '8' for a + 5-line staff. + + + 0 + + + +

    This attribute is ignored if the value of the style attribute is "mensur".

    +     +     + + Records the method of barring. + + + + + + Denotes the staff location of the bar line if its length is non-standard. + + + + +

    The location may include staff lines, the spaces between the lines, and the spaces + directly above and below the staff. The value ranges between 0 (just below the staff) to + 2 * number of staff lines (directly above the staff). For example, on a 5-line staff the + lines would be numbered 1, 3, 5, 7, and 9 while the spaces would be numbered 0, 2, 4, 6, + 8, and 10. So, a value of '9' puts the bar line through the top line of the staff.

    +

    This attribute is ignored if the value of the style attribute is "mensur".

    +     +     +     - + Visual domain attributes. - - - + + + + - + Used by layerDef, staffDef, and scoreDef to provide default values for attributes in the visual domain related to beaming. - - + + Color of beams, including those associated with tuplets. - - + + - + Encodes whether a beam is "feathered" and in which direction. - - + + Beam lines grow farther apart from left to right. - + Beam lines grow closer together from left to right. - + Beam lines are equally-spaced over the entire length of the beam. - + Captures beam slope. - - + + - + Visual domain attributes. - - + + - + Visual domain attributes. - - - - - - - - - + + + + + + + + + Indicates the number of slashes required to render the appropriate beat repeat symbol. When a single beat consisting of a single note or chord is repeated, the repetition symbol is a single thick, slanting slash; therefore, the value '1' should be used. When the beat is divided into even notes, the following values should be used: 4ths or 8ths=1, 16ths=2, 32nds=3, 64ths=4, 128ths=5. When the beat is comprised of mixed duration values, the default rendition is 2 slashes and 2 dots. - - + + - + Visual domain attributes. If the bulge or bezier attributes are present, the bend should be rendered as a curve. Otherwise, it should be rendered using lines. The ho and vo attributes describe the visual offset of the entire rendered bend. The endho, endvo and startho, startvo attribute pairs may be used to encode start and end points relative to their programmatic placement. For exact placement of the endpoints of the bend, use the x and y attributes. - - - - - - - - + + + + + + + + - + Visual domain attributes. - - - - - - - - - - - - - + + + + + + + + + + + + + Visual domain attributes. - - - - - - - - - - - - - + + + + + + + + + + + + + Visual domain attributes. - - + + - + Visual domain attributes. - - - - - - - - - - - - - + + + + + + + + + + + + + Visual domain attributes for chord. The slur, slur.dir, slur.rend, tie, tie.dir, and tie.rend attributes here are syntactic sugar for these attributes on each of the chord's individual notes. The values here apply to all the notes in the chord. If some notes are slurred or tied while others aren't, then the individual note attributes must be used. - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + Indicates a single, alternative note head should be displayed instead of individual note heads. The highest and lowest notes of the chord usually indicate the upper and lower boundaries of the cluster note head. - - + + - + Visual domain attributes. - + Visual domain attributes. - + Visual domain attributes. - - - - - - + + + + + + - + Used by staffDef and scoreDef to provide default values for attributes in the visual domain related to clefs. - - + + Describes the color of the clef. - - + + - + Determines whether the clef is to be displayed. - - + + - + Visual domain attributes. - + Visual domain attributes. - - - - - - - - - - - - + + + + + + + + + + + + Visual domain attributes. - - - - - - - - + + + + + + + + - + Visual domain attributes. - - - - - - + + + + + + - + Visual domain attributes. - + Visual domain attributes. - - - - - - - - + + + + + + + + - + Visual domain attributes. - - - - - - - - - - - - - + + + + + + + + + + + + + Visual domain attributes. - - - - - - - + + + + + + + + - + Visual domain attributes. - - + + - + + Visual domain attributes. + + + + + + + + + + + + + + + + + Horizontal stroke. + + + Vertical stroke. + + + + + Captures the placement of the episema with respect to the neume or neume component + with which it is associated. + + + + + + + Visual domain attributes. - - - - - - + + + + + + -

    If tstamp2 is not provided, then the extender should be drawn based on the value - of tstamp2 on the harm ancestor.

    +

    If tstamp2 is not provided, then the extender should be drawn based on the value + of tstamp2 on the harm ancestor.

         - + Visual domain attributes. - - - - - - - - - - - + + + + + + + + + + + Describes the visual appearance of the fermata; that is, whether it occurs as upright or inverted. - - + + Inverted, i.e., curve or bracket below the dot. - + Upright; i.e., curve or bracket above the dot. - + Describes the visual appearance of the fermata; that is, whether it has a curved, square, or angular shape. - - + + A curve above or below the dot. - + A bracket above or below the dot. - + A triangle above or below the dot. - + Visual domain attributes. - - - - - - + + + + + + -

    If tstamp2 is not provided, then the extender should be drawn based on the value - of tstamp2 on a fingering ancestor.

    +

    If tstamp2 is not provided, then the extender should be drawn based on the value + of tstamp2 on a fingering ancestor.

         - + Visual domain attributes. - - - - - - - - - - - + + + + + + + + + + + Combination expressed horizontally, as for brass instruments. - + Combination expressed vertically, as for woodwind instruments or piano. - + Visual domain attributes. - - + + Indicates the number of beams present. - - + + 1 6 - + Captures the number of "floating" beams, i.e., those not attached to stems. - - + + - + - + The number of floating beams must be less than or equal to the total number of beams. - + Records the amount of separation between floating beams and stems. - - + + - + Visual domain attributes. - - - - - - - - - - - - - + + + + + + + + + + + + + Visual domain attributes. - - - - - - + + + + + + - + Visual domain attributes. The startho and startvo attributes record the horizontal and vertical offsets of the left end, endho and endvo record the horizontal and vertical offsets of the right end, and the opening attribute records the width of the opening in staff @@ -37322,725 +25903,656 @@ and horizontally bifurcates it. The so-called "pitch" of hairpin may be controlled by use of the startho, endho, startvo, and endvo attributes, while the placement of the entire rendered mark may be controlled by use of the ho and vo attributes. - - - - - - - - - - - - + + + + + + + + + + + + Specifies the distance between the lines at the open end of a hairpin dynamic mark. - - + + - + Visual domain attributes. - - - - - - - + + + + + + + - + Visual domain attributes. - - - - - - - - - - + + + + + + + + + + Describes how the harmonic indication should be rendered. - - + + Chord tablature grid. - + Chord tablature grid and the element's textual content. - + Textual content of the element. - + + Visual domain attributes. + + + + + + + + + + + Visual domain attributes. - - - - - - - - + + + + + + + + + + + + + Captures the placement of the tick mark with respect to the neume or neume component + with which it is associated. + + + + + + Direction toward which the mark points. + + + + + - + Visual domain attributes. - + Visual domain attributes. - - - - - - - + + + + + + + - + Visual domain attributes. - - + + - - + + Determines whether cautionary accidentals should be displayed at a key change. - - + + - + Used by staffDef and scoreDef to provide default values for attributes in the visual domain related to key signatures. - - + + Indicates whether the key signature should be displayed. - - + + - + Determines whether cautionary accidentals should be displayed at a key change. - - + + - + Visual domain attributes. - - + + - + Visual domain attributes. - - - - + + + + - + Visual domain attributes. + + + - - Visual domain attributes. - - - - - - - - - - - - - + Attributes for describing the visual appearance of a line. - - - - - - - - - - + + + + + + + + + + Visual form of the line. - - + + - - + + Width of the line. - - + + - - + + Symbol rendered at end of line. - - + + - + Holds the relative size of the line-end symbol. - - - - - - + + + + + + Symbol rendered at start of line. - - + + - + Holds the relative size of the line-start symbol. - - + + + + + + + + + Visual domain attributes. + + + + + + + + + + + + + + Records direction of curvature. + + + Anti-clockwise curvature. + + + Clockwise curvature. + + + + + Indicates whether curve is closed. + + - - + Visual domain attributes. The vo attribute is the vertical offset (from its normal position) of the entire rendered tie. The startho, startvo, endho, and endvo attributes describe the horizontal and vertical offsets of the start and end points of the sign in terms of staff interline distance; that is, in units of 1/2 the distance between adjacent staff lines. Startto and endto describe the start and end points in terms of time; that is, beats. - - - - - - - - + + + + + + + + - + Visual domain attributes. - - - + + + - + Visual domain attributes. - - - + + + - + Visual domain attributes. These attributes describe the physical appearance of the mensuration sign/time signature of mensural notation. - - - - - - - - - + + + + + + + + + Indicates whether the base symbol is written vertically or horizontally. - - + + Horizontally oriented. - + Vertically oriented. - + Describes the rotation or reflection of the base symbol. - - + + - + Used by staffDef and scoreDef to provide default values for attributes in the visual domain related to mensuration. - - + + Records the color of the mensuration sign. Do not confuse this with the musical term 'color' as used in pre-CMN notation. - - + + - + Indicates whether the base symbol is written vertically or horizontally. - - + + Horizontally oriented. - + Vertically oriented. - + Holds the staff location of the mensuration sign. - - + + - + Describes the rotation or reflection of the base symbol. - - + + - + Describes the relative size of the mensuration sign. - - + + - + Visual domain attributes. - - - - - - - - + + + + + + + + Contains an indication of how the meter signature should be rendered. - - + + Show only the number of beats. - + The lower number in the meter signature is replaced by a note symbol. - + Meter signature rendered using traditional numeric values. - + Meter signature not rendered. - + Used by staffDef and scoreDef to provide default values for attributes in the visual domain related to meter signature. - - + + Contains an indication of how the meter signature should be rendered. - - + + Show only the number of beats. - + The lower number in the meter signature is replaced by a note symbol. - + Meter signature rendered using traditional numeric values. - + Meter signature not rendered. - - Determines whether a new meter signature should be displayed when the meter signature - changes. - - + + Determines whether the old meter signature should be displayed when the meter + signature changes. + + - + Visual domain attributes. - + Visual domain attributes. - + Visual domain attributes. - - - - - - - + + + + + + + - + Visual domain attributes. - - - - - - - - - - - - - + + + + + + + + + + + + + Visual domain attributes. - - - - - - + + + + + + - + Visual domain attributes. - - - - - - + + + + + + - + Visual domain attributes. - - - - + + + + - + Visual domain attributes. - - - - - - - - - + + + + + + + + + When the block attribute is used, combinations of the 1, 2, and 4 measure rest forms (Read, p. 104) should be rendered instead of the modern form or an alternative symbol. - - + + - + Visual domain attributes. - - - - - + + + + + - + Visual domain attributes. - - - - - - - - - - - - - - - - Connection to the previous component within the same neume. - - - - - The @con attribute is not allowed on the first - component of a neume. - - - - - - Gapped; not connected. - - - Looped. - - - - - - - - Anti-clockwise curvature. - - - Clockwise curvature. - - - - - - - - Up. - - - Down. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Curved. - - - Flat. - - - Jagged. - - - - - - - - 2 curves. - - - 3 curves. - - - - - - - - - - - - + + + + + + + + + + + + + Visual domain attributes. - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + - + Visual domain attributes. - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + Visual domain attributes. - - - - - - - + + + + + + + + + + + + + + + + + + Visual domain attributes. + + + + + + + - + + Visual domain attributes. + + + + + + + + + + + + + Visual domain attributes. - - - - - - - - + + + + + + + + - + Visual domain attributes. - + Visual domain attributes. - + Visual domain attributes. - + Visual domain attributes. - + Visual domain attributes. - - + + States the side of a leaf (as in a manuscript) on which the content following the pb element occurs. - - + + The back of a manuscript page. - + The front of a manuscript page. - + Visual domain attributes. The place attribute captures the placement of the pedal marking with respect to the staff with which it is associated. Modern publishing standards require the place to be 'below'; however, for transcriptions of manuscript works, this attribute class allows the full range of values. - - - - - - - - - - - - + + + + + + + + + + + + Determines whether piano pedal marks should be rendered as lines or as terms. - - + + Continuous line with start and end positions rendered by vertical bars and bounces shown by upward-pointing "blips". - + Pedal down and half pedal rendered with "Ped.", pedal up rendered by "*", pedal "bounce" rendered with "* Ped.". - + Pedal up and down indications same as with "pedstar", but bounce is rendered with "Ped." only. @@ -38048,425 +26560,478 @@ - + Visual domain attributes. - - - - - - - + + + + + + + - + Visual domain attributes. - - - - + + + + + + - + + Visual domain attributes. + + + + + + + + + + + + + + Number of "crests" of a wavy line. + + + 2 + 4 + + + + + + Visual domain attributes. - + Visual domain attributes. - - - - - - - - + + + + + + + + - + Visual domain attributes. - - - - - - + + + + + + - + Visual domain attributes. - - - - - - - - - - - - - - + + + + + + + + + + + + + + Visual domain attributes. - - - - + + + + - - + + Indicates whether hash marks should be rendered between systems. See Read, p. 436, ex. 26-3. - - + + Display hash marks between systems. - + Visual domain attributes. - + Visual domain attributes for scoreDef in the CMN repertoire. - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + Defines the height of a "virtual unit" (vu) in terms of real-world units. A single vu is half the distance between the vertical center point of a staff line and that of an adjacent staff line. - - - + + + \d+(\.\d+)?(cm|mm|in|pt|pc) - + Visual domain attributes. - - + + Indicates that staves begin again with this section. - - + + - + + Visual domain attributes. + + + + + + + + + + + + + + Captures the placement of the sequence of characters with respect to the neume or + neume component with which it is associated. + + + + + + + Visual domain attributes for slur. The vo attribute is the vertical offset (from its normal position) of the entire rendered slur/phrase mark. - - - - - - - - + + + + + + + + - + Visual domain attributes. - - - - - - + + + + + + - + Visual domain attributes. - - + + - - + + Indicates whether a space is 'compressible', i.e., if it may be removed at the discretion of processing software. - - + + - + Visual domain attributes. - - + + - + Visual domain attributes for staffDef. - - - - - - - - - - - - - - - - - - - - - "mensur" not allowed in this context. - - - - - + + + + + + + + + + + + + + + + + + + Determines whether to display guitar chord grids. - - + + - + Indicates the number of layers and their stem directions. - - + + - + Captures the colors of the staff lines. The value is structured; that is, it should have the same number of space-separated RGB values as the number of lines indicated by the lines attribute. A line can be made invisible by assigning it the same RGB value as the background, usually white. - - + + - + Records whether all staff lines are visible. - - + + - - Records the absolute distance (as opposed to the relative distances recorded in scoreDef elements) between this staff and the preceding one in the - same system. This value is meaningless for the first staff in a system since the - spacing.system attribute indicates the spacing between systems. - - + + Records the absolute distance (as opposed to the relative distances recorded in scoreDef elements) between this staff and the preceding one in the same + system. This value is meaningless for the first staff in a system since the spacing.system + attribute indicates the spacing between systems. + + - + Visual domain attributes. - - - + + + + - - + + Indicates whether bar lines go across the space between staves (true) or are only drawn across the lines of each staff (false). - - + + + +

    This attribute is ignored when the bar.method attribute's value is "mensur" or + "takt".

    +     - + Visual domain attributes. - - - - - - + + + + + + - + Visual domain attributes. - - - - - - - - - + + + + + + + + + + + + + + Visual domain attributes. + + + + + + + + + - + Visual domain attributes. - + Visual domain attributes. - - - - - - - - + + + + + + + + - + Visual domain attributes. - - - - - - - + + + + + + + - + Visual domain attributes. The vo attribute is the vertical offset (from its normal position) of the entire rendered tie. The startho, startvo, endho, and endvo attributes describe the horizontal and vertical offsets of the start and end points of the tie in terms of staff interline distance; that is, in units of 1/2 the distance between adjacent staff lines. Startto and endto describe the start and end points in terms of time; that is, beats. - - - - - - - - + + + + + + + + - + Visual domain attributes. - - - - - - - - - - - - - - + + + + + + + + + + + + + + Visual domain attributes. - - - + + + - - + + Used to state where a tuplet bracket will be placed in relation to the note heads. - - + + - + States whether a bracket should be rendered with a tuplet. - - + + - + Determines if the tuplet duration is visible. - - + + - + Controls how the num:numbase ratio is to be displayed. - - + + Only the num attribute is displayed, e.g., '7'. - + Both the num and numbase attributes are displayed, e.g., '7:4'. - + Visual domain attributes. - - + + - + Visual domain attributes. - - - - - - - - + + + + + + + + - + Visual domain attributes. - - - - - - - - + + + + + + + + - + Visual domain attributes. - - - - - - + + + + + +     diff --git a/tools/extractGuidelines.xsl b/tools/extractGuidelines.xsl index 9223cc0251e..fc2c12f4948 100644 --- a/tools/extractGuidelines.xsl +++ b/tools/extractGuidelines.xsl @@ -8,34 +8,27 @@ xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:rng="http://relaxng.org/ns/structure/1.0" xmlns:sch="http://purl.oclc.org/dsdl/schematron" - xmlns:local="no:where" xmlns:saxon="http://saxon.sf.net/" - exclude-result-prefixes="xs math xd xhtml tei local rng sch egx saxon" + xmlns:mei="http://www.music-encoding.org/ns/mei" + xmlns:tools="local" + exclude-result-prefixes="xs math xd xhtml tei rng sch egx saxon mei tools" version="3.0"> - Created on: Dec 12, 2015, updated on Oct 6, 2017 + Created on: Nov 16, 2018 Author: Johannes Kepper - This XSL generates the website version of the MEI Guidelines, directly from a canonicalized ODD file. - - - - - - - - - $role describes the role of the output: - 'release' qualifies this as official release of MEI, using the version number provided. - 'custom' qualifies this as output of a customization of MEI - 'dev' qualifies this as development version of MEI, taken from the official repo. - - This param is used for a running header in PDF output. + This XSL generates HTML / Markdown output for the website version of the MEI + Guidelines from a canonicalized ODD file. It's a complete rewrite and focusses + solely on the website (no code for generating PDFs anymore). - + + + + + @@ -48,2206 +41,174 @@ - - - + + + + + + + + + - $supported.version contains reference strings for every supported MEI version. - The only use of this variable is to indicate a mismatch between it and the - $version variable in a message, but nothing else happens. - Nevertheless, if adjusted to newer versions of MEI, these version numbers - should be added below. + $output.folder is the base folder where all outputs will be stored. - - - - + - - - - + + + + $includes.folder is the folder where all descriptions and examples will be stored + + + + + + + + $mei.source makes the input of this XSL (unmodified compiled ODD) available in a variable. + + + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + This is where processing starts. + + + - - - - - - - - - - - - - - - - - - - + - - - - - - - - - - - - - - - - - + + + + + + - + + + - + - + - - - - - - - - - - - - - - - - - - - - - - -
    -     -     - - - - - - - - -
    -     -     - - - - - - - -
    -     -     - - - - - - --- - - layout: sidebar - - sidebar: s1 - - title: "Elements" - - version: "" - - --- - - - - - - - - - - - - - - --- - - layout: sidebar - - sidebar: s1 - - title: "Model Classes" - - version: "" - - --- - - - - - - - - - - - - - - - --- - - layout: sidebar - - sidebar: s1 - - title: "Attribute Classes" - - version: "" - - --- - - - - - - - - - + + + - - - - - --- - - layout: sidebar - - sidebar: s1 - - title: "Data Types" - - version: "" - - --- - - - - - - - - - - - - -     - - - - - - -
    - - - -

    - - MEI Elements - MEI Model Classes - MEI Attribute Classes - -

    -
    - - - - - -
    -

    - -
    -     -     -
    -     - -

    MEI Data Types and Macros

    -
    - - - - - -
    -

    - -
    -     - -     - - - -
    -

    Macros

    - -
    -     -
    -     -     - -
    - -     - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --- - - layout: sidebar - - sidebar: s1 - - version: "" - - title: "" - - - sectionid: "" - - - --- - - - - - - - - - - -
    - -
    -     - - + + + - + + + - - - + + + -
    - -
    -     - - + + + - - - - - -

    - -

    -     - - - - - - - - - - - - - - - - - - - - - - - -

    - -

    -     -     -     - -
    Figure .
    -     - -
    Listing .
    -     - - - - - - -     + + + -     - - -

    - -

    -     - - - - - - - -
      - -
    • - -
      • -       -
    -     - - - - -
      - -
    1. - -
      2. -       -
    -     - -
    - -
    -
    -     -
    -     - - - - -
      - -
    • - -
      • -       -
    -     -     -     - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
      - - - - - - - - - - -
    • - - - - - - - - - - - - - - - - -
      - - - - - - - - - - - -
      -       -       -
      • -       -
    -     - - - -
    - - - - - - - - - - - - - - - - - - - - - - - -
    - - - - - - - - - - - -
    -     -     -
    -     - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    - -
    -     - - - - - - - - - - - - ** - - - - - - -
    - - -
    -     - - - - - - - - - - - -
    -

    <>

    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    - -
    Module
    Attributes - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    - -
    -     -
    Member of -
    - - - - -
    -
    Contained by -
    -
    - - - - - - - - - - - -
    - - - - - - - - -
    -     -
    -
    -
    May contain - - - - - - - - - - - - - - - - - - - - -
    - -
    - Text - -
    -     - - - - -
    - - - - - - - - -
    -     -
    -     - -
    - Empty - -
    -     -     -
    Declaration - - - -
    -
    Examples - -
    -     -
    Remarks -

    -
    Constraint -
    - -
    -     -
    -
    -
    -
    -     - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + This function generates the required output page for an object, depending on its type + + + + This is the object which needs to be processed. + + + + -
    - @ - () - + + - - Allowed values are: - - , "" () - - - and custom NMToken - - - - - - - Value conforms to . - - - One or two values from , separated by a space. - - - One or more values from , separated by spaces. - - - Value conforms to . - - - - - - + + - - - - - Value of datatype . - - - One or two values of datatype , separated by a space. - - - One or more values of datatype , separated by spaces. - - - Value is plain text. - - - Value is plain text. - - - Value is a valid xml:id. - - - Value is a decimal number. - - - Value is an integer. - - - Value is a positive integer. - - - Value is a positive integer, including 0. - - - Value is a language. - - - Value is a token. - - - Value is a NMTOKEN. - - - Value is an ISO duration. - - - Value conforms to the pattern "". - - - - - - + + - - - - - One or more values conforming to the pattern "". - - - One or more values, each consisting of a sequence of and sub-values. - - - One or more of . - - - One or more values, each consisting of a sequence of a part, followed by a . - - - - - - + + - - - - - Value must either conform to or . - - - Value must conform to . - - - Value must conform to data.BOOLEAN or . - - - - - - + + - - - - - Value is plain text. - - - Value is plain text. - - - - - - + + - - - - - - -
    - -     - - - - - - - - - - a string matching the following regular expression: "" - - - a decimal number between and - - - a positive integer between and - - - a positive integer no larger than - - - a positive integer no smaller than - - - a non-negative integer no larger than - - - a decimal number no smaller than - - - a decimal number larger than - - - one of the following integers: - - - a decimal number matching the pattern "" - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    -

    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    - -
    Module
    Available in -
    - - -
    - - - - -
    -     - - -
    - - - - -
    -     -
    -
    Members -
    - - -
    - - - - - - - - - - - - - -
    -     - - - -
    -
    Declaration - - - - -
    - - -
    Remarks -

    -
    Constraint -
    - -
    -     -
    -
    -
    -
    -     - - - +     - -
    -

    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    - -
    Module
    Members -
    - - -
    - - - - - - - - - - - - - -
    -     - - - -
    -
    Attributes - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    Declaration - - - - -
    - - -     - - - - -
    - - -     -
    Remarks -

    -
    Constraint -
    - - - - -
    -     -
    -
    -
    -
    - - - - - - - - - - + + - -
    - - - - - - (via ) - -
    + + - -
    - - (no elements directly inheriting from this class) -
    -     -     - - -     -     - - - - - - - - - - - -
    - - - - - - (via ) - -
    + + + + + + + + + + + - -
    - - (no elements directly inheriting from this class) -
    -     - - -     -     - - - - - -
    -

    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    - -
    Module
    Used by -
    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    -
    Allowed values -
    - -
    -     -
    -
    Declaration - - - - -
    - - -
    Remarks -

    -
    Constraint -
    - -
    -     -
    -
    -
    -
    -     - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    <> - - -
    -
    -
    -
    -
    -     - -
    -
    -
    -
    -     - -
    -
    -
    -     - -
    -
    -     - -
    -     -     - </>
    -     - -
    </></>
    -     -     -     - - - - - - -
    <!---->
    -     - - - ="" - - - - - ="" - ="" - - - - - ="" - - - - - - - - - - - - ="" - ="" - ="" - ="" - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ⃥ - - - - - - - - - - ⃥ - - - - - - - - - - - The following template provides the general frame for a complete HTML file with all contents - - - - - +     + + + --- + + layout: sidebar + + sidebar: s1 + + version: "" + + title: "" + + --- + +
    + +
    +     - - - - THIS FILE IS GENERATED FROM AN XML MASTER. DO NOT EDIT! - Music Encoding Initiative Guidelines - - - - - - - - - - - - - - -
    -
    -
    - Music Encoding Initiative Guidelines -
    - - -
    Version
    -     - -
    Latest development revision, based on Version
    -     - -
    Customization, based on Version
    -     -     - -
    -
    - - - Prepared and maintained by the Music Encoding Initiative Board - - - Developed by the Music Encoding Initiative Technical Team - - - - - -
    - -
    - - - Based on original work edited by Perry Roland and Johannes Kepper
    -
    - With contributions by Benjamin Bohl, Andrew Hankinson, Maja Hartwig, Zoltán Kömíves, Laurent Pugin,
    - Kristina Richts, Axel Teich Geertinger, Raffaele Viglianti, and Thomas Weber -     - - Edited by Perry Roland and Johannes Kepper
    -
    - With contributions by Benjamin Bohl, Andrew Hankinson, Maja Hartwig, Zoltán Kömíves, Laurent Pugin,
    - Kristina Richts, Axel Teich Geertinger, Raffaele Viglianti, and Thomas Weber -     -     -
    -
    - - -
    © for original Guidelines by the Music Encoding Initiative (MEI) Board.
    -     - -
    © by the Music Encoding Initiative (MEI) Board.
    -     -     -
    - Charlottesville and Detmold. - -
    -
    - Licensed under the Educational Community License, Version 2.0 (the "License"); you - may not use this file except in compliance with the License. You may obtain a copy - of the License at http://opensource.org/licenses/ECL-2.0. -
    -
    -
    - - -
    -
    -

    Table of contents

    - -
      - -
    • - -
      • -       -
    -
      - - - -
    • - . - - -
        - - - -
      • - . - - -
          - - - -
        • - . - - -
            - - - -
          • - . - - -
              - - - -
            • - . - -
              • - -               -
            -             -
            • - -             -
          -           -
          • - -           -
        -         -
        • - -         -
      -       -
      • -       -
    -     - - -
    -
    - - - - -
    - -
    -     -     - - -
    - - - - - -
    -

    MEI Data Dictionary

    -
    - -
    -
    -

    Elements

    - -
    -
    -

    Model Classes

    - -
    -
    -

    Attribute Classes

    - -
    -
    -

    Datatypes and Macros

    - -
    -
    -
    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - \ No newline at end of file diff --git a/tools/xsl/attClassHandling.xsl b/tools/xsl/attClassHandling.xsl new file mode 100644 index 00000000000..f7eac5b6c49 --- /dev/null +++ b/tools/xsl/attClassHandling.xsl @@ -0,0 +1,391 @@ + + + + + Created on: Nov 21, 2018 + Author: Johannes Kepper + + + + + + This template resolves attribute classes + + + +
    +

    +
    +
    + + + +
    + + + , + +
    +     +
    + + + + + + + + + + + + + +
    + +
    +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    + + + + +
    +     + + + + + + + +     + + + +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    + + + () + + + + + + Allowed values are: + + , "" () + + + and custom NMToken + + + + + + + Value conforms to . + + + One or two values from , separated by a space. + + + One or more values from , separated by spaces. + + + Value conforms to . + + + + + + + + + + + + Value of datatype . + + + One or two values of datatype , separated by a space. + + + One or more values of datatype , separated by spaces. + + + Value is plain text. + + + Value is plain text. + + + Value is a valid xml:id. + + + Value is a decimal number. + + + Value is an integer. + + + Value is a positive integer. + + + Value is a positive integer, including 0. + + + Value is a language. + + + Value is a token. + + + Value is a NMTOKEN. + + + Value is an ISO duration. + + + Value conforms to the pattern "". + + + + + + + + + + + + One or more values conforming to the pattern "". + + + One or more values, each consisting of a sequence of and sub-values. + + + One or more of . + + + One or more values, each consisting of a sequence of a part, followed by a . + + + + + + + + + + + + Value must either conform to or . + + + Value must conform to . + + + Value must conform to data.BOOLEAN or . + + + + + + + + + + + + Value is plain text. + + + Value is plain text. + + + + + + + + + + + + +
    + +     + + +     \ No newline at end of file diff --git a/tools/xsl/datatypeHandling.xsl b/tools/xsl/datatypeHandling.xsl new file mode 100644 index 00000000000..d87d108c3e8 --- /dev/null +++ b/tools/xsl/datatypeHandling.xsl @@ -0,0 +1,198 @@ + + + + + Created on: Nov 21, 2018 + Author: Johannes Kepper + + + + + + + This template resolves data types + + + +
    +

    +
    +
    + + + +
    + + + , + +
    +     +
    + + + + + + + + + + + + + +
    + +
    +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + /@ + + + + + + + + + + <> + + + + +
    +
    Used by
    +
    + + + – (</> is not used on any attribute) + + + + + + + + + + + + + +
    +
    +     + + + + + + + +
    +
    Allowed Values
    +
    + +
    + + + + + + +
    +     +
    +
    +     +     + + + + + + + + + + + a string matching the following regular expression: "" + + + a decimal number between and + + + a positive integer between and + + + a positive integer no larger than + + + a positive integer no smaller than + + + a non-negative integer no larger than + + + a decimal number no smaller than + + + a decimal number larger than + + + one of the following integers: + + + a decimal number matching the pattern "" + + + + + + + + + + +     \ No newline at end of file diff --git a/tools/xsl/elementHandling.xsl b/tools/xsl/elementHandling.xsl new file mode 100644 index 00000000000..dcc2a1e1708 --- /dev/null +++ b/tools/xsl/elementHandling.xsl @@ -0,0 +1,241 @@ + + + + + Created on: Nov 21, 2018 + Author: Johannes Kepper + + + + + + This template resolves elements + + + +
    +

    <>

    +
    +
    + + + +
    + + + , + +
    +     +
    + + + + + + + + + + + + + + + + + +
    + +
    +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    + + + + +
    +     +     + + + +     +     + + + + + + + + + +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + textual content + + + + + + + + + + + + + + + +
    + textual content +
    +     + +     + + + +
    + textual content +
    +     + + + + + + + + + + + + + + +
    + + + + +
    +     +     + + + +     +     + + + + + + + + +     + +
    +
    May Contain
    +
    + any XML element, with any attribute ( is self-nested) +
    +
    +     + + + +
    +
    May Contain
    +
    + – ( may not have child elements) +
    +
    +     +     + +     + +     \ No newline at end of file diff --git a/tools/xsl/globalFunctions.xsl b/tools/xsl/globalFunctions.xsl new file mode 100644 index 00000000000..50b25a45244 --- /dev/null +++ b/tools/xsl/globalFunctions.xsl @@ -0,0 +1,306 @@ + + + + + Created on: Nov 21, 2018 + Author: Johannes Kepper + + + + + + + + +
    +
    Module
    +
    + +
    +
    +     + + + + + + +
    +
    Remarks
    +
    +

    +
    +
    +     + +     + + + + + + + + + +
    + +
    +     +
    +     +     + + +
    +
    +
    +     +     + + + + + + + + +     +     + + + + + +
    +
    Declaration
    +
    + + + + + + +
    +
    +
    +     + + + + + + + + +
    +
    +
    +
      + +
    • + +
      • +       +
    + +
    + +
    +     +
    +
    + +     + + + + + + + +
    +
    + + +
    +
    + +
    +
    +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + --- + + layout: sidebar + + sidebar: s1 + + title: "" + + version: "" + + --- + +
    +

    +
    +
      + + +
    • + +
      • +       +
    +
    + + + +
    +
    +
    + + + + +
    +
    +     +
    +     + +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +     \ No newline at end of file diff --git a/tools/xsl/globalVariables.xsl b/tools/xsl/globalVariables.xsl new file mode 100644 index 00000000000..f4e61dc8f8c --- /dev/null +++ b/tools/xsl/globalVariables.xsl @@ -0,0 +1,98 @@ + + + + + Created on: Nov 21, 2018 + Author: Johannes Kepper + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/tools/xsl/javascript.xsl b/tools/xsl/javascript.xsl new file mode 100644 index 00000000000..01104f57044 --- /dev/null +++ b/tools/xsl/javascript.xsl @@ -0,0 +1,81 @@ + + + + + Created on: Nov 21, 2018 + Author: Johannes Kepper + + + + + + + + + + \ No newline at end of file diff --git a/tools/xsl/macrogroupHandling.xsl b/tools/xsl/macrogroupHandling.xsl new file mode 100644 index 00000000000..b79324249eb --- /dev/null +++ b/tools/xsl/macrogroupHandling.xsl @@ -0,0 +1,68 @@ + + + + + Created on: Nov 21, 2018 + Author: Johannes Kepper + + + + + + This template resolves Macro Groups (Parameter entities) + + + +
    +

    +
    +
    + + + +
    + + + , + +
    +     +
    + + + + + + + + + + + + + +
    + +
    +     + + + +     \ No newline at end of file diff --git a/tools/xsl/modelClassHandling.xsl b/tools/xsl/modelClassHandling.xsl new file mode 100644 index 00000000000..7cc0f79b295 --- /dev/null +++ b/tools/xsl/modelClassHandling.xsl @@ -0,0 +1,364 @@ + + + + + Created on: Nov 21, 2018 + Author: Johannes Kepper + + + + + + This template resolves model classes + + + +
    +

    +
    +
    + + + +
    + + + , + +
    +     +
    + + + + + + + + + + + + + +
    + +
    +     + + + +
    +
    Member of
    +
    + + + + +
    + + +
    +     + +
    + ( isn't member of any model class) +
    +     +
    +
    +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    + + + + +
    +     +     + + + +     +     + + + + + + + +     + +
    +
    Members
    +
    + – ( has no members) +
    +
    +     +     + +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    + textual content +
    +     + + + + +
    + + + + + + +
    +     + + + + + + + + + + + +     + +     + + + + + + + + + + +     + + + + + + + + + + + + + + +
    + + + + + + +
    +     + + + + + + +     + + + + + + + + + + + + + +     + + + + + + + +
    +
    + +
    + + + + + +
    + + + + + + +
    +     +
    +     + + + + + + + + +     + + + + + + + +
    +
    + + +
    + + + + +
    + + + + + + +
    +     + + + + +
    +     + + + + + + + + + + + + + + + + + + + + + + + + + + +     \ No newline at end of file diff --git a/tools/xsl/parseOdd.xsl b/tools/xsl/parseOdd.xsl new file mode 100644 index 00000000000..7b7aedcf171 --- /dev/null +++ b/tools/xsl/parseOdd.xsl @@ -0,0 +1,218 @@ + + + + + Created on: Nov 21, 2018 + Author: Johannes Kepper + + + + + + + + + + + + + + + +
    <> + + +
    +
    +
    +
    +
    +     + +
    +
    +
    +
    +     + +
    +
    +
    +     + +
    +
    +     + +
    +     +     + </>
    +     + +
    </></>
    +     +     +     + + + + + + +
    <!---->
    +     + + + ="" + + + + + ="" + ="" + + + + + ="" + + + + + + + + + + + + ="" + ="" + ="" + ="" + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + ⃥ + + + + + + + + + + ⃥ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +     \ No newline at end of file