From 07d65e479ced1dfbe76705bbebdeabe46c636b16 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Niklas=20Lindstr=C3=B6m?= Date: Wed, 14 Jan 2026 19:19:26 +0100 Subject: [PATCH 1/2] Remove `` and `` markup --- index.html | 185 +++++++++++++++++++++-------------------------------- 1 file changed, 73 insertions(+), 112 deletions(-) diff --git a/index.html b/index.html index 6c6aa58e..e2f7fce7 100644 --- a/index.html +++ b/index.html @@ -1083,7 +1083,7 @@

RDF Serialization/Deserialization

The active context consists of:

-

Each term definition's value consists of:

+

Each term definition's value consists of:

  • an IRI mapping (IRI),
  • a prefix flag (boolean),
    • @@ -1681,10 +1681,10 @@

    Algorithm

  • Set the term definition of term in active context to definition and the value associated with defined's entry term to - true and return.
    • + true. -
  • Otherwise, ifIf value contains the entry @id and its value +
  • Otherwise, if value contains the entry @id and its value does not equal term:
    1. If the @id entry of value @@ -2016,11 +2016,9 @@

      Algorithm

      If the active context has a default language, set default language to the default language from the active context normalized to lower case. - - If the active context has a default base direction, - concatenate its value to default language, - separated by an underscore (`"_"`). - + If the active context has a default base direction, + concatenate its value to default language, + separated by an underscore (`"_"`).
    2. For each key term and value term definition in the active context, ordered by shortest term @@ -2133,32 +2131,11 @@

      Algorithm

  • - (this step was removed by a candidate correction) - - Otherwise, if active context has a - default base direction: -
      -
    1. Initialize a variable lang dir - with the concatenation of default language and default base direction, - separate by an underscore (`"_"`), - normalized to lower case.
      2. -
    2. If language map does not have a lang dir entry, - create one and set its value to the term - being processed.
      3. -
    3. If language map does not have an `@none` entry, - create one and set its value to the term - being processed.
      4. -
    4. If type map does not have an `@none` entry, - create one and set its value to the term - being processed.
      5. -
    -     + (this step was removed by a candidate correction)
  • Otherwise:
      -
    1. If language map does not have a default language entry, - (after being normalized to lower case), - +
    2. If language map does not have a default language entry, create one and set its value to the term being processed.
    3. If language map does not have an @none @@ -3113,15 +3090,11 @@

      Algorithm

      For more information, refer to issue 380.

      Recursively repeat steps - - 3, - 8, - + 3, + 8, 13, and 14 using - - nesting-key for active property, and - + nesting-key for active property, and nested value for element.
      Steps 3 and 8 @@ -3918,7 +3891,7 @@

      Algorithm

      1. Reinitialize container key by IRI compacting - index key after first IRI expanding it.
        2. + index key after first IRI expanding it.
      2. Set map key to the first value of container key in compacted item, if any.
      3. If there are remaining values in compacted item for container key, use add value to @@ -5504,8 +5477,8 @@

        Algorithm

        converted value to true if the lexical form - of value matches "true" or "1", or false - if it matches "false" or "0". + of value matches "true" or "1", or false + if it matches "false" or "0". If it matches neither, set type to xsd:boolean.
        4. @@ -5515,30 +5488,30 @@

        Algorithm

        xsd:double and its lexical form is a valid xsd:integer or xsd:double - according to [[XMLSCHEMA11-2]], - set converted value - to the result of converting the - lexical form - to a JSON number. - : -
          -
        1. - Attempt to convert the lexical form to a JSON number - according to the - [[RFC8785]] - JSON Serialization Scheme (JCS) 3.2.2.3 Serialization of Numbers - procedure. -
          2. -
        2. - If the conversion is successful, set converted value - to its result. -
          3. -
        3. - Otherwise, set type to datatype IRI - of value. -
          4. -
        -         + according to [[XMLSCHEMA11-2]], + set converted value + to the result of converting the + lexical form + to a JSON number. + : +
          +
        1. + Attempt to convert the lexical form to a JSON number + according to the + [[RFC8785]] + JSON Serialization Scheme (JCS) 3.2.2.3 Serialization of Numbers + procedure. +
          2. +
        2. + If the conversion is successful, set converted value + to its result. +
          3. +
        3. + Otherwise, set type to datatype IRI + of value. +
          4. +
        +
      4. @@ -5788,11 +5761,11 @@

      Algorithm

      For more information, refer to issue 605.

      -

      Methods resolving a {{Promise}} with the internal representation +

      Methods resolving a {{Promise}} with the internal representation MUST either map it to the datatype used by the implementation, as described in , or serialize it to JSON (or another appropriate serialization format) - as described in .

       + as described in .

             /*
@@ -5898,9 +5871,7 @@ 
      Algorithm
      
                 to the provided context.
    • -
  • Resolve the promise with compacted output - transforming compacted output from the - internal representation to a JSON serialization.
    • +
  • Resolve the promise with compacted output.
    • @@ -5986,9 +5957,7 @@

    Algorithm

    set expanded output to an array containing only expanded output. -
  • Resolve the promise with expanded output - transforming expanded output from the - internal representation to a JSON serialization.
    • +
  • Resolve the promise with expanded output.
    • @@ -6050,9 +6019,7 @@

    Algorithm

    otherwise to null. -
  • Resolve the promise with flattened output - transforming flattened output from the - internal representation to a JSON serialization.
    • +
  • Resolve the promise with flattened output.
    • @@ -6090,9 +6057,7 @@

    Algorithm

    Serialize RDF as JSON-LD Algorithm method using dataset and options. -
  • Resolve the promise with expanded result - transforming expanded output from the - internal representation to a JSON serialization.
    • +
  • Resolve the promise with expanded result.
    • @@ -6127,8 +6092,8 @@

    Algorithm

    expand() method using input and options - with {{JsonLdOptions/ordered}} set to false, - and {{JsonLdOptions/extractAllScripts}} defaulting to true. + with {{JsonLdOptions/ordered}} set to false, + and {{JsonLdOptions/extractAllScripts}} defaulting to true.
  • Create a new RdfDataset dataset.
  • Create a new map node map.
  • Invoke the Node Map Generation algorithm, @@ -6283,37 +6248,34 @@

    Internal Representation in Implementations

    Serialization and Deserialization

    - - -

    This section defines the requirements for serializing and deserializing - JSON from and to the internal representation, as appropriate, - based on the provided or requested Content-Type. - A Content-Type of application/json, - or media type with a +json suffix as defined in [[RFC6839]] - MUST serialize or deserialize to a format consistent with the JSON Grammar - as specified in [[RFC8259]].

    +

    This section defines the requirements for serializing and deserializing + JSON from and to the internal representation, as appropriate, + based on the provided or requested Content-Type. + A Content-Type of application/json, + or media type with a +json suffix as defined in [[RFC6839]] + MUST serialize or deserialize to a format consistent with the JSON Grammar + as specified in [[RFC8259]].

    -

    This specification does not define serializations of the internal representation - for other media types, which may be defined by other specifications.

    +

    This specification does not define serializations of the internal representation + for other media types, which may be defined by other specifications.

    -

    See - for details on extracting JSON from HTML.

    +

    See + for details on extracting JSON from HTML.

    -
    -
    To transform a JSON-conforming string [[RFC8259]],
    -
    - deserialize into the - internal representation as described in {{LoadDocumentCallback}}; -
    +
    +
    To transform a JSON-conforming string [[RFC8259]],
    +
    + deserialize into the + internal representation as described in {{LoadDocumentCallback}}; +
    -
    To transform the internal representation to a JSON-LD document -
    -
    - serialize to JSON [[RFC8259]] using an appropriate serializer (e.g., - [[ECMASCRIPT]] [=ToString=]); -
    -
    - +
    To transform the internal representation to a JSON-LD document +
    +
    + serialize to JSON [[RFC8259]] using an appropriate serializer (e.g., + [[ECMASCRIPT]] [=ToString=]); +
    +
    @@ -6623,12 +6585,11 @@

    LoadDocumentCallback

    The HTTP Link Header is ignored for documents served as application/ld+json, text/html, or application/xhtml+xml.

    • -
  • Otherwise, if the retrieved document's Content-Type is neither +
  • Otherwise, if the retrieved document's Content-Type is neither application/json, application/ld+json, nor any other media type using a - +json suffix as defined in [[RFC6839]]. - Reject, then reject + +json suffix as defined in [[RFC6839]], then reject the promise passing a loading document failed error.
    Candidate Correction 6 From 923ceab59fac3c5fdf7bcddfe07218c12d34f8d6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Niklas=20Lindstr=C3=B6m?= Date: Fri, 16 Jan 2026 16:21:53 +0100 Subject: [PATCH 2/2] Apply suggestion from @davidlehn Co-authored-by: David I. Lehn --- index.html | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/index.html b/index.html index e2f7fce7..93bea958 100644 --- a/index.html +++ b/index.html @@ -5488,12 +5488,7 @@

    Algorithm

    xsd:double and its lexical form is a valid xsd:integer or xsd:double - according to [[XMLSCHEMA11-2]], - set converted value - to the result of converting the - lexical form - to a JSON number. - : + according to [[XMLSCHEMA11-2]]:
    1. Attempt to convert the lexical form to a JSON number