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. u|d|s|n|sh|sl (\+|\-)?[AdMmP][0-9]+ 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. Analytical domain attributes. Gestural domain attributes. Logical domain attributes. Visual domain attributes. Sign representing one or more musical pitches. Analytical domain attributes. Gestural domain attributes. Logical 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. Sign representing a single pitched event, although the exact pitch may not be known. nc Notes: · Following the maxim that frequently-used elements should have abbreviated names, I took the liberty of re-naming to . @connection was also renamed to @con for the same reason. Serious consideration should be given to doing the same for @significativeletters and @hispanicloop. (MEI practice is for attributes to have lower-case names.) · Since attribute names can't contain spaces, "significative letters" and "diagonal right" were replaced by "significativeletters" and "diagonalright", respectively. · I didn't create @direction for either or since there's already an MEI attribute (@intm) for contour info. The suggested values for @direction have been lower-cased to fit existing practice with regard to coded values. · A Schematron rule was added to disallow @con on the first child of . The same could be done for @intm. · The attributes without a list of suggested values take a Boolean (true/false) value. · The values for attributes with a list of values were abbreviated -- "u" and "d", instead of "up" and "down", etc. oXygen will supply the full value as a tool tip when hand coding. · Since @form and @name (or something similar) wasn't part of the request, I assume the plan is to use some combination of @label, @type, or @class to name and classify neumes and neume components.