Because storage layout information is available somewhere else I did not make a distinction between byte streams of a chunked dataset vs. a single byte stream of a contiguous dataset. The byteStreams key will always hold an array of byte stream information.
For the same reason, each byte stream information will have its location in the dataset's dataspace as dspace_anchor key. For contiguous datasets, its value will always be [0, 0, ...].
Checksum information has two keys: type (MD5, SHA1, a URI, etc.) and value. The type information is repeated for every byte stream but I wanted to allow having byte stream checksums of different types.
Checksum value's spec describes it simply as an ASCII string without the slash but we may want to be more accurate here.
This is my proposal to start a discussion...
Few explanations:
Because storage layout information is available somewhere else I did not make a distinction between byte streams of a chunked dataset vs. a single byte stream of a contiguous dataset. The
byteStreamskey will always hold an array of byte stream information.For the same reason, each byte stream information will have its location in the dataset's dataspace as
dspace_anchorkey. For contiguous datasets, its value will always be[0, 0, ...].Checksum information has two keys: type (MD5, SHA1, a URI, etc.) and value. The type information is repeated for every byte stream but I wanted to allow having byte stream checksums of different types.
Checksum value's spec describes it simply as an ASCII string without the slash but we may want to be more accurate here.