Altova Mailing List Archives

Re: CDATA sections in W3C XML Infoset

From: Joe English <jenglish@---------.--->
To: xml-dev@-----.---.---
Date: 3/28/2001 5:35:00 AM
Richard Lanyon wrote:
> Could someone explain to me why CDATA section start/end markers were
> taken out of the W3C Infoset?

I don't know the official rationale, but it makes sense:
CDATA section boundaries are a lexical artifact, much
like the distinction between '"' and ''' in attribute
value specifications, whitespace in tags, and entity
references, all of which are also omitted from the

> I was hoping to use the Infoset in writing the spec for XML Script,
> but the removal of these markers makes it very difficult to write an
> implementation of XML Script which is based around a DOM.  [...]
> Is there any chance that CDATA section start/end markers could be put
> back in?

Probably not, but there's no reason why you can't include CDATA
section boundaries in *your* Infoset.  The W3C XML Infoset
is a lowest common denominator; for XML Script to be "Infoset
compliant" it shouldn't throw anything in the W3C infoset out,
but it's free to add any new items that are appropriate.

That's my understanding anyway.

--Joe English



These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.