ISSUE-13 Updated 5.2.3 to say any resource can be in a LDPC and inserted 5.5.3 on rejecting member data on PUT to LDPC
authorsspeiche
Fri, 17 May 2013 16:14:22 -0400
changeset 113 6fd1ba20242d
parent 112 41e5e59c1e26
child 114 1629ff899e0e
ISSUE-13 Updated 5.2.3 to say any resource can be in a LDPC and inserted 5.5.3 on rejecting member data on PUT to LDPC
ldp.html
--- a/ldp.html	Fri May 17 14:34:55 2013 -0400
+++ b/ldp.html	Fri May 17 16:14:22 2013 -0400
@@ -958,7 +958,8 @@
 		membership predicate is also variable and will often be a predicate
 		from the server application vocabulary. If there is no obvious
 		predicate from the server application vocabulary to use, LDPC servers
-		SHOULD use the <code>rdfs:member</code> predicate.
+		SHOULD use the <code>rdfs:member</code> predicate. Member resources can be
+		any kind of resource identified by its URI, LDPR or otherwise.
 	</div>
 	
 	<div class="ldp-issue">
@@ -1001,14 +1002,10 @@
 		or that are from the representations of the members (if they have RDF
 		representations). This allows a LDPC server to provide clients with
 		information about the members without the client having to do a GET
-		on each member individually.  See section <a href="#ldpc-member_data">5.1.1 Container
+		on each member individually.  See section <a href="#ldpc-member_data">5.1.1 Container
 		Member Information</a> for additional details.
+    </div>
 		
-	<div class="ldp-issue">
-	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/13">ISSUE-13</a></div>
-	Include clarifications about LDPC representations that include member triples
-	</div>
-	</div>
 	<div id="ldpc-5_2_7" class="rule">5.2.7 The representation of a LDPC MUST have <code>rdf:type</code>
 		of <code>ldp:Container</code>, but it MAY have additional
 		<code>rdf:type</code>s.
@@ -1213,6 +1210,12 @@
 		MAY exclude server-managed properties such as <code>ldp:membershipSubject</code>, <code>ldp:membershipPredicate</code>
 		and <code>ldp:membershipPredicateInverse</code>.
 	</div>
+	    
+    <div id="ldpc-5_5_3" class="rule">5.5.3 LDPC servers SHOULD NOT allow HTTP PUT requests
+		with member information in the request representation.
+		See section <a href="#ldpc-member_data">5.1.1 Container
+		Member Information</a> for additional details.
+	</div>
 </section>
 
 <section>
@@ -1274,6 +1277,7 @@
 </p>
 <blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-20130307/">Second Public Working Draft</a></em></blockquote>
 <ul>
+	<li>2013-05-17 - ISSUE-13 Updated 5.2.3 to say any resource can be in a LDPC and inserted 5.5.3 on rejecting member data on PUT to LDPC (SS)</li>
 	<li>2013-05-17 - Tweaks to Terminology section for LDPR and LDPC (SS)</li>
 	<li>2013-05-17 - ISSUE-9 Moved section 4.1.7 out of spec to the <a href="http://www.w3.org/2012/ldp/wiki/Deployment_Guide#Servers_should_serve_up_canonical_URLs">deployment guide</a> (SS)</li>
 	<li>2013-05-15 - Updated wording for 5.2.2 from to be more clear (SS)</li>