<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
Dear members of the MEI-Neumes Interest Group,
<div class=""><br class="">
</div>
<div class="">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. :-)</div>
<div class=""><br class="">
</div>
<div class="">So the deadline is now July 1.</div>
<div class=""><br class="">
</div>
<div class="">I’ve uploaded the latest version of the Draft at<span id="docs-internal-guid-db00b4ab-d675-f728-53bb-9079f7009a13" class=""><span style="font-size: 10.5pt; font-family: Arial; font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;" class="">
</span><a href="http://bit.ly/MEI_Neumes_0_2_3" style="text-decoration:none;" class=""><span style="font-size: 10.5pt; font-family: Arial; color: rgb(17, 85, 204); font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; text-decoration: underline; -webkit-text-decoration-skip: none; vertical-align: baseline; white-space: pre-wrap;" class="">http://bit.ly/MEI_Neumes_0_2_</span></a><span style="font-size: 10.5pt; font-family: Arial; color: rgb(74, 134, 232); font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;" class="">3</span></span><br class="">
<div class="">It’s still undergoing changes, such as, @class / @type and <division>.</div>
<div class=""><br class="">
</div>
<div class="">The MEI is an evolving encoding system and we can always make changes.</div>
<div class="">Also we won’t know the consequences of these changes until we thoroughly use it and test it. </div>
<div class="">But let’s try to make this as best as we can before the deadline.</div>
<div class=""><br class="">
</div>
<div class="">
<div class="">Please post your questions, concerns, and edits on this mailing list.</div>
</div>
<div class=""><br class="">
</div>
<div class="">Thank you,</div>
<div class=""><br class="">
</div>
<div class="">Ichiro</div>
<div class=""><br class="">
</div>
<div class="">
<div><br class="">
<blockquote type="cite" class="">
<div class="">Begin forwarded message:</div>
<br class="Apple-interchange-newline">
<div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class="">
<span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">From:
</b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">Johannes Kepper <<a href="mailto:kepper@edirom.de" class="">kepper@edirom.de</a>><br class="">
</span></div>
<div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class="">
<span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">Subject:
</b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class=""><b class="">[MEI-L] Report from the Community Meeting at MEC2018</b><br class="">
</span></div>
<div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class="">
<span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">Date:
</b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">May 30, 2018 at 5:32:21 AM GMT-4<br class="">
</span></div>
<div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class="">
<span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">To:
</b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">Music Encoding Initiative <<a href="mailto:mei-l@lists.uni-paderborn.de" class="">mei-l@lists.uni-paderborn.de</a>><br class="">
</span></div>
<div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class="">
<span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">Reply-To:
</b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">Music Encoding Initiative <<a href="mailto:mei-l@lists.uni-paderborn.de" class="">mei-l@lists.uni-paderborn.de</a>><br class="">
</span></div>
<br class="">
<div class="">
<div class="">Dear Members of the MEI,<br class="">
<br class="">
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.<br class="">
<br class="">
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.<br class="">
<br class="">
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.<br class="">
<br class="">
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.<br class="">
<br class="">
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.<br class="">
<br class="">
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
<a href="https://github.com/music-encoding/mec-proceedings" class="">https://github.com/music-encoding/mec-proceedings</a>. 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.<br class="">
<br class="">
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
<a href="http://music-encoding.org/resources/tools.html" class="">http://music-encoding.org/resources/tools.html</a>, while all projects using MEI should be listed at
<a href="http://music-encoding.org/community/projects-users.html" class="">http://music-encoding.org/community/projects-users.html</a>. 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.<br class="">
<br class="">
There will be no separate minutes from the Board meeting at MEC2018, as we've mostly prepared the topics discussed at the Community Meeting.<br class="">
<br class="">
If there are questions, additions, suggestions etc., please comment.<br class="">
<br class="">
With best regards,<br class="">
jo<br class="">
<br class="">
_______________________________________________<br class="">
mei-l mailing list<br class="">
<a href="mailto:mei-l@lists.uni-paderborn.de" class="">mei-l@lists.uni-paderborn.de</a><br class="">
https://lists.uni-paderborn.de/mailman/listinfo/mei-l<br class="">
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
</body>
</html>