W3C home > Mailing lists > Public > public-qt-comments@w3.org > September 2015

[Bug 29081] [xslt 3.0] Use of reserved namespaces in extensions

From: <bugzilla@jessica.w3.org>
Date: Thu, 03 Sep 2015 22:00:46 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29081-523-z6R9NkUzQm@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29081

Michael Kay <mike@saxonica.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED

--- Comment #1 from Michael Kay <mike@saxonica.com> ---
The WG was minded to impose the rule that extensions must not use reserved
namespaces.

The following wording is proposed:

(a) In 5.1.3 change the sentence

Reserved namespaces must not be used, however, in the names of
stylesheet-defined objects such as variables and stylesheet functions.

to

Reserved namespaces must not be used, however, in the names of
stylesheet-defined objects such as variables and stylesheet functions, nor in
the names of extension functions or extension instructions.

(b) In 5.1.3 add:

It is not an error to use a reserved namespace in the name of an extension
attribute: attributes such as <code>xml:space</code> and <code>xsi:type</code>
fall into this category. XSLT processors MUST NOT reject such attributes, and
MUST NOT attach any meaning to them other than any meaning defined by the
relevant specification.

(c) Add the error:

[ERR XTSE0085] It is a static error to use a reserved namespace in the name of
any extension function or extension instruction, other than a function or
instruction defined in this specification or in a normatively referenced
specification. It is a static error to use a prefix bound to a reserved
namespace in the [xsl:]extension-element-prefixes attribute.

(d) In 24.1 Extension Functions

after the sentence "The set of functions that can be called from a
FunctionCallXP30 within an XPath expression may include one or more extension
functions. The expanded QName of an extension function always has a non-null
namespace URI."

add ", which MUST NOT be the URI of a reserved namespace."

(e) 24.2.1 Designating an Extension Namespace

add "A reserved namespace cannot be designated as an extension namespace: see
[ERR XTSE0085]"

(f) Add to the incompatibilities appendix: "XSLT 3.0 reserves certain
namespaces for use as defined in this or related specifications."

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 3 September 2015 22:00:48 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 3 September 2015 22:00:48 UTC