--- a/ldp.html	Wed Jan 22 16:03:35 2014 -0500
+++ b/ldp.html	Wed Jan 22 16:54:32 2014 -0500
@@ -452,12 +452,8 @@
 
 <section id="ldpclient">
 <h1>Linked Data Platform Clients</h1>
-<div class="ldp-issue-open">
-
-<p>All of the following rules are just copied here, without change; still need to be removed from original section.
-Should consider making this section come before the server sections; doing so would cause mass-renumbering however.
+<p>All of the following are conformance rules for <a title="LDP server">LDP Clients</a>.
 </p>
-</div>
 <section><h2>General</h2>
 	<section id="ldp-cli-multitype"><h2 class="normal">In the absence of special knowledge of the application or domain, 
 		<a title="LDP client">LDP clients</a> MUST assume that any LDPR can have multiple values for <code>rdf:type</code>.
@@ -640,15 +636,7 @@
 	<section id="ldpr-get-turtle"><h2 class="normal"><a title="LDP server">LDP servers</a> MUST provide a <code>text/turtle</code>
 		representation of the requested LDPR [[!TURTLE]].
 	</h2></section><!-- Was 4.3.3 / #ldpr-4_3_3 -->
-	
-	<section id="ldpr-get-multitypes"><h2 class="normal">In the absence of special knowledge of the application or domain, 
-		<a title="LDP client">LDP clients</a> MUST assume that any LDPR can have multiple values for <code>rdf:type</code>.
-	</h2></section><!-- Was 4.3.5 / #ldpr-4_3_5 -->
 
-	<section id="ldpr-get-typeschange"><h2 class="normal">In the absence of special knowledge of the application or domain, 
-		<a title="LDP client">LDP clients</a> MUST assume that the <code>rdf:type</code> values
-		of a given LDPR can change over time.
-	</h2></section><!-- Was 4.3.6 / #ldpr-4_3_6 -->
 </section>
 
 <section id="ldpr-HTTP_POST">
@@ -713,16 +701,6 @@
 		(Precondition Required) when the absence of a precondition is the only reason for rejecting the request [[!RFC6585]].
 	</h2></section><!-- Was 4.5.2 / #ldpr-4_5_2 -->
 	
-	<section id="ldpr-put-openpreds"><h2 class="normal"><a title="LDP client">LDP clients</a> SHOULD always assume that the set of predicates for a
-		resource of a particular type at an arbitrary server is open, in the
-		sense that different resources of the same type may not all have the
-		same set of predicates in their triples, and the set of predicates that
-		are used in the state of any one resource is not limited to any pre-defined
-		set.
-		<!-- TODO: This seems to fly in the face of systems that are closed, which we have many, which have a way to discover via some 
-		out of bands means. -->
-	</h2></section><!-- Was 4.5.3 / #ldpr-4_5_3 -->
-	
 	<section id="ldpr-put-failed"><h2 class="normal">
 		If an otherwise valid HTTP <code>PUT</code> request is received that contains triples the server 
 		chooses not to persist, e.g. unknown content,
@@ -735,13 +713,6 @@
 		<!-- TODO: MUST respond with Link rel='describedBy' as in 4.2.13 -->
 	</h2></section><!-- Was 4.5.4 / #ldpr-4_5_4 -->
 	
-	<section id="ldpr-put-perserveall"><h2 class="normal">An <a title="LDP client">LDP client</a> MUST preserve all triples retrieved using HTTP <code>GET</code> that
-		it doesn’t change whether it understands the predicates or not, when
-		its intent is to perform an update using HTTP <code>PUT</code>.  The use of HTTP
-		<code>PATCH</code> instead of HTTP <code>PUT</code> for update avoids this burden for clients
-		[[RFC5789]].
-	</h2></section><!-- Was 4.5.5 / #ldpr-4_5_5 -->
-	
 	<section id="ldpr-put-create"><h2 class="normal"><a title="LDP server">LDP servers</a> MAY choose to allow the creation of new resources using HTTP <code>PUT</code>.
 	</h2></section><!-- Was 4.5.6 / #ldpr-4_5_6 -->
 	
@@ -2104,6 +2075,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> -->
 <ul>
+	<li>2014-01-21 - Removed redudant reqs that have been moved to <a href="#ldpclient"></a> (SS)</li>
 	<li>2014-01-21 - Fixed formating with &gt;h2 formatting (SS)</li>
 	<li>2014-01-21 - Put reference to <a href="#base-specs">base-specs</a> into intro section (SS)</li>
 	<li>2014-01-17 - First attempt at correcting section ordering and anchors (SS)</li>