Use file extension in all examples when referencing external contexts
authorMarkus Lanthaler <mark_lanthaler@gmx.net>
Fri, 15 Jun 2012 16:57:39 +0200
changeset 722 a331528edad6
parent 721 6f3b3deb9e88
child 723 55df5f1d0bfe
Use file extension in all examples when referencing external contexts

I hope this helps to avoid confusion what happens when referencing an external context and is in line with the IANA considerations section.
spec/latest/json-ld-api/index.html
spec/latest/json-ld-syntax/index.html
--- a/spec/latest/json-ld-api/index.html	Fri Jun 15 16:49:52 2012 +0200
+++ b/spec/latest/json-ld-api/index.html	Fri Jun 15 16:57:39 2012 +0200
@@ -271,22 +271,22 @@
 <section id='sotd'>
 <p>This document has been under development for over 18 months in the
 JSON for Linking Data Community Group. The document has recently been
-approved for transfer into the RDF Working Group for 
+approved for transfer into the RDF Working Group for
 review with the intent to publish the
 document along the W3C
-Recommendation track. This specification has undergone significant 
+Recommendation track. This specification has undergone significant
 development, review, and changes during the course of the last 18
 months and is being published as a Final Community Group Specification so that
 it may gain wider review and feedback.
 </p>
 <p>
-There are currently 
-<a href="http://json-ld.org/#impl">five interoperable implementations</a> 
+There are currently
+<a href="http://json-ld.org/#impl">five interoperable implementations</a>
 of this specification. There is
-a <a href="https://github.com/json-ld/json-ld.org/tree/master/test-suite">fairly complete test suite</a> 
-and a  
-<a href="http://json-ld.org/playground/">live JSON-LD editor</a> 
-that is capable of demonstrating the features described in 
+a <a href="https://github.com/json-ld/json-ld.org/tree/master/test-suite">fairly complete test suite</a>
+and a
+<a href="http://json-ld.org/playground/">live JSON-LD editor</a>
+that is capable of demonstrating the features described in
 this document. While development on implementations, the test suite
 and the live editor will continue, they are believed to be mature enough
 to be integrated into a non-production system at this point in time with
@@ -295,12 +295,12 @@
 </p>
 <p class="issue">
 It is important for readers to understand that the scope of this document is
-currently under debate and new features may be added to the specification. 
+currently under debate and new features may be added to the specification.
 Existing features may be modified heavily or removed entirely from the
 specification upon further review and feedback from the broader community.
 This is a work in progress and publication as a First Public Working Draft
 does not require that all Working Group members agree on the content of the
-document. 
+document.
 </p>
 </section>
 
@@ -308,13 +308,13 @@
 <h2>Preface</h2>
 
 <p>
-This document is a detailed specification for an Application Programming 
-Interface for the JSON-LD Syntax. The document is primarily intended for 
+This document is a detailed specification for an Application Programming
+Interface for the JSON-LD Syntax. The document is primarily intended for
 the following audiences:
 </p>
 
 <ul>
-  <li>Web authors and developers that want a very detailed view of how 
+  <li>Web authors and developers that want a very detailed view of how
   a JSON-LD processor and the API operates.</li>
   <li>Software developers that want to implement processors and APIs for
   JSON-LD.</li>
@@ -344,18 +344,18 @@
     <li>Ad-hoc technical discussion primarily occurs on the public community mailing list:
       <a href="http://lists.w3.org/Archives/Public/public-linked-json/">[email protected]</a></li>
 
-    <li><a href="http://json-ld.org/minutes/">Public JSON-LD Community Group teleconferences</a> 
+    <li><a href="http://json-ld.org/minutes/">Public JSON-LD Community Group teleconferences</a>
     are held on Tuesdays at 1500UTC every week.</li>
 
-    <li>RDF Working Group teleconferences are held on Wednesdays at 1500UTC 
+    <li>RDF Working Group teleconferences are held on Wednesdays at 1500UTC
     every week. Participation is limited to RDF Working Group members.</li>
 
     <li>Specification bugs and issues should be reported in the
       <a href="https://github.com/json-ld/json-ld.org/issues">issue tracker</a>
-      if you do not want to send an e-mail to the public-rdf-comments mailing 
+      if you do not want to send an e-mail to the public-rdf-comments mailing
       list.</li>
 
-    <li><a href="https://github.com/json-ld/json-ld.org/tree/master/spec">Source code</a> 
+    <li><a href="https://github.com/json-ld/json-ld.org/tree/master/spec">Source code</a>
       for the specification can be found on Github.</li>
 
     <li>The <a href="http://webchat.freenode.net/?channels=json-ld">#json-ld</a>
@@ -370,44 +370,44 @@
 <h1>Introduction</h1>
 
 <p>
-The JSON-LD Syntax specification [[!JSON-LD]] outlines a language that may be 
-used to express Linked Data in JSON. Often, it is useful to be able to 
+The JSON-LD Syntax specification [[!JSON-LD]] outlines a language that may be
+used to express Linked Data in JSON. Often, it is useful to be able to
 transform JSON-LD documents so that they may be easily processed in
 a programming environment like JavaScript, Python or Ruby.
 </p>
 
 <p>
 There are three major types of transformation that are discussed in this
-document; compaction, expansion, and RDF conversion. 
+document; compaction, expansion, and RDF conversion.
 </p>
 
 <section>
   <h2>Expansion</h2>
   <p>
 Software algorithms are easiest to write when the data that they are processing
-have a regular form. Since information can be represented by JSON-LD in a 
+have a regular form. Since information can be represented by JSON-LD in a
 variety of different ways, transforming all of these methods into a uniform
 structure allows the developer to simplify their processing code. For example,
 note that the following input uses only <tref>term</tref>s and is fairly
 compact:
   </p>
- 
+
   <pre class="example" data-transform="updateExample">
 var input1 = {
-  "@context": "http://json-ld.org/contexts/person"
+  "@context": "http://json-ld.org/contexts/person.jsonld"
   "name": "Manu Sporny",
   "homepage": "http://manu.sporny.org/"
 }
   </pre>
 
   <p>
-The next input example uses one <tref>IRI</tref> to express a property, but 
+The next input example uses one <tref>IRI</tref> to express a property, but
 leaves the rest of the information untouched.
   </p>
 
   <pre class="example" data-transform="updateExample">
 var input2 = {
-  "@context": "http://json-ld.org/contexts/person"
+  "@context": "http://json-ld.org/contexts/person.jsonld"
   "****http://xmlns.com/foaf/0.1/name****": "Manu Sporny",
   "homepage": "http://manu.sporny.org/"
 }
@@ -418,10 +418,10 @@
 permutation of possible inputs can be difficult, especially when the incoming
 context could change as well. To ensure that the data can be given a more
 uniform structure, JSON-LD introduces the notion of expansion.
-<tdef>Expansion</tdef> performs two important operations. The first is to 
-expand all values that are <tref>IRI</tref>s to their fully expanded form. 
-The second is to express all values in <tdef>expanded form</tdef>. To 
-transform both inputs above to the same representation, the developer could 
+<tdef>Expansion</tdef> performs two important operations. The first is to
+expand all values that are <tref>IRI</tref>s to their fully expanded form.
+The second is to express all values in <tdef>expanded form</tdef>. To
+transform both inputs above to the same representation, the developer could
 do the following:
   </p>
 
@@ -431,7 +431,7 @@
 }
 
 // the second parameter is 'null' because the developer does not wish to
-// inject another context value 
+// inject another context value
 jsonld.expand(input1, null, expansionCallback);
 jsonld.expand(input2, null, expansionCallback);
   </pre>
@@ -450,10 +450,10 @@
   }]
 }]
   </pre>
- 
+
   <p>
 Note that in the example above; all <tref>context</tref> definitions have
-been removed, all <tref>term</tref> and prefixes have been expanded to full 
+been removed, all <tref>term</tref> and prefixes have been expanded to full
 IRIs, and all <tref>literal</tref>s are expressed in <tref>expanded form</tref>.
 While the output is more difficult for a human to read, it is easier for a
 software program to process because of its very regular structure.
@@ -467,14 +467,14 @@
 the opposite operation - expressing a given input as succinctly as possible.
 While expansion is meant to produce something that is easy to process by
 software programs, compaction is meant to produce something that is easy to
-ready by software developers. Compaction uses a developer-supplied 
-<tref>context</tref> to compresses all <tref>IRI</tref>s to <tref>term</tref>s 
-or <tref>prefix</tref>es, and compacts all <tref>literal</tref>s expressed 
-in <tref>expanded form</tref> as much as possible. 
+ready by software developers. Compaction uses a developer-supplied
+<tref>context</tref> to compresses all <tref>IRI</tref>s to <tref>term</tref>s
+or <tref>prefix</tref>es, and compacts all <tref>literal</tref>s expressed
+in <tref>expanded form</tref> as much as possible.
   </p>
 
   <p>
-The following example expresses input that has already been fully expanded: 
+The following example expresses input that has already been fully expanded:
   </p>
 
   <pre class="example" data-transform="updateExample">
@@ -492,34 +492,34 @@
 A developer that wants to transform the data above into a more human-readable
 form, could do the following using the JSON-LD API:
   </p>
-  
+
   <pre class="example" data-transform="updateExample">
 function compactionCallback(output) {
    console.log(output);
 }
 
-jsonld.compact(expandedInput, "http://json-ld.org/contexts/person", compactionCallback);
+jsonld.compact(expandedInput, "http://json-ld.org/contexts/person.jsonld", compactionCallback);
   </pre>
-  
+
   <p>
 The following would be the result of the call above:
   </p>
 
   <pre class="example" data-transform="updateExample">
 {
-  "@context": "http://json-ld.org/contexts/person"
+  "@context": "http://json-ld.org/contexts/person.jsonld"
   "name": "Manu Sporny",
   "homepage": "http://manu.sporny.org/"
 }
   </pre>
-  
+
   <p>
-Note that all of the <tref>term</tref>s have been compressed and 
+Note that all of the <tref>term</tref>s have been compressed and
 the <tref>context</tref> has been injected into the output. While compacted
-output is most useful to humans, it can also be carefully used to generate 
+output is most useful to humans, it can also be carefully used to generate
 structures that are easy to use for developers to program against as well.
   </p>
-  
+
 </section>
 
 <section>
@@ -528,23 +528,23 @@
 JSON-LD can be used to losslessly express the RDF data model as described in
 the RDF Concepts document  [[RDF-CONCEPTS]]. This ensures that
 data can be round-tripped from any RDF syntax, like N-Triples or TURTLE,
-without any loss in the fidelity of the data. Assume the following RDF input 
-in N-Triples format:  
+without any loss in the fidelity of the data. Assume the following RDF input
+in N-Triples format:
   </p>
-  
+
   <pre class="example" data-transform="updateExample">
-<!-- 
-var data = " 
+<!--
+var data = "
 <http://manu.sporny.org/about/#manu> <http://xmlns.com/foaf/0.1/name> \"Manu Sporny\" .\n
 <http://manu.sporny.org/about/#manu> <http://xmlns.com/foaf/0.1/homepage> <http://manu.sporny.org/> .";
 -->
   </pre>
-  
+
   <p>
-A developer can use the JSON-LD API to transform the markup above into a 
+A developer can use the JSON-LD API to transform the markup above into a
 JSON-LD document:
   </p>
-  
+
   <pre class="example" data-transform="updateExample">
 function conversionCallback(result)
 {
@@ -553,7 +553,7 @@
 
 jsonld.fromRDF(data, conversionCallback, {"format": "ntriples"});
   </pre>
-  
+
   <p>
 The following expanded output would be the result of the call above:
   </p>
@@ -568,27 +568,27 @@
     "@id": "http://manu.sporny.org/"
   }]
 }]
