<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">great, thanks for fixing!<br>
<br>
Benjamin<br>
<pre class="moz-signature" cols="72">***********************************************************
Musikwissenschaftliches Seminar Detmold/Paderborn
BMBF-Projekt "Freischütz Digital"
Benjamin Wolff Bohl
Gartenstraße 20
D–32756 Detmold
Tel. +49 (0) 5231 / 975-669
Fax: +49 (0) 5231 / 975-668
E-Mail: <a class="moz-txt-link-abbreviated" href="mailto:bohl@edirom.de">bohl@edirom.de</a>
<a class="moz-txt-link-freetext" href="http://www.freischuetz-digital.de">http://www.freischuetz-digital.de</a>
***********************************************************</pre>
Am 16.10.2014 18:26, schrieb Johannes Kepper:<br>
</div>
<blockquote
cite="mid:E33CCF1E-D852-4495-9A80-AF6053B5A8AF@edirom.de"
type="cite">
<pre wrap="">Dear *,
those of you making use of the Schematron rules in MEI may have noticed that our 2013 release (2.1.0) had some issues with the validity of the RNG schemata. This problem became visible only with newer versions of Oxygen that choked on doubled IDs on two sets of schematron rules for clefs and staffDefs. For those of you that never used a version newer than Oxygen 15.1 or Schematron at all, you shouldn't had any problems. For everyone else: we're all good again. We just updated the repository with a minor revision of MEI, which just fixes this schematron bug. *No new feature from the development tree has been adopted, nor has any functionality changed*. All valid 2013 v 2.1.0 files should be valid v 2.1.1 files and vice versa – with one important exception: The @meiversion.num attribute available on <mei>, <meiCorpus>, <meiHead> and <music> now allows only the value "2.1.1", instead of "2.1.0".
The music-encoding.org website has been updated to reflect this new release, and the google code repo holds a new tag for the release. You may download the full release from <a class="moz-txt-link-freetext" href="http://music-encoding.org/downloads/MEI2013_v2.1.1.zip">http://music-encoding.org/downloads/MEI2013_v2.1.1.zip</a>, and just the guidelines from <a class="moz-txt-link-freetext" href="http://music-encoding.googlecode.com/svn/tags/MEI2013_v2.1.1/guidelines/MEI_Guidelines_2013_v2.1.1.pdf">http://music-encoding.googlecode.com/svn/tags/MEI2013_v2.1.1/guidelines/MEI_Guidelines_2013_v2.1.1.pdf</a> (however, the PDF has no change beyond the version number, since the wrong IDs don't show up there). What hasn't been updated yet is the customization web service under custom.music-encoding.org, which will be updated without further notice on this list in the near future.
I hope none of you has any significant problems to update her or his data, tools or workflows. If you encounter any problems with the release, please let me know.
Best regards,
Johannes
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
mei-l mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mei-l@lists.uni-paderborn.de">mei-l@lists.uni-paderborn.de</a>
<a class="moz-txt-link-freetext" href="https://lists.uni-paderborn.de/mailman/listinfo/mei-l">https://lists.uni-paderborn.de/mailman/listinfo/mei-l</a>
</pre>
</blockquote>
<br>
</body>
</html>