Croenen, Godfried wrote:
> I just found out that the desc attribute on <gap> has been lost in P5,
> and I am puzzled as to how the <desc> element could be used to replace
> it. From reading the guidelines I understand that the <desc> element
> should be used as part of the technical documentation on the encoding
> practice used in a document, which would allow automatic processing of
> (some of the) markup. That seems to exclude the use to document a
> particular instance where the encoder wants to give more information
> about a particular occurrence of, say, <gap>. None of the examples given
> in the guidelines seem to warrant this kind of use.
Improving the examples to they reflect a broader use-cases is certainly
something that (continually) needs doing.
> The P4 encoding I am trying to convert to P5 goes like this:
> <gap desc="initial not executed" reason="unfinished"/>
> Should this now be <gap reason="unfinished"><desc>initial not
Yes, definitely! The reason for this is the war on free text-bearing
attributes. You'll see that most attributes now in P5 have a datatype and
don't take just free random CDATA. Part of the reason behind this was the,
very sensible, suggestion that you might need to use a non-unicode
character in your description. The TEI's mechanism for describing
non-unicode characters is the <g> element (which then references
descriptions in the teiHeader). Since you can't have markup inside an
attribute value, it makes sense to have such attributes converted to child
elements. A similar rational can be see in the introduction of choice
instead of the previous janus tags like <abbr expan="foo">.
> But then the guidelines state that "TEI convention requires that this be
> expressed as a finite clause, begining with an active verb."
> So should it be <gap reason="unfinished"><desc>indicates an initial that
> is not executed</desc></gap>?
I think that this solely means that the TEI convention with respect to the
TEI Guidelines (and their underlying files). Most of the <desc> elements
for elements start 'contains a such-and-forth' or 'attaches an anchor here'
or similar. The <desc> here is being used for a slightly different
intention than a <desc> in a <gap> and so I wouldn't feel bound by that
myself, but other people's opinions may differ.
Dr James Cummings, Oxford Text Archive, University of Oxford
James dot Cummings at oucs dot ox dot ac dot uk