DP - field "hash" in resource information is unclear.

[relet]

Is it a checksum?
Should it include the algorithm? Should it allow for several algorithms? Should it require certain algorithms?

"hash":"28cb0cb25701a242d84c2857fdf52775" 

or

"hash":{
  "md5":"28cb0cb25701a242d84c2857fdf52775",
  "sha256":"..."
}

?

[rufuspollock]

Yes it is a checksum. Options:

• Set one and only one option (e.g. md5 or sha256). md5 is attractive as common (cf s3) but has vulnerabilities.
• Have (and require) a prefix: e.g. "md5:{hash}" or "sha256:{hash}"
• Have a default and allow specification of a prefix
• Allow multiple hashes as per the suggestion above

I would incline to either option 1 or 4.

[relet]

All are valid options if the standard itself is versioned -
having just one option is easier on the tools (they have to implement all options if datasets can present either).

[rufuspollock]

OK, i'm going to recommend option 1 and recommend md5 (following s3 etc).

[rufuspollock]

@relet thank-you very much for the issue and the suggestions here. As per discussion have resolved by clarifying this is md5 and there is only one hash field.