Change boolean values from 1/0 to true/false

[heidiguenin]

As per the general consensus over on Issue #10

Because this is a breaking change, it would not be implemented until we move into the next major version. The issues been open for coming on 4 years, though, so once we're ready for the next major version, it would be great to include this change!

[jcn]

I propose that in the Field Definitions section we include language like:

• Boolean values must be JSON booleans, not strings (i.e. true or false, not "true" or "false")

[heidiguenin]

Proposal revised to reflect @jcn's recommendation to add new Field Definition.

[gcamp]

Look good to me

[heidiguenin]

I hereby call a vote on this proposal. Voting will be open for 7 full days, until 11:59PM UTC on December 6th.

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

[yocontra]

+1 from Stae

[madupras]

+1 from PBSC

[quicklywilliam]

+1 from Ride Report

[evansiroky]

+1 from IBI Group

[gcamp]

+1 from Transit

[johnpena]

+1 from Lime

[charlesjump]

+1 JUMP

[heidiguenin]

The vote on this is now closed, and it passes.

Votes for:

1. Stae
2. PBSC
3. Ride Report
4. IBI Group
5. Transit
6. Lime
7. Jump

There were no votes against. Much of the MobilityData team is traveling today, so we'll take next steps in the coming days!

[heidiguenin]

We'd love to make this an official part of the spec, but first we need to see this change being implemented. Could you comment here if your organization has implemented this?

@evansiroky @quicklywilliam @charlesjump @gcamp @contra @johnpena @madupras Others?

[madupras]

Please see this comment in the other ticket: #182 (comment)
This change is also part of our GBFS version 2 implentation plan.