- From: Erik Siegel <erik@xatapult.nl>
- Date: Sat, 9 Dec 2023 09:50:17 +0100
- To: <xproc-dev@w3.org>
Hi Wendell, In addition to what Gerrit writes: no maybes, it's *definitely* static-base-uri() you're looking for. I use it a lot when computing URIs (to schemas, data files and the likes) around my pipelines. So: select="resolve-uri('../xspec/', static-base-uri())) Erik > -----Original Message----- > From: Imsieke, Gerrit, le-tex <gerrit.imsieke@le-tex.de> > Sent: Saturday, 9 December 2023 00:38 > To: xproc-dev@w3.org > Subject: Re: Passing context in XProc 1.0 > > Hi Wendell, > > Maybe you want static-base-uri() instead of base-uri(.). > > Gerrit > > On 08.12.2023 23:30, Piez, Wendell A. (Fed) wrote: > > XProc Friends, > > > > In an XProc 1.0 pipeline, I have this: > > > > <p:with-param name="xspec-home" select="resolve-uri('../xspec/',base- > uri(.))"/> > > > > But this is not what I want. Apparently base-uri(.) is evaluated relative to the > source document being processed, or that’s what I am guessing. This works > sometimes but only by happenstance. > > > > I actually want to have the relative path here resolved with respect to the XProc > file (pipeline definition) or its directory. And relative to this one, not to another > pipeline that happens to import this one. > > > > Any tips? Is this easily done under XProc 1.0? Should I be thinking differently? > > > > Thanks for your assistance. I know it might be pretty basic – > > > > Regards, Wendell > >
Received on Saturday, 9 December 2023 08:50:37 UTC