W3C home > Mailing lists > Public > public-qt-comments@w3.org > August 2003

RE: [F&O] Comments on resolve-QName and expanded-QName

From: Ashok Malhotra <ashokma@microsoft.com>
Date: Wed, 13 Aug 2003 13:18:23 -0700
Message-ID: <E5B814702B65CB4DA51644580E4853FB0A3CBC4C@red-msg-12.redmond.corp.microsoft.com>
To: "Priscilla Walmsley" <priscilla@walmsley.com>, <public-qt-comments@w3.org>

Thanks for your comments!  As usual, right on!
I've made the changes you suggested but you should know that
there is an open issue on the coonstruction of QNames and the
functionality and/or semantics may change.

All the best, Ashok

> -----Original Message-----
> From: public-qt-comments-request@w3.org [mailto:public-qt-comments-
> request@w3.org] On Behalf Of Priscilla Walmsley
> Sent: Monday, July 07, 2003 5:05 AM
> To: public-qt-comments@w3.org
> Subject: [F&O] Comments on resolve-QName and expanded-QName
> 1. The beginning of Section of 10.1 says "Since the validity of a
> is situation dependent, there is no constructor function for QName
> defined in 5 Constructor Functions. Neither is casting defined for
> from any other type in 17 Casting Functions."  These sentences should
> removed, since they are no longer true.
> 2. The draft does not say what error resolve-QName or expanded-QName
> should raise if the argument is not a valid XML name (e.g. starts with
> number or contains an invalid character).  This could be fixed for
> expanded-QName by making the second argument an xs:NCName, but for
> resolve-QName it seems you would need a new error message.
> 3.  The example in the "Usage Note" (Section has two errors:
> (a) it is missing a right parenthesis at the end of the if-expression,
> and (b) it passes the empty sequence to expanded-QName when it should
> passing a zero-length string.  (This example is repeated in the
> to xs:Qname" section.)
> Thanks,
> Priscilla
Received on Wednesday, 13 August 2003 16:18:58 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:56:49 UTC