--- a/ldp.html Mon Feb 17 16:42:46 2014 -0500
+++ b/ldp.html Mon Feb 17 17:07:01 2014 -0500
@@ -7,20 +7,14 @@
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.
+
+Paging related:
+ TODO: Example 11 is missing ldp:contains, true? Omit due to GET on page resource, should make it more clear.
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,
- 5.2.10 Some LDPC's have membership object's that are not directly URIs minted upon LDPC member creation,
- (JohnA) I found these particularly hard to read. And I perpetrated the SortCollation paragraphs.
- Links to examples might be an 80-20 solution.
- - TODO: 5.3.1: I'd change the link to the example ("as in the example") to refer the concrete example #, I think example 9.
- Currently does not work when printing.
-->
<html>
<head>
@@ -1601,7 +1595,7 @@
whose predicate is <code>ldp:hasMemberRelation</code>,
and whose object is the URI of <var>membership-predicate</var>.
</h2>
- <section id="ldpc-containtriple-basic"><h2 class="normal"><a title="Linked Data Platform Basic Container">LDP-BCs</a> MUST
+ <section id="ldpc-containtriple-basic"><h2 class="normal"><a title="Linked Data Platform Basic Container">LDP-BCs</a> MUST
behave as if their state contains the triple
whose subject is the LDPC URI,
whose predicate is <code>ldp:hasMemberRelation</code>,
@@ -1691,7 +1685,7 @@
<a title="Membership triples">membership triples</a> following one of the consistent
patterns from that definition.
The membership-constant-URI of the triples MAY be the container itself
- or MAY be another resource (as in the <a href="#ldpc-ex-membership-subj">example</a>). See also
+ or MAY be another resource (as in the <a href="#ldpc-ex-membership-subj">net worth LDP-DC example</a>). See also
section on <a href="#ldpc-mbrpred">LDPC membership predicates</a>.
</h2></section><!-- Was 5.3.1 / #ldpc-5_3_1 -->