[iRail] APIv1.1

[Christophe Versieux]

Dear mailing list,

As you know , the MIVB didn't want to share his data with us and I am 
therefore planning to add these informations to my current application.

I think that feature may start a bigger war than with the NMBS. They 
seem to be faster to react, and I think eMich will see us a threat for 
his application (eMich, if you are on the mailing list, feel free to 
send us your opinion).

I would like to have your opinion on this point, should we begin to code 
applications or is it time to think a little bit before, and maybe try 
to contact them?

Yeri, Pieter, I was not there at the meeting you had with their staff, 
so I don't know their feelings for us.

Kind regards

Christophe


> 	Pieter Colpaert <mailto:pieter.colpaert at gmail.com>
> 8 mars 2011 19:44
>
>
> Dear Communitah,
>
> I have been writing code; In fact I've rewritten the entire stack behind
> the iRail API. The code now is extensible for inputs (can handle
> different companies) and is extensible for outputs (you can add your own
> outputmethod in no time.). Supported output methods at this time: json,
> jsonp and xml. Supported inputs are: NMBS and I'm working on MIVB. De
> Lijn is coming soon as well.
>
> The new API code needs to be tested on http://dev.api.irail.be
>
> PLEASE TEST YOUR APPS ON THIS API AND FILL IN THIS DOODLE:
> http://www.doodle.com/3bschxxv9z6k9vp3
>
> Changelog:
> ----------
>
> * add «&system=company» to your request to get the API responses for
> other companies. Default remains NMBS (STIB won't work at this moment,
> you'll have to use the Flemish name MIVB. If you don't like this, feel
> free to hack this in)
>
> * MIVB status: liveboard and stations kind of work
>
> * the liveboard call for the NMBS will return the information for the
> next hour. This was not like this by default until now.
>
> Additions to the json:
> * stationinfo: in each call this will contain more information about a
> station
> * platforminfo: more information about the station
> * the Liveboard bug if only 1 train arriving for json has been fixed
> * the array bug in json has been fixed
>
> Next steps:
> * End of the week I want to see this new API code go public
> * After next week APIv1.1 will be frozen and will get the "stable" flag
> * I'll start coding APIv2.0 and ask feedback on specification
> * MIVB will get coded in meantime
>
> Pieter
> ------------------------------------------------------------------------

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/irail/attachments/20110406/4d6fab8b/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: compose-unknown-contact.jpg
Type: image/jpeg
Size: 1421 bytes
Desc: not available
URL: <http://lists.okfn.org/pipermail/irail/attachments/20110406/4d6fab8b/attachment-0002.jpg>