From 3a86ea8189e0b7af3f352649c302a5da5abc45e1 Mon Sep 17 00:00:00 2001
From: Simone Onofri <simone@w3.org>
Date: Fri, 13 Sep 2024 09:41:56 +0000
Subject: [PATCH] Merge pull request #36 from verocri/verocri-patch-1

SHA: 91124ac3f3e1eb954b146036bb0f746bd2470ee4
Reason: push, by simoneonofri

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
---
 index.html | 24 ++++++++++++------------
 1 file changed, 12 insertions(+), 12 deletions(-)

diff --git a/index.html b/index.html
index edbcff2..49e4782 100644
--- a/index.html
+++ b/index.html
@@ -8,7 +8,7 @@
   <meta content="Bikeshed version 82ce88815, updated Thu Sep 7 16:33:55 2023 -0700" name="generator">
   <link href="https://www.w3.org/reports/identity-web-impact/" rel="canonical">
   <link href="https://www.w3.org/2008/site/images/favicon.ico" rel="icon">
-  <meta content="9afdccb5467986357e1f7a53c245f95124724d79" name="document-revision">
+  <meta content="91124ac3f3e1eb954b146036bb0f746bd2470ee4" name="document-revision">
 <style>/* Boilerplate: style-autolinks */
 .css.css, .property.property, .descriptor.descriptor {
     color: var(--a-normal-text);
@@ -413,7 +413,7 @@
   <div class="head">
    <p data-fill-with="logo"><a class="logo" href="https://www.w3.org/"> <img alt="W3C" height="48" src="https://www.w3.org/StyleSheets/TR/2021/logos/W3C" width="72"> </a> </p>
    <h1 class="p-name no-ref" id="title">Identity &amp; the Web</h1>
-   <p id="w3c-state"><time class="dt-updated" datetime="2024-09-04">4 September 2024</time></p>
+   <p id="w3c-state"><time class="dt-updated" datetime="2024-09-13">13 September 2024</time></p>
    <details open>
     <summary>More details about this document</summary>
     <div data-fill-with="spec-metadata">
@@ -780,24 +780,24 @@ <h5 class="heading settled" data-level="3.3.1.3" id="credential-layer"><span cla
    <p>The actors exchange:</p>
    <ul>
     <li data-md>
-     <p><strong>Verifiable Credential (VC)</strong>: When the Issuer sends them to the Holder, who then stores it in their Wallet. Credential is called <em>Verifiable</em> because has <em>technologies, such as digital signatures, makes verifiable credentials more tamper-evident and more trustworthy than their physical counterparts</em>.</p>
+     <p><strong>Verifiable Credential (VC)</strong>: When the Issuer sends them to the Holder, who then stores it in their Wallet. The word <em>Verifiable</em> refers to the characteristic of a credential (or presentation) as being able to be verified (though cryptographic mechanisms) by a <em>Verifier</em>. The addition of technologies, such as digital signatures, makes verifiable credentials more tamper-evident and more trustworthy than their physical counterparts.</p>
      <ul>
       <li data-md>
-       <p><strong>Metadata</strong>: of the Credentials.</p>
+       <p><strong>Metadata</strong>: of the Credentials, to describe properties such as the <em>Issuer</em>, the expiry date and time, a representative image, the <em>Issuer</em> public key to use for verification purposes, the revocation mechanism, and so on.</p>
       <li data-md>
        <p><strong>Claim(s)</strong>: one or more assertions where a characteristic of a subject is described (e.g., the subject is a citizen of a certain state, was born in a certain place on a certain day, month, and year, and can drive cars of this type).</p>
       <li data-md>
-       <p><strong>Proof(s)</strong>: cryptographic proof of the integrity of the credential, typically via a digital signature.</p>
+       <p><strong>Proof(s)</strong>: cryptographic proof of the integrity and the authenticity of the credential, typically via a digital signature. The proof is generated by the Issuer.</p>
      </ul>
     <li data-md>
-     <p><strong>Verifiable Presentation (VP)</strong>: When the Holder sends a credential to the Verifier, which then verifies it. The basic case is to present the credential as is. However, in many scenarios, the holder may wish to present only a subset of the credential claims to the verifier - called <em>Selective Disclosure (SD)</em> - or a combination of information from different credentials. It contains:</p>
+     <p><strong>Verifiable Presentation (VP)</strong>: When the Holder sends a credential to the Verifier, which then verifies it. VC are used to present claims to a Verifier by proving control over credentials that certify them. The basic case is to present the credential as is. However, in many scenarios, the holder may wish to present only a subset of the credential claims to the verifier - this mechanism is called <em>Selective Disclosure (SD)</em> - or a combination of information from different credentials. It may contain:</p>
      <ul>
       <li data-md>
-       <p><strong>Metadata</strong>: of the presentation.</p>
+       <p><strong>Metadata</strong>: of the Presentation, including the <em>Issuer</em> public key to use for verification purposes.</p>
       <li data-md>
-       <p><strong>Credential(s)</strong>: information derived or combined from one or more credentials.</p>
+       <p><strong>Credential(s)</strong>: information derived or combined from one or more credentials. If <em>Selective Disclosure</em> is adopted, no credentials are shown, but only a subset of the credential claims.</p>
       <li data-md>
-       <p><strong>Proof(s)</strong>: cryptographic proof of the integrity of the credential(s) and the presentation.</p>
+       <p><strong>Proof(s)</strong>: cryptographic proof of the integrity and authenticity of the presentation. The proof is generated by the Holder. It consists in a proof of knowledge of a credential certifying the (dislosed) credential claims. If <em>Selective Disclosure</em> is adopted, the proof is obtained through the use of a cryptographic zero-knowledge proof.</p>
      </ul>
    </ul>
    <p class="note" role="note"><span class="marker">Note:</span> Refer to Ivan Herman’s <a href="https://www.w3.org/TR/vc-overview/">W3C Verifiable Credentials Overview</a> for a comprehensive overview of Verifiable Credentials.</p>
@@ -808,7 +808,7 @@ <h5 class="heading settled" data-level="3.3.1.4" id="agents-and-infrastructure">
    <h5 class="heading settled" data-level="3.3.1.5" id="identifiers-and-namespaces"><span class="secno">3.3.1.5. </span><span class="content">Layer 1: Identifiers and Namespaces</span><a class="self-link" href="#identifiers-and-namespaces"></a></h5>
    <p>At this level, we find identifiers and the Verifiable Data Registry (VDR), where referenced information is written, updated, read, and deleted.</p>
    <p>As identifiers, we mainly refer to the <strong>Decentralized Identifiers (DIDs)</strong>, a new Uniform Resource Identifier (URI) <a data-link-type="biblio" href="#biblio-rfc3986" title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</a> type that allows entities and resources to be identified. DIDs, along with Verifiable Credentials, are considered one of the two pillars of decentralized models —</p>
-   <p>DIDs provide for different methods of referencing resources <a data-link-type="biblio" href="#biblio-did-core" title="Decentralized Identifiers (DIDs) v1.0">[did-core]</a>, called methods. These methods can rely on various technologies, including blockchains such as Bitcoin or Ethereum, the web, InterPlanetary File System (IPFS), and Domain Name System (DNS) <a data-link-type="biblio" href="#biblio-did-spec-registries" title="DID Specification Registries">[did-spec-registries]</a>, and it is possible to write your method.</p>
+   <p>DIDs provide for different methods of referencing resources <a data-link-type="biblio" href="#biblio-did-core" title="Decentralized Identifiers (DIDs) v1.0">[did-core]</a>, called methods. These methods can rely on various technologies, including blockchains such as Bitcoin or Ethereum, the web, InterPlanetary File System (IPFS), and Domain Name System (DNS) <a data-link-type="biblio" href="#biblio-did-spec-registries" title="Decentralized Identifier Extensions">[did-spec-registries]</a>, and it is possible to write your method.</p>
    <p>Some distinctive properties of DIDs are <a data-link-type="biblio" href="#biblio-did-intro" title="Introduction to Decentralized Identifiers (DID)">[did-intro]</a>:</p>
    <ul>
     <li data-md>
@@ -1173,7 +1173,7 @@ <h3 class="no-num no-ref heading settled" id="informative"><span class="content"
    <dt id="biblio-did-intro">[DID-INTRO]
    <dd><a href="https://www.youtube.com/watch?v=t8lMCmjPKq4"><cite>Introduction to Decentralized Identifiers (DID)</cite></a>. URL: <a href="https://www.youtube.com/watch?v=t8lMCmjPKq4">https://www.youtube.com/watch?v=t8lMCmjPKq4</a>
    <dt id="biblio-did-spec-registries">[DID-SPEC-REGISTRIES]
-   <dd>Manu Sporny. <a href="https://w3c.github.io/did-spec-registries/"><cite>DID Specification Registries</cite></a>. URL: <a href="https://w3c.github.io/did-spec-registries/">https://w3c.github.io/did-spec-registries/</a>
+   <dd>Manu Sporny. <a href="https://w3c.github.io/did-extensions/"><cite>Decentralized Identifier Extensions</cite></a>. URL: <a href="https://w3c.github.io/did-extensions/">https://w3c.github.io/did-extensions/</a>
    <dt id="biblio-digital-identities">[DIGITAL-IDENTITIES]
    <dd><a href="https://wicg.github.io/digital-identities/"><cite>Digital Credentials</cite></a>. Draft Community Group Report. URL: <a href="https://wicg.github.io/digital-identities/">https://wicg.github.io/digital-identities/</a>
    <dt id="biblio-digital-identity-explainer">[DIGITAL-IDENTITY-EXPLAINER]
@@ -1195,7 +1195,7 @@ <h3 class="no-num no-ref heading settled" id="informative"><span class="content"
    <dt id="biblio-evolution-toip">[EVOLUTION-TOIP]
    <dd><a href="https://trustoverip.org/wp-content/uploads/Evolution-of-the-ToIP-Stack-V1.0-2022-11-14.pdf"><cite>Evolution of the ToIP Stack</cite></a>. URL: <a href="https://trustoverip.org/wp-content/uploads/Evolution-of-the-ToIP-Stack-V1.0-2022-11-14.pdf">https://trustoverip.org/wp-content/uploads/Evolution-of-the-ToIP-Stack-V1.0-2022-11-14.pdf</a>
    <dt id="biblio-fedcm">[FEDCM]
-   <dd><a href="https://fedidcg.github.io/FedCM/"><cite>Federated Credential Management API</cite></a>. Draft Community Group Report. URL: <a href="https://fedidcg.github.io/FedCM/">https://fedidcg.github.io/FedCM/</a>
+   <dd>Nicolas Pena Moreno. <a href="https://w3c-fedid.github.io/FedCM/"><cite>Federated Credential Management API</cite></a>. URL: <a href="https://w3c-fedid.github.io/FedCM/">https://w3c-fedid.github.io/FedCM/</a>
    <dt id="biblio-harms-modeling">[HARMS-MODELING]
    <dd><a href="https://learn.microsoft.com/en-us/azure/architecture/guide/responsible-innovation/harms-modeling/"><cite>Harms modeling</cite></a>. URL: <a href="https://learn.microsoft.com/en-us/azure/architecture/guide/responsible-innovation/harms-modeling/">https://learn.microsoft.com/en-us/azure/architecture/guide/responsible-innovation/harms-modeling/</a>
    <dt id="biblio-how-have-passport-photos-changed-in-100-years">[HOW-HAVE-PASSPORT-PHOTOS-CHANGED-IN-100-YEARS]