On Wed, Dec 9, 2020 at 6:17 PM Baskauf, Steven James <
steve.baskauf@vanderbilt.edu> wrote:
> Full values are represented as nodes having prefix wdv:
and the local name being the hash of the value contents (e.g. wdv:382603eaa501e15688076291fc47ae54
).
There is no guarantee of the value of the hash except for the fact that
different values will be represented by different hashes, and same
value mentioned in different places will have the same hash.
indeed no assumptions should be made on this hash value, the initial goal was (I think) for two unrelated claims that have the same complex value elements to share it instead of reifying one for each claim/reference. I would strongly advise against storing this hash for later use.
About 35976d7cb070b06a2dec1482aaca2982df3fedd4 which I think you obtained from the wbgetclaims api[0]? I think this hash identifies the Snak while the one you see from the query service identifies the Value, the former will uniquely identifies the Snak so that for another entity using the same value[1] the Snak hash is different (8eb6208639efa82b5e7e4c709b7d18cbfca67411) but the value is identical (+2019-12-14T00:00:00Z).
I don't think you can extract the hash of the value using wbgetclaims but it is visible using the RDF output[2].