ldp.html
changeset 938 859f98c26867
parent 937 ae4acedaf21b
equal deleted inserted replaced
937:ae4acedaf21b 938:859f98c26867
  1057 	freedom in the resource model.  In these situations, it can be useful to help clients map
  1057 	freedom in the resource model.  In these situations, it can be useful to help clients map
  1058 	LDP patterns onto existing vocabularies, or to include members not created via the container; 
  1058 	LDP patterns onto existing vocabularies, or to include members not created via the container; 
  1059 	<a title="Linked Data Platform Direct Container">LDP Direct Containers</a>
  1059 	<a title="Linked Data Platform Direct Container">LDP Direct Containers</a>
  1060 	meet those kinds of needs.  Direct Containers allow membership triples to use a subject
  1060 	meet those kinds of needs.  Direct Containers allow membership triples to use a subject
  1061 	other than the container itself as the consistent membership value, and/or to use
  1061 	other than the container itself as the consistent membership value, and/or to use
  1062 	a  predicate from an application's domain model as the membership predicate. Let's
  1062 	a  predicate from an application's domain model as the membership predicate.</p>
  1063 	start with a pre-existing domain resource for a person's net worth, as illustrated below:</p>
  1063 	<p>Let's start with a pre-existing domain resource for a person's net worth, as illustrated 
       
  1064 	immediately below, and then see how a Container resource can be applied in subsequent examples:</p>
  1064 			
  1065 			
  1065 <em>Request</em> to <code>http://example.org/netWorth/nw1/</code>:
  1066 <em>Request</em> to <code>http://example.org/netWorth/nw1/</code>:
  1066 <pre class="example" id="ldpc-ex-membership-partial-req">GET /netWorth/nw1/ HTTP/1.1
  1067 <pre class="example" id="ldpc-ex-membership-partial-req">GET /netWorth/nw1/ HTTP/1.1
  1067 Host: example.org
  1068 Host: example.org
  1068 Accept: text/turtle</pre>
  1069 Accept: text/turtle</pre>
  2524 <!-- 
  2525 <!-- 
  2525 <h2>Detailed history</h2> -->
  2526 <h2>Detailed history</h2> -->
  2526 <!-- <blockquote><em><a href="http://www.w3.org/TR/2014/PR-ldp-20141216/">Proposed Recommendation Draft</a></em></blockquote> -->
  2527 <!-- <blockquote><em><a href="http://www.w3.org/TR/2014/PR-ldp-20141216/">Proposed Recommendation Draft</a></em></blockquote> -->
  2527 <!-- 
  2528 <!-- 
  2528 <ul>
  2529 <ul>
       
  2530 	<li>2015-01-26 - AC rep comment #2 on clarity on types in examples (SS)</li>
  2529 	<li>2015-01-26 - AC rep comment #1 on clarity in security considerations (SS)</li>
  2531 	<li>2015-01-26 - AC rep comment #1 on clarity in security considerations (SS)</li>
  2530 	<li>2015-01-26 - Align usage of Link: rel= to not use single quotes per RFC5988 (SS)</li>
  2532 	<li>2015-01-26 - Align usage of Link: rel= to not use single quotes per RFC5988 (SS)</li>
  2531 </ul>
  2533 </ul>
  2532 -->
  2534 -->
  2533 
  2535