From ichiro.fujinaga at mcgill.ca Thu May 11 09:26:27 2017 From: ichiro.fujinaga at mcgill.ca (Ichiro Fujinaga, Prof.) Date: Thu, 11 May 2017 07:26:27 +0000 Subject: [mei-neumes-ig] A draft for the new Neumes Module schema Message-ID: 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 element consists of one or more element(s). A is a single pitched event, although the exact pitch may not be known. Attributes for @direction (relative to the previous ) {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 @direction: pitch relative to the previous pitch () within the same {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 ) ================================ Ichiro -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: MEI_Neumes_ODD1.txt URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: mei-Neumes.rng Type: application/octet-stream Size: 813068 bytes Desc: mei-Neumes.rng URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: test-Neumes.mei Type: application/octet-stream Size: 5119 bytes Desc: test-Neumes.mei URL: From thomas.weber at notengrafik.com Thu May 11 12:15:29 2017 From: thomas.weber at notengrafik.com (Thomas Weber) Date: Thu, 11 May 2017 12:15:29 +0200 Subject: [mei-neumes-ig] A draft for the new Neumes Module schema In-Reply-To: References: Message-ID: <669d4351-0406-0fd5-a033-940990ca823e@notengrafik.com> An HTML attachment was scrubbed... URL: From ichiro.fujinaga at mcgill.ca Mon May 15 13:46:55 2017 From: ichiro.fujinaga at mcgill.ca (Ichiro Fujinaga, Prof.) Date: Mon, 15 May 2017 11:46:55 +0000 Subject: [mei-neumes-ig] Fwd: Un-Conference Day References: <5297_1494832716_5919564B_5297_20_1_cea46eeb4e7245bfbf9c6eca30bdcd28@BY1PR03MB1481.namprd03.prod.outlook.com> Message-ID: To those attending MEC this week, Read below. Anyone interested in attending the Metadata and Cataloging Interest Group meeting as well as our meeting? If so, should we meet from 2:30-4pm on Friday? Anyone planning to leave earlier on Friday? Ichiro Begin forwarded message: From: Vincent Besson > Subject: Re: Un-Conference Day Date: May 15, 2017 at 9:18:03 AM GMT+2 To: "Ichiro Fujinaga, Prof." > Cc: Philippe Rigaux >, Internal List for the MEI Board >, "Di Bacco, Giuliano" > Resent-From: > Dear Ichiro, The Friday, at 10:00, there is the Medadata and Cataloging Interest Group registred. Is it possible to have in parallel the MEI Neumes interest Group ? Best, Vincent ----- Mail original ----- De: "ichiro fujinaga" > À: "Philippe Rigaux" >, "Vincent Besson" > Cc: "Internal List for the MEI Board" >, "Di Bacco, Giuliano" > Envoyé: Lundi 15 Mai 2017 01:59:54 Objet: Un-Conference Day Dear Philippe & Vincent, I would like to organize the MEI-Neumes Interest Group meeting on the Friday 19 May. I propose to have this at: 10:00-11:30 I believe MEI-Mensural Interest Group meeting can be held at 11:30-13:00 (I’ve been in communication with Giuliano) then the Hackathon in the afternoon, although I’m not sure who is organizing this. Let us know if this works. Ichiro -- Vincent BESSON ♦ CENTRE D'ÉTUDES SUPÉRIEURES DE LA RENAISSANCE – http://www.cesr.cnrs.fr/ ♦ CONSORTIUM MUSICA – https://musica.hypotheses.org/ 59, rue Néricault-Destouches BP 12050 37020 Tours Cedex France +33 2 47 36 77 84 -------------- next part -------------- An HTML attachment was scrubbed... URL: From inga.behrendt at uni-tuebingen.de Mon May 15 19:04:35 2017 From: inga.behrendt at uni-tuebingen.de (Inga Behrendt) Date: Mon, 15 May 2017 19:04:35 +0200 Subject: [mei-neumes-ig] A draft for the new Neumes Module schema In-Reply-To: Message-ID: <20170515190435.Horde.2OpieuFhQy-zipjmCLs-ePq@webmail.uni-tuebingen.de> Dear Ich, dear Perry, thank you so much for this sending! The qualifying examinations take place on Friday, 19th of May, in our Musikhochschule in Rottenburg. It´ll start in the morning, and I´ll have to be in the committee until around 5pm. Unfortunately I´ll miss the Meeting. But, perhaps someone can take minutes? Inga Zitat von "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 element consists of one or more element(s). > > A is a single pitched event, although the exact > pitch may not be known. > > Attributes for > @direction (relative to the previous ) {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 > @direction: pitch relative to the previous pitch () > within the same {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 ) > > ================================ > > Ichiro From stefan.morent at uni-tuebingen.de Wed May 17 16:00:13 2017 From: stefan.morent at uni-tuebingen.de (Prof. Dr. Morent) Date: Wed, 17 May 2017 16:00:13 +0200 Subject: [mei-neumes-ig] A draft for the new Neumes Module schema In-Reply-To: Message-ID: <20170517160013.Horde.i-A6zxp4724sVI6XZtZsWgr@webmail.uni-tuebingen.de> Dear Perry, dear Ichirio, dear list, thank you very much for the further work on the MEI neumes module after our meeting at Tübingen, November 16. Unfortunately I can't attend the meeting at Tours this Friday, but would be great to get minutes or reports on this list. best Stefan PS Great art work in particular of this unknown incarnation of Hildegard :-)) ----- Nachricht von "Ichiro Fujinaga, Prof." --------- Datum: Thu, 11 May 2017 07:26:27 +0000 Von: "Ichiro Fujinaga, Prof." Antwort an: "Ichiro Fujinaga, Prof." , Neumes Interest Group of the Music Encoding Initiative Betreff: [mei-neumes-ig] A draft for the new Neumes Module schema An: Neumes Interest Group of the Music Encoding Initiative > 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 element consists of one or more element(s). > > A is a single pitched event, although the exact > pitch may not be known. > > Attributes for > @direction (relative to the previous ) {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 > @direction: pitch relative to the previous pitch () > within the same {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 ) > > ================================ > > Ichiro > > > > ----- Ende der Nachricht von "Ichiro Fujinaga, Prof." ----- -------------- next part -------------- An HTML attachment was scrubbed... URL: From thomas.weber at notengrafik.com Thu May 18 16:31:36 2017 From: thomas.weber at notengrafik.com (Thomas Weber) Date: Thu, 18 May 2017 16:31:36 +0200 Subject: [mei-neumes-ig] A draft for the new Neumes Module schema In-Reply-To: References: Message-ID: An HTML attachment was scrubbed... URL: From Jennifer.Bain at Dal.Ca Wed May 24 22:35:23 2017 From: Jennifer.Bain at Dal.Ca (Jennifer Bain) Date: Wed, 24 May 2017 20:35:23 +0000 Subject: [mei-neumes-ig] A draft for the new Neumes Module schema In-Reply-To: References:

Message-ID: I like all of Thomas Weber’s suggestions below. I hope there was a fruitful discussion in Tours, and I would also love to see the minutes if they are available. The syllable issue in relation to mensural modules is interesting. Is there a way to work around this? Having the syllable indicated is a huge step in being able to relate text and music computationally, so I wouldn’t want to lose that with the chant notation, but it is completely inappropriate in a mensural context. Thanks everyone for your work on this! All the best, Jennifer Jennifer Bain, Ph.D. Associate Professor Fountain School of Performing Arts bainj at dal.ca Dalhousie University 6101 University Avenue Halifax, NS, B3H 4R2, Canada Check out this Hildegard bibliography: http://hildegard.music.dal.ca/index.php Recent book: Hildegard of Bingen and Musical Reception: the Modern Revival of a Medieval Composer (Cambridge, 2015) From: mei-neumes-ig > on behalf of Thomas Weber > Reply-To: Neumes Interest Group of the Music Encoding Initiative > Date: Thursday, May 18, 2017 at 11:31 To: Neumes Interest Group of the Music Encoding Initiative > 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 inside to encode pitch information for diastematic notation - or alternatively, @pname/@oct on . is probably preferable. * Currently, you can put inside . 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 element. * Accidentals that are not attached to a neume, i.e. sort-of-but-not-quite key signatures. To use the currently allowed (inside ) 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 elements - most of the time (but not always) immediately after a . * We need to encode rubrics and would introduce a element inside , 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 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 element consists of one or more element(s). A is a single pitched event, although the exact pitch may not be known. Attributes for @direction (relative to the previous ) {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 @direction: pitch relative to the previous pitch () within the same {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 ) ================================ Ichiro _______________________________________________ mei-neumes-ig mailing list mei-neumes-ig at lists.uni-paderborn.dehttps://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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew.hankinson at mail.mcgill.ca Thu May 25 11:15:10 2017 From: andrew.hankinson at mail.mcgill.ca (Andrew Hankinson) Date: Thu, 25 May 2017 09:15:10 +0000 Subject: [mei-neumes-ig] A draft for the new Neumes Module schema In-Reply-To: <12129_1495658134_5925EE95_12129_124_17_D54B73C1.32355%bainj@dal.ca> References:

<12129_1495658134_5925EE95_12129_124_17_D54B73C1.32355%bainj@dal.ca> Message-ID: <44072501-8EFB-467C-A4FB-87A1E2A05CBF@mail.mcgill.ca> Music and "lyrical content" (i.e., sung texts) are always encoded in relationship to each other in MEI; the question for chant is whether the syllable is the primary organizational object, and how we reconcile that with later repertoires that can have non-sung content. In neume notation, we are organizing the music using: syllable syl ("Je-"): Carries the actual text that is sung; neume(s) while in mensural the 'syllable' disappears (since you can have instrumental mensural notation): note syl ("Je-") In both cases we encode the text with the music; the difference being a "philosophical" one about the primacy of the syllable as an organizational principle in the music. The 'syl' in neume notation is optional, but the 'syllable' isn't. This reflects the idea that there is always a sung text in neume notation, but we may not always know what that text is. -Andrew > On 24 May 2017, at 21:35, Jennifer Bain wrote: > > I like all of Thomas Weber’s suggestions below. I hope there was a fruitful discussion in Tours, and I would also love to see the minutes if they are available. > > The syllable issue in relation to mensural modules is interesting. Is there a way to work around this? Having the syllable indicated is a huge step in being able to relate text and music computationally, so I wouldn’t want to lose that with the chant notation, but it is completely inappropriate in a mensural context. > > Thanks everyone for your work on this! > > All the best, > > Jennifer > > > > Jennifer Bain, Ph.D. > Associate Professor > Fountain School of Performing Arts > > bainj at dal.ca > > Dalhousie University > 6101 University Avenue > Halifax, NS, B3H 4R2, Canada > > Check out this Hildegard bibliography: http://hildegard.music.dal.ca/index.php > > Recent book: Hildegard of Bingen and Musical Reception: the Modern Revival of a Medieval Composer (Cambridge, 2015) > > From: mei-neumes-ig on behalf of Thomas Weber > Reply-To: Neumes Interest Group of the Music Encoding Initiative > Date: Thursday, May 18, 2017 at 11:31 > To: Neumes Interest Group of the Music Encoding Initiative > 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 inside to encode pitch information for diastematic notation - or alternatively, @pname/@oct on . is probably preferable. > • Currently, you can put inside . 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 element. > • Accidentals that are not attached to a neume, i.e. sort-of-but-not-quite key signatures. To use the currently allowed (inside ) 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 elements - most of the time (but not always) immediately after a . > • We need to encode rubrics and would introduce a element inside , 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 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 element consists of one or more element(s). >> >> A is a single pitched event, although the exact pitch may not be known. >> >> Attributes for >> @direction (relative to the previous ) {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 >> @direction: pitch relative to the previous pitch () within the same {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 ) >> >> ================================ >> >> Ichiro >> >> >> >> >> >> _______________________________________________ >> mei-neumes-ig mailing list >> >> mei-neumes-ig at lists.uni-paderborn.dehttps://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 > > _______________________________________________ > mei-neumes-ig mailing list > mei-neumes-ig at lists.uni-paderborn.de > https://lists.uni-paderborn.de/mailman/listinfo/mei-neumes-ig From jason.stoessel at une.edu.au Thu May 25 12:44:16 2017 From: jason.stoessel at une.edu.au (Jason Stoessel) Date: Thu, 25 May 2017 20:44:16 +1000 Subject: [mei-neumes-ig] A draft for the new Neumes Module schema In-Reply-To: <44072501-8EFB-467C-A4FB-87A1E2A05CBF@mail.mcgill.ca> References:

<12129_1495658134_5925EE95_12129_124_17_D54B73C1.32355%bainj@dal.ca> <44072501-8EFB-467C-A4FB-87A1E2A05CBF@mail.mcgill.ca> Message-ID: <25AD4860-6631-43FC-B929-C449780C0A32@une.edu.au> An HTML attachment was scrubbed... URL: From pdr4h at eservices.virginia.edu Thu May 25 17:01:06 2017 From: pdr4h at eservices.virginia.edu (Roland, Perry D. (pdr4h)) Date: Thu, 25 May 2017 15:01:06 +0000 Subject: [mei-neumes-ig] A draft for the new Neumes Module schema In-Reply-To: <25AD4860-6631-43FC-B929-C449780C0A32@une.edu.au> References:

<12129_1495658134_5925EE95_12129_124_17_D54B73C1.32355%bainj@dal.ca> <44072501-8EFB-467C-A4FB-87A1E2A05CBF@mail.mcgill.ca> <25AD4860-6631-43FC-B929-C449780C0A32@une.edu.au> Message-ID: Hi Jason, To be precise, isn’t being excluded from mensural notation in MEI because it was never there in the first place. Let me explain – is declared in the Neumes module. In other words, it can only appear when that module is active. The Mensural customization switches off the Neumes module, making disappear. The Neumes customization, on the other hand, turns off features found in mensural notation. This may sound dire for Scribe, but there’s a relatively simple solution -- create a customization that activates both the Neumes and Mensural modules. The MEI-all customization turns on both modules, but it also permits CMN features, which may get in your way, so I recommend creating a new customization that contains the features that you want and excludes those you don’t. HTH, -- p. From: mei-neumes-ig [mailto:mei-neumes-ig-bounces+pdr4h=eservices.virginia.edu at lists.uni-paderborn.de] On Behalf Of Jason Stoessel Sent: Thursday, May 25, 2017 6:44 AM To: Neumes Interest Group of the Music Encoding Initiative Subject: Re: [mei-neumes-ig] A draft for the new Neumes Module schema The disregard of as a possible organisational unit in mensural as opposed to chant is of core concern to the the Scribe project in which both systems are organised around syllable. It is a key point of difference in which the Scribe project is currently irreconcilable with MEI mensural. So I am interested in where this discussion might “go”. JS On 25 May 2017, at 7:15 PM, Andrew Hankinson > wrote: Music and "lyrical content" (i.e., sung texts) are always encoded in relationship to each other in MEI; the question for chant is whether the syllable is the primary organizational object, and how we reconcile that with later repertoires that can have non-sung content. In neume notation, we are organizing the music using: syllable syl ("Je-"): Carries the actual text that is sung; neume(s) while in mensural the 'syllable' disappears (since you can have instrumental mensural notation): note syl ("Je-") In both cases we encode the text with the music; the difference being a "philosophical" one about the primacy of the syllable as an organizational principle in the music. The 'syl' in neume notation is optional, but the 'syllable' isn't. This reflects the idea that there is always a sung text in neume notation, but we may not always know what that text is. -Andrew On 24 May 2017, at 21:35, Jennifer Bain > wrote: I like all of Thomas Weber’s suggestions below. I hope there was a fruitful discussion in Tours, and I would also love to see the minutes if they are available. The syllable issue in relation to mensural modules is interesting. Is there a way to work around this? Having the syllable indicated is a huge step in being able to relate text and music computationally, so I wouldn’t want to lose that with the chant notation, but it is completely inappropriate in a mensural context. Thanks everyone for your work on this! All the best, Jennifer Jennifer Bain, Ph.D. Associate Professor Fountain School of Performing Arts bainj at dal.ca Dalhousie University 6101 University Avenue Halifax, NS, B3H 4R2, Canada Check out this Hildegard bibliography: http://hildegard.music.dal.ca/index.php Recent book: Hildegard of Bingen and Musical Reception: the Modern Revival of a Medieval Composer (Cambridge, 2015) From: mei-neumes-ig > on behalf of Thomas Weber > Reply-To: Neumes Interest Group of the Music Encoding Initiative > Date: Thursday, May 18, 2017 at 11:31 To: Neumes Interest Group of the Music Encoding Initiative > 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 inside to encode pitch information for diastematic notation - or alternatively, @pname/@oct on . is probably preferable. • Currently, you can put inside . 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 element. • Accidentals that are not attached to a neume, i.e. sort-of-but-not-quite key signatures. To use the currently allowed (inside ) 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 elements - most of the time (but not always) immediately after a . • We need to encode rubrics and would introduce a element inside , 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 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 element consists of one or more element(s). A is a single pitched event, although the exact pitch may not be known. Attributes for @direction (relative to the previous ) {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 @direction: pitch relative to the previous pitch () within the same {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 ) ================================ Ichiro _______________________________________________ mei-neumes-ig mailing list mei-neumes-ig at lists.uni-paderborn.dehttps://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 _______________________________________________ mei-neumes-ig mailing list mei-neumes-ig at lists.uni-paderborn.de https://lists.uni-paderborn.de/mailman/listinfo/mei-neumes-ig _______________________________________________ mei-neumes-ig mailing list mei-neumes-ig at lists.uni-paderborn.de https://lists.uni-paderborn.de/mailman/listinfo/mei-neumes-ig Dr Jason Stoessel, BMus/BA, BA Hons, PhD Coordinator of Bachelor of Music with Honours Coordinator of Research Seminar Series School of Arts University of New England ARMIDALE NSW 2351 AUSTRALIA jason.stoessel at une.edu.au Skype ID: jjstoessel FaceTime: jason.stoessel at gmail.com une-au.academia.edu/JasonStoessel -- Chief Investigator, ARC Discovery Project (DP150102135) “Canonic techniques and musical change, c.1330–c.1530" -- CRICOS Provider Number: 00003G _______________________________________________ mei-neumes-ig mailing list mei-neumes-ig at lists.uni-paderborn.de https://lists.uni-paderborn.de/mailman/listinfo/mei-neumes-ig -------------- next part -------------- An HTML attachment was scrubbed... URL: From pdr4h at eservices.virginia.edu Thu May 25 18:02:17 2017 From: pdr4h at eservices.virginia.edu (Roland, Perry D. (pdr4h)) Date: Thu, 25 May 2017 16:02:17 +0000 Subject: [mei-neumes-ig] A draft for the new Neumes Module schema In-Reply-To: References:

Message-ID: 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 but not others. Also, are we likely to have the same issue with other attributes of ? 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 , but I’d like to hear why you think adding inside is preferable. I’m confused with regard to one of your suggestions about . You want to appear between elements and that’s exactly where they can currently occur, but that makes them children of , which you say you don’t want. Once you’ve cleared that up, adding as a child of isn’t a problem. Likewise, adding 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 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 inside to encode pitch information for diastematic notation - or alternatively, @pname/@oct on . is probably preferable. * Currently, you can put inside . 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 element. * Accidentals that are not attached to a neume, i.e. sort-of-but-not-quite key signatures. To use the currently allowed (inside ) 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 elements - most of the time (but not always) immediately after a . * We need to encode rubrics and would introduce a element inside , 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 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 element consists of one or more element(s). A is a single pitched event, although the exact pitch may not be known. Attributes for @direction (relative to the previous ) {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 @direction: pitch relative to the previous pitch () within the same {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 ) ================================ Ichiro _______________________________________________ mei-neumes-ig mailing list 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From pdr4h at eservices.virginia.edu Fri May 26 15:44:29 2017 From: pdr4h at eservices.virginia.edu (Roland, Perry D. (pdr4h)) Date: Fri, 26 May 2017 13:44:29 +0000 Subject: [mei-neumes-ig] A draft for the new Neumes Module schema References:

Message-ID: Thomas, What if we added “u” (for unspecified) to the list of values for @quilisma and @oriscus? Would the same thing need to be done for other attributes of , i.e., @curved, @diagonal, @connection? -- p. From: Roland, Perry D. (pdr4h) Sent: Thursday, May 25, 2017 12:02 PM To: 'Neumes Interest Group of the Music Encoding Initiative' Subject: RE: [mei-neumes-ig] A draft for the new Neumes Module schema 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 but not others. Also, are we likely to have the same issue with other attributes of ? 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 , but I’d like to hear why you think adding inside is preferable. I’m confused with regard to one of your suggestions about . You want to appear between elements and that’s exactly where they can currently occur, but that makes them children of , which you say you don’t want. Once you’ve cleared that up, adding as a child of isn’t a problem. Likewise, adding 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 > 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 inside to encode pitch information for diastematic notation - or alternatively, @pname/@oct on . is probably preferable. * Currently, you can put inside . 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 element. * Accidentals that are not attached to a neume, i.e. sort-of-but-not-quite key signatures. To use the currently allowed (inside ) 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 elements - most of the time (but not always) immediately after a . * We need to encode rubrics and would introduce a element inside , 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 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 element consists of one or more element(s). A is a single pitched event, although the exact pitch may not be known. Attributes for @direction (relative to the previous ) {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 @direction: pitch relative to the previous pitch () within the same {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 ) ================================ Ichiro _______________________________________________ mei-neumes-ig mailing list 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From inga.behrendt at uni-tuebingen.de Mon May 29 21:29:47 2017 From: inga.behrendt at uni-tuebingen.de (Inga Behrendt) Date: Mon, 29 May 2017 21:29:47 +0200 Subject: [mei-neumes-ig] A draft for the new Neumes Module schema In-Reply-To: References:

Message-ID: <20170529212947.Horde.g_umdIbfaZ-mtZdKtf-R90o@webmail.uni-tuebingen.de> 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 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)" : > 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 but not others. Also, are we likely to have > the same issue with other attributes of ? 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 , but > I’d like to hear why you think adding inside is > preferable. > > I’m confused with regard to one of your suggestions about . > You want to appear between elements and that’s > exactly where they can currently occur, but that makes them children > of , which you say you don’t want. Once you’ve cleared > that up, adding as a child of isn’t a problem. > > Likewise, adding 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 > > 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 inside to encode pitch information for > diastematic notation - or alternatively, @pname/@oct on . > is probably preferable. > * Currently, you can put inside . 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 element. > * Accidentals that are not attached to a neume, i.e. > sort-of-but-not-quite key signatures. To use the currently allowed > (inside ) 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 elements - most of > the time (but not always) immediately after a . > > * We need to encode rubrics and would introduce a > element inside , 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 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 element consists of one or more element(s). > > A is a single pitched event, although the exact > pitch may not be known. > > Attributes for > @direction (relative to the previous ) {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 > @direction: pitch relative to the previous pitch () > within the same {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 ) > > ================================ > > Ichiro > > > > > > _______________________________________________ > > mei-neumes-ig mailing list > > 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