Some keys delivered are not part of API version 13

[LeSpocky]

According to SpaceAPI schema changelog contact address for Mastodon was added with v14. Although claiming to be at API version 13, we deliver it nonetheless. Maybe take the opportunity and check the whole output for API compatibility?

[penguineer]

https://github.com/SpaceApi/schema/blob/master/MIGRATION.md says:

Note that fields that were renamed or removed in v14 can still be present in your endpoint (without any function), since we ignore all unknown fields.

This is in line with modern API design, where ignoring unknown fields facilitates schema migration.

[penguineer]

The SpaceAPI validator called with our record URL (https://spaceapi.n39.eu/json) returns a successful validation. AFAIK this has also been done to validate the current implementation on its release.

[penguineer]

This is not a bug in the sense of the API spec.

[LeSpocky]

The SpaceAPI validator called with our record URL (https://spaceapi.n39.eu/json) returns a successful validation. AFAIK this has also been done to validate the current implementation on its release.

I learned from the comments of the schema repo, the validator is not strict, and does not cover the whole schema.

[penguineer]

Is there a reason not to switch to v14?

[LeSpocky]

Is there a reason not to switch to v14?

v14 was released in 2020. Sticking to an old version would only make sense, if there would be a known tool, which can not handle API versions higher than v13. So I guess we can just do it?

[penguineer]

Here is our internal dependency on the space status JSON:

• https://github.com/netz39/rollladensteuerung/blob/master/raspberry/doorcontrol/door-with-spacestatus.sh#L20

This would also work with v14.