PCDATA vs CDATA
tomo at everyware.com
Tue Jun 30 21:14:51 BST 1998
This topic has been touched on before, somewhat, in earlier posts (as I can
glean from the archives), but I haven't found the specific answer that I am
looking for so I hope someone can help.
Why can an element's mixed content only be declared as PCDATA, not CDATA?
There are many times when the content for an element may need to be cordoned
off in a CDATA section, but it is inconvenient (and ugly) to force it to be
entered every time. I don't understand why the decision to disallow a CDATA
declaration was made. Parsing does not seem to be any more difficult if it
were allowed, and in cases where most leaf elements can contain content that
may be misinterpreted as markup, removing the need to explicitly include
<![CDATA[ ... ]]> everywhere could reduce the document size (and parsing
time) substantially. The documents become far more readable as well.
In a case I am working on, many of the elements' content in my documents
can include HTML or other data easily confused for markup.
Thanks, in advance, for any comments.
Director of Research, EveryWare Development Inc.
"Try not! Do, or do not. There is no 'try'." - Yoda
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;
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)
More information about the Xml-dev