Deploy to GitHub pages

refs/pull/400/merge/en/_sources/remote-flow.rst.txt

@@ -440,7 +440,7 @@ Where the following parameters are used:
       - The requested Digital Credential (one or more, in format of SD-JWT VC or MDOC CBOR)
       - The Wallet Attestation
   * - **presentation_submission**
-    - JSON Object containing the mappings between the requested Verifiable Credentials and where to find them within the returned Verifiable Presentation Token, according to the `Presentation Exchange <https://identity.foundation/presentation-exchange/spec/v2.0.0/>`_. This is expressed via elements in the ``descriptor_map`` array (Input Descriptor Mapping Objects) that contain a field called ``path``, which MUST have the value $ (top level root path) when only one Verifiable Presentation is contained in the VP Token, and MUST have the value $[n] (indexed path from root) when there are multiple Verifiable Presentations, where ``n`` is the index to select. The Relyingh PArty receiving the `presentation_submission` descriptor therefore is able to use the corred method to decode each credential data format provided withi nthe ``vp_token``.
+    - JSON Object containing the mappings between the requested Verifiable Credentials and where to find them within the returned Verifiable Presentation Token, according to the `Presentation Exchange <https://identity.foundation/presentation-exchange/spec/v2.0.0/>`_. This is expressed via elements in the ``descriptor_map`` array (Input Descriptor Mapping Objects) that contain a field called ``path``, which MUST have the value $ (top level root path) when only one Verifiable Presentation is contained in the VP Token, and MUST have the value $[n] (indexed path from root) when there are multiple Verifiable Presentations, where ``n`` is the index to select. The Relying Party receiving the `presentation_submission` descriptor therefore is able to use the correct method to decode each credential data format provided within the ``vp_token``.
   * - **state**
     - Unique identifier provided by the Relying Party within the Authorization Request.
 

refs/pull/400/merge/en/relying-party-solution.html

@@ -746,7 +746,7 @@ <h3>Authorization Response Details<a class="headerlink" href="#authorization-res
 </td>
 </tr>
 <tr class="row-odd"><td><p><strong>presentation_submission</strong></p></td>
-<td><p>JSON Object containing the mappings between the requested Verifiable Credentials and where to find them within the returned Verifiable Presentation Token, according to the <a class="reference external" href="https://identity.foundation/presentation-exchange/spec/v2.0.0/">Presentation Exchange</a>. This is expressed via elements in the <code class="docutils literal notranslate"><span class="pre">descriptor_map</span></code> array (Input Descriptor Mapping Objects) that contain a field called <code class="docutils literal notranslate"><span class="pre">path</span></code>, which MUST have the value $ (top level root path) when only one Verifiable Presentation is contained in the VP Token, and MUST have the value $[n] (indexed path from root) when there are multiple Verifiable Presentations, where <code class="docutils literal notranslate"><span class="pre">n</span></code> is the index to select. The Relyingh PArty receiving the <cite>presentation_submission</cite> descriptor therefore is able to use the corred method to decode each credential data format provided withi nthe <code class="docutils literal notranslate"><span class="pre">vp_token</span></code>.</p></td>
+<td><p>JSON Object containing the mappings between the requested Verifiable Credentials and where to find them within the returned Verifiable Presentation Token, according to the <a class="reference external" href="https://identity.foundation/presentation-exchange/spec/v2.0.0/">Presentation Exchange</a>. This is expressed via elements in the <code class="docutils literal notranslate"><span class="pre">descriptor_map</span></code> array (Input Descriptor Mapping Objects) that contain a field called <code class="docutils literal notranslate"><span class="pre">path</span></code>, which MUST have the value $ (top level root path) when only one Verifiable Presentation is contained in the VP Token, and MUST have the value $[n] (indexed path from root) when there are multiple Verifiable Presentations, where <code class="docutils literal notranslate"><span class="pre">n</span></code> is the index to select. The Relying Party receiving the <cite>presentation_submission</cite> descriptor therefore is able to use the correct method to decode each credential data format provided within the <code class="docutils literal notranslate"><span class="pre">vp_token</span></code>.</p></td>
 </tr>
 <tr class="row-even"><td><p><strong>state</strong></p></td>
 <td><p>Unique identifier provided by the Relying Party within the Authorization Request.</p></td>

refs/pull/400/merge/en/remote-flow.html

@@ -736,7 +736,7 @@ <h2>Authorization Response Details<a class="headerlink" href="#authorization-res
 </td>
 </tr>
 <tr class="row-odd"><td><p><strong>presentation_submission</strong></p></td>
-<td><p>JSON Object containing the mappings between the requested Verifiable Credentials and where to find them within the returned Verifiable Presentation Token, according to the <a class="reference external" href="https://identity.foundation/presentation-exchange/spec/v2.0.0/">Presentation Exchange</a>. This is expressed via elements in the <code class="docutils literal notranslate"><span class="pre">descriptor_map</span></code> array (Input Descriptor Mapping Objects) that contain a field called <code class="docutils literal notranslate"><span class="pre">path</span></code>, which MUST have the value $ (top level root path) when only one Verifiable Presentation is contained in the VP Token, and MUST have the value $[n] (indexed path from root) when there are multiple Verifiable Presentations, where <code class="docutils literal notranslate"><span class="pre">n</span></code> is the index to select. The Relyingh PArty receiving the <cite>presentation_submission</cite> descriptor therefore is able to use the corred method to decode each credential data format provided withi nthe <code class="docutils literal notranslate"><span class="pre">vp_token</span></code>.</p></td>
+<td><p>JSON Object containing the mappings between the requested Verifiable Credentials and where to find them within the returned Verifiable Presentation Token, according to the <a class="reference external" href="https://identity.foundation/presentation-exchange/spec/v2.0.0/">Presentation Exchange</a>. This is expressed via elements in the <code class="docutils literal notranslate"><span class="pre">descriptor_map</span></code> array (Input Descriptor Mapping Objects) that contain a field called <code class="docutils literal notranslate"><span class="pre">path</span></code>, which MUST have the value $ (top level root path) when only one Verifiable Presentation is contained in the VP Token, and MUST have the value $[n] (indexed path from root) when there are multiple Verifiable Presentations, where <code class="docutils literal notranslate"><span class="pre">n</span></code> is the index to select. The Relying Party receiving the <cite>presentation_submission</cite> descriptor therefore is able to use the correct method to decode each credential data format provided within the <code class="docutils literal notranslate"><span class="pre">vp_token</span></code>.</p></td>
 </tr>
 <tr class="row-even"><td><p><strong>state</strong></p></td>
 <td><p>Unique identifier provided by the Relying Party within the Authorization Request.</p></td>