I guess I don't see what is wrong with using the "n" attribute. The
Guidelines say at 3.5:
"The n attribute allows identifying information (e.g. chapter numbers,
etc.) to be encoded even if it would not be a legal id value. Its value
may be any string of characters; typically it is a number or other
similar enumerator or label."
"n" is not necessarily a number, although many of us use it for that
purpose, e.g., <div type="chap" n="1">. It can just as easily be something
such as <text n="wombats">. If you really want to distinguish your texts by
some sort of label, I would suggest that "n" is a very appropriate
attribute for your purpose.
Nick Finke
--
*****************************************************
Nicholas D. Finke, Director Ph:513-556-0103
Center for Electronic Text in the Law Fx:513-556-6265
Head of Library Publications
University of Cincinnati College of Law Library
P.O. Box 210142 E-mail: [log in to unmask]
Clifton Ave & Calhoun Street
Cincinnati, OH 45221-0142
*****************************************************
----------
>From: "A.H. van der Weel" <[log in to unmask]>
>To: [log in to unmask]
>Subject: Identifying attribute for <group> and <text>
>Date: Tue, Sep 14, 1999, 8:14 AM
>
> 7bit
>
> Dear List
>
> In TEI and TEILite the possibility exists to create composite texts.
> This involves a tag called <group> which may contain either
> single/multiple <text> tags and/or single/multiple <group> tags (nested
> groups).
>
> e.g.
>
> <group>
> <text> </text>
> <text> </text>
> .
> .
> .
> </group>
>
> OR
>
> <group>
> <group>
> <text> </text>
> <text> </text>
> .
> .
> .
> </group>
> <group> </group>
> <text> </text>
> <text> </text>
> .
> .
> .
> </group>
>
> In the latter case it would seem to be desirable to be able to
> distinguish one <group>/<text> tag from the next. Unfortunately, neither
> TEIlite nor TEI allows for a 'type' attribute to be assigned to <group>
> or <text> and thus the ability to actually 'label' these tags doesn't
> exist. Various constructions could be devised to resolve this problem,
> but all of them are messy. The best option I have been able to find is
> to make use of the global attribute 'n', but this is going, to a large
> degree, against the intended purpose for 'n'. I have been unable to
> find anything better.
>
> Your help would be much appreciated.
>
> Saket Kulkarni
> Electronic Text Centre Leiden
> <[log in to unmask]>
>
|