~ tweaked rel= per http://www.w3.org/2012/ldp/wiki/Meetings:Telecon2014.01.27#ISSUE-92_-_Interaction_Model
--- a/Test Cases/LDP Test Cases.html Wed Jan 22 20:17:33 2014 -0500
+++ b/Test Cases/LDP Test Cases.html Wed Jan 22 20:41:00 2014 -0500
@@ -15,7 +15,7 @@
<p>see <a href="#TC-C9">TC-C9</a></p>
<!-- ul>
<li property="td:specificationReference" typeof="tn:Excerpt">
- <div><span property="tn:includesText">4.2.10 LDPR servers MUST advertise their LDP support by exposing a HTTP Link header with a target URI of http://www.w3.org/ns/ldp/Resource, and a link relation type of type (that is, rel="type") in all responses to requests made to the resource's HTTP Request-URI. [...]</span><span property="rdfs:seeAlso" href="http://www.w3.org/TR/ldp/"></span></div>
+ <div><span property="tn:includesText">4.2.10 LDPR servers MUST advertise their LDP support by exposing a HTTP Link header with a target URI of http://www.w3.org/ns/ldp/Resource, and a link relation type of type (that is, rel=profile) in all responses to requests made to the resource's HTTP Request-URI. [...]</span><span property="rdfs:seeAlso" href="http://www.w3.org/TR/ldp/"></span></div>
</li>
<li property="td:specificationReference" typeof="tn:Excerpt"> <div><span property="tn:includesText">5.4.1 [...] If the resource was created successfully, LDPC servers MUST respond with status code 201 (Created) and the Location header set to the new resource’s URL. [...] </span><span property="rdfs:seeAlso" href="http://www.w3.org/TR/ldp/"></span></div> </li>
<li property="td:specificationReference" typeof="tn:Excerpt"> <div><span property="tn:includesText">5.4.2 After a successful HTTP POST request to a LDPC, the new resource MUST appear as a member of the LDPC until the new resource is deleted or removed by other methods. [...] </span><span property="rdfs:seeAlso" href="http://www.w3.org/TR/ldp/"></span></div> </li>
@@ -51,7 +51,7 @@
<div property="dc:description">POST <LDPC URI>
<ul>
<li>[entity-header].Content-type = text/turtle</li>
- <li><span style="background-color: #cff;">[entity-header].Link-type = LDP:Container</span></li>
+ <li><span style="background-color: #cff;">[entity-header].Link: val=<LDP1ContainerInteraction>; rel=profile;</span></li>
<li>[message-body] = <LDPC2 representation></li>
</ul>
</div>
@@ -99,7 +99,7 @@
<ul>
<li>[Status-Line].Status-Code = 2xx</li>
<li>[response-header].ETag exists</li>
- <li>[response-header].Link = ldp:Resource; rel="type"</li>
+ <li>[response-header].Link: val=<LDP1ResourceInteraction>; rel=profile</li>
</ul>
</div>
</div>
@@ -130,7 +130,7 @@
<ul>
<li>[Status-Line].Status-Code = 201</li>
<li>[response-header].Location exists</li>
- <li><span style="background-color: #cff;">[response-header].Link<span style="color: #f30;">:</span> <span style="color: #f30;">val=</span>ldp:Container; rel="type"</span></li>
+ <li><span style="background-color: #cff;">[response-header].Link<span style="color: #f30;">:</span> <span style="color: #f30;">val=</span><LDP1ContainerInteraction>; rel=profile</span></li>
</ul>
</div>
</div>
@@ -141,7 +141,7 @@
<ul>
<li>[Status-Line].Status-Code = 2xx</li>
<li>[response-header].ETag exists</li>
- <li><span style="background-color: #cff;">[response-header].Link: val=ldp:Container; rel="type"</span></li>
+ <li><span style="background-color: #cff;">[response-header].Link: val=<LDP1ContainerInteraction>; rel=profile</span></li>
</ul>
</div>
</div>
@@ -172,7 +172,7 @@
<ul>
<li>[Status-Line].Status-Code = 2xx</li>
<li>[response-header].ETag exists</li>
- <li>[response-header].Link = ldp:Resource; rel="type"</li>
+ <li>[response-header].Link: val=<LDP1ResourceInteraction>; rel=profile</li>
</ul>
</div>
</div>
@@ -189,7 +189,7 @@
<p>see <a href="#TC-C9">TC-C9</a></p>
<!-- ul>
<li property="td:specificationReference" typeof="tn:Excerpt">
- <div><span property="tn:includesText">4.2.10 LDPR servers MUST advertise their LDP support by exposing a HTTP Link header with a target URI of http://www.w3.org/ns/ldp/Resource, and a link relation type of type (that is, rel="type") in all responses to requests made to the resource's HTTP Request-URI. [...]</span><span property="rdfs:seeAlso" href="http://www.w3.org/TR/ldp/"></span></div>
+ <div><span property="tn:includesText">4.2.10 LDPR servers MUST advertise their LDP support by exposing a HTTP Link header with a target URI of http://www.w3.org/ns/ldp/Resource, and a link relation type of type (that is, rel=profile) in all responses to requests made to the resource's HTTP Request-URI. [...]</span><span property="rdfs:seeAlso" href="http://www.w3.org/TR/ldp/"></span></div>
</li>
<li property="td:specificationReference" typeof="tn:Excerpt"> <div><span property="tn:includesText">5.4.1 [...] If the resource was created successfully, LDPC servers MUST respond with status code 201 (Created) and the Location header set to the new resource’s URL. [...] </span><span property="rdfs:seeAlso" href="http://www.w3.org/TR/ldp/"></span></div> </li>
<li property="td:specificationReference" typeof="tn:Excerpt"> <div><span property="tn:includesText">5.4.2 After a successful HTTP POST request to a LDPC, the new resource MUST appear as a member of the LDPC until the new resource is deleted or removed by other methods. [...] </span><span property="rdfs:seeAlso" href="http://www.w3.org/TR/ldp/"></span></div> </li>
@@ -225,7 +225,7 @@
<div property="dc:description">POST <LDPC URI>
<ul>
<li>[entity-header].Content-type = text/turtle</li>
- <li><span style="background-color: #cff;">[entity-header].Link-type = LDP:Resource</span></li>
+ <li><span style="background-color: #cff;">[entity-header].Link: val=<LDP1ResourceInteraction> rel="profile"</span></li>
<li>[message-body] = <LDPC2 representation></li>
</ul>
</div>
@@ -273,7 +273,7 @@
<ul>
<li>[Status-Line].Status-Code = 2xx</li>
<li>[response-header].ETag exists</li>
- <li>[response-header].Link = ldp:Resource; rel="type"</li>
+ <li>[response-header].Link: val=<LDP1ResourceInteraction>; rel=profile</li>
</ul>
</div>
</div>
@@ -304,7 +304,7 @@
<ul>
<li>[Status-Line].Status-Code = 201</li>
<li>[response-header].Location exists</li>
- <li><span style="background-color: #cff;">[response-header].Link<span style="color: #f30;">:</span> <span style="color: #f30;">val=</span>ldp:Resource; rel="type"</span></li>
+ <li><span style="background-color: #cff;">[response-header].Link<span style="color: #f30;">:</span> <span style="color: #f30;">val=</span>ldp:Resource; rel=profile</span></li>
</ul>
</div>
</div>
@@ -315,7 +315,7 @@
<ul>
<li>[Status-Line].Status-Code = 2xx</li>
<li>[response-header].ETag exists</li>
- <li><span style="background-color: #cff;">[response-header].Link: val=ldp:Resource; rel="type"</span></li>
+ <li><span style="background-color: #cff;">[response-header].Link: val=ldp:Resource; rel=profile</span></li>
</ul>
</div>
</div>
@@ -346,7 +346,7 @@
<ul>
<li>[Status-Line].Status-Code = 2xx</li>
<li>[response-header].ETag exists</li>
- <li>[response-header].Link = ldp:Resource; rel="type"</li>
+ <li>[response-header].Link: val=<LDP1ResourceInteraction>; rel=profile</li>
</ul>
</div>
</div>