--- a/ldp.html Sat Mar 01 15:15:19 2014 -0500
+++ b/ldp.html Sat Mar 01 15:32:14 2014 -0500
@@ -578,7 +578,7 @@
presence of a <var>(subject-URI, <code>rdf:type</code>, <code>ldp:Resource</code>)</var> triple in an LDP-RS.
The presence of this header asserts that the server complies with the LDP specification's constraints on
HTTP interactions with LDPRs, that is
- it asserts that the resource <a href="#ldpr-gen-tags">has Etags</a>, <a href="#ldpr-gen-rdf">has an RDF representation</a>, and so on,
+ it asserts that the resource <a href="#ldpr-gen-etags">has Etags</a>, <a href="#ldprs-gen-rdf">has an RDF representation</a>, and so on,
which is not true of all Web resources served as RDF media types.
</p>
<p>
@@ -701,7 +701,7 @@
<section id="ldpr-HTTP_HEAD">
<h2>HTTP HEAD</h2>
- <p>Note that certain LDP mechanisms, such as <a href="#ldpr-Paging">paging</a>, rely on HTTP headers, and HTTP generally requires that
+ <p>Note that certain LDP mechanisms rely on HTTP headers, and HTTP generally requires that
<code>HEAD</code> responses include the same headers as <code>GET</code> responses.
Thus, implementers should also carefully read sections <a href="#ldpr-HTTP_GET"></a>
and <a href="#ldpr-HTTP_OPTIONS"></a>.</p>
@@ -773,7 +773,7 @@
client applications that don’t support inferencing.
</h2></section><!-- Was 4.2.5 / #ldpr-4_2_5 -->
- <section id="ldpc-typecontainer"><h2 class="normal">The representation of an LDP-RS MAY have an <code>rdf:type</code>
+ <section id="ldprs-rdftype"><h2 class="normal">The representation of an LDP-RS MAY have an <code>rdf:type</code>
of only one of <code>ldp:RDFSource</code> for <a title="">Linked Data Platform RDF Source</a>.
</h2></section><!-- Was 5.2.7 / #ldpc-5_2_7 -->
@@ -1062,7 +1062,7 @@
to identify these advisors with URLs that contain a fragment (hash) to represent
these real-world resources, not the documents that describe them.</p>
-<pre class="example" id="ldpc-ex-membership-full"># The following is an elaborated representation of
+<pre class="example" id="ldpc-ex-membership-full-elab"># The following is an elaborated representation of
# http://example.org/netWorth/nw1
# Adding o:advisor but eaving off o:asset and o:liability for brevity.
<!-- @base is here only so it's easier to paste into validators for checking -->
@@ -1222,7 +1222,7 @@
to the LDPC's HTTP <code>Request-URI</code>.
<a title="LDP server">LDP servers</a> MAY provide additional HTTP <code>Link: rel='type'</code> headers
to advertise their support for <a href="#ldpc-typecontainer">specific LDPC types</a>.
- The <a href="#ldpr-gen_linktypehdr">notes on the corresponding LDPR constraint</a> apply
+ The <a href="#ldpr-gen-linktypehdr">notes on the corresponding LDPR constraint</a> apply
equally to LDPCs.
</h2></section><!-- Was 5.2.11 / #ldpc-5_2_11 -->
@@ -1415,7 +1415,7 @@
<section id="ldpc-HTTP_HEAD">
<h2>HTTP HEAD</h2>
- <p>Note that certain LDP mechanisms, such as <a href="#ldpr-Paging">paging</a>,
+ <p>Note that certain LDP mechanisms
rely on HTTP headers, and HTTP generally requires that
<code>HEAD</code> responses include the same headers as <code>GET</code> responses. Also <a title="LDP server">LDP servers</a> must also include HTTP headers
on response to <code>OPTIONS</code>, see <a href="#ldpr-HTTP_OPTIONS" class="sectionRef"></a>.
@@ -1502,7 +1502,7 @@
</section> <!-- ldpbc Basic -->
-<section id="ldpc-direct">
+<section id="ldpdc">
<h2>Direct</h2>
<!-- TODO: membership triples definitions? Could be valuable to have some informative statement here
such as: Direct containers add the concept of membership, flexibility of which resources associated and which predicate to indicate-->
@@ -1763,8 +1763,7 @@
or that are from the representations of the members (if they have RDF
representations). This allows an <a>LDP server</a> to provide clients with
information about the members without the client having to do a <code>GET</code>
- on each member individually. See <a href="#ldpc-member_data">Container
- Member Information</a> for additional details.
+ on each member individually.
</h2></section>
<section id="ldp-rdfconcepts-extra-triples-types"><h2 class="normal">The state of an LDPR can have more than one
@@ -2259,7 +2258,7 @@
<li>2014-01-17 - First attempt at correcting section ordering and anchors (SS)</li>
<li>2014-01-02 - ACTION-122 Updated 4.2.10, 5.4.4, example 8 + added 5.2.11 requiring rel=type for interaction model (JA)</li>
<li>2014-01-02 - ACTION-119 Added 5.4.15 requiring ldp:created for indirect containers (JA)</li>
- <li>2013-11-27 - ACTION-101 Added informative <a href="#security">security</a> section (SS)</li>
+ <li>2013-11-27 - ACTION-101 Added informative security section (SS)</li>
<li>2013-11-27 - ACTION-100 Added informative note to Ordering section that containers can be nested (SS)</li>
<li>2013-11-18 - Various editorial and validation fixes (SS)</li>
<li>2013-11-12 - Clean up some remnants of inlining (JA)</li>
@@ -2281,7 +2280,7 @@
<li>2013-10-01 - Revising introduction (JA)</li>
<li>2013-10-01 - Conformance section drafting + mock up "LDP Clients" section as part of that (JA)</li>
<li>2013-09-23 - Remove client/server-initiated paging terms (JA)</li>
- <li>2013-09-17 - Change must to MUST in <a href="#ldpc-5_6_4">5.6.4</a> (SS)</li>
+ <li>2013-09-17 - Change must to MUST in 5.6.4 (SS)</li>
<li>2013-09-17 - Removed "at-risk" inlining feature from spec, <a href="https://www.w3.org/2012/ldp/track/actions/98">ACTION-98</a> (SS)</li>
<li>2013-09-17 - Fixed vanishing section ref problem (SS)</li>
<li>2013-08-19 - Basic preparation for edits unto LC draft (SS)</li>
@@ -2301,7 +2300,7 @@
<li>2013-07-17 - Various updates from suggests from <a href="http://lists.w3.org/Archives/Public/public-ldp-wg/2013Jul/0067.html">Raúl</a> (SS)</li>
<li>2013-07-15 - Inserted ldp:insertedContentRelation into examples (SS)</li>
<li>2013-07-15 - ISSUE-79 ldp:contains => ldp:created (JA)</li>
- <li>2013-07-11 - Improving working in <a href="#ldpr-Paging" class="sectionRef"></a> to remove container references (SS)</li>
+ <li>2013-07-11 - Improving working in #ldpr-Paging to remove container references (SS)</li>
<li>2013-07-11 - Removed 4.1.5, section number fixup:4.1.8-13->6-11, 4.9.2.* fixup, 5.3.7-10->\2-5 (SS)</li>
<li>2013-07-11 - Removed all stubbed out sections 5.1.3, 5.3.2-6 (SS)</li>
<li>2013-07-11 - Various editorial clean up items from editor todo list (SS)</li>