--- a/ldp.html	Wed Sep 10 08:16:35 2014 -0400
+++ b/ldp.html	Wed Sep 10 11:05:23 2014 -0400
@@ -1070,8 +1070,8 @@
 	a  predicate from an application's domain model as the membership predicate. Let's
 	start with a pre-existing domain resource for a person's net worth, as illustrated below:</p>
 			
-<em>Request</em> to <code>http://example.org/netWorth/nw1</code>:
-<pre class="example" id="ldpc-ex-membership-partial-req">GET /netWorth/nw1 HTTP/1.1
+<em>Request</em> to <code>http://example.org/netWorth/nw1/</code>:
+<pre class="example" id="ldpc-ex-membership-partial-req">GET /netWorth/nw1/ HTTP/1.1
 Host: example.org
 Accept: text/turtle</pre>
 
@@ -1084,11 +1084,11 @@
       &lt;http://www.w3.org/ns/ldp#Resource&gt;; rel="type"
 Allow: GET,OPTIONS,HEAD,PUT,DELETE
 Transfer-Encoding: chunked
-<!-- @base <http://example.org/netWorth/nw1>. -->
+<!-- @base <http://example.org/netWorth/nw1/>. -->
 @prefix ldp: &lt;http://www.w3.org/ns/ldp#&gt;.
 @prefix o: &lt;http://example.org/ontology#&gt;.
 
-&lt;http://example.org/netWorth/nw1&gt;
+&lt;http://example.org/netWorth/nw1/&gt;
    a o:NetWorth;
    o:netWorthOf &lt;http://example.org/users/JohnZSmith&gt;;
    o:asset 
@@ -1124,8 +1124,8 @@
 	the LDP-RS example from before:
 	</p>
 	
-<em>Request</em> to <code>http://example.org/netWorth/nw1</code>:
-<pre class="example" id="ldpc-ex-membership-full-req">GET /netWorth/nw1 HTTP/1.1
+<em>Request</em> to <code>http://example.org/netWorth/nw1/</code>:
+<pre class="example" id="ldpc-ex-membership-full-req">GET /netWorth/nw1/ HTTP/1.1
 Host: example.org
 Accept: text/turtle</pre>
 
@@ -1138,11 +1138,11 @@
       &lt;http://www.w3.org/ns/ldp#Resource&gt;; rel="type"
 Allow: GET,OPTIONS,HEAD,PUT,DELETE
 Transfer-Encoding: chunked
-<!-- @base <http://example.org/netWorth/nw1>. -->
+<!-- @base <http://example.org/netWorth/nw1/>. -->
 @prefix ldp: &lt;http://www.w3.org/ns/ldp#&gt;.
 @prefix o: &lt;http://example.org/ontology#&gt;.
 
-&lt;http://example.org/netWorth/nw1&gt;
+&lt;http://example.org/netWorth/nw1/&gt;
    a o:NetWorth;
    o:netWorthOf &lt;http://example.org/users/JohnZSmith&gt;;
    o:asset 
@@ -1189,7 +1189,7 @@
 &lt;http://example.org/netWorth/nw1/assets/&gt;
    a ldp:DirectContainer;
    dcterms:title "The assets of JohnZSmith";
-   ldp:membershipResource &lt;http://example.org/netWorth/nw1&gt;;
+   ldp:membershipResource &lt;http://example.org/netWorth/nw1/&gt;;
    ldp:hasMemberRelation o:asset;
    ldp:contains &lt;a1&gt;, &lt;a2&gt;.
 </pre>
@@ -1229,7 +1229,7 @@
 &lt;http://example.org/netWorth/nw1/liabilities/&gt;
    a ldp:DirectContainer;
    dcterms:title "The liabilities of JohnZSmith";
-   ldp:membershipResource &lt;http://example.org/netWorth/nw1&gt;;
+   ldp:membershipResource &lt;http://example.org/netWorth/nw1/&gt;;
    ldp:hasMemberRelation o:liability;
    ldp:contains &lt;l1&gt;, &lt;l2&gt;, &lt;l3&gt;.
 </pre>
@@ -1270,14 +1270,14 @@
 	newly created liability resource, at least two new triples would be added.
 	</p>
 	<ol>
-	<li>In the net worth resource, <code>&lt;http://example.org/netWorth/nw1&gt; o:liability &lt;liabilities/l4&gt;</code></li>
+	<li>In the net worth resource, <code>&lt;http://example.org/netWorth/nw1/&gt; o:liability &lt;liabilities/l4&gt;</code></li>
 	<li>In the liability container, <code>&lt;http://example.org/netWorth/nw1/liabilities/&gt; ldp:contains &lt;l4&gt;</code>.</li>
 	</ol>
 
 	<p>
 	You might wonder why we chose to create two new containers instead of making
-	<code>http://example.org/netWorth/nw1</code> itself a container.
-	A single net worth container would be a fine design if <code>http://example.org/netWorth/nw1</code>
+	<code>http://example.org/netWorth/nw1/</code> itself a container.
+	A single net worth container would be a fine design if <code>http://example.org/netWorth/nw1/</code>
 	had only assets or only liabilities (basically: only a single predicate to manage), 
 	but since it has separate predicates for assets and liabilities an ambiguity arises:
 	it is unspecified whether a client's creation request (POST)