-  </pre>  
-  
+  </pre>
+
   <p>
 Note that the output above, could easily be compacted to produce the following
 using the technique outlined in the previous section:
   </p>
-  
+
   <pre class="example" data-transform="updateExample">
 {
-  "@context": "http://json-ld.org/contexts/person",
+  "@context": "http://json-ld.org/contexts/person.jsonld",
   "@id": "http://manu.sporny.org/about/#manu",
   "name": "Manu Sporny",
   "homepage": "http://manu.sporny.org/"
 }
   </pre>
-  
+
   <p>
 Transforming the object above back to RDF is as simple as calling the
 <code>toRDF()</code> method:
   </p>
-  
+
   <pre class="example" data-transform="updateExample">
 var jsonldDocument = ...; // assign the JSON-LD document here
 
@@ -609,14 +609,14 @@
 were not ready for publication at the time this document was published.
 Framing allows a developer to force a different layout for the data and
 effectively perform query-by-example on JSON-LD documents - this is most
-useful when a JSON-LD-based REST API does not know the exact form of the data 
-it is getting in, but still wants to operate upon it if some bare essentials 
+useful when a JSON-LD-based REST API does not know the exact form of the data
+it is getting in, but still wants to operate upon it if some bare essentials
 are found in the data. JSON-LD normalization allows JSON-LD documents to be
 deterministically serialized such that they can be digitally signed or be
 used to find the differences between two <tref>linked data graph</tref>s.
-It is expected that framing will be a part of the final API. It is expected 
+It is expected that framing will be a part of the final API. It is expected
 that normalization will be an optional feature that JSON-LD processors may
-implement.   
+implement.
   </p>
 </section>
 
@@ -626,9 +626,9 @@
   <h2>The Application Programming Interface</h2>
 
   <p>This API provides a clean mechanism that enables developers to convert
-  JSON-LD data into a a variety of output formats that are easier to work 
-  with in various programming languages. If a JSON-LD API is provided in 
-  a programming environment, the entirety of the following API MUST be 
+  JSON-LD data into a a variety of output formats that are easier to work
+  with in various programming languages. If a JSON-LD API is provided in
+  a programming environment, the entirety of the following API MUST be
   implemented.
   </p>
 
@@ -641,14 +641,14 @@
 in the RDF Concepts document to the extent to which it makes sense to do so.
 In general, if there is an analogue to terminology used in this document in
 the RDF Concepts document, the preference is to use the terminology in the
-RDF Concepts document. 
+RDF Concepts document.
   </p>
 
   <p>
-The following is an explanation of the general terminology used in this 
+The following is an explanation of the general terminology used in this
 document:
   </p>
-   
+
   <dl>
       <dt><tdef>JSON object</tdef></dt><dd>
       An object structure is represented as a pair of curly brackets surrounding zero or
@@ -658,7 +658,7 @@
     </dd>
     <dt><tdef>array</tdef></dt>
     <dd>
-      An array is represented as square brackets surrounding zero or more 
+      An array is represented as square brackets surrounding zero or more
       values that are separated by commas.
     </dd>
     <dt><tdef>string</tdef></dt><dd>
@@ -668,87 +668,87 @@
     </dd>
     <dt><tdef>number</tdef></dt>
     <dd>
-      A number is is similar to that used in most programming languages, except 
-      that the octal and hexadecimal formats are not used and that leading 
+      A number is is similar to that used in most programming languages, except
+      that the octal and hexadecimal formats are not used and that leading
       zeros are not allowed.</dd>
     <dt><tdef>true</tdef> and <tdef>false</tdef></dt><dd>
       Values that are used to express one of two possible boolean states.
     </dd>
     <dt><tdef>null</tdef></dt><dd>
