W3C home > Mailing lists > Public > xproc-dev@w3.org > December 2008

Re: p:pipeinfo

From: Norman Walsh <ndw@nwalsh.com>
Date: Fri, 19 Dec 2008 15:42:02 -0500
To: XProc Dev <xproc-dev@w3.org>
Message-ID: <m2wsdv7v8l.fsf@nwalsh.com>
"Dave Pawson" <dave.pawson@gmail.com> writes:

> Being implementation dependent, are there any examples of this yet?

Nope.

I almost created one but then decided that what I really wanted was a
set of pipeline options.

> 3.7 is a bit vague, just looking for examples please.

Here's a hypothetical example:

<p:pipeline ...>

  <p:pipeinfo>
    <cc:xproc-config xmlns:cc="http://xmlcalabash.com/ns/configuration">
      <cc:entity-resolver class-name="org.xmlresolver.Resolver"/> 
      <cc:uri-resolver class-name="org.xmlresolver.Resolver"/>
   </cc:xproc-config>
   <cx:catalog href="/path/t/catalog.xml"/>
  </p:pipeinfo>

  ...
</p:pipeline>

</cc:xproc-config>

Calabash could look for configuration options or catalog pointers
inside a p:pipeinfo.

But it doesn't today and I'm not strongly motivated to work on 
that :-)

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | No one gossips about other people's
http://nwalsh.com/            | secret virtues.--Bertrand Russell

Received on Friday, 19 December 2008 20:42:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 19 December 2008 20:42:43 GMT