--- a/ldp.html Mon Nov 18 08:32:01 2013 -0500
+++ b/ldp.html Mon Nov 18 09:10:17 2013 -0500
@@ -1,25 +1,14 @@
<!DOCTYPE html>
<!--
Editor TODO:
- - Convert cases like 5.4.3 to a sectionRef ... search on sectionRef in case numbers change
- - Once companion documents have URLs, link to them. Search on "companion".
- - In #ldpr-HTTP_POST, move "Clients can create LDPRs via" content into an intro/overview section and add PATCH.
+ - Search "TODO" within this document.
+ - Convert cases like 5.4.3 to a sectionRef ... search on sectionRef in case numbers change
+ - Once companion documents (best practices, primer) have URLs, link to them. Search on "companion".
- 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.
- Paging intro: add 3rd example showing header linkage amongst pages and (HEAD on) the base resource.
Maybe also insert HEAD on base as new first example instead of relying on text alone.
- - The word "canonical" is used twice in the document. Since we do not deal with URI
- canonicalization in the specification, I would remove the word and the meaning of
- the sentences is the same.
- - section 4.6...respec is adding extra spaces to the sectionRefs
- carefully read section 4.2 .
- ->
- carefully read section 4.2.
-
- defined in section 4.8 .
- ->
- defined in section 4.8.
- - The ReSpec SPARQL QUERY link is http://www.w3.org/TR/rdf-sparql-query/ , which has highlighted text
+ - 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?
Various pre-LC comments:
- 5.2.5.1 For a given triple T with a subject C of the LDPC and predicate of ldp:containsRelation,
@@ -636,6 +625,7 @@
<code>PUT</code> (<a href="#ldpc-HTTP_PUT" class="sectionRef"></a>) to a LDPC, see those
sections for more details. Any server-imposed constraints on LDPR creation or update
<a href="#ldpr-4_2_13">must be advertised</a> to clients.
+ <!-- TODO: movethis content into an intro/overview section and add PATCH. -->
</p>
</section>