From d40f8e0eb469c6cb301dfe8723579fc43ce7a88d Mon Sep 17 00:00:00 2001 From: Manu Sporny Date: Sat, 4 Nov 2023 14:33:29 -0400 Subject: [PATCH] Reflow more text that was corrupted by PRs. --- index.html | 100 +++++++++++++++++++++++++++++------------------------ 1 file changed, 54 insertions(+), 46 deletions(-) diff --git a/index.html b/index.html index a94eedfd4..3a1b93e09 100644 --- a/index.html +++ b/index.html @@ -851,15 +851,17 @@

Presentations

verifiable presentation, which is normally composed of at least four information graphs. The first of these graphs, the verifiable presentation graph (which is the default graph), -expresses the verifiable presentation itself, and contains presentation metadata. -The verifiableCredential property in the verifiable presentation graph -refers to one or more verifiable credentials, each being one of the -second information graphs, i.e., a self-contained verifiable credential graph -which in turn contains credential metadata and other claims. Each of these graphs are -separate named graphs. The third information graph, the verifiable credential -proof graph, expresses the credential graph proof, which is usually a digital signature. -The fourth information named graph, the presentation proof graph, expresses the -presentation's digital proof, which is usually a digital signature. +expresses the verifiable presentation itself, and contains presentation +metadata. The verifiableCredential property in the verifiable +presentation graph refers to one or more verifiable credentials, each +being one of the second information graphs, i.e., a self-contained +verifiable credential graph which in turn contains credential metadata +and other claims. Each of these graphs are separate named graphs. The +third information graph, the verifiable credential proof graph, +expresses the credential graph proof, which is usually a digital signature. The +fourth information named graph, the presentation proof graph, +expresses the presentation's digital proof, which is usually a digital +signature.

@@ -2826,10 +2828,10 @@

Extensibility

use of [[?LINKED-DATA]].
  • -Support multiple types of cryptographic proof formats through the use of -JOSE or COSE [[VC-JOSE-COSE]], Data Integrity Proofs [[VC-DATA-INTEGRITY]], and a variety of cryptographic -suites listed in the Verifiable Credential Specifications Directory -[[?VC-SPECS]]. +Support multiple types of cryptographic proof formats through the use of JOSE or +COSE [[VC-JOSE-COSE]], Data Integrity Proofs [[VC-DATA-INTEGRITY]], and a +variety of cryptographic suites listed in the Verifiable Credential +Specifications Directory [[?VC-SPECS]].
  • Provide all of the extensibility mechanisms outlined above in a data format that @@ -3010,11 +3012,11 @@

    Integrity of Related Resources

    To validate that a resource referenced by a verifiable credential is the same at verification time as it is at issuing time, an implementer MAY include a -property named relatedResource that stores an array of objects that -describe additional integrity metadata about each resource referenced by the -verifiable credential. If relatedResource is present, there -MUST be an object in the array for each remote resource for each context used in -the verifiable credential. +property named relatedResource that +stores an array of objects that describe additional integrity metadata about +each resource referenced by the verifiable credential. If +relatedResource is present, there MUST be an object in the array +for each remote resource for each context used in the verifiable credential.

    The requirement that contexts be listed in `relatedResource` is currently being @@ -3024,9 +3026,9 @@

    Integrity of Related Resources

    Each object in the relatedResource array MUST contain the following: the [[URL]] to the resource named id and the -digestSRI information for the resource constructed using the method -specified in Subresource -Integrity. +digestSRI information for the resource +constructed using the method specified in +Subresource Integrity.

    The Working Group is currently attempting to determine if cryptographic hash @@ -3230,19 +3232,23 @@

    Terms of Use

    The value of the termsOfUse property might be used to tell the verifier any or all of the following, among other things: +

    -
    • -the procedures or policies that were used in issuing the verifiable credential, -for example, by providing a pointer to the location where these procedures -or policies can be found, or naming the standard that defines them; -
      • -
    • +
        +
      • +the procedures or policies that were used in issuing the verifiable +credential, for example, by providing a pointer to the location where these +procedures or policies can be found, or naming the standard that defines them; +
        • +
      • the rules and policies of the issuer that apply to the presentation of this verifiable credential to the verifier; -
        • -
      • -the identity of the entity under whose authority the issuer issued this particular verifiable credential. -
      +
      • +
    • +the identity of the entity under whose authority the issuer issued this +particular verifiable credential. +
      • +
    termsOfUse
    @@ -3868,11 +3874,11 @@

    Ecosystem Compatibility

    -Readers are advised that a digital credential is only considered -compatible with the W3C Verifiable Credentials ecosystem if it is a -conforming document and it utilizes at least one securing mechanism, as -described by their respective requirements in this specification. While some communities might call some digital -credential formats that are not conforming documents +Readers are advised that a digital credential is only considered compatible with +the W3C Verifiable Credentials ecosystem if it is a conforming document +and it utilizes at least one securing mechanism, as described by their +respective requirements in this specification. While some communities might call +some digital credential formats that are not conforming documents "verifiable credentials", doing so does NOT make that digital credential compliant to this specification.

    @@ -3993,13 +3999,14 @@

    Syntactic Sugar

  • The verifiableCredential and proof properties -are defined as JSON-LD 1.1 graph containers. +are defined as +JSON-LD 1.1 graph containers. This means the creation of named graphs used to isolate sets of data -asserted by different entities. This ensures, for example, proper -cryptographic separation between the data graph provided by each issuer -and the one provided by the holder presenting the -verifiable credential to ensure the provenance of the information for -each graph is preserved. +asserted by different entities. This ensures, for example, proper cryptographic +separation between the data graph provided by each issuer +and the one provided by the holder presenting the verifiable +credential to ensure the provenance of the information for each graph is +preserved.
  • The @protected properties feature of [[!JSON-LD]] 1.1 is used to @@ -4088,10 +4095,11 @@

    Media Types

    `application/vc+ld+json` and `application/vp+ld+json`.

    -The `application/vc+ld+json` and `application/vp+ld+json` media types do not imply any particular securing -mechanism, but are intended to be used in conjunction with securing mechanisms. -A securing mechanism needs to be applied to protect the integrity of these media types. -Do not assume security of content regardless of the media type used to communicate it. +The `application/vc+ld+json` and `application/vp+ld+json` media types do not +imply any particular securing mechanism, but are intended to be used in +conjunction with securing mechanisms. A securing mechanism needs to be applied +to protect the integrity of these media types. Do not assume security of content +regardless of the media type used to communicate it.