--- a/ldp.html Mon Feb 17 14:51:39 2014 -0500
+++ b/ldp.html Mon Feb 17 16:42:46 2014 -0500
@@ -3,16 +3,16 @@
<!--
TODO: Search for them within this document.
TODO: Once companion documents (best practices, primer) have URLs, link to them. Search on "companion".
- TODO: Stabilize terminology/names such as (LDP-RR, LDP-BR, LDP-BC, LDP-DC, LDP-IC) and membership* predicate names
- TODO: Consider incorporating RDF Document into our Terms http://www.w3.org/TR/rdf11-concepts/#dfn-rdf-document
TODO: Once the membership* names stabilize, take a pass through for "membership consistent value", membership-constant-URI
and see if there is a friendlier way to phrase it.
TODO: Consider how to not have to explicitly list parent classes.
+ TODO: Improve LDPC intro by explaining simply that LDP-DC restricts LDPC and LDP-BC restricts LDP-DC.
TODO: Paging intro: add 3rd example showing header link age amongst pages and (HEAD on) the base resource.
Maybe also insert HEAD on base as new first example instead of relying on text alone.
TODO: The ReSpec SPARQL QUERY link is http://www.w3.org/TR/rdf-sparql-query/ , which has highlighted text
referring readers to SPARQL 1.1. Which normative reference do we want? http://www.w3.org/TR/sparql11-query/ Ask Sandro
TODO: Add new "discovery of server capabilities" non-norm section
+ TODO: Example 11 is missing ldp:contains
Various pre-LC comments:
- TODO: (now 6.2.7) 5.2.5.1 For a given triple T with a subject C of the LDPC and predicate of ldp:hasMemberRelation,
5.2.5.2 For a given triple T with a subject C of the LDPC and predicate of ldp:isMemberOfRelation,
@@ -302,7 +302,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 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
- <dfn>RDF Source</dfn> from [[rdf11-concepts]].
+ <a href="http://www.w3.org/TR/rdf11-concepts/#dfn-rdf-source">RDF Source</a> from [[!RDF11-CONCEPTS]].
<p></p></dd>
<dt><dfn>Linked Data Platform Non-RDF Source</dfn> (<abbr title="Linked Data Platform Non-RDF Source">LDP-NR</abbr>)</dt>
@@ -312,7 +312,7 @@
<dt><dfn>Linked Data Platform Container</dfn> (<abbr title="Linked Data Platform Container">LDPC</abbr>)</dt>
<dd>An LDPR representing a collection of <a title="Membership">member</a> resources and/or <a title="Containment">contained</a>
- documents (information resources [[!WEBARCH]])
+ documents (<a href="http://www.w3.org/TR/rdf11-concepts/#dfn-rdf-document">RDF Document</a> [[!RDF11-CONCEPTS]] or information resources [[!WEBARCH]])
that responds to client requests for creation, modification, and/or enumeration of its members and documents,
and that conforms to the simple lifecycle
patterns and conventions in <a href="#ldpc" class="sectionRef"></a>.
@@ -1297,7 +1297,7 @@
representations. 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
+ would be represented within the liability and asset containers [[RDF11-CONCEPTS]]. Generally, the membership triples belong
to the representation of a LDP-RS and the containment triples belong to the representation of the LDPC.
</p>
@@ -1813,7 +1813,7 @@
<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]].
+ 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 model cannot be honored, the server MUST fail the request.
</h2><!-- Was 5.4.4 / #ldpc-5_4_4 -->
<ul>
@@ -1932,7 +1932,7 @@
<section id="ldpc-put-create"><h2 class="normal"><a title="LDP server">LDP servers</a> that allow member creation via <code>PUT</code>
SHOULD NOT re-use URIs. For RDF representations (LDP-RSs),the created resource
- can be thought of as a RDF <a href="http://www.w3.org/TR/rdf11-concepts/#dfn-named-graph">named graph</a> [[rdf11-concepts]].
+ can be thought of as a RDF <a href="http://www.w3.org/TR/rdf11-concepts/#dfn-named-graph">named graph</a> [[!RDF11-CONCEPTS]].
</h2></section><!-- Was 5.5.4 / #ldpc-5_5_4 -->
</section>
@@ -2572,6 +2572,7 @@
<!-- <blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-20130930/">Candidate Recommendation Draft</a></em></blockquote> wah -->
<!-- <blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-20130730/">Last Call Draft</a></em></blockquote> -->
<ul>
+ <li>2014-02-17 - Reference to RDF Document into terms (SS) </li>
<li>2014-02-17 - Adopted container hierarchy and merged Indirect Container into Container (SS) </li>
<li>2014-02-17 - Adopted new resource types: LDP RDF Source (LDP-RS) (was LDP RDF Resource) and LDP Non-RDF Source (LDP-NR) (was LDP Binary Resource) (SS)</li>
<li>2014-02-17 - Adopted new predicate names: ldp:membershipResource, ldp:hasMemberRelation and ldp:isMemberOfRelation (SS) </li>