--- a/ldp.html Tue Apr 15 13:28:48 2014 -0400
+++ b/ldp.html Tue Apr 15 14:08:54 2014 -0400
@@ -308,7 +308,7 @@
<dt><dfn>Linked Data Platform RDF Source</dfn> (<abbr title="Linked Data Platform RDF Source">LDP-RS</abbr>)</dt>
<dd>An <a title="Linked Data Platform Resource">LDPR</a> whose state is fully represented in RDF, corresponding to
- an RDF <a href="http://www.w3.org/TR/rdf11-concepts/#dfn-named-graph">named graph</a>. See also the term
+ an RDF graph. See also the term
<a href="http://www.w3.org/TR/rdf11-concepts/#dfn-rdf-source">RDF Source</a> from [[!rdf11-concepts]].
<p></p></dd>
@@ -1054,14 +1054,6 @@
triples whose subject is the LDPC resource itself.
</p>
- <p>Alternatively, servers may provide the net worth resource and supporting containers in a single response
- representation. When doing this, a preference would be for RDF formats that support multiple named graphs, one
- named graph for the net worth resource and then two others for asset and liability containers. This allows for
- the membership triples to be represented with the named graph for the net worth resource, while the containment triples
- would be represented within the liability and asset containers [[rdf11-concepts]]. Generally, the membership triples belong
- to the representation of an LDP-RS and the containment triples belong to the representation of the LDPC.
- </p>
-
<p>Additionally, we could extend our net worth example to include a container for
advisors (people) that have managed the assets and liabilities. We have decided
to identify these advisors with URLs that contain a fragment (hash) to represent
@@ -1295,9 +1287,8 @@
</h2></section><!-- Was 5.4.3 / #ldpc-5_4_3 -->
<section id="ldpc-post-createrdf"><h2 class="normal"><a title="LDP server">LDP servers</a> that successfully create a resource from a
- RDF representation in the request entity body MUST honor the client's requested interaction model(s). The created resource
- can be thought of as an RDF <a href="http://www.w3.org/TR/rdf11-concepts/#dfn-named-graph">named graph</a> [[!rdf11-concepts]].
- If any requested model cannot be honored, the server MUST fail the request.
+ RDF representation in the request entity body MUST honor the client's requested interaction model(s).
+ If any requested interaction model cannot be honored, the server MUST fail the request.
</h2><!-- Was 5.4.4 / #ldpc-5_4_4 -->
<ul>
<li>If the request header specifies <a href="#ldpr-gen-linktypehdr">an LDPR interaction model</a>, then the server MUST handle subsequent
@@ -1396,8 +1387,7 @@
</h2></section><!-- Was 5.5.1 / #ldpc-5_5_1 -->
<section id="ldpc-put-create"><h2 class="normal"><a title="LDP server">LDP servers</a> that allow LDPR creation via <code>PUT</code>
- SHOULD NOT re-use URIs. For RDF representations (LDP-RSs),the created resource
- can be thought of as an RDF <a href="http://www.w3.org/TR/rdf11-concepts/#dfn-named-graph">named graph</a> [[!rdf11-concepts]].
+ SHOULD NOT re-use URIs.
</h2></section><!-- Was 5.5.4 / #ldpc-5_5_4 -->
</section>