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
Do we have a fixed convention for how to use json terminology in the spec?
For object ({}) I think we are currently using dictionary. And for array ([]) we are using list.
I.e. we are using the names of the equivalent python data structures. I think this is fine (esp. since we don't want to use array due to the overloaded meaning in the zarr spec), but it should be stated somewhere in the preamble of the spec.
The text was updated successfully, but these errors were encountered:
Do we have a fixed convention for how to use json terminology in the spec?
For
object
({}
) I think we are currently usingdictionary
. And forarray
([]
) we are usinglist
.I.e. we are using the names of the equivalent python data structures. I think this is fine (esp. since we don't want to use
array
due to the overloaded meaning in the zarr spec), but it should be stated somewhere in the preamble of the spec.The text was updated successfully, but these errors were encountered: