Re: [xsl] Re: Over the years, have you created an XSLT library?

["Wendell Piez wapiez@xxxxxxxxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>]

Alan, thanks for mentioning FunctX. Its example shows that a good library
is useful not only as a toolbox, but also a reference work. (A 'library'?)

Didn't someone also mention Joel K's excellent library? There is also
Transpect (Gerrit and co), Erik Siegel's xtpxlib (XProc with lots of XSLT)
and others, to say nothing of things on the boundaries of 'library' such as
XSLT applications (XSweet comes to mind), oXygen frameworks etc. etc.

My own response to the question was somewhat like Vincent's - to note how
libraries are 'fractal' - part of the design problem, in that they are
addressed to dealing with problems at different levels of 'semantic
granularity', and accordingly they are not always generalized or meant to
be generalized.

At one extreme we have the functions that might eventually belong in the
specs (such as the Saxon extension libraries), while on the other we have
things like the round-time-to-the-half-hour code I was writing yesterday -
shouldn't that be in a library?

Also there are other reasons to make libraries besides code reuse.

Almost any non-trivial XSLT application will have a library of some sort,
even if bolted on and bespoke.

But is this different from other language ecosystems? I guess there is a
difference in the way we use and deploy 'libraries' or even conceive of
them.

Cheers, Wendell


On Thu, Mar 6, 2025 at 2:16b/AM Alan Painter alan.painter@xxxxxxxxx <
xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:

> Pardon me if I missed it being mentioned already, but I haven't seen any
> mention of functx, Priscilla Walmsley's venerable library of xpath
> functions.  I regularly refer to it for inspiration. I've even made a
> monetary contribution to its maintenance.
>
> https://www.datypic.com/xsl/
>
> Functx is the poetry of xpath functions. All libraries should be so useful
> and harmonious.
>
> On Thu, Mar 6, 2025, 00:45 Martin Honnen martin.honnen@xxxxxx <
> xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:
>
>>
>> On 06/03/2025 00:31, Lizzi, Vincent vincent.lizzi@xxxxxxxxxxxxxxxxxxxx
>> wrote:
>> > Seeing as XSLT 4.0 is in development now, is it possible to consider
>> > adding an option to xsl:next-match that could enable passing along all
>> > parameters? This option might take the form of a new optional
>> > attribute on xsl:next-match named with-all-params that takes a yes/no
>> > (or Boolean) value and defaults to no (false). If this suggestion
>> > seems worthwhile, what would be the correct way to submit this
>> > suggestion for consideration?
>>
>>
>> Development has started long ago so it would be better you would have
>> already submitted your suggestion as an issue at
>> https://github.com/qt4cg/qtspecs/issues. But work is still going on so
>> of course you can still give it a try, I think.
>>
>>
>> XSL-List info and archive <http://www.mulberrytech.com/xsl/xsl-list>
> EasyUnsubscribe <http://lists.mulberrytech.com/unsub/xsl-list/174322> (by
> email <>)
>


--
...Wendell Piez... ...wendell -at- nist -dot- gov...
...wendellpiez.com... ...pellucidliterature.org... ...pausepress.org...
...github.com/wendellpiez... ...gitlab.coko.foundation/wendell...