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

extra fields in metadata #209

Open
d-v-b opened this issue Aug 1, 2023 · 0 comments
Open

extra fields in metadata #209

d-v-b opened this issue Aug 1, 2023 · 0 comments

Comments

@d-v-b
Copy link
Contributor

d-v-b commented Aug 1, 2023

As far as I can tell, all of the metadata in the spec permits additional fields to be added. Should we impose any restrictions on this? My concern is that if we allow implementations unlimited additions to the ome-ngff metadata, then users will be tempted to add fields, but as those fields are not explicitly part of the spec, there will be no guarantee that those fields survive a round-trip through arbitrary ome-ngff-compatible tools.

For something like multiscale metadata, there's already an unconstrained metadata field in which users or applications can put anything they want. Given this option, it seems reasonable to then require that users refrain from adding extra fields to the rest of the multiscales dictionaries.

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

1 participant