<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>

Examples of overlapping structures Physical features like pages, columns, and lines, and textual things like paragraphs or names Verse lines and quotations, names, other phrasal elements Verse lines and linguistic features Dramatic speeches and verse lines Handwritten additions or deletions and other structures Typographical features and linguistic features

This is a potential problem for all XML encoding

Particularly common when encoding extant older texts: the encoder does not control structure

generally less common when creating documents

There are a variety of approaches to representing these kinds of overlapping structures in TEI: sometimes you just have one option sometimes there are a few different ways to approach the problem we'll look at the various possibilities; some we've already seen without realizing it

Empty elements used as milestones digested. Its long trunk, as seen slanting down from out of the building across the wharf and into the ship, is a mere wooden pipe; but this pipe is divided within. It has two departments; and as the grain-bearing troughs pass up the one on a pliable band, they pass empty down the other. The system therefore is that of an ordinary dredging machine; only that corn, and not mud is taken away, and that the buckets or troughs are hidden from sight. Below, within the stomach of the poor bark, three or four labourers are at work, helping to feed the elevator. They shovel the corn up towards its maw, so that at every swallow he should take in all that he can hold... ...The transit of the bushels of corn from the larger vessel to the smaller will have taken less than a minute, and the cost of that transit will have been—a farthing.

]]>

Simplest option: instead of encoding the feature by enclosing it in an element, instead just mark its boundaries with empty elements

The most common case of this is with milestone elements: Elements that divide the text into segments according to some system: pages, columns, lines works perfectly for an information structure which is completely flat and divides up the whole text into parts: page breaks, signatures, reels of a movie i.e. there's nothing in the text that isn't on some page; there's nothing in a paragraph that's not on some line in these cases, you mark the boundaries between segments, so each boundary element marks the end of one segment and the start of the next.

Empty elements used as endpoints

An elevator is as ugly a monster as has been yet produced. In uncouthness of form it outdoes those obsolete old brutes who used to roam about the semi- acqueous world, and live a most uncomfortable life with their great hungering stomachs and huge un- satisfied maws. The elevator itself consists of a big moveable trunk,—moveable as is that of an elephant, but not pliable, and less graceful even than an ele- phant's. This is attached to a huge granary or barn...

]]> ...for the elevator is an amphibious insti- tution, and flourishes only on the banks of navigable waters. When its head is ensconced within its box, and the beast of prey is thus nearly hidden within the building, the unsuspicious vessel is brought up within reach of the creature's trunk, and down it comes, like a mosquito's proboscis, right through the deck, in at the open aperture of the hold, and so into the very vitals and bowels of the ship. When there, it goes to work upon its food with a greed and avidity that is disgusting to a beholder of any taste or imagination.

And now I must explain the anatomical arrangement by which the elevator still devours and continues to devour, till the corn within its reach has all been swallowed, masticated, and digested.

]]>

But in addition there are other cases where it's handy to be able to mark the ends of an element at arbitrary places, rather than having to fit the element neatly into the document hierarchy classic example is additions and deletions: authors often add large chunks of stuff, or delete parts of things that don't match the textual structure

For these, as we saw briefly yesterday, we can mark them much more effectively by putting an empty element at each end, sort of like marking the boundaries of an impromptu soccer field by putting your shoes at each end

Then create a link between the two, using the pointing system we talked about yesterday...

Fragmentation Leo. Go on, go on: Thou canst not speake too much, I have deserv'd All tongues to talk their bittrest. Lord. Say no more; How ere the business goes, you have made fault I'th boldnesse of your speech. Pauline. I am sorry for't; All faults I make, when I shall come to know them ]]>

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; the first is the part= attribute...

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

Another approach to fragmentation Mortal, she said, I'm sent to you, Then hold my precepts fast; Remember earth's best joys are few, And can't for ever last. ]]>

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