Mercurial > hg > ldpwg / changeset
summary | shortlog | changelog | graph | tags | bookmarks | branches | files | changeset
fiddling with pre's and div's
authorRoger Menday <roger.menday@uk.fujitsu.com>
Wed, 18 Jun 2014 11:47:20 +0100
changeset 672 f8742743f4d5
parent 671 5303831dcced
child 673 7fe3a1c86f0b
fiddling with pre's and div's
TR/WD-ldp-primer-20140620/Overview.html
ldp-primer/ldp-primer.html 
--- a/TR/WD-ldp-primer-20140620/Overview.html	Wed Jun 18 12:28:32 2014 +0200
+++ b/TR/WD-ldp-primer-20140620/Overview.html	Wed Jun 18 11:47:20 2014 +0100
@@ -626,7 +626,7 @@
 
       <p>First Alice looks up her storage by retrieving the LDP Basic Container assigned to her to hold her documents. Alice's LDP client does this by doing a GET request on the URI, http://example.org/alice/. </p>
 
-      <div class="example"><div class="example-title"><span>Example 1</span>: Request - basic container retrieval</div><pre class="example"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>GET /alice/ HTTP/1.1
+      <div class="example"><div class="example-title"><span>Example 1</span>: Request - basic container retrieval</div><div class="exxample"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>GET /alice/ HTTP/1.1
 Host: example.org
 Accept: text/turtle
 
@@ -678,10 +678,10 @@
 		 In the previous example, we saw that Alice can discover what operations are allowed on a resource by doing a GET request on the resource. As an alternative, she can use the OPTIONS operation to learn of the permitted operations on any given resource.
       </p>
 
-      <div class="example"><div class="example-title"><span>Example 3</span>: Request - retreiving OPTIONS of a basic container</div><pre class="example">OPTIONS /alice/ HTTP/1.1
+      <div class="example"><div class="example-title"><span>Example 3</span>: Request - retreiving OPTIONS of a basic container</div><div class="exxample">OPTIONS /alice/ HTTP/1.1
 Host: example.org      </pre></div> 
 
-      <div class="example"><div class="example-title"><span>Example 4</span>: Response - retreiving OPTIONS of a basic container</div><pre class="example">HTTP/1.1 204 OK
+      <div class="example"><div class="example-title"><span>Example 4</span>: Response - retreiving OPTIONS of a basic container</div><div class="exxample">HTTP/1.1 204 OK
 Allow: OPTIONS,HEAD,GET,POST,PUT,PATCH
 Accept-Post: text/turtle, application/ld+json, image/bmp, image/jpeg
 Accept-Patch: example/patch
@@ -705,7 +705,7 @@
       
       </p>
 
-      <div class="example"><div class="example-title"><span>Example 5</span>: Request - creating a RDF resource</div><pre class="example"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>POST /alice/ HTTP/1.1
+      <div class="example"><div class="example-title"><span>Example 5</span>: Request - creating a RDF resource</div><div class="exxample"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>POST /alice/ HTTP/1.1
 Host: example.org
 Slug: foaf
 Content-Type: text/turtle
@@ -740,18 +740,18 @@
 
     
 
-   <div class="example"><div class="example-title"><span>Example 6</span>: Response - creating a RDF resource</div><pre class="example">HTTP/1.1 201 Created
+   <div class="example"><div class="example-title"><span>Example 6</span>: Response - creating a RDF resource</div><div class="exxample">HTTP/1.1 201 Created
 Location: http://example.org/alice/foaf
 Link: &lt;http://www.w3.org/ns/ldp#Resource&gt;; rel='type'
 Content-Length: 0 </pre></div>
       <p> The response to the create request provides a Link to the newly created resource using the Location header. In this case, the server has honored the hint provided by the slug header and created the new resource in the URL http://example.org/alice/foaf. </p>
       <p>Knowing the URL of the newly created resource, Alice can check the container again to confirm that the container correctly contains the newly created resource.</p>
 
