- From: Alexander Witzigmann <alexander.witzigmann@tanner.de>
- Date: Tue, 16 Jun 2009 08:49:53 +0200
- To: "xproc-dev@w3.org" <xproc-dev@w3.org>
good overview to show the intention and spirit of a pipeline. all problems in the domain of information processing / transformation (information centric problems) are tend to be complex if you look at them as a monolith operation. the trick is to split the problem into smaller, semantically complete steps of sub-problems needs to be solved. if you compare a technical pipeline with a assembly line in production you see the trick. transform a stream of data with short and less complex steps. we does provide much benefit for human works in some cases but it provides much benefit for automatic steps either in assembly lines as well as in technical pipelines working on information flows. alex http://trent-intovalue.blogspot.com/ Costello, Roger L. schrieb: > Hi Folks, > > I want to get a high-level understanding of pipelines, their value, and their niche in the world. > > Why do people rave about Unix pipelines? What made them so excellent? > > Will people rave about XProc pipelines? Do XProc pipelines have the same qualities as Unix pipelines? What are those qualities? > > When is it better to use pipelines than imperative (procedural) code? > > What's the Zen of pipelines? > > Are there books on pipelines, which discusses pipelines from a high-level perspective? > > /Roger
Received on Tuesday, 16 June 2009 12:17:08 UTC