Fix typo
authorMarkus Lanthaler <mark_lanthaler@gmx.net>
Thu, 04 Jul 2013 09:57:55 +0200
changeset 1744 0b7daa8699a2
parent 1743 e735df024e5c
child 1745 783a34c37f86
Fix typo
spec/latest/json-ld/index.html
--- a/spec/latest/json-ld/index.html	Wed Jul 03 21:15:01 2013 +0200
+++ b/spec/latest/json-ld/index.html	Thu Jul 04 09:57:55 2013 +0200
@@ -97,10 +97,10 @@
 
 <body>
 <section id="abstract">
-  <p>JSON is a useful data serialization and messaging format. 
+  <p>JSON is a useful data serialization and messaging format.
     This specification defines JSON-LD, a JSON-based format to serialize
-    Linked Data. The syntax is designed to easily integrate into deployed 
-    systems that already use JSON, and provides a smooth upgrade path from 
+    Linked Data. The syntax is designed to easily integrate into deployed
+    systems that already use JSON, and provides a smooth upgrade path from
     JSON to JSON-LD.
     It is primarily intended to be a way to use Linked Data in Web-based
     programming environments, to build interoperable Web services, and to
@@ -209,8 +209,8 @@
    RDF syntax, like Turtle [[TURTLE]]. Complete details of how JSON-LD relates
    to RDF are in <a href="#relationship-to-rdf"></a>.
   </p>
-  
-  <p>   
+
+  <p>
     The syntax is designed to not disturb already
    deployed systems running on JSON, but provide a smooth upgrade path from
    JSON to JSON-LD. Since the shape of such data varies wildly, JSON-LD
@@ -282,7 +282,7 @@
     <dd>JSON-LD must be usable by developers as
       idiomatic JSON, with no need to understand RDF [[RDF11-CONCEPTS]].
       JSON-LD must also be usable as RDF, so people intending to use JSON-LD
-      with RDF tools will find it can be used like any other RDF syntax. 
+      with RDF tools will find it can be used like any other RDF syntax.
       Complete details of how JSON-LD relates to RDF are in
       <a href="#relationship-to-rdf"></a>.</dd>
   </dl>
@@ -2708,11 +2708,11 @@
   <h1>Data Model</h1>
 
   <p>JSON-LD is a serialization format for Linked Data based on JSON.
-    It is therefore important to distinguish between the syntax, which is 
-    defined by JSON in [[RFC4627]], and the 
-    <tdef title="data model">data model</tdef> which is an extention of the
+    It is therefore important to distinguish between the syntax, which is
+    defined by JSON in [[RFC4627]], and the
+    <tdef title="data model">data model</tdef> which is an extension of the
     RDF data model [[RDF11-CONCEPTS]]. To ease understanding for developers
-    unfamiliar with the RDF model, the following normative summary is 
+    unfamiliar with the RDF model, the following normative summary is
     provided:</p>
 
   <ul>
@@ -2776,24 +2776,24 @@
       <tref title="IRI">IRIs</tref>, minting new "Skolem IRIs" as per
       <cite><a href="http://www.w3.org/TR/rdf11-concepts/#section-skolemization">Replacing Blank Nodes with IRIs</a></cite>
       of [[RDF11-CONCEPTS]]. Based on feedback from implementors, the
-      Working Group may decide to disallow blank node properties in JSON-LD. 
+      Working Group may decide to disallow blank node properties in JSON-LD.
       If this change would affect you, be sure to send in a comment.</p>
   </div>
 
-  <p>The intent is for the definitions above to be as compatible as possible 
+  <p>The intent is for the definitions above to be as compatible as possible
     with the abstract syntax of RDF datasets and RDF graphs. The only point at
-    which the definitions deviate from the ones in RDF Concepts is when 
-    the RDF model is extended. Complete details of how JSON-LD 
+    which the definitions deviate from the ones in RDF Concepts is when
+    the RDF model is extended. Complete details of how JSON-LD
     extends the RDF model can be found in
     <a class="sectionRef" href="#relationship-to-rdf"></a>.</p>
 
   <p>
    <tref title="JSON-LD document">JSON-LD documents</tref>
    MAY contain data that cannot be represented by the
