icg: sync of docs

.markdownlintignore

@@ -2,4 +2,4 @@ interoperability/algohosting.md
 interoperability/algohostingenv.md
 interoperability/geospatial_explorer.qmd
 interoperability/businessmodel.md
-interoperability/datahosting.md
+interoperability/datahosting.qmd

_quarto.yml

@@ -88,8 +88,6 @@ website:
                   - href: guides/algorithm_services_catalogue_benchmarks.qmd
                   - href: guides/algorithm_catalogue_dashboard.md
                     text: APEx Algorithm Dashboard
-              - href: guides/file_formats.qmd
-                text: File format recommendations
           - section: Admin Guides
             contents:
               - href: guides/account.md
@@ -112,7 +110,7 @@ website:
           - href: interoperability/definitions.qmd
           - href: propagation/service_development.qmd
           - href: interoperability/algohosting.md
-          - href: interoperability/datahosting.md
+          - href: interoperability/datahosting.qmd
           - href: interoperability/algohostingenv.md
           - href: interoperability/geospatial_explorer.qmd
           - href: interoperability/businessmodel.md

interoperability/algohostingenv.md

@@ -17,6 +17,8 @@ The aim of these requirements is:
   technologies and architectures that suit their needs.
 * To allow APEx to perform automated checks on the developed services, guaranteeing that they work and produce the
   expected result at the expected cost.
+* Support the integration of the onboarded services into APEx ecosystem, such as service execution through the
+  [APEx Geospatial Explorer](../instantiation/geospatial_explorer.md).
 
 @tbl-algohostingenv provides an overview of the requirements for operators of algorithm hosting platforms to ensure
 their compatibility with the APEx standards.
@@ -87,6 +89,27 @@ their compatibility with the APEx standards.
       <td>The algorithm hosting platform shall expose process metadata publicly without requiring authentication, unless the nature of the algorithm requires its description to be hidden.</td>
       <td>APEx tools request service metadata for informative purposes, also from browser-based applications that do not have platform tokens available.</td>
     </tr>
+    <tr>
+      <td>HOST-REQ-09</td>
+      <td>The algorithm hosting platform shall support the OAuth 2.0 Token Exchange RFC.</td>
+      <td>
+        <p>The Token Exchange RFC is essential for executing APEx-compliant services on the platform using APEx tooling,
+        such as the [APEx Geospatial Explorer](../instantiation/geospatial_explorer.md).</p>
+        <p>The RFC is automatically accessible when the platform adheres to EOEPCA’s best practices and utilises Keycloak
+        as its primary user management system.</p>
+      </td>
+    </tr>
+    <tr>
+      <td>HOST-REQ-10</td>
+      <td>The algorithm hosting platform shall provide the APEx project with a client ID and secret to support the
+      execution of published services.</td>
+      <td>
+        <p>This client is utilised to execute APEx-compliant services on the platform using APEx tooling, such as the
+        [APEx Geospatial Explorer](../instantiation/geospatial_explorer.md).</p>
+        <p>This client is employed to execute the Token Exchange RFC (HOST-REQ-09) to facilitate the exchange of an
+        APEx-based user token with a user token that is recognized and validated by the platform.</p>
+      </td>
+    </tr>
   </tbody>
 </table>