[mei-neumes-ig] A draft for the new Neumes Module schema

Inga Behrendt inga.behrendt at uni-tuebingen.de
Mon May 29 21:29:47 CEST 2017 

Dear List, dear Perry, dear Thomas,

I´m not sure whether I misunderstood the discussion.  It might be that
my item carries away from what Thomas wanted to say. Perhaps he´s/you  
are simply speaking about the technical structure of the MEI-Code?  
That´s why I do not know whether my wording fits. Please have look.


***

Of course, I do not like to lose any attributes.

Later on it should be possible to search for a curved, ad diagonal, a  
connected, a Quilisma-, a Oriscus ... neutral/high/same... Note.
Actually, if we give up all the attributes, we end up with incoding  
Hufnagel or Square-Notation. (Remember all These different Levels of  
nail Notation, square - notations that we know of...)

And for the semilogists that I know and that I´m, too: We would love  
to find out more about the usage of the Quilisma and the Oriscus.  
Perhaps we can understand more about the performance practise of the  
singing when an Oriscus appears.

***

But perhaps the discussion is only reflecting different levels within  
the code structure? - like my impression of the discussion of the  
<syllable> was.   ?

***

I liked that Perry suggested to speak of moduls, that can be switched  
on or not ("The MEI-all customization turns on both modules, but it  
also permits CMN features, which may get in your way, so I reccomend  
creating a new customization that contains the Features that you want  
and excludes those you don´t.").

The amount of attributes is not restricted, right? I thought we can  
add more and more, as we identify more and more new neumes (Armenian  
neumes etc.)...
Why do you, dear Thomas, want to reduce it (Quilisma/Oriscus)? I  
thought he can use one modul or not. Right?

Herzlich, yours
Inga





Zitat von "Roland, Perry D. (pdr4h)" <pdr4h at eservices.virginia.edu>:

> Hi Thomas,
>
> Mixing primitive datatypes; that is, “true|false|2|3”, creates a  
> number of issues that I’d like to avoid.  But there are other  
> options –
>
>
> 1.       creating, as you suggest, two attributes each for quilisma  
> and orisicus: quilisima and quilisma.form and orisicus and  
> oriscus.form,
>
> 2.       promoting @quilisma and @oriscus to element status and  
> giving them attributes to describe their visual qualities,
>
> 3.       creation of a customization for your project that  
> substitutes “true|false” for “2|3” in the official schema.
>
> We explored the 2nd possibility in Tours, but I’m not convinced  
> that’s the best path because it creates inconsistency by promoting  
> some attributes of <nc> but not others.  Also, are we likely to have  
> the same issue with other attributes of <nc>?  For instance, should  
> the presence of a diagonalright (whatever that is) be separate from  
> whether it’s pointing up or down?  So, I’m inclined toward the 3rd  
> option.
>
> Adding @strophicus is simple, but what should its values be?   
> True/false, like oriscus, etc. or something else?
>
> To deal with pitch, we decided to add @pname and @oct on <nc>, but  
> I’d like to hear why you think adding <note> inside <nc> is  
> preferable.
>
> I’m confused with regard to one of your suggestions about <accid>.   
> You want <accid> to appear between <neume> elements and that’s  
> exactly where they can currently occur, but that makes them children  
> of <syllable>, which you say you don’t want.  Once you’ve cleared  
> that up, adding <accid> as a child of <neume> isn’t a problem.
>
> Likewise, adding <rubric> poses no problems.  It should also come in  
> handy for mensural notation.
>
> --
> p.
>
>
> From: mei-neumes-ig  
> [mailto:mei-neumes-ig-bounces at lists.uni-paderborn.de] On Behalf Of  
> Thomas Weber
> Sent: Thursday, May 18, 2017 10:32 AM
> To: Neumes Interest Group of the Music Encoding Initiative  
> <mei-neumes-ig at lists.uni-paderborn.de>
> Subject: Re: [mei-neumes-ig] A draft for the new Neumes Module schema
>
> Dear list,
>
> because Elaine and me aren't in Tours, we looked through the draft  
> together and would like to give our input for the upcoming meeting.   
> From the perspective of Corpus monodicum, this definitely is heading  
> in the right direction.  There are some changes we'd suggest:
>
>   *   Quilisma/Oriscus: So far, we've only encoded whether something  
> is or is not an oriscus or quilisma - i.e. no more detailed  
> information about the shape.  The project won't change that, so we'd  
> like to suggest to also offer a simple "true/false" option, like  
> with @episima.  Mixing boolean and numbers is a little odd, but the  
> alternative would be two separate attributes, which wouldn't be any  
> handier.
>   *   We'd suggest a strophicus attribute.  Strophici could be  
> handled using taxonomies, but they are so common that we think they  
> deserve their own attribute, just like oriscus and quilisma.
>   *   We'd need <note> inside <nc> to encode pitch information for  
> diastematic notation - or alternatively, @pname/@oct on <nc>. <note>  
> is probably preferable.
>   *   Currently, you can put <accid> inside <syllable>.  I don't  
> think this is the appropriate place to put an accidental.  We have  
> two situations where we have to deal with accidentals:
>
>      *   Accidentals that are "attached to" a neume.  It would make  
> most sense if they were child elements of that <neume> element.
>      *   Accidentals that are not attached to a neume, i.e.  
> sort-of-but-not-quite key signatures.  To use the currently allowed  
> <keySig> (inside <staffDef>) in these situations doesn't seem  
> appropriate.  It would suggest that use and implications of these  
> accidentals are identical to modern key signatures, which as far as  
> I understand is not the case - or we lack that knowledge.  It would  
> be useful to put them right between the <neume> elements - most of  
> the time (but not always) immediately after a <sb>.
>
>   *   We need to encode rubrics and would introduce a <rubric>  
> element inside <layer>, ideally with a @type attribute that might be  
> an open list with suggested values feast (e.g. for a rubric "De  
> Sancto Stephano"), service (e.g. for a rubric "Ad summam missam")  
> and genre (e.g. for a rubric "Alleluia").
> During the last meeting in Tübingen, the <syllable> element was  
> challenged.  I think one motivation was to make the hierarchy of the  
> neumes and mensural modules more compatible for projects that have  
> to deal with both.  We can't say a lot about that, though.
>
> To everybody in Tours:  Have a great un-conference day!
> Thomas
>
>
> Am 11.05.2017 um 09:26 schrieb Ichiro Fujinaga, Prof.:
> Dear List,
>
> Perry Roland has kindly worked on a new version of the MEI Neumes  
> Module schema.
> This was based on my suggestions, which were based on the  
> discussions at the last MEI Neumes Interest Group (19 November 2016,  
> Tübingen) and at various Cantus Ultimus meetings.
>
> I hope this will be a staring point for fruitful discussions on this  
> list and at the upcoming Neumes Interest Group meeting in Tours on  
> Friday 19 May.
>
> Attached are an ODD file with Perry’s comments at the bottom; an RNG  
> file; and a test MEI file. All provided by Perry.
> Below is what I provided to Perry.
>
> ================================
>
> A <neume> element consists of one or more <neumeComponent> element(s).
>
> A <neumeComponent> is a single pitched event, although the exact  
> pitch may not be known.
>
> Attributes for <neume>
> @direction (relative to the previous <neume>) {N|S|L|H|SH|SL}
>    N: neutral or unknown
>    H: higher
>    L: lower
>    S: same
>    SH: same or higher (but not lower)
>    SL: same or lower (but not higher)
> @significative letters
> @hispanicLoop (not sure about this)
>
> Attributes for <neumeComponent>
> @direction: pitch relative to the previous pitch (<neumeComponent>)  
> within the same <neume> {N|S|L|H|SH|SL}
>    N: neutral or unknown
>    H: higher
>    L: lower
>    S: same or unison
>    SH: same or higher (but not lower)
>    SL: same or lower (but not higher)
> @wavy
> @curved (anticlockwise, clockwise)
> @angled
> @episma
> @flat
> @jagged
> @liquescence
> @extended
> @diagonal right (up or down)
> @quilisma (2 or 3 curves)
> @long
> @oriscus (curved, flat, jagged)
> @connection (gapped, looped) (to the previous neumeComponent within  
> the same <neume>)
>
> ================================
>
> Ichiro
>
>
>
>
>
> _______________________________________________
>
> mei-neumes-ig mailing list
>
> mei-neumes-ig at lists.uni-paderborn.de<mailto:mei-neumes-ig at lists.uni-paderborn.de>
>
> https://lists.uni-paderborn.de/mailman/listinfo/mei-neumes-ig
>
>
>
> --
>
>
>
> Notengrafik Berlin GmbH
>
> HRB 15007
>
>
>
> UstID: DE 289234097
>
> Geschäftsführer:
>
> Thomas Weber und Werner J. Wolff
>
>
>
> fon: +49 30 220661685
>
>
>
> Leuschnerdamm 13
>
> 10999 Berlin
>
>
>
> notengrafik.com



Hochschule für Kirchenmusik
der Diözese Rottenburg-Stuttgart
St.-Meinrad-Weg 6
72108 Rottenburg
http://www.kirchenmusik-hochschule.org/

Eberhard Karls Universität Tübingen
Musikwissenschaftliches Institut
Schulberg 2
72070 Tübingen
E-Mail: inga.behrendt at uni-tuebingen.de

Tel.: +49 1520 610 16 44

http://gregorien.info/
http://www.aiscgre.org/
http://cantus.simssa.ca/
https://uncinussite.wordpress.com/
https://opticalneumerecognition.wordpress.com/activities/

http://www.uni-tuebingen.de/fakultaeten/philosophische-fakultaet/fachbereiche/altertums-und-kunstwissenschaften/mwi/studium.html

More information about the mei-neumes-ig mailing list