The TOMP-API is ready for the next level of interoperability with a new release adding new features and adhering to requests made by implementors.
This (minor) release for Dragonfly version 1.2.0 is fully backwards compatible with the 1.x range and with it, we are introducing a Long Term Supported version. For extra assurance, this is a safe en reliable version to implement for the future. We will keep working and improving the API with additions instead of changes and thus avoiding breaking changes.
The roadmap below depicts the progress made and our plans for moving forward.
With Dragonfly version 1.2.0 we introduce some new and improved features :
- Standardized access methods to open/use assets. (Deeplinking, QR codes, Aztec, OV Chipcard, EMV, AXA EKey, … )
- Getting ready for the MaaS ecosystem (Personal information).
- Incorporating the CROW-travel dictionary.
- Improved support for “negative” flows (Cancellation, Stolen assets,..).
- Minor updates.
A full list of updates & features can be found on our Github wiki :
https://github.com/TOMP-WG/TOMP-API/wiki/Changes
For any questions and remarks regarding this update or the TOMP-API in general we can also refer to our Github pages. In the upcoming days, we will release small blogposts diving deeper into the new features.
The TOMP working group has continued working with great enthusiasm from the comfort of our own homes, switching to a fully digital way of working. We are, however, looking forward to the end of this pandemic crisis and looking each other in the eye again.
Stay safe and healthy,
TOMP Working Group