- From: Hans Hübner <hans.huebner@lambdawerk.com>
- Date: Fri, 22 Sep 2017 11:35:56 +0200
- To: Norman Walsh <ndw@nwalsh.com>
- Cc: XProc Dev <xproc-dev@w3.org>
- Message-ID: <CAAArA2Y-7bZh-omAdUbak92QEHcBDdwVOMqe7kxhB+DprCp3-w@mail.gmail.com>
Using XPaths into the original pipeline source will not work for implicit connections. It might be possible to specify an intermediate (static) XML model, with implicit connections expanded, as being the context in which locator XPaths are evaluated. On Fri, Sep 22, 2017 at 11:06 AM, Norman Walsh <ndw@nwalsh.com> wrote: > Achim Berndzen <achim.berndzen@xml-project.com> writes: > > Yes, I completely agree with you that we also have to deal with > > pipeline calls (I am not sure about dynamic pipeline with p:eval). For > > called pipelines the locator expression is a bit more complex, but I > > think we could do something with > > > > /p:declare-step/foo:caller[1]/p:declare-step/.... or > > /p:declare-step/foo:caller[1]/p:library/p:declare-step .... > > Like I said yesterday, I don’t really like the idea of using XPath > expressions over the original pipeline source as the locator > mechanism. But even if we do, I think it would be a mistake to “reach > through” the call to a step. > > I suppose it might be possible to have different traces in different > calls, but I wouldn’t swear to it. > > Be seeing you, > norm > > -- > Norman Walsh > Lead Engineer > MarkLogic Corporation > Phone: +1 512 761 6676 > www.marklogic.com > -- LambdaWerk GmbH Oranienburger Straße 87/89 10178 Berlin Phone: +49 30 555 7335 0 Fax: +49 30 555 7335 99 HRB 169991 B Amtsgericht Charlottenburg USt-ID: DE301399951 Geschäftsführer: Hans Hübner http://lambdawerk.com/
Received on Friday, 22 September 2017 09:36:40 UTC