Deploy to GitHub pages

wallet-instance-lifecycle/en/_sources/wallet-attestation.rst.txt

@@ -483,13 +483,13 @@ Wallet Instance Lifecycle
 -----------------------------
 
 The ability of the Wallet Instance to obtain a Wallet Attestation is bound to its current state. 
-The Wallet Instance calculates its current state based on its local credentials storage and its revocation state on the Wallet Provider's backend, if present.
+The Wallet Instance assesses its current state based on the Credentials stored locally and the Wallet Attestation issued by the Wallet Provider.
 
-The Wallet Instance lifecycle defines all possible states a Wallet Instance can be in, as well as the transitions between them. The Wallet Instance lifecycle is illustrated in the following diagram:
+The lifecycle of a Wallet Instance encompasses all the potential states it can configure, along with the transitions from one state to another. This lifecycle is depicted in the diagram below:
 
 .. figure:: ../../images/wallet_instance_lifecycle.svg
    :name: Wallet Instance Lifecycle
-   :alt: The image illustrates the Wallet Instance lifecycle, with the states explained below.
+   :alt: Illustration representing the Wallet Instance lifecycle, with the states explained below.
    :target: https://www.plantuml.com/plantuml/uml/SoWkIImgAStDuOhMYbNGrRLJyCm32kNafAPOAMH2c5mAG00N1YloBqWjIYp9pCzBpB5IA4ijoaoh1Ab25WUh2qlCoKm1gW1HYIMf83KGCKnJClDmg799JKmkoIm3IW1DAaejoyzEHRSBfpfCbmEzQQLGceVaDOH6x4emxS9KWd0mfgH3QbuAC801
 
 
@@ -511,21 +511,24 @@ States
 
 Transitions
 ~~~~~~~~~~~~~~~~~~
-+--------------+--------------------------------------------------------------------------------------------------------------+
-| Transition   | Description                                                                                                  |
-+==============+==============================================================================================================+
-| `install`    | The Holder performs a fresh installation or restore the initial state of the Wallet Instance on the device   |
-+--------------+--------------------------------------------------------------------------------------------------------------+
-| `verify`     | The Wallet Instance has been verified by the Wallet Provider and its Wallet Hardware Key has been registered |
-+--------------+--------------------------------------------------------------------------------------------------------------+
-| `validate`   | The Wallet Instance obtains a valid PID                                                                      |
-+--------------+--------------------------------------------------------------------------------------------------------------+
-| `invalidate` | The PID expires or gets revoked                                                                              |
-+--------------+--------------------------------------------------------------------------------------------------------------+
-| `revoke`     | The Wallet Provider marks the Wallet Instance as not usable                                                  |
-+--------------+--------------------------------------------------------------------------------------------------------------+
-| `uninstall`  | The Holder removes the Wallet Instance from the device                                                       |
-+--------------+--------------------------------------------------------------------------------------------------------------+
+.. list-table::
+   :widths: 20 60
+   :header-rows: 1
+
+   * - **Transition**
+     - **Description**
+   * - `install`
+     - The User performs a fresh installation or restores the initial state of the Wallet Instance on the device.
+   * - `verify`
+     - The Wallet Instance has been verified by the Wallet Provider and its Wallet Hardware Key has been registered.
+   * - `validate`
+     - The Wallet Instance obtains a valid PID.
+   * - `invalidate`
+     - The PID expires or gets revoked.
+   * - `revoke`
+     - The Wallet Provider marks the Wallet Instance as not usable.
+   * - `uninstall`
+     - The User removes the Wallet Instance from the device.
 
 Revocations
 ~~~~~~~~~~~~~~~~~~
@@ -534,8 +537,8 @@ The Wallet Provider, which holds the Wallet Hardware Keys, can mark them as *rev
 
 The details of the revocation mechanism used by the Wallet Provider as well as the data model for maintaining the Wallet Instance references is delegated to the Wallet Provider's implementation.
 
