--- a/ldp-bp/ldp-bp.html Mon Jul 07 14:20:54 2014 -0400
+++ b/ldp-bp/ldp-bp.html Tue Jul 08 09:09:21 2014 -0500
@@ -375,8 +375,7 @@
It is often very useful to know the type (class) of an LDPR, though
it is not essential to work with the interaction capabilities that
LDP offers. Still, to make data more useful in the broadest context,
- type should be explicitly defined using the
- <code>rdf:type</code>
+ type should be explicitly defined using the <code>rdf:type</code>
predicate defined by [[RDF-SCHEMA]].
</p>
@@ -912,21 +911,21 @@
</section>
<section>
- <h3>Respond with canonical URLs and use them for identity comparison</h3>
+ <h3>Respond with primary URLs and use them for identity comparison</h3>
- <p>Clients can access an LDPR using multiple URLs. An LDPR server
+ <p>Clients can access an LDPR using multiple URLs. An LDP server
should respond to each of those requests using a single consistent
- URL, a canonical URL, for the LDPR. This canonical URL may be found
+ URL, a primary URL, for the LDPR. This primary URL may be found
in the response's Location and/or Content-Location headers, and
potentially also in the representation of the LDPR. A common case is
URLs that vary by protocol, one HTTP and one HTTPS, but are
otherwise identical. In most cases those two URLs refer to the same
resource, and the server should respond to requests on either URL
- with a single (canonical) URL.</p>
+ with a single (primary) URL.</p>
- <p>Clients should use the canonical URL as an LDPR's identity;
+ <p>Clients should use the primary URL as an LDPR's identity;
for example, when determining if two URLs refer to the same resource
- clients should compare the canonical URLs, not the URLs used to
+ clients should compare the primary URLs, not the URLs used to
access the resources.</p>
</section>
@@ -944,7 +943,7 @@
<section>
<h3>Minimize server-specific constraints</h3>
- <p>LDPR servers should enable simple creation and modification of
+ <p>LDP servers should enable simple creation and modification of
LDPRs.</p>
<P>It may be common for LDP servers to put restrictions on
@@ -973,7 +972,7 @@
<h3>Containers are not limited to membership and containment triples</h3>
<p>It is important to remember that a Linked Data Platform
- Container (LDPC) is also a Linked Data Platform Resource (LDPR) and
+ Container (LDPC) is also a Linked Data Platform RDF Source (LDP-RS) and
though it might exist as a membership controller, it may also represent
additional data that is valuable to the agents that access
it.</p>