- From: <bugzilla@jessica.w3.org>
- Date: Mon, 24 Aug 2015 20:06:51 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29081 Bug ID: 29081 Summary: [xslt 3.0] Use of reserved namespaces in extensions Product: XPath / XQuery / XSLT Version: Last Call drafts Hardware: PC OS: All Status: NEW Severity: normal Priority: P2 Component: XSLT 3.0 Assignee: mike@saxonica.com Reporter: mike@saxonica.com QA Contact: public-qt-comments@w3.org Target Milestone: --- Tests maps-901a to maps-901e assume that a processor is required to reject calls on the map:new() function. Now, as it happens, current Saxon releases support this function in order to ease transition from earlier working drafts. The question therefore arises whether this is non-conformant. If the function is allowed at all, then it is an extension function, and the question is whether extension functions are permitted in a reserved namespace. Section 5.1.3 on reserved namespaces says that they can be used for some purposes (names of literal result elements and attributes) and not others (names of stylesheet-defined variables and functions). Extension functions are not mentioned. Do we want to disallow use of reserved namespaces in the names of extension functions (and presumably extension elements?) If so, we should say so, otherwise we need to remove these tests. Allowing extension functions in these namespaces allows vendors to implement a function defined in one version of the W3C specs in a processor that aims for conformance with a different version. This can help interoperability in some ways, and hinder it in others, so the right answer is not obvious. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 24 August 2015 20:06:53 UTC