ldp.html
changeset 74 30624f0a7534
parent 73 c19607773ae2
child 75 6b1114af16c2
--- a/ldp.html	Tue Feb 26 08:10:39 2013 -0500
+++ b/ldp.html	Sat Mar 02 16:51:18 2013 -0500
@@ -590,7 +590,7 @@
 		container (the fact that it is a container and a brief title):</p>
 
 <pre class="example"># The following is the representation of
-#    http://example.org/container1
+#    http://example.org/container1/
 @prefix dcterms: &lt;http://purl.org/dc/terms/&gt;.
 @prefix rdfs: &lt;http://www.w3.org/2000/01/rdf-schema#&gt;.
 @prefix ldp: &lt;http://www.w3.org/ns/ldp#&gt;.
@@ -613,7 +613,7 @@
 
 <pre class="example" id="ldpc-ex-membership-subj">
 # The following is the representation of
-#   http://example.org/netWorth/nw1/assetContainer
+#   http://example.org/netWorth/nw1/assetContainer/
 @prefix ldp: &lt;http://www.w3.org/ns/ldp#&gt;.
 @prefix o: &lt;http://example.org/ontology/&gt;.
 
@@ -637,7 +637,7 @@
 		the new asset directly there. That would be a fine design if <code>http://example.org/netWorth/nw1</code> had only assets, but if it has separate
 		predicates for assets and liabilities, that design will not work
 		because it is unspecified to which predicate the POST should add a
-		membership triple. Having separate <code>http://example.org/netWorth/nw1/assetContainer</code> and <code>http://example.org/netWorth/nw1/liabilityContainer</code> container resources allows both assets and
+		membership triple. Having separate <code>http://example.org/netWorth/nw1/assetContainer/</code> and <code>http://example.org/netWorth/nw1/liabilityContainer/</code> container resources allows both assets and
 		liabilities to be created.
 	</p>
 	<p>In this example, clients cannot simply guess
@@ -664,7 +664,7 @@
 		(assets) in the representation:</p>
 
 <pre class="example"># The following is the representation of
-#	 http://example.org/netWorth/nw1/assetContainer
+#	 http://example.org/netWorth/nw1/assetContainer/
 @prefix dcterms: &lt;http://purl.org/dc/terms/&gt;.
 @prefix ldp:      &lt;http://www.w3.org/ns/ldp#&gt;.
 @prefix o:       &lt;http://example.org/ontology/&gt;.
@@ -708,7 +708,7 @@
 		associating SPARQL endpoints. [[SPARQL-QUERY]]</p>
 	<p>
 		Here is an example requesting the non-member properties of a
-		container identified by the URL <code>http://example.org/container1</code>
+		container identified by the URL <code>http://example.org/container1/</code>
 		and adding the query string <code>?non-member-properties</code> :
 	</p>
 <p>Request:</p>
@@ -726,7 +726,7 @@
 @prefix dcterms: &lt;http://purl.org/dc/terms/&gt;.
 @prefix ldp: &lt;http://www.w3.org/ns/ldp#&gt;.
 
-&lt;http://example.org/container1&gt;
+&lt;http://example.org/container1/&gt;
    a ldp:Container;
    dcterms:title "A Linked Data Platform Container of Acme Resources";
    ldp:membershipPredicate rdfs:member;
@@ -760,25 +760,25 @@
 	<p>
 		Continuing on from the member information from the JohnZSmith net
 		worth example, we’ll split the response across two pages.  The client
-		requests the first page as <code>http://example.org/netWorth/nw1/assetContainer?firstPage</code>:
+		requests the first page as <code>http://example.org/netWorth/nw1/assetContainer/?firstPage</code>:
 	</p>
 <pre class="example"># The following is the representation of
