Crypto namespace ends with slash not hash #404
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an update suggested by @gllmflndn through the SPM NIDM exporter (cf. incf-nidash/nidmresults-spm#42).
NIDM-Results is currently using
http://id.loc.gov/vocabulary/preservation/cryptographicHashFunctions#
as base URI for the crypto namespace though, according to the corresponding website, we should usehttp://id.loc.gov/vocabulary/preservation/cryptographicHashFunctions/
(with a final/
).This PR updates the model and examples to use the official namespace.
This change will break backward compatibility so should be included in the next major release of NIDM-Results. In practice, I don't think that any of our tools is using this attribute yet.