Require lowercase enums

[josee-sabourin]

What problem does your proposal solve? Please begin with the relevant issue number. If there is no existing issue, please also describe alternative solutions you have considered.

As discussed on the validator repo, having both uppercase and lowercase enum values creates deserialization issues.

What is the proposal?

Modifies enum field type to say that enums MUST be lowercase, rather than SHOULD.

Is this a breaking change?

• Yes
• No
• Unsure

Which files are affected by this change?

• vehicle_types.json
• station_information.json
• free_bike_status.json
• system_alerts.json

cc: @testower

[AntoineAugusti]

We (@ transport.data.gouv.fr) had to get in touch with multiple people in regards to this, thanks for clarifying it!

[josee-sabourin]

I hereby call a vote on this proposal. Voting will be open for 10 full calendar days until 11:59PM UTC on Thursday, March 9th, 2023.

Please vote for or against the proposal, and include the organization for which you are voting in your comment.

Please note if you can commit to implementing the proposal.

[testower]

Entur votes in favour and will implement this proposal.

[benwedge]

Joyride (feed provider) votes in favour and recently made this change on our 2.3 feeds, so we will absolutely comply in 3.0.

[fbouchPBSC]

+1 for PBSC for version 3.0

[cmonagle]

+1 for Transit

[josee-sabourin]

This vote has now closed, and it passes!

Votes in favor:
Entur (consumer)
Joyride (producer)
PBSC (producer)
Transit (consumer)


There were no votes against.