- From: <bugzilla@wiggum.w3.org>
- Date: Wed, 08 Jul 2009 22:52:40 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6131
Bogdan Butnaru <bogdanb+w3c+bugzilla@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bogdanb+w3c+bugzilla@gmail.c
| |om
--- Comment #9 from Bogdan Butnaru <bogdanb+w3c+bugzilla@gmail.com> 2009-07-08 22:52:39 ---
Is there any particular reason why allowing an URILiteral wherever a NCName
prefix would be allowed wouldn't work?
This mostly means:
* allow « URILiteral ":" NCName /* ws:explicit */ » for QName (the xs:QName
generated will have an implementation-dependent prefix; we might want to
restrict implementations NOT to use a prefix that is already bound to a
different namespace (though that wouldn't necessarily be a problem), and maybe
explicitly allow/require to reuse a prefix defined for that namespace, if it
exists), and
* « URILiteral ":" "*" /* ws:explicit */ » for wildcard tests.
An empty URILiteral means, of course, no namespace (this might be useful to
keep things out of the default element namespace, without explicitly defining a
prefix for the empty namespace).
I can't think of any context where a URILiteral followed by a colon currently
means something, in either XQuery or XPath (not sure about XSLT).
Also, I believe this would also work for direct element constructors. (I
haven't checked the production for NameStart, but I think it disallows quotes.)
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 8 July 2009 22:52:49 UTC