Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Decoupling version numbers of different specifications #47

Closed
constantinpape opened this issue Apr 26, 2021 · 2 comments
Closed

Decoupling version numbers of different specifications #47

constantinpape opened this issue Apr 26, 2021 · 2 comments

Comments

@constantinpape
Copy link
Contributor

While working on #46 I noticed that we now need to bump the version number for the HCS spec, although nothing in it has changed. In the future with more specifications for different OME-NGFF formats, this can become pretty confusing, because any change in one of the specifications will require a "global" version bump.

I am not sure if there is a better solution, because having diverging version numbering in the same repository could introduce it's own set of problems. But I still wanted to bring this up for discussion.

@joshmoore
Copy link
Member

Agreed. My (strong) preference would be to introduce a single top-level item that provides the version:

{
    "@context": "https://ngff.openmicroscopy.org/contexts/0.2"
}

that would allow for a json-ld parsing: https://json-ld.org/spec/latest/json-ld/#the-context

@constantinpape
Copy link
Contributor Author

Closed in favor of #83

@joshmoore joshmoore mentioned this issue Feb 3, 2022
13 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants