For our first TOMP-interview, we had an interesting conversation with Eddy Borremans, software architect for Nazza: a Linux/Java based software integrator in the mobility domain. They offer a cloud based…
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…
NTM, the National Mobility Data Access Point, is supporting technical MaaS standards in the Netherlands since 1 January 2023. This means for the TOMP-WG that NTM takes over the supporting…
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,…
Last year around the holidays we released version 1.3, this year we want to keep up with that tradition and give you another present towards the standardisation of mobility data.…
Ghent is the city for epicureans, nothing is necessary, everything is possible. For the past two years, the TOMP working group meetings have been forced to be held online via…
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…
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.…
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…