The Open Transport initiative has made some great progress so far. With a range of different transport and data specialists providing feedback on our draft API specifications until the peer review period closed recently. It therefore looks like we will be able to create a first complete version of our API specifications as-planned for the …
Continue reading “Planning our Open Standard “version 1” launch”
ABT is the acronym for Account Based Ticketing (or Account Based Travel, to give it a more appropriate name). This is the concept where customers use a central “back office” account for transport, rather than buy individual tickets in advance. This account allows either pre-pay functionality (where the customer adds funds to the account beforehand …
Yesterday, Friday 20th December, was the final date that was set for feedback and questions of our two different draft API specifications. customer-accountCustomer API for open-transport standard operator-infoCentral look-up / directory for referencing operator API locations, including “customer-account” resources We are now finalising version 1 (v1) in preparation for its launch on Friday 3rd January 20200. …
Hayden has written an update on the recent progress of the Open Transport initiative. This is available here:https://www.linkedin.com/pulse/open-transport-update-december-2019-hayden-sutherland/
As well as releasing a “customer-account” API specification (for the consistent integration of purchase, usage and concession transport data), we have also published an “operator-info” specification too. This “operator-info” is our design for a central transport look-up for both validating key mobility data and providing references to each transport operator’s account APIs, including participating “customer-account” …
Continue reading “Further uses for the “operator-info” look-up service”
We have now created a Twitter account, for better engagement on Social Media with those who are interested in transport, mobility, open standards and account interoperability. https://twitter.com/opentransport1
Transport & mobility data belongs to the account owner. So why shouldn’t they have quick and convenient access to all their transport account data in the way that they want? This may seem like a bold claim, especially when so many transport providers are looking to leverage their customer data and monetise their digital platforms. …
Continue reading “Account data sharing principles & entities”
The integration of different transport accounts owned by the same person (e.g. their rail, subway and electric scooter accounts) is certainly a technical challenge. But one that the Open Transport initiative believe can be overcome, especially if common standards such as open APIs are used. But technology isn’t the only barrier to overcome. Complete transport …
A person’s journey (e.g. making their regular commute to work) does not start and end when they board and get off a bus or train. For most travellers there is also additional travel taking place (e.g. when they leave the house to get to the stop or station and when they continie their onwards journey …
Continue reading “Helping to piece together end-to-end journeys”
We have been asked what our timescales are around delivering an Open Standard, so we thought we would be completely transparent about our aims here. Note: The current work to create both API specifications (‘customer-account’ and ‘operator-info’) are the intellectual property of Ideal Interface. This will change when version 1.0 of the Open Standard is …
Continue reading “Deliverables & timescales to create an initial Open Standard”
Open Transport - Transport & Mobility Data Interoperability 