-#    http://example.org/netWorth/nw1/assetContainer?firstPage
+#    http://example.org/netWorth/nw1/assetContainer/?firstPage
 @prefix rdf: &lt;http://www.w3.org/1999/02/22-rdf-syntax-ns#&gt;.
 @prefix dcterms: &lt;http://purl.org/dc/terms/&gt;.
 @prefix ldp: &lt;http://www.w3.org/ns/ldp#&gt;.
 @prefix o: &lt;http://example.org/ontology/&gt;.
 
-&lt;http://example.org/netWorth/nw1/assetContainer&gt;
+&lt;http://example.org/netWorth/nw1/assetContainer/&gt;
    a ldp:Container;
    dcterms:title "The assets of JohnZSmith";
    ldp:membershipSubject &lt;http://example.org/netWorth/nw1&gt;;
    ldp:membershipPredicate o:asset.
 
-&lt;http://example.org/netWorth/nw1/assetContainer?firstPage&gt;
+&lt;http://example.org/netWorth/nw1/assetContainer/?firstPage&gt;
    a ldp:Page;
-   ldp:pageOf &lt;http://example.org/netWorth/nw1/assetContainer&gt;;
-   ldp:nextPage &lt;http://example.org/netWorth/nw1/assetContainer?p=2&gt;.
+   ldp:pageOf &lt;http://example.org/netWorth/nw1/assetContainer/&gt;;
+   ldp:nextPage &lt;http://example.org/netWorth/nw1/assetContainer/?p=2&gt;.
  
 &lt;http://example.org/netWorth/nw1&gt;
     a o:NetWorth;
@@ -802,21 +802,21 @@
 	</p>
 
 <pre class="example"># The following is the representation of
-#  http://example.org/netWorth/nw1/assetContainer?p=2
+#  http://example.org/netWorth/nw1/assetContainer/?p=2
 @prefix rdf: &lt;http://www.w3.org/1999/02/22-rdf-syntax-ns#&gt;.
 @prefix dcterms: &lt;http://purl.org/dc/terms/&gt;.
 @prefix ldp: &lt;http://www.w3.org/ns/ldp#&gt;.
 @prefix o: &lt;http://example.org/ontology/&gt;.
 
-&lt;http://example.org/netWorth/nw1/assetContainer&gt;
+&lt;http://example.org/netWorth/nw1/assetContainer/&gt;
    a ldp:Container;
    dcterms:title "The assets of JohnZSmith";
    ldp:membershipSubject &lt;http://example.org/netWorth/nw1&gt;;
    ldp:membershipPredicate o:asset.
 
-&lt;http://example.org/netWorth/nw1/assetContainer?p=2&gt;
+&lt;http://example.org/netWorth/nw1/assetContainer/?p=2&gt;
    a ldp:Page;
-   ldp:pageOf &lt;http://example.org/netWorth/nw1/assetContainer&gt;;
+   ldp:pageOf &lt;http://example.org/netWorth/nw1/assetContainer/&gt;;
    ldp:nextPage rdf:nil.
 
 &lt;http://example.org/netWorth/nw1&gt;
@@ -868,7 +868,7 @@
 	<p>Here is an example container described
 		previously, with representation for ordering of the assets:</p>
 <pre class="example"># The following is the ordered representation of
-#   http://example.org/netWorth/nw1/assetContainer
+#   http://example.org/netWorth/nw1/assetContainer/
 @prefix dcterms: &lt;http://purl.org/dc/terms/&gt;.
 @prefix ldp: &lt;http://www.w3.org/ns/ldp#&gt;.
 @prefix o: &lt;http://example.org/ontology/&gt;.
@@ -1229,6 +1229,7 @@
 <h1>Change History</h1>
 <blockquote><em>First Public Working Draft</em></blockquote>
 <ul>
+	<li>2013-03-02 - Adding trailing '/' on Container URLs to help with readability based on WG suggestion (SS)</li>
 	<li>2013-02-26 - Updated Acknowledgements section (SS)</li>
 	<li>2013-02-25 - ISSUE-29 - Use relative URIs in examples (SS)</li>
 	<li>2013-02-25 - ISSUE-31 - Added a more complete conformance section, motived by SPARQL 1.1 (SS)</li>