W3C home > Mailing lists > Public > public-xml-processing-model-wg@w3.org > September 2007

Re: pipeline library

From: Norman Walsh <ndw@nwalsh.com>
Date: Fri, 21 Sep 2007 07:52:43 -0400
To: public-xml-processing-model-wg@w3.org
Message-ID: <m27imkz14k.fsf@nwalsh.com>
/ Rui Lopes <rlopes@di.fc.ul.pt> was heard to say:
| Adding this attribute to p:pipeline-library would allow for directly
| running pipeline libraries without specifying the initial pipeline to
| be run, a nice feature for self contained XProc-based applications and
| automation scripts (both XProc usages that must not be taken into
| account).
| This feature isn't cumbersome to implement, easy to understand from
| author's point of view, and has a minimal impact on the spec.
| I propose an attribute @default, as an NCName (in consonance with
| p:pipeline's @name), or QName (in consonance with p:pipeline's @type).
| To prevent ambiguity, if a pipeline library imports other libraries
| and if it defines its default pipeline, it will shadow all of the
| imported libraries' @default attributes.
| Thoughts?

I don't really understand. Where does the default come into play?
Whether you import a single pipeline or an entire library, the import
and the call are always separate steps:

  <p:import href="/some/URI"/>

What would hcange if the library at /some/URI declared default="default-pipe"?

                                        Be seeing you,

Norman Walsh <ndw@nwalsh.com> | What is familiar is what we are used
http://nwalsh.com/            | to; and what we are used to is most
                              | difficult to 'Know'--that is, to see as
                              | a problem; that is, to see as strange,
                              | as distant, as 'outside us'.-- Nietzsche

Received on Friday, 21 September 2007 11:52:56 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:32:44 UTC