ldp.html
changeset 456 6130538abdf0
parent 454 4a28a15ee8fd
child 458 241a71502265
equal deleted inserted replaced
455:043ab2b9229b 456:6130538abdf0
   288 	<dt><dfn>Linked Data Platform Resource</dfn> (<abbr title="Linked Data Platform Resource">LDPR</abbr>)</dt>
   288 	<dt><dfn>Linked Data Platform Resource</dfn> (<abbr title="Linked Data Platform Resource">LDPR</abbr>)</dt>
   289 	<dd>HTTP resource whose state is represented in any representation that conforms to the simple lifecycle
   289 	<dd>HTTP resource whose state is represented in any representation that conforms to the simple lifecycle
   290 		patterns and conventions in <a href="#ldpr" class="sectionRef"></a>.<p></p></dd>
   290 		patterns and conventions in <a href="#ldpr" class="sectionRef"></a>.<p></p></dd>
   291 		
   291 		
   292 	<dt><dfn>Linked Data Platform RDF Resource</dfn> (<abbr title="Linked Data Platform RDF Resource">LDP-RR</abbr>)</dt>
   292 	<dt><dfn>Linked Data Platform RDF Resource</dfn> (<abbr title="Linked Data Platform RDF Resource">LDP-RR</abbr>)</dt>
   293 	<dd>An <a title="Linked Data Platform Resource">LDP-R</a> whose state is represented in an RDF representation.
   293 	<dd>An <a title="Linked Data Platform Resource">LDP-R</a> whose state is represented in an RDF representation, specifically
       
   294 	an RDF <a href="http://www.w3.org/TR/rdf11-concepts/#dfn-named-graph">named graph</a> [[rdf11-concepts]].
   294 	<p></p></dd>	
   295 	<p></p></dd>	
   295 
   296 
   296 	<dt><dfn>Linked Data Platform Binary Resource</dfn> (<abbr title="Linked Data Platform Binary Resource">LDP-BR</abbr>)</dt>
   297 	<dt><dfn>Linked Data Platform Binary Resource</dfn> (<abbr title="Linked Data Platform Binary Resource">LDP-BR</abbr>)</dt>
   297 	<dd>An <a title="Linked Data Platform Resource">LDPR</a> whose state is <em>not</em> represented in an RDF representation.
   298 	<dd>An <a title="Linked Data Platform Resource">LDPR</a> whose state is <em>not</em> represented in an RDF representation.
   298 	These are binary or text resources that do not have useful RDF representations.
   299 	These are binary or text resources that do not have useful RDF representations.
  1130 	<p>From this example, there is a <code>rdf:type</code> of <code>o:NetWorth</code> indicating the
  1131 	<p>From this example, there is a <code>rdf:type</code> of <code>o:NetWorth</code> indicating the
  1131 	resource represents an instance of a person's net worth and <code>o:netWorthOf</code> predicate indicating 
  1132 	resource represents an instance of a person's net worth and <code>o:netWorthOf</code> predicate indicating 
  1132 	the associated person.  There are two sets of same-subject, same-predicate pairings; one for assets and
  1133 	the associated person.  There are two sets of same-subject, same-predicate pairings; one for assets and
  1133 	one for liabilities.  It would be helpful to be able to associate these multi-valued sets using a URL
  1134 	one for liabilities.  It would be helpful to be able to associate these multi-valued sets using a URL
  1134 	for them to assist with managing these, this is done by associating containers with them as 
  1135 	for them to assist with managing these, this is done by associating containers with them as 
  1135 	illustrated below:
  1136 	illustrated in the 3 examples below:
  1136 	</p>
  1137 	</p>
  1137 
  1138 
  1138 <pre class="example" id="ldpc-ex-membership-full"># The following is an elaborated representation of
  1139 <pre class="example" id="ldpc-ex-membership-full"># The following is an elaborated representation of LDPR
  1139 #   http://example.org/netWorth/nw1/
  1140 #   http://example.org/netWorth/nw1
  1140 <!-- @base is here only so it's easier to paste into validators for checking -->
  1141 <!-- @base is here only so it's easier to paste into validators for checking -->
  1141 # @base &lt;http://example.org/netWorth/nw1/&gt;
  1142 # @base &lt;http://example.org/netWorth/nw1/&gt;.
  1142 @prefix ldp: &lt;http://www.w3.org/ns/ldp#&gt;.
  1143 @prefix ldp: &lt;http://www.w3.org/ns/ldp#&gt;.
  1143 @prefix dcterms: &lt;http://purl.org/dc/terms/&gt;.
  1144 @prefix dcterms: &lt;http://purl.org/dc/terms/&gt;.
  1144 @prefix o: &lt;http://example.org/ontology/&gt;.
  1145 @prefix o: &lt;http://example.org/ontology/&gt;.
  1145 &lt;&gt;
  1146 &lt;&gt;
  1146    a o:NetWorth;
  1147    a o:NetWorth;
  1150       &lt;assetContainer/a2&gt;;
  1151       &lt;assetContainer/a2&gt;;
  1151    o:liability 
  1152    o:liability 
  1152       &lt;liabilityContainer/l1&gt;,
  1153       &lt;liabilityContainer/l1&gt;,
  1153       &lt;liabilityContainer/l2&gt;,
  1154       &lt;liabilityContainer/l2&gt;,
  1154       &lt;liabilityContainer/l3&gt;.
  1155       &lt;liabilityContainer/l3&gt;.
  1155 
  1156 </pre>
  1156 &lt;assetContainer/&gt;
  1157 
       
  1158 <pre class="example" id="ldpc-ex-membership-subj"># The following is an elaborated representation of LDPC
       
  1159 #   http://example.org/netWorth/nw1/assetContainer/
       
  1160 <!-- @base is here only so it's easier to paste into validators for checking -->
       
  1161 # @base &lt;http://example.org/netWorth/nw1/assetContainer/&gt;
       
  1162 @prefix ldp: &lt;http://www.w3.org/ns/ldp#&gt;.
       
  1163 @prefix dcterms: &lt;http://purl.org/dc/terms/&gt;.
       
  1164 @prefix o: &lt;http://example.org/ontology/&gt;.
       
  1165 &lt;&gt;
  1157    a ldp:Container, ldp:DirectContainer;
  1166    a ldp:Container, ldp:DirectContainer;
  1158    dcterms:title "The assets of JohnZSmith";
  1167    dcterms:title "The assets of JohnZSmith";
  1159    ldp:containerResource &lt;&gt;;
  1168    ldp:containerResource &lt;&gt;;
  1160    ldp:containsRelation o:asset;
  1169    ldp:containsRelation o:asset;
  1161    ldp:insertedContentRelation ldp:MemberSubject;
  1170    ldp:insertedContentRelation ldp:MemberSubject;
  1162    ldp:contains &lt;assetContainer/a1&gt;,
  1171    ldp:contains &lt;a1&gt;, &lt;a2&gt;.
  1163       &lt;assetContainer/a2&gt;.
  1172 </pre>
  1164 
  1173 
  1165 &lt;liabilityContainer/&gt;
  1174 <pre class="example" id="ldpc-ex-membership-full-liabcont"># The following is an elaborated representation of LDPC
       
  1175 #   http://example.org/netWorth/nw1/liabilityContainer/
       
  1176 <!-- @base is here only so it's easier to paste into validators for checking -->
       
  1177 # @base &lt;http://example.org/netWorth/nw1/liabilityContainer/&gt;
       
  1178 @prefix ldp: &lt;http://www.w3.org/ns/ldp#&gt;.
       
  1179 @prefix dcterms: &lt;http://purl.org/dc/terms/&gt;.
       
  1180 @prefix o: &lt;http://example.org/ontology/&gt;.
       
  1181 &lt;&gt;
  1166    a ldp:Container, ldp:DirectContainer;
  1182    a ldp:Container, ldp:DirectContainer;
  1167    dcterms:title "The liabilities of JohnZSmith";
  1183    dcterms:title "The liabilities of JohnZSmith";
  1168    ldp:containerResource &lt;&gt;;
  1184    ldp:containerResource &lt;&gt;;
  1169    ldp:containsRelation o:liability;
  1185    ldp:containsRelation o:liability;
  1170    ldp:insertedContentRelation ldp:MemberSubject;
  1186    ldp:insertedContentRelation ldp:MemberSubject;
  1171    ldp:contains
  1187    ldp:contains l1&gt;, l2&gt;, l3&gt;.
  1172       &lt;liabilityContainer/l1&gt;,
       
  1173       &lt;liabilityContainer/l2&gt;,
       
  1174       &lt;liabilityContainer/l3&gt;..
       
  1175 </pre>
  1188 </pre>
  1176 
  1189 
  1177 	<p>The essential structure of the container is
  1190 	<p>The essential structure of the container is
  1178 	the same, but in this example, the consistent membership value (still in the subject position) is not the
  1191 	the same, but in this example, the consistent membership value (still in the subject position) is not the
  1179 	container itself – it is a separate net worth resource. The
  1192 	container itself – it is a separate net worth resource. The
  1193 	 <a title="Linked Data Platform Basic Container">LDP Basic Container</a> is a constrained form of 
  1206 	 <a title="Linked Data Platform Basic Container">LDP Basic Container</a> is a constrained form of 
  1194 	 <a title="Linked Data Platform Direct Container">LDP Direct Container</a> where the 
  1207 	 <a title="Linked Data Platform Direct Container">LDP Direct Container</a> where the 
  1195 	 membership predicate is <code>ldp:contains</code> and the container resource is the container itself.
  1208 	 membership predicate is <code>ldp:contains</code> and the container resource is the container itself.
  1196 	</p>
  1209 	</p>
  1197 
  1210 
  1198 <pre class="example" id="ldpc-ex-membership-subj"># The following is the representation of
  1211 	<p>As seen in the <a href="#ldpc-ex-membership-subj"><code>assetContainer/</code> example</a>, 
  1199 #   http://example.org/netWorth/nw1/assetContainer/
  1212 	clients cannot correctly guess
  1200 <!-- @base is here only so it's easier to paste into validators for checking -->
       
  1201 # @base &lt;http://example.org/netWorth/nw1/assetContainer/&gt;
       
  1202 @prefix ldp: &lt;http://www.w3.org/ns/ldp#&gt;.
       
  1203 @prefix o: &lt;http://example.org/ontology/&gt;.
       
  1204 
       
  1205 &lt;&gt;
       
  1206    a ldp:Container, ldp:DirectContainer;
       
  1207    ldp:containerResource &lt;http://example.org/netWorth/nw1&gt;;
       
  1208    ldp:containsRelation o:asset;
       
  1209    ldp:insertedContentRelation ldp:MemberSubject.
       
  1210 
       
  1211 &lt;http://example.org/netWorth/nw1&gt;
       
  1212    a o:NetWorth;
       
  1213    o:asset &lt;a1&gt;, &lt;a2&gt;.</pre>
       
  1214 
       
  1215 	<p>In this example, clients cannot correctly guess
       
  1216 	at the membership triples, so the example includes this information in
  1213 	at the membership triples, so the example includes this information in
  1217 	triples whose subject is the LDPC resource itself.
  1214 	triples whose subject is the LDPC resource itself.
       
  1215 	</p>
       
  1216 	
       
  1217 	<p>Alternatively, servers may provide the net worth resource and supporting containers in a single response
       
  1218 	representations.  When doing this, a preference would be for RDF formats that support multiple named graphs, one
       
  1219 	named graph for the net worth resource and then two others for asset and liability containers.  This allows for
       
  1220 	the membership triples to be represented with the named graph for the net worth resource, while the containment triples
       
  1221 	would be represented within the liability and asset containers [[rdf11-concepts]].  Generally, the membership triples belong
       
  1222 	to the representation of a LDP-RR and the containment triples belong to the representation of the LDPC.
  1218 	</p>
  1223 	</p>
  1219 	
  1224 	
  1220 	<p>Additionally, we could extend our net worth example to include a container for
  1225 	<p>Additionally, we could extend our net worth example to include a container for
  1221 	advisors (people) that have managed the assets and liabilities.  We have decided
  1226 	advisors (people) that have managed the assets and liabilities.  We have decided
  1222 	to identify these advisors with URLs that contain a fragment (hash) to represent
  1227 	to identify these advisors with URLs that contain a fragment (hash) to represent
  1223 	these real-world resources, not the documents that decribe them.</p>
  1228 	these real-world resources, not the documents that decribe them.</p>
  1224 	
  1229 	
  1225 <pre class="example" id="ldpc-ex-membership-full"># The following is an elaborated representation of
  1230 <pre class="example" id="ldpc-ex-membership-full"># The following is an elaborated representation of
  1226 #   http://example.org/netWorth/nw1/
  1231 #   http://example.org/netWorth/nw1
  1227 # Adding o:advisor but eaving off o:asset and o:liability for brevity.
  1232 # Adding o:advisor but eaving off o:asset and o:liability for brevity.
  1228 <!-- @base is here only so it's easier to paste into validators for checking -->
  1233 <!-- @base is here only so it's easier to paste into validators for checking -->
  1229 # @base &lt;http://example.org/netWorth/nw1/&gt;
  1234 # @base &lt;http://example.org/netWorth/nw1/&gt;
  1230 @prefix ldp: &lt;http://www.w3.org/ns/ldp#&gt;.
  1235 @prefix ldp: &lt;http://www.w3.org/ns/ldp#&gt;.
  1231 @prefix dcterms: &lt;http://purl.org/dc/terms/&gt;.
  1236 @prefix dcterms: &lt;http://purl.org/dc/terms/&gt;.
  1492 			and whose object is the LDPC URI itself.
  1497 			and whose object is the LDPC URI itself.
  1493 		</h2></section>
  1498 		</h2></section>
  1494 	</section><!-- Was 5.2.4 / #ldpc-5_2_4 -->
  1499 	</section><!-- Was 5.2.4 / #ldpc-5_2_4 -->
  1495 	
  1500 	
  1496 	<section id="ldpc-containtriples"><h2 class="normal">An <a title="Linked Data Platform Direct Container">LDP Direct Container</a>
  1501 	<section id="ldpc-containtriples"><h2 class="normal">An <a title="Linked Data Platform Direct Container">LDP Direct Container</a>
  1497 		and <a title="Linked Data Platform Inirect Container">LDP Indirect Container</a> representation MUST contain exactly one triple 
  1502 		and <a title="Linked Data Platform Indirect Container">LDP Indirect Container</a> representation MUST contain exactly one triple 
  1498 		whose subject is the LDPC URI, 
  1503 		whose subject is the LDPC URI, 
  1499 		and whose predicate is either <code>ldp:containsRelation</code> or <code>ldp:containedByRelation</code>. 
  1504 		and whose predicate is either <code>ldp:containsRelation</code> or <code>ldp:containedByRelation</code>. 
  1500 		The object of the triple is constrained by other sections, such as
  1505 		The object of the triple is constrained by other sections, such as
  1501 		<a href="#ldpc-containtriple-relation" class="sectionRef">ldp:containsRelation</a> or 
  1506 		<a href="#ldpc-containtriple-relation" class="sectionRef">ldp:containsRelation</a> or 
  1502 		<a href="#ldpc-containtriple-byrelation" class="sectionRef">ldp:containedByRelation</a>, based on the 
  1507 		<a href="#ldpc-containtriple-byrelation" class="sectionRef">ldp:containedByRelation</a>, based on the 
  1688 		creation of any kind of resource, for example binary resources.  See <a href="#ldpc-post-acceptposthdr">AcceptPost section</a> for 
  1693 		creation of any kind of resource, for example binary resources.  See <a href="#ldpc-post-acceptposthdr">AcceptPost section</a> for 
  1689 		details on how clients can discover whether a LDPC supports this behavior.
  1694 		details on how clients can discover whether a LDPC supports this behavior.
  1690 	</h2></section><!-- Was 5.4.3 / #ldpc-5_4_3 -->
  1695 	</h2></section><!-- Was 5.4.3 / #ldpc-5_4_3 -->
  1691 	
  1696 	
  1692 	<section id="ldpc-post-createrdf"><h2 class="normal"><a title="LDP server">LDP servers</a> that successfully create a resource from a
  1697 	<section id="ldpc-post-createrdf"><h2 class="normal"><a title="LDP server">LDP servers</a> that successfully create a resource from a
  1693 		RDF representation in the request entity body MUST honor the client's requested interaction model(s). 
  1698 		RDF representation in the request entity body MUST honor the client's requested interaction model(s). The created resource
       
  1699 		MUST be an RDF <a href="http://www.w3.org/TR/rdf11-concepts/#dfn-named-graph">named graph</a> [[rdf11-concepts]].
  1694 		If any model cannot be honored, the server MUST fail the request.
  1700 		If any model cannot be honored, the server MUST fail the request.
  1695 	</h2><!-- Was 5.4.4 / #ldpc-5_4_4 -->
  1701 	</h2><!-- Was 5.4.4 / #ldpc-5_4_4 -->
  1696 	<ul>
  1702 	<ul>
  1697 	<li>If the request header <a href="#ldpr-gen-linktypehdr">specifies an LDPR interaction model</a>, then the server MUST create an LDPR.</li>
  1703 	<li>If the request header <a href="#ldpr-gen-linktypehdr">specifies an LDPR interaction model</a>, then the server MUST create an LDPR.</li>
  1698 	<li>If the request header <a href="#ldpc-linktypehdr">specifies an LDPC interaction model</a>, then the server MUST create an LDPC.
  1704 	<li>If the request header <a href="#ldpc-linktypehdr">specifies an LDPC interaction model</a>, then the server MUST create an LDPC.
  1811 		The <a href="#ldpc-HTTP_OPTIONS" class="sectionRef"></a> describes the process by which clients
  1817 		The <a href="#ldpc-HTTP_OPTIONS" class="sectionRef"></a> describes the process by which clients
  1812 		use HTTP <code>OPTIONS</code> to discover whether the server offers such a resource, and if so its URL. 
  1818 		use HTTP <code>OPTIONS</code> to discover whether the server offers such a resource, and if so its URL. 
  1813 	</h2></section><!-- Was 5.5.2 / #ldpc-5_5_2 -->
  1819 	</h2></section><!-- Was 5.5.2 / #ldpc-5_5_2 -->
  1814 	    
  1820 	    
  1815 	<section id="ldpc-put-create"><h2 class="normal"><a title="LDP server">LDP servers</a> that allow member creation via <code>PUT</code> 
  1821 	<section id="ldpc-put-create"><h2 class="normal"><a title="LDP server">LDP servers</a> that allow member creation via <code>PUT</code> 
  1816 		SHOULD NOT re-use URIs.
  1822 		SHOULD NOT re-use URIs.  For RDF representations (LDP-RRs),the created resource
       
  1823 		MUST be an RDF <a href="http://www.w3.org/TR/rdf11-concepts/#dfn-named-graph">named graph</a> [[rdf11-concepts]].
  1817 	</h2></section><!-- Was 5.5.4 / #ldpc-5_5_4 -->
  1824 	</h2></section><!-- Was 5.5.4 / #ldpc-5_5_4 -->
  1818 	
  1825 	
  1819 </section>
  1826 </section>
  1820 
  1827 
  1821 <section id="ldpc-HTTP_DELETE">
  1828 <section id="ldpc-HTTP_DELETE">
  2214 </p>
  2221 </p>
  2215 
  2222 
  2216 <!-- <blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-20130930/">Candidate Recommendation Draft</a></em></blockquote> wah -->
  2223 <!-- <blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-20130930/">Candidate Recommendation Draft</a></em></blockquote> wah -->
  2217 <!-- <blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-20130730/">Last Call Draft</a></em></blockquote> -->
  2224 <!-- <blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-20130730/">Last Call Draft</a></em></blockquote> -->
  2218 <ul>
  2225 <ul>
       
  2226 	<li>2014-02-04 - ACTION-124 LDPR-RR as named graphs  (SS)</li>
  2219 	<li>2014-02-04 - ACTION-120 (complete) Updated LDPC general, GET and POST sections (SS)</li>
  2227 	<li>2014-02-04 - ACTION-120 (complete) Updated LDPC general, GET and POST sections (SS)</li>
  2220 	<li>2014-02-04 - ACTION-120 (Part 3) Added ldp:member (SS)</li>
  2228 	<li>2014-02-04 - ACTION-120 (Part 3) Added ldp:member (SS)</li>
  2221 	<li>2014-02-04 - ACTION-120 (Part 2) Added concepts of containers (basic, direct and indirect) to LDPC intro (SS)</li>
  2229 	<li>2014-02-04 - ACTION-120 (Part 2) Added concepts of containers (basic, direct and indirect) to LDPC intro (SS)</li>
  2222 	<li>2014-01-30 - ACTION-120 (Part 1) Added concepts of containers (basic, direct and indirect) (SS)</li>
  2230 	<li>2014-01-30 - ACTION-120 (Part 1) Added concepts of containers (basic, direct and indirect) (SS)</li>
  2223 	<li>2014-01-30 - ACTION-123 Added concepts of LDP-RDF-Resource and LDP-Binary-Resource (SS)</li>
  2231 	<li>2014-01-30 - ACTION-123 Added concepts of LDP-RDF-Resource and LDP-Binary-Resource (SS)</li>