From ce9cf159a1079c6a3a9a549c141b1aa0ef8cd1c0 Mon Sep 17 00:00:00 2001
From: Manu Sporny
-When including a link to an external resource in a verifiable credential,
+When including a link to an external resource in a conforming document,
it is desirable to know whether the resource that is pointed to is the same at
signing time as it is at verification time. This applies to cases where there is
an external resource that is remotely retrieved as well as to cases where the
-issuer and/or verifier may have local cached copies of a resource.
+issuer and/or verifier might have local cached copies of a
+resource.
It is also desirable to know that the contents of the JSON-LD context(s) used in
-the verifiable credential are the same when used by both the
+a conforming document are the same when used by both the
issuer and verifier.
-To validate that a resource referenced by a verifiable credential is the
+To validate that a resource referenced by a conforming document is the
same at verification time as it is at issuing time, an implementer MAY include a
property named
The requirement that contexts be listed in `relatedResource` is currently being
@@ -3118,7 +3119,7 @@
-Any object in the verifiable credential that contains an `id` [[URL]]
+Any object in a conforming document that contains an `id` [[URL]]
property MAY be annotated with integrity information as specified in this
section by inclusion of Semantic Interoperability
Integrity of Related Resources
relatedResource
that
stores an array of objects that describe additional integrity metadata about
-each resource referenced by the verifiable credential. If
+each resource referenced by the conforming document. If
relatedResource
is present, there MUST be an object in the array
-for each remote resource for each context used in the verifiable credential.
+for each remote resource used in the verifiable credential.
Integrity of Related Resources
digestSRI
in the object.
@@ -3140,7 +3141,7 @@ Integrity of Related Resources
FIPS 180-4 Secure Hash Standard and the
Commercial National Security Algorithm Suite 2.0 to ensure that they are
-chosing a current and reliable hash algorithm. At the time of this writing
+choosing a current and reliable hash algorithm. At the time of this writing
`sha384` SHOULD be considered the minimum strength hash algorithm for use by
implementers.
-An example of an object in a `credentialSubject` that is refering to an +An example of an object in a `credentialSubject` that is referring to an integrity protected image.
From acc5b0a78ac982113dabef01d1f7dc5f34807304 Mon Sep 17 00:00:00 2001 From: Manu Sporny+The Working Group is seeking feedback from implementers on whether the +`relatedResource` property is useful when used in `VerifiablePresentation` +objects. Based on feedback, the Working Group might determine that the property +is not useful and will then remove the feature during the Candidate +Recommendation phase.
Each object in the relatedResource
array MUST contain the
From de8355957fc69fe3b390caf93f48234bddf3fde5 Mon Sep 17 00:00:00 2001
From: Manu Sporny Integrity of Related Resources
debated in the VCWG. This requirement might be removed in future iterations of
the specification.
+
The Working Group is seeking feedback from implementers on whether the `relatedResource` property is useful when used in `VerifiablePresentation` objects. Based on feedback, the Working Group might determine that the property