-      Unless otherwise specified, a JSON-LD processor MUST act as if a 
-      key-value pair in the body of a JSON-LD document was never declared when 
-      the value equals <em>null</em>. If <code>@value</code>, 
-      <code>@list</code>, or <code>@set</code> is set to <em>null</em> in 
-      expanded form, then the entire JSON object is ignored. If 
-      <code>@context</code> is set to <em>null</em>, the 
+      Unless otherwise specified, a JSON-LD processor MUST act as if a
+      key-value pair in the body of a JSON-LD document was never declared when
+      the value equals <em>null</em>. If <code>@value</code>,
+      <code>@list</code>, or <code>@set</code> is set to <em>null</em> in
+      expanded form, then the entire JSON object is ignored. If
+      <code>@context</code> is set to <em>null</em>, the
       <tref>active context</tref> is reset and when used
-      within a <tref>context</tref>, it removes any definition associated 
+      within a <tref>context</tref>, it removes any definition associated
       with the key, unless otherwise specified.
     </dd>
     <dt><tdef>subject definition</tdef></dt><dd>
-      A <tref>JSON object</tref> used to represent a <tref>subject</tref> and 
-      one or more properties of that subject. A <tref>JSON object</tref> is a 
-      subject definition if it does not contain they keys <code>@value</code>, 
-      <code>@list</code> or <code>@set</code> and it has one or more keys 
+      A <tref>JSON object</tref> used to represent a <tref>subject</tref> and
+      one or more properties of that subject. A <tref>JSON object</tref> is a
+      subject definition if it does not contain they keys <code>@value</code>,
+      <code>@list</code> or <code>@set</code> and it has one or more keys
       other than <code>@id</code>.</dd>
     <dt><tdef>subject reference</tdef></dt><dd>
-      A <tref>JSON object</tref> used to reference a subject having only the 
+      A <tref>JSON object</tref> used to reference a subject having only the
       <code>@id</code> key.</dd>
     <dt><tdef>Linked Data</tdef></dt>
-    <dd>A set of documents, each containing a representation of a 
+    <dd>A set of documents, each containing a representation of a
     <tref>linked data graph</tref>.</dd>
     <dt><tdef>linked data graph</tdef> or <tdef>dataset</tdef></dt>
-    <dd>An unordered labeled directed graph, where <tref>node</tref>s are 
-    <tref>subject</tref>s or <tref>object</tref>s, and edges are 
+    <dd>An unordered labeled directed graph, where <tref>node</tref>s are
+    <tref>subject</tref>s or <tref>object</tref>s, and edges are
     properties.</dd>
     <dt><tdef>node</tdef></dt>
-    <dd>A piece of information that is represented in a 
+    <dd>A piece of information that is represented in a
     <tref>linked data graph</tref>.</dd>
     <dt><tdef>named graph</tdef></dt>
-    <dd>A <tref>linked data graph</tref> that has one or more 
+    <dd>A <tref>linked data graph</tref> that has one or more
     <tref>IRI</tref> that are used to refer to it.</dd>
     <dt><tdef>graph name</tdef></dt>
-    <dd>An <tref>IRI</tref> that is a reference to a 
-    <tref>named graph</tref>.</dd> 
+    <dd>An <tref>IRI</tref> that is a reference to a
+    <tref>named graph</tref>.</dd>
     <dt><tdef>default graph</tdef></dt>
-    <dd>When executing an algorithm, the graph where data should be placed 
+    <dd>When executing an algorithm, the graph where data should be placed
     if a <tref>named graph</tref> is not specified.</dd>
     <dt><tdef>subject</tdef></dt>
-    <dd>Any node in a <tref>linked data graph</tref> with at least one 
+    <dd>Any node in a <tref>linked data graph</tref> with at least one
     outgoing edge.</dd>
     <dt><tdef><abbr title="Internationalized Resource Identifier">IRI</abbr></tdef></dt>
-    <dd>An Internationalized Resource Identifier as described 
+    <dd>An Internationalized Resource Identifier as described
     in [[!RFC3987]]).</dd>
     <dt><tdef>object</tdef></dt>
