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

[Bug 28116] [xslt 3.0] xsl:original and reserved namespaces

From: <bugzilla@jessica.w3.org>
Date: Sun, 15 Mar 2015 18:18:27 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-28116-523-137dEarUo5@http.www.w3.org/Bugs/Public/>

Abel Braaksma <abel.braaksma@xs4all.nl> changed:

           What    |Removed                     |Added
                 CC|                            |abel.braaksma@xs4all.nl

--- Comment #1 from Abel Braaksma <abel.braaksma@xs4all.nl> ---
Please note also that we do not say much about error codes in fn:error,
xsl:assert and xsl:message, but we do say about standard namespaces that their
use is very restrictive:

"[…] and MUST  be used only as specified in this and related specifications."


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

We do not have a definition of what a stylesheet-defined object is, but I would
assume error codes to belong in there. It is clear from this description that
<xsl:variable name="err:somevalue" /> is disallowed, but is
fn:error('err:somevalue') also disallowed?

If it were disallowed, early discovery of non-existing errors is possible: for
<xsl:catch errors="err:UNDEFINED" />, a processor can warn that the error will
never be raised because it is not defined in the spec and homegrown errors with
such name are impossible. Potentially, perhaps, this should even be an error
case and the processor should statically raise an error that an unspecified
error code in the standard error namespace is used.

The accompanying error code as in the Description of this bug, does not mention
this use as being forbidden, though perhaps it should be.

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Sunday, 15 March 2015 18:18:30 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:53 UTC