Instead of an <appSpan/> wouldn't it be better to use <app> in
the stand off manner documented at
i.e. use @from and @to to point to the starting point and
ending point of the app, by use of @xml:ids on elements there
(e.g. <anchor/>) or xpointer schemes like xpath()?
And no, my suggestion of @except and @select were not intended to
argue against a block level <app>, though you could indeed use
@select to model such in some ways. When you get to things of
such size, as Peter notes, there may be more worry about overlap
(though as you note, that happens at phrase level), but merely
because of the size and for clarity I would be more tempted by a
standoff pointing or outofline markup approach rather than an
embedded one of wrapping <blockApp> (or something) around a set
of <blockRdg> elements which had <div>s or some such inside
them. Just starts to get messy.
On 19/05/15 15:02, Burghart Marjorie wrote:
> Hi Peter!
> I'm all for an <appSpan/>, but I do not think it is mutually
> exclusive with a block-level <app/>. I beg to disagree with
> the argument that a block-level <app/> would run into
> overlapping issues more than the current phrase-level one. Let
> me have a block-level app for the many cases when it is just
> what we need, AND an <appSpan/>, more difficult to process but
> very useful too, indeed.
> Best wishes, Marjorie
> ----- Mail original ----- De: "Peter Boot"
> <[log in to unmask]> À: "Burghart Marjorie"
> <[log in to unmask]>, [log in to unmask] Envoyé:
> Mardi 19 Mai 2015 15:49:18 Objet: RE: Encoding divergent
> ending of a story (or: the <app> strikes back)
> Hi Marjorie
>> We REALLY need a block-level <app/>.
> What you need is an appSpan, not just a block-level app, as
> that would often run into overlap issues.
Dr James Cummings, [log in to unmask]
Academic IT Services, University of Oxford