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
Anyone on the @zarr-developers/implementation-council or @zarr-developers/steering-council who would like to discuss ZEP0001 and the related zarr-developers/zarr-specs#149 is invited to join this Wednesday's community call.
Thanks for everyone who attended but especially from those from the ZIC (Ward, Jeremy, Greg, and Trevor). Full notes will be in the regular place, but a few high-level summary points:
ZEP0001 & sharding -- In order to keep ZEP0001 moving forward, the consensus was to delay the sharding discussion for a follow ZEP, but to include the necessary API/hooks in ZEP0001 so that implementations will be aware of the upcoming addition.
v3 file layout -- Several proposals were discussed but the suggestions include:
move the metadata files to the main file tree so that groups and arrays can be referenced by a path that exists on disk
combine the array and group metadata files
v3 data types similarly:
make the codec config a list to create a pipeline (removes the need for a raw codec)
clarify and/or simplify the relationship between filters and codecs (keeping HDF5's model & needs in mind)
move endianness out of the data type in favor of returning native endianness to end users
Anyone on the @zarr-developers/implementation-council or @zarr-developers/steering-council who would like to discuss ZEP0001 and the related zarr-developers/zarr-specs#149 is invited to join this Wednesday's community call.
Details can be found at https://zarr.dev/#community-meetings
The text was updated successfully, but these errors were encountered: