Status of JSON Schema for references spec

[cisaacstern]

@TomNicholas and I noted @martindurant's mention in #17 (comment) of the possibility of eventually representing the references spec as JSON Schema. We do not see further mention of JSON Schema in the docs or in any issues/prs and are curious what the current status of this is.

Edit: For context, we imagine a machine-readable spec may be useful in many contexts including validation and possibly further development of JS-based frontend clients for kerchunk.

[martindurant]

Lack of time? The spec is fairly well defined in the documentation, but kerchunk uses "simple" references a lot internally, and the new(ish) parquet storage is fairly different enough. Perhaps the spec could be written as a simpler definition:

• mapping
  • string: (ascii string | base64string | bytes | [url] | [url, offset, size] )

(where JSON cannot store raw bytes)