diff --git a/common/algorithm-terms.html b/common/algorithm-terms.html index e9968d2e..3cc56e8f 100644 --- a/common/algorithm-terms.html +++ b/common/algorithm-terms.html @@ -49,8 +49,8 @@ copied into a new processor state when entering a new JSON object.
promise
- A promise is an object that represents the eventual result of a single asynchronous operation. - Promises are defined in [[ECMASCRIPT-6.0]].
+ A promise is an object that represents the eventual result of a single asynchronous operation. + Promises are defined in [[ECMASCRIPT]].
require all flag
A flag specifying that all properties present in the input frame MUST either have a default value or be present in the JSON-LD diff --git a/common/terms.html b/common/terms.html index 322b72b7..a44f9b3f 100644 --- a/common/terms.html +++ b/common/terms.html @@ -10,19 +10,19 @@ Sets and Lists in the JSON-LD Syntax specification [[JSON-LD11]]).
JSON object
- In the JSON serialization, an object structure is represented as a pair of curly brackets surrounding zero or + In the JSON serialization, an object structure is represented as a pair of curly brackets surrounding zero or more key-value pairs. A key is a string. A single colon comes after each key, separating the key from the value. A single comma separates a value from a following key. In JSON-LD the keys in an object MUST be unique. In the internal representation a JSON object is equivalent to a - dictionary (see [[WEBIDL]]).
+ dictionary (see [[!WEBIDL]]).
JSON-LD internal representation
The JSON-LD internal representation is the result of transforming a JSON syntactic structure into the core data structures suitable for direct processing: arrays, dictionaries, strings, numbers, booleans, and null.
null
- The use of the null value within JSON-LD is used to + The use of the null value within JSON-LD is used to ignore or reset values. A key-value pair in the @context where the value, or the @id of the value, is null explicitly decouples a term's association with an IRI. A key-value pair in @@ -32,22 +32,22 @@ null in expanded form, then the entire JSON object is ignored.
number
- In the JSON serialization, a number is similar to that used in most programming languages, except + In the JSON serialization, a number is similar to that used in most programming languages, except that the octal and hexadecimal formats are not used and that leading zeros are not allowed. In the internal representation, a number is equivalent to either a long or double, depending - on if the number has a non-zero fractional part (see [[WEBIDL]]).
+ on if the number has a non-zero fractional part (see [[!WEBIDL]]).
scalar
A scalar is either a JSON string, number, true, or false.
string
- A string is a sequence of zero or more Unicode (UTF-8) characters, + A string is a sequence of zero or more Unicode (UTF-8) characters, wrapped in double quotes, using backslash escapes (if necessary). A character is represented as a single character string.
true and false
- Values that are used to express one of two possible + Values that are used to express one of two possible boolean states.
@@ -182,12 +182,12 @@ section of the JSON-LD specification [[JSON-LD11]]. A linked data graph is a generalized representation of an RDF graph - as defined in [[!RDF-CONCEPTS]]. + as defined in [[!RDF11-CONCEPTS]].
list
A list is an ordered sequence of IRIs, blank nodes, and JSON-LD values. See RDF collection - in [[RDF-SCHEMA]].
+ in [[!RDF-SCHEMA]].
list object
A list object is a JSON object that has an @list member.
@@ -282,7 +282,7 @@
typed literal
A typed literal is a literal with an associated IRI which indicates the literal's datatype. - See RDF literal in [[!RDF-CONCEPTS]].
+ See RDF literal in [[!RDF11-CONCEPTS]].
typed value
A typed value consists of a value, which is a string, and a type, which is an IRI.
diff --git a/index.html b/index.html index f92b2ca3..a9505463 100644 --- a/index.html +++ b/index.html @@ -202,11 +202,11 @@

Introduction

To understand the basics in this specification you must first be familiar with - JSON, which is detailed in [[!RFC7159]]. You must also understand the + JSON, which is detailed in [[!RFC8288]]. You must also understand the JSON-LD syntax defined in the JSON-LD 1.1 Syntax specification [[!JSON-LD11]], which is the base syntax used by all of the algorithms in this document. To understand the API and how it is intended to operate in a programming environment, it is useful to have working - knowledge of the JavaScript programming language [[ECMASCRIPT-6.0]] and + knowledge of the JavaScript programming language [[ECMASCRIPT]] and WebIDL [[WEBIDL]]. To understand how JSON-LD maps to RDF, it is helpful to be familiar with the basic RDF concepts [[RDF11-CONCEPTS]].

@@ -232,8 +232,8 @@

Contributing

Terminology

-

This document uses the following terms as defined in JSON [[!RFC7159]]. Refer - to the JSON Grammar section in [[!RFC7159]] for formal definitions.

+

This document uses the following terms as defined in JSON [[!RFC8288]]. Refer + to the JSON Grammar section in [[!RFC8288]] for formal definitions.

@@ -4395,7 +4395,7 @@

Data Round Tripping

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 [[!RFC7159]] + its value space is not limited. While the JSON specification [[!RFC8288]] does not limit the value space of numbers either, concrete implementations typically do have a limited value space.

@@ -4431,7 +4431,7 @@

The Application Programming Interface

The JSON-LD API uses Promises to represent the result of the various asynchronous operations. - Promises are defined in [[ECMASCRIPT-6.0]]. + Promises are defined in [[ECMASCRIPT]]. General use within specifications can be found in [[promises-guide]].

@@ -4548,7 +4548,7 @@

The JsonLdProcessor Interface

as local context. If expandContext is a dictionary having an @context member, pass that member's value instead. -
  • Once input has been retrieved, the response has an HTTP Link Header [[!RFC5988]] +
  • Once input has been retrieved, the response has an HTTP Link Header [[!RFC8288]] 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 @@ -4765,7 +4765,7 @@

    RemoteDocument

    contextUrl
    -
    If available, the value of the HTTP Link Header [[!RFC5988]] using the +
    If available, the value of the HTTP Link Header [[!RFC8288]] 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 is ignored. If multiple HTTP Link Headers using @@ -4963,7 +4963,7 @@

    JsonLdErrorCode

    loading remote context failed
    There was a problem encountered loading a remote context.
    multiple context link headers
    -
    Multiple HTTP Link Headers [[!RFC5988]] using the +
    Multiple HTTP Link Headers [[!RFC8288]] using the http://www.w3.org/ns/json-ld#context link relation have been detected.
    processing mode conflict