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 need to implement?‘.
To be able to provide an answer to this question for everyone interested, we are preparing a list of ‘use cases’. We have provided use cases for all six of the TOMP-API modules.
These use cases do have the form of ‘As a [some kind of actor] I would like to [do something] in order to [reason]’. For instance:
As a transport operator
I would like to enable external parties to book a specific asset
in order to provide the asset as a service.
With these ‘use cases’ we can describe precisely what you have to implement in different situations or phases of implementation.
For the example above, we can tell you that you need the one-stop-booking endpoint and you have to specify this direct booking option in the meta-endpoint in the process identifiers.
You can study the use cases. Please keep in mind that, for the moment, it is a work in progress.
“Ok, that’s clear to me. I have to look at all the use cases and find out which ones are related to my business. But how do I know which use cases are implemented by companies like mine?”
We will support you with a wiki page, describing the minimal viable products per modality that describes which use cases are relevant for e.g. taxi or scooter. And we indicate the priority of each of the use cases.
Happy coding!