--- a/spec/latest/json-ld-syntax/index.html Sat Feb 02 11:59:50 2013 -0500
+++ b/spec/latest/json-ld-syntax/index.html Sat Feb 02 14:08:36 2013 -0500
@@ -1348,7 +1348,7 @@
programming languages are able to handle empty property names.</p>
<section>
- <h2>Context via HTTP Link Header</h2>
+ <h2>Interpreting JSON as JSON-LD</h2>
<p>Ordinary JSON documents can be interpreted as JSON-LD by referencing a JSON-LD
<tref>context</tref> document in an HTTP Link Header. Doing so allows JSON to
@@ -2551,11 +2551,9 @@
<li>Every <tdef>edge</tdef> has a direction associated with it and is labeled with
an <tref>IRI</tref> or a <tref>blank node identifier</tref>. Within the JSON-LD syntax
these edge labels are called <tdef title="property">properties</tdef>.</li>
- <li>Every <tdef>node</tdef> represents a <tdef>resource</tdef> or a
- <tdef>value</tdef>. <tref title="resource">Resources</tref> are labeled
- using either an <tref>IRI</tref> or a <tref>blank node identifier</tref>.
- <tref title="value">Values</tref> are a
- <tref>JSON-LD value</tref> or a <tref>list</tref>.</li>
+ <li>Every <tdef>node</tdef> is either an <tref>IRI</tref>,
+ a <tref>blank node</tref>, a <tref>JSON-LD value</tref>,
+ or a <tref>list</tref>.</li>
<li>A <tref>node</tref> having an outgoing edge MUST be an <tref>IRI</tref> or a
<tref>blank node</tref>.</li>
<li>A <tref>JSON-LD graph</tref> MUST NOT contain unconnected <tref title="node">nodes</tref>,
@@ -2565,8 +2563,8 @@
defined in [[RFC3987]]. <tref title="IRI">IRIs</tref> used within a
<tref>JSON-LD graph</tref> SHOULD return a <tref>Linked Data</tref> document describing
the resource denoted by that IRI when being dereferenced.</li>
- <li>A <tdef>blank node</tdef> is a <tref>resource</tref> which is not
- labeled with an <tref>IRI</tref>. A blank node MAY be identified
+ <li>A <tdef>blank node</tdef> is a <tref>node</tref> which is not
+ an <tref>IRI</tref>. A blank node MAY be identified
using a <tref>blank node identifier</tref>.</li>
<li>A <tdef>blank node identifier</tdef> is a string that can be used as an identifier
for a <tref>blank node</tref> within the scope of a <tref>JSON-LD document</tref>.
@@ -3280,25 +3278,24 @@
<dt>Optional parameters:</dt>
<dd>
<dl>
- <dt><code>form</code></dt>
- <dd>Determines the serialization form for the JSON-LD document. The only
- valid value at the moment is <code>expanded</code>. If no form is
- specified in an HTTP request header to an HTTP server, the server MAY
- choose any form. If no form is specified in an HTTP response, the form
- MUST NOT be assumed to take any particular form.</dd>
- </dl>
- <dl>
<dt><code>profile</code></dt>
<dd>A whitespace-separated list of IRIs identifying specific constraints
or conventions that apply to a JSON-LD document. A profile MUST NOT change
- the semantics of the resource representation when processed without profile
- knowledge, so that clients both with and without knowledge of a profiled
- resource can safely use the same representation. The <code>profile</code>
+ the semantics of the resource representation. The <code>profile</code>
parameter MAY also be used by clients to express their preferences in the
content negotiation process. It is RECOMMENDED that profile IRIs are
dereferenceable and provide useful documentation at that IRI. This
- specification, however, does not define any formats for such profile
- descriptions.
+ specification defines four values for the <code>profile</code> parameter.
+ To request or specify Expanded JSON-LD document form, the
+ <code>http://www.w3.org/ns/json-ld#expanded</code> URL SHOULD be used.
+ To request or specify Expanded, Flattened JSON-LD document form, the
+ <code>http://www.w3.org/ns/json-ld#expanded-flattened</code> URL SHOULD
+ be used.
+ To request or specify Compacted JSON-LD document form, the
+ <code>http://www.w3.org/ns/json-ld#compacted</code> URL SHOULD be used.
+ To request or specify Compacted, Flattened JSON-LD document form, the
+ <code>http://www.w3.org/ns/json-ld#compacted-flattened</code> URL
+ SHOULD be used.
</dd>
</dl>
</dd>