-      <div class="example"><div class="example-title"><span>Example 7</span>: Request - basic container retrieval after resource created</div><pre class="example">GET /alice/ HTTP/1.1
+      <div class="example"><div class="example-title"><span>Example 7</span>: Request - basic container retrieval after resource created</div><div class="exxample">GET /alice/ HTTP/1.1
 Host: example.org
 Accept: text/turtle, application/ld+json</pre></div>
 
-     <div class="example"><div class="example-title"><span>Example 8</span>: Response - basic container retrieval after resource created</div><pre class="example"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>HTTP/1.1 200 OK 
+     <div class="example"><div class="example-title"><span>Example 8</span>: Response - basic container retrieval after resource created</div><div class="exxample"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>HTTP/1.1 200 OK 
 Content-Type: text/turtle; charset=UTF-8
 Link: &lt;http://www.w3.org/ns/ldp#BasicContainer&gt;; rel='type'
 Allow: OPTIONS,HEAD,GET,POST,PUT,PATCH
@@ -785,7 +785,7 @@
 
       <p>Next, Alice wants to upload a photo of herself to the document storage. She can create an image by POSTing it in the same way she created the RDF document.</p>
 
-      <div class="example"><div class="example-title"><span>Example 9</span>: Request - creating a non-RDF resource</div><pre class="example">POST /alice/ HTTP/1.1
+      <div class="example"><div class="example-title"><span>Example 9</span>: Request - creating a non-RDF resource</div><div class="exxample">POST /alice/ HTTP/1.1
 Host: example.org
 Slug: avatar
 Link: &lt;http://www.w3.org/ns/ldp#Resource&gt;; rel="type"
@@ -794,7 +794,7 @@
 
 ### binary data ###</pre></div> 
 
-      <div class="example"><div class="example-title"><span>Example 10</span>: Response - creating a non-RDF resource</div><pre class="example">HTTP/1.1 201 Created
+      <div class="example"><div class="example-title"><span>Example 10</span>: Response - creating a non-RDF resource</div><div class="exxample">HTTP/1.1 201 Created
 Location: http://example.org/alice/avatar
 Link: &lt;http://www.w3.org/ns/ldp#Resource&gt;; rel="type"
 Link: &lt;http://example.org/alice/avatar/meta&gt;; rel="describedby"
@@ -805,7 +805,7 @@
       <p>The outcome of creating a non-RDF is similar to creating a RDF resource. If successful, the server will return a 201 success code with a Location header that points to the created resource. Furthermore, in the case of binary resources the server may create an additional file to maintain the metadata about the binary file. In the above example, the server creates a new LDP-RS to maintain metadata about the binary resource such as creation date, owner, etc. and this metadata resource is advertised using a Link header with the relation "describedby". </p>
       
       <p> Similar to creating a RDF resource (LDP-RS), a containment triple will be added to the container when a non-RDF (LDP-NR) is created. Thus, the representation of the LDP container after creating the image looks like the following. </p>
-      <div class="example"><div class="example-title"><span>Example 11</span>: Container representation after the non-RDF resource creation</div><pre class="example"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>@prefix dcterms: &lt;http://purl.org/dc/terms/&gt;.
+      <div class="example"><div class="example-title"><span>Example 11</span>: Container representation after the non-RDF resource creation</div><div class="exxample"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>@prefix dcterms: &lt;http://purl.org/dc/terms/&gt;.
 @prefix ldp: &lt;http://www.w3.org/ns/ldp#&gt;.
   
 &lt;http://example.org/alice/&gt; a ldp:Container, ldp:BasicContainer;
@@ -827,7 +827,7 @@
 
       <p>After creating the image as shown in the previous example, Alice now wants to update her FOAF profile with a link to the image. After retrieving her FOAF profile using a HTTP GET operation, she uses HTTP PUT to update the document by amending the RDF with a link to her photo.</p>
       <p> In this example, Alice's LDP client sends the E-tag of the resource representation that it retrieved previously to prevent any lost update problems. </p>
