RE: [XQuery] Computed CDATA constructor

CDATA generation is currently a serialization option and not a data
model/language feature. We made this decision explicitly, since most
parsers do not communicate CDATA boundaries and maintaining them in the
data model would be problematic.

Did you look at the serialization spec to see if it addresses your
issue?

If you cannot use CDATA on serialization, could you live with defining
this using the extensibility mechanism in your implementation? 

Best regards
Michael

> -----Original Message-----
> From: public-qt-comments-request@w3.org [mailto:public-qt-comments-
> request@w3.org] On Behalf Of Sarah Wilkin
> Sent: Monday, November 10, 2003 2:31 PM
> To: Jonathan Robie
> Cc: public-qt-comments@w3.org
> Subject: Re: [XQuery] Computed CDATA constructor
> 
> 
> > What is it that you would like to do with such a computed
constructor
> > that you can't do without it? Can you think of any scenarios where
the
> > following two expressions could have different results?
> >
> > 1. <foo>{ cdata{ $a } }</foo>
> > 2. <foo>{ $a }</foo>
> 
> Yes. If the implementor has decided to retain CDATA sections and $a is
> "<", then
> 1. <foo><![CDATA[<]]></foo>
> 2. <foo>&lt;</foo>
> 
> Although these are semantically identical, it may be important to the
> user to provide such hints for serialization. Other applications may
> depend on this information being retained (for example, creating a
> document for an app that parses CDATA sections differently -- or for
> that matter scrapes them out).
> 
> --Sarah
>

Received on Monday, 10 November 2003 19:47:44 UTC