diff --git a/Gemfile.lock b/Gemfile.lock index 7e296e7..d41cbde 100644 --- a/Gemfile.lock +++ b/Gemfile.lock @@ -1,16 +1,18 @@ GIT remote: git://github.com/ruby-rdf/json-ld.git - revision: 7717390f78fea8152f9d82a1d52f3695dd36575e + revision: d1acea9a066ef1dcc28a24212dea29559b07a60d branch: develop specs: json-ld (3.0.2) + link_header (~> 0.0, >= 0.0.8) multi_json (~> 1.13) rack (>= 1.6, < 3.0) + rdf (~> 3.0, >= 3.0.8) GEM remote: https://rubygems.org/ specs: - addressable (2.5.2) + addressable (2.6.0) public_suffix (>= 2.0.2, < 4.0) bcp47 (0.3.3) i18n @@ -29,7 +31,7 @@ GEM hamster (3.0.0) concurrent-ruby (~> 1.0) htmlentities (4.3.4) - i18n (1.4.0) + i18n (1.5.3) concurrent-ruby (~> 1.0) json-ld-preloaded (3.0.2) json-ld (~> 3.0) @@ -71,14 +73,14 @@ GEM multi_json (1.13.1) net-http-persistent (3.0.0) connection_pool (~> 2.2) - nokogiri (1.9.1) + nokogiri (1.10.1) mini_portile2 (~> 2.4.0) nokogumbo (1.5.0) nokogiri public_suffix (3.0.3) rack (2.0.6) rake (12.3.2) - rdf (3.0.9) + rdf (3.0.10) hamster (~> 3.0) link_header (~> 0.0, >= 0.0.8) rdf-aggregate-repo (2.2.1) @@ -124,7 +126,7 @@ GEM rdf-turtle (~> 3.0, >= 3.0.3) rdf-trix (2.2.1) rdf (>= 2.2, < 4.0) - rdf-turtle (3.0.3) + rdf-turtle (3.0.5) ebnf (~> 1.1) rdf (~> 3.0) rdf-vocab (3.0.4) diff --git a/Rakefile b/Rakefile index e14cf9c..94d4d38 100644 --- a/Rakefile +++ b/Rakefile @@ -1,3 +1,4 @@ +require 'bundler/setup' task default: :test desc "Test examples in spec files" diff --git a/common/terms.html b/common/terms.html index 62f5aa1..fc58f1c 100644 --- a/common/terms.html +++ b/common/terms.html @@ -112,6 +112,16 @@ Whenever possible, an edge should be labeled with an IRI.
The use of blank node identifiers to label properties is obsolete, and may be removed in a future version of JSON-LD.
+
embedded context
+ An embedded context is a dictionary composed of a combintation of + term definitions, a vocabulary mapping, a base IRI and default language. + An embedded context may appear as part of a node object or value object using the + @context member. +
+
scoped context
+ A scoped context is part of an expanded term definition using the + @context member. It has the same form as an embedded context. +
expanded term definition
An expanded term definition is a term definition where the value is a dictionary @@ -150,7 +160,8 @@ is a graph object which does not have an @id member. Note that node objects may have a @graph member, but are not considered graph objects if they include any other members. - A top-level object consisting of @graph is also not a graph object.
+ A top-level object consisting of @graph is also not a graph object. + Note that a node object may also represent a named graph it it includes other properties.
index map
An index map is a dictionary value of a term defined with @container set to @index, @@ -212,7 +223,8 @@ A list is an ordered sequence of IRIs, blank nodes, and JSON-LD values. See RDF collection in [[RDF-SCHEMA]].
list object
- A list object is a dictionary that has a @list key.
+ A list object is a dictionary that has a @list key. + It may also have an @index key, but no other members.
literal
An object expressed as a value such as a string, number or in expanded form.
local context
@@ -294,7 +306,8 @@ are resolved relative to the vocabulary mapping, not the base IRI.
set object
- A set object is a dictionary that has an @set member.
+ A set object is a dictionary that has an @set member. + It may also have an @index key, but no other members.
subject
A subject is a node in a linked data graph @@ -335,5 +348,5 @@ A value object is a dictionary that has an @value member.
vocabulary mapping
The vocabulary mapping is set in the context using the @vocab key - whose value MUST be an absolute IRI or null.
+ whose value MUST be an IRI or null. diff --git a/index.html b/index.html index 9ce7f8f..b15ce8f 100644 --- a/index.html +++ b/index.html @@ -1684,6 +1684,8 @@

application/ld+json

Subtype name:
ld+json
Required parameters:
+
None
+
Optional parameters:
profile
@@ -1697,11 +1699,11 @@

application/ld+json

http://www.w3.org/ns/json-ld#framed
To specify a JSON-LD Frame.
+

The http://www.w3.org/ns/json-ld#framed SHOULD + be used when serving and requesting a JSON-LD frame document.

-
Optional parameters:
-
None.
Encoding considerations:
See RFC 8259, section 11.
Security considerations: