RE: What is the mental model of XProc?

> I don't see a contradiction between
> 
>    "streams of XML flowing through steps"
> and
>   "dividing problems into bite-sized chunks"

What I meant is: 

    XProc is not about creating subroutines 
    that are invoked with arguments. 

This weekend I caught myself falling back into old programming habits of creating subroutines. I was trying to do FORTRAN in XProc.

I am trying to learn how to write good XProc pipelines. But what is a good XProc pipeline? What are the characteristics of good XProc pipelines? 

What do you think?

/Roger 



> -----Original Message-----
> From: David A. Lee [mailto:dlee@calldei.com] 
> Sent: Sunday, June 14, 2009 12:02 PM
> To: Costello, Roger L.
> Cc: 'xproc-dev@w3.org'
> Subject: Re: What is the mental model of XProc?
> 
> I dont see a contradiction between
> 
> 
>    "streams of XML flowing through steps"
> and
>   "dividing problems into bite-sized chunks"
> 
> 
> 
> 
> 
> David A. Lee
> dlee@calldei.com  
> http://www.calldei.com
> http://www.xmlsh.org
> 812-482-5224
> 
> 
> 
> Costello, Roger L. wrote:
> > Hi Folks,
> >
> > What is XProc's mental model?
> >
> > Here's what I think it is:
> >
> >    The mental model of XProc is streams
> >    of XML flowing through steps which
> >    operate on the XML.
> >
> > What seems clear to me is that XProc is not about dividing 
> problems into bite-sized chunks (steps) so as to invoke the 
> chunks - passing arguments and getting results - in a 
> specific order to implement some algorithm. XProc is not 
> about writing procedural code.
> >
> > Does an XProc pipeline have a goal? Should a pipeline have a goal?
> >
> > ... XProc is streams of XML ... Do streams have goals?
> >
> > What do you think?
> >
> > /Roger
>

Received on Sunday, 14 June 2009 20:44:08 UTC