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

Re: p:pipeline

From: Rui Lopes <rlopes@di.fc.ul.pt>
Date: Tue, 25 Jul 2006 18:06:31 +0100
Message-ID: <44C64F97.5050302@di.fc.ul.pt>
To: public-xml-processing-model-wg@w3.org
Norman Walsh wrote:
> / Rui Lopes <rlopes@di.fc.ul.pt> was heard to say:
> | I'm with Jenny on this one, I believe that component declarations
> | shouldn't occur inside a pipeline, but on a separate file (as in
> | configuration file).
> 
> That seems an unnecessary burden. I don't want to have to put each
> p:pipeline in a separate file, somehow I want to be able to combine
> them. Whether I do this by simply nesting or by adding a new wrapper
> is a separable question.

I agree. I want to be able to define two pipelines in the same file, as 
well as in separate files.

> Once I've got the ability to have two p:pipeline's in the same file, I
> want to be able to put a p:component-definition in that file too, so
> that I can define the three components I need (two pipelines and one
> extension component) in the same place.

For interoperability sake, I would prefer implementation-specific 
components to be defined elsewhere. Or, at least, if an extension 
component is defined but not used, an error isn't raised.


Cheers,
Rui

Received on Tuesday, 25 July 2006 17:06:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:21:48 GMT