Package loading

We dropped the XQuery Invocation Feature through bug 29251 (its changes have not been logged, I reported that as an editorial bug here: https://www.w3.org/Bugs/Public/show_bug.cgi?id=29375).

We know that how a package is located and presented is implementation defined. It can be a compiled package etc, etc. However, I think it makes sense to add a little Note somewhere that strongly suggests that an implementation is free to offer a package written in any language. The way we currently describe it seems to suggest that only a package with xsl:package is allowed, but a package can just as well be written in a different language (C#, Python, Java) or be an XQuery module (presented by the processor using the proper package manifest structure).

This is not a bug in the spec, but it can help readers to understand that a package is a more abstract concept.

Cheers,
Abel 

Received on Thursday, 14 January 2016 12:25:43 UTC