Release not available

[pvanlaake]

schema.json and README.md refer to a release that is supposedly to be found under /refs/tags/v1. That release however does not exist. With the $id in schema.json I am now running into problems with validating schemas that use this convention. Is this something that can be easily fixed?

[kylebarron]

I think this is because the tag hasn't been created yet, not because it's been deleted.

[pvanlaake]

That makes external use of this schema rather awkward at the moment. I am embedding proj: in another convention and now my validator needs bespoke code to support validation of proj: sub-clauses. That's not really a tenable arrangement.

[kylebarron]

I agree I'd like to have a tag we can point to. I think the current situation is related to the planned versioning, where people wanted to start the versioning at 1.0, but the current state of the repo might not be ready for 1.0...?

I'm not entirely sure but I think @maxrjones probably can explain better.

[pvanlaake]

I understand the conundrum perfectly well as I am working on multiple conventions myself, including one which references several other conventions.

Perhaps we can consider another arrangement for published conventions - GitHub is not intended as a long-term repository for stable code anyway (even though enough people use it just for that), it's an environment for code development. Would it be possible to host published conventions on geozarr.org? That could then be dressed up with some more features, such as a look-up service by UUID, a web page for each convention for the formal spec and a manual/tutorial-style page, etc.

[maxrjones]

fixed via https://github.com/zarr-conventions/proj/releases/tag/v0.1