changeset 505 7c9fc6642481
parent 504 065e49b91d0b
child 506 c828dbebaebb
--- a/ldp.html	Mon Feb 24 09:13:53 2014 -0500
+++ b/ldp.html	Thu Feb 27 16:00:38 2014 -0500
@@ -1,15 +1,13 @@
 <!DOCTYPE html>
 	TODO: Search for them within this document.
 	TODO: Once companion documents (best practices, primer) have URLs, link to them.  Search on "companion".
-	TODO: Once the membership* names stabilize, take a pass through for "membership consistent value", membership-constant-URI
-     and see if there is a friendlier 	way to phrase it.
     TODO: Consider how to not have to explicitly list parent classes.
     TODO: Improve LDPC intro by explaining simply that LDP-DC restricts LDPC and LDP-BC restricts LDP-DC.
 	TODO: Add new "discovery of server capabilities" non-norm section
     TODO: Missing namespace definition clause?
     TODO: 6.2.2 -- consider rules LDP-DC MUST BE a LDPC, ... to deal with inferencing
+    TODO: Consider folding LDP Clients section, feels a bit out of place
@@ -1396,7 +1394,7 @@
 	201-Created and URI indicated by <code>Location</code> response header), <a title="LDP server">LDP servers</a> MAY create an associated 
 	<a title="Linked Data Platform RDF Source">LDP-RS</a>
 	to contain data about the newly created LDP-NR.  If an LDPC server creates this associated <a title="Linked Data Platform RDF Source">LDP-RS</a> it MUST indicate
-	its location on the HTTP response using the HTTP <code>Link</code> response header with link relation <code>describedBy</code>
+	its location on the HTTP response using the HTTP <code>Link</code> response header with link relation <code>describedby</code>
 	and <code>href</code> to be the URI of the associated LDP-RS resource [[!RFC5988]].
 	</h2></section><!-- Was 5.4.12 / #ldpc-5_4_12 -->
@@ -1536,7 +1534,7 @@
 	to contain data about the non-LDPR (see <a href="#ldpc-post-createbinlinkmetahdr">LDPC POST section</a>).  
 	For LDP-NRs that have this associated LDP-RS, an LDPC server MUST provide an HTTP <code>Link</code>
 	header whose target URI is the associated LDP-RS, and whose link relation type is 
-	<code>describedBy</code> [[!RFC5988]].
+	<code>describedby</code> [[!RFC5988]].
 	</h2></section><!-- Was 5.9.2 / #ldpc-5_9_2 -->
 </section> <!-- h2 -->
@@ -1772,7 +1770,6 @@
 		fragment component [[!RFC3986]].
-		</h2>
 	<section id="prefer-omit"><h2 class="normal">
@@ -1787,7 +1784,6 @@
 		Where <code>WSP</code> and <code>ldp-uri-list</code> are defined as above for <a href="#prefer-include">include</a>.
-		</h2>
 	<section id="prefer-conflicts"><h2 class="normal">
@@ -2082,7 +2078,7 @@
 <!-- <blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-20130930/">Candidate Recommendation Draft</a></em></blockquote> wah -->
 <!-- <blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-20130730/">Last Call Draft</a></em></blockquote> -->
-	<li>2014-02-24 - Corrected rel=meta to be rel=describedBy (SS) </li>
+	<li>2014-02-24 - Corrected rel=meta to be rel=describedby (SS) </li>
 	<li>2014-02-24 - Adjusted term membership triples and membership predicate (SS) </li>
 	<li>2014-02-24 - Removed 6.3.1 LDPC GET requirement and put in general clause (SS) </li>
 	<li>2014-02-20 - Changed LDPC SHOULD NOT put (6.5.1) to be about containment (SS) </li>