OK, that's cool. Next question: what about ? At present, its content model is macro.paraContent. All the other members of model.segLike have a content model of macro.phraseSeq (the difference is that macro.paraContent permits additionally members of model.inter such as lists) I think this is anomalous. Can anyone come up with a specific use case where a should need to include things that can appear between paragraphs? note that it cannot currently contain paragraphs! aurent Romary writes: > I would definitely avoid breaking this and not impose too many > constraints at the level of the guidelines. The flexibility we have at > present should be counterbalanced by annotation projects defining > precise encoding manuals, depending on the kind of precision and depth > they want to acheive. We had a long discussion on what should be > equivalent to, namely or and I am still not sure that we > should restrain to . > > Le 9 juin 09 à 13:36, Lou Burnard a écrit : > > > At present, segments smaller than (e.g. , ) and those > > larger (eg ) > > are all members of model.segLike. This means that (inter alia) the > > following are > > all valid > > (i) > > (ii) > > (iii) > > While we can all agree that (iii) is barking mad and should be > > stopped, > > it's less clear what to do about (ii). On the one hand, we do now have > > a nice new element for punctuation, which could be defined as a > > sibling for , so that (ii) could be replaced by > > (ii*) > > On the other hand, in the absence till now of , there are > > literally millions of words of corpus out there which follow the > > pattern of (ii). Do we really want them all to become broken? > > I think not, but maybe (as one of the perpetrators) I'm biassed. > > _______________________________________________ > > tei-council mailing list > > tei-council@lists.village.Virginia.EDU > > http://lists.village.Virginia.EDU/mailman/listinfo/tei-council >