ldp.html
changeset 427 9680ab51d5fa
parent 419 afe7bcda2e56
child 428 fff13d6627df
--- a/ldp.html	Sun Nov 24 21:05:33 2013 -0600
+++ b/ldp.html	Wed Nov 27 15:04:53 2013 -0500
@@ -1352,7 +1352,10 @@
 			and server to determine the appropriate predicate to indicate the
 			resource’s order within a page, and up to the client receiving this 
 			representation to use that order in whatever way is appropriate, for 
-			example to sort the data prior to presentation on a user interface.
+			example to sort the data prior to presentation on a user interface. Also
+			as it is possible for a container to have as its members other containers,
+			the ordering approach doesn't change as containers themselves are LDPRs and the
+			properties from the domain model can be leveraged for the sort criteria.
 		</p>
 </section>
 
@@ -2171,6 +2174,7 @@
 
 <!-- <blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-20130930/">Candidate Recommendation Draft</a></em></blockquote> wah -->
 <ul>
+	<li>2013-11-27 - ACTION-100 Added informative note to Ordering section that containers can be nested (SS)</li>
 	<li>2013-11-18 - Various editorial and validation fixes (SS)</li>
     <li>2013-11-12 - Clean up some remnants of inlining (JA)</li>
     <li>2013-11-12 - Clean up some overly specific language (implications that POST is the only way to create members, etc) (JA)</li>