[Bug 26679] New: [xslt 3.0] Errors in xsl:expose and xsl:accept

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

            Bug ID: 26679
           Summary: [xslt 3.0] Errors in xsl:expose and xsl:accept
           Product: XPath / XQuery / XSLT
           Version: Working 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

xsl:expose has

[ERR XTSE3020] It is a static error if an xsl:expose element matches no
components in the containing package, unless the tokens in the names attribute
are all wildcards.

and xsl:accept similarly has

[ERR XTSE3030] It is a static error if an xsl:accept element matches no
components in the used package, unless the tokens in its names attribute are
all wildcards.

The means that if the attribute names="a b c" is used, it's OK provided at
least one of a, b, or c exists in the relevant package. This seems to make
little sense. I think the rule should be that any token that isn't a wildcard
is required to match the name of a component in the relevant package. The rules
should be rewritten thus:

[ERR XTSE3020] It is a static error if a token in the names attribute of
xsl:expose, other than a wildcard, matches no component in the containing
package.

and xsl:accept similarly has

[ERR XTSE3030] It is a static error if a token in the names attribute of
xsl:accept, other than a wildcard, matches no component in the used package.

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

Received on Wednesday, 27 August 2014 10:11:43 UTC