From ad934946419527e03f75fbe3affec7ec5d5aeb16 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Niklas=20Lindstr=C3=B6m?= Date: Tue, 18 Nov 2025 17:28:11 +0100 Subject: [PATCH 1/4] Add test case 0028 Test use native types flag with non-native values. --- tests/fromRdf-manifest.jsonld | 10 ++++++++++ tests/fromRdf/0028-in.nq | 5 +++++ tests/fromRdf/0028-out.jsonld | 28 ++++++++++++++++++++++++++++ 3 files changed, 43 insertions(+) create mode 100644 tests/fromRdf/0028-in.nq create mode 100644 tests/fromRdf/0028-out.jsonld diff --git a/tests/fromRdf-manifest.jsonld b/tests/fromRdf-manifest.jsonld index 787e4089..9e0bd705 100644 --- a/tests/fromRdf-manifest.jsonld +++ b/tests/fromRdf-manifest.jsonld @@ -205,6 +205,16 @@ }, "input": "fromRdf/0027-in.nq", "expect": "fromRdf/0027-out.jsonld" + }, { + "@id": "#t0028", + "@type": ["jld:PositiveEvaluationTest", "jld:FromRDFTest"], + "name": "use native types flag with non-native values", + "purpose": "Ensure that useNativeTypes flag being true does not interfere with values that cannot be serialized into a native value.", + "option": { + "useNativeTypes": true + }, + "input": "fromRdf/0028-in.nq", + "expect": "fromRdf/0028-out.jsonld" }, { "@id": "#tdi01", "@type": [ "jld:PositiveEvaluationTest", "jld:FromRDFTest" ], diff --git a/tests/fromRdf/0028-in.nq b/tests/fromRdf/0028-in.nq new file mode 100644 index 00000000..8cdda3ea --- /dev/null +++ b/tests/fromRdf/0028-in.nq @@ -0,0 +1,5 @@ + "string" . + "hello"@en . + "No"^^ . + "AAA"^^ . + "{\"x\": 1}"^^ . diff --git a/tests/fromRdf/0028-out.jsonld b/tests/fromRdf/0028-out.jsonld new file mode 100644 index 00000000..a9bdab56 --- /dev/null +++ b/tests/fromRdf/0028-out.jsonld @@ -0,0 +1,28 @@ +[ + { + "@id": "http://example.com", + "http://example.com/property": [ + { + "@value": "AAA", + "@type": "http://www.w3.org/2001/XMLSchema#double" + }, + { + "@value": { + "x": 1 + }, + "@type": "@json" + }, + { + "@value": "No", + "@type": "http://www.w3.org/2001/XMLSchema#boolean" + }, + { + "@value": "string" + }, + { + "@language": "en", + "@value": "hello" + } + ] + } +] From 868917d2a162fadd21cf773048982e851c0c3c94 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Niklas=20Lindstr=C3=B6m?= Date: Sat, 6 Jun 2026 15:33:20 +0200 Subject: [PATCH 2/4] Order 0028 test output as in input, for clarity --- tests/fromRdf/0028-out.jsonld | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/tests/fromRdf/0028-out.jsonld b/tests/fromRdf/0028-out.jsonld index a9bdab56..ba4db3f1 100644 --- a/tests/fromRdf/0028-out.jsonld +++ b/tests/fromRdf/0028-out.jsonld @@ -3,25 +3,25 @@ "@id": "http://example.com", "http://example.com/property": [ { - "@value": "AAA", - "@type": "http://www.w3.org/2001/XMLSchema#double" + "@value": "string" }, { - "@value": { - "x": 1 - }, - "@type": "@json" + "@language": "en", + "@value": "hello" }, { "@value": "No", "@type": "http://www.w3.org/2001/XMLSchema#boolean" }, { - "@value": "string" + "@value": "AAA", + "@type": "http://www.w3.org/2001/XMLSchema#double" }, { - "@language": "en", - "@value": "hello" + "@value": { + "x": 1 + }, + "@type": "@json" } ] } From ec5ff8cb8bd7cc20bc1ed32b6bc54fe32cfa1137 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Niklas=20Lindstr=C3=B6m?= Date: Sat, 6 Jun 2026 16:08:16 +0200 Subject: [PATCH 3/4] Fix incomplete literal conversion When useNativeTypes is true, the else clause was never reached even if a native type couldn't be used; leaving only plain strings where e.g. language-tagged string literals were the source. This is a slight refactoring of the RDF to Object Conversion algorithm, to address this issue, whilst keeping or improving the clarify of the algorithm. Fixes #670 --- index.html | 99 +++++++++++++++++++++++++++++++++--------------------- 1 file changed, 60 insertions(+), 39 deletions(-) diff --git a/index.html b/index.html index 2860eaf5..ff7b4381 100644 --- a/index.html +++ b/index.html @@ -5459,7 +5459,28 @@

Algorithm

