From 7d96b2a479e60808bb2d773689b87985659fab26 Mon Sep 17 00:00:00 2001 From: Markus Sabadello Date: Tue, 3 Dec 2024 21:06:23 +0100 Subject: [PATCH] Fix HTML structure (#101) * Move paragraphs to valid places in the HTML structure. * Fix nested ordered list. --- index.html | 38 ++++++++++++++++++++------------------ 1 file changed, 20 insertions(+), 18 deletions(-) diff --git a/index.html b/index.html index ea85a98..1ffb832 100644 --- a/index.html +++ b/index.html @@ -1055,13 +1055,6 @@

Dereferencing the Primary Resource

  • Return the output service endpoint URL.
    • - -

    There have been discussions whether in addition to the DID parameter service, - there could also be a DID parameter serviceType to select services based - on their type rather than ID. - See - comments by Dave Longley about `serviceType`.

    -
  • Otherwise, if the input DID URL contains no DID path and no DID query: 
    did:example:1234
      @@ -1087,6 +1080,12 @@

      Dereferencing the Primary Resource

    +

    There have been discussions whether in addition to the DID parameter service, + there could also be a DID parameter serviceType to select services based + on their type rather than ID. + See + comments by Dave Longley about `serviceType`.

    +
    @@ -1106,11 +1105,6 @@

    Dereferencing the Secondary Resource

    the output service endpoint URL "inherits" the DID fragment of the input DID URL.
  • Return the output service endpoint URL.
    • -

    - This behavior of the DID fragment is analogous to the handling of a fragment in an HTTP URL in the - case when dereferencing it returns an HTTP 3xx (Redirection) response with a - Location header (see section 7.1.2 of [[RFC7231]]. -

  • Otherwise, dereference the secondary resource identified by the DID fragment as defined by the media type ([[RFC2046]]) of the primary resource. For example, if the primary resource is a representation of a DID document with media type application/did+ld+json, then @@ -1118,13 +1112,20 @@

    Dereferencing the Secondary Resource

    JSON-LD 1.1: application/ld+json media type [JSON-LD11].
    • -

    - This use of the DID fragment is consistent with the definition of the fragment identifier in - [[RFC3986]]. It identifies a secondary resource which is a subset of the primary resource - (the DID document). -

    +

    + This use of the DID fragment is consistent with the definition of the fragment identifier in + [[RFC3986]]. It identifies a secondary resource which is a subset of the primary resource + (the DID document). +

    + +

    + This behavior of the DID fragment is analogous to the handling of a fragment in an HTTP URL in the + case when dereferencing it returns an HTTP 3xx (Redirection) response with a + Location header (see section 7.1.2 of [[RFC7231]]. +

    + @@ -1841,7 +1842,7 @@

    HTTP(S) Binding

    ) and/or DID URL dereferencing function (see ) can be executed as follows:

      -
    1. Initialize a request HTTP(S) URL with the DID resolver HTTP(S) endpoint.
      2. +
    2. Initialize a request HTTP(S) URL with the DID resolver HTTP(S) endpoint.
      1. Append the input DID or input DID URL to the request HTTP(S) URL. Certain characters @@ -1852,6 +1853,7 @@

        HTTP(S) Binding

      2. Encode all other resolution options as query parameters in the request HTTP(S) URL.
      +
    3. Execute an HTTP GET request on the request HTTP(S) URL.
    4. Dereference the input DID or input DID URL by executing the DID URL dereferencing algorithm as defined in