- From: Jeni Tennison <jeni@jenitennison.com>
- Date: Tue, 25 Jul 2006 21:52:30 +0100
- To: public-xml-processing-model-wg@w3.org
Norm 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). I should clarify: I think that it *ought*to*be*possible* to put component declarations in a separate file that you import into multiple pipeline files, not that it ought to be mandated. > 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. > > 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. I'm with Norm :) Cheers, Jeni -- Jeni Tennison http://www.jenitennison.com
Received on Wednesday, 26 July 2006 08:04:45 UTC