From 73a1bb054cf9767c573e06afc623466ea53d16b3 Mon Sep 17 00:00:00 2001 From: Pierre-Antoine Champin Date: Fri, 5 Jun 2026 11:47:43 +0200 Subject: [PATCH] finalize the removal of candidate corrections the 'candidate correction' blocks have been removed, and their content transferred to the corresponding changelog entries. A remaining in common/terms.html was also removed. --- index.html | 140 ++++++++++++++++------------------------------------- 1 file changed, 43 insertions(+), 97 deletions(-) diff --git a/index.html b/index.html index 2860eaf5..2824baf2 100644 --- a/index.html +++ b/index.html @@ -312,10 +312,6 @@

This specification is intended to supersede the [[[JSON-LD10-API]]] [[JSON-LD10-API]] specification.

-

- This document includes Candidate Corrections to the current - W3C Recommendation dated 16 July 2020.

-

Set of Documents

This document is one of three JSON-LD 1.2 Recommendations produced by the @@ -1075,15 +1071,6 @@

RDF Serialization/Deserialization

using information provided by the active context. This section describes how to produce an active context.

-
- Candidate Correction 8 -

Change the type of term definition from array to map in active context, - to be consistent with the way it is used in the algorithms. - Clarify the notion of "term definition". - For more information, refer to issue 630. -

-
-

The active context consists of:

  • the active term definitions which specify how @@ -1647,11 +1634,6 @@

    Algorithm

  • If value contains the entry @reverse: -
    - Candidate Correction 3 -

    This changes the algorithm for processing a reverse term so that it doesn't return early. - For more information, refer to issue 565.

    -
    1. If value contains @id or @nest, entries, an invalid reverse property @@ -2008,14 +1990,6 @@

      Algorithm

      1. Initialize result to an empty map.
      2. -
        - Candidate Correction 8 -

        Simplify the algorithm by handling the default base direction - once and for all in this step, rather than in each iteration. - For more information, refer to issue 633. -

        -
        - Initialize default language to @none. If the active context has a default language, set default language to the default language from the active context @@ -2134,9 +2108,6 @@

        Algorithm

        being processed.
      2. -
    2. - (this step was removed by a candidate correction) -
    3. Otherwise:
      1. If language map does not have a default language entry, @@ -3087,12 +3058,6 @@

        Algorithm

        invalid @nest value error has been detected and processing is aborted.
      2. -
        - Candidate Correction 1 -

        This algorithm step omitted two additional steps - which include nesting-key in addition to nested value. - For more information, refer to issue 380.

        -
        Recursively repeat steps 3, 8, @@ -3887,12 +3852,6 @@

        Algorithm

        set map key to the value of @index in expanded item, if any.
      3. Otherwise, if container includes @index and index key is not @index: -
        - Candidate Correction 2 -

        The value of `@index` on a property map can be a Compact IRI in addition to an IRI. - The Compaction Algorithm is updated to first expand this value before re-compacting it. - For more information, refer to issue 380.

        -
        1. Reinitialize container key by IRI compacting index key after first IRI expanding it.
          2. @@ -5462,12 +5421,6 @@

          Algorithm

        2. Initialize converted value to value.
        3. Initialize type to null
        4. If useNativeTypes is true -
          - Candidate Correction 5 -

          This changes behavior when using native numbers where useNativeTypes is `true`. - For more information, refer to issue 555. -

          -
          1. If the datatype IRI @@ -5742,24 +5695,6 @@

            Algorithm

            is used instead of looking at the HTTP Link Header directly. For the sake of simplicity, none of the algorithms in this document mention this directly.

            -
            - Candidate Correction 7 -

            Details about transforming to and from a given serialization format - have been abstracted so that other specifications can define - serialization and deserialization requirements for their specific formats. - The algorithm is now more explicit about serializing and deserializing - to the internal representation. - See marked changes here and in the following locations:

            - -

            For more information, refer to issue 605.

            -
            -

            Methods resolving a {{Promise}} with the internal representation MUST either map it to the datatype used by the implementation, as described in , @@ -6077,13 +6012,6 @@

            Algorithm

            Transforms the given input into an RdfDataset according to the steps in the Deserialize JSON-LD to RDF Algorithm:

            -
            - Candidate Correction 4 -

            This changes the default for extractAllScripts to be `false`, - which is consistent with the wording in Embedding JSON-LD in HTML Documents in [[JSON-LD11]]. - For more information, refer to issue 603.

            -
            -
            1. Create a new {{Promise}} promise and return it. The following steps are then deferred.
              2. @@ -6590,13 +6518,6 @@

              LoadDocumentCallback

              nor any other media type using a +json suffix as defined in [[RFC6839]], then reject the promise passing a loading document failed error. -
              - Candidate Correction 6 -

              This changes corrects the processing by not assuming that the - Content-Type is for JSON, but making processing conditional - on that Content-Type. - For more information, refer to issue 622.

              -
            2. Create a new RemoteDocument remote document using url as {{RemoteDocument/documentUrl}}, @@ -7052,20 +6973,23 @@

              Change log

              -
            3. 2020-02-23: Added some clarifications to - as described in Candidate Correction 1.
              4. +
            4. 2020-02-23: Added some clarifications to . + For more information, refer to issue 380. +
            5. 2021-05-15: Added additional language to the Compaction Algorithm step 12.8.9.6.1 to first expand - container key before compacting it, - as described in Candidate Correction 2.
              6. -
            6. 2023-06-28: Changed the Create Term Definition + container key before compacting it (as it can be a Compact IRI). + For more information, refer to issue 380. +
              7. +
            7. 2023-06-28: Changed Create Term Definition in section 4.2 of the Context Processing Algorithms, to ensure that all possible features for reverse term definitions are processed. The change was to remove and return from the end of step 13, and revise step - 14 to begin with Otherwise, - as described in Candidate Correction 3.
              8. + 14 to begin with Otherwise. + For more information, refer to issue 565. +
            8. 2024-07-10: Specify that the value of extractAllScripts @@ -7073,21 +6997,43 @@

              Change log

              defaults to `true`, rather than `false`. This is consistent with wording in Embedding JSON-LD in HTML Documents [[JSON-LD11]] - for treating script elements as a single document, - as described in Candidate Correction 4.
              9. + for treating script elements as a single document. + For more information, refer to issue 603. +
            9. 2025-01-25: Correct some corner cases in transforming RDF Number Literals - to JSON numbers when useNativeTypes is `true`, - as described in Candidate Correction 5.
              10. + to JSON numbers when useNativeTypes is `true`. + For more information, refer to issue 555. +
            10. 2024-01-25: Change processing step for LoadDocumentCallback to not presume that the content type is for JSON, - as described in Candidate Correction 6
              11. -
            11. 2024-10-31: Abstract JSON serialization from WebIDL interfaces to allow - for alternative formats, - as described in Candidate Correction 7
              12. -
            12. 2025-02-28: Clarifiy language about term definitions, - as described in Candidate Correction 8
              13. + but making processing conditional on the content type. + For more information, refer to issue 622. + +
            13. 2024-10-31: Details about transforming to and from a given serialization format + have been abstracted so that other specifications can define + serialization and deserialization requirements for their specific formats. + The algorithm is now more explicit about serializing and deserializing + to the internal representation. + This impacts + compact() step 10, + expand() step 9, + flatten() step 7, + fromRdf() step 3, and + . + For more information, refer to issue 605. +
              14. +
            14. 2025-02-28: Clarifiy language about term definitions: + change how they are represented in the Context Processing Algorithm + (as a map rather than an array), + to be consistent with the way they are used in the algorithms, + and clarify the definition of "term definition" in Section . + For more information, refer to issue 630. +
            15. 2025-02-28: Simplify the Inverse Context Creation algorithm - as described in Candidate Correction 8
              16. + by handling the default base direction + once and for all in this step, rather than in each iteration. + For more information, refer to issue 633. +