OK, could work in this case. But this does not solve of course the critical edition issue.
We REALLY need a block-level <app/>.
----- Mail original -----
De: "James Cummings" <[log in to unmask]>
À: [log in to unmask]
Envoyé: Mardi 19 Mai 2015 12:51:24
Objet: Re: Encoding divergent ending of a story (or: the <app> strikes back)
On 18/05/15 13:10, Federico Meschini wrote:
> >While we wait for the much-needed upgrade of <app> from
> phrase-level to paragraph-level (or >better div-level), what
> would be the best-practice recommended to encode this alternative
> My (quick) two cents.
> I would use the linking part of the Guidelines together with the
> @ana attribute to indicate the actual alternative between these
> two endings, and, eventually, if you want a more structured way
> for expressing this alternative, feature structure could be a
> interesting solution to explore.
Isn't this precisely what the global attribute @exclude is for?
It points to one or more elements that are in exclusive
alternation with the current element.
<div xml:id="variant1" exclude="#variant2">....</div>
<div xml:id="variant2" exclude="#variant1">....</div>
Or if you want to select one or more alternants for this element
use the @select element.
Dr James Cummings, [log in to unmask]
Academic IT Services, University of Oxford