- From: <bugzilla@jessica.w3.org>
- Date: Sat, 30 Nov 2013 11:43:01 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23944 Bug ID: 23944 Summary: xsl:package/xsl:expose position Product: XPath / XQuery / XSLT Version: Working drafts Hardware: All OS: All Status: NEW Severity: normal Priority: P2 Component: XSLT 3.0 Assignee: mike@saxonica.com Reporter: tgraham@mentea.net QA Contact: public-qt-comments@w3.org See http://www.biglist.com/lists/lists.mulberrytech.com/xsl-list/archives/201311/msg00107.html and following messages in thread. I find it odd that in the XSLT 3.0 xsl:package [1] element, the stylesheet comes between the definitions of what the package needs and what the package provides: (xsl:use-package*, (xsl:stylesheet | xsl:transform), xsl:expose*) If I had a working implementation of xsl:package, the first thing I would package is an existing 557-line module [2]. To have to jump between the top and the bottom of the file when packagising it seems like unnecessary work compared to allowing xsl:expose before the stylesheet. For a new user of an existing package, having to jump between the top and bottom of the package when working out what's needed for and what's provided in the package also seems to me to require unnecessary effort. [1] http://www.w3.org/TR/xslt-30/#packages [2] https://github.com/MenteaXML/xslt3testbed/blob/master/xsl/xhtml-tables-fo.xsl -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Saturday, 30 November 2013 11:43:02 UTC