W3C home > Mailing lists > Public > public-qt-comments@w3.org > February 2016

[Bug 29460] New: External (non-XSLT) packages

From: <bugzilla@jessica.w3.org>
Date: Mon, 15 Feb 2016 09:36:10 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29460-523@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29460

            Bug ID: 29460
           Summary: External (non-XSLT) packages
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          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
  Target Milestone: ---

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

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 15 February 2016 09:36:13 UTC

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