ldp.html
changeset 102 04e3e77e4e78
parent 99 bce7fdfc503d
child 104 78fd14175304
equal deleted inserted replaced
101:c571cc15ebe4 102:04e3e77e4e78
   240 
   240 
   241 <p>A conforming <b>LDP Server</b> is an application program that processes HTTP 
   241 <p>A conforming <b>LDP Server</b> is an application program that processes HTTP 
   242 requests and generates HTTP responses that conform to the rules defined in sections on <a href="#linked-data-platform-resources">LDPRs</a>
   242 requests and generates HTTP responses that conform to the rules defined in sections on <a href="#linked-data-platform-resources">LDPRs</a>
   243 and <a href="#linked-data-platform-containers">LDPCs</a></p>
   243 and <a href="#linked-data-platform-containers">LDPCs</a></p>
   244 
   244 
       
   245 <div class="ldp-issue">
       
   246 	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/57">ISSUE-57</a></div>
       
   247 	How can a client determine that it is in communication with an LDP server?
       
   248 	</div>
       
   249 
   245 <p>A conforming <b>LDP Client</b> is an application program that generates HTTP 
   250 <p>A conforming <b>LDP Client</b> is an application program that generates HTTP 
   246 requests and processes HTTP responses that conform to the rules defined in sections on <a href="#linked-data-platform-resources">LDPRs</a>
   251 requests and processes HTTP responses that conform to the rules defined in sections on <a href="#linked-data-platform-resources">LDPRs</a>
   247 and <a href="#linked-data-platform-containers">LDPCs</a></p>
   252 and <a href="#linked-data-platform-containers">LDPCs</a></p>
   248 
   253 
   249 </section>
   254 </section>
   736    o:value 20000.
   741    o:value 20000.
   737 &lt;a3&gt;
   742 &lt;a3&gt;
   738    a o:RealEstateHolding;
   743    a o:RealEstateHolding;
   739    o:value 300000.</pre>
   744    o:value 300000.</pre>
   740 
   745 
       
   746 <div class="ldp-issue">
       
   747 	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/58">ISSUE-58</a></div>
       
   748 	Property for asserting that complete description of members is included in LDPC representation
       
   749 	</div>
       
   750 
   741 	<div id="ldpc-get_non-member_props" class="rule">5.1.2 Retrieving Only Non-member Properties
   751 	<div id="ldpc-get_non-member_props" class="rule">5.1.2 Retrieving Only Non-member Properties
   742 	</div>
   752 	</div>
   743 	<em>This section is non-normative</em>
   753 	<em>This section is non-normative</em>
   744 	<p>The representation of a container
   754 	<p>The representation of a container
   745 		that has many members will be large. There are several important
   755 		that has many members will be large. There are several important
   977 		from the server application vocabulary. If there is no obvious
   987 		from the server application vocabulary. If there is no obvious
   978 		predicate from the server application vocabulary to use, LDPC servers
   988 		predicate from the server application vocabulary to use, LDPC servers
   979 		SHOULD use the <code>rdfs:member</code> predicate.
   989 		SHOULD use the <code>rdfs:member</code> predicate.
   980 	</div>
   990 	</div>
   981 	
   991 	
       
   992 	<div class="ldp-issue">
       
   993 	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/51">ISSUE-51</a></div>
       
   994 	Linking from a Resource to its Containers (not the containers the resource is in)
       
   995 	</div>
       
   996 	
   982 	<div id="ldpc-5_2_4" class="rule">5.2.4 An LDPC MUST contain one triple containing the <code>ldp:membershipSubject</code>
   997 	<div id="ldpc-5_2_4" class="rule">5.2.4 An LDPC MUST contain one triple containing the <code>ldp:membershipSubject</code>
   983 		predicate when the membership subject is not the LDPC itself.  
   998 		predicate when the membership subject is not the LDPC itself.  
   984 		This triple's object provides clients with the LDPC's membership subject URI.
   999 		This triple's object provides clients with the LDPC's membership subject URI.
   985 	</div>
  1000 	</div>
   986 	
  1001 	
  1054 		retrieve non-member resource properties via a Request-URI of “<code>&lt;containerURL&gt;?non-member-properties</code>”,
  1069 		retrieve non-member resource properties via a Request-URI of “<code>&lt;containerURL&gt;?non-member-properties</code>”,
  1055 		MUST return a HTTP status code 404 (Not Found).  An LDPC server that supports a request to
  1070 		MUST return a HTTP status code 404 (Not Found).  An LDPC server that supports a request to
  1056 		retrieve non-member resource properties via a different Request-URI than “<code>&lt;containerURL&gt;?non-member-properties</code>”,
  1071 		retrieve non-member resource properties via a different Request-URI than “<code>&lt;containerURL&gt;?non-member-properties</code>”,
  1057 		MUST return a HTTP Redirection 3xx status code such as 301 (Moved Permanently) or 302 (Found).
  1072 		MUST return a HTTP Redirection 3xx status code such as 301 (Moved Permanently) or 302 (Found).
  1058 	</div>
  1073 	</div>
       
  1074 	
       
  1075 	<div class="ldp-issue">
       
  1076 	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/55">ISSUE-55</a></div>
       
  1077 	Hypermedia as the Engine of Application State (HATEOAS) Compliance
       
  1078 	</div>
       
  1079 	
  1059 	<div id="ldpc-5_3_3" class="rule">5.3.3 An LDPC server that does not support a request to retrieve the first
  1080 	<div id="ldpc-5_3_3" class="rule">5.3.3 An LDPC server that does not support a request to retrieve the first
  1060 		page resource representation from a known LDPC whose URL is “<code>&lt;containerURL&gt;</code>” by using
  1081 		page resource representation from a known LDPC whose URL is “<code>&lt;containerURL&gt;</code>” by using
  1061 		the Request-URI “<code>&lt;containerURL&gt;?firstPage</code>”, MUST return a HTTP status code 404 (Not
  1082 		the Request-URI “<code>&lt;containerURL&gt;?firstPage</code>”, MUST return a HTTP status code 404 (Not
  1062 		Found).
  1083 		Found).
  1063 		An LDPC server that supports that request using a different Request-URI than “<code>&lt;containerURL&gt;?firstPage</code>”,
  1084 		An LDPC server that supports that request using a different Request-URI than “<code>&lt;containerURL&gt;?firstPage</code>”,
  1127 <h2 id="ldpc-HTTP_POST">HTTP POST</h2>
  1148 <h2 id="ldpc-HTTP_POST">HTTP POST</h2>
  1128 	<p>This specification imposes the following new requirements on HTTP POST for LDPCs 
  1149 	<p>This specification imposes the following new requirements on HTTP POST for LDPCs 
  1129 		only when an LDPC supports that method.  This specification does not impose any
  1150 		only when an LDPC supports that method.  This specification does not impose any
  1130 		new requirement to support that method, and [[!HTTP11]] makes it optional.</p>
  1151 		new requirement to support that method, and [[!HTTP11]] makes it optional.</p>
  1131 		
  1152 		
       
  1153 	<div class="ldp-issue">
       
  1154 	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/50">ISSUE-50</a></div>
       
  1155 	Intuitive Containers: better support for relative URIs
       
  1156 	</div>	
       
  1157 		
  1132 	<div id="ldpc-5_4_1" class="rule">5.4.1 LDPC clients SHOULD create member resources by submitting a representation as
  1158 	<div id="ldpc-5_4_1" class="rule">5.4.1 LDPC clients SHOULD create member resources by submitting a representation as
  1133 		the entity body of the HTTP POST to a known LDPC. If the resource was created successfully, LDPC servers MUST
  1159 		the entity body of the HTTP POST to a known LDPC. If the resource was created successfully, LDPC servers MUST
  1134 		respond with status code 201 (Created) and the <code>Location</code>
  1160 		respond with status code 201 (Created) and the <code>Location</code>
  1135 		header set to the new resource’s URL. Clients shall not expect any representation in the response
  1161 		header set to the new resource’s URL. Clients shall not expect any representation in the response
  1136 		entity body on a 201 (Created) response.
  1162 		entity body on a 201 (Created) response.
  1197 <section>
  1223 <section>
  1198 <h2 id="ldpc-HTTP_PUT">HTTP PUT</h2>
  1224 <h2 id="ldpc-HTTP_PUT">HTTP PUT</h2>
  1199 	<p>This specification imposes the following new requirements on HTTP PUT for LDPCs 
  1225 	<p>This specification imposes the following new requirements on HTTP PUT for LDPCs 
  1200 		only when an LDPC supports that method.  This specification does not impose any
  1226 		only when an LDPC supports that method.  This specification does not impose any
  1201 		new requirement to support that method, and [[!HTTP11]] makes it optional.</p>
  1227 		new requirement to support that method, and [[!HTTP11]] makes it optional.</p>
       
  1228 		
       
  1229 	<div class="ldp-issue">
       
  1230 	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/56">ISSUE-56</a></div>
       
  1231 	How can clients discover LDPR PUT URLs?
       
  1232 	</div>	
  1202 		
  1233 		
  1203 	<div id="ldpc-5_5_1" class="rule">5.5.1 LDPC servers SHOULD NOT allow HTTP PUT to update a LDPC’s members; 
  1234 	<div id="ldpc-5_5_1" class="rule">5.5.1 LDPC servers SHOULD NOT allow HTTP PUT to update a LDPC’s members; 
  1204 		if the server receives such a request, it SHOULD respond with a 409
  1235 		if the server receives such a request, it SHOULD respond with a 409
  1205 		(Conflict) status code.
  1236 		(Conflict) status code.
  1206 	</div>
  1237 	</div>
  1228 	</div>
  1259 	</div>
  1229 	<div id="ldpc-5_6_3" class="rule">5.6.3 When the LDPC includes an <code>rdf:type</code> predicate with an object of <code>ldp:CompositeContainer</code>,
  1260 	<div id="ldpc-5_6_3" class="rule">5.6.3 When the LDPC includes an <code>rdf:type</code> predicate with an object of <code>ldp:CompositeContainer</code>,
  1230 		the server MUST also delete the resources that are referenced as its contents.  
  1261 		the server MUST also delete the resources that are referenced as its contents.  
  1231 		The LDPC membership triple MUST also be updated as defined by <a href="#ldpc-5_6_1">5.6.1</a> above.
  1262 		The LDPC membership triple MUST also be updated as defined by <a href="#ldpc-5_6_1">5.6.1</a> above.
  1232 	</div>
  1263 	</div>
       
  1264 	
       
  1265 	<div class="ldp-issue">
       
  1266 	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/59">ISSUE-59</a></div>
       
  1267 	Recursive delete: reconsider usage of Aggregate/Composite construct to get predictable container delete behavior
       
  1268 	</div>	
  1233 	
  1269 	
  1234 	<div class="ldp-issue">
  1270 	<div class="ldp-issue">
  1235 	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/28">ISSUE-28</a></div>
  1271 	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/28">ISSUE-28</a></div>
  1236 	transaction/rollback when deleting resources from a LDPC.
  1272 	transaction/rollback when deleting resources from a LDPC.
  1237 	note also that 5.6.2's reminder about 5.6.1 is only sensible if there is no transactional behavior in the recursive delete.
  1273 	note also that 5.6.2's reminder about 5.6.1 is only sensible if there is no transactional behavior in the recursive delete.