A FAIR TOMP-API
The TOMP-Working Group is on a mission to develop an API that is ‘FAIR’: Findable, Accessible, Interoperable and Reusable.
Read more about this ambition in the blog written by Edwin van den Belt.
The TOMP-Working Group is on a mission to develop an API that is ‘FAIR’: Findable, Accessible, Interoperable and Reusable.
Read more about this ambition in the blog written by Edwin van den Belt.
The mission and vision of the TOMP Working Group call for an interoperable standard that can work with all existing and recognized standards. That is why it is very important…
Smooth – and less smooth – travel Imagine that you want to travel by public transport from Amsterdam to Simpelveld, a village in the southwest of the Netherlands. You open…
In the past, I have talked to a lot of Transport Operators, also known as Mobility providers. Each of them had their own business model and way of working. Together…
The TOMP-API is a modular specification, consisting of six modules. Each of these modules contains multiple endpoints. One of the questions that reaches us the most is, ‘What do I…
The TOMP-API is agnostic regarding ‘static information’ that is needed to book. Static information (data from level 1 of MaaS Maturity modal of RISE) can be supplied using GBFS, GTFS,…
Easter is coming up. Time to have a short retro. Wow! In the past 3 years of the rise of the TOMP-API, we have created quite a few deliverables. I…
Blockchain In a pilot project together with BloXmove, we found out that the TOMP-API should be extended a bit to cope with exchanging validatable account information. Next to this, the…
MobilityData is a non-profit organization that develops and maintains mobility standards such as GFBS and GTFS. It recently started the GOFS project, which will result in GTFS-GOFS. The first part…
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…