diff --git a/index.html b/index.html index e61eda0a1..aaf2cbdeb 100644 --- a/index.html +++ b/index.html @@ -585,15 +585,16 @@

Use Cases and Requirements

-A conforming document is any concrete expression of the data model -that complies with the normative statements in this specification. -Specifically, all relevant normative statements in Sections -, , and - of this document MUST be enforced. A serialization -format for the conforming document MUST be deterministic, bi-directional, -and lossless as described in Section . -The conforming document MAY be transmitted or stored in any such -serialization format. +A conforming document is a +compacted JSON-LD +document that complies with all of the relevant "MUST" statements in this +specification. Specifically, the relevant normative "MUST" statements in +Sections , , and + of this document MUST be enforced. +A conforming document is either a verifiable credential that MUST be +serialized using the `application/vc+ld+json` media type or a +verifiable presentation that MUST be serialized using the +`application/vp+ld+json` media type.

@@ -3864,12 +3865,9 @@

Ecosystem Compatibility

If conceptually aligned digital credential formats can be transformed into a conforming document according to the rules provided in this section, they -are considered "compatible with the W3C Verifiable Credentials ecosystem". -A conforming document is either a verifiable credential serialized -as the `application/vc+ld+json` media type or a verifiable presentation -serialized as the `application/vp+ld+json` media type. Specifications that -describe how to perform transformations that enable compatibility with -the Verifiable Credentials ecosystem: +are considered "compatible with the W3C Verifiable Credentials +ecosystem". Specifications that describe how to perform transformations +that enable compatibility with the Verifiable Credentials ecosystem:

-
-

Data Model Conformance Checking

- -

-The algorithm in this section can be used to determine if a provided document is -conformant with the data model provided in this specification. This algorithm -takes a document (object inputDocument) and produces an object -(dataModelConformanceChecked) that contains the following: -

- - - -

-The data model verification algorithm is as follows: -

- -
    -
  1. -Set dataModelConformanceChecked to an empty object. Initialize the following -fields in dataModelConformanceChecked: status to `false`, -warnings to an empty array, and errors to an empty array. -
    2. -
  2. -Ensure that the `@context` property of document conforms to the -statements in . If not, return -dataModelConformanceChecked, which will contain a false verification status. -
    3. -
  3. -Starting at the top level, recursively process each object obj in -document, setting -MALFORMED_VALUE_ERROR errors in -dataModelConformanceChecked.errors if errors are found, by -performing the following checks: -
      -
    1. -If present, ensure that the `id` property conforms to the "MUST" statements in -Section . -
      2. -
    2. -If present, ensure that the `type` property conforms to the "MUST" statements in -Section . -
      3. -
    3. -If present, ensure that the `name` and/or `description` properties conform to -the "MUST" statements in Section . -
      4. -
    4. -If the `type` property is present and contains an object with the type -`VerifiablePresentation`, ensure that the object conforms to the -"MUST" statements in Section . -
      5. -
    5. -If the `type` property is present and contains an object with the type -`VerifiableCredential`, perform the following checks: -
        -
      1. -Ensure that the `credentialSubject` property conforms to the -"MUST" statements in Section . -
        2. -
      2. -Ensure that the `issuer` property conforms to the -"MUST" statements in Section . -
        3. -
      3. -If present, ensure that the `validFrom` and/or `validUntil` properties conform -to the "MUST" statements in Section . -
        4. -
      4. -If present, ensure that the `credentialStatus` property conforms to -the "MUST" statements in Section . -
        5. -
      5. -If present, ensure that the `credentialSchema` property conforms to -the "MUST" statements in Section . -
        6. -
      6. -If present, ensure that the `relatedResource` property conforms to -the "MUST" statements in Section . -
        7. -
      7. -If present, ensure that the `refreshService` property conforms to -the "MUST" statements in Section . -
        8. -
      8. -If present, ensure that the `evidence` property conforms to -the "MUST" statements in Section . -
        9. -
      -
      6. -
    -
    4. -
  4. -If no errors were detected to this point, set -dataModelConformanceChecked.document to inputDocument, -dataModelConformanceChecked.status to `true`. -
    5. -
  5. -Return dataModelConformanceChecked. -
    6. -
- -
-

Verify Securing Mechanism

@@ -4896,7 +4765,7 @@

Problem Details

The value associated with a particular property is malformed. The name of the property and the path to the property SHOULD be provided in the ProblemDetails object. See Section -. +. @@ -7347,7 +7216,7 @@

Revision History

or are at risk for removal.
  • -Restrict data model expression to JSON-LD in compact document form. +Restrict data model expression to JSON-LD in compacted document form.
  • Update ZKP section to remove older content.