-      <div class="example"><div class="example-title"><span>Example 12</span>: Request - updating a RDF resource</div><pre class="example"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>PUT /alice/foaf HTTP/1.1
+      <div class="example"><div class="example-title"><span>Example 12</span>: Request - updating a RDF resource</div><div class="exxample"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>PUT /alice/foaf HTTP/1.1
 Host: example.org
 If-Match: W/"123454321"
 Content-Type: text/turtle
@@ -856,7 +856,7 @@
   "dcterms:title": "Alice’s FOAF file"
 }</pre></div></pre></div> 
 
-      <div class="example"><div class="example-title"><span>Example 13</span>: Response - updating a RDF resource</div><pre class="example">HTTP/1.1 204 No Content 
+      <div class="example"><div class="example-title"><span>Example 13</span>: Response - updating a RDF resource</div><div class="exxample">HTTP/1.1 204 No Content 
 Link: &lt;http://www.w3.org/ns/ldp#Resource&gt;; rel="type" </pre></div>
 
       <p>If the operation is successful as shown above, the document will be updated with new information.</p>
@@ -873,15 +873,15 @@
       <p>Similar to the previous update operation, Alice uses the etag of the resource representation she retrieved with If-Match header to do a conditional delete to ensure that the resource state
       was not changed since she decided to delete it. </p>
 
-      <div class="example"><div class="example-title"><span>Example 14</span>: Request - deleting a RDF resource</div><pre class="example">DELETE /alice/avatar HTTP/1.1
+      <div class="example"><div class="example-title"><span>Example 14</span>: Request - deleting a RDF resource</div><div class="exxample">DELETE /alice/avatar HTTP/1.1
 Host: example.org
 If-Match: W/"123454322"        </pre></div> 
 
-      <div class="example"><div class="example-title"><span>Example 15</span>: Response - deleting a RDF resource</div><pre class="example">HTTP/1.1 204 No Content </pre></div>
+      <div class="example"><div class="example-title"><span>Example 15</span>: Response - deleting a RDF resource</div><div class="exxample">HTTP/1.1 204 No Content </pre></div>
    
      <p> As well as deleting the resource, the server removes the containment triple from the container. For example, a subsequent GET request on the container will return a graph isomorphic to the one shown in the following representation::</p>
      
-     <div class="example"><div class="example-title"><span>Example 16</span>: Container representation after resource deletion</div><pre class="example"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>@prefix dcterms: &lt;http://purl.org/dc/terms/&gt;.
+     <div class="example"><div class="example-title"><span>Example 16</span>: Container representation after resource deletion</div><div class="exxample"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>@prefix dcterms: &lt;http://purl.org/dc/terms/&gt;.
 @prefix ldp: &lt;http://www.w3.org/ns/ldp#&gt;.
   
 &lt;http://example.org/alice/&gt; a ldp:Container, ldp:BasicContainer;
@@ -898,11 +898,11 @@
 }</pre></div></pre></div> 
      
      <p> For any subsequent request on the deleted resource, the server will respond with the appropriate HTTP response code. </p>
-      <div class="example"><div class="example-title"><span>Example 17</span>: Request - after deletion</div><pre class="example">GET /alice/avatar HTTP/1.1
+      <div class="example"><div class="example-title"><span>Example 17</span>: Request - after deletion</div><div class="exxample">GET /alice/avatar HTTP/1.1
 Host: example.org
 Accept: image/png</pre></div>
      
-      <div class="example"><div class="example-title"><span>Example 18</span>: Response - after deletion</div><pre class="example">HTTP/1.1 410 Gone </pre></div>     
+      <div class="example"><div class="example-title"><span>Example 18</span>: Response - after deletion</div><div class="exxample">HTTP/1.1 410 Gone </pre></div>     
     </section>
 
     <section typeof="bibo:Chapter" resource="#meta-structure" rel="bibo:Chapter" id="structural-manipulation-child-containers">
@@ -915,7 +915,7 @@
       <figcaption>Fig. <span class="figno">5</span> <span class="fig-title">Child Containers inside a Basic Container.</span></figcaption>
     </figure>
 
-      <div class="example"><div class="example-title"><span>Example 19</span>: State of Alice's document store before creating the photo (child) container</div><pre class="example"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>@prefix ldp: &lt;http://www.w3.org/ns/ldp#&gt; .
+      <div class="example"><div class="example-title"><span>Example 19</span>: State of Alice's document store before creating the photo (child) container</div><div class="exxample"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>@prefix ldp: &lt;http://www.w3.org/ns/ldp#&gt; .
 @prefix dcterms: &lt;http://purl.org/dc/terms/&gt; .
 
 &lt;http://example.org/alice/&gt; a ldp:Container, ldp:BasicContainer ;
@@ -931,7 +931,7 @@
 }</pre></div></pre></div>  
 
       <p>To create a new container for managing photos, Alice POSTs a representation of a container (LDP-BC) to the root container. Alice express her intention that the newly created resource should be an LDP Basic Container by including a Link header in the request with the relationship 'type'. </p>
-      <div class="example"><div class="example-title"><span>Example 20</span>: Request - creating a new container</div><pre class="example"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>POST alice/ HTTP/1.1
+      <div class="example"><div class="example-title"><span>Example 20</span>: Request - creating a new container</div><div class="exxample"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>POST alice/ HTTP/1.1
 Host: example.org
 Content-Type: text/turtle
 Link: &lt;http://www.w3.org/ns/ldp/BasicContainer&gt;; rel='type'
@@ -958,12 +958,12 @@
   "dcterms:description": "This container will contain photos of Alice."
 }</pre></div></pre></div>  
       <p>If the create is successful, the server responds with location of the newly created container for the photos.</p>
-      <div class="example"><div class="example-title"><span>Example 21</span>: Response - creating the new container</div><pre class="example">HTTP/1.1 201 Created
+      <div class="example"><div class="example-title"><span>Example 21</span>: Response - creating the new container</div><div class="exxample">HTTP/1.1 201 Created
 Location: http://example.org/alice/photos/
 Content-Length: 0  </pre></div>  
 
       <p>After creation of this new container, the parent container will look like</p>
-      <div class="example"><div class="example-title"><span>Example 22</span>: State of Alice's document store after creating the photo (child) container</div><pre class="example"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>@prefix ldp: &lt;http://www.w3.org/ns/ldp#&gt; .
+      <div class="example"><div class="example-title"><span>Example 22</span>: State of Alice's document store after creating the photo (child) container</div><div class="exxample"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>@prefix ldp: &lt;http://www.w3.org/ns/ldp#&gt; .
 @prefix dcterms: &lt;http://purl.org/dc/terms/&gt; .
 
 &lt;http://example.org/alice/&gt; a ldp:Container, ldp:BasicContainer ;
@@ -981,7 +981,7 @@
    ]
 }</pre></div></pre></div> 
       <p>and the photo container will look like the following.</p>
-      <div class="example"><div class="example-title"><span>Example 23</span>: State of Alice's newly created photo container</div><pre class="example"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>@prefix ldp: &lt;http://www.w3.org/ns/ldp#&gt; .
+      <div class="example"><div class="example-title"><span>Example 23</span>: State of Alice's newly created photo container</div><div class="exxample"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>@prefix ldp: &lt;http://www.w3.org/ns/ldp#&gt; .
 @prefix dcterms: &lt;http://purl.org/dc/terms/&gt; .
 
 &lt;http://example.org/alice/photos/&gt; a ldp:Container, ldp:BasicContainer;
