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

Use version suffix with omexManifest/content@format #100

Open
jonrkarr opened this issue Jul 1, 2021 · 2 comments
Open

Use version suffix with omexManifest/content@format #100

jonrkarr opened this issue Jul 1, 2021 · 2 comments

Comments

@jonrkarr
Copy link
Contributor

jonrkarr commented Jul 1, 2021

My understanding is that the value of omexManifest/content@format should continue to be http://identifiers.org/combine.specifications/omex-metadata. Since the details of the new version diverge from that of the previous version, I think it would be helpful to use version suffixes to indicate which version is being used.

@CiaranWelsh
Copy link
Contributor

I'm not sure exactly how to resolve this - @jhgennari @nickerso perhaps you have some input here?

@jonrkarr
Copy link
Contributor Author

jonrkarr commented Aug 4, 2021

Instead of http://identifiers.org/combine.specifications/omex-metadata, manifests could be encouraged to use http://identifiers.org/combine.specifications/omex-metadata.version-1_2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants