[Bug 29808] New: [XSLT30] (editorial) xsl:use-package and using unnamed packages

https://www.w3.org/Bugs/Public/show_bug.cgi?id=29808

            Bug ID: 29808
           Summary: [XSLT30] (editorial) xsl:use-package and using unnamed
                    packages
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSLT 3.0
          Assignee: mike@saxonica.com
          Reporter: abel.braaksma@xs4all.nl
        QA Contact: public-qt-comments@w3.org
  Target Milestone: ---

It is understandable that we disallow unnamed packages as library packages, but
it is unclear what error should be raised. I suggest XTSE3000.

Under 3.5 Packages we say this:

"Unnamed packages are allowed, but they can only be used as the “top level” of
an application; they cannot be the target of an xsl:use-package declaration in
another package."

I couldn't find normatively whether this is illegal, though:

<xsl:use-package name="" version="*" />

Since an empty URI is also a legal (relative) URI, and we only say in the text
that the name must be codepoint-equal, it would work that this actually loads
an unnamed package (which would then subsequently fail because of the rule in
3.5).

I don't think we intend to allow this to happen. I suggest therefore an
editorial clarification, for instance on the xsl:use-package/@name attribute,
which can then consequently specify the error we would like to assign.

For instance, we could replace this:

"The used package must have a name that is an exact match for the name in the
name attribute (using codepoint comparison), and its explicit or implicit
package-version must match the version range given in the package-version
attribute."

With something like this (added sentences):

"The used package must have a name that is an exact match for the name in the
name attribute (using codepoint comparison), and its explicit or implicit
package-version must match the version range given in the package-version
attribute. If the value of the name attribute is the empty string, or exists
entirely of whitespace, it designates the unnamed package. However, the empty
package may only appear as top-level package: err:XTSE3000."

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Monday, 5 September 2016 03:13:28 UTC