[Bug 28129] [xslt 3.0] xsl:global-context-item/@use-accumulators

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

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

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

--- Comment #2 from Abel Braaksma <abel.braaksma@xs4all.nl> ---
I think the issue discussed in comment#1 is a result of merging xsl:package and
xsl:stylesheet/transform into one top-level element, as proposed and
implemented as a result of Bug 26468. From that bug's resolution:

<quote>
1. xsl:package has the same content model as xsl:stylesheet/transform, with the
addition that it allows xsl:expose and xsl:use-package elements to appear as
children (in any position).
</quote>

It appears to me that we simply forgot to allow xsl:global-context-item as a
child of xsl:stylesheet. It makes sense to put it there, as a stylesheet with
an xsl:stylesheet root is still a (simplified) package.

> (b) it is an error if it appears in an included or imported stylesheet 
> module unless an equivalent declaration appears in the top-level module 
> of the package.

I think we should always consider it an error. I can't think of a use-case why
we should allow it in an imported module. It is a feature of packages, there
are not XSLT 2.0 stylesheets around with such a declaration so there's no
backwards compatibility issue, and if someone wants to import that declaration,
he or she should create a package (by replacing xsl:stylesheet with xsl:package
and use xsl:use-package instead).

Another argument against this is that *only* the principal stylesheet is a
simplified package, the imported or included modules are not, so they should
not contain features that are only available with packages.

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

Received on Friday, 13 March 2015 17:13:22 UTC