From 30e304732aa9cc5b4cab4da378a86907fe8577e8 Mon Sep 17 00:00:00 2001 From: Fabien Richard-Allouard Date: Wed, 23 Oct 2024 14:23:55 +0200 Subject: [PATCH] Best practice regarding URLs and version upgrades (#699) --- gbfs.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/gbfs.md b/gbfs.md index f904219a..2fd6a818 100644 --- a/gbfs.md +++ b/gbfs.md @@ -79,7 +79,11 @@ geofencing_zones.json
*(added in v2.1)* | OPTIONAL | Geofencing zones and t ## Accessibility -Datasets SHOULD be published at an easily accessible, public, permanent URL. (for example, https://www.example.com/gbfs/v3/gbfs.json). The URL SHOULD be directly available without requiring login to access the file to facilitate download by consuming software applications. +Datasets SHOULD be published at an easily accessible, public, permanent URL. + +The URL SHOULD contain the MAJOR version number. If upgrading to a MINOR version, the URL SHOULD NOT change. (for example, https://www.example.com/gbfs/v3/gbfs.json). + +The URL SHOULD be directly available without requiring login to access the file to facilitate download by consuming software applications. To be compliant with GBFS, all systems MUST have an entry in the [systems.csv](https://github.com/MobilityData/gbfs/blob/master/systems.csv) file.