@@ -1298,8 +1298,8 @@
 	to identify these advisors with URLs that contain a fragment (hash) to represent
 	these real-world resources, not the documents that describe them.</p>
 
-<em>Request</em> to <code>http://example.org/netWorth/nw1</code>:
-<pre class="example" id="ldpc-ex-membership-full-elab-req">GET /netWorth/nw1 HTTP/1.1
+<em>Request</em> to <code>http://example.org/netWorth/nw1/</code>:
+<pre class="example" id="ldpc-ex-membership-full-elab-req">GET /netWorth/nw1/ HTTP/1.1
 Host: example.org
 Accept: text/turtle</pre>
 
@@ -1312,13 +1312,13 @@
       &lt;http://www.w3.org/ns/ldp#Resource&gt;; rel="type"
 Allow: GET,OPTIONS,HEAD,PUT,DELETE
 Transfer-Encoding: chunked
-<!-- @base <http://example.org/netWorth/nw1>. -->
+<!-- @base <http://example.org/netWorth/nw1/>. -->
 @prefix ldp: &lt;http://www.w3.org/ns/ldp#&gt;.
 @prefix dcterms: &lt;http://purl.org/dc/terms/&gt;.
 @prefix foaf: &lt;http://xmlns.com/foaf/0.1/&gt;.
 @prefix o: &lt;http://example.org/ontology#&gt;.
 
-&lt;http://example.org/netWorth/nw1&gt;
+&lt;http://example.org/netWorth/nw1/&gt;
    a o:NetWorth;
    o:netWorthOf &lt;http://example.org/users/JohnZSmith&gt;;
    o:advisor
@@ -1382,7 +1382,7 @@
 	newly created advisor resource, at least two new triples would be added.
 	</p>
 	<ol>
-	<li>In the net worth resource, <code>&lt;http://example.org/netWorth/nw1&gt; o:advisor &lt;advisors/george#me&gt;</code></li>
+	<li>In the net worth resource, <code>&lt;http://example.org/netWorth/nw1/&gt; o:advisor &lt;advisors/george#me&gt;</code></li>
 	<li>In the advisors container, <code>&lt;http://example.org/netWorth/nw1/advisors/&gt; ldp:contains &lt;george&gt;</code></li>
 	</ol>
 
@@ -2300,11 +2300,11 @@
 &lt;&gt;
    a ldp:DirectContainer;
    dcterms:title "The assets of JohnZSmith";
-   ldp:membershipResource &lt;http://example.org/netWorth/nw1&gt;;
+   ldp:membershipResource &lt;http://example.org/netWorth/nw1/&gt;;
    ldp:hasMemberRelation o:asset;
    ldp:insertedContentRelation ldp:MemberSubject.
 
-&lt;http://example.org/netWorth/nw1&gt;
+&lt;http://example.org/netWorth/nw1/&gt;
    a o:NetWorth;
    o:asset &lt;a1&gt;, &lt;a3&gt;, &lt;a2&gt;.
 
@@ -2353,7 +2353,7 @@
 &lt;http://example.org/netWorth/nw1/assets/&gt;
    a ldp:DirectContainer;
    dcterms:title "The assets of JohnZSmith";
-   ldp:membershipResource &lt;http://example.org/netWorth/nw1&gt;;
+   ldp:membershipResource &lt;http://example.org/netWorth/nw1/&gt;;
    ldp:hasMemberRelation o:asset;
    ldp:insertedContentRelation ldp:MemberSubject.</pre>
 
@@ -2395,7 +2395,7 @@
 &lt;http://example.org/netWorth/nw1/assets/&gt;
    a ldp:DirectContainer;
    dcterms:title "The assets of JohnZSmith";
-   ldp:membershipResource &lt;http://example.org/netWorth/nw1&gt;;
+   ldp:membershipResource &lt;http://example.org/netWorth/nw1/&gt;;
    ldp:hasMemberRelation o:asset;
    ldp:insertedContentRelation ldp:MemberSubject.</pre>
 
@@ -2442,11 +2442,11 @@
 &lt;http://example.org/netWorth/nw1/assets/&gt;
    a ldp:DirectContainer;
    dcterms:title "The assets of JohnZSmith";
-   ldp:membershipResource &lt;http://example.org/netWorth/nw1&gt;;
+   ldp:membershipResource &lt;http://example.org/netWorth/nw1/&gt;;
    ldp:hasMemberRelation o:asset;
    ldp:insertedContentRelation ldp:MemberSubject.
 
-&lt;http://example.org/netWorth/nw1&gt;
+&lt;http://example.org/netWorth/nw1/&gt;
    a o:NetWorth;
    o:asset &lt;a1&gt;, &lt;a3&gt;, &lt;a2&gt;.</pre>
 
@@ -2616,6 +2616,7 @@
 
 <blockquote><em><a href="http://www.w3.org/TR/2014/WD-ldp-20140916">Last Call Working Draft 3</a></em></blockquote>
 <ul>
+	<li>2014-09-10 - Fix examples per Rob Sanderson's email ... /nw1 > /nw1/ </li> (JA) </li>
 	<li>2014-09-10 - Wafer thin change to Turtle-required words, lest the chair fetchez la vache (JA) </li>
 	<li>2014-09-09 - Re-factor Turtle/JSON-LD required words for readability and completeness (JA) </li>
 	<li>2014-09-08 - Add link to Best Practices now that it has been published (JA) </li>