We have now updated the ‘Customer Account” API Specification to version 0.9.2 This is available to view on SwaggerHub here: https://app.swaggerhub.com/apis/open-transport For this update we have added to the “usage” entity potentially any number of “services” that are consumed. Each ‘service” each having a “type” and “amount”. So as well as expecting to cover “services” …
Continue reading “Customer Account API spec update to v0.9.2”
We have submitted our “Customer Account” API to ProgrammableWeb, the world’s leading source of news and information about Internet-based APIs and this has been accepted. Details can be found here:https://www.programmableweb.com/api/open-transport-initiative-uk Note: This version submitted (v0.8.1) was the one issued for wider industry peer review and ratification. However it has been updated since, based on some …
Continue reading “Open Transport Customer Account API now available on ProgrammableWeb”
Residents and visitors of cities, regions and even countries often face a dis-aggregated public transportation network (what we have alternatively called a fragmented transport landscape). Making it more difficult for them to move around without resorting to private transport modes that are typically higher carbon producing than their mass transit competitors. So the idea of …
Open Standards are useful when developing a technical system. They help to ensure that one application can work with another application in a common way. They therefore provide flexibility to the solution, as they enable: Data to be shared Software to be written by different people or organisations Components to be reused and adapted And …
Devising a centralised transport operator look-up service has been an interesting output for the Open Transport initiative (as well as creating the actual customer account integration API). But it wasn’t something that we originally anticipated that we would need to do. It was just something that we identified along-the-way as being necessary for true interoperability …
When creating the Open Transport API and its associated documentation, it would have been easy to fall into the the trap of just of just focusing on the technology tasks. However, it was also a key consideration of the team to consider the User Experience of those systems that have adopted the Open Standard for …
Continue reading “User Experience principles for Open Transport adoption”
Today there’s two updates to the Open Transport API: The creation of a new centralised operator look-up API (following our recent decision to create an API that will act as a directory of each registered mobility operator). This has been given the name “operator-info” and the specification set at version 0.9.1 An update to the …
One of the expected benefits of an interoperability standard for transport accounts is the improvement it gives the end user. Suppose you are a traveller who uses 6 different transport services on a pretty regular basis. This means that (aside from how you plan and buy your tickets) to get a collective view of what …
Continue reading “An improved user experience with interoperable transport accounts”
Our aim for the Open Transport Initiative is for it to be adopted as a standard by as many transport operators and MaaS platforms as possible. It is why we plan to make v1.0 an Open Standard and freely available without conditions or constraints. “So what do the participating organisations expect to get out of …
Continue reading “Open Transport account integration. Where’s the trick?”
The incremental delivery of the the Open Transport initiative has been the plan since it started. Trying to deliver (what we believe) all the functionality the transport industry needs at once Would not be realistic, given the limited resources of the founding team Does not allow for flexibility in delivery over time, as our understanding …
Open Transport - Transport & Mobility Data Interoperability 