This specification defines an Application Programming Interface (API) and a set of algorithms for programmatic transformations of JSON-LD documents. Restructuring data according to the defined transformations often dramatically simplifies its usage.

Features

The JSON-LD Syntax specification [[!JSON-LD]] defines a syntax to express Linked Data in JSON. Because there is more than one way to express Linked Data using this syntax, it is often useful to be able to transform JSON-LD documents so that they may be more easily consumed by specific applications.

JSON-LD uses contexts to allow Linked Data to be expressed in a way that is specifically tailored to a particular person or application. By providing a context, JSON data can be expressed in a way that is a natural fit for a particular person or application whilst also indicating how the data should be understood at a global scale. In order for people or applications to share data that was created using a context that is different from their own, a JSON-LD processor must be able to transform a document from one context to another. Instead of requiring JSON-LD processors to write specific code for every imaginable context switching scenario, it is much easier to specify a single algorithm that can remove any context. Similarly, another algorithm can be specified to subsequently apply any context. These two algorithms represent the most basic transformations of JSON-LD documents. They are referred to as expansion and compaction, respectively.

There are four major types of transformation that are discussed in this document: expansion, compaction, flattening, and RDF serialization/deserialization.

Expansion

The algorithm that removes context is called expansion. Before performing any other transformations on a JSON-LD document, it is easiest to remove any context from it and to make data structures more regular.

To get an idea of how context and data structuring affects the same data, here is an example of JSON-LD that uses only terms and is fairly compact:

The next input example uses one IRI to express a property and an array to encapsulate another, but leaves the rest of the information untouched.

Note that both inputs are valid JSON-LD and both represent the same information. The difference is in their context information and in the data structures used. A JSON-LD processor can remove context and ensure that the data is more regular by employing expansion.

Expansion has two important goals: removing any contextual information from the document, and ensuring all values are represented in a regular form. These goals are accomplished by expanding all properties to absolute IRIs and by expressing all values in arrays in expanded form. Expanded form is the most verbose and regular way of expressing of values in JSON-LD; all contextual information from the document is instead stored locally with each value. Running the Expansion algorithm (expand operation) against the above examples results in the following output:

Note that in the output above all context definitions have been removed, all terms and compact IRIs have been expanded to absolute IRIs, and all JSON-LD values are expressed in arrays in expanded form. While the output is more verbose and difficult for a human to read, it establishes a baseline that makes JSON-LD processing easier because of its very regular structure.

Compaction

While expansion removes context from a given input, compaction's primary function is to perform the opposite operation: to express a given input according to a particular context. Compaction applies a context that specifically tailors the way information is expressed for a particular person or application. This simplifies applications that consume JSON or JSON-LD by expressing the data in application-specific terms, and it makes the data easier to read by humans.

Compaction uses a developer-supplied context to shorten IRIs to terms or compact IRIs and JSON-LD values expressed in expanded form to simple values such as strings or numbers.

For example, assume the following expanded JSON-LD input document:

Additionally, assume the following developer-supplied JSON-LD context:

Running the Compaction Algorithm (compact operation) given the context supplied above against the JSON-LD input document provided above would result in the following output:

Note that all IRIs have been compacted to terms as specified in the context, which has been injected into the output. While compacted output is useful to humans, it is also used to generate structures that are easy to program against. Compaction enables developers to map any expanded document into an application-specific compacted document. While the context provided above mapped http://xmlns.com/foaf/0.1/name to name, it could also have been mapped to any other term provided by the developer.

Flattening

While expansion ensures that a document is in a uniform structure, flattening goes a step further to ensure that the shape of the data is deterministic. In expanded documents, the properties of a single node may be spread across a number of different JSON objects. By flattening a document, all properties of a node are collected in a single JSON object and all blank nodes are labeled with a blank node identifier. This may drastically simplify the code required to process JSON-LD data in certain applications.

For example, assume the following JSON-LD input document:

Running the Flattening algorithm (flatten operation) with a context set to null to prevent compaction returns the following document:

Note how in the output above all properties of a node are collected in a single JSON object and how the blank node representing "Dave Longley" has been assigned the blank node identifier _:t0.

To make it easier for humans to read or for certain applications to process it, a flattened document can be compacted by passing a context. Using the same context as the input document, the flattened and compacted document looks as follows:

Please note that the result of flattening and compacting a document is always a JSON object which contains an @graph member that represents the default graph.

RDF Serialization/Deserialization

JSON-LD can be used to serialize RDF data as described in [[RDF11-CONCEPTS]]. This ensures that data can be round-tripped to and from any RDF syntax without any loss in fidelity.

For example, assume the following RDF input serialized in Turtle [[TURTLE]]:

Using the Serialize from RDF algorithm a developer could transform this document into expanded JSON-LD:

Note that the output above could easily be compacted using the technique outlined in the previous section. It is also possible to deserialize the JSON-LD document back to RDF using the Deserialize to RDF algorithm.

Context Processing Algorithms

Context Processing Algorithm

When processing a JSON-LD data structure, each processing rule is applied using information provided by the active context. This section describes how to produce an active context.

The active context contains the active term definitions which specify how properties and values have to be interpreted as well as the current base IRI, the vocabulary mapping and the default language. Each term definition consists of an IRI mapping, a boolean flag reverse property, an optional type mapping or language mapping, and an optional container mapping. A term definition can not only be used to map a term to an IRI, but also to map a term to a keyword, in which case it is referred to as a keyword alias.

When processing, the active context is initialized without any term definitions, vocabulary mapping, or default language. If a local context is encountered during processing, a new active context is created by cloning the existing active context. Then the information from the local context is merged into the new active context. Given that local contexts may contain references to remote contexts, this includes their retrieval.

Overview

First we prepare a new active context result by cloning the current active context. Then we normalize the form of the passed local context to an array. Local contexts may be in the form of a JSON object, a string, or an array containing a combination of the two. Finally we process each context contained in the local context array as follows.

If context is a string, it represents a reference to a remote context. We dereference the remote context and replace context with the value of the @context key of the top-level object in the retrieved JSON-LD document. If there's no such key, an invalid remote context has been detected. Otherwise, we process context by recursively using this algorithm ensuring that there is no cyclical reference.

If context is a JSON object, we first update the base IRI, the vocabulary mapping, and the default language by processing three specific keywords: @base, @vocab, and @language. These are handled before any other keys in the local context because they affect how the other keys are processed. Please note that @base is ignored when processing remote contexts.

Then, for every other key in local context, we update the term definition in result. Since term definitions in a local context may themselves contain terms or compact IRIs, we may need to recurse. When doing so, we must ensure that there is no cyclical dependency, which is an error. After we have processed any term definition dependencies, we update the current term definition, which may be a keyword alias.

Finally, we return result as the new active context.

Algorithm

This algorithm specifies how a new active context is updated with a local context. The algorithm takes three input variables: an active context, a local context, and an array remote contexts which is used to detect cyclical context inclusions. If remote contexts is not passed, it is initialized to an empty array.

Initialize result to the result of cloning active context.
If local context is not an array, set it to an array containing only local context.
For each item context in local context:
1. If context is null, set result to a newly-initialized active context and continue with the next context. The base IRI of the active context is set to the IRI of the currently being processed document (which might be different from the currently being processed context), if available; otherwise to null. If set, the compactArrays option of a JSON-LD API Implementation overrides the base IRI.
2. If context is a string,
  1. Set context to the result of resolving value against the base IRI which is established as specified in section 5.1 Establishing a Base URI of [[!RFC3986]]. Only the basic algorithm in section 5.2 of [[!RFC3986]] is used; neither Syntax-Based Normalization nor Scheme-Based Normalization are performed. Characters additionally allowed in IRI references are treated in the same way that unreserved characters are treated in URI references, per section 6.5 of [[!RFC3987]].
  2. If context is in the remote contexts array, a recursive context inclusion error has been detected and processing is aborted; otherwise, add context to remote contexts.
  3. Dereference context. If context cannot be dereferenced, a loading remote context failed error has been detected and processing is aborted. If the dereferenced document has no top-level JSON object with an @context member, an invalid remote context has been detected and processing is aborted; otherwise, set context to the value of that member.
  4. Set result to the result of recursively calling this algorithm, passing result for active context, context for local context, and remote contexts.
  5. Continue with the next context.
3. If context is not a JSON object, an invalid local context error has been detected and processing is aborted.
4. If context has an @base key and remote contexts is empty, i.e., the currently being processed context is not a remote context:
  1. Initialize value to the value associated with the @base key.
  2. If value is null, remove the base IRI of result.
  3. Otherwise, if value is an absolute IRI, the base IRI of result is set to value.
  4. Otherwise, if value is a relative IRI and the base IRI of result is not null, set the base IRI of result to the result of resolving value against the current base IRI of result.
  5. Otherwise, an invalid base IRI error has been detected and processing is aborted.
5. If context has an @vocab key:
  1. Initialize value to the value associated with the @vocab key.
  2. If value is null, remove any vocabulary mapping from result.
  3. Otherwise, if value is an absolute IRI or blank node identifier, the vocabulary mapping of result is set to value. If it is not an absolute IRI or blank node identifier, an invalid vocab mapping error has been detected and processing is aborted.
6. If context has an @language key:
  1. Initialize value to the value associated with the @language key.
  2. If value is null, remove any default language from result.
  3. Otherwise, if value is string, the default language of result is set to lowercased value. If it is not a string, an invalid default language error has been detected and processing is aborted.
7. Create a JSON object defined to use to keep track of whether or not a term has already been defined or currently being defined during recursion.
8. For each key-value pair in context where key is not @base, @vocab, or @language, invoke the Create Term Definition algorithm, passing result for active context, context for local context, key, and defined.
Return result.

Create Term Definition

This algorithm is called from the Context Processing algorithm to create a term definition in the active context for a term being processed in a local context.

Overview

Term definitions are created by parsing the information in the given local context for the given term. If the given term is a compact IRI, it may omit an IRI mapping by depending on its prefix having its own term definition. If the prefix is a key in the local context, then its term definition must first be created, through recursion, before continuing. Because a term definition can depend on other term definitions, a mechanism must be used to detect cyclical dependencies. The solution employed here uses a map, defined, that keeps track of whether or not a term has been defined or is currently in the process of being defined. This map is checked before any recursion is attempted.

After all dependencies for a term have been defined, the rest of the information in the local context for the given term is taken into account, creating the appropriate IRI mapping, container mapping, and type mapping or language mapping for the term.

Algorithm

The algorithm has four required inputs which are: an active context, a local context, a term, and a map defined.

If defined contains the key term and the associated value is true (indicating that the term definition has already been created), return. Otherwise, if the value is false, a cyclic IRI mapping error has been detected and processing is aborted.
Set the value associated with defined's term key to false. This indicates that the term definition is now being created but is not yet complete.
Since keywords cannot be overridden, term must not be a keyword. Otherwise, a keyword redefinition error has been detected and processing is aborted.
Remove any existing term definition for term in active context.
Initialize value to a copy of the value associated with the key term in local context.
If value is null or value is a JSON object containing the key-value pair @id-null, set the term definition in active context to null, set the value associated with defined's key term to true, and return.
Otherwise, if value is a string, convert it to a JSON object consisting of a single member whose key is @id and whose value is value.
Otherwise, value must be a JSON object, if not, an invalid term definition error has been detected and processing is aborted.
Create a new term definition, definition.
If value contains the key @type:
1. Initialize type to the value associated with the @type key, which must be a string. Otherwise, an invalid type mapping error has been detected and processing is aborted.
2. Set type to the result of using the IRI Expansion algorithm, passing active context, type for value, true for vocab, false for document relative, local context, and defined. If the expanded type is neither @id, nor @vocab, nor an absolute IRI, an invalid type mapping error has been detected and processing is aborted.
3. Set the type mapping for definition to type.
If value contains the key @reverse:
1. If value contains an @id, member, an invalid reverse property error has been detected and processing is aborted.
2. If the value associated with the @reverse key is not a string, an invalid IRI mapping error has been detected and processing is aborted.
3. Otherwise, set the IRI mapping of definition to the result of using the IRI Expansion algorithm, passing active context, the value associated with the @reverse key for value, true for vocab, false for document relative, local context, and defined. If the result is not an absolute IRI, i.e., it contains no colon (:), an invalid IRI mapping error has been detected and processing is aborted.
4. If value contains an @container member, set the container mapping of definition to its value; if its value is neither @set, nor @index, nor null, an invalid reverse property error has been detected (reverse properties only support set- and index-containers) and processing is aborted.
5. Set the reverse property flag of definition to true.
6. Set the term definition of term in active context to definition and the value associated with defined's key term to true and return.
Set the reverse property flag of definition to false.
If value contains the key @id and its value does not equal term:
1. If the value associated with the @id key is not a string, an invalid IRI mapping error has been detected and processing is aborted.
2. Otherwise, set the IRI mapping of definition to the result of using the IRI Expansion algorithm, passing active context, the value associated with the @id key for value, true for vocab, false for document relative, local context, and defined. If the resulting IRI mapping equals @context, an invalid keyword alias error has been detected and processing is aborted.
Otherwise if the term contains a colon (:):
1. If term is a compact IRI with a prefix that is a key in local context a dependency has been found. Use this algorithm recursively passing active context, local context, the prefix as term, and defined.
2. If term's prefix has a term definition in active context, set the IRI mapping of definition to the result of concatenating the value associated with the prefix's IRI mapping and the term's suffix.
3. Otherwise, term is an absolute IRI. Set the IRI mapping of definition to term.
Otherwise, if active context has a vocabulary mapping, the IRI mapping of definition is set to the result of concatenating the value associated with the vocabulary mapping and term. If it does not have a vocabulary mapping, an invalid IRI mapping error been detected and processing is aborted.
If value contains the key @container:
1. Initialize container to the value associated with the @container key, which must be either @list, @set, @index, or @language. Otherwise, an invalid container mapping error has been detected and processing is aborted.
2. Set the container mapping of definition to container.
If value contains the key @language and does not contain the key @type:
1. Initialize language to the value associated with the @language key, which must be either null or a string. Otherwise, an invalid language mapping error has been detected and processing is aborted.
2. If language is a string set it to lowercased language. Set the language mapping of definition to language.
Set the term definition of term in active context to definition and set the value associated with defined's key term to true.

IRI Expansion

In JSON-LD documents, some keys and values may represent IRIs. This section defines an algorithm for transforming a string that represents an IRI into an absolute IRI or blank node identifier. It also covers transforming keyword aliases into keywords.

IRI expansion may occur during context processing or during any of the other JSON-LD algorithms. If IRI expansion occurs during context processing, then the local context and its related defined map from the Context Processing algorithm are passed to this algorithm. This allows for term definition dependencies to be processed via the Create Term Definition algorithm.

Overview

In order to expand value to an absolute IRI, we must first determine if it is null, a term, a keyword alias, or some form of IRI. Based on what we find, we handle the specific kind of expansion; for example, we expand a keyword alias to a keyword and a term to an absolute IRI according to its IRI mapping in the active context. While inspecting value we may also find that we need to create term definition dependencies because we're running this algorithm during context processing. We can tell whether or not we're running during context processing by checking local context against null. We know we need to create a term definition in the active context when value is a key in the local context and the defined map does not have a key for value with an associated value of true. The defined map is used during Context Processing to keep track of which terms have already been defined or are in the process of being defined. We create a term definition by using the Create Term Definition algorithm.

Algorithm

The algorithm takes two required and four optional input variables. The required inputs are an active context and a value to be expanded. The optional inputs are two flags, document relative and vocab, that specifying whether value can be interpreted as a relative IRI against the document's base IRI or the active context's vocabulary mapping, respectively, and a local context and a map defined to be used when this algorithm is used during Context Processing. If not passed, the two flags are set to false and local context and defined are initialized to null.

If value is a keyword or null, return value as is.
If local context is not null, it contains a key that equals value, and the value associated with the key that equals value in defined is not true, invoke the Create Term Definition algorithm, passing active context, local context, value as term, and defined. This will ensure that a term definition is created for value in active context during Context Processing.
If vocab is true and the active context has a term definition for value, return the associated IRI mapping.
If value contains a colon (:), it is either an absolute IRI or a compact IRI:
1. Split value into a prefix and suffix at the first occurrence of a colon (:).
2. If prefix is underscore (_) or suffix begins with double-forward-slash (//), return value as it is already an absolute IRI or a blank node identifier.
3. If local context is not null, it contains a key that equals prefix, and the value associated with the key that equals prefix in defined is not true, invoke the Create Term Definition algorithm, passing active context, local context, prefix as term, and defined. This will ensure that a term definition is created for prefix in active context during Context Processing.
4. If active context contains a term definition for prefix, return the result of concatenating the IRI mapping associated with prefix and suffix.
5. Return value as it is already an absolute IRI.
If vocab is true, and active context has a vocabulary mapping, return the result of concatenating the vocabulary mapping with value.
Otherwise, if document relative is true, set value to the result of resolving value against the base IRI. Only the basic algorithm in section 5.2 of [[!RFC3986]] is used; neither Syntax-Based Normalization nor Scheme-Based Normalization are performed. Characters additionally allowed in IRI references are treated in the same way that unreserved characters are treated in URI references, per section 6.5 of [[!RFC3987]].
If local context is not null and value is not an absolute IRI, an invalid IRI mapping error has been detected and processing is aborted.
Otherwise, return value as is.

Expansion Algorithms

Expansion Algorithm

This algorithm expands a JSON-LD document, such that all context definitions are removed, all terms and compact IRIs are expanded to absolute IRIs, blank node identifiers, or keywords and all JSON-LD values are expressed in arrays in expanded form.

Overview

Starting with its root element, we can process the JSON-LD document recursively, until we have a fully expanded result. When expanding an element, we can treat each one differently according to its type, in order to break down the problem:

If the element is null, there is nothing to expand.
Otherwise, if element is a scalar, we expand it according to the Value Expansion algorithm.
Otherwise, if the element is an array, then we expand each of its items recursively and return them in a new array.
Otherwise, element is a JSON object. We expand each of its keys, adding them to our result, and then we expand each value for each key recursively. Some of the keys will be terms or compact IRIs and others will be keywords or simply ignored because they do not have definitions in the context. Any IRIs will be expanded using the IRI Expansion algorithm.

Finally, after ensuring result is in an array, we return result.

Algorithm

The algorithm takes three input variables: an active context, an active property, and an element to be expanded. To begin, the active context is set to the result of performing, Context Processing on the passed expandContext, or empty if expandContext is null, active property is set to null, and element is set to the JSON-LD input.

If element is null, return null.
If element is a scalar,
1. If active property is null or @graph, drop the free-floating scalar by returning null.
2. Return the result of the Value Expansion algorithm, passing the active context, active property, and element as value.
If element is an array,
1. Initialize an empty array, result.
2. For each item in element:
  1. Initialize expanded item to the result of using this algorithm recursively, passing active context, active property, and item as element.
  2. If the active property is @list or its container mapping is set to @list, the expanded item must not be an array or a list object, otherwise a list of lists error has been detected and processing is aborted.
  3. If expanded item is an array, append each of its items to result. Otherwise, if expanded item is not null, append it to result.
3. Return result.
Otherwise element is a JSON object.
If element contains the key @context, set active context to the result of the Context Processing algorithm, passing active context and the value of the @context key as local context.
Initialize an empty JSON object, result.
For each key and value in element, ordered lexicographically by key:
1. If key is @context, continue to the next key.
2. Set expanded property to the result of using the IRI Expansion algorithm, passing active context, key for value, and true for vocab.
3. If expanded property is null or it neither contains a colon (:) nor it is a keyword, drop key by continuing to the next key.
4. If expanded property is a keyword:
  1. If active property equals @reverse, an invalid reverse property map error has been detected and processing is aborted.
  2. If result has already an expanded property member, an colliding keywords error has been detected and processing is aborted.
  3. If expanded property is @id and value is not a string, an invalid @id value error has been detected and processing is aborted. Otherwise, set expanded value to the result of using the IRI Expansion algorithm, passing active context, value, and true for document relative.
  4. If expanded property is @type and value is neither a string nor an array of strings, an invalid type value error has been detected and processing is aborted. Otherwise, set expanded value to the result of using the IRI Expansion algorithm, passing active context, true for vocab, and true for document relative to expand the value or each of its items.
  5. If expanded property is @graph, set expanded value to the result of using this algorithm recursively passing active context, @graph for active property, and value for element.
  6. If expanded property is @value and value is not a scalar or null, an invalid value object value error has been detected and processing is aborted. Otherwise, set expanded value to value. If expanded value is null, set the @value member of result to null and continue with the next key from element. Null values need to be preserved in this case as the meaning of an @type member depends on the existence of an @value member.
  7. If expanded property is @language and value is not a string, an invalid language-tagged string error has been detected and processing is aborted. Otherwise, set expanded value to lowercased value.
  8. If expanded property is @index and value is not a string, an invalid @index value error has been detected and processing is aborted. Otherwise, set expanded value to value.
  9. If expanded property is @list:
    1. If active property is null or @graph, continue with the next key from element to remove the free-floating list.
    2. Otherwise, initialize expanded value to the result of using this algorithm recursively passing active context, active property, and value for element.
    3. If expanded value is a list object, a list of lists error has been detected and processing is aborted.
  10. If expanded property is @set, set expanded value to the result of using this algorithm recursively, passing active context, active property, and value for element.
  11. If expanded property is @reverse and value is not a JSON object, an invalid @reverse value error has been detected and processing is aborted. Otherwise
    1. Initialize expanded value to the result of using this algorithm recursively, passing active context, @reverse as active property, and value as element.
    2. If expanded value contains an @reverse member, i.e., properties that are reversed twice, execute for each of its property and item the following steps:
      1. If result does not have a property member, create one and set its value to an empty array.
      2. Append item to the value of the property member of result.
    3. If expanded value contains members other than @reverse:
      1. If result does not have an @reverse member, create one and set its value to an empty JSON object.
      2. Reference the value of the @reverse member in result using the variable reverse map.
      3. For each property and items in expanded value other than @reverse:
        
        For each item in items:
        
        If item is a value object or list object, an invalid reverse property value has been detected and processing is aborted.
        
        If reverse map has no property member, create one and initialize its value to an empty array.
        
        Append item to the value of the property member in reverse map.
    4. Continue with the next key from element.
  12. Unless expanded value is null, set the expanded property member of result to expanded value.
  13. Continue with the next key from element.
5. Otherwise, if key's container mapping in active context is @language and value is a JSON object then value is expanded from a language map as follows:
  1. Initialize expanded value to an empty array.
  2. For each key-value pair language-language value in value, ordered lexicographically by language:
    1. If language value is not an array set it to an array containing only language value.
    2. For each item in language value:
      1. item must be a string, otherwise an invalid language map value error has been detected and processing is aborted.
      2. Append a JSON object to expanded value that consists of two key-value pairs: (@value-item) and (@language-lowercased language).
6. Otherwise, if key's container mapping in active context is @index and value is a JSON object then value is expanded from an index map as follows:
  1. Initialize expanded value to an empty array.
  2. For each key-value pair index-index value in value, ordered lexicographically by index:
    1. If index value is not an array set it to an array containing only index value.
    2. Initialize index value to the result of using this algorithm recursively, passing active context, key as active property, and index value as element.
    3. For each item in index value:
      1. If item does not have the key @index, add the key-value pair (@index-index) to item.
      2. Append item to expanded value.
7. Otherwise, initialize expanded value to the result of using this algorithm recursively, passing active context, key for active property, and value for element.
8. If expanded value is null, ignore key by continuing to the next key from element.
9. If the container mapping associated to key in active context is @list and expanded value is not already a list object, convert expanded value to a list object by first setting it to an array containing only expanded value if it is not already an array, and then by setting it to a JSON object containing the key-value pair @list-expanded value.
10. Otherwise, if the term definition associated to key indicates that it is a reverse property
  1. If result has no @reverse member, create one and initialize its value to an empty JSON object.
  2. Reference the value of the @reverse member in result using the variable reverse map.
  3. If expanded value is not an array, set it to an array containing expanded value.
  4. For each item in expanded value
    1. If item is a value object or list object, an invalid reverse property value has been detected and processing is aborted.
    2. If reverse map has no expanded property member, create one and initialize its value to an empty array.
    3. Append item to the value of the expanded property member of reverse map.
11. Otherwise, if key is not a reverse property:
  1. If result does not have an expanded property member, create one and initialize its value to an empty array.
  2. Append expanded value to value of the expanded property member of result.
If result contains the key @value:
1. The result must not contain any keys other than @value, @language, @type, and @index. It must not contain both the @language key and the @type key. Otherwise, an invalid value object error has been detected and processing is aborted.
2. If the value of result's @value key is null, then set result to null.
3. Otherwise, if the value of result's @value member is not a string and result contains the key @language, an invalid language-tagged value error has been detected (only strings can be language-tagged) and processing is aborted.
4. Otherwise, if the result has a @type member and its value is not an IRI, an invalid typed value error has been detected and processing is aborted.
Otherwise, if result contains the key @type and its associated value is not an array, set it to an array containing only the associated value.
Otherwise, if result contains the key @set or @list:
1. The result must contain at most one other key and that key must be @index. Otherwise, an invalid set or list object error has been detected and processing is aborted.
2. If result contains the key @set, then set result to the key's associated value.
If result contains only the key @language, set result to null.
If active property is null or @graph, drop free-floating values as follows:
1. If result is an empty JSON object or contains the keys @value or @list, set result to null.
2. Otherwise, if result is a JSON object whose only key is @id, set result to null.
Return result.

If, after the above algorithm is run, the result is a JSON object that contains only an @graph key, set the result to the value of @graph's value. Otherwise, if the result is null, set it to an empty array. Finally, if the result is not an array, then set the result to an array containing only the result.

Value Expansion

Some values in JSON-LD can be expressed in a compact form. These values are required to be expanded at times when processing JSON-LD documents. A value is said to be in expanded form after the application of this algorithm.

Overview

If active property has a type mapping in the active context set to @id or @vocab, a JSON object with a single member @id whose value is the result of using the IRI Expansion algorithm on value is returned.

Otherwise, the result will be a JSON object containing an @value member whose value is the passed value. Additionally, an @type member will be included if there is a type mapping associated with the active property or an @language member if value is a string and there is language mapping associated with the active property.

Algorithm

The algorithm takes three required inputs: an active context, an active property, and a value to expand.

If the active property has a type mapping in active context that is @id, return a new JSON object containing a single key-value pair where the key is @id and the value is the result of using the IRI Expansion algorithm, passing active context, value, and true for document relative.
If active property has a type mapping in active context that is @vocab, return a new JSON object containing a single key-value pair where the key is @id and the value is the result of using the IRI Expansion algorithm, passing active context, value, true for vocab, and true for document relative.
Otherwise, initialize result to a JSON object with an @value member whose value is set to value.
If active property has a type mapping in active context, add an @type member to result and set its value to the value associated with the type mapping.
Otherwise, if value is a string:
1. If a language mapping is associated with active property in active context, add an @language to result and set its value to the language code associated with the language mapping; unless the language mapping is set to null in which case no member is added.
2. Otherwise, if the active context has a default language, add an @language to result and set its value to the default language.
Return result.

Compaction Algorithms

Compaction Algorithm

This algorithm compacts a JSON-LD document, such that the given context is applied. This must result in shortening any applicable IRIs to terms or compact IRIs, any applicable keywords to keyword aliases, and any applicable JSON-LD values expressed in expanded form to simple values such as strings or numbers.

Overview

Starting with its root element, we can process the JSON-LD document recursively, until we have a fully compacted result. When compacting an element, we can treat each one differently according to its type, in order to break down the problem:

If the element is a scalar, it is already in compacted form, so we simply return it.
If the element is an array, we compact each of its items recursively and return them in a new array.
Otherwise element is a JSON object. The value of each key in element is compacted recursively. Some of the keys will be compacted, using the IRI Compaction algorithm, to terms or compact IRIs and others will be compacted from keywords to keyword aliases or simply left unchanged because they do not have definitions in the context. Values will be converted to compacted form via the Value Compaction algorithm. Some data will be reshaped based on container mappings specified in the context such as @index or @language maps.

The final output is a JSON object with a @context key, if a non-empty context was given, where the JSON object is either result or a wrapper for it where result appears as the value of an (aliased) @graph key because result contained two or more items in an array.

Algorithm

The algorithm takes five required input variables: an active context, an inverse context, an active property, an element to be compacted, and a flag compactArrays. To begin, the active context is set to the result of performing Context Processing on the passed context, the inverse context is set to the result of performing the Inverse Context Creation algorithm on active context, the active property is set to null, element is set to the result of performing the Expansion algorithm on the JSON-LD input, and, if not passed, compactArrays is set to true.

If element is a scalar, it is already in its most compact form, so simply return element.
If element is an array:
1. Initialize result to an empty array.
2. For each item in element:
  1. Initialize compacted item to the result of using this algorithm recursively, passing active context, inverse context, active property, and item for element.
  2. If compacted item is not null, then append it to result.
3. If result contains only one item (it has a length of 1), active property has no container mapping in active context, and compactArrays is true, set result to its only item.
4. Return result.
Otherwise element is a JSON object.
If element has an @value or @id member and the result of using the Value Compaction algorithm, passing active context, inverse context, active property,and element as value is a scalar, return that result.
Initialize inside reverse to true if active property equals @reverse, otherwise to false.
Initialize result to an empty JSON object.
For each key expanded property and value expanded value in element, ordered lexicographically by expanded property:
1. If expanded property is @id or @type:
  1. If expanded value is a string, then initialize compacted value to the result of using the IRI Compaction algorithm, passing active context, inverse context, expanded value for iri, and true for vocab if expanded property is @type, false otherwise.
  2. Otherwise, expanded value must be a @type array:
    1. Initialize compacted value to an empty array.
    2. For each item expanded type in expanded value, append the result of of using the IRI Compaction algorithm, passing active context, inverse context, expanded type for iri, and true for vocab, to compacted value.
    3. If compacted value contains only one item (it has a length of 1), then set compacted value to its only item.
  3. Initialize alias to the result of using the IRI Compaction algorithm, passing active context, inverse context, expanded property for iri, and true for vocab.
  4. Add a member alias to result whose value is set to compacted value and continue to the next expanded property.
2. If expanded property is @reverse:
  1. Initialize compacted value to the result of using this algorithm recursively, passing active context, inverse context, @reverse for active property, and expanded value for element.
  2. For each property and value in compacted value:
    1. If the term definition for property in the active context indicates that property is a reverse property
      1. If the term definition for property in the active context has a container mapping of @set or compactArrays is false, and value is not an array, set value to a new array containing only value.
      2. If property is not a member of result, add one and set its value to value.
      3. Otherwise, if the value of the property member of result is not an array, set it to a new array containing only the value. Then append value to its value if value is not an array, otherwise append each of its items.
      4. Remove the property member from compacted value.
  3. If compacted value has some remaining members, i.e., it is not an empty JSON object:
    1. Initialize alias to the result of using the IRI Compaction algorithm, passing active context, inverse context, @reverse for iri, and true for vocab.
    2. Set the value of the alias member of result to compacted value.
  4. Continue with the next expanded property from element.
3. If expanded property is @index and active property has a container mapping in active context that is @index, then the compacted result will be inside of an @index container, drop the @index property by continuing to the next expanded property.
4. Otherwise, if expanded property is @index, @value, or @language:
  1. Initialize alias to the result of using the IRI Compaction algorithm, passing active context, inverse context, expanded property for iri, and true for vocab.
  2. Add a member alias to result whose value is set to expanded value and continue with the next expanded property.
5. If expanded value is an empty array:
  1. Initialize item active property to the result of using the IRI Compaction algorithm, passing active context, inverse context, expanded property for iri, expanded value for value, true for vocab, and inside reverse.
  2. If result does not have the key that equals item active property, set this key's value in result to an empty array. Otherwise, if the key's value is not an array, then set it to one containing only the value.
6. At this point, expanded value must be an array due to the Expansion algorithm. For each item expanded item in expanded value:
  1. Initialize item active property to the result of using the IRI Compaction algorithm, passing active context, inverse context, expanded property for iri, expanded item for value, true for vocab, and inside reverse.
  2. Initialize container to null. If there is a container mapping for item active property in active context, set container to its value.
  3. Initialize compacted item to the result of using this algorithm recursively, passing active context, inverse context, item active property for active property, expanded item for element if it does not contain the key @list, otherwise pass the key's associated value for element.
  4. If expanded item is a list object:
    1. If compacted item is not an array, then set it to an array containing only compacted item.
    2. If container is not @list:
      1. Convert compacted item to a list object by setting it to a JSON object containing key-value pair where the key is the result of the IRI Compaction algorithm, passing active context, inverse context, @list for iri, and compacted item for value.
      2. If expanded item contains the key @index, then add a key-value pair to compacted item where the key is the result of the IRI Compaction algorithm, passing active context, inverse context, @index as iri, and the value associated with the @index key in expanded item as value.
    3. Otherwise, item active property must not be a key in result because there cannot be two list objects associated with an active property that has a container mapping; a compaction to list of lists error has been detected and processing is aborted.
  5. If container is @language or @index:
    1. If item active property is not a key in result, initialize it to an empty JSON object. Initialize map object to the value of item active property in result.
    2. If container is @language and compacted item contains the key @value, then set compacted item to the value associated with its @value key.
    3. Initialize map key to the value associated with with the key that equals container in expanded item.
    4. If map key is not a key in map object, then set this key's value in map object to compacted item. Otherwise, if the value is not an array, then set it to one containing only the value and then append compacted item to it.
  6. Otherwise,
    1. If compactArrays is false, container is @set or @list, or expanded property is @list or @graph and compacted item is not an array, set it to a new array containing only compacted item.
    2. If item active property is not a key in result then add the key-value pair, (item active property-compacted item), to result.
    3. Otherwise, if the value associated with the key that equals item active property in result is not an array, set it to a new array containing only the value. Then append compacted item to the value if compacted item is not an array, otherwise, concatenate it.
Return result.

If, after the algorithm outlined above is run, the result result is an array, replace it with a new JSON object with a single member whose key is the result of using the IRI Compaction algorithm, passing active context, inverse context, and @graph as iri and whose value is the array result. Finally, if a non-empty context has been passed, add an @context member to result and set its value to the passed context.

Inverse Context Creation

When there is more than one term that could be chosen to compact an IRI, it has to be ensured that the term selection is both deterministic and represents the most context-appropriate choice whilst taking into consideration algorithmic complexity.

In order to make term selections, the concept of an inverse context is introduced. An inverse context is essentially a reverse lookup table that maps container mappings, type mappings, and language mappings to a simple term for a given active context. A inverse context only needs to be generated for an active context if it is being used for compaction.

To make use of an inverse context, a list of preferred container mappings and the type mapping or language mapping are gathered for a particular value associated with an IRI. These parameters are then fed to the Term Selection algorithm, which will find the term that most appropriately matches the value's mappings.

Overview

To create an inverse context for a given active context, each term in the active context is visited, ordered by length, shortest first (ties are broken by choosing the lexicographically least term). For each term, an entry is added to the inverse context for each possible combination of container mapping and type mapping or language mapping that would legally match the term. Illegal matches include differences between a value's type mapping or language mapping and that of the term. If a term has no container mapping, type mapping, or language mapping (or some combination of these), then it will have an entry in the inverse context using the special key @none. This allows the Term Selection algorithm to fall back to choosing more generic terms when a more specifically-matching term is not available for a particular IRI and value combination.

Algorithm

The algorithm takes one required input: the active context that the inverse context is being created for.

Initialize result to an empty JSON object.
Initialize default language to @none. If the active context has a default language, set default language to it.
For each key term and value term definition in the active context, ordered by shortest term first (breaking ties by choosing the lexicographically least term):
1. If the term definition is null, term cannot be selected during compaction, so continue to the next term.
2. Initialize container to @none. If there is a container mapping in term definition, set container to its associated value.
3. Initialize iri to the value of the IRI mapping for the term definition.
4. If iri is not a key in result, add a key-value pair where the key is iri and the value is an empty JSON object to result.
5. Reference the value associated with the iri member in result using the variable container map.
6. If container map has no container member, create one and set its value to a new JSON object with two members. The first member is @language and its value is a new empty JSON object, the second member is @type and its value is a new empty JSON object.
7. Reference the value associated with the container member in container map using the variable type/language map.
8. If the term definition indicates that the term represents a reverse property:
  1. Reference the value associated with the @type member in type/language map using the variable type map.
  2. If type map does not have a @reverse member, create one and set its value to the term being processed.
9. Otherwise, if term definition has a type mapping:
  1. Reference the value associated with the @type member in type/language map using the variable type map.
  2. If type map does not have a member corresponding to the type mapping in term definition, create one and set its value to the term being processed.
10. Otherwise, if term definition has a language mapping (might be null):
  1. Reference the value associated with the @language member in type/language map using the variable language map.
  2. If the language mapping equals null, set language to @null; otherwise set it to the language code in language mapping.
  3. If language map does not have a language member, create one and set its value to the term being processed.
11. Otherwise:
  1. Reference the value associated with the @language member in type/language map using the variable language map.
  2. If language map does not have a default language member, create one and set its value to the term being processed.
  3. If language map does not have a @none member, create one and set its value to the term being processed.
  4. Reference the value associated with the @type member in type/language map using the variable type map.
  5. If type map does not have a @none member, create one and set its value to the term being processed.
Return result.

IRI Compaction

This algorithm compacts an IRI to a term or compact IRI, or a keyword to a keyword alias. A value that is associated with the IRI may be passed in order to assist in selecting the most context-appropriate term.

Overview

If the passed IRI is null, we simply return null. Otherwise, we first try to find a term that the IRI or keyword can be compacted to if it is relative to active context's vocabulary mapping. In order to select the most appropriate term, we may have to collect information about the passed value. This information includes which container mappings would be preferred for expressing the value, and what its type mapping or language mapping is. For JSON-LD lists, the type mapping or language mapping will be chosen based on the most specific values that work for all items in the list. Once this information is gathered, it is passed to the Term Selection algorithm, which will return the most appropriate term to use.

If no term was found that could be used to compact the IRI, an attempt is made to compact the IRI using the active context's vocabulary mapping, if there is one. If the IRI could not be compacted, an attempt is made to find a compact IRI. If there is no appropriate compact IRI, the IRI is transformed to a relative IRI using the document's base IRI. Finally, if the IRI or keyword still could not be compacted, it is returned as is.

Algorithm

This algorithm takes three required inputs and three optional inputs. The required inputs are an active context, an inverse context, and the iri to be compacted. The optional inputs are a value associated with the iri, a vocab flag which specifies whether the passed iri should be compacted using the active context's vocabulary mapping, and a reverse flag which specifies whether a reverse property is being compacted. If not passed, value is set to null and vocab and reverse are both set to false.

If iri is null, return null.
If vocab is true and iri is a key in inverse context:
1. Initialize default language to active context's default language, if it has one, otherwise to @none.
2. Initialize containers to an empty array. This array will be used to keep track of an ordered list of preferred container mappings for a term, based on what is compatible with value.
3. Initialize type/language to @language, and type/language value to @null. These two variables will keep track of the preferred type mapping or language mapping for a term, based on what is compatible with value.
4. If value is a JSON object that contains the key @index, then append the value @index to containers.
5. If reverse is true, set type/language to @type, type/language value to @reverse, and append @set to containers.
6. Otherwise, if value is a list object, then set type/language and type/language value to the most specific values that work for all items in the list as follows:
  1. If @index is a not key in value, then append @list to containers.
  2. Initialize list to the array associated with the key @list in value.
  3. Initialize common type and common language to null. If list is empty, set common language to default language.
  4. For each item in list:
    1. Initialize item language to @none and item type to @none.
    2. If item contains the key @value:
      1. If item contains the key @language, then set item language to its associated value.
      2. Otherwise, if item contains the key @type, set item type to its associated value.
      3. Otherwise, set item language to @null.
    3. Otherwise, set item type to @id.
    4. If common language is null, set it to item language.
    5. Otherwise, if item language does not equal common language and item contains the key @value, then set common language to @none because list items have conflicting languages.
    6. If common type is null, set it to item type.
    7. Otherwise, if item type does not equal common type, then set common type to @none because list items have conflicting types.
    8. If common language is @none and common type is @none, then stop processing items in the list because it has been detected that there is no common language or type amongst the items.
  5. If common language is null, set it to @none.
  6. If common type is null, set it to @none.
  7. If common type is not @none then set type/language to @type and type/language value to common type.
  8. Otherwise, set type/language value to common language.
7. Otherwise:
  1. If value is a value object:
    1. If value contains the key @language and does not contain the key @index, then set type/language value to its associated value and append @language to containers.
    2. Otherwise, if value contains the key @type, then set type/language value to its associated value and set type/language to @type.
  2. Otherwise, set type/language to @type and set type/language value to @id.
  3. Append @set to containers.
8. Append @none to containers. This represents the non-existence of a container mapping, and it will be the last container mapping value to be checked as it is the most generic.
9. If type/language value is null, set it to @null. This is the key under which null values are stored in the inverse context entry.
10. Initialize preferred values to an empty array. This array will indicate, in order, the preferred values for a term's type mapping or language mapping.
11. If type/language value is @reverse, append @reverse to preferred values.
12. If type/language value is @id or @reverse and value has an @id member:
  1. If the result of using the IRI compaction algorithm, passing active context, inverse context, the value associated with the @id key in value for iri, true for vocab, and true for document relative has a term definition in the active context with an IRI mapping that equals the value associated with the @id key in value, then append @vocab, @id, and @none, in that order, to preferred values.
  2. Otherwise, append @id, @vocab, and @none, in that order, to preferred values.
13. Otherwise, append type/language value and @none, in that order, to preferred values.
14. Initialize term to the result of the Term Selection algorithm, passing inverse context, iri, containers, type/language, and preferred values.
15. If term is not null, return term.
At this point, there is no simple term that iri can be compacted to. If vocab is true and active context has a vocabulary mapping:
1. If iri begins with the vocabulary mapping's value but is longer, then initialize suffix to the substring of iri that does not match. If suffix does not have a term definition in active context, then return suffix.
The iri could not be compacted using the active context's vocabulary mapping. Try to create a compact IRI, starting by initializing compact IRI to null. This variable will be used to tore the created compact IRI, if any.
For each key term and value term definition in the active context:
1. If the term contains a colon (:), then continue to the next term because terms with colons can't be used as prefixes.
2. If the term definition is null, its IRI mapping equals iri, or its IRI mapping is not a substring at the beginning of iri, the term cannot be used as a prefix because it is not a partial match with iri. Continue with the next term.
3. Initialize candidate by concatenating term, a colon (:), and the substring of iri that follows after the value of the term definition's IRI mapping.
4. If either compact IRI is null or candidate is shorter or the same length but lexicographically less than compact IRI and candidate does not have a term definition in active context or if the term definition has an IRI mapping that equals iri and value is null, set compact IRI to candidate.
If compact IRI is not null, return compact IRI.
If vocab is false then transform iri to a relative IRI using the document's base IRI.
Finally, return iri as is.

Term Selection

This algorithm, invoked via the IRI Compaction algorithm, makes use of an active context's inverse context to find the term that is best used to compact an IRI. Other information about a value associated with the IRI is given, including which container mappings and which type mapping or language mapping would be best used to express the value.

Overview

The inverse context's entry for the IRI will be first searched according to the preferred container mappings, in the order that they are given. Amongst terms with a matching container mapping, preference will be given to those with a matching type mapping or language mapping, over those without a type mapping or language mapping. If there is no term with a matching container mapping then the term without a container mapping that matches the given type mapping or language mapping is selected. If there is still no selected term, then a term with no type mapping or language mapping will be selected if available. No term will be selected that has a conflicting type mapping or language mapping. Ties between terms that have the same mappings are resolved by first choosing the shortest terms, and then by choosing the lexicographically least term. Note that these ties are resolved automatically because they were previously resolved when the Inverse Context Creation algorithm was used to create the inverse context.

Algorithm

This algorithm has five required inputs. They are: an inverse context, a keyword or IRI iri, an array containers that represents an ordered list of preferred container mappings, a string type/language that indicates whether to look for a term with a matching type mapping or language mapping, and an array representing an ordered list of preferred values for the type mapping or language mapping to look for.

Initialize container map to the value associated with iri in the inverse context.
For each item container in containers:
1. If container is not a key in container map, then there is no term with a matching container mapping for it, so continue to the next container.
2. Initialize type/language map to the value associated with the container member in container map.
3. Initialize value map to the value associated with type/language member in type/language map.
4. For each item in preferred values:
  1. If item is not a key in value map, then there is no term with a matching type mapping or language mapping, so continue to the next item.
  2. Otherwise, a matching term has been found, return the value associated with the item member in value map.
No matching term has been found. Return null.

Value Compaction

Expansion transforms all values into expanded form in JSON-LD. This algorithm performs the opposite operation, transforming a value into compacted form. This algorithm compacts a value according to the term definition in the given active context that is associated with the value's associated active property.

Overview

The value to compact has either an @id or an @value member.

For the former case, if the type mapping of active property is set to @id or @vocab and value consists of only an @id member and, if the container mapping of active property is set to @index, an @index member, value can be compacted to a string by returning the result of using the IRI Compaction algorithm to compact the value associated with the @id member. Otherwise, value cannot be compacted and is returned as is.

For the latter case, it might be possible to compact value just into the value associated with the @value member. This can be done if the active property has a matching type mapping or language mapping and there is either no @index member or the container mapping of active property is set to @index. It can also be done if @value is the only member in value (apart an @index member in case the container mapping of active property is set to @index) and either its associated value is not a string, there is no default language, or there is an explicit null language mapping for the active property.

Algorithm

This algorithm has four required inputs: an active context, an inverse context, an active property, and a value to be compacted.

Initialize number members to the number of members value contains.
If value has an @index member and the container mapping associated to active property is set to @index, decrease number members by 1.
If number members is greater than 2, return value as it cannot be compacted.
If value has an @id member:
1. If number members is 1 and the type mapping of active property is set to @id, return the result of using the IRI compaction algorithm, passing active context, inverse context, and the value of the @id member for iri.
2. Otherwise, if number members is 1 and the type mapping of active property is set to @vocab, return the result of using the IRI compaction algorithm, passing active context, inverse context, the value of the @id member for iri, and true for vocab.
3. Otherwise, return value as is.
Otherwise, if value has an @type member whose value matches the type mapping of active property, return the value associated with the @value member of value.
Otherwise, if value has an @language member whose value matches the language mapping of active property, return the value associated with the @value member of value.
Otherwise, if number members equals 1 and either the value of the @value member is not a string, or the active context has no default language, or the language mapping of active property is set to null,, return the value associated with the @value member.
Otherwise, return value as is.

Flattening Algorithms

Flattening Algorithm

This algorithm flattens an expanded JSON-LD document by collecting all properties of a node in a single JSON object and labeling all blank nodes with blank node identifiers. This resulting uniform shape of the document, may drastically simplify the code required to process JSON-LD data in certain applications.

Overview

First, a node map is generated using the Node Map Generation algorithm which collects all properties of a node in a single JSON object. In the next step, the node map is converted to a JSON-LD document in flattened document form. Finally, if a context has been passed, the flattened document is compacted using the Compaction algorithm before being returned.

Algorithm

The algorithm takes two input variables, an element to flatten and an optional context used to compact the flattened document. If not passed, context is set to null.

This algorithm generates new blank node identifiers and relabels existing blank node identifiers. The used Generate Blank Node Identifier algorithm keeps an identifier map and a counter to ensure consistent relabeling and avoid collisions. Thus, before this algorithm is run, the identifier map is reset and the counter is initialized to 0.

Initialize node map to a JSON object consisting of a single member whose key is @default and whose value is an empty JSON object.
Perform the Node Map Generation algorithm, passing element and node map.
Initialize default graph to the value of the @default member of node map, which is a JSON object representing the default graph.
For each key-value pair graph name-graph in node map where graph name is not @default, perform the following steps:
1. If default graph does not have a graph name member, create one and initialize its value to a JSON object consisting of an @id member whose value is set to graph name.
2. Reference the value associated with the graph name member in default graph using the variable entry.
3. Add an @graph member to entry and set it to an empty array.
4. For each id-node pair in graph ordered by id, add node to the @graph member of entry, unless the only member of node is @id.
Initialize an empty array flattened.
For each id-node pair in default graph ordered by id, add node to flattened, unless the only member of node is @id.
If context is null, return flattened.
Otherwise, return the result of compacting flattened according the Compaction algorithm passing context ensuring that the compaction result has only the @graph keyword (or its alias) at the top-level other than @context, even if the context is empty or if there is only one element to put in the @graph array. This ensures that the returned document has a deterministic structure.

Node Map Generation

This algorithm creates a JSON object node map holding an indexed representation of the graphs and nodes represented in the passed expanded document. All nodes that are not uniquely identified by an IRI get assigned a (new) blank node identifier. The resulting node map will have a member for every graph in the document whose value is another object with a member for every node represented in the document. The default graph is stored under the @default member, all other graphs are stored under their graph name.

Overview

The algorithm recursively runs over an expanded JSON-LD document to collect all properties of a node in a single JSON object. The algorithm constructs a JSON object node map whose keys represent the graph names used in the document (the default graph is stored under the key @default) and whose associated values are JSON objects which index the nodes in the graph. If a property's value is a node object, it is replaced by a node object consisting of only an @id member. If a node object has no @id member or it is identified by a blank node identifier, a new blank node identifier is generated. This relabeling of blank node identifiers is also done for properties and values of @type.

Algorithm

The algorithm takes as input an expanded JSON-LD document element and a reference to a JSON object node map. Furthermore it has the optional parameters active graph (which defaults to @default), an active subject, active property, and a reference to a JSON object list. If not passed, active subject, active property, and list are set to null.

If element is an array, process each item in element as follows and then return:
1. Run this algorithm recursively by passing item for element, node map, active graph, active subject, active property, and list.
Otherwise element is a JSON object. Reference the JSON object which is the value of the active graph member of node map using the variable graph. If the active subject is null, set node to null otherwise reference the active subject member of graph using the variable node.
If element has an @type member, perform for each item the following steps:
1. If item is a blank node identifier, replace it with a newly generated blank node identifier passing item for identifier.
If element has an @value member, perform the following steps:
1. If list is null:
  1. If node does not have an active property member, create one and initialize its value to an array containing element.
  2. Otherwise, compare element against every item in the array associated with the active property member of node. If there is no item equivalent to element, append element to the array. Two JSON objects are considered equal if they have equivalent key-value pairs.
2. Otherwise, append element to the @list member of list.
Otherwise, if element has an @list member, perform the following steps:
1. Initialize a new JSON object result consisting of a single member @list whose value is initialized to an empty array.
2. Recursively call this algorithm passing the value of element's @list member for element, active graph, active subject, active property, and result for list.
3. Append result to the the value of the active property member of node.
Otherwise element is a node object, perform the following steps:
1. If element has an @id member, set id to its value and remove the member from element. If id is a blank node identifier, replace it with a newly generated blank node identifier passing id for identifier.
2. Otherwise, set id to the result of the Generate Blank Node Identifier algorithm passing null for identifier.
3. If graph does not contain a member id, create one and initialize its value to a JSON object consisting of a single member @id whose value is id.
4. If active property is not null, perform the following steps:
  1. Create a new JSON object reference consisting of a single member @id whose value is id.
  2. If list is null:
    1. If node does not have an active property member, create one and initialize its value to an array containing reference.
    2. Otherwise, compare reference against every item in the array associated with the active property member of node. If there is no item equivalent to reference, append reference to the array. Two JSON objects are considered equal if they have equivalent key-value pairs.
  3. Otherwise, append element to the @list member of list.
5. Reference the value of the id member of graph using the variable node.
6. If element has an @type key, append each item of its associated array to the array associated with the @type key of node unless it is already in that array. Finally remove the @type member from element.
7. If element has an @index member, set the @index member of node to its value. If node has already an @index member with a different value, a conflicting indexes error has been detected and processing is aborted. Otherwise, continue by removing the @index member from element.
8. If element has an @reverse member:
  1. Create a JSON object referenced node with a single member @id whose value is id.
  2. Set reverse map to the value of the @reverse member of element.
  3. For each key-value pair property-values in reverse map:
    1. For each value of values:
      1. If value has a property member, append referenced node to its value; otherwise create a property member whose value is an array containing referenced node.
      2. Recursively invoke this algorithm passing value for element, node map, and active graph.
  4. Remove the @reverse member from element.
9. If element has an @graph member, recursively invoke this algorithm passing the value of the @graph member for element, node map, and id for active graph before removing the @graph member from element.
10. Finally, for each key-value pair property-value in element ordered by property perform the following steps:
  1. If property is a blank node identifier, replace it with a newly generated blank node identifier passing property for identifier.
  2. If node does not have a property member, create one and initialize its value to an empty array.
  3. Recursively invoke this algorithm passing value for element, node map, active graph, id for active subject, and property for active property.

Generate Blank Node Identifier

This algorithm is used to generate new blank node identifiers or to relabel an existing blank node identifier to avoid collision by the introduction of new ones.

Overview

The simplest case is if there exists already a blank node identifier in the identifier map for the passed identifier, in which case it is simply returned. Otherwise, a new blank node identifier is generated by concatenating the string _:b and the counter. If the passed identifier is not null, an entry is created in the identifier map associating the identifier with the blank node identifier. Finally, the counter is increased by one and the new blank node identifier is returned.

Algorithm

The algorithm takes a single input variable identifier which may be null. Between its executions, the algorithm needs to keep an identifier map to relabel existing blank node identifiers consistently and a counter to generate new blank node identifiers. The counter is initialized to 0 by default.

If identifier is not null and has an entry in the identifier map, return the mapped identifier.
Otherwise, generate a new blank node identifier by concatenating the string _:b and counter.
Increment counter by 1.
If identifier is not null, create a new entry for identifier in identifier map and set its value to the new blank node identifier.
Return the new blank node identifier.

RDF Serialization-Deserialization Algorithms

This section describes algorithms to deserialize a JSON-LD document to an RDF dataset and vice versa. The algorithms are designed for in-memory implementations with random access to JSON object elements.

Throughout this section, the following vocabulary prefixes are used in compact IRIs:

Prefix	IRI
rdf	http://www.w3.org/1999/02/22-rdf-syntax-ns#
rdfs	http://www.w3.org/2000/01/rdf-schema#
xsd	http://www.w3.org/2001/XMLSchema#

Deserialize to RDF Algorithm

This algorithm deserializes a JSON-LD document to an RDF dataset. Please note that RDF does not allow a blank node to be used as a property, while JSON-LD does. Therefore, by default RDF triples that would have contained blank nodes as properties are discarded when interpreting JSON-LD as RDF. For authors and developers working with blank nodes as properties when deserializing to RDF, three potential approaches are suggested (in descending order of preference):

If the author is not yet ready to commit to a stable IRI, the property should be mapped to an IRI that is documented as unstable.
If the developer wishes to use blank nodes as properties and also wishes to interpret the data as a (non-standard) generalized RDF Dataset, there is an option, produce generalized RDF, to do so.
If the author or developer wishes to use blank nodes as properties and wishes to interpret the data as a standard (non-generalized) RDF Dataset, it is possible to losslessly interpret JSON-LD as RDF by transforming blank nodes used as properties to IRIs, by minting new "Skolem IRIs" as per Replacing Blank Nodes with IRIs of [[RDF11-CONCEPTS]].

Note: This feature is "at risk" and may be removed from this specification based on feedback. Please send feedback to public-rdf-comments@w3.org. For the current status see features "at risk" in JSON-LD 1.0

RDF graphs do not allow blank nodes to be used as an RDF predicate, while JSON-LD does. Unless the produce generalized RDF flag is set, this algorithm will exclude triples including a blank node RDF predicate.

Overview

The JSON-LD document is expanded and converted to a node map using the Node Map Generation algorithm. This allows each graph represented within the document to be extracted and flattened, making it easier to process each node object. Each graph from the node map is processed to extract RDF triples, to which any (non-default) graph name is applied to create an RDF dataset. Each node object in the node map has an @id member which corresponds to the RDF subject, the other members represent RDF predicates. Each member value is either an IRI or blank node identifier or can be transformed to an RDF literal to generate an RDF triple. Lists are transformed into an RDF Collection using the List to RDF Conversion algorithm.

Algorithm

The algorithm takes a JSON-LD document element and returns an RDF dataset. Unless the produce generalized RDF flag is set to true, RDF triples containing a blank node predicate are excluded from output.

Expand element according to the Expansion algorithm.
Generate a node map according to the Node Map Generation algorithm.
Initialize an empty RDF dataset dataset.
For each graph name and graph in node map ordered by graph name:
1. Initialize triples as an empty array.
2. For each subject and node in graph ordered by subject:
  1. For each property and values in node ordered by property:
    1. If property is @type, then for each type in values, append a triple composed of subject, rdf:type, and type to triples.
    2. Otherwise, if property is a keyword continue to the next property-values pair.
    3. Otherwise, if property is a blank node identifier and the produce generalized RDF flag is not true, continue to the next property-values pair.
    4. Otherwise, property is an IRI or blank node identifier. For each item in values:
      1. If item is a list object, initialize list triples as an empty array and list head to the result of the List Conversion algorithm, passing the value associated with the @list key from item and list triples. Append first a triple composed of subject, property, and list head to triples and finally append all triples from list triples to triples.
      2. Otherwise, item is a value object or a node object. Append a triple composed of subject, property, and the result of using the Object to RDF Conversion algorithm passing item to triples.
3. If graph name is @default, add triples to the default graph in dataset.
4. Otherwise, create a named graph in dataset composed of graph name and add triples.
Return dataset.

Object to RDF Conversion

This algorithm takes a node object or value object and transforms it into an RDF resource to be used as the object of an RDF triple.

Overview

Value objects are transformed to RDF literals as described in Data Round Tripping whereas node objects are transformed to IRIs or blank node identifiers.

Algorithm

The algorithm takes as its sole argument item which must be either a value object or node object.

If item is a node object return the IRI or blank node identifier associated with its @id member.
Otherwise, item is a value object. Initialize value to the value associated with the @value member in item.
Initialize datatype to the value associated with the @type member of item or null if item does not have such a member.
If value is true or false, set value to the string true or false which is the canonical lexical form as described in Data Round Tripping If datatype is null, set it to xsd:boolean.
Otherwise, if value is a number with a non-zero fractional part (the result of a modulo‑1 operation) or value is a number and datatype equals xsd:double, convert value to a string in canonical lexical form of an xsd:double as defined in [[!XMLSCHEMA11-2]] and described in Data Round Tripping. If datatype is null, set it to xsd:double.
Otherwise, if value is a number with no non-zero fractional part (the result of a modulo‑1 operation) or value is a number and datatype equals xsd:integer, convert value to a string in canonical lexical form of an xsd:integer as defined in [[!XMLSCHEMA11-2]] and described in Data Round Tripping. If datatype is null, set it to xsd:integer.
Otherwise, if datatype is null, set it to xsd:string or rdf:langString, depending on if item has an @language member.
Initialize literal as an RDF literal using value and datatype. If item has an @language member, add the value associated with the @language key as the language tag of literal.
Return literal.

List to RDF Conversion

List Conversion is the process of taking a list object and transforming it into an RDF Collection as defined in RDF Semantics [[!RDF-MT]].

Overview

For each element of the list a new blank node identifier is allocated which is used to generate rdf:first and rdf:rest triples. The algorithm returns the list head, which is either the the first allocated blank node identifier or rdf:nil if the list is empty.

Algorithm

The algorithm takes two inputs: an array list and an empty array list triples used for returning the generated triples.

If list is empty, return rdf:nil.
Otherwise, create an array bnodes composed of a newly generated blank node identifier for each entry in list.
Initialize an empty array list triples.
For each pair of subject from bnodes and item from list:
1. Append a triple composed of subject, rdf:first, and the result of using th Object to RDF Conversion algorithm passing item to list triples.
2. Set rest as the next entry in bnodes, or if that does not exist, rdf:nil. Append a triple composed of subject, rdf:rest, and rest to list triples.
Return the first blank node from bnodes or rdf:nil if bnodes is empty.

Serialize from RDF Algorithm

This algorithm serializes an RDF dataset consisting of a default graph and zero or more named graphs into a JSON-LD document.

Overview

Iterate through each graph in the dataset, converting each RDF Collection into a list and generating a JSON-LD document in expanded form for all RDF literals, IRIs and blank node identifiers. If the use native types flag is set to true, RDF literals with a datatype IRI that equals xsd:integer or xsd:double are converted to a JSON numbers and RDF literals with a datatype IRI that equals xsd:boolean are converted to true or false based on their lexical form as described in Data Round Tripping.

Algorithm

The algorithm takes two required inputs: an RDF dataset and a flag use native types that defaults to false.

Initialize default graph to an empty JSON object.
Initialize graph map to a JSON object consisting of a single member @default whose value references default graph.
For each graph in RDF dataset:
1. If graph is the default graph, set name to @default, otherwise to the graph name associated with graph.
2. If graph map has no name member, create one and set its value to an empty JSON object.
3. If graph is not the default graph and default graph does not have a name member, create such a member and initialize its value to a new JSON object with a single member @id whose value is name.
4. Reference the value of the name member in graph map using the variable node map.
5. For each RDF triple in graph consisting of subject, predicate, and object:
  1. If node map does not have a subject member, create one and initialize its value to a new JSON object consisting of a single member @id whose value is set to subject.
  2. Reference the value of the subject member in node map using the variable node.
  3. If object is an IRI or blank node identifier, and node map does not have an object member, create one and initialize its value to a new JSON object consisting of a single member @id whose value is set to object.
  4. If predicate equals rdf:type, and object is an IRI or blank node identifier, append object to the value of the @type member of node; unless such an item already exists. If no such member exists, create one and initialize it to an array whose only item is object. Finally, continue to the next RDF triple.
  5. Set value to the result of using the RDF to Object Conversion algorithm, passing object and use native types.
  6. If node does not have an predicate member, create one and initialize its value to an empty array.
  7. If there is no item equivalent to value in the array associated with the predicate member of node, append a reference to value to the array. Two JSON objects are considered equal if they have equivalent key-value pairs.
  8. If object is a blank node identifier or IRI, it might represent the a list node:
    1. If the object member of node map has no usages member, create one and initialize it to an empty array.
    2. Reference the usages member of the object member of node map using the variable usages.
    3. Append a new JSON object consisting of three members, node, property, and value to the usages array. The node member is set to a reference to node, property to predicate, and value to a reference to value.
For each name and graph object in graph map:
1. If graph object has no rdf:nil member, continue with the next name-graph object pair as the graph does not contain any lists that need to be converted.
2. Initialize nil to the value of the rdf:nil member of graph object.
3. For each item usage in the usages member of nil, perform the following steps:
  1. Initialize node to the value of the value of the node member of usage, property to the value of the property member of usage, and head to the value of the value member of usage.
  2. Initialize two empty arrays list and list nodes.
  3. If property equals rdf:rest, the value associated to the usages member of node has exactly 1 entry, node has a rdf:first and rdf:rest property, both of which have as value an array consisting of a single element, and node has no other members apart from an optional @type member whose value is an array with a single item equal to rdf:List, node represents a well-formed list node. Continue with the following steps:
    1. Append the only item of rdf:first member of node to the list array.
    2. Append the value of the @id member of node to the list nodes array.
    3. Initialize node usage to the only item of the usages member of node.
    4. Set node to the value of the node member of node usage, property to the value of the property member of node usage, and head to the value of the value member of node usage.
    5. If the @id member of node is a blank node identifier, continue to look for the head of the list by jumping to step 4.3.3.
  4. If property equals rdf:first, i.e., the detected list is nested inside another list
    1. and the value of the @id of node equals rdf:nil, i.e., the detected list is empty, continue with the next usage item. The rdf:nil node cannot be converted to a list object as it would result in a list of lists, which isn't supported.
    2. Otherwise, the list consists of at least one item. We preserve the head node and transform the rest of the linked list to a list object.
    3. Set head id to the value of the @id member of head.
    4. Set head to the value of the head id member of graph object so that all it's properties can be accessed.
    5. Then, set head to the the only item in the value of the rdf:rest member of head.
    6. Finally, remove the last item of the list array and the last item of the list nodes array.
  5. Remove the @id member from head.
  6. Reverse the order of the list array.
  7. Add a @list member to head and initialize its value to the the list array.
  8. For each item node id in list nodes, remove the node id member from graph object.
Initialize an empty array result.
For each subject and node in default graph ordered by subject:
1. If graph map has a subject member:
  1. Add a @graph member to node and initialize its value to an empty array.
  2. For each key-value pair s-n in the the subject member of graph map ordered by s, append n to the @graph member of node after removing its usages member, unless the only remaining member of n is @id.
2. Append node to result after removing its usages member, unless the only remaining member of node is @id.
Return result.

RDF to Object Conversion

This algorithm transforms an RDF literal to a JSON-LD value object and a RDF blank node or IRI to an JSON-LD node object.

Overview

RDF literals are transformed to value objects whereas IRIs and blank node identifiers are transformed to node objects. If the use native types flag is set to true, RDF literals with a datatype IRI that equals xsd:integer or xsd:double are converted to a JSON numbers and RDF literals with a datatype IRI that equals xsd:boolean are converted to true or false based on their lexical form as described in Data Round Tripping.

Algorithm

This algorithm takes two required inputs: a value to be converted to a JSON object and a flag use native types.

If value is an an IRI or a blank node identifier, return a new JSON object consisting of a single member @id whose value is set to value.
Otherwise value is an RDF literal:
1. Initialize a new empty JSON object result.
2. Initialize converted value to value.
3. Initialize type to null
4. If use native types is true
  1. If the datatype IRI of value equals xsd:string, set converted value to the lexical form of value.
  2. Otherwise, if the datatype IRI of value equals xsd:boolean, set converted value to true if the lexical form of value matches true, or false if it matches false. If it matches neither, set type to xsd:boolean.
  3. Otherwise, if the datatype IRI of value equals xsd:integer or xsd:double and its lexical form is a valid xsd:integer or xsd:double according [[!XMLSCHEMA11-2]], set converted value to the result of converting the lexical form to a JSON number.
5. Otherwise, if value is a language-tagged string add a member @language to result and set its value to the language tag of value.
6. Otherwise, set type to the datatype IRI of value, unless it equals xsd:string which is ignored.
7. Add a member @value to result whose value is set to converted value.
8. If type is not null, add a member @type to result whose value is set to type.
9. Return result.

Data Round Tripping

When deserializing JSON-LD to RDF JSON-native numbers are automatically type-coerced to xsd:integer or xsd:double depending on whether the number has a non-zero fractional part or not (the result of a modulo‑1 operation), the boolean values true and false are coerced to xsd:boolean, and strings are coerced to xsd:string. The numeric or boolean values themselves are converted to canonical lexical form, i.e., a deterministic string representation as defined in [[!XMLSCHEMA11-2]].

The canonical lexical form of an integer, i.e., a number with no non-zero fractional part or a number coerced to xsd:integer, is a finite-length sequence of decimal digits (0-9) with an optional leading minus sign; leading zeros are prohibited. In JavaScript, implementers can use the following snippet of code to convert an integer to canonical lexical form:

The canonical lexical form of a double, i.e., a number with a non-zero fractional part or a number coerced to xsd:double, consists of a mantissa followed by the character E, followed by an exponent. The mantissa is a decimal number and the exponent is an integer. Leading zeros and a preceding plus sign (+) are prohibited in the exponent. If the exponent is zero, it is indicated by E0. For the mantissa, the preceding optional plus sign is prohibited and the decimal point is required. Leading and trailing zeros are prohibited subject to the following: number representations must be normalized such that there is a single digit which is non-zero to the left of the decimal point and at least a single digit to the right of the decimal point unless the value being represented is zero. The canonical representation for zero is 0.0E0. xsd:double's value space is defined by the IEEE double-precision 64-bit floating point type [[!IEEE-754-1985]] whereas the value space of JSON numbers is not specified; when deserializing JSON-LD to RDF the mantissa is rounded to 15 digits after the decimal point. In JavaScript, implementers can use the following snippet of code to convert a double to canonical lexical form:

The canonical lexical form of the boolean values true and false are the strings true and false.

When JSON-native numbers are deserialized to RDF, lossless data round-tripping cannot be guaranteed, as rounding errors might occur. When serializing RDF to JSON-LD, similar rounding errors might occur. Furthermore, the datatype or the lexical representation might be lost. An xsd:double with a value of 2.0 will, e.g., result in an xsd:integer with a value of 2 in canonical lexical form when converted from RDF to JSON-LD and back to RDF. It is important to highlight that in practice it might be impossible to losslessly convert an xsd:integer to a number because its value space is not limited. While the JSON specification [[RFC4627]] does not limit the value space of numbers either, concrete implementations typically do have a limited value space.

To ensure lossless round-tripping the Serializing from RDF algorithm specifies a use native types flag which controls whether RDF literals with a datatype IRI equal to xsd:integer, xsd:double, or xsd:boolean are converted to their JSON-native counterparts. If the use native types flag is set to false, all literals remain in their original string representation.

Some JSON serializers, such as PHP's native implementation in some versions, backslash-escape the forward slash character. For example, the value http://example.com/ would be serialized as http:\/\/example.com\/. This is problematic as other JSON parsers might not understand those escaping characters. There is no need to backslash-escape forward slashes in JSON-LD. To aid interoperability between JSON-LD processors, forward slashes MUST NOT be backslash-escaped.

The Application Programming Interface

This API provides a clean mechanism that enables developers to convert JSON-LD data into a variety of output formats that are often easier to work with. A conformant JSON-LD API Implementation MUST implement the entirety of the following API.

The JSON-LD API uses Promises to represent the result of the various asynchronous operations. Promises are defined in section 4 Promises of [[!DOM-WHATWG]].

Note: This feature is "at risk" and may be removed or modified heavily from the feature described in this specification based on reviewer feedback. Please send feedback to public-rdf-comments@w3.org. For the current status see features "at risk" in JSON-LD 1.0

The JSON-LD API specification currently only refers to the "Promise" interface and does not attempt to provide any details on the specific implementation of Promises. That is, it does not reference whether or not '.then()' must be specified. This is done in order to allow for some implementation flexibility in the event the DOM Promises spec changes. The editors of the WHATWG DOM specification have asserted that the Promise interface is ready to be incorporated into specifications. The issue relates to how to properly refer to a spec living in the WHATWG as a living standard as well as how to ensure that the interface provided by the spec is stable.

The JsonLdProcessor Interface

The JsonLdProcessor interface is the high-level programming structure that developers use to access the JSON-LD transformation methods.

It is important to highlight that conformant JSON-LD API Implementations MUST NOT modify the input parameters. If an error is detected, the Promise is rejected passing a JsonLdError with the corresponding error code and processing is stopped.

Promise compact()

Compacts the given input using the context according to the steps in the Compaction algorithm:

Create a new Promise promise and return it. The following steps are then executed asynchronously.
If the passed input is a DOMString representing the IRI of a remote document, dereference it. If the retrieved document's content type is neither application/json, nor application/ld+json, nor any other media type using a +json suffix as defined in [[RFC6839]] or if the document cannot be parsed as JSON, reject the promise passing an loading document failed error.
Initialize a new empty active context. The base IRI of the active context is set to the IRI of the currently being processed document, if available; otherwise to null. If set, the compactArrays overrides the base IRI.
If an expandContext has been passed, update the active context using the Context Processing algorithm, passing the expandContext as local context.
If the input has been retrieved, the response has an HTTP Link Header [[!RFC5988]] using the http://www.w3.org/ns/json-ld#context link relation and a content type of application/json or any media type with a +json suffix as defined in [[RFC6839]] except application/ld+json, update the active context using the Context Processing algorithm, passing the context referenced in the HTTP Link Header as local context. The HTTP Link Header is ignored for documents served as application/ld+json If multiple HTTP Link Headers using the http://www.w3.org/ns/json-ld#context link relation are found, the promise is rejected with a JsonLdError whose code is set to multiple context link headers and processing is terminated.
Set expanded to the result of using the Expansion algorithm, passing the active context and input as element.
Set compacted to the result of using the Compaction algorithm, passing context, expanded as element, and if passed, the compactArrays flag in options.
Fulfill the promise passing compacted.

any input: The JSON-LD object or array of JSON-LD objects to perform the compaction upon or an IRI referencing the JSON-LD document to compact.
JsonLdContext context: The context to use when compacting the input; it can be specified by using a JSON object, an IRI, or an array consisting of JSON objects and IRIs.
optional JsonLdOptions options: A set of options to configure the algorithms. This allows, e.g., to set the input document's base IRI.

Promise expand()

Expands the given input according to the steps in the Expansion algorithm:

Create a new Promise promise and return it. The following steps are then executed asynchronously.
If the passed input is a DOMString representing the IRI of a remote document, dereference it. If the retrieved document's content type is neither application/json, nor application/ld+json, nor any other media type using a +json suffix as defined in [[RFC6839]], reject the promise passing an loading document failed error.
Initialize a new empty active context. The base IRI of the active context is set to the IRI of the currently being processed document, if available; otherwise to null. If set, the compactArrays overrides the base IRI.
If an expandContext has been passed, update the active context using the Context Processing algorithm, passing the expandContext as local context.
If the input has been retrieved, the response has an HTTP Link Header [[!RFC5988]] using the http://www.w3.org/ns/json-ld#context link relation and a content type of application/json or any media type with a +json suffix as defined in [[RFC6839]] except application/ld+json, update the active context using the Context Processing algorithm, passing the context referenced in the HTTP Link Header as local context. The HTTP Link Header is ignored for documents served as application/ld+json If multiple HTTP Link Headers using the http://www.w3.org/ns/json-ld#context link relation are found, the promise is rejected with a JsonLdError whose code is set to multiple context link headers and processing is terminated.
Set expanded to the result of using the Expansion algorithm, passing the active context and input as element.
Fulfill the promise passing expanded.

any input: The JSON-LD object or array of JSON-LD objects to perform the expansion upon or an IRI referencing the JSON-LD document to expand.
optional JsonLdOptions options: A set of options to configure the used algorithms such. This allows, e.g., to set the input document's base IRI.

Promise flatten()

Flattens the given input and compacts it using the passed context according to the steps in the Flattening algorithm:

Create a new Promise promise and return it. The following steps are then executed asynchronously.
If the passed input is a DOMString representing the IRI of a remote document, dereference it. If the retrieved document's content type is neither application/json, nor application/ld+json, nor any other media type using a +json suffix as defined in [[RFC6839]], reject the promise passing an loading document failed error.
Initialize a new empty active context. The base IRI of the active context is set to the IRI of the currently being processed document, if available; otherwise to null. If set, the compactArrays overrides the base IRI.
If an expandContext has been passed, update the active context using the Context Processing algorithm, passing the expandContext as local context.
If the input has been retrieved, the response has an HTTP Link Header [[!RFC5988]] using the http://www.w3.org/ns/json-ld#context link relation and a content type of application/json or any media type with a +json suffix as defined in [[RFC6839]] except application/ld+json, update the active context using the Context Processing algorithm, passing the context referenced in the HTTP Link Header as local context. The HTTP Link Header is ignored for documents served as application/ld+json If multiple HTTP Link Headers using the http://www.w3.org/ns/json-ld#context link relation are found, the promise is rejected with a JsonLdError whose code is set to multiple context link headers and processing is terminated.
Set expanded to the result of using the Expansion algorithm, passing the active context and input as element.
Initialize an empty identifier map and a counter (set to 0) to be used by the Generate Blank Node Identifier algorithm.
Set flattened to the result of using the Flattening algorithm, passing expanded as element, context, and if passed, the compactArrays flag in options (which is internally passed to the Compaction algorithm).
Fulfill the promise passing flattened.

any input: The JSON-LD object or array of JSON-LD objects or an IRI referencing the JSON-LD document to flatten.
optional JsonLdContext? context: The context to use when compacting the flattened input; it can be specified by using a JSON object, an IRI, or an array consisting of JSON objects and IRIs. If not passed or null is passed, the result will not be compacted but kept in expanded form.
optional JsonLdOptions options: A set of options to configure the used algorithms such. This allows, e.g., to set the input document's base IRI.

The JsonLdContext type is used to refer to a value that that may be a JSON object, an IRI, or an array of JSON objects and IRIs.

The JsonLdOptions Type

The JsonLdOptions type is used to pass various options to the JsonLdProcessor methods.

DOMString? base: The base IRI to use when expanding or compacting the document. If set, this overrides the input document's IRI.
boolean compactArrays = true: If set to true, the JSON-LD processor replaces arrays with just one element with that element during compaction. If set to false, all arrays will remain arrays even if they have just one element.
LoadDocumentCallback documentLoader = null: The callback of the loader to be used to retrieve remote documents and contexts. If specified, it MUST be used to retrieve remote documents and contexts; otherwise, if not specified, the processor's built-in loader MUST be used.
(object? or DOMString) expandContext = null: A context that is used to initialize the active context when expanding a document.
DOMString processingMode = "json-ld-1.0": If set to json-ld-1.0, the JSON-LD processor MUST produce exactly the same results as the algorithms defined in this specification. If set to another value, the JSON-LD processor is allowed to extend or modify the algorithms defined in this specification to enable application-specific optimizations. The definition of such optimizations is beyond the scope of this specification and thus not defined. Consequently, different implementations MAY implement different optimizations. Developers MUST NOT define modes beginning with json-ld as they are reserved for future versions of this specification.

Remote Document and Context Retrieval

Developers can utilize a callback to control how remote documents and contexts are retrieved by JSON-LD API Implementations. This section details the parameters of that callback and the data structure used to return the retrieved context.

LoadDocumentCallback

The LoadDocumentCallback defines a callback that custom document loaders have to implement to be used to retrieve remote documents and contexts.

DOMString url: The URL of the remote document or context to load.

All errors MUST result in the Promise being rejected with a JsonLdError whose code is set to loading document failed or multiple context link headers as described in the next section.

RemoteDocument

The RemoteDocument type is used by a LoadDocumentCallback to return information about a remote document or context.

DOMString contextUrl = null: If available, the value of the HTTP Link Header [[!RFC5988]] using the http://www.w3.org/ns/json-ld#context link relation in the response. If the response's content type is application/ld+json, the HTTP Link Header MUST be ignored. If multiple HTTP Link Headers using the http://www.w3.org/ns/json-ld#context link relation are found, the Promise of the LoadDocumentCallback MUST be rejected with a JsonLdError whose code is set to multiple context link headers.
DOMString documentUrl: The final URL of the loaded document. This is important to handle HTTP redirects properly.
any document: The retrieved document. This can either be the raw payload or the already parsed document.

Error Handling

This section describes the datatype definitions used within the JSON-LD API for error handling.

JsonLdError

The JsonLdError type is used to report processing errors.

JsonLdErrorCode code: a string representing the particular error type, as described in the various algorithms in this document.
DOMString? message = null: an optional error message containing additional debugging information. The specific contents of error messages are outside the scope of this specification.

JsonLdErrorCode

The JsonLdErrorCode represents the collection of valid JSON-LD error codes.

loading document failed: The document could not be loaded or parsed as JSON.
list of lists: A list of lists was detected. List of lists are not supported in this version of JSON-LD due to the algorithmic complexity associated with deserialization to RDF.
invalid @index value: An @index member was encountered whose value was not a string.
conflicting indexes: Multiple conflicting indexes have been found for the same node.
invalid @id value: An @id member was encountered whose value was not a string.
invalid local context: In invalid local context was detected.
multiple context link headers: Multiple HTTP Link Headers [[!RFC5988]] using the http://www.w3.org/ns/json-ld#context link relation have been detected.
loading remote context failed: There was a problem encountered loading a remote context.
invalid remote context: No valid context document has been found for a referenced, remote context.
recursive context inclusion: A cycle in remote context inclusions has been detected.
invalid base IRI: An invalid base IRI has been detected, i.e., it is neither an absolute IRI nor null.
invalid vocab mapping: An invalid vocabulary mapping has been detected, i.e., it is neither an absolute IRI nor null.
invalid default language: The value of the default language is not a string or null and thus invalid.
keyword redefinition: A keyword redefinition has been detected.
invalid term definition: An invalid term definition has been detected.
invalid reverse property: An invalid reverse property definition has been detected.
invalid IRI mapping: A local context contains a term that has an invalid or missing IRI mapping.
cyclic IRI mapping: A cycle in IRI mappings has been detected.
invalid keyword alias: An invalid keyword alias definition has been encountered.
invalid type mapping: An @type member in a term definition was encountered whose value could not be expanded to an absolute IRI.
invalid language mapping: An @language member in a term definition was encountered whose value was neither a string nor null and thus invalid.
colliding keywords: Two properties which expand to the same keyword have been detected. This might occur if a keyword and an an alias thereof are used at the same time.
invalid container mapping: An @container member was encountered whose value was not one of the following strings: @list, @set, or @index.
invalid type value: An invalid value for an @type member has been detected, i.e., the value was neither a string nor an array of strings.
invalid value object: A value object with disallowed members has been detected.
invalid value object value: An invalid value for the @value member of a value object has been detected, i.e., it is neither a scalar nor null.
invalid language-tagged string: A language-tagged string with an invalid language value was detected.
invalid language-tagged value: A number, true, or false with an associated language tag was detected.
invalid typed value: A typed value with an invalid type was detected.
invalid set or list object: A set object or list object with disallowed members has been detected.
invalid language map value: An invalid value in a language map has been detected. It has to be a string or an array of strings.
compaction to list of lists: The compacted document contains a list of lists as multiple lists have been compacted to the same term.
invalid reverse property map: An invalid reverse property map has been detected. No keywords apart from @context are allowed in reverse property maps.
invalid @reverse value: An invalid value for an @reverse member has been detected, i.e., the value was not a JSON object.
invalid reverse property value: An invalid value for a reverse property has been detected. The value of an inverse property must be a node object.

Introduction

Features

Expansion

Compaction

Flattening

RDF Serialization/Deserialization

Conformance

General Terminology

Algorithm Terms

Context Processing Algorithms

Context Processing Algorithm

Overview

Algorithm

Create Term Definition

Overview

Algorithm

IRI Expansion

Overview

Algorithm

Expansion Algorithms

Expansion Algorithm

Overview

Algorithm

Value Expansion

Overview

Algorithm

Compaction Algorithms

Compaction Algorithm

Overview

Algorithm

Inverse Context Creation

Overview

Algorithm

IRI Compaction

Overview

Algorithm

Term Selection

Overview

Algorithm

Value Compaction

Overview

Algorithm

Flattening Algorithms

Flattening Algorithm

Overview

Algorithm

Node Map Generation

Overview

Algorithm

Generate Blank Node Identifier

Overview

Algorithm

RDF Serialization-Deserialization Algorithms

Deserialize to RDF Algorithm

Overview

Algorithm

Object to RDF Conversion

Overview

Algorithm

List to RDF Conversion

Overview

Algorithm

Serialize from RDF Algorithm

Overview

Algorithm

RDF to Object Conversion

Overview

Algorithm

Data Round Tripping

The Application Programming Interface

The JsonLdProcessor Interface

The JsonLdOptions Type

Remote Document and Context Retrieval

LoadDocumentCallback

RemoteDocument

Error Handling

JsonLdError

JsonLdErrorCode

Acknowledgements