From b01d0d2e581b4124a34ffb3c5ed1dee6742fad4e Mon Sep 17 00:00:00 2001
From: Anatoly Scherbakov 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.
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. @@ -5731,7 +5731,7 @@
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)
@@ -5841,7 +5841,7 @@ This section defines the requirements for serializing and deserializing
JSON from and to the internal representation, as appropriate,
@@ -6257,7 +6257,7 @@ Algorithm
to the provided context.
-
+
transforming compacted output from the
internal representation to a JSON serialization.Algorithm
set expanded output to an array containing only expanded output.
+
transforming expanded output from the
internal representation to a JSON serialization.Algorithm
otherwise to null
.
+
transforming flattened output from the
internal representation to a JSON serialization.Algorithm
Serialize RDF as JSON-LD Algorithm method
using dataset
and options.
+
transforming expanded output from the
internal representation to a JSON serialization.Internal Representation in Implementations
Serialization and Deserialization
-
+
Serialization and Deserialization
- This section left intentially blank.
+ This section left intentially blank.
Change log
as described in Candidate Correction 4.