[tei-council] rowing back on <mixedContent>

[Sebastian Rahtz]

we decided this week to fork <content> into 

  a) a full <content> which allows any construct you like, including <textNode>
  b) a restricted <mixedContent> which does not permit <textNode>, and is interpreted
as meaning “everything is an alternation with PCDATA”

which seemed like a good idea.

I wonder now, though, why we are bothering? we are supplying <mixedContent>
simply to provide a safe environment for those who will need to make an XML DTD
from their efforts. Is that a sensible use of our time and energy?
--
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.