diff --git a/common/terms.html b/common/terms.html index 62f5aa19..d3aa9851 100644 --- a/common/terms.html +++ b/common/terms.html @@ -335,5 +335,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 d5d3aba0..ce8365a0 100644 --- a/index.html +++ b/index.html @@ -770,7 +770,7 @@

The Context

either be a simple string, mapping the term to an IRI, or a dictionary.

-

When a when a member with a term key has a dictionary value, the dictionary is called +

When a member with a term key has a dictionary value, the dictionary is called an expanded term definition. The example above specifies that the values of image and homepage, if they are strings, are to be interpreted as @@ -10469,16 +10469,24 @@

application/ld+json

It is RECOMMENDED that profile URIs are dereferenceable and provide useful documentation at that URI. For more information and background please refer to [[RFC6906]].

-

This specification defines three values for the profile parameter. - To request or specify expanded JSON-LD document form, - the URI http://www.w3.org/ns/json-ld#expanded SHOULD be used. - To request or specify compacted JSON-LD document form, - the URI http://www.w3.org/ns/json-ld#compacted SHOULD be used. - To request or specify flattened JSON-LD document form, - the URI http://www.w3.org/ns/json-ld#flattened SHOULD be used. - Please note that, according [[HTTP11]], the value of the profile - parameter has to be enclosed in quotes (") because it contains - special characters and, if multiple profiles are combined, whitespace.

+

This specification defines four values for the profile parameter.

+
+
http://www.w3.org/ns/json-ld#expanded
+
To request or specify expanded JSON-LD document form.
+
http://www.w3.org/ns/json-ld#compacted
+
To request or specify compacted JSON-LD document form.
+
http://www.w3.org/ns/json-ld#flattened
+
To request or specify flattened JSON-LD document form.
+
http://www.w3.org/ns/json-ld#framed
+
To request or specify framed JSON-LD document form.
+
+

Other specifications may publish additional profile parameter + URIs with their own defined sematics.

+

+ When used as a media type paramter [[RFC4288]] + in an HTTP Accept header [[RFC7231]], + the value of the profile parameter MUST be enclosed in quotes (") if it contains + special characters such as whitespace, which is required when multiple profile URIs are combined.

When processing the "profile" media type parameter, it is important to note that its value contains one or more URIs and not IRIs. In some cases it might therefore be necessary to convert between IRIs and URIs as specified in @@ -10488,16 +10496,16 @@

application/ld+json

Encoding considerations:
-
See RFC 6839, section 3.1.
+
See RFC 8259, section 11.
Security considerations:
-
See [[RFC8259]] +
See RFC 8259, section 12 [[RFC8259]]

Since JSON-LD is intended to be a pure data exchange format for directed graphs, the serialization SHOULD NOT be passed through a code execution mechanism such as JavaScript's eval() function to be parsed. An (invalid) document may contain code that, when executed, could lead to unexpected side effects compromising the security of a system.

-

When processing JSON-LD documents, links to remote contexts are +

When processing JSON-LD documents, links to remote contexts and frames are typically followed automatically, resulting in the transfer of files without the explicit request of the user for each one. If remote contexts are served by third parties, it may allow them to gather @@ -10537,7 +10545,7 @@

application/ld+json

Person & email address to contact for further information:
-
Manu Sporny <msporny@digitalbazaar.com>
+
Ivan Herman <ivan@w3.org>
Intended usage:
Common
Restrictions on usage:
@@ -10552,6 +10560,56 @@

application/ld+json

are treated as in RDF syntaxes, as per RDF 1.1 Concepts and Abstract Syntax [[RDF11-CONCEPTS]].

+ +
+

Examples

+

The following examples illustrate different ways in which the profile parameter may be used + to describe different acceptable responses.

+ + 
+    
+
+

Requests the server to return the requested resource as JSON-LD + in expanded document form.

+ + 
+    
+
+

Requests the server to return the requested resource as JSON-LD + in compacted document form. + As no explicit context resource is specified, the server compacts + using an application-specific default context.

+ + 
+    
+
+

Requests the server to return the requested resource as JSON-LD + in both compacted document form + and flattened document form. + Note that as whitespace is used to separate the two URIs, they + are enclosed in double quotes (").

+