You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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 themultiscales
dictionaries.The text was updated successfully, but these errors were encountered: