Specify what trip type should be assumed when trips are sent with no trip_types

[pierre-bouffort]

Is your feature request related to a problem? Please describe.

The problem we are facing, mostly with new modes like with the Passenger Services and Delivery Robot, is that there is some blur revolving around what trips should be sent in the case that the optional field trip_type isn't populated.
When operators send the data for their different trips with the trip_type populated, the standard allows us to very easily identify the types of trips we are looking at (deliveries and passenger trips most importantly). But when that field isn't populated it becomes impossible to make sure that the "core" trips (meaning the deliveries and passenger trips) are what we are looking at.

Describe the solution you'd like

My suggestion would simply be to add a comment saying that, by default, if the trips are published without a trip_type, it will by default be considered as

• a private passenger trip for the Passenger Services mode.
• a delivery trip for Delivery Robot mode
• a rider trip for Micromobility
• a private trip for Carsharing

This way, the specification makes it unequivocal what type of trip we are looking at if the trip_type is empty.

Is this a breaking change

A breaking change would require consumers or implementors of the API to modify their code for it to continue to function (ex: renaming of a required field or the change in data type of an existing field). A non-breaking change would allow existing code to continue to function (ex: addition of an optional field or the creation of a new optional endpoint).

• No, not breaking

Impacted Spec

For which spec is this feature being requested?

• agency
• provider

[schnuerle]

I think this is solved as part of our Delivery work. See this comment and the linked commits, and let us know if you think that works. #959 (comment)