Return-Path: 
 <cocoon-dev-return-23501-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 94241 invoked by uid 500); 1 Mar 2002 08:44:26 -0000
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:cocoon-dev-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-dev-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-dev@xml.apache.org>
Reply-To: cocoon-dev@xml.apache.org
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 94229 invoked from network); 1 Mar 2002 08:44:26 -0000
Message-Id: <200203010844.g218iY123766@hercules.home>
X-Mailer: exmh 2.5 10/15/1999 with XEmacs 21.4.6 on Linux 2.4.8-34.1mdk
From: Ovidiu Predescu <ovidiu@webweavertech.com>
To: "Nicola Ken Barozzi" <barozzi@nicolaken.com>
Cc: cocoon-dev@xml.apache.org
Subject: Re: XML Pipeline Definition Language Version 1.0 
In-Reply-To: Your message of "Fri, 01 Mar 2002 09:07:45 +0100."
             <01ce01c1c0f8$2beded40$670004c0@PC103>
X-Url: http://www.geocities.com/SiliconValley/Monitor/7464/
X-Image-Url: http://www.geocities.com/SiliconValley/Monitor/7464/ovidiu.tiff
X-Face: 
 ?(@Y~qjBA}~8ZMh5gM4{Q{bE_*:sCJ3@Z?{B*Co=J!#8bb~-z?-0._vJjt~MM59!MjxG%>U
 5>MW^2-\7~z04buszR^=m^U|m66>FdR@cFwhb;.A(8*D.QmLkK]z,md0'HiOE\pyeiv_PACR+P:Cm.
 wq_%l':E:q]g-UCc>r&s@BVo'kFN;(\9PF22Myg5w%nUBWQ6MJJ#qL#w>2oxckP'H:\$9F"mxsz]Dg
 k{1`fTcP'Y$CgGnc^paTV$dzhVX<SVN1RPb="gz3>+;(U$;Eb)P<>G)g)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 01 Mar 2002 00:44:33 -0800
Sender: ovidiu@webweavertech.com
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

On Fri, 1 Mar 2002 09:07:45 +0100, "Nicola Ken Barozzi" <barozzi@nicolaken.com> wrote:

> <fyi url="http://www.w3.org/TR/xml-pipeline/">
> 
> XML Pipeline Definition Language Version 1.0
> W3C Note 28 February 2002
> 
> Editors:
> Norman Walsh, Sun Microsystems, Inc. <Norman.Walsh@Sun.COM>
> Eve Maler, Sun Microsystems, Inc. <Eve.Maler@Sun.COM>
> 
> The W3C has released XML Pipeline Definition Language, which describes "the
> processing relationships between XML resources" as a Note.
> 
> Pipelining has been a popular term lately in XML discussions, with
> initiatives like XPipe and DSDL building models for how to pass XML between
> different kinds of processing. The Note focuses on particular set of issues
> managed by a single controller:
> "A pipeline document specifies the inputs and outputs to XML processes and a
> pipeline controller uses this document to figure out the chain of processing
> that must be executed in order to get a particular result."
> 
> </fyi>

The language seems to be heavily influenced by Ant, and although is
not explicitly stated, a pipeline processor that implements the
language can do lots of optimizations to parallelize the computations.

No mention of how the components in the pipeline interact with each
other. The output of a processing is specified as a file name, but
nothing stops the engine to connect the ends of intermediate pipelines
using the same mechanisms as in the internal pipelines.

I bet the prototype implementation (there is one isn't it?) written by
Norman is based on Ant.

Cheers,
-- 
Ovidiu Predescu <ovidiu@cup.hp.com>
http://www.geocities.com/SiliconValley/Monitor/7464/ (GNU, Emacs, other stuff)

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org