- From: Eric Stephan <ericphb@gmail.com>
- Date: Tue, 3 May 2016 15:54:49 -0700
- To: Newton Calegari <newton@nic.br>
- Cc: Annette Greiner <amgreiner@lbl.gov>, Public DWBP WG <public-dwbp-wg@w3.org>
Received on Tuesday, 3 May 2016 22:55:16 UTC
Newton, Sorry I hit the send button to early: :-) I am wondering just to make the API a bit more complex if we could add a status Bus status {root}/bus/status bus_id In this case status could represent something like "on-schedule", "out-of-service", "delay" Eric S On Tue, May 3, 2016 at 3:52 PM, Eric Stephan <ericphb@gmail.com> wrote: > Newton this looks great. > > I am wondering just to make the API a bit more complex if we could add a > status > > Bus status {root}/bus/status > > On Tue, May 3, 2016 at 2:59 PM, Newton Calegari <newton@nic.br> wrote: > >> Hi Annette and Eric, >> >> I made some small changes on the real-time example page [1] in order to >> adapt the example to the case we talked yesterday. >> >> Could you please take a look on it and, if necessary, suggest some >> improvements? >> >> Cheers, >> >> Newton >> >> [1] http://w3c.github.io/dwbp/dwbp-realtime-example.html >> >> >
Received on Tuesday, 3 May 2016 22:55:16 UTC