changeset 554 5a4fe2b38a2a
parent 553 3d27d1a1d553
child 558 63b736cb76bf
--- a/ldp.html	Tue Apr 15 15:47:01 2014 -0400
+++ b/ldp.html	Tue Apr 15 16:25:52 2014 -0400
@@ -400,7 +400,7 @@
 	These triples <strong>always</strong> have the form: <var>( LDPC URI, ldp:contains , document-URI )</var>.
-	<dt><dfn>Empty-container triples</dfn></dt>
+	<dt><dfn>Minimal-container triples</dfn></dt>
 	The portion of an LDPC's state that would be present when the container is empty.  Currently, this definition
 	is equivalent to all the LDPC's triples minus its containment triples and minus its membership
@@ -1120,7 +1120,7 @@
 	<table style="border: 1px solid gray" id="ldpc-mbrcntdiff">
-		<thead><tr><th rowspan="2">Completed Request</th><th colspan="2">Effects</th></tr>
+		<thead><tr><th rowspan="2">Completed Request</th><th style="background:#FFFFFF;" colspan="2">Effects</th></tr>
 		       <tr class="oddrow"><th>Membership</th><th>Containment</th></tr></thead>
 		<tr><td>LDPR created in LDP-BC</td><td>New triple: (LDPC, ldp:contains, LDPR)</td><td>Same</td></tr>
 		<tr><td>LDPR created in LDP-DC</td><td>New triple links LDP-RS to created LDPR. LDP-RS URI may be same as LDP-DC</td>
@@ -1133,14 +1133,14 @@
 			(LDPC, ldp:contains, LDPR) and contained LDPRs may be removed</td></tr>
-<section id="ldpc-get_empty-container_props"><h2 class="normal">Retrieving Only Empty-Container Triples
-	</h2><!-- Was 5.1.1 / #ldpc-get_empty-container_props -->
+<section id="ldpc-get_minimal-container_props"><h2 class="normal">Retrieving Only Minimal-Container Triples
+	</h2><!-- Was 5.1.1 / #ldpc-get_minimal-container_props -->
 	<p>The representation of a container
 		that has many members will be large. There are several important
 		cases where clients need to access only the subset of the container's properties 
 		that are unrelated to member resources and unrelated to contained documents, for
 		example to determine the membership triple pattern and membership predicate of an 
-		LDP-DC.  LDP calls these <a title="Empty-container triples">empty-container triples</a>,
+		LDP-DC.  LDP calls these <a title="Minimal-container triples">minimal-container triples</a>,
 		because they are what remains when the container has zero members and zero contained resources.
 		Since retrieving the whole container representation to
 		get this information may be onerous for clients and cause unnecessary
@@ -1152,19 +1152,19 @@
 		(see <a href="#prefer-parameters" class="sectionRef"></a> for details).
 	<p>The example listed here only shows
-		a simple case where few empty-container triples are
+		a simple case where few minimal-container triples are
 		retrieved. In real world situations more complex cases are likely, such as those that add other predicates to
 		containers, for example providing validation information and
 		associating SPARQL endpoints. [[sparql11-query]]</p>
-		Here is an example requesting the empty-container triples of a
+		Here is an example requesting the minimal-container triples of a
 		container identified by the URL <code>http://example.org/container1/</code>.
-<p id="ldpc-ex-empty-container">Request:</p>
+<p id="ldpc-ex-minimal-container">Request:</p>
 <pre class="example">GET /container1 HTTP/1.1
 Host: example.org
 Accept: text/turtle; charset=UTF-8
-Prefer: return=representation; include="http://www.w3.org/ns/ldp#PreferEmptyContainer"
+Prefer: return=representation; include="http://www.w3.org/ns/ldp#PreferMinimalContainer"
 <pre class="example">HTTP/1.1 200 OK
@@ -1189,7 +1189,7 @@
 		LDP recommends using PATCH to update these properties, if necessary.  It provides no facility
 		for updating them via PUT without replacing the entire container's state.
-	</section><!-- ldpc-get_empty-container_props -->
+	</section><!-- ldpc-get_minimal-container_props -->
@@ -1458,7 +1458,7 @@
 	<section id="ldpc-patch-req"><h2 class="normal">
 		<a title="LDP server">LDP servers</a> are RECOMMENDED 
 		to support HTTP <code>PATCH</code> as the preferred method for 
-		updating a LDPC's <a title="Empty-container triples">empty-container triples</a>.
+		updating a LDPC's <a title="Minimal-container triples">minimal-container triples</a>.
 	</h2></section><!-- Was 5.8.1 / #ldpc-5_8_1 -->
@@ -1939,9 +1939,9 @@
 		<td> <code>http://www.w3.org/ns/ldp#PreferMembership</code> </td>
-		<td> <a title="Empty-container triples">Empty-container triples</a>
+		<td> <a title="Minimal-container triples">Minimal-container triples</a>
-		<td> <code>http://www.w3.org/ns/ldp#PreferEmptyContainer</code> </td>
+		<td> <code>http://www.w3.org/ns/ldp#PreferMinimalContainer</code> </td>
@@ -1992,10 +1992,10 @@
 	   o:value 300000 .
-	<p id="prefer-examples-direct-empty-container-only1">
+	<p id="prefer-examples-direct-minimal-container-only1">
 	Clients interested only in information about the container 
 	(for example, which membership predicate it uses) might use this hint on a <code>GET</code> request:
-	<code>Prefer: return=representation; include="http://www.w3.org/ns/ldp#PreferEmptyContainer"</code>
+	<code>Prefer: return=representation; include="http://www.w3.org/ns/ldp#PreferMinimalContainer"</code>
 	A server that honors this hint would return a following response containing the HTTP header 
@@ -2020,13 +2020,13 @@
 	   ldp:insertedContentRelation ldp:MemberSubject.
-	<p id="prefer-examples-direct-empty-container-only2">
+	<p id="prefer-examples-direct-minimal-container-only2">
 	Clients interested only in information about the container 
 	(same as before) might use this hint instead:
 	<code>Prefer: return=representation; omit="http://www.w3.org/ns/ldp#PreferMembership http://www.w3.org/ns/ldp#PreferContainment"</code>.  Note: <strong>Treating the two as equivalent is not recommended.</strong> While today this 
 	<code>omit</code> parameter value is equivalent to the preceding <code>include</code> parameter value, 
 	they may not be equivalent in the future 
-	due to the definition of <a title="Empty-container triples">empty-container triples</a>.
+	due to the definition of <a title="Minimal-container triples">minimal-container triples</a>.
 	Clients should preferentially use the <code>include</code> parameter, as it more precisely communicates their needs.
@@ -2054,7 +2054,7 @@
 	<p id="prefer-examples-direct-membershiponly">
 	Clients interested only in information about the container 
 	(for example, which membership predicate it uses) and its membership might use this hint on a <code>GET</code> request:
-	<code>Prefer: return=representation; include="http://www.w3.org/ns/ldp#PreferMembership http://www.w3.org/ns/ldp#PreferEmptyContainer"</code>
+	<code>Prefer: return=representation; include="http://www.w3.org/ns/ldp#PreferMembership http://www.w3.org/ns/ldp#PreferMinimalContainer"</code>
 	A server that honors this hint would return