-    <dd>A node in a <tref>linked data graph</tref> with at least one 
+    <dd>A node in a <tref>linked data graph</tref> with at least one
     incoming edge.</dd>
     <dt><tdef>property</tdef></dt>
     <dd>An edge of the <tref>linked data graph</tref>.</dd>
     <dt><tdef>literal</tdef></dt>
-    <dd>An <tref>object</tref> with a label that is not an 
+    <dd>An <tref>object</tref> with a label that is not an
     <tref>IRI</tref>.</dd>
     <dt><tdef>quad</tdef></dt>
-    <dd>A piece of information that contains four items; a 
+    <dd>A piece of information that contains four items; a
     <tref>subject</tref>, a <tref>property</tref>, a <tref>object</tref>,
     and a <tref>graph name</tref>.</dd>
     <dt><tdef>context</tdef></dt>
-    <dd>A <tref>JSON object</tref> that contains rules for interpreting a 
+    <dd>A <tref>JSON object</tref> that contains rules for interpreting a
     JSON-LD document.</dd>
     <dt><tdef>keyword</tdef></dt>
-    <dd>A JSON key that is specific to JSON-LD, specified in the JSON-LD 
-    Syntax specification [[!JSON-LD]] in the section titled 
+    <dd>A JSON key that is specific to JSON-LD, specified in the JSON-LD
+    Syntax specification [[!JSON-LD]] in the section titled
     <a href="http://sites.local/json-ld.org/spec/latest/json-ld-syntax/#syntax-tokens-and-keywords">Syntax Tokens and Keywords</a>.</dd>
    </dl>
  </section>
 
   <section>
     <h3>JsonLdProcessor</h3>
-    
+
     <p>
-The JSON-LD Processor interface is the high-level programming structure that 
-developers use to access the JSON-LD transformation methods. 
+The JSON-LD Processor interface is the high-level programming structure that
+developers use to access the JSON-LD transformation methods.
     </p>
-    
+
     <dl title="[NoInterfaceObject] interface JsonLdProcessor" class="idl">
 
       <dt>void expand()</dt>
@@ -1020,9 +1020,9 @@
     does not contain a de-reference-able identifier because it is either
     ephemeral in nature or does not contain information that needs to be linked
     to from outside of the <tref>linked data graph</tref>.
-    A blank node is assigned an identifier starting 
-    with the prefix <code>_:</code> and an implementation dependent, 
-    auto-generated suffix that is unique to all information associated with the 
+    A blank node is assigned an identifier starting
+    with the prefix <code>_:</code> and an implementation dependent,
+    auto-generated suffix that is unique to all information associated with the
     particular blank node.
     </p>
 
@@ -1800,22 +1800,22 @@
     of existing libraries for parsing JSON.
   </p>
   <p>
-    As with other grammars used for describing <tref>Linked Data</tref>, a key 
-    concept is that of a <tref>node</tref> in a <tref>linked data graph</tref>. 
+    As with other grammars used for describing <tref>Linked Data</tref>, a key
+    concept is that of a <tref>node</tref> in a <tref>linked data graph</tref>.
     Nodes may be of three basic types.
-    The first is the <ldtref>IRI</ldtref>, which is used to refer to 
-    <tref>node</tref>s in other <tref>linked data graph</tref>s. 
-    The second is the 
+    The first is the <ldtref>IRI</ldtref>, which is used to refer to
+    <tref>node</tref>s in other <tref>linked data graph</tref>s.
+    The second is the
     <tref>blank node</tref>, which are nodes for which an external name does not
-    exist, or is not known. The third is a <tref>Literal</tref>, which express 
-    values such as strings, dates and other information having a lexical 
+    exist, or is not known. The third is a <tref>Literal</tref>, which express
+    values such as strings, dates and other information having a lexical
     form, possibly including an explicit language or datatype.
   </p>
   <p>Data described with JSON-LD may be considered to be a graph made
