diff --git a/index.html b/index.html index 7d9d559..6c06ddc 100644 --- a/index.html +++ b/index.html @@ -423,8 +423,11 @@

- Registry of protocols for requesting digital credential + Registry of protocols

+

+ Initiating the registration a protocol is done by filing an issue in our GitHub repository. +

The following is the registry of [=digital credential/exchange protocols=] that are supported by this specification. @@ -434,11 +437,114 @@

the future.

- Inclusion criteria + General inclusion criteria

+

- To be included in the registry... + 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 {{DigitalCredentialsProvider}}'s + {{DigitalCredentialsProvider/request}} 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 Interest + Group and Federated Identity Working Group. + +
    7. +
  7. MUST have undergone security review by the Federated Identity Working 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 protocol identifier +
+
+ The protocol identifier MUST be a unique string that is not already in + use in the registry. Use only lowercase ASCII letters, digits, and + hyphens (e.g., "protocol", "the-protocol"). The 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 @@ -452,13 +558,15 @@

- Protocol identifier + Protocol + identifier - Description + Type - Specification + Specification