IEEE.org     |     IEEE Xplore Digital Library     |     IEEE Standards     |     IEEE Spectrum     |     More Sites

Commit 31aeb7de authored by Charles King's avatar Charles King
Browse files

ETag

Comment ID: 26446300023
Page: 3
Line: 21
Comment: ".. should be included in the generation of the hash"  - Hashsum calculation of JSON object trees are non-trivial and must be clearly defined. Out of scope for BioCompute?
Must Be Satisfied: Yes
Proposed Change: Reference a formal specification of JSON object hashing, or remove 'hash'. (alternative: rename to 'etag' and have looser definition)
parent 46a98682
......@@ -7,7 +7,7 @@
"required": [
"bco_id",
"bco_spec_version",
"checksum",
"etag",
"provenance_domain",
"usability_domain",
"description_domain",
......@@ -128,7 +128,7 @@
"readOnly": true,
"format": "uri"
},
"checksum": {
"etag": {
"type": "string",
"description": "A string-type, read-only value, protecting the object from internal or external alterations without proper validation generated with a SHA-256 hash function.",
"examples": [
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment