Comments received from David Woods: abstract, paging informative (part 1)
authorsspeiche
Mon, 04 Mar 2013 10:25:53 -0500
changeset 78 539b6b098ee8
parent 77 724403b40995
child 79 fc72f1aea311
Comments received from David Woods: abstract, paging informative (part 1)
ldp.html
--- a/ldp.html	Mon Mar 04 08:40:31 2013 -0500
+++ b/ldp.html	Mon Mar 04 10:25:53 2013 -0500
@@ -110,7 +110,8 @@
 <body>
 <section id='abstract'>
 A set of best practices and simple approach for a read-write Linked Data architecture, based on
-HTTP access to web resources that describe their state using <abbr title="Resource Description Framework">RDF</abbr>.
+HTTP access to web resources that describe their state using the <abbr title="Resource Description Framework">RDF</abbr>
+data model.
 </section>
  
 <section>
@@ -741,7 +742,7 @@
 		Alternatively, a server may recognize that a container that has been
 		requested is too big to return in a single message.</p>
 	<p>
-		To address this problem, LDPCs may support a technique called Paging.  Paging can be achieved with a
+		To address this problem, LDPCs should support a technique called Paging.  Paging can be achieved with a
 		simple RDF pattern. For each container resource, <code>&lt;containerURL&gt;</code>, we define a new
 		resource <code>&lt;containerURL&gt;?firstPage</code>.
 		The triples in the representation of <code>&lt;containerURL&gt;?firstPage</code>
@@ -1214,6 +1215,7 @@
 <h1>Change History</h1>
 <blockquote><em>First Public Working Draft</em></blockquote>
 <ul>
+	<li>2013-03-04 - Comments received from David Woods: abstract, paging informative (part 1)  (SS)</li>
 	<li>2013-03-04 - ISSUE-36 - Added informative text regarding creationg of containers in 5.4.4 (SS)</li>
  	<li>2013-03-04 - ISSUE-12 - Added section 4.7.3 not to allow PATCH for create (SS)</li>
 	<li>2013-03-03 - Adjustments to language about different container behavior (SS)</li>
@@ -1291,6 +1293,10 @@
 	</li>
 	<li>5.4.5: in light of the existence of server-managed properties, why not allow response body from create?
 	</li>
+	<li>Per David Woods, 'Sections 4.4.1, 4.5.1, 4.7.1, 5.4.1, 5.6.1 and 5.8.1 all relate to 
+ allowable write operations.  I suggest adding the statement, "An LDPR server
+ MAY require a user to be authenticated and authorized before this action is 
+ permitted." to each of those sections.', consider place to edit this in.</li>
 </ul>
 	<div class="ldp-issue">
 	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/37">ISSUE-37</a></div>