ldp.html
changeset 129 99dfce0c02d9
parent 126 e4ae46fd5294
child 130 1e1f91d7effc
--- a/ldp.html	Mon Jun 17 17:08:22 2013 +0100
+++ b/ldp.html	Wed Jun 19 04:38:01 2013 -0400
@@ -1175,7 +1175,7 @@
 		whose subject is the sort criterion identifier, 
 		whose predicate is <code>ldp:containerSortPredicate</code> 
 		and whose object is 
-		the predicate whose value is used to order members within the page.
+		the predicate whose value is used to order members between pages (the <dfn>page-ordering values</dfn>).
 		The only predicate data types whose behavior LDP constrains are those defined
 		by SPARQL SELECT’s ORDER BY clause [[!SPARQL-QUERY]].  Other data types
 		can be used, but LDP
@@ -1194,6 +1194,13 @@
 		assigns no meaning to them and interoperability will be limited.
 	</div>
 
+	<div class="ldp-issue-pending">
+	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/14">ISSUE-14</a></div>
+	Include clarifications about ordering in LDPC representations.
+	The ReSpec SPARQL QUERY link is http://www.w3.org/TR/rdf-sparql-query/ , which has highlighted text
+	referring readers to SPARQL 1.1.  Which normative reference do we want?
+	</div>
+
 	<div id="ldpc-5_3_10" class="rule">5.3.10 LDPC page representations 
 		ordered using <code>ldp:containerSortCriteria</code> MAY contain, 
 		in any <code>ldp:containerSortCriterion</code> list entry,
@@ -1201,28 +1208,27 @@
 		whose subject is the sort criterion identifier, 
 		whose predicate is <code>ldp:containerSortCollation</code> 
 		and whose object identifies the collation used.  LDP defines no values for use
-		as the object of this triple.  Any value can be used, but LDP
-		assigns no meaning to them and interoperability will be limited.
+		as the object of this triple.  While it is better for interoperability to use
+		open standardized values, any value can be used.
 		When the <code>ldp:containerSortCollation</code> triple is absent and the 
-		ordering values are strings or simple literals [[!SPARQL-QUERY]], the
+		<a title="page-ordering values">page-ordering values</a> are strings or simple literals [[!SPARQL-QUERY]], the
 		resulting order is as defined by SPARQL SELECT’s ORDER BY clause 
-		[[!SPARQL-QUERY]] using two-argument <code>fn:compare</code>, that is, the implementation's 
-		default collation.
+		[[!SPARQL-QUERY]] using two-argument <code>fn:compare</code>, that is, 
+		it behaves as if <code>http://www.w3.org/2005/xpath-functions/collation/codepoint</code> 
+		was the specified collation.
 		When the <code>ldp:containerSortCollation</code> triple is present and the 
-		ordering values are strings or simple literals [[!SPARQL-QUERY]], the
+		<a title="page-ordering values">page-ordering values</a> are strings or simple literals 
+		[[!SPARQL-QUERY]], the
 		resulting order is as defined by SPARQL SELECT’s ORDER BY clause 
 		[[!SPARQL-QUERY]] using three-argument <code>fn:compare</code>, that is, the 
 		specified collation.
-		When the <code>ldp:containerSortCollation</code> triple is present for other
-		types of comparisons, LDP assigns no meaning to it.
+		When the <code>ldp:containerSortCollation</code> triple SHOULD be omitted for comparisons
+		involving <a title="page-ordering values">page-ordering values</a> for which [[!SPARQL-QUERY]] does not use collations.
 	</div>
 
 	<div class="ldp-issue-pending">
-	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/14">ISSUE-14</a></div>
-	Include clarifications about ordering in LDPC representations.
-	Do we need to say anything about strings in 5.3.8?
-	The ReSpec SPARQL QUERY link is http://www.w3.org/TR/rdf-sparql-query/ , which has highlighted text
-	referring readers to SPARQL 1.1.  Which normative reference do we want?
+	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/63">ISSUE-63</a></div>
+	Need to be able to specify collation with container ordering.  Drafted per 2013-06-18 F2F resolution.
 	</div>
 </section>
 
@@ -1434,6 +1440,7 @@
 <blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-20130701/">Third Public Working Draft</a></em></blockquote>
 -->
 <ul>
+	<li>2013-06-18 - ISSUE-63 End of 5.3 + example rewritten for 2013-06-18 F2F resolution (JA)</li>
 	<li>2013-06-15 - ISSUE-14 End of 5.3 + example rewritten for ascending/descending sorts with optional collation (JA)</li>
 	<li>2013-06-13 - ISSUE-54 New 5.4.8.1 to set base URI on create for relative URI resolution (SS)</li>
 	<li>2013-06-10 - ISSUE-74 4.4.2 require 428 Condition Required status code when appropriate; SS adding 6585 to biblio (JA)</li>