XSchema Spec Section 2.3, Draft 1

[Simon St.Laurent]

>The whole point of Mixed is that it signals that
>both PCDATA and elements are permitted.
>
>It occurs to me that the Mixed element should have a
>Frequency attribute declared #FIXED "ZeroOrMore".

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?

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...

Simon St.Laurent
Dynamic HTML: A Primer / XML: A Primer / Cookies


xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)