W3C home > Mailing lists > Public > xproc-dev@w3.org > May 2009

Re: Immediate Market Needs for XProc

From: Kurt Cagle <kurt.cagle@gmail.com>
Date: Sat, 9 May 2009 19:18:27 -0700
Message-ID: <6fa681b10905091918m2cb680faj7d4c7986066efa01@mail.gmail.com>
To: "Costello, Roger L." <costello@mitre.org>
Cc: "xproc-dev@w3.org" <xproc-dev@w3.org>
This might also be a little controversial, but what about human workflow
steps? Something like a <p:wait/> or <p:user-input/> step that will hold the
processor in a holding pattern until some kind of response is received. I
could see this especially in a setup that generates an XForms for input.

Kurt Cagle
Managing Editor
http://xmlToday.org


On Sat, May 9, 2009 at 4:12 PM, Costello, Roger L. <costello@mitre.org>wrote:

>
> Hi Leif,
>
> > I've been working on an XProc GUI using WireIt [1].
>
> Great! I'm eager to see it when you have it ready.
>
> > Is the configuration management tool similiar
> > to a version control system
> > (i.e. git, svn, etc)?
>
> Yes, that's what I was thinking.
>
> > I was thinking it would be nice to have a central directory of XProc
> > libraries that encapsulate web service APIs.  Yahoo recently put a
> > user-contributable directory of web service wrappers up on github for use
> > from YQL [2].  They specify the URL and input parameters (required or
> > optional), but don't seem to say much about the output of the web
> services
> > (arguably much more complicated).
>
> > Maybe say, I'd want a bus arrival step (that encapsulates my transit
> service
> > api), and later on some info from that could go into a mapping step...
>
> Great idea!
>
> /Roger
>
> > [1] http://javascript.neyric.com/wireit/
> > [2]
>
> http://www.javarants.com/2009/02/05/yql-opens-up-3rd-party-web-service-table-definitions-to-developers/
>
> > -Leif Warner
>
Received on Sunday, 10 May 2009 02:19:13 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 10 May 2009 02:19:14 GMT