Over the past months, the TOMP working group has put a lot of effort into further alignment with the MaaS ecosystem to enhance interoperability.
We started collaborating with GTFS, within the GOFS project. This project is led by MobilityData and aims to establish a standard for the On-Demand mobility world (hence the ‘O’ in the abbreviation). Next to this, we extended the API with functionality for ancillaries. And last, but not least, some upgrades to the TOMP-API were made to make it possible to exchange validatable information from end-users using the blockchain.
At the moment, the TOMP working group is busy creating release candidate 1.3.0. We will announce the exact release date around Christmas, a Christmas present of sorts.
With this publication we are ‘closing the gates’ for the new release, this means no new issues – unless they are really blocking – are taken into account constructing version 1.3.0 from now on.
What will change with version 1.3.0?
As promised with the 1.2.0 LTS release, this release will contain no breaking changes. Current implementations can continue running unchanged if this is required.
The upcoming changes can be categorized 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’ve already described ancillaries in an earlier blog and in the coming weeks, we will publish different blog posts with more clarifications on the other items of this update.
We will keep you posted!