[tei-council] <content> vs <mixedContent>

[Sebastian Rahtz]

On 3 Oct 2014, at 20:26, Lou Burnard <lou.burnard at retired.ox.ac.uk> wrote:
> 
> Hmm, is that true? Surely you'd just write the new <content> model? I don't think you can say @mode="delete" on  elements which are not members of att. combinable

then you end up with both <content> and <mixedContent> in the cooked ODD, which has to illegal, surely.

as you say

> The interesting question is how an ODD processor knows that since only one of  mixedContent or content is permissible here, whichever one your spec supplies replaces the other.

which is implementable. as in, it is unambiguous. if the customisation has a content or a mixed content, it overrides
any existing content or mixed content.

--
Sebastian Rahtz      
Director (Research) of Academic IT
University of Oxford IT Services
13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431

Não sou nada.
Nunca serei nada.
Não posso querer ser nada.
À parte isso, tenho em mim todos os sonhos do mundo.