Re: XProc and iXML

To make sure we are all on the same page, we are describing the last few comments on this GitHub issue still, correct?

https://github.com/ndw/xmlcalabash1/issues/335

________________________________
From: Piez, Wendell A. (Fed) <wendell.piez@nist.gov>
Sent: Monday, February 5, 2024 10:38 AM
To: Piez, Wendell A. (Fed) <wendell.piez@nist.gov>; Norm Tovey-Walsh <ndw@nwalsh.com>
Cc: Stein, A.J. Mr. (Fed) <alexander.stein@nist.gov>; xproc-dev@w3.org <xproc-dev@w3.org>
Subject: RE: XProc and iXML

Wait! I see Martin actually (and characteristically) gave more syntax, which I skipped past too quickly.

Wiring up the config is a question but between these I may be able to stitch something?

Meanwhile my questions still stand --

Thanks, Wendell

-----Original Message-----
From: Piez, Wendell A. (Fed) <wendell.piez@nist.gov>
Sent: Monday, February 5, 2024 10:33 AM
To: Norm Tovey-Walsh <ndw@nwalsh.com>
Cc: Stein, A.J. Mr. (Fed) <alexander.stein@nist.gov>; xproc-dev@w3.org
Subject: RE: XProc and iXML

Hi Norm, Martin and group,

If this has turned into a Saxon or XML Calabash question feel free to send me off. Thanks for the hints so far!

On the Saxon documentation page for XSLT configuration https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.saxonica.com%2Fdocumentation12%2Findex.html%23!configuration%2Fconfiguration-file%2Fconfig-xslt&data=05%7C02%7Calexander.stein%40nist.gov%7C208b2cc2c5f2490d68c408dc26608938%7C2ab5d82fd8fa4797a93e054655c61dec%7C0%7C0%7C638427443259956693%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=wqZdDW2NRnhJiD9vApyLpd966KMuV%2Bkb%2BkjkGJzEI5I%3D&reserved=0<https://www.saxonica.com/documentation12/index.html#!configuration/configuration-file/config-xslt> some features are indeed marked as "Applies to HE" - so I guess there is hope.

But apologies for being dense, while I see an "xslt/extensionElement" element for binding extension elements (instructions), there is nothing evident for binding extension functions. (Maybe I need an example - I've also looked at the 'global` element.) And in any case those are PE/EE features and won't work under my 'unencumbered use of standard features' requirement....

Put that way I know this might be a bit of a tall order. Nevertheless I'd be grateful for any more advice or guidance. (This does work fine under Saxon-HE when I can call the initializer.) I'm a little hesitant to ask the Saxon list for a how-do-you-avoid-buying-Saxon question 😊 -- even if my users are arguably next year's Saxon customers....

Thanks, Wendell

-----Original Message-----
From: Norm Tovey-Walsh <ndw@nwalsh.com>
Sent: Monday, February 5, 2024 9:44 AM
To: Piez, Wendell A. (Fed) <wendell.piez@nist.gov>
Cc: Stein, A.J. Mr. (Fed) <alexander.stein@nist.gov>; xproc-dev@w3.org
Subject: Re: XProc and iXML

> There is one thing I can’t get working yet, however, under XML
> Calabash using Saxon-HE, namely configure Saxon’s extension
> functionality to use Norm’s CoffeeSacks XSLT extension. (Saxon-HE is extensible only by means of an initialization called either programmatically or via an -init flag).

I thought there was a flag for that, or an XML Calabash configuration option (I’d have *sworn*…), but I went looking the other day on behalf of someone else and I couldn’t find it.

I’ll try to sort that out in the near future.

In the meantime, I think Martin’s proposal to do it in the *Saxon* configuration file will work. Just put the names of the classes that implement the functions in there:

  org.nineml.coffeesacks.LoadGrammar
  org.nineml.coffeesacks.MakeParser
  org.nineml.coffeesacks.HygieneReportFunction

                                        Be seeing you,
                                          norm

--
Norm Tovey-Walsh <ndw@nwalsh.com>
https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fnorm.tovey-walsh.com%2F&data=05%7C02%7Calexander.stein%40nist.gov%7C208b2cc2c5f2490d68c408dc26608938%7C2ab5d82fd8fa4797a93e054655c61dec%7C0%7C0%7C638427443259964580%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=2gP0umqH%2FP19C66vt%2FRBvf7geIWCXoAhWKLPqch5DpE%3D&reserved=0<https://norm.tovey-walsh.com/>

> One must not confuse scientific fact with scientific misconception.
> They're more or less opposites, of course. But a scientific
> misconception, if widely believed, creates a kind of truth of its own.
> This doesn't seem to make sense, but it's true.--Adam Felber