Skip to content

Remove misleading section of readme #155

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
testower merged 1 commit into from
Oct 3, 2025
Merged

Remove misleading section of readme #155

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 0 additions & 16 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -66,19 +66,3 @@ List of additional rules:
* `NoMissingCurrentRangeMetersInVehicleStatusForMotorizedVehicles`
* `NoMissingStoreUriInSystemInformation`

## Non-schema rules:

Some rules can't be validated with json schema:

Existing rules:

* All version of gbfs require the system_information endpoint.
* In addition, gbfs endpoint is required as of v2.0.

Planned rules:

* Either station_information or station_status is required if the other is present
* Can this be checked by cross-checking ids between files - using schema patching?
* vehicle_types is required if vehicle types are referenced in other files (already covered?)
* system_pricing_plans is required if pricing plans are referenced in other files