>>>>> "Jean" == Jean Veronis <[log in to unmask]> writes:
Jean> At 9:50 4/07/95, Eric Peterson wrote:
Eric> I am attempting to encode some verb conjugations using the
Eric> TEI DTD for SGML. In my searches through chapter 12 of
Eric> the TEI guidelines, I found no way to specify a stem for a
Eric> verb. I wish to be able to specify the verb stem and
Eric> reference it in <ovar> fashion. [...]
Jean> A suggestion, which does not involve the addition of any new
Jean> tag or attribute, although implies a customization of the
Jean> current TEI DTD to enable "m.formPointers" to appear anywhere
Jean> in the entry and not only in examples (see below).
Thanks for your kind and knowledgeable reply. Your approach seems
much more in the spirit of the TEI.
One minor point: PSGML already allows me to place <oref> anywhere
within the entry and NSGMLS parsed your suggested form without
complaint. I understand little about SGML DTD's so I'm probably just
not understanding the point that you are trying to make about the
scoping of "m.formPointers".
Jean> Note that I used <oRef> and not <oVar>. I feel that I have to explain a
Jean> little since I am the one who proposed these two tags. The intent (but
Jean> not sure that we explained it well in the Dictionary chapter) was that
Jean> <oRef> refers to the content of an <orth> element (hence the name
Jean> whereas <oVar> stands for a variant of the headword not given in the
Jean> dictionary. I would use <oVar> in the following case:
Jean> <form type=infl>
Jean> <orth><oVar type=stem>cri</oVar>e</orth>
I assume that you are saying this is an equally valid encoding to your
first example which perhaps realizes different goals on the part of
the person encoding the SGML? You say you "would use <oVar> in the
following case:" yet it seems to me that this <oVar> case is an
encoding of the exact same example text as your first example
encoding. So I guess I'm not yet seeing why this is being treated as a
separate case which requires an <oVar>.
Thanks again for bring your experience to bear on this problem. Your
suggestions will us a non-force-fit way of accomplishing our goal
without creating needless tags and features.