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: [xml-dev] CDATA headache

On Wed, Sep 9, 2009 at 4:54 PM, michael odling-smee
<mike.odlingsmee@gmail.com> wrote:
>  about 5% of the elements in the source
> document are <value/> elements not all of which contain CDATA. If we added
> new CDATA sections to the output this would probably not satisfy the
> customer either.

Just to add another point. If some of input <value /> elements,
contain CDATA markers, then it means to me, that your application
design has thought, that CDATA was necessary on <value /> elements.
Some of <value /> elements in your input XML don't have CDATA markers,
and this I think, is the problem of the process, which created this

But leaving the problem aside, of incompletely specified CDATA markers
in your input, you can fix this problem completely, entirely within
your stylesheet. You can put cdata-section-elements="value" in your
XSLT stylesheet, and this will generate CDATA markers in all the
<value /> elements, in the output. And this is what your application
design thought, in the first place. So this to me, is what should be

As an additional work, and if you want, you can work to improve the
process, which is producing your input XML, so that it put's CDATA
markers in all the <value /> elements.

Mukul Gandhi

[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