-During the *Wallet Instance initialization and registration* phase the Wallet Provider may associate the Wallet Instance with a specific Holder uniquely identified within the Wallet Provider's systems as well as with metadata regarding the device the Wallet Instance is running on such as operative system version, chipset capabilities and the Wallet Solution version. 
-These informations can allow the Wallet Provider to selectively revoke Wallet Instances based on specific criteria.
+During the *Wallet Instance initialization and registration* phase the Wallet Provider MAY associate the Wallet Instance with a specific User. The User SHOULD be uniquely identified as well as with metadata regarding the device the Wallet Instance is running on, the metadata MAY include data related to the operative system and general technical capabilities of the device. 
+These information allow the User to request the Wallet revocation directly interacting with the Wallet Provider as well as enabling the Wallet Provider to revoke a specific Wallet Instance.
 
 The choice of which data need to be stored is left to the Wallet Provider.
 

wallet-instance-lifecycle/en/wallet-attestation.html

@@ -1521,10 +1521,10 @@ <h3>Wallet Attestation Issuance<a class="headerlink" href="#wallet-attestation-i
 <section id="wallet-instance-lifecycle">
 <h2>Wallet Instance Lifecycle<a class="headerlink" href="#wallet-instance-lifecycle" title="Permalink to this heading">¶</a></h2>
 <p>The ability of the Wallet Instance to obtain a Wallet Attestation is bound to its current state.
-The Wallet Instance calculates its current state based on its local credentials storage and its revocation state on the Wallet Provider's backend, if present.</p>
-<p>The Wallet Instance lifecycle defines all possible states a Wallet Instance can be in, as well as the transitions between them. The Wallet Instance lifecycle is illustrated in the following diagram:</p>
+The Wallet Instance assesses its current state based on the Credentials stored locally and the Wallet Attestation issued by the Wallet Provider.</p>
+<p>The lifecycle of a Wallet Instance encompasses all the potential states it can configure, along with the transitions from one state to another. This lifecycle is depicted in the diagram below:</p>
 <figure class="align-default" id="id3">
-<a class="reference external image-reference" href="https://www.plantuml.com/plantuml/uml/SoWkIImgAStDuOhMYbNGrRLJyCm32kNafAPOAMH2c5mAG00N1YloBqWjIYp9pCzBpB5IA4ijoaoh1Ab25WUh2qlCoKm1gW1HYIMf83KGCKnJClDmg799JKmkoIm3IW1DAaejoyzEHRSBfpfCbmEzQQLGceVaDOH6x4emxS9KWd0mfgH3QbuAC801"><img alt="The image illustrates the Wallet Instance lifecycle, with the states explained below." src="../../images/wallet_instance_lifecycle.svg" /></a>
+<a class="reference external image-reference" href="https://www.plantuml.com/plantuml/uml/SoWkIImgAStDuOhMYbNGrRLJyCm32kNafAPOAMH2c5mAG00N1YloBqWjIYp9pCzBpB5IA4ijoaoh1Ab25WUh2qlCoKm1gW1HYIMf83KGCKnJClDmg799JKmkoIm3IW1DAaejoyzEHRSBfpfCbmEzQQLGceVaDOH6x4emxS9KWd0mfgH3QbuAC801"><img alt="Illustration representing the Wallet Instance lifecycle, with the states explained below." src="../../images/wallet_instance_lifecycle.svg" /></a>
 </figure>
 <p>A Wallet Instance can obtain a Wallet Attestation if it's in either <cite>Installed</cite>, <cite>Operational</cite> or <cite>Valid</cite> state; that implies that a <cite>Deactivated</cite> Wallet Instance cannot obtain a Wallet Attestation hence it cannot interact with other entities such as PID/(Q)EAA Providers and Relying Parties.</p>
 <section id="states">
