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

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

From: Priscilla Walmsley <priscilla@walmsley.com>
Date: Mon, 7 Jul 2003 08:05:15 -0400
To: <public-qt-comments@w3.org>
Message-ID: <003401c34480$0732ac90$ef2efea9@WALMSLEYPH>

1. The beginning of Section of 10.1 says "Since the validity of a QName
is situation dependent, there is no constructor function for QName
defined in 5 Constructor Functions. Neither is casting defined for QName
from any other type in 17 Casting Functions."  These sentences should be
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 a
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 be
passing a zero-length string.  (This example is repeated in the "Casting
to xs:Qname" section.)

Received on Monday, 7 July 2003 08:05:24 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:13 UTC