ldp.html
changeset 176 60b0a09af2c4
parent 175 bcc13fba2593
child 178 0ec347702232
child 179 9d563e756b28
equal deleted inserted replaced
175:bcc13fba2593 176:60b0a09af2c4
  1082 			which resource is the membership subject and which predicate is the
  1082 			which resource is the membership subject and which predicate is the
  1083 			membership predicate, so the example includes this information in
  1083 			membership predicate, so the example includes this information in
  1084 			triples whose subject is the LDPC resource itself.
  1084 			triples whose subject is the LDPC resource itself.
  1085 	</p>
  1085 	</p>
  1086 	
  1086 	
       
  1087 	<!-- @@@ TODO: ISSUE-72 sample for membershipObject-->
       
  1088 	
  1087 	<div id="ldpc-member_data" class="rule">5.1.1 Container Member Information</div>
  1089 	<div id="ldpc-member_data" class="rule">5.1.1 Container Member Information</div>
  1088 	<em>This section is non-normative</em>
  1090 	<em>This section is non-normative</em>
  1089 	<p>In many – perhaps most – applications
  1091 	<p>In many – perhaps most – applications
  1090 		involving containers, it is desirable for the client to be able to
  1092 		involving containers, it is desirable for the client to be able to
  1091 		get information about each container member without having to do a
  1093 		get information about each container member without having to do a
  1262 			representation to use that order in whatever way is appropriate, for 
  1264 			representation to use that order in whatever way is appropriate, for 
  1263 			example to sort the data prior to presentation on a user interface.
  1265 			example to sort the data prior to presentation on a user interface.
  1264 		</p>
  1266 		</p>
  1265 </section>
  1267 </section>
  1266 
  1268 
       
  1269 	<!-- @@@ TODO: ISSUE-72 new section just for membershipObject?-->
       
  1270 
  1267 <section>
  1271 <section>
  1268 <h2 id="ldpc-general">General</h2>
  1272 <h2 id="ldpc-general">General</h2>
  1269 	<p>The Linked Data Platform does not define how clients
  1273 	<p>The Linked Data Platform does not define how clients
  1270 		discover <dfn><abbr title="Linked Data Platform Containers">LDPCs</abbr></dfn>.</p>
  1274 		discover <dfn><abbr title="Linked Data Platform Containers">LDPCs</abbr></dfn>.</p>
  1271 
  1275 
  1351 		Certain specific cases exist where a LDPC server MAY delete a resource and then later re-use the
  1355 		Certain specific cases exist where a LDPC server MAY delete a resource and then later re-use the
  1352 		URI when it identifies the same resource, but only when consistent with Web architecture [[WEBARCH]].
  1356 		URI when it identifies the same resource, but only when consistent with Web architecture [[WEBARCH]].
  1353 		While it is difficult to provide absolute implementation guarantees of non-reuse in all failure
  1357 		While it is difficult to provide absolute implementation guarantees of non-reuse in all failure
  1354 		scenarios, re-using URIs creates ambiguities for clients that are best avoided.
  1358 		scenarios, re-using URIs creates ambiguities for clients that are best avoided.
  1355 	</div>
  1359 	</div>
       
  1360 	
       
  1361 	<!-- @@@ TODO: ISSUE-72 rules for membershipObject-->
  1356 	
  1362 	
  1357 </section>
  1363 </section>
  1358 
  1364 
  1359 <section>	
  1365 <section>	
  1360 <h2 id="ldpc-HTTP_GET">HTTP GET</h2>
  1366 <h2 id="ldpc-HTTP_GET">HTTP GET</h2>
  1603 		whose subject is the container's URI, 
  1609 		whose subject is the container's URI, 
  1604 		whose predicate is <code>ldp:contains</code>, and
  1610 		whose predicate is <code>ldp:contains</code>, and
  1605 		whose object is the newly created member resource's URI; 
  1611 		whose object is the newly created member resource's URI; 
  1606 		it MAY add other triples as well.
  1612 		it MAY add other triples as well.
  1607 	</div>
  1613 	</div>
       
  1614 	
       
  1615 	<!-- @@@ TODO: ISSUE-72 creation requirements with membershipObject
       
  1616 	
       
  1617 	- do we need to handle membershipPredicateInverse with membershipObject (my head hurts)?
       
  1618 	- we don't have membershipPredicateInverse in samples/intro, treat membershipObject same?
       
  1619 	- what happens when a client POSTs w/o the triple to indicate membershipObject, guess we 
       
  1620 	  just default to if mO is omitted (ie server gets to pick)
       
  1621 	- since we have ldp:membershipSubject and ldp:membershipPredicate which help a client know
       
  1622 	  what is used to determine membership....ldp:membershipObject is *different* in that it
       
  1623 	  tells clients what triple to insert of the form:
       
  1624 	     <> {membershipObject} <#me>.
       
  1625 	- do we need to make rules about POSTed triples like:
       
  1626 	     <> {mO} <http://someotherserver.com/foo>.
       
  1627 	  these seem not like intended behavior but "could" work
       
  1628 	  
       
  1629 	-->
  1608 	
  1630 	
  1609 	
  1631 	
  1610 </section>
  1632 </section>
  1611 
  1633 
  1612 <section>
  1634 <section>