I made a feature request (*add element rs as member of model.linePart*) here:
The request may also be seen as an agent for reconsidering whether there should be more elements of a rather interpretative transcription within the boundaries set for documentary editing so far.
There has been a similar discussion on the list, started by Elena Pierazzo in January 2012 (*Content model of <line>*). As with the recent discussion about <rs>, opinions diverged considerably on the subject.
Just to make one more point: I would say that we already have rather 'interpretative' elements available within <line> by way of model.global, like <interp> or <index> or all the elements from model.global.spoken.
Von: Roberto Rosselli Del Turco [mailto:[log in to unmask]]
Gesendet: Dienstag, 26. November 2013 17:44
An: Oliver Gasperlin; [log in to unmask]
Betreff: Re: Er: [TEI-L] Using <rs> in documentary markup
Il 26/11/2013 12:21, Oliver Gasperlin ha scritto:
> I agree that the <seg> solution within <line> is really abusive and not to
> be considered good markup.
I wouldn't say that it is "abusive": <seg> is generic segment of text,
and is clearly provided as an easy way out in case you need more
interpretative markup in your <line>s. The fact that you can do almost
anything you want by means of <seg> may be a good reason to allow more
specific elements in <line> ... or to reconsider the latter to make it
more consistent with the original "no overlap!" intention ;)
Roberto Rosselli Del Turco roberto.rossellidelturco at unito.it
Dipartimento di Studi rosselli at ling.unipi.it
Umanistici Then spoke the thunder DA
Universita' di Torino Datta: what have we given? (TSE)
Hige sceal the heardra, heorte the cenre,
mod sceal the mare, the ure maegen litlath. (Maldon 312-3)