RDF literal:
  1. Initialize a new empty map result.
    2. -
  2. Initialize converted value to value.
    3. +
  3. + Initialize converted value to null. +
    + Candidate Correction 10 +

    + Let converted value be initially unset, and only + actively set if a native type can be used. Then group the + other cases in an else block, defaulting to use the lexical + form of value. Since type is set in the + final else clause (unless it equals xsd:string), + there is no need to set it in the clause for + useNativeTypes. +

    +

    + Previously, the else clause was never reached even if a + native type couldn't be used, leaving only plain strings + where e.g. language-tagged string literals were the source. + For more information, refer to + issue 670. +

    +
    +
  4. Initialize type to null
  5. If useNativeTypes is true
    @@ -5480,12 +5501,8 @@

    Algorithm

    of value equals xsd:boolean, set converted value to true if the lexical form - - of value matches "true" or "1", or false - if it matches "false" or "0". - - If it matches neither, - set type to xsd:boolean.
    6. + of value matches "true" or "1", or false + if it matches "false" or "0".
  6. Otherwise, if the datatype IRI of value equals xsd:integer or @@ -5505,46 +5522,47 @@

    Algorithm

    If the conversion is successful, set converted value to its result.
    7. -
  7. - Otherwise, set type to datatype IRI - of value. -
-
  • Otherwise, if processing mode is not `json-ld-1.0`, - and value is a JSON literal, - set converted value to the result of - turning the lexical value of value - into the JSON-LD internal representation, and set type to @json. - If the lexical value of value is not valid JSON according to - the JSON Grammar [[RFC8259]], - an invalid JSON literal - error has been detected and processing is aborted.
    • -
  • Otherwise, if the datatype IRI of value starts with `https://www.w3.org/ns/i18n#`, - and {{JsonLdOptions/rdfDirection}} is `i18n-datatype`: -
      +
    1. + If converted value is null, +
      1. Set converted value to the lexical form of value.
        2. -
      2. If the string prefix of the fragment identifier - of the datatype IRI up until the underscore (`"_"`) is not empty, - add an entry `@language` to result and set its value to that prefix. -
        As `@direction` may be used without `@language`, - it is possible, and legitimate, to create a datatype IRI - such as `http://w3.org/ns/i18n#_ltr`, which does not encode a language tag.
        3. -
      3. Add an entry `@direction` to result and set its value to the substring of the - fragment identifier following - the underscore (`"_"`).
        4. +
      4. If processing mode is not `json-ld-1.0`, + and value is a JSON literal, + set converted value to the result of + turning the lexical value of value + into the JSON-LD internal representation, and set type to @json. + If the lexical value of value is not valid JSON according to + the JSON Grammar [[RFC8259]], + an invalid JSON literal + error has been detected and processing is aborted.
        5. +
      5. Otherwise, if the datatype IRI of value starts with `https://www.w3.org/ns/i18n#`, + and {{JsonLdOptions/rdfDirection}} is `i18n-datatype`: +
          +
        1. If the string prefix of the fragment identifier + of the datatype IRI up until the underscore (`"_"`) is not empty, + add an entry `@language` to result and set its value to that prefix. +
          As `@direction` may be used without `@language`, + it is possible, and legitimate, to create a datatype IRI + such as `http://w3.org/ns/i18n#_ltr`, which does not encode a language tag.
          2. +
        2. Add an entry `@direction` to result and set its value to the substring of the + fragment identifier following + the underscore (`"_"`).
          3. +
        +
        6. +
      6. Otherwise, if value is a + language-tagged string + add an entry @language to result and set its value to the + language tag of value.
        7. +
      7. Otherwise, set type to the + datatype IRI + of value, unless it equals xsd:string which is ignored.
      2. -
    2. Otherwise, if value is a - language-tagged string - add an entry @language to result and set its value to the - language tag of value.
      3. -
    3. Otherwise, set type to the - datatype IRI - of value, unless it equals xsd:string which is ignored.
    4. Add an entry @value to result whose value is set to converted value.
    5. If type is not null, add an entry @type @@ -7088,6 +7106,9 @@

      Change log

      as described in Candidate Correction 8
    6. 2025-02-28: Simplify the Inverse Context Creation algorithm as described in Candidate Correction 8
      7. +
    7. 2026-06-06: Fix unconditional skip of other clauses when + useNativeTypes is `true`, as + described in Candidate Correction 10.
      8. From 8e1a6c725660bb9c39a9747fc3a6238308931934 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Niklas=20Lindstr=C3=B6m?= Date: Wed, 10 Jun 2026 18:14:26 +0200 Subject: [PATCH 4/4] Apply suggestion from @TallTed Co-authored-by: Ted Thibodeau Jr --- index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/index.html b/index.html index ff7b4381..87adf2dd 100644 --- a/index.html +++ b/index.html @@ -5475,7 +5475,7 @@

      Algorithm

      Previously, the else clause was never reached even if a native type couldn't be used, leaving only plain strings - where e.g. language-tagged string literals were the source. + where, e.g., language-tagged string literals were the source. For more information, refer to issue 670.