<div dir="ltr">Hi Thomas,<div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 30, 2015 at 5:37 AM, Thomas Weber <span dir="ltr"><<a href="mailto:tw@notabit.eu" target="_blank">tw@notabit.eu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Unless I'm missing something, would it be sensible to take the mentioned TEI elements as a model for MEI? To the TEI experts - what exactly is the difference between <ab> and <seg>? It seems to me <ab> is more like an HTML <div> (a "block" - is that what TEI calls a "chunk"?), while <seg> is more like an HTML <span> ("inline" in HTML terms).<br>
<br></blockquote><div><br></div><div>That's my understanding too. They belong to two different levels and class systems.</div><div><br></div><div>I am wary of adding more semantic text encoding to MEI. My rule of thumb is that if I'm finding it difficult to encode text with MEI, it's time to switch to TEI. ODD makes it possible to mix the two at a fairly granular level (though admittedly using both standard at once does add substantial overhead to your ODD workflow).</div><div><br></div><div>Raff</div><div><br></div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Specifically I was looking into how to sensibly encode rubrics in neumatic notation, wondering whether I should use something like<br>
<br>
<br>
<div type="rubric"><br>
<p>some rubric text</p><br>
</div><br>
<br>
<br>
but I don't think describing rubrics as paragraphs is semantically appropriate. <head> could be considered appropriate in some cases, but it's not allowed as the only element inside a <div>. I'll probably circumvent that problem by adding a NeumesXML-like <rubric> element[2] in our customization, but I feel the general problem that standard MEI might currently force one to classify text in potentially inappropriate ways remains.<br>
<br>
One option could also be to allow text immediately inside <div> without having to wrap it into a more semantically specific element, but enforcing more semantical markup is of course not a bad idea, provided semantically appropriate choices are made available, including a fallback to more generic markup.<br>
<br>
<br>
[1] <a href="http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SA.html#SASE" rel="noreferrer" target="_blank">http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SA.html#SASE</a><br>
[2] <a href="http://www.scribeserver.com/NEUMES/neumesxml_tree/tree_detail_west/rubric.htm" rel="noreferrer" target="_blank">http://www.scribeserver.com/NEUMES/neumesxml_tree/tree_detail_west/rubric.htm</a><br>
<br>
--<br>
Thomas Weber<br>
Notabit<br>
Burgkstraße 28<br>
01159 Dresden<br>
<br>
Tel.: <a href="tel:%2B49%20%280%29351%204794689" value="+493514794689">+49 (0)351 4794689</a><br>
<a href="http://notabit.eu/" rel="noreferrer" target="_blank">http://notabit.eu/</a><br>
<br>
<br>
_______________________________________________<br>
mei-l mailing list<br>
<a href="mailto:mei-l@lists.uni-paderborn.de">mei-l@lists.uni-paderborn.de</a><br>
<a href="https://lists.uni-paderborn.de/mailman/listinfo/mei-l" rel="noreferrer" target="_blank">https://lists.uni-paderborn.de/mailman/listinfo/mei-l</a><br>
</blockquote></div><br></div></div>