Am 05.02.2014 17:41, schrieb Martin Holmes:
> If you start to allow structural markup such as <list>s inside
> <sourceDoc> elements, you're going to have to decide, at every level,
> what nests inside what. For instance, should an <item> appear inside a
> <line>? What if it wraps to the next line? Is that two <line>s inside
> one <item>, or two <item>s linked with @next/@prev inside discrete
> <line>s? You would have to privilege one hierarchy, and presumably it
> would be the genetic hierarchy (otherwise you'd be using <text>); the
> other hierarchy would end up horribly fragmented, and its own natural
> relationships (names containing name parts, addresses with addrLines,
> etc.) would be increasingly messy.
This is a very serious point.
Admittedly, the problems inherent in the new version of chapter 11 may
even get worse when content models are carelessly relaxed.
In the documentary (embedded) transcriptions of our project (2000
written modern manuscript pages) <zone> is a kind of div-level element,
whereas <line> is working like a chunk (analogous to a possible
hierarchy of <div> and <ab>).
Now I find that <zone> may not only contain <line>, but also
phrase-level elements. Morever, <line> may even contain <zone>.
Isn't there any defined nesting order?
In comparison, making <line> p-like seems harmless to me.
Goethe-Universität Frankfurt am Main | Institut für deutsche Literatur und ihre Didaktik
Historisch-kritische Edition von Goethes Faust | Genetic Edition of Goethe's Faust | faustedition.net
Freies Deutsches Hochstift | Großer Hirschgraben 23-25 | 60311 Frankfurt am Main | Fon +49(0)69-13880-292