W3C home > Mailing lists > Public > xproc-dev@w3.org > August 2013

Re: New step: wait for input

From: James Fuller <jim@webcomposite.com>
Date: Tue, 6 Aug 2013 08:50:22 +0200
Message-ID: <CAEaz5mu-DH1R0hh-np4fjxZ53J5T5+PbAo6MxNvkmhJzFEQSyg@mail.gmail.com>
To: Norman Walsh <ndw@nwalsh.com>
Cc: XProc Dev <xproc-dev@w3.org>
On 5 August 2013 18:38, Norman Walsh <ndw@nwalsh.com> wrote:
> Ari's Balisage symposium talk highlights the need for a step that will wait
> for user input. I wonder if
>
>   <p:wait-for-update href="someURI"/>

and at xprocathon did we not have someone ask for a wait-for-input ?

how far would we go, eg. should we consider a compound step as in the
example below ?

<p:wait>
  <p:xpath-context/>
  <p:variable/>
  <p:option name="check-every"/>
  <p:option name="timeout"/>
  <p:when test="">
   <! sub pipeline //>
  </p:when>
  <p:otherwise>
   <! sub pipeline //>
  </p:otherwise>
</p:wait>

this would generalize the step but unsure how we would handle
detecting state change.

J

> would do the trick. The proposed semantics are that it waits until someURI has
> changed. For file: URIs, this is obvious, but I think it could be made to work
> for HTTP URIs as well, at least those where the server returns a last-modified
> or etag header.
>
>                                         Be seeing you,
>                                           norm
>
> --
> Norman Walsh
> Lead Engineer
> MarkLogic Corporation
> Phone: +1 512 761 6676
> www.marklogic.com
Received on Tuesday, 6 August 2013 06:50:50 UTC

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