This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 5270 - Casting between NOTATION and QName
Summary: Casting between NOTATION and QName
Status: CLOSED DUPLICATE of bug 4901
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Functions and Operators 3.0 (show other bugs)
Version: Working drafts
Hardware: PC Windows XP
: P2 enhancement
Target Milestone: ---
Assignee: Michael Kay
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
Depends on:
Reported: 2007-11-16 09:25 UTC by Michael Kay
Modified: 2009-10-12 22:31 UTC (History)
0 users

See Also:


Description Michael Kay 2007-11-16 09:25:43 UTC
The following comment was raised as part of the discussion on bug #4874, and is raised here as an enhancement request so that it is not lost when 4874 is closed.

For the future: it seems unsatisfactory that the only way of constructing a
NOTATION is from a literal string, and that there is no way of processing a
NOTATION other than converting it to a string. This makes it impossible for the
user to determine, for example, what namespace a NOTATION is in, or to ensure
that this namespace is declared when an attribute of type NOTATION is written
to the result tree. I suggest that we should allow casting between QName and
NOTATION in both directions, with the obvious semantics, making operations
defined on QNames available for constructing and deconstructing NOTATIONs.
Comment 1 Michael Kay 2007-11-16 09:30:15 UTC

*** This bug has been marked as a duplicate of bug 4901 ***
Comment 2 Michael Kay 2009-10-12 22:31:27 UTC
Since this is a duplicate of a bug that has been closed, I am marking this as closed.