W3C home > Mailing lists > Public > xproc-dev@w3.org > October 2011

Re: XProc Usability (was Re: New to Xproc Question : conditionnal "output port" definition?)

From: Alex Muir <alex.g.muir@gmail.com>
Date: Wed, 12 Oct 2011 16:26:03 +0000
Message-ID: <CAFtPEJbn3saPQAGkOTJmJuEVrJORpxfC_PAJ=mUcjnwKtnmOWg@mail.gmail.com>
To: Norman Walsh <ndw@nwalsh.com>
Cc: XProc Dev <xproc-dev@w3.org>
I wonder were the coder responsible to specify to save a document in
memory to be accessed later on in the process it could it make
implementing the program such as developing calabash much easier
because you wouldn't be required to determine when something needs to
be saved in memory for use later on because a pipe is requesting
output from another step?

So you could have some <p:put  id="fish"> when  <p:get name="fish> or
<p:put-many... get-many to create or iterate on a collection. clearly
that concept could be expanded upon

Also there is something complex about input/results and ports that
probably could be simplified. Does a developer really want to be
bothered with a message that you need to specify your result
differently somehow somewhere in the document... (been a while so I'm
not being specific here) But really for the most part I tend to think
what is coming out of the last step or what I specify to save in some
location is what is specifying the result of a pipeline not some
declaration at the top of the document for example..

Alex Muir
Instructor | Program Organizer - University Technology Student Work
Experience Building
University of the Gambia

Low budget software development benefiting development in the Gambia,
West Africa
Experience of a lifetime, come to Gambia and Join UTSWEB -
Received on Wednesday, 12 October 2011 16:26:39 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:03:09 UTC