> To my surprise, the guidelines did not give the following option:
> <xptr doc="B" target="elementid in B"/>.
Well, not with that precise syntax, but this capability and more is
<xptr doc="B" from="id ( duck )"/>
does exactly that. The disadvantage with this (very powerful, well
thought out, reasonably well documented, easy to parse) system is
that there are very very few actual implementations.
I sympathize with the idea that target= is a better name when only
one pointer is used, but honestly have never found it to be a big
deal. (Using just from= is exactly what the Guidelines say to do; see
the last paragraph of 14.2.2 (just before 18.104.22.168, p. 354) of
> Any objections to my adaption of the DTD?
I'm not sure I understand what you mean here. If you mean "would it
be a good idea to customize TEI so that my encoders can use target=
instead of from=", I'd say yes, it is, but you should also consider
other solutions. E.g., what is called "Sebastian's hack" of adding a
url= attribute to <xptr>, so that it would look something like
You also might find that you really want to link the commentary in B
with the corresponding locations in A, rather than just point from A
to B. I.e., in C:
<link evaluate="all" type="commentary" targOrder="Y" targets="bduck aduck"/>
<!-- ... -->
<xptr id="aduck" doc="A" from="id(duck)"/>
<xptr id="bduck" doc="B" from="id(duck)"/>