Roger, overlapping markup is what's possible using SGML's CONCUR feature. Apart from the classic examples in poetry and drama, I've encountered the need for overlapping markup in text encoding of postal addresses, where there's an expectation to present an address on a postal piece in a particular way with respect to what goes into which line, yet the structural decomposition of the address into parts according to eg. UPU S1 sometimes needs to overlap parts of the conventional line address representations. Btw postal/logistical addressing is also a good example for interpreting line-end characters and other tokens as markup delimiters, ie what SGML SHORTREF is about, and what's being rediscovered as "invisible markup" by XML heads. And XML is not a "data language", it's a markup language. Saying this because, while entertaining and sometimes useful, reflecting on markup features without the text representation angle can never result in meaningful discussion about the intention of the characteristics of a language the whole point of which is to represent serialized text. Marcus sgml.io Am 30.05.2022 um 05:55 schrieb Dimitre Novatchev <dnovatchev@gmail.com>:
|