error in system_alerts example

[albertoabellagarcia]

The example of payload for the system_alerts data model does not validate against its schema, start and end should be literal numbers and not strings as provided.
Additionally in other examples of data models (sorry I did not take notes of which ones) failed validations against their schemas because the version attribute has not the enumeration value "3.0"

[heidiguenin]

We moved this issue to the gbfs validator repo, so I'm closing it here.

[isabelle-dr]

Hi @albertoabellagarcia, thanks for opening this issue!
I'm looking into and I can't find an error in the JSON schemas related to this.

• the start and end in system_alerts are modelled this way:

  "start": {
      "description": "Start time of the alert.",
      "type": "number",
      "minimum": 1450155600
    },
    "end": {
      "description": "End time of the alert.",
      "type": "number",
      "minimum": 1450155600
    }

This is how the timestamp types are modelled in the JSON Schemas

• The version attribute of all gbfs_versions.json files have the value 3.0.

Could you explain those errors a little more? Is it an error in the validator itself?
Thanks

[albertoabellagarcia]

If you take the schema for system_alerts and the payload in the examples is wrong because the figures are quoted (therefore it is a string) while they should be unquoted to be a number. (for times subproperty of data->alerts)

[isabelle-dr]

Oh okay I see :)
This has been fixed since the v2.2 release, see the master branch.