notationsubtype attribute semi-open list of values #835
martha-thomae
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The
@notationtype
attribute has a closed list of values:cmn
,mensural
,mensural.white
,mensural.black
,neume
, andtab
. In mensural notation, it is common to have the need to specify the subtype of notation we are dealing with: Ars antiqua, Ars nova, Italian trecento, etc. We usually do this using the@notationsubtype
attribute, which can have any value as long as it consists of only one token. I was wondering if, as is the case with other attributes (examples at the end),@notationsubtype
could be given a semi-open list of values that includes the three mentioned above:Ars_antiqua
,Ars_nova
,Italian_trecento
, while also allowing for any other token to be passed as value as well.I think that pre-defined values for known mensural notation subtypes can help at the moment of developing applications that deal with a particular style of mensural notation. The Measuring Polyphony Editor already needs to deal with notation style to determine how to interpret the notes entered by the user (as Ars antiqua or Ars nova). Having some type of agreement in a set of pre-defined values, while still keeping the list open to new values provided by the user, might prove helpful when transferring MEI files from one application to another.
A few examples of attributes that already have a semi-open list of values and still allow for user-provided values:
@removed.by
in<cutout>
has two pre-defined valuescut
andrip
, but it also allows for a user-provided value@glyph.auth
inatt.extSym
, which has a pre-defined valid valuesmufl
, but other user-provided values can be valid@evidence
attribute in the MEI.shared classatt.evidence
@func
for<bracketSpan>
with pre-defined valuescoloration
,cross-rhythm
, andligature
, but also receiving other valid values as well. Same with@func
in<pedal>
and@function
in<metaMark>
@form
of an element (e.g., in<incipCode>
,@form
can have any value from the semi-open list ofplaineAndEasie
,humdrumKern
, andparsons
, and other token entered by the user)@type
of an element (see<q>
,<nc>
, and<divLine>
)I wanted to bring this to the technical team to see if there are any objections before proposing it to the Mensural IG and discuss then the appropriate pre-defined values. Thank you!
Beta Was this translation helpful? Give feedback.
All reactions