CDATA by any other name... (was The raw and the cooked)

[Borden, Jonathan]

Lauren Wood wrote:

>
> No. If people think it would be useful, we could potentially add
> some sort of "turn CDATA section into Text" method (and/or vice
> versa) in Level 2. Then the DOM client could run that before
> accessing the data. I'm not sure how else we could determine
> access without losing information (I assume you don't mean that
> information in the CDATA sections should be invisible to the client
> application).
>

	Alternatively, you can expose both CDATA as an element of type CDATA and as
text within the TEXT element. This would preserve the intended behavior
w.r.t. text as well as allowing the option of iterating over CDATA elements
for interested parties.

Jonathan Borden
JABR Technology
http://jabr.ne.mediaone.net


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)