@@ -1113,7 +1113,7 @@
       <h3 aria-level="2" role="heading" id="h3_navandret"><span class="secno">3.1 </span>Navigation and Retrieval (GET on an LDP-DC)</h3>
 
       <p>One of the main use cases of the example bug tracker is to list a given product's bugs. Assuming that a user got a URL of a product by out of band means, she can look it up to get more information including the bugs associated with it. To get the description of the product, a user (or her LDP client) can do a GET request on the URI of the known product resource. LDPR servers must provide text/turtle representations of the requested LDPRs and may provide other RDF format representations such as JSON-LD or RDF/XML using standard HTTP content negotiation.</p>
-      <div class="example"><div class="example-title"><span>Example 24</span>: Request - Product Lookup</div><pre class="example"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>GET /tracker/ldp-demo/ HTTP/1.1
+      <div class="example"><div class="example-title"><span>Example 24</span>: Request - Product Lookup</div><div class="exxample"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>GET /tracker/ldp-demo/ HTTP/1.1
 Host: example.org
 Accept: text/turtle; charset=UTF-8
 
@@ -1122,7 +1122,7 @@
 Accept: application/ld+json; charset=UTF-8</pre></div></pre></div>
       <p>If the product resource is available, the server responds with the RDF representation of the Direct Container that corresponds to the given product using the requested media type,
         <code>text/turtle</code> or <code>application/ld+json</code> in this case.</p>
-      <div class="example"><div class="example-title"><span>Example 25</span>: Response - Product Lookup</div><pre class="example"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>HTTP/1.1 200 OK 
+      <div class="example"><div class="example-title"><span>Example 25</span>: Response - Product Lookup</div><div class="exxample"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>HTTP/1.1 200 OK 
 Content-Type: text/turtle; charset=UTF-8
 Link: &lt;http://www.w3.org/ns/ldp#DirectContainer&gt;; rel="type",  &lt;http://www.w3.org/ns/ldp#Resource&gt;; rel='type'
 Allow: OPTIONS,HEAD,GET,POST,PUT,PATCH
@@ -1194,7 +1194,7 @@
 
       <p> The bug report document includes statements about the resource to be created. According the LDP specification, a client can use null relative URI (&lt;&gt;) in the request entity body to refer to resource to be created.
 
-      </p><div class="example"><div class="example-title"><span>Example 26</span>: A request for creating a bug</div><pre class="example"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>POST /tracker/ldp-demo/ HTTP/1.1
+      </p><div class="example"><div class="example-title"><span>Example 26</span>: A request for creating a bug</div><div class="exxample"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>POST /tracker/ldp-demo/ HTTP/1.1
 Host: example.org
 Content-Type: text/turtle
 Link: &lt;http://www.w3.org/ns/ldp#Resource&gt;; rel="type"
@@ -1224,7 +1224,7 @@
 Content-Length: 0           </pre></div>  
 
       <p>If the creation fails, the server will respond with an appropriate status code depending on the error. If successful, the LDP Demo product description LDPC will have the following representation after the creation of new resource.</p>
-      <div class="example"><div class="example-title"><span>Example 28</span>: The state of the product LDPC after the bug creation</div><pre class="example"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>@prefix ldp: &lt;http://www.w3.org/ns/ldp#&gt; .
+      <div class="example"><div class="example-title"><span>Example 28</span>: The state of the product LDPC after the bug creation</div><div class="exxample"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>@prefix ldp: &lt;http://www.w3.org/ns/ldp#&gt; .
 @prefix dcterms: &lt;http://purl.org/dc/terms/&gt; .
 @prefix bt: &lt;http://example.org/vocab/bugtracker#&gt; .
 
