W3C home > Mailing lists > Public > xproc-dev@w3.org > October 2010

Re: Simplifying a series of simple p:xslt steps

From: Will McCutchen <mccutchen@gmail.com>
Date: Tue, 12 Oct 2010 10:51:15 -0500
Message-ID: <AANLkTikb966da7jOV3EPhZLSH8=y=oQhXp2yirbYSOFr@mail.gmail.com>
To: Philip Fennell <Philip.Fennell@marklogic.com>
Cc: "xproc-dev@w3.org" <xproc-dev@w3.org>

On Tue, Oct 12, 2010 at 1:52 AM, Philip Fennell
<Philip.Fennell@marklogic.com> wrote:
> If you are desperate to simplify this then you can declare your own
> pipeline step that encapsulates the p:xslt step. If all it is that
> changes is the URL of the XSLT document then make that the single
> option in your step. The down side to this is that because you
> cannot parameterise the href attribute on the p:document instruction
> you will need to use a p:load in your step in order to bring the
> referenced transform into the pipeline. You'd end up with a sequence
> of one line steps in you pipeline plus a reference to the library
> module that your step declaration exists in.

Would you mind elaborating on that?  I've been unable to figure out
how to put it together myself... I'm a little overwhelmed by XProc, at
the moment.  The solution you describe sounds like the exact solution
I was hoping would be possible. A sequence of one line steps would be
ideal for my use case.

> That'd 'simplify' the appearance of the pipeline but obfuscate
> what's going.

I think I'm fine with that tradeoff.  This simplification is for the
benefit of some end users who are a little uncomfortable making
changes to these unfamiliar XML files.

Thanks so much,
- Hide quoted text -

Will McCutchen.
Received on Tuesday, 12 October 2010 15:51:50 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:03:07 UTC