Cart
[Home] [By Thread] [By Date] [Recent Entries]
Simon St.Laurent wrote: > 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@c... 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) xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i... Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ To (un)subscribe, mailto:majordomo@i... the following message; (un)subscribe xml-dev To subscribe to the digests, mailto:majordomo@i... the following message; subscribe xml-dev-digest List coordinator, Henry Rzepa (mailto:rzepa@i...)
|
