xsl:package/xsl:expose?

Is it just me that thinks 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.

(Yes, element folding in a XML editor is a wonderful thing -- right up
until you also want to see the documentation or implementation of one of
the exposed items -- and having a single buffer open in multiple windows
in Emacs is common, but why should any of that be necessary?)

I would like to be persuaded that it's sane and rational.  Actually, I'd
like to file a bug about it on the W3C Bugzilla [3], but that wouldn't be
much use unless it's generally seen as a problem, hence this email.

Regards,


Tony Graham                                   tgraham@xxxxxxxxxx
Consultant                                 http://www.mentea.net
Mentea       13 Kelly's Bay Beach, Skerries, Co. Dublin, Ireland
 --  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --
    XML, XSL-FO and XSLT consulting, training and programming
       Chair, Print and Page Layout Community Group @ W3C

[1] http://www.w3.org/TR/xslt-30/#packages
[2]
https://github.com/MenteaXML/xslt3testbed/blob/master/xsl/xhtml-tables-fo.xsl
[3] http://www.w3.org/XML/2005/04/qt-bugzilla