- From: <bugzilla@wiggum.w3.org>
- Date: Mon, 05 Jun 2006 21:23:42 +0000
- To: public-qt-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=3314 Summary: 3.14 Extension Expressions, what can the namespace URI contain? Product: XPath / XQuery / XSLT Version: Candidate Recommendation Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: XQuery AssignedTo: chamberl@almaden.ibm.com ReportedBy: frans.englich@telia.com QAContact: public-qt-comments@w3.org 3.14 Extension Expressions reads: <quote> The QName of a pragma must resolve to a namespace URI and local name, using the statically known namespaces [err:XPST0081]. Note: There is no default namespace for pragmas. </quote> I think two things is attempted to be said here: * That the QName cannot contain an undeclared prefix, as for any other QName(Hence, XPST0081). * That the namespace URI cannot be "empty", just as for user functions. (Why is it otherwise stressed no default namespace exists?) I don't think the latter is clear. Neither, making the default namespace undefined, doesn't cover this case: declare namespace prefix = ""; (# prefix:notRecognized #) Proposed wording: After: "The QName of a pragma must resolve to a namespace URI and local name, using the statically known namespaces [err:XPST0081]." Add: "The namespace URI must be non-empty[ERROR CODE]. In effect, this means the QName must always have a prefix." I don't know about what error code to use, XPST0081 seems a bit out of place.(Allocate a XQST-code?) An other alternative is that I'm completely out of space, of course. Frans
Received on Monday, 5 June 2006 21:23:50 UTC