ROR schema backward compatibility

A relatively trivial issue is that at https://github.com/ror-community/ror-schema the "master" branch currently does not include the v2.1 schema -- I had to go to the "schema-v2-1" branch in order to get the updated version. Since v2.1 is now public I think that schema should not be hidden in a feature branch.

The stickier issue actually came up earlier, when I tried to parse a newer ROR entry using the v2.0 schema. This failed because of the enumerated values here:

This enum only includes "1.0" and "2.0" -- so trying to parse data marked with schema v2.1 fails because "2.1" is not enumerated.

Thanks for the quick reply!

I'm afraid this does not do much to alleviate my concerns about versioning. It just doesn't seem workable for us to preemptively update our ROR clients based on somebody watching these forums.

I don't have a lot of expertise around json schemas, but I found a few references to this pitfall around enums:

I tried swapping "x-extensible-enum" for "enum" (as suggested in the first link) in the schema and this worked as expected -- my generated code treats these as strings rather than enums so the data validates. I do appreciate that this is nonstandard, though. Alternatively, would it be possible to make the version a simple string (perhaps with a regex), or include only the major version number? The fact that this will break clients even on point version changes is the part that concerns me the most.

(Also, feel free to tell me that the intended use of the schema is primarily intended for internal validation rather than for use by external clients.)

Cheers,

Adam