Re: “Packaging”

> I wonder: Why do we need such tool if we already have in XPath 3.1 the standard function
> fn:load-xquery-module -
> https://www.w3.org/TR/xpath-functions-31/#func-load-xquery-module

Mostly because I’m imagining a future where the package might be more
than a naked XQuery module. Suppose, for example, I wanted to make my
XInclude implementation into a package. I might like to ship that with
Java classes code that implements it in Saxon, perhaps C# classes that
implement it in SaxonCS, a different set of Java classes that implement
it in BaseX and eXist. And maybe an implementation that uses MarkLogic
extensions. Imagine all that bundled into a zip file with appropriate
metadata and manifests. Then a user can say “use that” and the
implementation can go look in there and say “hmm, okay, from this
manifest, it looks like I should load these classes, add these
namespaces and function declarations to the appropriate context, etc.”

                                        Be seeing you,
                                          norm

--
Norm Tovey-Walsh
Saxonica