@@ -1554,29 +1554,33 @@ <h3>States<a class="headerlink" href="#states" title="Permalink to this heading"
 <section id="transitions">
 <h3>Transitions<a class="headerlink" href="#transitions" title="Permalink to this heading">¶</a></h3>
 <table class="docutils align-default">
+<colgroup>
+<col style="width: 25%" />
+<col style="width: 75%" />
+</colgroup>
 <thead>
-<tr class="row-odd"><th class="head"><p>Transition</p></th>
-<th class="head"><p>Description</p></th>
+<tr class="row-odd"><th class="head"><p><strong>Transition</strong></p></th>
+<th class="head"><p><strong>Description</strong></p></th>
 </tr>
 </thead>
 <tbody>
 <tr class="row-even"><td><p><cite>install</cite></p></td>
-<td><p>The Holder performs a fresh installation or restore the initial state of the Wallet Instance on the device</p></td>
+<td><p>The User performs a fresh installation or restores the initial state of the Wallet Instance on the device.</p></td>
 </tr>
 <tr class="row-odd"><td><p><cite>verify</cite></p></td>
-<td><p>The Wallet Instance has been verified by the Wallet Provider and its Wallet Hardware Key has been registered</p></td>
+<td><p>The Wallet Instance has been verified by the Wallet Provider and its Wallet Hardware Key has been registered.</p></td>
 </tr>
 <tr class="row-even"><td><p><cite>validate</cite></p></td>
-<td><p>The Wallet Instance obtains a valid PID</p></td>
+<td><p>The Wallet Instance obtains a valid PID.</p></td>
 </tr>
 <tr class="row-odd"><td><p><cite>invalidate</cite></p></td>
-<td><p>The PID expires or gets revoked</p></td>
+<td><p>The PID expires or gets revoked.</p></td>
 </tr>
 <tr class="row-even"><td><p><cite>revoke</cite></p></td>
-<td><p>The Wallet Provider marks the Wallet Instance as not usable</p></td>
+<td><p>The Wallet Provider marks the Wallet Instance as not usable.</p></td>
 </tr>
 <tr class="row-odd"><td><p><cite>uninstall</cite></p></td>
-<td><p>The Holder removes the Wallet Instance from the device</p></td>
+<td><p>The User removes the Wallet Instance from the device.</p></td>
 </tr>
 </tbody>
 </table>
@@ -1586,8 +1590,8 @@ <h3>Revocations<a class="headerlink" href="#revocations" title="Permalink to thi
 <p>As mentioned in the <em>Wallet Instance initialization and registration</em> section above, a Wallet Instance is bound to a Wallet Hardware Key and it's uniquely identified by it.
 The Wallet Provider, which holds the Wallet Hardware Keys, can mark them as <em>revoked</em> so to make the related Wallet Instance unusable.</p>
 <p>The details of the revocation mechanism used by the Wallet Provider as well as the data model for maintaining the Wallet Instance references is delegated to the Wallet Provider's implementation.</p>
-<p>During the <em>Wallet Instance initialization and registration</em> phase the Wallet Provider may associate the Wallet Instance with a specific Holder uniquely identified within the Wallet Provider's systems as well as with metadata regarding the device the Wallet Instance is running on such as operative system version, chipset capabilities and the Wallet Solution version.
-These informations can allow the Wallet Provider to selectively revoke Wallet Instances based on specific criteria.</p>
+<p>During the <em>Wallet Instance initialization and registration</em> phase the Wallet Provider MAY associate the Wallet Instance with a specific User. The User SHOULD be uniquely identified as well as with metadata regarding the device the Wallet Instance is running on, the metadata MAY include data related to the operative system and general technical capabilities of the device.
+These information allow the User to request the Wallet revocation directly interacting with the Wallet Provider as well as enabling the Wallet Provider to revoke a specific Wallet Instance.</p>
 <p>The choice of which data need to be stored is left to the Wallet Provider.</p>
 </section>
 </section>