<hi rend="CSS(color:red;)">O V E R L</hi> <hi> </hi> <hi rend="CSS(color:blue;)">H</hi> <hi> </hi> <hi rend="CSS(color:purple;)">A P</hi> <hi> </hi> <hi rend="CSS(color:blue;)">P E N S</hi> Syd Bauman WARNING: XInclude processing failed — this file should not be copied or used (and is invalid) as a result.

None.

 automatically converted from presentation.odd conforming to yaps.odd conforming using p2y.xslt and p2y.perl
The Problem XML elements may not overlap document structures often do potential problem for all XML encoding particularly common when encoding extant older texts encoder does not control structure generally less common when creating documents
The Size of The Problem there exist dozens of solutions up to half a dozen papers a year an entire day-long pre-conference event in 2007 an entire chapter of the TEI Guidelines frustration has caused many to investigate non-XML encodings
Solutions milestones fragmentation HORSE

There are roughly half a dozen others which I will not be addressing
Milestones work perfectly for an alternate hierarchy which is completely flat and tessellates page breaks signatures reels of a movie can work well for similar constructs line breaks column breaks
Fragmentation

Take what is logically a single content object encode it as multiple separate XML elements indicate that each XML element is only a partial element optionally have each partial element indicate which is the next piece of the whole content object

TEI provides 2 methods for doing this
Fragmentation: aggregation by hunting/gathering with part

The part attribute can be used for serial cases: all fragments are in sequential order no intervening occurrence of same element type that is not part of the aggregate element e.g., good for l but sometimes not q available on l, lg, div, seg, ab, s, cl, phr, w, m, c

Fragmentation: aggregation by pointing with next and prev

The next and prev attributes can be used for any cases: available on every element when additional tagset for segmentation & alignment is used each fragment must bear either next or prev probably better if each fragment bears both

<l>I found at a conference C M Sperberg-McQueen</l> <l>Sang <q>closing, keynoting, I'm speaking</q></l> <l>And I said to him, <q xml:id="q1" next="#q2">Superman, have you not seen</q>,</l> <l><q xml:id="q2" prev="#q1">The embarrassment havoc I'm wreaking?</q></l>
HORSE not currently available in any system I know of special case of typed segment-boundary delimiter rather than giving an element content, use an empty element for both start and end special attributes point from the start to the end, and from the end to the start <l>I found at a conference C M Sperberg-McQueen</l> <l>Sang <q>closing, keynoting, I'm speaking</q></l> <l>And I said to him, <q sID="q2"/>Superman, have you not seen,</l> <l>The embarrassment havoc I'm wreaking?<q eID="q2"/></l>