TOMP-WG / TOMP-API

Transport Operator to Mobility-as-a-Service Provider-API development for Mobility as a Service
Apache License 2.0
100 stars 41 forks source link

Communicate API-version to be used #29

Closed pimmeh closed 5 years ago

pimmeh commented 5 years ago

MaaS-providers and Transport Operators are not going to use the same TOMP-version at the same time. In essence, there will be no big bang moment that all the companies will switch to a newer version once we release it. I therefore suggest that we include a way that the version to be used in the communication is in the communication itself.

For instance, in each authentication handshake between MP and TO, the API-standard to be used is included in the header so that the receiving party know's what TOMP-version to communicate back and forth.

efel85 commented 5 years ago

Suggestion to add the API-version in the header of each message that is exchanged. We need to specify the header for the communication.

paxx-dev commented 5 years ago

Solved in #48?

efel85 commented 5 years ago

Yes, solved in #48