Dear all,<div><br></div><div>The genetic encoding group within the Manuscript SIG of the TEI faced similar issues. They came up with a new TEI module that takes a documentary approach before a semantic one. It suggests to use the element ge:document as an alternative to tei:text, the element that contains the semantic tagging. They extend the model of tei:zone and introduce new elements like ge:page (a non-empty element) and ge:line (non-empty), which simply marks a line of text, regardless of its orientation. Attribute like @rotate and the integration of SVG allow for the encoding of complex manuscript material.</div>
<div>Here is their current proposal: <a href="http://www.tei-c.org/SIG/Manuscripts/genetic.html" target="_blank">http://www.tei-c.org/SIG/Manuscripts/genetic.html</a></div>
<div><br></div><div><a href="http://www.tei-c.org/SIG/Manuscripts/genetic.html" target="_blank"></a>I think MEI could be looking at using some of the concepts introduced here and possibly include some of this TEI elements (possibly with their namespace) into a document-oriented customization. Something like ge:line might not make sense for MEI, though it might be used to model a mei:system. </div>
<div><br></div><div>Having a look at the work done by this group might shed some light on some of the topics of this discussion.</div><div><br></div><div>Best wishes,</div><div>Raffaele<br><br><div class="gmail_quote">On Mon, Feb 7, 2011 at 8:52 PM, Johannes Kepper <span dir="ltr"><<a href="mailto:kepper@edirom.de" target="_blank">kepper@edirom.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Perry,<br>
<div><br>
><br>
> - <zone> has no type attribute, but it already has @n, which can be used for the same effect.<br>
><br>
<br>
</div>I think a @type is something different than @n. Using @n as replacement for a missing @type seems to be "attribute abuse". Either there's a reason why there is no @type (in which case using @n is obviously wrong), or we should introduce it (in which case using @n is unnecessary). Btw: Anyone else who thinks that @n should be xs:string instead of xs:NMTOKEN? Think of <mdiv n="Allegro moderato"/>…<br>
<div><br>
> - I'm not sure what the advantage of nesting <zone> elements is and I'm afraid it may create more problems than it alleviates as users attempt to replicate the visual layout of the page using hierarchically-structured zones (better to leave the zones as a list where the coordinates of any zones may overlap).<br>
><br>
<br>
</div>You're probably right, although it might be interesting to group zones somehow. Question is if a parent-zone must be a bounding box for all child-zones, or maybe if it even has to have coordinates? But I'm just thinking loud, I'm not yet convinced of anything. Any other arguments, wishes, opinions out there?<br>
<font color="#888888"><br>
Johannes<br>
</font><div><div></div><div>_______________________________________________<br>
mei-l mailing list<br>
<a href="mailto:mei-l@lists.uni-paderborn.de" target="_blank">mei-l@lists.uni-paderborn.de</a><br>
<a href="https://lists.uni-paderborn.de/mailman/listinfo/mei-l" target="_blank">https://lists.uni-paderborn.de/mailman/listinfo/mei-l</a><br>
</div></div></blockquote></div><br></div>