-   <tref title="data model">data model</tref> defined above. Unless otherwise 
+   <tref title="data model">data model</tref> defined above. Unless otherwise
    specified, such data is ignored when a <tref>JSON-LD document</tref>
-   is being processed. One result of this rule is that properties which 
-   are not mapped to an <tref>IRI</tref> or <tref>blank node</tref> will 
+   is being processed. One result of this rule is that properties which
+   are not mapped to an <tref>IRI</tref> or <tref>blank node</tref> will
    be ignored.
   </p>
 
@@ -3172,7 +3172,7 @@
       <tref title="IRI">IRIs</tref> or <tref title="blank node">blank nodes</tref>
       whereas in RDF properties (predicates) have to be
       <tref title="IRI">IRIs</tref>.</li>
-    <li>In JSON-LD sets and lists are part of the data model whereas in RDF 
+    <li>In JSON-LD sets and lists are part of the data model whereas in RDF
       they are part of a vocabulary, namely [[RDF-SCHEMA]].</li>
     <li>RDF values are either typed <em>literals</em>
       (<tref title="typed value">typed values</tref>) or <em>language-tagged strings</em>
@@ -3186,12 +3186,12 @@
   </ul>
 
   <p class="note">All JSON numbers and booleans can be mapped to XML Schema
-  datatypes, which are built-in datatypes in the RDF model. 
-  Non-decimal JSON numbers map to <code>xsd:integer</code> and  
-  decimal numbers map to <code>xsd:double</code>. JSON numbers are 
-  described as extensions to the RDF data model because they combine the value 
-  space of <code>xsd:integer</code> and <code>xsd:double</code> into a single 
-  value space. JSON booleans may be mapped to XML Schema using the 
+  datatypes, which are built-in datatypes in the RDF model.
+  Non-decimal JSON numbers map to <code>xsd:integer</code> and
+  decimal numbers map to <code>xsd:double</code>. JSON numbers are
+  described as extensions to the RDF data model because they combine the value
+  space of <code>xsd:integer</code> and <code>xsd:double</code> into a single
+  value space. JSON booleans may be mapped to XML Schema using the
   <code>xsd:boolean</code> datatype. JSON booleans are described as extensions
   to the RDF data model because, while they have the same value space,
   they omit the values of <code>0</code> and <code>1</code> from the
@@ -3800,15 +3800,15 @@
     their input on the specification: Adrian Walker, Alexandre Passant,
     Andy Seaborne, Ben Adida, Blaine Cook, Bradley Allen, Brian Peterson,
     Bryan Thompson, Conal Tuohy, Dan Brickley, Danny Ayers, Daniel Leja,
-    Dave Reynolds, David Booth, David I. Lehn, David Wood, Dean Landolt, 
+    Dave Reynolds, David Booth, David I. Lehn, David Wood, Dean Landolt,
     Ed Summers, elf Pavlik,
     Eric Prud'hommeaux, Erik Wilde, Fabian Christ, Jon A. Frost, Gavin Carothers,
     Glenn McDonald, Guus Schreiber, Henri Bergius, Jose María Alvarez Rodríguez,
     Ivan Herman, Jack Moffitt, Josh Mandel, KANZAKI Masahide, Kingsley Idehen,
     Kuno Woudt, Larry Garfield, Mark Baker, Mark MacGillivray, Marko Rodriguez,
-    Marios Meimaris, 
+    Marios Meimaris,
     Melvin Carvalho, Nathan Rixham, Olivier Grisel, Paolo Ciccarese, Pat Hayes,
-    Patrick Logan, Paul Kuykendall, Pelle Braendgaard, 
+    Patrick Logan, Paul Kuykendall, Pelle Braendgaard,
     Peter Patel-Schneider, Peter Williams, Pierre-Antoine Champin,
     Richard Cyganiak, Roy T. Fielding, Sandro Hawke, Srecko Joksimovic,
     Stephane Fellah, Steve Harris, Ted Thibodeau Jr., Thomas Steiner, Tim Bray,