Fixes to IANA registration and Acknowledgements section.
authorManu Sporny <msporny@digitalbazaar.com>
Sun, 27 Jan 2013 23:54:13 -0500
changeset 1164 b910d6f773ff
parent 1163 fed5262af53e
child 1165 494f472ce1d0
Fixes to IANA registration and Acknowledgements section.
spec/latest/json-ld-syntax/index.html
--- a/spec/latest/json-ld-syntax/index.html	Sun Jan 27 22:52:34 2013 -0500
+++ b/spec/latest/json-ld-syntax/index.html	Sun Jan 27 23:54:13 2013 -0500
@@ -2556,8 +2556,8 @@
     <li>A <tdef>JSON-LD document</tdef> serializes a collection of
       <tref title="JSON-LD graph">JSON-LD graphs</tref> and comprises exactly one
       <tdef>default graph</tdef> and zero or more <tdef title="named graph">named graphs</tdef>.</li>
-    <li>The default graph does not have a name and MAY be empty.</li>
-    <li>Each named graph is a pair consisting of a <tdef>graph name</tdef> 
+    <li>The <tref>default graph</tref> does not have a name and MAY be empty.</li>
+    <li>Each <tref>named graph</tref> is a pair consisting of a <tdef>graph name</tdef> 
       and a <tref>JSON-LD graph</tref>. The
       <tref>graph name</tref> SHOULD be an <tref>IRI</tref> or
       <tref>blank node identifier</tref>.</li>
@@ -2572,7 +2572,7 @@
       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>A node having an outgoing edge MUST be an <tref>IRI</tref> or a
+    <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>,
       i.e., nodes which are not connected by an <tref>edge</tref> to any other <tref>node</tref>.</li>
@@ -2955,7 +2955,7 @@
       (<tref title="language-tagged string">language-tagged strings</tref>) whereas
       JSON-LD also supports JSON's native data types, i.e., <tref title="number">number</tref>,
       <tref title="string">strings</tref>, and the boolean values <tref>true</tref>
-      and <tref>false</tref>. The JSON-LD API [[JSON-LD-API]] specification defines
+      and <tref>false</tref>. The JSON-LD Algorithms and API specification [[JSON-LD-API]] defines
       the conversion rules between JSON's native data types and RDF's counterparts to
       allow full round-tripping.</li>
 
@@ -2964,7 +2964,8 @@
   <p>Summarized these differences mean that JSON-LD is capable of serializing any RDF
     graph or dataset and most, but not all, JSON-LD documents can be transformed to RDF.
     A complete description of the algorithms to convert from RDF to JSON-LD and from
-    JSON-LD to RDF is included in the JSON-LD API [[JSON-LD-API]] specification.</p>
+    JSON-LD to RDF is included in the JSON-LD Algorithms and API specification 
+    [[JSON-LD-API]].</p>
 
   <p>Even though JSON-LD serializes RDF datasets, it can also be used as a RDF graph source.
     In that case, a consumer MUST only use the default graph and ignore all named graphs.
@@ -3023,7 +3024,9 @@
 -->
 </pre>
 
-<p class="note">JSON-LD has no equivalent for the Turtle <code>@base</code> declaration.</p>
+<p class="note">JSON-LD has no equivalent for the Turtle <code>@base</code> 
+declaration, but can use a prefix such as <code>base</code> to encode the
+information in the document.</p>
 
 </section>
 
@@ -3323,7 +3326,13 @@
     code execution mechanism such as JavaScript's <code>eval()</code>
     function. It is RECOMMENDED that a conforming parser does not attempt to
     directly evaluate the JSON-LD serialization and instead purely parse the
-    input into a language-native data structure. </dd>
+    input into a language-native data structure. <br/>
+    JSON-LD contexts that are loaded from the Web over non-secure connections,
+    such as HTTP, run the risk of modifying the JSON-LD 
+    <tref>active context</tref> in a way that could compromise security. It
+    is advised that any application that depends on a remote context for mission 
+    critical purposes vet and cache the remote context before allowing the
+    system to use it.</dd>
   <dt>Interoperability considerations:</dt>
   <dd>Not Applicable</dd>
   <dt>Published specification:</dt>
@@ -3331,7 +3340,7 @@
   <dt>Applications that use this media type:</dt>
   <dd>Any programming environment that requires the exchange of
     directed graphs. Implementations of JSON-LD have been created for
-    JavaScript, Python, Ruby, PHP and C++.
+    JavaScript, Python, Ruby, PHP, and C++.
   </dd>
   <dt>Additional information:</dt>
   <dd>
@@ -3351,7 +3360,7 @@
   <dt>Restrictions on usage:</dt>
   <dd>None</dd>
   <dt>Author(s):</dt>
-  <dd>Manu Sporny, Gregg Kellogg, Markus Lanthaler, Dave Longley</dd>
+  <dd>Manu Sporny, Dave Longley, Gregg Kellogg, Markus Lanthaler, Niklas Lindström</dd>
   <dt>Change controller:</dt>
   <dd>W3C</dd>
 </dl>
@@ -3367,13 +3376,22 @@
 <section class="appendix informative">
   <h1>Acknowledgements</h1>
 
-  <p>A large amount of thanks goes out to the JSON-LD Community Group participants
-    who worked through many of the technical issues on the mailing list and the weekly
-    telecons - of special mention are François Daoust, Lin Clark, and Zdenko 'Denny' Vrandečić.
-    The editors would like to thank Mark Birbeck, who provided a great deal of the
-    initial push behind the JSON-LD work via his work on RDFj. The work of Dave Lehn
-    and Mike Johnson are appreciated for reviewing, and performing several implementations
-    of the specification. Ian Davis is thanked for this work on RDF/JSON. Thanks also
+  <p>The authors would like to extend a deep appreciation and the most sincere
+    thanks to Mark Birbeck, who contributed foundational concepts 
+    to JSON-LD via his work on RDFj. JSON-LD uses a number of core concepts 
+    introduced in RDFj, such as the context as a mechanism to provide an
+    environment for interpreting JSON data. Mark had also been very involved in
+    the work on RDFa as well. RDFj built upon that work. JSON-LD exists
+    because of the work and ideas he started nearly a decade ago in 2004.</p>
+
+  <p>A large amount of thanks goes out to the JSON-LD Community Group 
+    participants who worked through many of the technical issues on the mailing 
+    list and the weekly telecons - of special mention are François Daoust, 
+    Stéphane Corlosquet, Lin Clark, and Zdenko 'Denny' Vrandečić.</p>
+
+  <p>The work of David I. Lehn and Mike Johnson are appreciated for 
+    reviewing, and performing several implementations
+    of the specification. Thanks to Ian Davis for this work on RDF/JSON. Thanks also
     to Nathan Rixham, Bradley P. Allen, Kingsley Idehen, Glenn McDonald, Alexandre Passant,
     Danny Ayers, Ted Thibodeau Jr., Olivier Grisel, Josh Mandel, Eric Prud'hommeaux,
     David Wood, Guus Schreiber, Pat Hayes, Sandro Hawke, and Richard Cyganiak