add missing Linked headers to responses
authorNandana Mihindukulasooriya <nandana.cse@gmail.com>
Mon, 15 Sep 2014 12:28:29 +0200
changeset 830 1006614214e6
parent 829 7f6e09b0128b
child 831 f486e0154209
add missing Linked headers to responses
ldp-primer/examples/bcget_res.txt
ldp-primer/ldp-primer.html
--- a/ldp-primer/examples/bcget_res.txt	Fri Sep 12 11:05:59 2014 -0700
+++ b/ldp-primer/examples/bcget_res.txt	Mon Sep 15 12:28:29 2014 +0200
@@ -1,6 +1,6 @@
 HTTP/1.1 200 OK 
 Content-Type: text/turtle; charset=UTF-8
-Link: <http://www.w3.org/ns/ldp#BasicContainer>; rel='type'
+Link: <http://www.w3.org/ns/ldp#BasicContainer>; rel='type', <http://www.w3.org/ns/ldp#Resource>; rel='type'
 Allow: OPTIONS,HEAD,GET,POST,PUT,PATCH
 Content- Length: 245
 ETag: W/'123456789'
@@ -16,7 +16,7 @@
 
 HTTP/1.1 200 OK 
 Content-Type: application/ld+json; charset=UTF-8
-Link: <http://www.w3.org/ns/ldp#BasicContainer>; rel='type'
+Link: <http://www.w3.org/ns/ldp#BasicContainer>; rel='type', <http://www.w3.org/ns/ldp#Resource>; rel='type'
 Allow: OPTIONS,HEAD,GET,POST,PUT,PATCH
 Content- Length: 255
 ETag: W/'123456789'
--- a/ldp-primer/ldp-primer.html	Fri Sep 12 11:05:59 2014 -0700
+++ b/ldp-primer/ldp-primer.html	Mon Sep 15 12:28:29 2014 +0200
@@ -471,7 +471,7 @@
 Allow: OPTIONS,HEAD,GET,POST,PUT,PATCH
 Accept-Post: text/turtle, application/ld+json, image/bmp, image/jpeg
 Accept-Patch: example/patch
-Link: &lt;http://www.w3.org/ns/ldp#BasicContainer&gt;; rel=&#39;type&#39;     
+Link: &lt;http://www.w3.org/ns/ldp#BasicContainer&gt;; rel=&#39;type&#39;, &lt;http://www.w3.org/ns/ldp#Resource&gt;; rel=&#39;type&#39;     
       </pre> 
 
       <p>According to the response, HTTP operations {OPTIONS,HEAD, GET,POST,PUT,PATCH} are allowed on her root container. In addition to the allowed operations, Accept-Post and Accept-Patch provides which media types are supported by the respective operations. The rel="type" Link header advertises that this resource supports LDP protocol and it is an LDP Basic Container.</p>
@@ -579,7 +579,8 @@
    </pre> 
 
       <pre title="Response - deleting a RDF resource" class="example"> 
-HTTP/1.1 204 No Content 
+HTTP/1.1 204 No Content
+Link: &lt;http://www.w3.org/ns/ldp#Resource&gt;; rel=&quot;type&quot;
    </pre>
    
      <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>
@@ -616,6 +617,7 @@
       <pre title="Response - creating the new container" class="example">
 HTTP/1.1 201 Created
 Location: http://example.org/alice/photos/
+Link: &lt;http://www.w3.org/ns/ldp#Resource&gt;; rel=&quot;type&quot;
 Content-Length: 0  
         </pre>  
 
@@ -776,6 +778,7 @@
       <pre title="A response of creating new a bug" class='example' data-oninclude='fixCode'>
 HTTP/1.1 201 Created
 Location: http://example.org/tracker/ldp-demo/bug67
+Link: &lt;http://www.w3.org/ns/ldp#Resource&gt;; rel=&quot;type&quot;
 Content-Length: 0           
       </pre>  
 
@@ -802,6 +805,7 @@
       <p>If the  delete is successful, the server will respond with a success status code.</p>
       <pre class="example">
  HTTP/1.1 204 No Content
+ Link: &lt;http://www.w3.org/ns/ldp#Resource&gt;; rel=&quot;type&quot; 
         </pre>  
         
        <p> After the deletion, the representation of the container will look like the following</p>