This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Originally raised on email, see https://lists.w3.org/Archives/Public/public-xsl-wg/2016Jan/0002.html We dropped the XQuery Invocation Feature through bug 29251 (its changes have not been logged, I reported that as an editorial bug here: https://www.w3.org/Bugs/Public/show_bug.cgi?id=29375). We know that how a package is located and presented is implementation defined. It can be a compiled package etc, etc. However, I think it makes sense to add a little Note somewhere that strongly suggests that an implementation is free to offer a package written in any language. The way we currently describe it seems to suggest that only a package with xsl:package is allowed, but a package can just as well be written in a different language (C#, Python, Java) or be an XQuery module (presented by the processor using the proper package manifest structure). This is not a bug in the spec, but it can help readers to understand that a package is a more abstract concept. Cheers, Abel
Suggestion: Addition to the intro section in 2.7 Although this specification defines packages as constructs written using a defined XSLT syntax, implementations MAY provide mechanisms that allow packages to be written using other languages. Change the penult para of 2.7 to start "A package is defined *in XSLT* by....", then add the above para after it. Resolved to accept this wording.
Was this updated in the spec or was it snowed under by the other bug reports?
(In reply to Abel Braaksma from comment #2) > Was this updated in the spec or was it snowed under by the other bug reports? Reply to my own comment: the changes are visible in the current WD, search for this bug number to see the changes.