A new year brings new opportunities. Besides wishing you all the best for the year 2022, we from the TOMP working group have something to share with all of you. A new version of the TOMP-API.
As promised this version is fully compatible with the Long Term Support version 1.2, there are no breaking changes and all current implementations can continue running without issues.
The world of MaaS is evolving our API is evolving with it, so we would not want to keep the new goodies from you.
The changes for the can be divided into the following categories:
- Functional extension for ancillaries
- Alignment with GOFS: 2 new endpoints, extra fields on the booking
- Alignment with blockchain technology to facilitate user information verification.
- Extension of the areas principle: make it possible to exchange no-parking, no-access, and price reduction areas
- Extensions of asset properties: mileage, license plate, maximum speed, number of doors,…
- Improvement of the object model: reference of assetType into pricing plans and conditions
- Fixed technical issues: removing circular dependencies, correction of typo’s,…
- Other minor changes
We have published blogs on the On-Demand standard – alignment with GOFS and the alignment with Blockchain technology that dive into some more details on certain specifics of this new release.
As always the API specification was published on our wiki and in Swaggerhub format. The wiki has been freshened up so be sure to check that out.
There is a reference implementation to get your project kickstarted.
The proposal list of supported “user claims” list for blockchain implementations can be found here.
The extended CROW travellers dictionary can be found here