@@ -1257,7 +1257,7 @@
        (&lt;/tracker/ldp-demo/#it&gt;, &lt;bt:hasbug&gt;, &lt;/tracker/ldp-demo/bug67&gt;). The former is added in any type of container and the latter is defined by the direct 
        container properties. </p>
       <p>The created Bug resource will have the following representation. Note that server has added a server managed property, creation date (dcterms:created), and a default value for the state (bt:isInState) to the Bug in addition to what was POSTed.</p>
-      <div class="example"><div class="example-title"><span>Example 29</span>: The state of the bug LDPR</div><pre class="example"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>@prefix dcterms: &lt;http://purl.org/dc/terms/&gt; .
+      <div class="example"><div class="example-title"><span>Example 29</span>: The state of the bug LDPR</div><div class="exxample"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>@prefix dcterms: &lt;http://purl.org/dc/terms/&gt; .
 @prefix bt: &lt;http://example.org/vocab/bugtracker#&gt; .
 
 &lt;/tracker/ldp-demo/bug67&gt; a bt:Bug;
@@ -1285,15 +1285,15 @@
       
      This example illustrates the behaviour of a Direct Container when a resource is deleted.
       
-      <div class="example"><div class="example-title"><span>Example 30</span></div><pre class="example">DELETE /tracker/ldp-demo/bug3 HTTP/1.1 
+      <div class="example"><div class="example-title"><span>Example 30</span></div><div class="exxample">DELETE /tracker/ldp-demo/bug3 HTTP/1.1 
 Host: example.org
 If-Match: W/"123454322"</pre></div>
       <p>If the  delete is successful, the server will respond with a success status code.</p>
-      <div class="example"><div class="example-title"><span>Example 31</span></div><pre class="example">HTTP/1.1 204 No Content</pre></div>  
+      <div class="example"><div class="example-title"><span>Example 31</span></div><div class="exxample">HTTP/1.1 204 No Content</pre></div>  
         
        <p> After the deletion, the representation of the container will look like the following</p> 
        
-       <div class="example"><div class="example-title"><span>Example 32</span>: The state of the product LDPC after the bug deletion</div><pre class="example"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>@prefix ldp: &lt;http://www.w3.org/ns/ldp#&gt; .
+       <div class="example"><div class="example-title"><span>Example 32</span>: The state of the product LDPC after the bug deletion</div><div class="exxample"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>@prefix ldp: &lt;http://www.w3.org/ns/ldp#&gt; .
 @prefix dcterms: &lt;http://purl.org/dc/terms/&gt; .
 @prefix bt: &lt;http://example.org/vocab/bugtracker#&gt; .
 
@@ -1341,7 +1341,7 @@
       
       <p> Similar to the previous LDP-DC example, first we will retrieve the representation of the LDP Indirect Container.</p>
       
-      <div class="example"><div class="example-title"><span>Example 33</span>: Product lookup request</div><pre class="example"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>GET /tracker/ldp-demo/ HTTP/1.1
+      <div class="example"><div class="example-title"><span>Example 33</span>: Product lookup request</div><div class="exxample"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>GET /tracker/ldp-demo/ HTTP/1.1
 Host: example.org
 Accept: text/turtle; charset=UTF-8
 
@@ -1349,7 +1349,7 @@
 Host: example.org
 Accept: application/ld+json; charset=UTF-8</pre></div></pre></div>
       <p> As a response to the GET request, the server responds with the representation of the product description container.</p>
-      <div class="example"><div class="example-title"><span>Example 34</span>: HTTP response for product lookup</div><pre class="example"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>HTTP/1.1 200 OK 
+      <div class="example"><div class="example-title"><span>Example 34</span>: HTTP response for product lookup</div><div class="exxample"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>HTTP/1.1 200 OK 
 Content-Type: text/turtle; charset=UTF-8
 Link: &lt;http://www.w3.org/ns/ldp#IndirectContainer&gt;; rel="type",  &lt;http://www.w3.org/ns/ldp#Resource&gt;; rel='type'
 Allow: OPTIONS,HEAD,GET,POST,PUT,PATCH
@@ -1406,7 +1406,7 @@
       <p>Continuing from the previous example, we can create a new Bug Report against the 'LDP demo' product by creating a Bug Report LDPR under the 'LDP Demo' product description LDPC.</p>
 
       <p>The client POSTs a representation of a Bug Report to the Bug Tracker LDPC.</p>
-      <div class="example"><div class="example-title"><span>Example 35</span>: A request for creating a bug</div><pre class="example"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>POST /tracker/ldp-demo/ HTTP/1.1
+      <div class="example"><div class="example-title"><span>Example 35</span>: A request for creating a bug</div><div class="exxample"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>POST /tracker/ldp-demo/ HTTP/1.1
 Host: example.org
 Content-Type: text/turtle
 
@@ -1442,7 +1442,7 @@
 Content-Length: 0           </pre></div>        
 
       <p>If the creation fails, the server will respond with an appropriate status code depending on the error. After the resource is creation, the Product A LDPC will have the following representation.</p>
-      <div class="example"><div class="example-title"><span>Example 37</span>: The state of the product LDPC after the bug creation</div><pre class="example"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>@prefix ldp: &lt;http://www.w3.org/ns/ldp#&gt; .
+      <div class="example"><div class="example-title"><span>Example 37</span>: The state of the product LDPC after the bug creation</div><div class="exxample"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>@prefix ldp: &lt;http://www.w3.org/ns/ldp#&gt; .
 @prefix dcterms: &lt;http://purl.org/dc/terms/&gt; .
 @prefix bt: &lt;http://example.org/vocab/bugtracker#&gt; .
 
@@ -1541,4 +1541,4 @@
 </dd><dt id="bib-WEBARCH">[WEBARCH]</dt><dd rel="dcterms:references">Ian Jacobs; Norman Walsh. <a href="http://www.w3.org/TR/webarch/"><cite>Architecture of the World Wide Web, Volume One</cite></a>. 15 December 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/webarch/">http://www.w3.org/TR/webarch/</a>
 </dd><dt id="bib-json-ld">[json-ld]</dt><dd rel="dcterms:references">Manu Sporny; Gregg Kellogg; Markus Lanthaler. <a href="http://www.w3.org/TR/json-ld/"><cite>JSON-LD 1.0</cite></a>. 16 January 2014. W3C Recommendation. URL: <a href="http://www.w3.org/TR/json-ld/">http://www.w3.org/TR/json-ld/</a>
 </dd><dt id="bib-turtle">[turtle]</dt><dd rel="dcterms:references">Eric Prud'hommeaux; Gavin Carothers. <a href="http://www.w3.org/TR/turtle/"><cite>RDF 1.1 Turtle</cite></a>. 25 February 2014. W3C Recommendation. URL: <a href="http://www.w3.org/TR/turtle/">http://www.w3.org/TR/turtle/</a>
-</dd></dl></section></section></body></html>
\ No newline at end of file
+</dd></dl></section></section></body></html>
--- a/ldp-primer/ldp-primer.html	Wed Jun 18 12:28:32 2014 +0200
+++ b/ldp-primer/ldp-primer.html	Wed Jun 18 11:47:20 2014 +0100
@@ -39,7 +39,7 @@
         display('jsonld', 'none');
         set_display_by_id('hide-js', 'none');
         set_display_by_id('show-js', '');
-      }, 500)
+      }, 3000)
     }
 
     function display(syntax, status) {
@@ -105,7 +105,7 @@
       }
     }
   </script>
-  <script src='https://www.w3.org/Tools/respec/respec-w3c-common' class='remove' async></script>
+  <script src='https://www.w3.org/Tools/respec/respec-w3c-common' class='remove'></script>
   <script class='remove'>
     var respecConfig = {
       // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
ldpwg

Hosted by W3C Systems Team, please report bugs to sysreq@w3.org