-    up of <tref>subject</tref> and <tref>object</tref> 
-    <tref title="node">nodes</tref> related via a <tref>property</tref> 
-    <tref>node</tref>. Specific implementations may also choose to operate 
-    on the document as a normal JSON description of objects having 
+    up of <tref>subject</tref> and <tref>object</tref>
+    <tref title="node">nodes</tref> related via a <tref>property</tref>
+    <tref>node</tref>. Specific implementations may also choose to operate
+    on the document as a normal JSON description of objects having
     attributes. Both approaches are valid ways to interact with JSON-LD
     documents.</p>
 </section>
@@ -1881,7 +1881,7 @@
     similar to Turtle's <code>blankNodePropertyList</code>.</p>
 
   <p>After expansion, JSON-LD <tref title="number">numbers</tref>,
-    <tref title="true">booleans</tref>, typed- and language-tagged-<tref 
+    <tref title="true">booleans</tref>, typed- and language-tagged-<tref
     title="literal">literals</tref>, and <tref title="iri">IRIs</tref>
     become explicit, and can be directly transformed into their RDF representations.</p>
 
@@ -2285,7 +2285,7 @@
 performed several implementations of the specification, and Ian Davis, who
 created 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, 
+Thibodeau Jr., Olivier Grisel, Josh Mandel, Eric Prud'hommeaux,
 David Wood, Guus Schreiber, Pat Hayes, Sandro Hawke, and Richard
 Cyganiak for their input on the specification.
 </p>
--- a/spec/latest/json-ld-syntax/index.html	Fri Jun 15 16:49:52 2012 +0200
+++ b/spec/latest/json-ld-syntax/index.html	Fri Jun 15 16:57:39 2012 +0200
@@ -649,14 +649,14 @@
 -->
 </pre>
 
-<p>Assuming that this context document can be retrieved at <code>http://json-ld.org/contexts/person</code>,
+<p>Assuming that this context document can be retrieved at <code>http://json-ld.org/contexts/person.jsonld</code>,
   it can be referenced from a JSON-LD document by adding a single line. The JSON markup shown in the previous
   section could be changed as follows:</p>
 
 <pre class="example" data-transform="updateExample">
 <!--
 {
-  ****"@context": "http://json-ld.org/contexts/person",****
+  ****"@context": "http://json-ld.org/contexts/person.jsonld",****
   "name": "Manu Sporny",
   "homepage": "http://manu.sporny.org/",
   "depiction": "http://twitter.com/account/profile_image/manusporny"
@@ -728,7 +728,7 @@
 <!--
 {
   ****"@context": [
-    "http://json-ld.org/contexts/person",
+    "http://json-ld.org/contexts/person.jsonld",
     {
       "pic": "http://xmlns.com/foaf/0.1/depiction"
     }
@@ -1474,7 +1474,7 @@
 <pre class="example" data-transform="updateExample">
 <!--
 {
-  ****"@context": "http://json-ld.org/contexts/person"****,
+  ****"@context": "http://json-ld.org/contexts/person.jsonld"****,
   "name": "Manu Sporny",
   "homepage": "http://manu.sporny.org/",
   "depiction": "http://twitter.com/account/profile_image/manusporny"
@@ -1490,11 +1490,11 @@
 {
   ****"@context":
   [
-    "http://json-ld.org/contexts/person",
+    "http://json-ld.org/contexts/person.jsonld",
     {
       "foaf": "http://xmlns.com/foaf/0.1/"
     },
-    "http://json-ld.org/contexts/event",
+    "http://json-ld.org/contexts/event.jsonld",
   ]****
   "name": "Manu Sporny",
   "homepage": "http://manu.sporny.org/",
@@ -1595,7 +1595,7 @@
 HTTP/1.0 200 OK
 ...
 Content-Type: ****application/json****
-****Link: <http://json-ld.org/contexts/person>; rel="describedby"; type="application/ld+json"****
+****Link: <http://json-ld.org/contexts/person.jsonld>; rel="describedby"; type="application/ld+json"****
 
 {
   "name": "Markus Lanthaler",