The latest Dragonfly TOMP API version 1.3.0 sets the standard for integration between MaaS providers, Transport Operators, organizations and governments. The TOMP-WG has closely monitored compatibility with the previous version with this release, ensuring that the previously chosen path for companies to interconnect remains operational.
In recent months, the working group has put a lot of effort into further aligning with the MaaS ecosystem to increase interoperability. The results are impressive. With the latest TOMP API version, some upgrades were made to the TOMP API to enable the exchange of verifiable information from end users using the blockchain. In an ICT world where standards are the order of the day, the TOMP API has become an unmistakable link for many integration partners.
When you travel MaaS way, you normally use services that the different carriers offer. Sometimes you may need other things related to ownership such as a helmet on a fast bike. And then the question arises: is the TOMP API capable of including these 'add-ons' or 'tools in the process in a generic way? Until the current version 1.2.0, the answer was no. But in the latest version they are going to facilitate add-ons as an integral part of the TOMP API. The current way of planning and booking has been extended to facilitate add-ons. The expansion also affects the delivery of general and payment information
Within the GOFS project, the working group started working together with GTFS. This project is led by MobilityData and aims to set a standard for the mobility world. Its members are key players in the mobility industry who know that widely accepted data standards make it easier for travelers to find, understand, pay for and use transport options such as public transport, shared mobility or public transport.
It seems that adding ancillary equipment affects operator information, scheduling, and trip execution endpoints. This includes many of the building blocks of the TOMP API. Fortunately, these are non-breaking extensions. This means that a 1.3.0 implementation should be able to handle a message from a 1.2.0 implementation without technical problems or complications. Conversely, communication with a newer implementer should also be seamless, but of course the newly introduced concepts cannot be handled yet.
The TOMP-WG is a collaborative initiative to create a standard API for the technical communication between Transport Operators and MaaS Providers within the MaaS ecosystem by means of an API (Applicable Programming Interface). The TOMP API is an open standard and is being developed in the working group with public and private parties. Participants are facilitated by the Ministry of Infrastructure and Water Management.
Also read: TOMP must end spaghetti of connections