diff --git a/index.html b/index.html index af0ffd41..7c643bec 100644 --- a/index.html +++ b/index.html @@ -117,8 +117,7 @@

credential/presentation requests|presentation=] [=digital credential/exchange protocols=], credential [=digital credential/issuance request|issuance=] [=digital credential/issuance protocols|protocols=] - and credential formats. However, to promote interoperability this - document includes a [[[#protocol-registry]]]. + and credential formats.

The API is designed to support the following goals: @@ -517,8 +516,7 @@

A standardized protocol used for exchanging a [=digital credential=] between a [=holder=] and a [=verifier=]. A protocol is identified by a - [=digital credential/protocol identifier=]. See section also - [[[#protocol-registry]]]. + [=digital credential/protocol identifier=].
Protocol identifier @@ -537,7 +535,7 @@

A standardized protocol used for communication between an [=issuer=] and a [=holder=] during the issuance of a [=digital credential=]. The issuance protocol is identified by a [=digital credential/protocol - identifier=]. See also section [[[#protocol-registry]]]. + identifier=]. -

- General inclusion criteria -

- -

- To be included in the registry, the [=digital credential/exchange - protocol=]: -

-
    -
  1. MUST be standardized at a consortium the W3C liaises with -
    2. -
  2. MUST be defined in a specification which is freely and publicly - available at the stable URL listed in the registry. -
    3. -
  3. MUST define a representation, as either a [[WebIDL]] [=dictionary=] - or a JSON object, of the [=digital credential/exchange protocol=] request - structure (i.e., the [=dictionary=] which defines the semantics and - validation of the {{DigitalCredentialGetRequest}}'s - {{DigitalCredentialGetRequest/data}} member) and the [=digital - credential/issuance protocol=] request structure (i.e., the - [=dictionary=] which defines the semantics and validation of the - {{DigitalCredentialCreateRequest}}'s - {{DigitalCredentialCreateRequest/data}} member). -
    4. -
  4. MUST define a representation, as either a [[WebIDL]] [=dictionary=] - or a JSON object, of the [=digital credential/exchange protocol=] - response structure (i.e., the [=dictionary=] which defines the semantics - and validation of the {{DigitalCredential}}'s {{DigitalCredential/data}} - member. -
    5. -
  5. MUST define validation rules for members of the request and response - structures. -
    6. -
  6. MUST have undergone privacy review by the W3C's Privacy Working Group and - Federated Identity Working - Group. - -
    7. -
  7. MUST have undergone security review by the Security Interest Group. -
    8. -
  8. MUST have implementation commitment from at least one browser engine, - one credential provider/wallet, and one issuer or verifier (depending on - the protocol type). Each component MUST be from independent - organizations. -
    9. -
  9. MUST have formally recorded consensus by the Federated Identity - Working Group to be included in the registry. -
    10. -
-

- Presentation-specific inclusion criteria -

-

- To be included as a presentation protocol in the registry (used with - `navigator.credentials.get`), the [=digital credential/exchange - protocol=]: -

-
    -
  1. MUST support response encryption. -
    2. -
  2. MUST encrypt any response containing personally identifiable - information (PII). -
    3. -
-

- Change process -

-

- To add a new [=digital credential/exchange protocol=] to the registry, or - to update an existing one: -

-
-
- Define a [=digital credential/protocol identifier=]. -
-
- The [=digital credential/protocol identifier=] MUST be a unique string - that is not already in use in the registry. The [=digital - credential/protocol identifier=] MUST uniquely define the set of - required parameters and/or behavior that a digital credential provider - implementation needs to support to successfully handle the request. If - the set of required parameters or behaviors is updated in a way which - would require a digital credential provider to also require an update - to remain functional, a new protocol identifier MUST be assigned and be - added to the registry. -
-
- Specify a protocol - type. -
-
- The protocol type is either "Presentation" for presentation protocols - used with `navigator.credentials.get` or "Issuance" for issuance - protocols used with `navigator.credentials.create`. -
-
- Describe the - protocol. -
-
- The description MUST be a brief summary of the protocol's purpose and - use case. -
-
- Provide a link to the - specification. -
-
- The specification MUST be a stable URL that points to the authoritative - source for the protocol, including validation rules. -
-
-

- [=User agents=] MUST support the following [=digital credential/exchange - protocols=]: -

- - - - - - - - - - - - - - - -
- Table of officially registered [=digital credential/exchange - protocols=]. -
- [=digital credential/Protocol identifier=] - - [=registry/Type=] - - [=registry/Description=] - - [=registry/link|Specification=] -
- Coming soon... -