OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: Tradeoffs of XML encoding by enclosing all content in CDATA blocks

Karr, David wrote:

> I pointed out to a client that they're seeing failures parsing XML 
> because some of the element content that they're producing contains 
> characters illegal in XML content, like "&" (unencoded).  They 
> acknowledged that should be fixed, but they also said they could
> instead enclose all content with CDATA blocks.  That seems bizarre to
> me, but I'm not sure I can immediately come up with all the cogent
> arguments against that.  Can someone summarize specifically why you
> should NOT do that?

If they aren't willing to consider what characters exist in their data, 
they can't guarantee that the string "]]>" can't exist, delimiting their 
CDATA section and breaking their document. I've never liked CDATA 
sections and rarely use them - I think they're generally a lazy answer 
to a simple question.


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS