--- a/ldp-paging.html	Mon Aug 04 11:54:17 2014 -0400
+++ b/ldp-paging.html	Mon Aug 04 14:17:12 2014 -0400
@@ -1644,7 +1644,7 @@
 		for server ordering of members in containers, because any client can
 		order the members in any way it chooses based on the value of any
 		available property of the members. In the example below, the value of
-		the <code>o:value</code> predicate is present for each
+		the <code>o:marketValue</code> predicate is present for each
 		member, so the client can easily order the members according to the
 		value of that property. 
 	</p>
@@ -1719,13 +1719,13 @@
 
 &lt;a1&gt;
    a o:Stock;
-   o:value 100.00 .
+   o:marketValue 100.00 .
 &lt;a2&gt;
    a o:Cash;
-   o:value 505.00 .
+   o:marketValue 505.00 .
 &lt;a3&gt;
    a o:RealEstateHolding;
-   o:value 100.00 .
+   o:marketValue 100.00 .
 </pre>
 	<p>
 		The client knows that LDP Paging was not used to form the response, because the HTTP status code is <code>200 OK</code>
@@ -1773,23 +1773,23 @@
 
 &lt;a1&gt;
    a o:Stock;
-   o:value 100.00 .
+   o:marketValue 100.00 .
    
 # The remainder of the content describes the sort order.
 # Note that the new base URI here matches the target URI of the pageSortCriteria Link header above.
 
 @base &lt;http://example.org/netWorth/nw1/assetContainer/pageSortOrder/&gt; .
 @prefix rdf: &lt;http://www.w3.org/1999/02/22-rdf-syntax-ns#&gt;.
-<!-- (#Sort-o.value-Ascending) does not work, because the subject uri would be a blank node -->
+<!-- (#Sort-o.marketValue-Ascending) does not work, because the subject uri would be a blank node -->
 &lt;&gt; 
    a rdf:List;
-   rdf:first &lt;#Sort-o.value-Ascending&gt; ; 
+   rdf:first &lt;#Sort-o.marketValue-Ascending&gt; ; 
    rdf:rest rdf:nil .
 
-&lt;#Sort-o.value-Ascending&gt;
+&lt;#Sort-o.marketValue-Ascending&gt;
    a ldp:pageSortCriterion;
    ldp:pageSortOrder ldp:Ascending;
-   ldp:pageSortPredicate o:value.
+   ldp:pageSortPredicate o:marketValue.
 </pre>
 	
 	<p>
@@ -1811,9 +1811,9 @@
 	</li>
 	<li>
 		The contents of the page sort criteria resource
-		asserts that the <code>o:value</code> predicate will be used 
+		asserts that the <code>o:marketValue</code> predicate will be used 
 		to assign sets of members to pages in ascending order.  
-		The server is telling the client that the values of <code>o:value</code> of all assets
+		The server is telling the client that the values of <code>o:marketValue</code> of all assets
 		on the first page are no lower than the values on subsequent pages.
 		Since only one such value happens to fall on the first page, this is trivially satisfied.
 	</li>
@@ -1846,10 +1846,10 @@
 
 &lt;a2&gt;
    a o:Cash;
-   o:value 505.00 .
+   o:marketValue 505.00 .
 &lt;a3&gt;
    a o:RealEstateHolding;
-   o:value 100.00 .
+   o:marketValue 100.00 .
 </pre>
 	
 	<ul>
@@ -1865,7 +1865,7 @@
 		to retrieve the sort criteria.
 	</li>
 	<li>
-		As the example shows, the values of <code>o:value</code> all assets
+		As the example shows, the values of <code>o:marketValue</code> all assets
 		on the second page are greater than or equal to the values on earlier pages.
 		<em>The values within this page are not ordered according to the 
 		sort criterion</em>, illustrating that this criterion applies only to the 
@@ -2164,6 +2164,7 @@
 <!-- <blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-paging-20140930/">Candidate Recommendation Draft</a></em></blockquote> wah -->
 <!-- <blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-paging-20140730/">Last Call Draft</a></em></blockquote> -->
 <ul>
+	<li>2014-08-04 - Fuss with SortValueAscending value for Sandro (JA) </li>
 	<li>2014-08-04 - Incorporating resolutions from today's WG meeting (JA) </li>
 	<li>2014-07-30 - Rewording based on SS's 7/17 email comments (JA) </li>
 	<li>2014-07-29 - Fully specify 303+location's URI (JA) </li>

--- a/ldp.html	Mon Aug 04 11:54:17 2014 -0400
+++ b/ldp.html	Mon Aug 04 14:17:12 2014 -0400
@@ -2271,13 +2271,13 @@
 
 <a1>
    a o:Stock;
-   o:value 100.00 .
+   o:marketValue 100.00 .
 <a2>
    a o:Cash;
-   o:value 50.00 .
+   o:marketValue 50.00 .
 <a3>
    a o:RealEstateHolding;
-   o:value 300000 .</pre>
+   o:marketValue 300000 .</pre>
 
 	<p id="prefer-examples-direct-minimal-container-only1">
 	Clients interested only in information about the container 
@@ -2576,6 +2576,11 @@
 
 <blockquote><em><a href="http://www.w3.org/TR/2014/CR-ldp-20140619">Candidate Recommendation Draft</a></em></blockquote> -->
 <ul>
+	<li>2014-08-04 - Fuss with o:value in examples for Sandro to remain consistent with Paging spec (JA) </li>
+</ul>
+
+<blockquote><em><a href="http://www.w3.org/TR/2014/CR-ldp-20140619">Candidate Recommendation Draft</a></em></blockquote> -->
+<ul>
 	<li>2014-07-28 - Clarified syntax used by clients to request specific interaction model (JA) </li>
 	<li>2014-06-16 - Updated examples in Prefer section to be in request/response format (SS) </li>
 	<li>2014-06-16 - Updated examples in container sections to be in request/response format (SS) </li>