Agreed, Peter. To rephrase: I would be happy with whatever makes it possible for various mid-level users (whether of XML/XSLT or of the particular work or literary genre) to understand and manipulate the material within a few minutes. The @n and @subtype attributes seem to be doing the majority of that user-friendliness work here; perhaps the @type attribute goes too far, as you say. But whether a few more or a few less, I think the basic feedback to Patrick's question remains the same: Such attributes need not be required by the guidelines, but they can still serve to conveniently store annotations concerning traditional structural information.

On Fri, Nov 2, 2018 at 7:17 AM Peter Scharf <scharf@sanskritlibrary.org> wrote:
It is not really necessary to include level1, level2 in every div.  One could describe this structure, namely, that level1 is volume, level 2 is Ahnika, etc., in the header in machine readable form.
Yours,
Peter

******************************
Peter M. Scharf, President
The Sanskrit Library
******************************

On 2 Nov 2018, at 2:57 AM, Dominik Wujastyk <wujastyk@gmail.com> wrote:


On Thu, 18 Oct 2018 at 15:06, Tyler Neill <tyler.g.neill@gmail.com> wrote:

<div n="1" type="level1" subtype="volume">
<div n="1" type="level2" subtype="āhnika">
<div n="2" type="level2" subtype="āhnika">
<div n="3" type="level2" subtype="āhnika">
etc.

I agree with Tyler's view that this is clear and conveys all the information one wants without having to extend TEI in local ways.

Best,
Dominik
_______________________________________________
Indic-texts mailing list
Indic-texts@lists.tei-c.org
http://lists.lists.tei-c.org/mailman/listinfo/indic-texts