- From: Ashok Malhotra <ashok.malhotra@oracle.com>
- Date: Mon, 17 Jan 2005 17:10:48 -0800
- To: Laurens Holst <lholst@students.cs.uu.nl>, public-qt-comments@w3.org
That was a bug in the status section. It now says... "Construction of xs:QNames and types derived from xs:NOTATIONs has been clarified. It is now possible to construct xs:QNames and types derived from xs:NOTATIONs from xs:string literals." Sorry about that! All the best, Ashok > -----Original Message----- > From: public-qt-comments-request@w3.org > [mailto:public-qt-comments-request@w3.org] On Behalf Of Laurens Holst > Sent: Monday, January 17, 2005 4:54 PM > To: public-qt-comments@w3.org > Subject: Re: [F&O] Casting to xs:NOTATION, xs:QName not clarified > > > Michael Rys wrote: > > The casting table applies to both forms: > > > > So if the casting tables says that you cannot cast from one type to > > another, it applies to both cast as Type and Type(). > > > > Best regards > > Michael > > What confuses me is, that in the 'Status of this Document' > section of XQuery 1.0 and XPath 2.0 Functions and Operators, it says: > > "Some of the more significant changes that appear in this > version of the document are: > > * Casting to QName and xs:NOTATION has been clarified. > It is now possible to cast from xs:string literals to QName > and xs:NOTATION." > > --- > > That aside, a quick question... I have been looking at the > spec for a little while to find a way to resolve an > xs:string, containing an XPath query, to a nodeset... Does > anyone know how to achieve that? :) > > > ~Grauw > > -- > Ushiko-san! Kimi wa doushite, Ushiko-san!! > > >
Received on Tuesday, 18 January 2005 01:11:34 UTC