- From: Wendell Piez <wapiez@wendellpiez.com>
- Date: Wed, 2 Jul 2025 13:25:20 -0400
- To: XProc Dev <xproc-dev@w3.org>
- Message-ID: <CAAO_-xxvHs17=q0PaFjfYCT=Du4sE70wPdiX_589Xe9RCBbViQ@mail.gmail.com>
Hello XProc people, Probably I am not the only one who can tell from "side effects" when the committee has been busy at work updating and improving things. For example, recently a pipeline of mine broke ... apparently because relevant pieces of the specs in the 3.0-steps repository now use XInclude. No problem, XProc can do XInclude. But I tried, and this does not work: <p:declare-step xmlns:p="http://www.w3.org/ns/xproc" version="3.0"> <p:output/> <p:load href=" https://raw.githubusercontent.com/xproc/3.0-steps/master/step-text/src/main/xml/specification.xml " content-type="application/xml"/> <p:xinclude/> </p:declare-step> This returns an error in both XML Calabash and Morgana IIIse. It returns a different error related to the same cause if you leave 'content-type="application/xml"' from the p:load. (I blame Github.) What is up with this? Is there any way to read the raw XML off Github, as XML? If not, are there alternative pathways -- short of cloning the repository and reading via file: not http: ? i.e. alternative all-XProc approaches to reading the specs dynamically in place. Thanks for any insights, Wendell -- ...Wendell Piez... ...wendell -at- nist -dot- gov... ...wendellpiez.com... ...pellucidliterature.org... ...pausepress.org... ...github.com/wendellpiez... ...gitlab.coko.foundation/wendell...
Received on Wednesday, 2 July 2025 17:25:38 UTC