W3C home > Mailing lists > Public > public-qt-comments@w3.org > November 2004

RE: [F&O] Casting to xs:NOTATION, xs:QName not clarified

From: Ashok Malhotra <ashok.malhotra@oracle.com>
Date: Fri, 5 Nov 2004 14:46:28 -0800
To: Sarah Wilkin <swilkin@apple.com>, public-qt-comments@w3.org
Message-ID: <20041105144628744.00000002360@amalhotr-pc>

Sarah:
The status section is incorrect.  It shd say:

Construction of xs:QName and xs:NOTATION has been clarified. It is now possible to construct xs:QName and xs:NOTATION from string literals. 


All the best, Ashok

-----Original Message-----
From: public-qt-comments-request@w3.org [mailto:public-qt-comments-request@w3.org] On Behalf Of Sarah Wilkin
Sent: Thursday, November 04, 2004 2:33 PM
To: public-qt-comments@w3.org
Subject: [F&O] Casting to xs:NOTATION, xs:QName not clarified


In the Oct spec, it says:

Casting to QName and xs:NOTATION has been clarified. It is now possible to cast from xs:string literals to QName and xs:NOTATION.

But in the casting section it says:

Casting from xs:string and xdt:untypedAtomic to xs:QName, xs:NOTATION, or types derived from them is not possible because it requires knowledge of the namespace context. Constructor functions are available to construct values of these types provided that the lexical representation is known statically.

So which is it?

--Sarah
Received on Friday, 5 November 2004 22:47:19 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 18:14:37 GMT