Provide configuration endpoint that describes the existing/implemented data structure of the producer

[matt-wirtz]

What is the issue and why is it an issue?

As a consumer who is not familiar with the shared service the many "conditionally required" and "optional" structures (and endpoints) make an implementation more difficult: e.g. vehicles[].current_range_meters is required if the corresponding vehicle_type definition for this vehicle has a motor. But if there are no vehicle_types provided - which should be in the case if powered vehicles are provided but which is not a must - then it's tedious to find out.

Please describe some potential solutions you have considered (even if they aren’t related to GBFS).

It would be good to have some kind of "configuration" endpoint which describes the provider / service explicitly and thus enables an API consumer to rely on existence of structures / endpoints instead of having to check multiple combinations of "is it there or is it missing?

Is your potential solution a breaking change?

• Yes
• [ X ] No
• Unsure

[mobilitydataio]

This discussion has been automatically marked as stale because it has not had recent activity. It will be closed in 30 days if no further activity occurs. Thank you for your contributions.