Re: [xsl] xsl:package/xsl:expose?

[Wendell Piez <wapiez@xxxxxxxxxxxxxxx>]

I agree with Tony. This is the kind of thing that machines don't care
about, but people do. Which is why it's a hard aspect of design.

If the order of the elements is unconstrained, I expect Tony's way
will emerge as best practice. It is more convenient for users of the
package (won't we want to know first what's exposed?) even if it
doesn't reflect the logical (dare I say "procedural"?) order from the
developer's point of view.

Cheers, Wendell
Wendell Piez | http://www.wendellpiez.com
XML | XSLT | electronic publishing
Eat Your Vegetables
_____oo_________o_o___ooooo____ooooooo_^


On Tue, Nov 19, 2013 at 7:38 AM, Tony Graham <tgraham@xxxxxxxxxx> wrote:
> On Tue, November 19, 2013 12:23 pm, David Carlisle wrote:
>> On 19/11/2013 12:09, Tony Graham wrote:
>>> 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.
>>
>> although you need to add /xsl:package to the end anyway, it's not as if
>> you can just edit the top, admittedly it would be easier for an editor
>> to inject that at the end without actually requiring you to look, but
>> still..
>
> That's just a keystroke (Ctrl-E) or a right-click in Oxygen.  (No doubt
> there's similar a keystroke in PSGML that's now missing in nxml-mode.)
>
> Even though they don't have to, people tend to put their xsl:include at
> the top of the stylesheet, right after any xsl:import, for the sake of
> housekeeping.  My contention is that it would make for better housekeeping
> if xsl:expose was at the top, too.
>
> 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