breaking-change: universal links are not used

docs/en/remote-flow.rst

@@ -106,7 +106,7 @@ A non-normative example of the HTTP request is represented below:
   Content-Type: application/json
 
   {
-      "authorization_endpoint": "https://wallet-solution.digital-strategy.europa.eu/authorization",
+      "authorization_endpoint": "openid4vp:",
       "response_types_supported": [
         "vp_token"
       ],
@@ -160,7 +160,7 @@ Below a non-normative example of the response containing the required parameters
 
 .. code-block:: javascript
 
-  https://wallet-solution.digital-strategy.europa.eu/authorization?client_id=...&request_uri=...&client_id_scheme=entity_id&request_uri_method=post
+  openid4vp://?client_id=...&request_uri=...&client_id_scheme=entity_id&request_uri_method=post
 
 The value corresponding to the `request_uri` endpoint SHOULD be randomized, according to `RFC 9101, The OAuth 2.0 Authorization Framework: JWT-Secured Authorization Request (JAR) <https://www.rfc-editor.org/rfc/rfc9101.html#section-5.2.1>`_ Section 5.2.1.
 
@@ -170,7 +170,7 @@ In the **Same Device Flow** the Relying Party uses an HTTP response redirect (wi
 .. code:: text
 
     HTTP/1.1 /authorization Found
-    Location: https://wallet-solution.digital-strategy.europa.eu?
+    Location: openid4vp://?
     client_id=https%3A%2F%2Frelying-party.example.org%2Fcb
     &request_uri=https%3A%2F%2Frelying-party.example.org%2Frequest_uri
     &client_id_scheme=entity_id
@@ -190,7 +190,7 @@ Below is represented a non-normative example of the QR Code raw payload:
 
 .. code-block:: text
 
-  https://wallet-solution.digital-strategy.europa.eu/authorization?client_id=https%3A%2F%2Frelying-party.example.org&request_uri=https%3A%2F%2Frelying-party.example.org&client_id_scheme=entity_id&request_uri_method=post
+  openid4vp://?client_id=https%3A%2F%2Frelying-party.example.org&request_uri=https%3A%2F%2Frelying-party.example.org&client_id_scheme=entity_id&request_uri_method=post
 
 .. note::
     The *error correction level* chosen for the QR Code MUST be Q (Quartily - up to 25%), since it offers a good balance between error correction capability and data density/space. This level of quality and error correction allows the QR Code to remain readable even if it is damaged or partially obscured.