[tei-council] encodingDesc content
Lou Burnard
lou.burnard at oucs.ox.ac.uk
Sun May 24 07:44:29 EDT 2009
Ticket 2761884 raises an interesting question, which I am not completely
certain how to deal with.
" Section 2.3 says, "The encoding description may contain paragraphs of
text,
marked up using the p element, or it may contain more specialised elements
taken from the model.encodingPart class." This doesn't match the content
model:
( model.encodingPart | model.pLike )+"
In response, I observe that we could of course change the content model
to match the prose
( (model.encodingPart, model.encodingPart*)
| (model.pLike, model.pLike*) )
but as this risks breaking existing P5 documents, I am not sure whether to
introduce the change or not. For what it's worth, the content model in P4
(and before that P3) did *not* permit interleaving of paragraphs and other
specialised elements; this is a possibility introduced in P5.
I cannot now remember whether this change was a conscious decision,
presumably made at the time we introduced the model.encodingPart class,
or not.
Whaddya say, council?
More information about the tei-council
mailing list