XSLT 2.0 uses typed value throughout its semantics, with the single exception being the fn:string() function. It has to use typed value, because XSLT always accesses data via XPath expressions. Michael Kay > -----Original Message----- > From: Daniela Florescu [mailto:danielaf@bea.com] > Sent: 16 February 2004 19:48 > To: Michael Kay > Cc: public-qt-comments@w3.org > Subject: Re: [DM] BEA_003 > > > > In which contexts does XSLT 2.0 uses the typed value and how > ? Maybe it should use the string version instead ? > > Best regards, > Dana > > > >> The typed value of a document should raise an error. > >> The typed value of a element with complex type with > >> mixed content should raise an error. > >> The typed error on a namespace node should raise an error. > The typed > >> value of a processing instruction should raise an error. The typed > >> value of comment should raise an error. > > > > > Changing any of the four rules above would break most XSLT 1.0 > > stylesheets. >Received on Monday, 16 February 2004 16:31:55 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:14:05 GMT