Josh Moore
Josh Moore
> Could you elaborate on the idea of an "internal identity"? ``` my_experiment.zarr/ ├── analysis │ └── segmentation └── image_data ``` One of the keys of [linked data](https://en.wikipedia.org/wiki/Linked_data) is the...
> Storing arrays and groups in the same level of hierarchy can complicate semantics. In the case of labels, I can definitely see correcting the structure as it currently stands....
> Zarr already provides a set of operational semantics for "list-like thing" (zarr group) and "value-like thing" (zarr array). Guess I think of zarr groups as being more dictionary like...
toCSV will be easy enough. fromCSV will for many (if not most?) cases require extra metadata. There are a number of attempts to provide such metadata, e.g., https://specs.frictionlessdata.io/data-package/
Also cc: @kevinyamauchi and @ivirshup who are also discussing more on this this week. I think you are right that there's no tree representation in the current discussions, but perhaps...
> https://github.com/ome/ngff/issues/31#issuecomment-787820475 Currently I think that I would prefer storing images within a zarr container without any hierarchy, i.e. just as a flat list. Is this a MAY or a...
> https://github.com/ome/ngff/issues/31#issuecomment-791273590 So I imagine they could be changed without moving the data on disk. No. To move objects around in object storage is *always* a copy/delete operation. > https://github.com/ome/ngff/issues/31#issuecomment-791033216...
Just to clarify one issue that will become more important with Zarr V3, each of those paths contains an `OME-Zarr image`. In the future, there will be a root file...
:+1: for both constraints (title of issue updated)
> So, I guess we first need to agree on a term (extension, properties, attributes etc) and then decide where in the spec we want it? With the caveat that...