diff --git a/spec/latest/common/terms.html b/spec/latest/common/terms.html
index 49313b480..f8753fcff 100644
--- a/spec/latest/common/terms.html
+++ b/spec/latest/common/terms.html
@@ -69,7 +69,7 @@
IRI, nor a JSON-LD value, nor a list.
A blank node does not contain a de-referenceable
identifier because it is either ephemeral in nature or does not contain information that needs to be
- linked to from outside of the linked data graph. A blank node is assigned an identifier starting with
+ linked to from outside of the linked data graph. A blank node is assigned an identifier starting with
the prefix _:
.
The following is a list of issues open at the time of publication.
- - - + + + - - - - - - + + + + + + - - + - + - - - + + - - - - + + + +The following is a list of issues open at the time of publication.
- + diff --git a/spec/latest/json-ld/index.html b/spec/latest/json-ld/index.html index 05d3e56c3..8152a67ac 100644 --- a/spec/latest/json-ld/index.html +++ b/spec/latest/json-ld/index.html @@ -1,4 +1,4 @@ - +An expanded term definition can include a @context
- property, which defines a context for values of properties defined using that term. This allows
values to use term definitions, base IRI,
vocabulary mapping or default language which is different from the
@@ -2436,7 +2436,7 @@
In this case, the social profile is defined using the schema.org vocabulary, but interest is imported from FOAF, and is used to define a node describing one of Manu's interests where those properties now come from the FOAF vocabulary.
-Expanding this document, uses a combination of terms defined in the outer context, and those defined specifically for that term.
+Expanding this document, uses a combination of terms defined in the outer context, and those defined specifically for that term in an embedded context.
@@ -2479,7 +2479,19 @@-Scoped Contexts
-->
Scoping on @type
is useful when common properties are used to relate things of different types, where the vocabularies in use within different entities calls for different context scoping. For example, `hasPart`/`partOf` may be common terms used in a document, but mean different things depending on the context.
Scoping on @type
is useful when common properties are used to
+ relate things of different types, where the vocabularies in use within
+ different entities calls for different context scoping. For example,
+ hasPart
/partOf
may be common terms used in a document, but mean
+ different things depending on the context.
When expanding, each value of @type
is considered
+ (ordering them lexographically) where that value is also a term in
+ the active context having its own embedded context. If so, that
+ embedded context is applied to the active context. When compacting, if
+ a term is chosen to represent an IRI used as a value of @type
where that
+ term definition also has an embedded context, it is then applied to the
+ active context to affect further compaction.
The values of @type
are unordered, so if multiple
types are listed, the order that scoped contexts are applied is based on
@@ -5102,25 +5114,23 @@
The following is a list of issues open at the time of publication.
- + - - - - - - - - + + + + + + - - - - - - - - + + + + + + + +