[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Removing namespaces without escaping CDATA???

Subject: Re: Removing namespaces without escaping CDATA???
From: "Mukul Gandhi" <gandhi.mukul@xxxxxxxxx>
Date: Mon, 9 Apr 2007 23:03:27 +0530
Re:  Removing namespaces without escaping CDATA???
I shall try to explain my point of view..

Let's say we have following XML:
<x>
 <y></y>
 <p>
   <y></y>
   <q>
      <y></y>
   </q>
 </p>
</x>
(text content can be placed anywhere as desired)

If I do, <xsl:output cdata-section-elements="y" />, then all y
elements will contain CDATA sections. This may be desirable in very
specific cases. But it will be more convenient, if I am able to put
CDATA section at this location /x/p/q/y, and not to any other y's.

Can we achieve this (in 1.0 or 2.0)?

On 4/9/07, Abel Braaksma <abel.online@xxxxxxxxx> wrote:
>> Also, specifying cdata-section-elements here, <xsl:output
>> cdata-section-elements="qnames" /> seem to have a shortcoming, that
>> it's too global (as I said earlier). Do you agree to this point?

You can 'annotate' the result tree in XSLT 2.0, though possibly not as
conveniently as Mukul Gandhi requests. The attribute
'cdata-section-elements' is an AVT in the xsl:result-document element
and it must result in one or more qnames. But this requires redesigning
your stylesheets in such a way that you use xsl:result-document, instead
of xsl:output (but that should not be too hard if it is 'global'). This:

<xsl:variable name="my-cdata" select="'as-cdata'" />
<xsl:result-document cdata-section-elements="{$my-cdata}"
href="analyze.xml">
  <as-cdata>
      <xsl:text>Has some text</xsl:text>
      <not-cdata />
  </as-cdata>
  <as-cdata>Less then is: &lt;, ampersand is: &amp;</as-cdata>
</xsl:result-document>


results in the following output (Saxon 8.9):


<as-cdata><![CDATA[Has some text]]><not-cdata/>
</as-cdata>
<as-cdata><![CDATA[Less then is: <, ampersand is: &]]></as-cdata>


You have all freedom, the only drawback compared to your d-o-e-like approach is that you will have to determine the contents of the AVT beforehand, instead of per element. But as Michael and David already pointed out, would you really want to do this?

Cheers,
-- Abel

PS: it is probably better to declare $my-cdata as 'xs:Qname' or 'xs:Qname*'.


--
Regards,
Mukul Gandhi

Current Thread

PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.