--- a/spec/latest/json-ld-framing/index.html Tue Aug 28 20:01:17 2012 +0200
+++ b/spec/latest/json-ld-framing/index.html Wed Aug 29 11:25:51 2012 +0200
@@ -399,6 +399,27 @@
<cite><a href="http://www.w3.org/TR/rdf11-concepts/#dfn-rdf-triple">RDF triple</a></cite>,
which most closely aligns to <a>Quad</a>.</li>
</ol>
+
+<div class="issue" data-number="47">
+ <p>Richard Cyganiak suggests that the data model is at odds with [[RDF-CONCEPTS]] and should
+ be more closely aligned with it instead of creating new terminology.</p>
+ <p>One proposal requiring further discussion would be to simplify the Linked Data definition
+ to something like this:</p>
+ <ol>
+ <li>Linked Data is a set of documents, each containing a representation of a linked data graph.</li>
+ <li>A linked data graph is an unordered labeled directed graph.</li>
+ <li>A node having an outgoing edge MUST be an IRI or Blank Node.</li>
+ <li>A node having an incoming edge MUST be an IRI, Blank Node or value such as a number or a string.</li>
+ <li>A node MAY have both incoming and outgoing edges.</li>
+ <li>An edge MUST be an absolute IRI.</li>
+ <li>Two nodes related by an edge form a <em>statement</em> where the nodes are referred to <em>subject</em>
+ and <em>object</em> and the edge referred to as the <em>predicate</em>.
+ <strong>(At Risk, we may not need to talk about subjects, predicates or objects at all).</strong></li>
+ <li>IRIs used within a linked data graph SHOULD be dereferenceable to a Linked Data document describing
+ the resource denoted by that IRI.</li>
+ </ol>
+</div>
+
</section>
<section>
--- a/spec/latest/json-ld-syntax/index.html Tue Aug 28 20:01:17 2012 +0200
+++ b/spec/latest/json-ld-syntax/index.html Wed Aug 29 11:25:51 2012 +0200
@@ -508,7 +508,7 @@
used, more semantics are added to the JSON markup.</p>
<section>
-<h2>Linking Data</h2>
+<h2>Linked Data</h2>
<p>
The following definition for <tref>Linked Data</tref> is the one that will
@@ -530,9 +530,25 @@
<p class="issue">An illustration of a linked data graph would probably help here.</p>
-<p class="issue" data-number="136">EricP suggests that the definitions of subject and
-object, while being practical, are at odds with [[RDF-CONCEPTS]]
-use in their roles within a triple.</p>
+<div class="issue" data-number="47">
+ <p>Richard Cyganiak suggests that the data model is at odds with [[RDF-CONCEPTS]] and should
+ be more closely aligned with it instead of creating new terminology.</p>
+ <p>One proposal requiring further discussion would be to simplify the Linked Data definition
+ to something like this:</p>
+ <ol>
+ <li>Linked Data is a set of documents, each containing a representation of a linked data graph.</li>
+ <li>A linked data graph is an unordered labeled directed graph.</li>
+ <li>A node having an outgoing edge MUST be an IRI or Blank Node.</li>
+ <li>A node having an incoming edge MUST be an IRI, Blank Node or value such as a number or a string.</li>
+ <li>A node MAY have both incoming and outgoing edges.</li>
+ <li>An edge MUST be an absolute IRI.</li>
+ <li>Two nodes related by an edge form a <em>statement</em> where the nodes are referred to <em>subject</em>
+ and <em>object</em> and the edge referred to as the <em>predicate</em>.
+ <strong>(At Risk, we may not need to talk about subjects, predicates or objects at all).</strong></li>
+ <li>IRIs used within a linked data graph SHOULD be dereferenceable to a Linked Data document describing
+ the resource denoted by that IRI.</li>
+ </ol>
+</div>
<p class="note">JSON-LD allows properties to be BNodes, while RDF does
not. When used as just JSON-LD, this is not unreasonable;
@@ -569,61 +585,63 @@
-->
</pre>
-<section>
- <h2>Syntax Tokens and Keywords</h2>
-
- <p>JSON-LD specifies a number of syntax tokens and <tdef title="keyword">keywords</tdef>
- that are a core part of the language:</p>
-
- <dl>
- <dt><code>@context</code></dt>
- <dd>Used to define the short-hand names that are used throughout a JSON-LD
- document. These short-hand names are called <tref>term</tref>s and help
- developers to express specific identifiers in a compact manner. The
- <code>@context</code> keyword is described in detail in the section titled
- <a href="#the-context"></a>.</dd>
- <dt><code>@graph</code></dt><dd>Used to explicitly label a <tref>linked data graph</tref>.
- This keyword is described in <a href="#named-graphs"></a>.</dd>
- <dt><code>@id</code></dt>
- <dd>Used to uniquely identify <em>things</em> that are being described in the document.
- This keyword is described in
- <a href="#identifying-the-subject"></a>.</dd>
- <dt><code>@value</code></dt>
- <dd>Used to specify the data that is associated with a particular
- <tref>property</tref> in the graph. This keyword is described in
- <a href="#string-internationalization"></a> and
- <a href="#typed-values"></a>.</dd>
- <dt><code>@language</code></dt>
- <dd>Used to specify the native language for a particular value or the default
- language of a JSON-LD document. This keyword is described in the section titled
- <a href="#string-internationalization"></a>.</dd>
- <dt><code>@type</code></dt>
- <dd>Used to set the data type of a <tref>subject</tref> or
- <tref>typed value</tref>. This keyword is described in the section titled
- <a href="#typed-values"></a>.</dd>
- <dt><code>@container</code></dt>
- <dd>Used to set the container of a particular value.
- This keyword is described in the section titled <a href="#sets-and-lists"></a>.</dd>
- <dt><code>@list</code></dt>
- <dd>Used to express an ordered set of data.
- This keyword is described in the section titled <a href="#sets-and-lists"></a>.</dd>
- <dt><code>@set</code></dt>
- <dd>Used to express an unordered set of data.
- This keyword is described in the section titled <a href="#sets-and-lists"></a>.</dd>
- <dt><code>@vocab</code></dt>
- <dd>Used to set the base <tref>IRI</tref> for all property IRIs affected by the
- <tref>active context</tref>. This keyword is described in section <a href="#iris"></a>.</dd>
- <dt><code>:</code></dt>
- <dd>The separator for JSON keys and values that use
- <tref title="compact_iri">compact IRIs</tref>.</dd>
- </dl>
-
- <p>For the avoidance of doubt, all keys, <tref title="keyword">keywords</tref>, and values in JSON-LD are
- case-sensitive.</p>
</section>
<section>
-<h3>The Context</h3>
+<h2>Syntax Tokens and Keywords</h2>
+
+<p>JSON-LD specifies a number of syntax tokens and <tdef title="keyword">keywords</tdef>
+that are a core part of the language:</p>
+
+<dl>
+<dt><code>@context</code></dt>
+<dd>Used to define the short-hand names that are used throughout a JSON-LD
+ document. These short-hand names are called <tref>term</tref>s and help
+ developers to express specific identifiers in a compact manner. The
+ <code>@context</code> keyword is described in detail in the section titled
+ <a href="#the-context"></a>.</dd>
+<dt><code>@graph</code></dt><dd>Used to explicitly label a <tref>linked data graph</tref>.
+ This keyword is described in <a href="#named-graphs"></a>.</dd>
+<dt><code>@id</code></dt>
+<dd>Used to uniquely identify <em>things</em> that are being described in the document.
+ This keyword is described in
+ <a href="#identifying-the-subject"></a>.</dd>
+<dt><code>@value</code></dt>
+<dd>Used to specify the data that is associated with a particular
+ <tref>property</tref> in the graph. This keyword is described in
+ <a href="#string-internationalization"></a> and
+ <a href="#typed-values"></a>.</dd>
+<dt><code>@language</code></dt>
+<dd>Used to specify the native language for a particular value or the default
+ language of a JSON-LD document. This keyword is described in the section titled
+ <a href="#string-internationalization"></a>.</dd>
+<dt><code>@type</code></dt>
+<dd>Used to set the data type of a <tref>subject</tref> or
+ <tref>typed value</tref>. This keyword is described in the section titled
+ <a href="#typed-values"></a>.</dd>
+<dt><code>@container</code></dt>
+<dd>Used to set the container of a particular value.
+ This keyword is described in the section titled <a href="#sets-and-lists"></a>.</dd>
+<dt><code>@list</code></dt>
+<dd>Used to express an ordered set of data.
+ This keyword is described in the section titled <a href="#sets-and-lists"></a>.</dd>
+<dt><code>@set</code></dt>
+<dd>Used to express an unordered set of data.
+ This keyword is described in the section titled <a href="#sets-and-lists"></a>.</dd>
+<dt><code>@vocab</code></dt>
+<dd>Used to set the base <tref>IRI</tref> for all property IRIs affected by the
+ <tref>active context</tref>. This keyword is described in section <a href="#iris"></a>.</dd>
+<dt><code>:</code></dt>
+<dd>The separator for JSON keys and values that use
+ <tref title="compact_iri">compact IRIs</tref>.</dd>
+</dl>
+
+<p>For the avoidance of doubt, all keys, <tref title="keyword">keywords</tref>, and values in JSON-LD are
+case-sensitive.</p>
+</section>
+
+<section>
+<h2>The Context</h2>
<p>In JSON-LD, a <tdef>context</tdef> is used to map <tref>term</tref>s, i.e., properties with associated
values in an JSON document, to <tref>IRI</tref>s. A <tdef>term</tdef> is a short word that expands to an
@@ -823,7 +841,7 @@
</section>
<section>
-<h3>From JSON to JSON-LD</h3>
+<h2>From JSON to JSON-LD</h2>
<p>If a set of <tref>term</tref>s such as, <strong>name</strong>,
<strong>homepage</strong>, and <strong>depiction</strong>,
@@ -859,7 +877,6 @@
contain an <code>@id</code> are known as an <tref title="unlabeled node">unlabeled nodes</tref>.</p>
</section>
-</section>
<section>
<h2>IRIs</h2>