|
From: Michael B. <Mic...@Al...> - 2002-03-01 19:12:05
|
Cool! This proposal looks pretty good to me, although there are some fuzzy areas. One thing I wasn't clear on is if I can parameterize all of the inputs and outputs. It uses URIs for these and the only thing that seems to be passed in from the application context is the target. (Or at least that's what the note says, though in looking at the examples, it didn't seem evident to me that the target was really an external parameter.) I'd like to have something like this where the pipeline def is a model that does not specify hard-coded paths (except perhaps for temporary intermediate files), and lets me specify the concrete inputs and target at runtime, not just the target. It doesn't seem to permit that in its current formulation, unless I've misread it. -----Original Message----- From: Sean McGrath To: Michael Brennan; xpi...@li... Sent: 3/1/02 2:56 AM Subject: Re: [Xpipe-developers] FW: [xml-dev] Check out the pipeline submission Michael, The company I work for, Propylon, are involved with this W3C submission and I hope to be able to get involved in whatever W3C activities come from it. http://www.w3.org/Submission/2002/01/Comment Sean |