From ichiro.fujinaga at mcgill.ca Wed Jun 6 21:55:51 2018 From: ichiro.fujinaga at mcgill.ca (Ichiro Fujinaga, Prof.) Date: Wed, 6 Jun 2018 19:55:51 +0000 Subject: [mei-neumes-ig] Fwd: [MEI-L] Report from the Community Meeting at MEC2018 References: <7747_1527673069_5B0E70ED_7747_50_1_BE8143A8-D935-4F06-A48D-8BC762B88CD5@edirom.de> Message-ID: Dear members of the MEI-Neumes Interest Group, I?m not sure if you noticed at the beginning of the fifth paragraph of the Report from Johannes (see below), where he says: "For version 4.0 of the MEI Schema, we're waiting for some last-minute changes from one of our Interest Groups.? That would be us. :-) So the deadline is now July 1. I?ve uploaded the latest version of the Draft at http://bit.ly/MEI_Neumes_0_2_3 It?s still undergoing changes, such as, @class / @type and . The MEI is an evolving encoding system and we can always make changes. Also we won?t know the consequences of these changes until we thoroughly use it and test it. But let?s try to make this as best as we can before the deadline. Please post your questions, concerns, and edits on this mailing list. Thank you, Ichiro Begin forwarded message: From: Johannes Kepper > Subject: [MEI-L] Report from the Community Meeting at MEC2018 Date: May 30, 2018 at 5:32:21 AM GMT-4 To: Music Encoding Initiative > Reply-To: Music Encoding Initiative > Dear Members of the MEI, for those of you who weren't able to join us, here's a report from last week's Community Meeting. First of all, we had a wonderful Music Encoding Conference over in College Park, with an exciting program and good organisation ? thanks again to Karen, Raffaele, Stephen and their respective teams. MEC2019 will be hosted by a team led by Robert Klugseder (Austrian Academy of Sciences) and Franz Kelnreiter (Mozarteum Salzburg), and will be held from May 29 to June 1 in wonderful Vienna. We're excited that Kevin Page (Oxford) will serve as Program Chair. We encouraged institutions to respond to our Call for Hosting MEC2020, which is open until August 1. While we've been able to alternate between Europe and North America so far, that's not a strict requirement. However, we'd be happy to strengthen our North American Community by having another conference there in 2020. Interested parties are invited to reach out to Raff Viglianti or the MEI Board to discuss possible proposals upfront. As in previous years, MEI has three Institutional Members: ZenMEM (2500? / year), the ?AW (500? / year) and TiDo (500$ / year). With their support, we've been able to sponsor student bursaries at Music Encoding Conferences. For version 4.0 of the MEI Schema, we're waiting for some last-minute changes from one of our Interest Groups. The current plan is to have these ready by July 1, and to release the new version shortly thereafter. As Perry may not use his official working time for MEI anymore, the MEI Board would like to initiate annual developer meetings in fall. These meetings will have a specific topic, and are open to anyone who wants to actively contribute work to that topic. Sending delegates to these workshops will be accepted as in-kind contribution, which means that such institutions will be treated as Institutional Members of MEI (for that year) and will get their logo on the MEI website. Our Technical Chairs will announce a date and topic for such a workshop in the next few weeks; interested people are requested to respond to that. If your institution may not be able to support you with travel money, please contact the Technical Chairs anyway. While there is no formal procedure for this ready yet, the Board is willing to step in and support such cases with MEI money. The proceedings for MEC2015 and 2016 will be bundled together and will go out for final author corrections very soon. Proceedings for MEC2017 will be combined with this year's submissions. There will be a separate announcement to this year's authors in the coming week, but basically the same rules as for the last years apply: Please submit either a simple Word file, or try to follow the guidelines given at https://github.com/music-encoding/mec-proceedings. Deadline for submissions will be August 31. We hope to get both volumes ? MEC2015+16 and MEC2017+18 ? out by the end of the year. During the Community meeting, we intensively discussed ways on how to improve communication on MEI-L and elsewhere. This also involved discussions about (paid) memberships. It seems like MEI has changed over the last couple of years, and we may have to respond to these changes accordingly. A very simple suggestion is to make sure that all the tools developed should be listed at http://music-encoding.org/resources/tools.html, while all projects using MEI should be listed at http://music-encoding.org/community/projects-users.html. Both pages can be modified through Github (please submit pull requests). If you need assistance, our Technical Team will happily support you. However, it is your responsibility to speak up and get your activities listed there. Regarding the major issues of improving communication / reorganising MEI, we plan to set up a dedicated working group in the coming weeks. There will be a separate mail for that, but if you already know that you'd like to participate in that effort, please contact me off-list. There will be no separate minutes from the Board meeting at MEC2018, as we've mostly prepared the topics discussed at the Community Meeting. If there are questions, additions, suggestions etc., please comment. With best regards, jo _______________________________________________ mei-l mailing list mei-l at lists.uni-paderborn.de https://lists.uni-paderborn.de/mailman/listinfo/mei-l -------------- next part -------------- An HTML attachment was scrubbed... URL: From ichiro.fujinaga at mcgill.ca Thu Jun 21 17:16:27 2018 From: ichiro.fujinaga at mcgill.ca (Ichiro Fujinaga, Prof.) Date: Thu, 21 Jun 2018 15:16:27 +0000 Subject: [mei-neumes-ig] Liquescent Message-ID: <5B921D0C-8630-486B-82C0-0853DFEA77CB@mcgill.ca> Dear all, Currently (http://bit.ly/MEI_Neumes_0_2_3), a liquescent is encoded as a boolean attribute of : @liques On the other hand, episema is an element with its own attributes: @form {vert | horiz} @place {n | ne | e | se | s | sw | w | nw} (the placement of the episema with respect to the or with which it is associated) My question is whether liquescent should be an element? Do we need to encode different ?forms? of liquescents? Do we need to encode different placements of liquescents? Or something else? Ichiro From micahjwalter at gmail.com Thu Jun 21 17:23:18 2018 From: micahjwalter at gmail.com (Micah John Walter) Date: Thu, 21 Jun 2018 11:23:18 -0400 Subject: [mei-neumes-ig] Liquescent In-Reply-To: <5B921D0C-8630-486B-82C0-0853DFEA77CB@mcgill.ca> References: <5B921D0C-8630-486B-82C0-0853DFEA77CB@mcgill.ca> Message-ID: <4B014E85-8315-4290-9A9D-19780752FC8E@gmail.com> Dear Ichiro and all, Well, one thing I can think of is whether, for neumes on a staff, the notehead is visible. (Liquescent neumes without a clear notehead are, I believe, a predecessor to the plica.) If this were to be encoded, however, it could be an attribute on the rather than a liquescent element. Micah > On 21 June 2018, at 11:16, Ichiro Fujinaga, Prof. wrote: > > Dear all, > > Currently (http://bit.ly/MEI_Neumes_0_2_3), a liquescent is encoded as a boolean attribute of : @liques > > On the other hand, episema is an element with its own attributes: > @form {vert | horiz} > @place {n | ne | e | se | s | sw | w | nw} (the placement of the episema with respect to the or with which it is associated) > > My question is whether liquescent should be an element? > > Do we need to encode different ?forms? of liquescents? > Do we need to encode different placements of liquescents? > Or something else? > > Ichiro > > > _______________________________________________ > mei-neumes-ig mailing list > mei-neumes-ig at lists.uni-paderborn.de > https://lists.uni-paderborn.de/mailman/listinfo/mei-neumes-ig From katehelsen at gmail.com Thu Jun 21 17:56:12 2018 From: katehelsen at gmail.com (Kate Helsen) Date: Thu, 21 Jun 2018 11:56:12 -0400 Subject: [mei-neumes-ig] Liquescent In-Reply-To: <4B014E85-8315-4290-9A9D-19780752FC8E@gmail.com> References: <5B921D0C-8630-486B-82C0-0853DFEA77CB@mcgill.ca> <4B014E85-8315-4290-9A9D-19780752FC8E@gmail.com> Message-ID: Looking at the adiastematic neumes in Hartker, I would say that liquescence is a way of rendering an that would otherwise (by "default") look a different way. I think this means it is naturally described at the *attribute* level. In this type of notation I would start with liquescent *forms* such as: "curled" and "hoop" - to indicate that the curl has closed all the way into a sort of circle." The *placement* of these liquescents is usually at the 'end' of the note (so often "ne") but sometimes they at at the "se" - it depends on the shape of the rest of the neume. One might also want to think about *direction* of the "curl" - 95% of the time I'd say that it's clockwise, but there the torculus resupinus liquescent bucks the trend by going the other way... On Thu, 21 Jun 2018 at 11:23 Micah John Walter wrote: > Dear Ichiro and all, > > Well, one thing I can think of is whether, for neumes on a staff, the > notehead is visible. (Liquescent neumes without a clear notehead are, I > believe, a predecessor to the plica.) If this were to be encoded, however, > it could be an attribute on the rather than a liquescent element. > > Micah > > > > On 21 June 2018, at 11:16, Ichiro Fujinaga, Prof. < > ichiro.fujinaga at mcgill.ca> wrote: > > > > Dear all, > > > > Currently (http://bit.ly/MEI_Neumes_0_2_3), a liquescent is encoded as > a boolean attribute of : @liques > > > > On the other hand, episema is an element with its own attributes: > > @form {vert | horiz} > > @place {n | ne | e | se | s | sw | w | nw} (the placement of the > episema with respect to the or with which it is associated) > > > > My question is whether liquescent should be an element? > > > > Do we need to encode different ?forms? of liquescents? > > Do we need to encode different placements of liquescents? > > Or something else? > > > > Ichiro > > > > > > _______________________________________________ > > 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew.hankinson at mail.mcgill.ca Thu Jun 21 19:54:21 2018 From: andrew.hankinson at mail.mcgill.ca (Andrew Hankinson) Date: Thu, 21 Jun 2018 17:54:21 +0000 Subject: [mei-neumes-ig] Liquescent In-Reply-To: References: <5B921D0C-8630-486B-82C0-0853DFEA77CB@mcgill.ca> <4B014E85-8315-4290-9A9D-19780752FC8E@gmail.com> Message-ID: <9DA7A10B-FDAF-4578-8527-9C651A802592@mail.mcgill.ca> How does this function in other repertoires where hooks and loops are not a part of the shape? On 21 Jun 2018, at 16:56, Kate Helsen > wrote: Looking at the adiastematic neumes in Hartker, I would say that liquescence is a way of rendering an that would otherwise (by "default") look a different way. I think this means it is naturally described at the attribute level. In this type of notation I would start with liquescent forms such as: "curled" and "hoop" - to indicate that the curl has closed all the way into a sort of circle." The placement of these liquescents is usually at the 'end' of the note (so often "ne") but sometimes they at at the "se" - it depends on the shape of the rest of the neume. One might also want to think about direction of the "curl" - 95% of the time I'd say that it's clockwise, but there the torculus resupinus liquescent bucks the trend by going the other way... On Thu, 21 Jun 2018 at 11:23 Micah John Walter > wrote: Dear Ichiro and all, Well, one thing I can think of is whether, for neumes on a staff, the notehead is visible. (Liquescent neumes without a clear notehead are, I believe, a predecessor to the plica.) If this were to be encoded, however, it could be an attribute on the rather than a liquescent element. Micah > On 21 June 2018, at 11:16, Ichiro Fujinaga, Prof. > wrote: > > Dear all, > > Currently (http://bit.ly/MEI_Neumes_0_2_3), a liquescent is encoded as a boolean attribute of : @liques > > On the other hand, episema is an element with its own attributes: > @form {vert | horiz} > @place {n | ne | e | se | s | sw | w | nw} (the placement of the episema with respect to the or with which it is associated) > > My question is whether liquescent should be an element? > > Do we need to encode different ?forms? of liquescents? > Do we need to encode different placements of liquescents? > Or something else? > > Ichiro > > > _______________________________________________ > 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 _______________________________________________ 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 thomas.weber at notengrafik.com Fri Jun 22 09:52:58 2018 From: thomas.weber at notengrafik.com (Thomas Weber) Date: Fri, 22 Jun 2018 09:52:58 +0200 Subject: [mei-neumes-ig] Liquescent In-Reply-To: References: <5B921D0C-8630-486B-82C0-0853DFEA77CB@mcgill.ca> Message-ID: An HTML attachment was scrubbed... URL: From ichiro.fujinaga at mcgill.ca Fri Jun 22 15:44:37 2018 From: ichiro.fujinaga at mcgill.ca (Ichiro Fujinaga, Prof.) Date: Fri, 22 Jun 2018 13:44:37 +0000 Subject: [mei-neumes-ig] Liquescent In-Reply-To: References: <5B921D0C-8630-486B-82C0-0853DFEA77CB@mcgill.ca>

Message-ID: > On Jun 22, 2018, at 3:52 AM, Thomas Weber wrote: > > Am 21.06.2018 um 17:56 schrieb Kate Helsen: >> Looking at the adiastematic neumes in Hartker, I would say that liquescence is a way of rendering an that would otherwise (by "default") look a different way. I think this means it is naturally described at the attribute level. > > > Though from a musicological perspective, you would call liquescence an attribute of the a neume component concept, this doesn't technically mean we have to make it an XML attribute. As you stated, we can describe liquescence in more detail if we want: > Yes, I should have been more clear when I asked: >> Do we need to encode different ?forms? of liquescents? >> Do we need to encode different placements of liquescents? >> Or something else? As Thomas said, the question is: do we want/need to specifically "describe liquescence in more detail?? >> >> In this type of notation I would start with liquescent forms such as: "curled" and "hoop" - to indicate that the curl has closed all the way into a sort of circle." >> The placement of these liquescents is usually at the 'end' of the note (so often "ne") but sometimes they at at the "se" - it depends on the shape of the rest of the neume. >> One might also want to think about direction of the "curl" - 95% of the time I'd say that it's clockwise, but there the torculus resupinus liquescent bucks the trend by going the other way... > > This technically means we should make liquescence an element so that we can go one level deeper in describing it with attributes. > Yes, let?s try making the liquescent an element. Given that, what should be its attributes? @curl / curve {anticlockwise | clockwise}? @place {n | ne | e | se | s | sw | w | nw}? Note that we should be encoding things that either we know or suspect to mean different things. For example, if we all agree that a curl anticlockwise and a curl clockwise mean the same thing, we don?t need to encode that. On the other hand, if you suspect that a curl that is closed is sung differently from a curl that is not closed, then we should encode that fact (e.g., @closed= ?true? or @loop= ?closed"). It would be great, as Thomas suggests below, if you can post your favourite examples of liquescent neumes here so we can all discuss them. > I want to suggest to start small with the new neumes module. I think there are a few fundamental things that are basically agreed upon. Step by step completing the module over a few releases would IMO be much better than publishing a schema that no one has tested. If we only have an abstract schema, I doubt that we really grasp the technical and musicological implications as this field is so specialized. I think we really need to discuss practical examples (with facsimiles and MEI encoding) to avoid too many breaking changes later on. I have to apologize in advance that I might not be very actively participating in discussion, though. > Thank you. Yes, I agree completely that we have to test this schema with various notation styles. With the SIMSSA project we have been testing the schema with St. Gall, Old Hispanic, Salzinnes (16th C. square), and Solesmes. I would love to test the schema with more notation styles, but with the looming deadline of 1 July for the release of MEI Version 4.0; I?m trying to make this schema as good as it can for now. It would definitely go though many revisions and releases as we improve upon it. I should also mention that the SIMSSA project is developing a new interactive neume editor based on Verovio, in addition to the OMR system for neumes based on machine learning. So these tools can be used for large-scale testing of the schema. Ichiro > Thomas > > -- > > 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 ichiro.fujinaga at mcgill.ca Thu Jun 28 16:30:38 2018 From: ichiro.fujinaga at mcgill.ca (Ichiro Fujinaga, Prof.) Date: Thu, 28 Jun 2018 14:30:38 +0000 Subject: [mei-neumes-ig] Strophicus / Stropha Message-ID: Dear all, I?m considering introducing a new element (could be ). [cid:83EFE933-15D9-4FB4-BBF0-7EDAD584F762] What attributes should it have other than @pname, @oct, and @intm? Please provide an example that would explain the attribute. Can we take a quick vote on your preference for the name: or ? Just say: ?I prefer ? or "I prefer ?. Thank you, Ichiro -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: PastedGraphic-3.png Type: image/png Size: 3307 bytes Desc: PastedGraphic-3.png URL: From micahjwalter at gmail.com Thu Jun 28 16:32:36 2018 From: micahjwalter at gmail.com (Micah Walter) Date: Thu, 28 Jun 2018 10:32:36 -0400 Subject: [mei-neumes-ig] Strophicus / Stropha In-Reply-To: References: Message-ID: I prefer . On Thu, Jun 28, 2018 at 10:30 AM, Ichiro Fujinaga, Prof. < ichiro.fujinaga at mcgill.ca> wrote: > Dear all, > > I?m considering introducing a new element (could be > ). > > What attributes should it have other than @pname, @oct, and @intm? > Please provide an example that would explain the attribute. > > Can we take a quick vote on your preference for the name: or > ? > > Just say: ?I prefer ? or "I prefer ?. > > Thank you, > > Ichiro > > > _______________________________________________ > 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: PastedGraphic-3.png Type: image/png Size: 3307 bytes Desc: not available URL: From ichiro.fujinaga at mcgill.ca Fri Jun 29 17:47:27 2018 From: ichiro.fujinaga at mcgill.ca (Ichiro Fujinaga, Prof.) Date: Fri, 29 Jun 2018 15:47:27 +0000 Subject: [mei-neumes-ig] Final draft before MEI Version 4.0 In-Reply-To: References: <7747_1527673069_5B0E70ED_7747_50_1_BE8143A8-D935-4F06-A48D-8BC762B88CD5@edirom.de> Message-ID: <1BF644AF-3B33-4653-8AB9-3066C2149D50@mcgill.ca> Dear all, Here?s the latest and possibly the last draft before the schema goes into MEI Version 4.0: http://bit.ly/MEI_Neumes_0_2_4 The deadline is 1 July. As I said before: > The MEI is an evolving encoding system and we can always make changes. > Also we won?t know the consequences of these changes until we thoroughly use it and test it. > But let?s try to make this as best as we can before the deadline. Please post your questions, concerns, and edits on this mailing list. Thank you, Ichiro From inga.behrendt at uni-tuebingen.de Fri Jun 29 21:38:22 2018 From: inga.behrendt at uni-tuebingen.de (Inga Behrendt) Date: Fri, 29 Jun 2018 21:38:22 +0200 Subject: [mei-neumes-ig] Strophicus / Stropha In-Reply-To: Message-ID: <20180629213822.Horde.rOCM-FFxVUUkWswrGon8b1P@webmail.uni-tuebingen.de> "I prefer ? Inga Zitat von "Ichiro Fujinaga, Prof." : > Dear all, > > I?m considering introducing a new element (could be ). > [cid:83EFE933-15D9-4FB4-BBF0-7EDAD584F762] > > What attributes should it have other than @pname, @oct, and @intm? > Please provide an example that would explain the attribute. > > Can we take a quick vote on your preference for the name: > or ? > > Just say: ?I prefer ? or "I prefer ?. > > Thank you, > > Ichiro From katehelsen at gmail.com Fri Jun 29 21:49:08 2018 From: katehelsen at gmail.com (Kate Helsen) Date: Fri, 29 Jun 2018 15:49:08 -0400 Subject: [mei-neumes-ig] Strophicus / Stropha In-Reply-To: <20180629213822.Horde.rOCM-FFxVUUkWswrGon8b1P@webmail.uni-tuebingen.de> References: <20180629213822.Horde.rOCM-FFxVUUkWswrGon8b1P@webmail.uni-tuebingen.de> Message-ID: Forgive my ignorance but I'm wondering if there is a semantic difference between strophica and stropha? K On Fri, Jun 29, 2018, 3:38 PM Inga Behrendt wrote: > "I prefer ? > Inga > > Zitat von "Ichiro Fujinaga, Prof." : > > > Dear all, > > > > I?m considering introducing a new element (could be > ). > > [cid:83EFE933-15D9-4FB4-BBF0-7EDAD584F762] > > > > What attributes should it have other than @pname, @oct, and @intm? > > Please provide an example that would explain the attribute. > > > > Can we take a quick vote on your preference for the name: > > or ? > > > > Just say: ?I prefer ? or "I prefer ?. > > > > Thank you, > > > > Ichiro > > > > > _______________________________________________ > 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 ichiro.fujinaga at mcgill.ca Fri Jun 29 23:53:21 2018 From: ichiro.fujinaga at mcgill.ca (Ichiro Fujinaga, Prof.) Date: Fri, 29 Jun 2018 21:53:21 +0000 Subject: [mei-neumes-ig] Strophicus / Stropha In-Reply-To: <20180629213822.Horde.rOCM-FFxVUUkWswrGon8b1P@webmail.uni-tuebingen.de> References: <20180629213822.Horde.rOCM-FFxVUUkWswrGon8b1P@webmail.uni-tuebingen.de> Message-ID: <246F3EFF-C8D9-4AFF-88EB-E336B924249F@mcgill.ca> I need more votes to break the tie. Ichiro > On Jun 29, 2018, at 3:38 PM, Inga Behrendt wrote: > > "I prefer ? > Inga > > Zitat von "Ichiro Fujinaga, Prof." : > >> Dear all, >> >> I?m considering introducing a new element (could be ). >> [cid:83EFE933-15D9-4FB4-BBF0-7EDAD584F762] >> >> What attributes should it have other than @pname, @oct, and @intm? >> Please provide an example that would explain the attribute. >> >> Can we take a quick vote on your preference for the name: or ? >> >> Just say: ?I prefer ? or "I prefer ?. >> >> Thank you, >> >> Ichiro > > > > > _______________________________________________ > mei-neumes-ig mailing list > mei-neumes-ig at lists.uni-paderborn.de > https://lists.uni-paderborn.de/mailman/listinfo/mei-neumes-ig From katehelsen at gmail.com Sat Jun 30 00:40:54 2018 From: katehelsen at gmail.com (Kate Helsen) Date: Fri, 29 Jun 2018 18:40:54 -0400 Subject: [mei-neumes-ig] Strophicus / Stropha In-Reply-To: <246F3EFF-C8D9-4AFF-88EB-E336B924249F@mcgill.ca> References: <20180629213822.Horde.rOCM-FFxVUUkWswrGon8b1P@webmail.uni-tuebingen.de> <246F3EFF-C8D9-4AFF-88EB-E336B924249F@mcgill.ca> Message-ID: If we go with Strophicus, then we should rename the Pes, Podatus. That's the only thing, I think that we should keep in mind. On Fri, Jun 29, 2018, 5:53 PM Ichiro Fujinaga, Prof. < ichiro.fujinaga at mcgill.ca> wrote: > I need more votes to break the tie. > > Ichiro > > > On Jun 29, 2018, at 3:38 PM, Inga Behrendt < > inga.behrendt at uni-tuebingen.de> wrote: > > > > "I prefer ? > > Inga > > > > Zitat von "Ichiro Fujinaga, Prof." : > > > >> Dear all, > >> > >> I?m considering introducing a new element (could be > ). > >> [cid:83EFE933-15D9-4FB4-BBF0-7EDAD584F762] > >> > >> What attributes should it have other than @pname, @oct, and @intm? > >> Please provide an example that would explain the attribute. > >> > >> Can we take a quick vote on your preference for the name: > or ? > >> > >> Just say: ?I prefer ? or "I prefer ?. > >> > >> Thank you, > >> > >> Ichiro > > > > > > > > > > _______________________________________________ > > 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From stefan.morent at uni-tuebingen.de Sat Jun 30 00:54:24 2018 From: stefan.morent at uni-tuebingen.de (Prof. Dr. Morent) Date: Sat, 30 Jun 2018 00:54:24 +0200 Subject: [mei-neumes-ig] Strophicus / Stropha In-Reply-To: References: <20180629213822.Horde.rOCM-FFxVUUkWswrGon8b1P@webmail.uni-tuebingen.de> <246F3EFF-C8D9-4AFF-88EB-E336B924249F@mcgill.ca> Message-ID: <20180630005424.Horde.lp7LclKe_owG4EEaMy--kBx@webmail.uni-tuebingen.de> Since historical nomenclature for neumes vary over time and space it wil be hard to find the one and only ... Is it possible to allow various names? Or point to various neume tables? Stefan ----- Nachricht von Kate Helsen --------- ? ? ?Datum: Fri, 29 Jun 2018 18:40:54 -0400 ? ? ? ?Von: Kate Helsen Antwort an: Neumes Interest Group of the Music Encoding Initiative ? ?Betreff: Re: [mei-neumes-ig] Strophicus / Stropha ? ? ? ? An: "Ichiro Fujinaga, Prof." , Neumes Interest Group of the Music Encoding Initiative > If we go with Strophicus, then we should rename the Pes, Podatus. > That's the only thing, I think that we should keep in mind. > > On Fri, Jun 29, 2018, 5:53 PM Ichiro Fujinaga, Prof. > wrote: > >> I need more votes to break the tie. >> >> Ichiro >> >>> On Jun 29, 2018, at 3:38 PM, Inga Behrendt >>> wrote: >>> >>> "I prefer? ? >>> Inga >>> >>> Zitat von "Ichiro Fujinaga, Prof." : >>> >>>> Dear all, >>>> >>>> I?m considering introducing a new element (could be >>>> ). >>>> [cid:83EFE933-15D9-4FB4-BBF0-7EDAD584F762] >>>> >>>> What attributes should it have other than @pname, @oct, and @intm? >>>> Please provide an example that would explain the attribute. >>>> >>>> Can we take a quick vote on your preference for the name:? >>>> or ? >>>> >>>> Just say: ?I prefer? ? or "I prefer? ?. >>>> >>>> Thank you, >>>> >>>> Ichiro >>> >>> >>> >>> >>> _______________________________________________ >>> 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 ----- Ende der Nachricht von Kate Helsen ----- -------------- next part -------------- An HTML attachment was scrubbed... URL: From ichiro.fujinaga at mcgill.ca Sat Jun 30 02:15:57 2018 From: ichiro.fujinaga at mcgill.ca (Ichiro Fujinaga, Prof.) Date: Sat, 30 Jun 2018 00:15:57 +0000 Subject: [mei-neumes-ig] Strophicus / Stropha In-Reply-To: <20180630005424.Horde.lp7LclKe_owG4EEaMy--kBx@webmail.uni-tuebingen.de> References: <20180629213822.Horde.rOCM-FFxVUUkWswrGon8b1P@webmail.uni-tuebingen.de> <246F3EFF-C8D9-4AFF-88EB-E336B924249F@mcgill.ca> , <20180630005424.Horde.lp7LclKe_owG4EEaMy--kBx@webmail.uni-tuebingen.de> Message-ID: Yes, that?s what we had plan to do; but I haven?t figured out how to do that properly and I?ve run out of time for this round. In general, we have avoided naming neumes, but I needed to name few things. These are episema, quilisma, liquescent, oriscus, and strophicus / stropha. We can revisit the naming of these things later. Ichiro On Jun 29, 2018, at 18:54, Prof. Dr. Morent > wrote: Since historical nomenclature for neumes vary over time and space it wil be hard to find the one and only ... Is it possible to allow various names? Or point to various neume tables? Stefan ----- Nachricht von Kate Helsen > --------- Datum: Fri, 29 Jun 2018 18:40:54 -0400 Von: Kate Helsen > Antwort an: Neumes Interest Group of the Music Encoding Initiative > Betreff: Re: [mei-neumes-ig] Strophicus / Stropha An: "Ichiro Fujinaga, Prof." >, Neumes Interest Group of the Music Encoding Initiative > If we go with Strophicus, then we should rename the Pes, Podatus. That's the only thing, I think that we should keep in mind. On Fri, Jun 29, 2018, 5:53 PM Ichiro Fujinaga, Prof. > wrote: I need more votes to break the tie. Ichiro > On Jun 29, 2018, at 3:38 PM, Inga Behrendt > wrote: > > "I prefer ? > Inga > > Zitat von "Ichiro Fujinaga, Prof." >: > >> Dear all, >> >> I?m considering introducing a new element (could be ). >> [cid:83EFE933-15D9-4FB4-BBF0-7EDAD584F762] >> >> What attributes should it have other than @pname, @oct, and @intm? >> Please provide an example that would explain the attribute. >> >> Can we take a quick vote on your preference for the name: or ? >> >> Just say: ?I prefer ? or "I prefer ?. >> >> Thank you, >> >> Ichiro > > > > > _______________________________________________ > 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 ----- Ende der Nachricht von Kate Helsen > ----- _______________________________________________ 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 stefan.morent at uni-tuebingen.de Sat Jun 30 10:34:57 2018 From: stefan.morent at uni-tuebingen.de (Prof. Dr. Morent) Date: Sat, 30 Jun 2018 10:34:57 +0200 Subject: [mei-neumes-ig] Strophicus / Stropha In-Reply-To: References: <20180629213822.Horde.rOCM-FFxVUUkWswrGon8b1P@webmail.uni-tuebingen.de> <246F3EFF-C8D9-4AFF-88EB-E336B924249F@mcgill.ca> <20180630005424.Horde.lp7LclKe_owG4EEaMy--kBx@webmail.uni-tuebingen.de> Message-ID: <20180630103457.Horde.xSmJ76UuGFac9XGlxv1Yxw8@webmail.uni-tuebingen.de> I see. If we agree that these names are more or less general "logical concepts" or technical placeholders not totally missleading we could see later on how to tie them to historical names. Stefan ----- Nachricht von "Ichiro Fujinaga, Prof." --------- ? ? ?Datum: Sat, 30 Jun 2018 00:15:57 +0000 ? ? ? ?Von: "Ichiro Fujinaga, Prof." Antwort an: Neumes Interest Group of the Music Encoding Initiative ? ?Betreff: Re: [mei-neumes-ig] Strophicus / Stropha ? ? ? ? An: Neumes Interest Group of the Music Encoding Initiative > Yes, that?s what we had plan to do; but I haven?t figured out how to > do that properly and I?ve run out of time for this round. > ? > In general, we have avoided naming neumes, but I needed to name > few things. These are episema, quilisma, liquescent, oriscus, and > strophicus / stropha. > ? > We can revisit the naming of these things later. > ? > Ichiro > ? > > On Jun 29, 2018, at 18:54, Prof. Dr. Morent > wrote: > ? > >> Since historical nomenclature for neumes vary over time and space >> it wil be hard to find the one and only ... >> Is it possible to allow various names? Or point to various neume tables? >> >> Stefan >> >> ----- Nachricht von Kate Helsen --------- >> ? ? ?Datum: Fri, 29 Jun 2018 18:40:54 -0400 >> ? ? ? ?Von: Kate Helsen >> Antwort an: Neumes Interest Group of the Music Encoding Initiative >> >> ? ?Betreff: Re: [mei-neumes-ig] Strophicus / Stropha >> ? ? ? ? An: "Ichiro Fujinaga, Prof." , >> Neumes Interest Group of the Music Encoding Initiative >> >> >>> If we go with Strophicus, then we should rename the Pes, Podatus. >>> That's the only thing, I think that we should keep in mind. >>> >>> On Fri, Jun 29, 2018, 5:53 PM Ichiro Fujinaga, Prof. >>> wrote: >>> >>>> I need more votes to break the tie. >>>> >>>> Ichiro >>>> >>>>> On Jun 29, 2018, at 3:38 PM, Inga Behrendt >>>>> wrote: >>>>> >>>>> "I prefer? ? >>>>> Inga >>>>> >>>>> Zitat von "Ichiro Fujinaga, Prof." : >>>>> >>>>>> Dear all, >>>>>> >>>>>> I?m considering introducing a new element (could >>>>>> be ). >>>>>> [cid:83EFE933-15D9-4FB4-BBF0-7EDAD584F762] >>>>>> >>>>>> What attributes should it have other than @pname, @oct, and @intm? >>>>>> Please provide an example that would explain the attribute. >>>>>> >>>>>> Can we take a quick vote on your preference for the name:? >>>>>> or ? >>>>>> >>>>>> Just say: ?I prefer? ? or "I prefer? ?. >>>>>> >>>>>> Thank you, >>>>>> >>>>>> Ichiro >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> mei-neumes-ig mailing list >>>>> mei-neumes-ig at lists.uni-paderborn.de[1] >>>>> https://lists.uni-paderborn.de/mailman/listinfo/mei-neumes-ig[2] >>>> >>>> _______________________________________________ >>>> mei-neumes-ig mailing list >>>> mei-neumes-ig at lists.uni-paderborn.de >>>> https://lists.uni-paderborn.de/mailman/listinfo/mei-neumes-ig >> >> ----- Ende der Nachricht von Kate Helsen ----- >> ? > >> _______________________________________________ >> mei-neumes-ig mailing list >> mei-neumes-ig at lists.uni-paderborn.de >> https://lists.uni-paderborn.de/mailman/listinfo/mei-neumes-ig ----- Ende der Nachricht von "Ichiro Fujinaga, Prof." ----- Links: ------ [1] mailto:mei-neumes-ig at lists.uni-paderborn.de [2] https://lists.uni-paderborn.de/mailman/listinfo/mei-neumes-ig -------------- next part -------------- An HTML attachment was scrubbed... URL: