[tei-council] empty elements revisited

Lou Burnard lou.burnard at retired.ox.ac.uk
Wed Sep 28 13:53:25 EDT 2011

The trouble with this is that once you allow model.glossLike elements in 
general you open the door to all sorts of crud.

I imagine that young Stormageddon would throw a fit at the idea of 
having to process  e.g.

<lb><desc>This is a line break I want to discuss for some bizarre 

and I think I would agree with him.

Wouldn't your use case be better met by a stand-off solution? i.e. why 
not do

<lb xml:id="n13"/><certainty cert="low" target="#n13" locus="location"/>

On 28/09/11 18:16, Gabriel Bodard wrote:
> A couple years ago we had a discussion about adding certainty and
> precision to model.glossLike, so that empty elements such as gap and
> space could take these as children, and so take advantage of the use of
> relative XPath in @match. (Discussion was here:
> http://purl.org/TEI/FR/2862151 --we agreed also to allow glossLike
> inside space.)
> At the time, although not, I see, in the ticket, I also argued for
> glossLike to be allowed inside milestoneLike elements such as tei:lb,
> but I guess I didn't convince anybody, perhaps because I didn't have a
> compelling use-case to hand.
> I now do.
> We want to be able to express low certainty about a line-break, and
> there are, of course, many aspects of the lb element and it's attributes
> about which we might be less certain. Wouldn't it be lovely to be able
> to do the following:
> <lb n="13"><certainty cert="low" match=".." locus="location"/></lb>
> All perfectly canonical, except that tei:lb can't contain glossLike
> elements. Would anyone be offended by this suggestion (or have other
> ways of encoding this information that make my proposal redundant)?
> Cheers,
> G

More information about the tei-council mailing list