> I can accept dropping the PCData - it takes out a nuisance declaration - but
> now I wonder about PCData elements. They're technically Mixed but without any
> optional elements. Do we need PCData elements?
That was my original design. Ron thought it was clearer to allow
an explicit PCData element equivalent to an empty Mixed element,
and I acquiesced.
> Also, why does the element need a frequency attribute? Isn't that built into
> the nature of Mixed? It's not like you can nest a Mixed content model under a
> Choice or Seq directly or anything...
It *is* "built in", which is why it can sensibly be represented by a
#FIXED attribute. That way, people can see Mixed, Seq, and Choice
as adhering to a common "frequency architecture". Just a thought,
not anything I'm fanatical about.
-- John Cowan http://www.ccil.org/~cowan cowan@ccil.org You tollerday donsk? N. You tolkatiff scowegian? Nn. You spigotty anglease? Nnn. You phonio saxo? Nnnn. Clear all so! 'Tis a Jute.... (Finnegans Wake 16.5)