--- a/TR/WD-ldp-20140311/Overview.html Tue Mar 04 13:14:38 2014 -0500
+++ b/TR/WD-ldp-20140311/Overview.html Tue Mar 04 13:40:45 2014 -0500
@@ -1,5 +1,5 @@
<!DOCTYPE html>
-<!-- saved from url=(0054)https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html -->
+<!-- saved from url=(0054) -->
<html lang="en" dir="ltr" typeof="bibo:Document w3p:LastCall" about="" property="dcterms:language" content="en" prefix="bibo: http://purl.org/ontology/bibo/ w3p: http://www.w3.org/2001/02pd/rec54#"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Linked Data Platform 1.0</title>
@@ -279,12 +279,12 @@
<p class="copyright">
<a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>
- © 2014 <a href="http://www.w3.org/"><acronym
- title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a
- href="http://www.csail.mit.edu/"><acronym
- title="Massachusetts Institute of Technology">MIT</acronym></a>, <a
- href="http://www.ercim.eu/"><acronym
- title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>,
+ © 2014 <a href="http://www.w3.org/"><abbr
+ title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup> (<a
+ href="http://www.csail.mit.edu/"><abbr
+ title="Massachusetts Institute of Technology">MIT</abbr></a>, <a
+ href="http://www.ercim.eu/"><abbr
+ title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>,
<a href="http://www.keio.ac.jp/">Keio</a>, <a
href="http://ev.buaa.edu.cn/">Beihang</a>), All Rights Reserved. W3C
<a
@@ -314,9 +314,9 @@
<p>
This is the 2nd Last Call for Comments where the Working Group has addressed all
- raised issues and as a result some significant changes have been made, see <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#history" class="sectionRef sec-ref">section <span class="secno">B.</span> <span class="sec-title">Change History</span></a>. Most notably
+ raised issues and as a result some significant changes have been made, see <a href="#history" class="sectionRef sec-ref">section <span class="secno">B.</span> <span class="sec-title">Change History</span></a>. Most notably
the Working Group has decided to handle paging as an extension to LDP in a separate
- REC-track specification. [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-LDP-PAGING">LDP-PAGING</a></cite>]
+ REC-track specification. [<cite><a class="bibref" href="#bib-LDP-PAGING">LDP-PAGING</a></cite>]
</p>
<p>
@@ -379,7 +379,7 @@
-</section><section id="toc"><h2 class="introductory" aria-level="1" role="heading" id="h2_toc">Table of Contents</h2><ul class="toc" role="directory" id="respecContents"><li class="tocline"><a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#intro" class="tocxref"><span class="secno">1. </span>Introduction</a></li><li class="tocline"><a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#terms" class="tocxref"><span class="secno">2. </span>Terminology</a><ul class="toc"><li class="tocline"><a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#conventions" class="tocxref"><span class="secno">2.1 </span>Conventions Used in This Document</a></li></ul></li><li class="tocline"><a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#conformance" class="tocxref"><span class="secno">3. </span>Conformance</a></li><li class="tocline"><a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpr" class="tocxref"><span class="secno">4. </span>Linked Data Platform Resources</a><ul class="toc"><li class="tocline"><a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpr-informative" class="tocxref"><span class="secno">4.1 </span>Introduction</a></li><li class="tocline"><a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpr-resource" class="tocxref"><span class="secno">4.2 </span>Resource</a><ul class="toc"></ul></li><li class="tocline"><a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldprs" class="tocxref"><span class="secno">4.3 </span><abbr title="Resource Description Framework">RDF</abbr> Source</a><ul class="toc"></ul></li><li class="tocline"><a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpnr" class="tocxref"><span class="secno">4.4 </span>Non-<abbr title="Resource Description Framework">RDF</abbr> Source</a><ul class="toc"></ul></li></ul></li><li class="tocline"><a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpc" class="tocxref"><span class="secno">5. </span>Linked Data Platform Containers</a><ul class="toc"><li class="tocline"><a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpc-informative" class="tocxref"><span class="secno">5.1 </span>Introduction</a><ul class="toc"></ul></li><li class="tocline"><a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpc-container" class="tocxref"><span class="secno">5.2 </span>Container</a><ul class="toc"></ul></li><li class="tocline"><a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpbc" class="tocxref"><span class="secno">5.3 </span>Basic</a><ul class="toc"></ul></li><li class="tocline"><a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpdc" class="tocxref"><span class="secno">5.4 </span>Direct</a><ul class="toc"></ul></li><li class="tocline"><a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpic" class="tocxref"><span class="secno">5.5 </span>Indirect</a><ul class="toc"></ul></li></ul></li><li class="tocline"><a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#base-specs" class="tocxref"><span class="secno">6. </span>Notable information from normative references</a><ul class="toc"><li class="tocline"><a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#specs-webarch" class="tocxref"><span class="secno">6.1 </span>Architecture of the World Wide Web</a><ul class="toc"></ul></li><li class="tocline"><a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#specs-http" class="tocxref"><span class="secno">6.2 </span>HTTP 1.1</a><ul class="toc"></ul></li><li class="tocline"><a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#specs-rdf" class="tocxref"><span class="secno">6.3 </span><abbr title="Resource Description Framework">RDF</abbr></a><ul class="toc"></ul></li></ul></li><li class="tocline"><a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#http-header-definitions" class="tocxref"><span class="secno">7. </span>HTTP Header Definitions</a><ul class="toc"><li class="tocline"><a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#header-accept-post" class="tocxref"><span class="secno">7.1 </span>The Accept-Post Response Header</a><ul class="toc"></ul></li><li class="tocline"><a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#prefer-parameters" class="tocxref"><span class="secno">7.2 </span>Preferences on the Prefer Request Header</a><ul class="toc"></ul></li></ul></li><li class="tocline"><a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#security" class="tocxref"><span class="secno">8. </span>Security Considerations</a></li><li class="tocline"><a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#acknowledgements" class="tocxref"><span class="secno">A. </span>Acknowledgements</a></li><li class="tocline"><a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#history" class="tocxref"><span class="secno">B. </span>Change History</a></li><li class="tocline"><a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#references" class="tocxref"><span class="secno">C. </span>References</a><ul class="toc"><li class="tocline"><a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#normative-references" class="tocxref"><span class="secno">C.1 </span>Normative references</a></li><li class="tocline"><a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#informative-references" class="tocxref"><span class="secno">C.2 </span>Informative references</a></li></ul></li></ul></section>
+</section><section id="toc"><h2 class="introductory" aria-level="1" role="heading" id="h2_toc">Table of Contents</h2><ul class="toc" role="directory" id="respecContents"><li class="tocline"><a href="#intro" class="tocxref"><span class="secno">1. </span>Introduction</a></li><li class="tocline"><a href="#terms" class="tocxref"><span class="secno">2. </span>Terminology</a><ul class="toc"><li class="tocline"><a href="#conventions" class="tocxref"><span class="secno">2.1 </span>Conventions Used in This Document</a></li></ul></li><li class="tocline"><a href="#conformance" class="tocxref"><span class="secno">3. </span>Conformance</a></li><li class="tocline"><a href="#ldpr" class="tocxref"><span class="secno">4. </span>Linked Data Platform Resources</a><ul class="toc"><li class="tocline"><a href="#ldpr-informative" class="tocxref"><span class="secno">4.1 </span>Introduction</a></li><li class="tocline"><a href="#ldpr-resource" class="tocxref"><span class="secno">4.2 </span>Resource</a><ul class="toc"></ul></li><li class="tocline"><a href="#ldprs" class="tocxref"><span class="secno">4.3 </span><abbr title="Resource Description Framework">RDF</abbr> Source</a><ul class="toc"></ul></li><li class="tocline"><a href="#ldpnr" class="tocxref"><span class="secno">4.4 </span>Non-<abbr title="Resource Description Framework">RDF</abbr> Source</a><ul class="toc"></ul></li></ul></li><li class="tocline"><a href="#ldpc" class="tocxref"><span class="secno">5. </span>Linked Data Platform Containers</a><ul class="toc"><li class="tocline"><a href="#ldpc-informative" class="tocxref"><span class="secno">5.1 </span>Introduction</a><ul class="toc"></ul></li><li class="tocline"><a href="#ldpc-container" class="tocxref"><span class="secno">5.2 </span>Container</a><ul class="toc"></ul></li><li class="tocline"><a href="#ldpbc" class="tocxref"><span class="secno">5.3 </span>Basic</a><ul class="toc"></ul></li><li class="tocline"><a href="#ldpdc" class="tocxref"><span class="secno">5.4 </span>Direct</a><ul class="toc"></ul></li><li class="tocline"><a href="#ldpic" class="tocxref"><span class="secno">5.5 </span>Indirect</a><ul class="toc"></ul></li></ul></li><li class="tocline"><a href="#base-specs" class="tocxref"><span class="secno">6. </span>Notable information from normative references</a><ul class="toc"><li class="tocline"><a href="#specs-webarch" class="tocxref"><span class="secno">6.1 </span>Architecture of the World Wide Web</a><ul class="toc"></ul></li><li class="tocline"><a href="#specs-http" class="tocxref"><span class="secno">6.2 </span>HTTP 1.1</a><ul class="toc"></ul></li><li class="tocline"><a href="#specs-rdf" class="tocxref"><span class="secno">6.3 </span><abbr title="Resource Description Framework">RDF</abbr></a><ul class="toc"></ul></li></ul></li><li class="tocline"><a href="#http-header-definitions" class="tocxref"><span class="secno">7. </span>HTTP Header Definitions</a><ul class="toc"><li class="tocline"><a href="#header-accept-post" class="tocxref"><span class="secno">7.1 </span>The Accept-Post Response Header</a><ul class="toc"></ul></li><li class="tocline"><a href="#prefer-parameters" class="tocxref"><span class="secno">7.2 </span>Preferences on the Prefer Request Header</a><ul class="toc"></ul></li></ul></li><li class="tocline"><a href="#security" class="tocxref"><span class="secno">8. </span>Security Considerations</a></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span class="secno">A. </span>Acknowledgements</a></li><li class="tocline"><a href="#history" class="tocxref"><span class="secno">B. </span>Change History</a></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">C. </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">C.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">C.2 </span>Informative references</a></li></ul></li></ul></section>
@@ -388,7 +388,7 @@
<p>This specification describes the use
of HTTP for accessing, updating, creating and deleting resources from
servers that expose their resources as Linked Data. It provides clarifications
- and extensions of the rules of Linked Data [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-LINKED-DATA">LINKED-DATA</a></cite>]:</p>
+ and extensions of the rules of Linked Data [<cite><a class="bibref" href="#bib-LINKED-DATA">LINKED-DATA</a></cite>]:</p>
<ol>
<li>Use URIs as names for things</li>
<li>Use HTTP URIs so that people can look up those names</li>
@@ -399,44 +399,44 @@
</ol>
<p>This specification discusses standard HTTP and <abbr title="Resource Description Framework">RDF</abbr> techniques
used when constructing clients and servers that
- create, read, and write <a title="Linked Data Platform Resource" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-resource" class="internalDFN">Linked Data Platform Resources</a>.
+ create, read, and write <a title="Linked Data Platform Resource" href="#dfn-linked-data-platform-resource" class="internalDFN">Linked Data Platform Resources</a>.
A companion document discusses best practices that you
should use, and anti-patterns you should avoid, when constructing these clients and servers.
</p>
- <p>This specification defines a special type of <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-resource" class="internalDFN">Linked Data Platform Resource</a>: a
- <a title="Linked Data Platform Container" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-container" class="internalDFN">Container</a>. Containers are very useful
+ <p>This specification defines a special type of <a href="#dfn-linked-data-platform-resource" class="internalDFN">Linked Data Platform Resource</a>: a
+ <a title="Linked Data Platform Container" href="#dfn-linked-data-platform-container" class="internalDFN">Container</a>. Containers are very useful
in building application models involving collections of resources, often homogeneous ones.
For example, universities offer a collection of classes
and have a collection of faculty members, each faculty member teaches a collection of courses, and so on.
This specification discusses how to work with containers. Resources can be added to containers
using standard HTTP operations like
- POST (see <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpc-HTTP_POST" class="sectionRef sec-ref">section <span class="secno">5.2.3</span> <span class="sec-title">HTTP POST</span></a>).</p>
+ POST (see <a href="#ldpc-HTTP_POST" class="sectionRef sec-ref">section <span class="secno">5.2.3</span> <span class="sec-title">HTTP POST</span></a>).</p>
<p>The intention of this specification is to enable additional rules and layered groupings of rules as
additional specifications. The scope is intentionally narrow to provide a set of key rules for
reading and writing Linked Data that most, if not all, other specifications will depend upon and
implementations will support.</p>
<p>This specification provides some approaches to deal with large resources. An extension to this specification
- provides the ability to break large resource representations into multiple paged responses [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-LDP-PAGING">LDP-PAGING</a></cite>].</p>
- <p>For context and background, it could be useful to read <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-LDP-UCR">Linked Data Platform Use Case and Requirements</a> [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-LDP-UCR">LDP-UCR</a></cite>]
- and <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#base-specs" class="sectionRef sec-ref">section <span class="secno">6.</span> <span class="sec-title">Notable information from normative references</span></a>.</p>
+ provides the ability to break large resource representations into multiple paged responses [<cite><a class="bibref" href="#bib-LDP-PAGING">LDP-PAGING</a></cite>].</p>
+ <p>For context and background, it could be useful to read <a href="#bib-LDP-UCR">Linked Data Platform Use Case and Requirements</a> [<cite><a class="bibref" href="#bib-LDP-UCR">LDP-UCR</a></cite>]
+ and <a href="#base-specs" class="sectionRef sec-ref">section <span class="secno">6.</span> <span class="sec-title">Notable information from normative references</span></a>.</p>
</section>
<section id="terms" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<!--OddPage--><h2 aria-level="1" role="heading" id="h2_terms"><span class="secno">2. </span>Terminology</h2>
-<p>Terminology is based on <abbr title="World Wide Web Consortium">W3C</abbr>'s Architecture of the World Wide Web [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-WEBARCH">WEBARCH</a></cite>] and Hyper-text Transfer Protocol [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-HTTP11">HTTP11</a></cite>].
+<p>Terminology is based on <abbr title="World Wide Web Consortium">W3C</abbr>'s Architecture of the World Wide Web [<cite><a class="bibref" href="#bib-WEBARCH">WEBARCH</a></cite>] and Hyper-text Transfer Protocol [<cite><a class="bibref" href="#bib-HTTP11">HTTP11</a></cite>].
</p>
<dl class="glossary">
<dt>Link</dt>
<dd>A relationship between two resources when one resource (representation) refers to the other resource by means
- of a URI [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-WEBARCH">WEBARCH</a></cite>].
+ of a URI [<cite><a class="bibref" href="#bib-WEBARCH">WEBARCH</a></cite>].
<p></p></dd>
<dt>Linked Data</dt>
- <dd>As defined by Tim Berners-Lee [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-LINKED-DATA">LINKED-DATA</a></cite>].<p></p></dd>
+ <dd>As defined by Tim Berners-Lee [<cite><a class="bibref" href="#bib-LINKED-DATA">LINKED-DATA</a></cite>].<p></p></dd>
<dt>Client</dt>
- <dd>A program that establishes connections for the purpose of sending requests [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-HTTP11">HTTP11</a></cite>].<p></p></dd>
+ <dd>A program that establishes connections for the purpose of sending requests [<cite><a class="bibref" href="#bib-HTTP11">HTTP11</a></cite>].<p></p></dd>
<dt>Server</dt>
<dd>An application
@@ -448,46 +448,46 @@
connection, rather than to the program's capabilities in general.
Likewise, any server may act as an origin server, proxy, gateway,
or tunnel, switching behavior based on the nature of each request
- [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-HTTP11">HTTP11</a></cite>]. </p></dd>
+ [<cite><a class="bibref" href="#bib-HTTP11">HTTP11</a></cite>]. </p></dd>
<dt><dfn id="dfn-linked-data-platform-resource">Linked Data Platform Resource</dfn> (<abbr title="Linked Data Platform Resource">LDPR</abbr>)</dt>
<dd>A HTTP resource whose state is represented in any way that conforms to the simple lifecycle
- patterns and conventions in <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpr" class="sectionRef sec-ref">section <span class="secno">4.</span> <span class="sec-title">Linked Data Platform Resources</span></a>.<p></p></dd>
+ patterns and conventions in <a href="#ldpr" class="sectionRef sec-ref">section <span class="secno">4.</span> <span class="sec-title">Linked Data Platform Resources</span></a>.<p></p></dd>
<dt><dfn id="dfn-linked-data-platform-rdf-source">Linked Data Platform <abbr title="Resource Description Framework">RDF</abbr> Source</dfn> (<abbr title="Linked Data Platform RDF Source">LDP-RS</abbr>)</dt>
- <dd>An <a title="Linked Data Platform Resource" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-resource" class="internalDFN"><abbr title="Linked Data Platform Resource">LDPR</abbr></a> whose state is fully represented in <abbr title="Resource Description Framework">RDF</abbr>, corresponding to
+ <dd>An <a title="Linked Data Platform Resource" href="#dfn-linked-data-platform-resource" class="internalDFN"><abbr title="Linked Data Platform Resource">LDPR</abbr></a> whose state is fully represented in <abbr title="Resource Description Framework">RDF</abbr>, corresponding to
an <abbr title="Resource Description Framework">RDF</abbr> <a href="http://www.w3.org/TR/rdf11-concepts/#dfn-named-graph">named graph</a>. See also the term
- <a href="http://www.w3.org/TR/rdf11-concepts/#dfn-rdf-source"><abbr title="Resource Description Framework">RDF</abbr> Source</a> from [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-rdf11-concepts">rdf11-concepts</a></cite>].
+ <a href="http://www.w3.org/TR/rdf11-concepts/#dfn-rdf-source"><abbr title="Resource Description Framework">RDF</abbr> Source</a> from [<cite><a class="bibref" href="#bib-rdf11-concepts">rdf11-concepts</a></cite>].
<p></p></dd>
<dt><dfn id="dfn-linked-data-platform-non-rdf-source">Linked Data Platform Non-<abbr title="Resource Description Framework">RDF</abbr> Source</dfn> (<abbr title="Linked Data Platform Non-RDF Source">LDP-NR</abbr>)</dt>
- <dd>An <a title="Linked Data Platform Resource" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-resource" class="internalDFN"><abbr title="Linked Data Platform Resource">LDPR</abbr></a> whose state is <em>not</em> represented in <abbr title="Resource Description Framework">RDF</abbr>.
+ <dd>An <a title="Linked Data Platform Resource" href="#dfn-linked-data-platform-resource" class="internalDFN"><abbr title="Linked Data Platform Resource">LDPR</abbr></a> whose state is <em>not</em> represented in <abbr title="Resource Description Framework">RDF</abbr>.
These are binary or text documents that do not have useful <abbr title="Resource Description Framework">RDF</abbr> representations.
<p></p></dd>
<dt><dfn id="dfn-linked-data-platform-container">Linked Data Platform Container</dfn> (<abbr title="Linked Data Platform Container">LDPC</abbr>)</dt>
<dd>An <abbr title="Linked Data Platform RDF Source">LDP-RS</abbr> representing a collection of linked
- documents (<a href="http://www.w3.org/TR/rdf11-concepts/#dfn-rdf-document"><abbr title="Resource Description Framework">RDF</abbr> Document</a> [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-rdf11-concepts">rdf11-concepts</a></cite>] or information resources [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-WEBARCH">WEBARCH</a></cite>])
+ documents (<a href="http://www.w3.org/TR/rdf11-concepts/#dfn-rdf-document"><abbr title="Resource Description Framework">RDF</abbr> Document</a> [<cite><a class="bibref" href="#bib-rdf11-concepts">rdf11-concepts</a></cite>] or information resources [<cite><a class="bibref" href="#bib-WEBARCH">WEBARCH</a></cite>])
that responds to client requests for creation, modification, and/or enumeration of its linked members and documents,
and that conforms to the simple lifecycle
- patterns and conventions in <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpc" class="sectionRef sec-ref">section <span class="secno">5.</span> <span class="sec-title">Linked Data Platform Containers</span></a>.
+ patterns and conventions in <a href="#ldpc" class="sectionRef sec-ref">section <span class="secno">5.</span> <span class="sec-title">Linked Data Platform Containers</span></a>.
<p></p></dd>
<dt><dfn id="dfn-linked-data-platform-basic-container">Linked Data Platform Basic Container</dfn> (<abbr title="Linked Data Platform Basic Container">LDP-BC</abbr>)</dt>
- <dd>An <a title="Linked Data Platform Container" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-container" class="internalDFN"><abbr title="Linked Data Platform Container">LDPC</abbr></a> that defines a simple link to
- its <a title="Containment" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-containment" class="internalDFN">contained</a> documents (information resources) [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-WEBARCH">WEBARCH</a></cite>].
+ <dd>An <a title="Linked Data Platform Container" href="#dfn-linked-data-platform-container" class="internalDFN"><abbr title="Linked Data Platform Container">LDPC</abbr></a> that defines a simple link to
+ its <a title="Containment" href="#dfn-containment" class="internalDFN">contained</a> documents (information resources) [<cite><a class="bibref" href="#bib-WEBARCH">WEBARCH</a></cite>].
<p></p></dd>
<dt><dfn id="dfn-linked-data-platform-direct-container">Linked Data Platform Direct Container</dfn> (<abbr title="Linked Data Platform Direct Container">LDP-DC</abbr>)</dt>
- <dd>An <a title="Linked Data Platform Container" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-container" class="internalDFN"><abbr title="Linked Data Platform Container">LDPC</abbr></a> adds the concept <a title="Membership" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-membership" class="internalDFN">membership</a>, allows the flexibility of choosing what form its
- <a title="Membership triples" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-membership-triples" class="internalDFN">membership triples</a> take, and allows <a title="Membership" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-membership" class="internalDFN">members</a> to be
- any resources [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-WEBARCH">WEBARCH</a></cite>], not only documents.
+ <dd>An <a title="Linked Data Platform Container" href="#dfn-linked-data-platform-container" class="internalDFN"><abbr title="Linked Data Platform Container">LDPC</abbr></a> adds the concept <a title="Membership" href="#dfn-membership" class="internalDFN">membership</a>, allows the flexibility of choosing what form its
+ <a title="Membership triples" href="#dfn-membership-triples" class="internalDFN">membership triples</a> take, and allows <a title="Membership" href="#dfn-membership" class="internalDFN">members</a> to be
+ any resources [<cite><a class="bibref" href="#bib-WEBARCH">WEBARCH</a></cite>], not only documents.
<p></p></dd>
<dt><dfn id="dfn-linked-data-platform-indirect-container">Linked Data Platform Indirect Container</dfn> (<abbr title="Linked Data Platform Indirect Container">LDP-IC</abbr>)</dt>
- <dd>An <a title="Linked Data Platform Container" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-container" class="internalDFN"><abbr title="Linked Data Platform Container">LDPC</abbr></a> that is similar to a <a title="Linked Data Platform Direct Container" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-direct-container" class="internalDFN"><abbr title="Linked Data Platform Direct Container">LDP-DC</abbr></a>
- and is capable of having <a title="Membership" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-membership" class="internalDFN">members</a> whose URIs are based
- on the content of its <a title="Containment" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-containment" class="internalDFN">contained</a> documents rather than the URIs assigned to those documents.
+ <dd>An <a title="Linked Data Platform Container" href="#dfn-linked-data-platform-container" class="internalDFN"><abbr title="Linked Data Platform Container">LDPC</abbr></a> that is similar to a <a title="Linked Data Platform Direct Container" href="#dfn-linked-data-platform-direct-container" class="internalDFN"><abbr title="Linked Data Platform Direct Container">LDP-DC</abbr></a>
+ and is capable of having <a title="Membership" href="#dfn-membership" class="internalDFN">members</a> whose URIs are based
+ on the content of its <a title="Containment" href="#dfn-containment" class="internalDFN">contained</a> documents rather than the URIs assigned to those documents.
<p></p></dd>
<dt><dfn id="dfn-membership">Membership</dfn></dt>
@@ -514,7 +514,7 @@
inherent in their name, and existing vocabularies contain useful examples that read naturally in
each direction. <code>ldp:member</code> and <code>dcterms:isPartOf</code> are representative examples.
<p>
- Each linked container exposes properties (see <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpc-general" class="sectionRef sec-ref">section <span class="secno">5.2.1</span> <span class="sec-title">General</span></a>)
+ Each linked container exposes properties (see <a href="#ldpc-general" class="sectionRef sec-ref">section <span class="secno">5.2.1</span> <span class="sec-title">General</span></a>)
that allow clients to determine which pattern it
uses, what the actual <var>membership-predicate</var> and <var>membership-constant-URI</var> values are,
and (for containers that allow the creation of new members) what value is used
@@ -523,7 +523,7 @@
<p></p></dd>
<dt><dfn id="dfn-membership-predicate">Membership predicate</dfn></dt>
- <dd>The predicate of all an <abbr title="Linked Data Platform RDF Source">LDP-RS</abbr>'s <a title="Membership triples" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-membership-triples" class="internalDFN">membership triples</a>.
+ <dd>The predicate of all an <abbr title="Linked Data Platform RDF Source">LDP-RS</abbr>'s <a title="Membership triples" href="#dfn-membership-triples" class="internalDFN">membership triples</a>.
<p></p></dd>
<dt><dfn id="dfn-containment">Containment</dfn></dt>
@@ -551,7 +551,7 @@
<h3 aria-level="2" role="heading" id="h3_conventions"><span class="secno">2.1 </span>Conventions Used in This Document</h3>
<p>The namespace for LDP is <code>http://www.w3.org/ns/ldp#</code>.</p>
<p>Sample resource representations are provided in <code>text/turtle</code>
- format [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-turtle">turtle</a></cite>].</p>
+ format [<cite><a class="bibref" href="#bib-turtle">turtle</a></cite>].</p>
<p>Commonly used namespace prefixes:</p>
<pre style="word-wrap: break-word; white-space: pre-wrap;"> @prefix dcterms: <http://purl.org/dc/terms/>.
@prefix foaf: <http://xmlns.com/foaf/0.1/>.
@@ -569,7 +569,7 @@
</p>
<p>
The key words <em class="rfc2119" title="MUST">MUST</em>, <em class="rfc2119" title="MUST NOT">MUST NOT</em>, <em class="rfc2119" title="REQUIRED">REQUIRED</em>, <em class="rfc2119" title="SHOULD">SHOULD</em>, <em class="rfc2119" title="SHOULD NOT">SHOULD NOT</em>, <em class="rfc2119" title="RECOMMENDED">RECOMMENDED</em>, <em class="rfc2119" title="MAY">MAY</em>,
- and <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> in this specification are to be interpreted as described in [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-RFC2119">RFC2119</a></cite>].
+ and <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> in this specification are to be interpreted as described in [<cite><a class="bibref" href="#bib-RFC2119">RFC2119</a></cite>].
</p>
@@ -589,14 +589,14 @@
<li>C.2 Non-normative references: <b>non-normative</b></li>
</ul>
-<p>A conforming <b><dfn id="dfn-ldp-client">LDP client</dfn></b> is a conforming HTTP client [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-HTTP11">HTTP11</a></cite>] that follows the rules defined by LDP in
-<a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpr" class="sectionRef sec-ref">section <span class="secno">4.</span> <span class="sec-title">Linked Data Platform Resources</span></a> and also
-<a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpc" class="sectionRef sec-ref">section <span class="secno">5.</span> <span class="sec-title">Linked Data Platform Containers</span></a>.
+<p>A conforming <b><dfn id="dfn-ldp-client">LDP client</dfn></b> is a conforming HTTP client [<cite><a class="bibref" href="#bib-HTTP11">HTTP11</a></cite>] that follows the rules defined by LDP in
+<a href="#ldpr" class="sectionRef sec-ref">section <span class="secno">4.</span> <span class="sec-title">Linked Data Platform Resources</span></a> and also
+<a href="#ldpc" class="sectionRef sec-ref">section <span class="secno">5.</span> <span class="sec-title">Linked Data Platform Containers</span></a>.
</p>
-<p>A conforming <b><dfn id="dfn-ldp-server">LDP server</dfn></b> is a conforming HTTP server [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-HTTP11">HTTP11</a></cite>] that follows the rules defined by LDP in
-<a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpr" class="sectionRef sec-ref">section <span class="secno">4.</span> <span class="sec-title">Linked Data Platform Resources</span></a> when it is serving <abbr title="Linked Data Platform Resources">LDPRs</abbr>, and also
-<a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpc" class="sectionRef sec-ref">section <span class="secno">5.</span> <span class="sec-title">Linked Data Platform Containers</span></a> when it is serving <abbr title="Linked Data Platform Containers">LDPCs</abbr>.
+<p>A conforming <b><dfn id="dfn-ldp-server">LDP server</dfn></b> is a conforming HTTP server [<cite><a class="bibref" href="#bib-HTTP11">HTTP11</a></cite>] that follows the rules defined by LDP in
+<a href="#ldpr" class="sectionRef sec-ref">section <span class="secno">4.</span> <span class="sec-title">Linked Data Platform Resources</span></a> when it is serving <abbr title="Linked Data Platform Resources">LDPRs</abbr>, and also
+<a href="#ldpc" class="sectionRef sec-ref">section <span class="secno">5.</span> <span class="sec-title">Linked Data Platform Containers</span></a> when it is serving <abbr title="Linked Data Platform Containers">LDPCs</abbr>.
LDP does not constrain its behavior when serving other HTTP resources.
</p>
</section>
@@ -609,11 +609,11 @@
<p>Linked Data Platform Resources (<dfn id="dfn-linked-data-platform-resources"><abbr title="Linked Data Platform Resources">LDPRs</abbr></dfn>) are HTTP resources
that conform to the simple patterns and conventions in this section.
HTTP requests to access, modify, create or delete <abbr title="Linked Data Platform Resources">LDPRs</abbr> are accepted
- and processed by <a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a>. Most <abbr title="Linked Data Platform Resources">LDPRs</abbr> are domain-specific resources
+ and processed by <a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a>. Most <abbr title="Linked Data Platform Resources">LDPRs</abbr> are domain-specific resources
that contain data for an entity in some domain, which could be
commercial, governmental, scientific, religious, or other.</p>
<p>Some of the rules defined in this document provide
- clarification and refinement of the base Linked Data rules [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-LINKED-DATA">LINKED-DATA</a></cite>];
+ clarification and refinement of the base Linked Data rules [<cite><a class="bibref" href="#bib-LINKED-DATA">LINKED-DATA</a></cite>];
others address additional needs.</p>
<p>The rules for Linked Data Platform Resources address basic
questions such as:</p>
@@ -637,12 +637,12 @@
</p>
<p><abbr title="Linked Data Platform RDF Source">LDP-RS</abbr>'s representations may be too big, one strategy is to break up the response representation
into client consumable chunks called pages. A separate LDP specification outlines the conformance
- rules around pagination [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-LDP-PAGING">LDP-PAGING</a></cite>].
+ rules around pagination [<cite><a class="bibref" href="#bib-LDP-PAGING">LDP-PAGING</a></cite>].
</p>
- <p>An LDP server manages two kinds of <a title="Linked Data Platform Resources" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-resources" class="internalDFN"><abbr title="Linked Data Platform Resources">LDPRs</abbr></a>, those resources who whose state
+ <p>An LDP server manages two kinds of <a title="Linked Data Platform Resources" href="#dfn-linked-data-platform-resources" class="internalDFN"><abbr title="Linked Data Platform Resources">LDPRs</abbr></a>, those resources who whose state
is represented using <abbr title="Resource Description Framework">RDF</abbr> (<abbr title="Linked Data Platform RDF Source">LDP-RS</abbr>) and those using other formats (<abbr title="Linked Data Platform Non-RDF Source">LDP-NR</abbr>). LDP-RSs have the unique
quality that their representation is based on <abbr title="Resource Description Framework">RDF</abbr>, which addresses a number of use cases from web metadata, open data
- models, machine processable information, and automated processing by software agents [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-rdf11-concepts">rdf11-concepts</a></cite>]. LDP-NRs are almost anything
+ models, machine processable information, and automated processing by software agents [<cite><a class="bibref" href="#bib-rdf11-concepts">rdf11-concepts</a></cite>]. LDP-NRs are almost anything
on the Web today: images, HTML pages, word processing documents, spreadsheets, etc. and LDP-RSs hold
metadata associated with LDP-NRs in some cases.
</p>
@@ -650,7 +650,7 @@
<img src="images/ldpr1.png" alt="Sample separation of Linked Data Platform Resource">
<figcaption>Fig. <span class="figno">1</span> <span class="fig-title">Samples of different types of <abbr title="Linked Data Platform Resources">LDPRs</abbr></span></figcaption>
</figure>
- <p>The LDP-NRs and LDP-RSs are simply sub-types of <abbr title="Linked Data Platform Resources">LDPRs</abbr>, as illustrated in <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#fig-ldpr-class" class="fig-ref">Fig. <span class="figno">2</span> <span class="fig-title">Class relationship of types of Linked Data Platform Resources</span></a>.</p>
+ <p>The LDP-NRs and LDP-RSs are simply sub-types of <abbr title="Linked Data Platform Resources">LDPRs</abbr>, as illustrated in <a href="#fig-ldpr-class" class="fig-ref">Fig. <span class="figno">2</span> <span class="fig-title">Class relationship of types of Linked Data Platform Resources</span></a>.</p>
<figure id="fig-ldpr-class">
<img src="images/ldpr2.png" alt="Class Diagram of Linked Data Platform Resource">
<figcaption>Fig. <span class="figno">2</span> <span class="fig-title">Class relationship of types of Linked Data Platform Resources</span></figcaption>
@@ -664,19 +664,19 @@
<section id="ldpr-general" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h4 aria-level="3" role="heading" id="h4_ldpr-general"><span class="secno">4.2.1 </span>General</h4>
- <section id="ldpr-gen-http" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpr-gen-http"><span class="secno">4.2.1.1 </span><a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MUST">MUST</em> at least be HTTP/1.1 conformant servers [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-HTTP11">HTTP11</a></cite>].
+ <section id="ldpr-gen-http" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpr-gen-http"><span class="secno">4.2.1.1 </span><a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MUST">MUST</em> at least be HTTP/1.1 conformant servers [<cite><a class="bibref" href="#bib-HTTP11">HTTP11</a></cite>].
</h5></section><!-- Was 4.2.1 / #ldpr-4_2_1 -->
- <section id="ldpr-gen-binary" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpr-gen-binary"><span class="secno">4.2.1.2 </span><a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MAY">MAY</em> host a mixture of <abbr title="Linked Data Platform Resources">LDPRs</abbr>, <a title="Linked Data Platform RDF Source" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-rdf-source" class="internalDFN">LDP-RSs</a>
- and <a title="Linked Data Platform Non-RDF Source" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-non-rdf-source" class="internalDFN">LDP-NRs</a>. For example, it
- is common for <a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> to need to host binary or text resources
+ <section id="ldpr-gen-binary" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpr-gen-binary"><span class="secno">4.2.1.2 </span><a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MAY">MAY</em> host a mixture of <abbr title="Linked Data Platform Resources">LDPRs</abbr>, <a title="Linked Data Platform RDF Source" href="#dfn-linked-data-platform-rdf-source" class="internalDFN">LDP-RSs</a>
+ and <a title="Linked Data Platform Non-RDF Source" href="#dfn-linked-data-platform-non-rdf-source" class="internalDFN">LDP-NRs</a>. For example, it
+ is common for <a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> to need to host binary or text resources
that do not have useful <abbr title="Resource Description Framework">RDF</abbr> representations.</h5></section><!-- Was 4.2.3 / #ldpr-4_2_3 -->
- <section id="ldpr-gen-etags" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpr-gen-etags"><span class="secno">4.2.1.3 </span><a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP server</a> responses <em class="rfc2119" title="MUST">MUST</em> use entity tags (either
+ <section id="ldpr-gen-etags" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpr-gen-etags"><span class="secno">4.2.1.3 </span><a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP server</a> responses <em class="rfc2119" title="MUST">MUST</em> use entity tags (either
weak or strong ones) as response <code>ETag</code> header values.
</h5></section><!-- Was 4.2.8 / #ldpr-4_2_8 -->
- <section id="ldpr-gen-linktypehdr" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpr-gen-linktypehdr"><span class="secno">4.2.1.4 </span><a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a>
+ <section id="ldpr-gen-linktypehdr" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpr-gen-linktypehdr"><span class="secno">4.2.1.4 </span><a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a>
exposing <abbr title="Linked Data Platform Resources">LDPRs</abbr>
<em class="rfc2119" title="MUST">MUST</em> advertise their LDP support by exposing a HTTP <code>Link</code> header
with a target URI of <code>http://www.w3.org/ns/ldp#Resource</code>, and
@@ -693,28 +693,28 @@
presence of a <var>(subject-URI, <code>rdf:type</code>, <code>ldp:Resource</code>)</var> triple in an <abbr title="Linked Data Platform RDF Source">LDP-RS</abbr>.
The presence of this header asserts that the server complies with the LDP specification's constraints on
HTTP interactions with <abbr title="Linked Data Platform Resources">LDPRs</abbr>, that is
- it asserts that the resource <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpr-gen-etags">has Etags</a>, <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldprs-gen-rdf">has an <abbr title="Resource Description Framework">RDF</abbr> 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 <abbr title="Resource Description Framework">RDF</abbr> representation</a>, and so on,
which is not true of all Web resources served as <abbr title="Resource Description Framework">RDF</abbr> media types.
</p>
<p>
Note:
- <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpr-gen-binary">An LDP server can host a mixture of <abbr title="Linked Data Platform Resources">LDPRs</abbr> and other resources</a>, and therefore there is no implication
+ <a href="#ldpr-gen-binary">An LDP server can host a mixture of <abbr title="Linked Data Platform Resources">LDPRs</abbr> and other resources</a>, and therefore there is no implication
that LDP support advertised on one HTTP <code>Request-URI</code> means that other
resources on the same server are also <abbr title="Linked Data Platform Resources">LDPRs</abbr>. Each HTTP <code>Request-URI</code> needs to be
individually inspected, in the absence of outside information.
</p>
</blockquote>
- <section id="ldpr-gen-defbaseuri" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpr-gen-defbaseuri"><span class="secno">4.2.1.5 </span><a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MUST">MUST</em> assign the default
- base-URI for [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-RFC3987">RFC3987</a></cite>] relative-URI resolution to be the HTTP
+ <section id="ldpr-gen-defbaseuri" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpr-gen-defbaseuri"><span class="secno">4.2.1.5 </span><a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MUST">MUST</em> assign the default
+ base-URI for [<cite><a class="bibref" href="#bib-RFC3987">RFC3987</a></cite>] relative-URI resolution to be the HTTP
<code>Request-URI</code> when the resource already exists, and to the URI of the created resource when the request results
in the creation of a new resource.
</h5></section><!-- Was 4.2.12 / #ldpr-4_2_12 -->
- <section id="ldpr-gen-pubclireqs" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpr-gen-pubclireqs"><span class="secno">4.2.1.6 </span><a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MUST">MUST</em>
- publish any constraints on <a title="LDP client" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-client" class="internalDFN">LDP clients’</a> ability to
+ <section id="ldpr-gen-pubclireqs" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpr-gen-pubclireqs"><span class="secno">4.2.1.6 </span><a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MUST">MUST</em>
+ publish any constraints on <a title="LDP client" href="#dfn-ldp-client" class="internalDFN">LDP clients’</a> ability to
create or update <abbr title="Linked Data Platform Resources">LDPRs</abbr>, by adding a Link header with <code>rel='describedby'</code>
- [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-RFC5988">RFC5988</a></cite>] to all responses to requests which fail due to violation of
+ [<cite><a class="bibref" href="#bib-RFC5988">RFC5988</a></cite>] to all responses to requests which fail due to violation of
those constraints. For example, a server that refuses resource creation
requests via HTTP PUT, POST, or PATCH would return this <code>Link</code> header on its
4xx responses to such requests.
@@ -728,11 +728,11 @@
<section id="ldpr-HTTP_GET" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h4 aria-level="3" role="heading" id="h4_ldpr-HTTP_GET"><span class="secno">4.2.2 </span>HTTP GET</h4>
- <section id="ldpr-get-must" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpr-get-must"><span class="secno">4.2.2.1 </span><a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MUST">MUST</em> support the HTTP <code>GET</code> Method for <abbr title="Linked Data Platform Resources">LDPRs</abbr>.
+ <section id="ldpr-get-must" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpr-get-must"><span class="secno">4.2.2.1 </span><a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MUST">MUST</em> support the HTTP <code>GET</code> Method for <abbr title="Linked Data Platform Resources">LDPRs</abbr>.
</h5></section><!-- Was 4.3.1 / #ldpr-4_3_1 -->
- <section id="ldpr-get-options" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpr-get-options"><span class="secno">4.2.2.2 </span><a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MUST">MUST</em> support the HTTP response headers defined in
- <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpr-HTTP_OPTIONS" class="sectionRef sec-ref">section <span class="secno">4.2.8</span> <span class="sec-title">HTTP OPTIONS</span></a>.
+ <section id="ldpr-get-options" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpr-get-options"><span class="secno">4.2.2.2 </span><a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MUST">MUST</em> support the HTTP response headers defined in
+ <a href="#ldpr-HTTP_OPTIONS" class="sectionRef sec-ref">section <span class="secno">4.2.8</span> <span class="sec-title">HTTP OPTIONS</span></a>.
</h5></section><!-- Was 4.3.2 / #ldpr-4_3_2 -->
</section>
@@ -740,16 +740,16 @@
<section id="ldpr-HTTP_POST" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h4 aria-level="3" role="heading" id="h4_ldpr-HTTP_POST"><span class="secno">4.2.3 </span>HTTP POST</h4>
<p>
- Per [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-HTTP11">HTTP11</a></cite>], this HTTP method is optional and
- this specification does not require <a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> to support it.
+ Per [<cite><a class="bibref" href="#bib-HTTP11">HTTP11</a></cite>], this HTTP method is optional and
+ this specification does not require <a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> to support it.
When an LDP server supports this method,
this specification imposes no new requirements for <abbr title="Linked Data Platform Resources">LDPRs</abbr>.
</p>
- <p>Clients can create <abbr title="Linked Data Platform Resources">LDPRs</abbr> via <code>POST</code> (<a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpc-HTTP_POST" class="sectionRef sec-ref">section <span class="secno">5.2.3</span> <span class="sec-title">HTTP POST</span></a>) to an <abbr title="Linked Data Platform Container">LDPC</abbr>,
- via <code>PUT</code> (<a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpr-HTTP_PUT" class="sectionRef sec-ref">section <span class="secno">4.2.4</span> <span class="sec-title">HTTP PUT</span></a>), or any other methods allowed
+ <p>Clients can create <abbr title="Linked Data Platform Resources">LDPRs</abbr> via <code>POST</code> (<a href="#ldpc-HTTP_POST" class="sectionRef sec-ref">section <span class="secno">5.2.3</span> <span class="sec-title">HTTP POST</span></a>) to an <abbr title="Linked Data Platform Container">LDPC</abbr>,
+ via <code>PUT</code> (<a href="#ldpr-HTTP_PUT" class="sectionRef sec-ref">section <span class="secno">4.2.4</span> <span class="sec-title">HTTP PUT</span></a>), or any other methods allowed
for HTTP resources. Any server-imposed constraints on <abbr title="Linked Data Platform Resource">LDPR</abbr> creation or update
- <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpr-gen-pubclireqs">must be advertised</a> to clients.
+ <a href="#ldpr-gen-pubclireqs">must be advertised</a> to clients.
</p>
</section>
@@ -757,30 +757,30 @@
<section id="ldpr-HTTP_PUT" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h4 aria-level="3" role="heading" id="h4_ldpr-HTTP_PUT"><span class="secno">4.2.4 </span>HTTP PUT</h4>
<p>
- Per [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-HTTP11">HTTP11</a></cite>], this HTTP method is optional and
- this specification does not require <a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> to support it.
+ Per [<cite><a class="bibref" href="#bib-HTTP11">HTTP11</a></cite>], this HTTP method is optional and
+ this specification does not require <a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> to support it.
When an LDP server supports this method,
this specification imposes the following new requirements for <abbr title="Linked Data Platform Resources">LDPRs</abbr>.
</p>
<p>
Any server-imposed constraints on <abbr title="Linked Data Platform Resource">LDPR</abbr> creation or update
- <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpr-gen-pubclireqs">must be advertised</a> to clients.
+ <a href="#ldpr-gen-pubclireqs">must be advertised</a> to clients.
</p>
<section id="ldpr-put-replaceall" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpr-put-replaceall"><span class="secno">4.2.4.1 </span>If a HTTP <code>PUT</code> is accepted on an existing resource,
- <a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MUST">MUST</em>
+ <a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MUST">MUST</em>
replace the entire persistent state of the identified resource with
the entity representation in the body of the request.
- <a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MAY">MAY</em> ignore server managed properties such as <code>dcterms:modified</code>
+ <a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MAY">MAY</em> ignore server managed properties such as <code>dcterms:modified</code>
and <code>dcterms:creator</code> if they are not under
- client control. Any <a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> that wish
+ client control. Any <a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> that wish
to support a more sophisticated merge of data provided by the client
with existing state stored on the server for a resource <em class="rfc2119" title="MUST">MUST</em> use HTTP
<code>PATCH</code>, not HTTP <code>PUT</code>.
</h5></section><!-- Was 4.5.1 / #ldpr-4_5_1 -->
- <section id="ldpr-put-simpleupdate" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpr-put-simpleupdate"><span class="secno">4.2.4.2 </span><a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="SHOULD">SHOULD</em> allow clients to update resources without
+ <section id="ldpr-put-simpleupdate" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpr-put-simpleupdate"><span class="secno">4.2.4.2 </span><a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="SHOULD">SHOULD</em> allow clients to update resources without
requiring detailed knowledge of server-specific constraints.
This is a consequence of the requirement to enable simple creation and modification of <abbr title="Linked Data Platform Resources">LDPRs</abbr>.
</h5></section><!-- Was 4.5.7 / #ldpr-4_5_7 -->
@@ -788,10 +788,10 @@
<section id="ldprs-put-servermanagedprops" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldprs-put-servermanagedprops"><span class="secno">4.2.4.3 </span>
If an otherwise valid HTTP <code>PUT</code> request is received
that attempts to change properties the server does not allow clients to modify,
- <a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MUST">MUST</em>
+ <a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MUST">MUST</em>
respond with a 4xx range status code (typically
409 Conflict).
- <a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="SHOULD">SHOULD</em> provide a corresponding response body containing
+ <a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="SHOULD">SHOULD</em> provide a corresponding response body containing
information about which properties could not be
persisted.
The format of the 4xx response body is not constrained by LDP.
@@ -805,26 +805,26 @@
<section id="ldprs-put-failed" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldprs-put-failed"><span class="secno">4.2.4.4 </span>
If an otherwise valid HTTP <code>PUT</code> request is received that contains properties the server
chooses not to persist, e.g. unknown content,
- <a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MUST">MUST</em> respond with an appropriate 4xx range status code
- [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-HTTP11">HTTP11</a></cite>].
- <a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="SHOULD">SHOULD</em> provide a corresponding response body containing
+ <a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MUST">MUST</em> respond with an appropriate 4xx range status code
+ [<cite><a class="bibref" href="#bib-HTTP11">HTTP11</a></cite>].
+ <a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="SHOULD">SHOULD</em> provide a corresponding response body containing
information about which properties could not be
persisted.
The format of the 4xx response body is not constrained by LDP. LDP servers
- expose these application-specific constraints as described in <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpr-general" class="sectionRef sec-ref">section <span class="secno">4.2.1</span> <span class="sec-title">General</span></a>.
+ expose these application-specific constraints as described in <a href="#ldpr-general" class="sectionRef sec-ref">section <span class="secno">4.2.1</span> <span class="sec-title">General</span></a>.
</h5></section><!-- Was 4.5.4 / #ldpr-4_5_4 -->
- <section id="ldpr-put-precond" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpr-put-precond"><span class="secno">4.2.4.5 </span><a title="LDP client" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-client" class="internalDFN">LDP clients</a> <em class="rfc2119" title="SHOULD">SHOULD</em> use the HTTP <code>If-Match</code>
+ <section id="ldpr-put-precond" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpr-put-precond"><span class="secno">4.2.4.5 </span><a title="LDP client" href="#dfn-ldp-client" class="internalDFN">LDP clients</a> <em class="rfc2119" title="SHOULD">SHOULD</em> use the HTTP <code>If-Match</code>
header and HTTP <code>ETags</code> to ensure it isn’t
modifying a resource that has changed since the client last retrieved
- its representation. <a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="SHOULD">SHOULD</em> require the HTTP <code>If-Match</code> header and HTTP <code>ETags</code>
- to detect collisions. <a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MUST">MUST</em> respond with status code 412
+ its representation. <a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="SHOULD">SHOULD</em> require the HTTP <code>If-Match</code> header and HTTP <code>ETags</code>
+ to detect collisions. <a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MUST">MUST</em> respond with status code 412
(Condition Failed) if <code>ETag</code>s fail to match when there are no other
- errors with the request [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-HTTP11">HTTP11</a></cite>]. <a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> that require conditional requests <em class="rfc2119" title="MUST">MUST</em> respond with status code 428
- (Precondition Required) when the absence of a precondition is the only reason for rejecting the request [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-RFC6585">RFC6585</a></cite>].
+ errors with the request [<cite><a class="bibref" href="#bib-HTTP11">HTTP11</a></cite>]. <a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> that require conditional requests <em class="rfc2119" title="MUST">MUST</em> respond with status code 428
+ (Precondition Required) when the absence of a precondition is the only reason for rejecting the request [<cite><a class="bibref" href="#bib-RFC6585">RFC6585</a></cite>].
</h5></section><!-- Was 4.5.2 / #ldpr-4_5_2 -->
- <section id="ldpr-put-create" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpr-put-create"><span class="secno">4.2.4.6 </span><a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MAY">MAY</em> choose to allow the creation of new resources using HTTP <code>PUT</code>.
+ <section id="ldpr-put-create" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpr-put-create"><span class="secno">4.2.4.6 </span><a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MAY">MAY</em> choose to allow the creation of new resources using HTTP <code>PUT</code>.
</h5></section><!-- Was 4.5.6 / #ldpr-4_5_6 -->
</section>
@@ -832,14 +832,14 @@
<section id="ldpr-HTTP_DELETE" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h4 aria-level="3" role="heading" id="h4_ldpr-HTTP_DELETE"><span class="secno">4.2.5 </span>HTTP DELETE</h4>
<p>
- Per [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-HTTP11">HTTP11</a></cite>], this HTTP method is optional and
- this specification does not require <a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> to support it.
+ Per [<cite><a class="bibref" href="#bib-HTTP11">HTTP11</a></cite>], this HTTP method is optional and
+ this specification does not require <a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> to support it.
When an LDP server supports this method,
this specification imposes the following new requirements for <abbr title="Linked Data Platform Resources">LDPRs</abbr>.
</p>
<p>Additional requirements on HTTP <code>DELETE</code> of <abbr title="Linked Data Platform Resources">LDPRs</abbr> within containers can be found in
- <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpc-HTTP_DELETE" class="sectionRef sec-ref">section <span class="secno">5.2.5</span> <span class="sec-title">HTTP DELETE</span></a>.
+ <a href="#ldpc-HTTP_DELETE" class="sectionRef sec-ref">section <span class="secno">5.2.5</span> <span class="sec-title">HTTP DELETE</span></a>.
</p>
</section>
@@ -847,28 +847,28 @@
<h4 aria-level="3" role="heading" id="h4_ldpr-HTTP_HEAD"><span class="secno">4.2.6 </span>HTTP HEAD</h4>
<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="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpr-HTTP_GET" class="sec-ref"><span class="secno">4.2.2</span> <span class="sec-title">HTTP GET</span></a>
- and <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpr-HTTP_OPTIONS" class="sec-ref"><span class="secno">4.2.8</span> <span class="sec-title">HTTP OPTIONS</span></a>.</p>
- <section id="ldpr-head-must" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpr-head-must"><span class="secno">4.2.6.1 </span><a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MUST">MUST</em> support the HTTP <code>HEAD</code> method.
+ Thus, implementers should also carefully read sections <a href="#ldpr-HTTP_GET" class="sec-ref"><span class="secno">4.2.2</span> <span class="sec-title">HTTP GET</span></a>
+ and <a href="#ldpr-HTTP_OPTIONS" class="sec-ref"><span class="secno">4.2.8</span> <span class="sec-title">HTTP OPTIONS</span></a>.</p>
+ <section id="ldpr-head-must" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpr-head-must"><span class="secno">4.2.6.1 </span><a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MUST">MUST</em> support the HTTP <code>HEAD</code> method.
</h5></section><!-- Was 4.7.1 / #ldpr-4_7_1 -->
</section>
<section id="ldpr-HTTP_PATCH" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h4 aria-level="3" role="heading" id="h4_ldpr-HTTP_PATCH"><span class="secno">4.2.7 </span>HTTP PATCH</h4>
<p>
- Per [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-RFC5789">RFC5789</a></cite>], this HTTP method is optional and
- this specification does not require <a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> to support it.
+ Per [<cite><a class="bibref" href="#bib-RFC5789">RFC5789</a></cite>], this HTTP method is optional and
+ this specification does not require <a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> to support it.
When an LDP server supports this method,
this specification imposes the following new requirements for <abbr title="Linked Data Platform Resources">LDPRs</abbr>.
</p>
<p>
Any server-imposed constraints on <abbr title="Linked Data Platform Resource">LDPR</abbr> creation or update
- <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpr-gen-pubclireqs">must be advertised</a> to clients.
+ <a href="#ldpr-gen-pubclireqs">must be advertised</a> to clients.
</p>
- <section id="ldpr-patch-acceptpatch" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpr-patch-acceptpatch"><span class="secno">4.2.7.1 </span><a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> that support <code>PATCH</code> <em class="rfc2119" title="MUST">MUST</em>
- include an <code>Accept-Patch</code> HTTP response header [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-RFC5789">RFC5789</a></cite>] on HTTP <code>OPTIONS</code>
+ <section id="ldpr-patch-acceptpatch" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpr-patch-acceptpatch"><span class="secno">4.2.7.1 </span><a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> that support <code>PATCH</code> <em class="rfc2119" title="MUST">MUST</em>
+ include an <code>Accept-Patch</code> HTTP response header [<cite><a class="bibref" href="#bib-RFC5789">RFC5789</a></cite>] on HTTP <code>OPTIONS</code>
requests, listing patch document media type(s) supported by the server.
</h5></section><!-- Was 4.8.4 / #ldpr-4_8_4 -->
@@ -877,16 +877,16 @@
<section id="ldpr-HTTP_OPTIONS" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h4 aria-level="3" role="heading" id="h4_ldpr-HTTP_OPTIONS"><span class="secno">4.2.8 </span>HTTP OPTIONS</h4>
<p>This specification imposes the following new requirements on HTTP <code>OPTIONS</code> for <abbr title="Linked Data Platform Resources">LDPRs</abbr>
- beyond those in [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-HTTP11">HTTP11</a></cite>]. Other sections of this specification, for example
- <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpr-HTTP_PATCH">PATCH</a>,
- <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#header-accept-post">Accept-Post</a>,
+ beyond those in [<cite><a class="bibref" href="#bib-HTTP11">HTTP11</a></cite>]. Other sections of this specification, for example
+ <a href="#ldpr-HTTP_PATCH">PATCH</a>,
+ <a href="#header-accept-post">Accept-Post</a>,
add other requirements on <code>OPTIONS</code> responses.
</p>
- <section id="ldpr-options-must" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpr-options-must"><span class="secno">4.2.8.1 </span><a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MUST">MUST</em> support the HTTP <code>OPTIONS</code> method.
+ <section id="ldpr-options-must" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpr-options-must"><span class="secno">4.2.8.1 </span><a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MUST">MUST</em> support the HTTP <code>OPTIONS</code> method.
</h5></section><!-- Was 4.9.1 / #ldpr-4_9_1 -->
- <section id="ldpr-options-allow" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpr-options-allow"><span class="secno">4.2.8.2 </span><a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MUST">MUST</em> indicate their support for HTTP Methods by
+ <section id="ldpr-options-allow" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpr-options-allow"><span class="secno">4.2.8.2 </span><a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MUST">MUST</em> indicate their support for HTTP Methods by
responding to a HTTP <code>OPTIONS</code> request on the <abbr title="Linked Data Platform Resource">LDPR</abbr>’s URL with the HTTP
Method tokens in the HTTP response header <code>Allow</code>.
</h5></section><!-- Was 4.9.2 / #ldpr-4_9_2 -->
@@ -898,53 +898,53 @@
<section id="ldprs" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h3 aria-level="2" role="heading" id="h3_ldprs"><span class="secno">4.3 </span><abbr title="Resource Description Framework">RDF</abbr> Source</h3>
-<p>The following section contains normative clauses for <a title="" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-rdf-source" class="internalDFN">Linked Data Platform <abbr title="Resource Description Framework">RDF</abbr> Source</a>.</p>
+<p>The following section contains normative clauses for <a title="" href="#dfn-linked-data-platform-rdf-source" class="internalDFN">Linked Data Platform <abbr title="Resource Description Framework">RDF</abbr> Source</a>.</p>
<section id="ldprs-general" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h4 aria-level="3" role="heading" id="h4_ldprs-general"><span class="secno">4.3.1 </span>General</h4>
- <section id="ldprs-are-ldpr" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldprs-are-ldpr"><span class="secno">4.3.1.1 </span>Each <a title="Linked Data Platform RDF Source" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-rdf-source" class="internalDFN">LDP <abbr title="Resource Description Framework">RDF</abbr> Source</a> <em class="rfc2119" title="MUST">MUST</em> also be
- a conforming <a title="Linked Data Platform Resource" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-resource" class="internalDFN">LDP Resource</a> in <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpr-resource" class="sectionRef sec-ref">section <span class="secno">4.2</span> <span class="sec-title">Resource</span></a> along the
- following restrictions in this section. <a title="" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-client" class="internalDFN">LDP client</a>s <em class="rfc2119" title="MAY">MAY</em> infer the following triple:
+ <section id="ldprs-are-ldpr" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldprs-are-ldpr"><span class="secno">4.3.1.1 </span>Each <a title="Linked Data Platform RDF Source" href="#dfn-linked-data-platform-rdf-source" class="internalDFN">LDP <abbr title="Resource Description Framework">RDF</abbr> Source</a> <em class="rfc2119" title="MUST">MUST</em> also be
+ a conforming <a title="Linked Data Platform Resource" href="#dfn-linked-data-platform-resource" class="internalDFN">LDP Resource</a> in <a href="#ldpr-resource" class="sectionRef sec-ref">section <span class="secno">4.2</span> <span class="sec-title">Resource</span></a> along the
+ following restrictions in this section. <a title="" href="#dfn-ldp-client" class="internalDFN">LDP client</a>s <em class="rfc2119" title="MAY">MAY</em> infer the following triple:
whose subject is <code>ldp:RDFSource</code>,
whose predicate is <code>rdfs:subClassOf</code>,
and whose object is <code>ldp:Resource</code>,
but there is no requirement to materialize this triple in the <abbr title="Linked Data Platform RDF Source">LDP-RS</abbr> representation.
</h5></section>
- <section id="ldprs-gen-atleast1rdftype" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldprs-gen-atleast1rdftype"><span class="secno">4.3.1.2 </span><a title="Linked Data Platform RDF Source" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-rdf-source" class="internalDFN">LDP-RSs</a> representations <em class="rfc2119" title="SHOULD">SHOULD</em> have at least one <code>rdf:type</code>
+ <section id="ldprs-gen-atleast1rdftype" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldprs-gen-atleast1rdftype"><span class="secno">4.3.1.2 </span><a title="Linked Data Platform RDF Source" href="#dfn-linked-data-platform-rdf-source" class="internalDFN">LDP-RSs</a> representations <em class="rfc2119" title="SHOULD">SHOULD</em> have at least one <code>rdf:type</code>
set explicitly. This makes the representations much more useful to
client applications that don’t support inferencing.
</h5></section><!-- Was 4.2.5 / #ldpr-4_2_5 -->
<section id="ldprs-rdftype" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldprs-rdftype"><span class="secno">4.3.1.3 </span>The representation of an <abbr title="Linked Data Platform RDF Source">LDP-RS</abbr> <em class="rfc2119" title="MAY">MAY</em> have an <code>rdf:type</code>
- of only one of <code>ldp:RDFSource</code> for <a title="" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-rdf-source" class="internalDFN">Linked Data Platform <abbr title="Resource Description Framework">RDF</abbr> Source</a>.
+ of only one of <code>ldp:RDFSource</code> for <a title="" href="#dfn-linked-data-platform-rdf-source" class="internalDFN">Linked Data Platform <abbr title="Resource Description Framework">RDF</abbr> Source</a>.
</h5></section><!-- Was 5.2.7 / #ldpc-5_2_7 -->
- <section id="ldprs-gen-rdf" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldprs-gen-rdf"><span class="secno">4.3.1.4 </span><a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MUST">MUST</em> provide an <abbr title="Resource Description Framework">RDF</abbr> representation for <a title="Linked Data Platform RDF Source" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-rdf-source" class="internalDFN">LDP-RSs</a>.
+ <section id="ldprs-gen-rdf" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldprs-gen-rdf"><span class="secno">4.3.1.4 </span><a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MUST">MUST</em> provide an <abbr title="Resource Description Framework">RDF</abbr> representation for <a title="Linked Data Platform RDF Source" href="#dfn-linked-data-platform-rdf-source" class="internalDFN">LDP-RSs</a>.
The HTTP <code>Request-URI</code> of the <abbr title="Linked Data Platform RDF Source">LDP-RS</abbr> is typically the subject of most triples in the response.
</h5></section><!-- Was 4.2.2 / #ldpr-4_2_2 -->
- <section id="ldprs-gen-reusevocab" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldprs-gen-reusevocab"><span class="secno">4.3.1.5 </span><a title="Linked Data Platform RDF Source" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-rdf-source" class="internalDFN">LDP-RSs</a> <em class="rfc2119" title="SHOULD">SHOULD</em> reuse existing vocabularies instead of creating
+ <section id="ldprs-gen-reusevocab" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldprs-gen-reusevocab"><span class="secno">4.3.1.5 </span><a title="Linked Data Platform RDF Source" href="#dfn-linked-data-platform-rdf-source" class="internalDFN">LDP-RSs</a> <em class="rfc2119" title="SHOULD">SHOULD</em> reuse existing vocabularies instead of creating
their own duplicate vocabulary terms. In addition to this general rule, some specific cases are
covered by other conformance rules.
</h5></section><!-- Was 4.2.4 / #ldpr-4_2_4 -->
- <section id="ldprs-gen-reusevocabsuchas" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldprs-gen-reusevocabsuchas"><span class="secno">4.3.1.6 </span><a title="Linked Data Platform RDF Source" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-rdf-source" class="internalDFN">LDP-RSs</a> predicates <em class="rfc2119" title="SHOULD">SHOULD</em> use standard vocabularies such as Dublin Core
- [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-DC-TERMS">DC-TERMS</a></cite>], <abbr title="Resource Description Framework">RDF</abbr> [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-rdf11-concepts">rdf11-concepts</a></cite>] and <abbr title="Resource Description Framework">RDF</abbr> Schema [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-rdf-schema">rdf-schema</a></cite>], whenever
+ <section id="ldprs-gen-reusevocabsuchas" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldprs-gen-reusevocabsuchas"><span class="secno">4.3.1.6 </span><a title="Linked Data Platform RDF Source" href="#dfn-linked-data-platform-rdf-source" class="internalDFN">LDP-RSs</a> predicates <em class="rfc2119" title="SHOULD">SHOULD</em> use standard vocabularies such as Dublin Core
+ [<cite><a class="bibref" href="#bib-DC-TERMS">DC-TERMS</a></cite>], <abbr title="Resource Description Framework">RDF</abbr> [<cite><a class="bibref" href="#bib-rdf11-concepts">rdf11-concepts</a></cite>] and <abbr title="Resource Description Framework">RDF</abbr> Schema [<cite><a class="bibref" href="#bib-rdf-schema">rdf-schema</a></cite>], whenever
possible.
</h5></section><!-- Was 4.2.4.1 / #ldpr-4_2_4_1 -->
<section id="ldp-cli-multitype" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldp-cli-multitype"><span class="secno">4.3.1.7 </span>In the absence of special knowledge of the application or domain,
- <a title="LDP client" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-client" class="internalDFN">LDP clients</a> <em class="rfc2119" title="MUST">MUST</em> assume that any <abbr title="Linked Data Platform RDF Source">LDP-RS</abbr> can have multiple values for <code>rdf:type</code>.
+ <a title="LDP client" href="#dfn-ldp-client" class="internalDFN">LDP clients</a> <em class="rfc2119" title="MUST">MUST</em> assume that any <abbr title="Linked Data Platform RDF Source">LDP-RS</abbr> can have multiple values for <code>rdf:type</code>.
</h5></section> <!-- Was 4.3.5 / #ldpr-4_3_5 -->
<section id="ldpr-cli-typeschange" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpr-cli-typeschange"><span class="secno">4.3.1.8 </span>In the absence of special knowledge of the application or domain,
- <a title="LDP client" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-client" class="internalDFN">LDP clients</a> <em class="rfc2119" title="MUST">MUST</em> assume that the <code>rdf:type</code> values
+ <a title="LDP client" href="#dfn-ldp-client" class="internalDFN">LDP clients</a> <em class="rfc2119" title="MUST">MUST</em> assume that the <code>rdf:type</code> values
of a given <abbr title="Linked Data Platform RDF Source">LDP-RS</abbr> can change over time.
</h5></section> <!-- Was 4.3.6 / #ldpr-4_3_6 -->
- <section id="ldpr-cli-openpreds" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpr-cli-openpreds"><span class="secno">4.3.1.9 </span><a title="LDP client" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-client" class="internalDFN">LDP clients</a> <em class="rfc2119" title="SHOULD">SHOULD</em> always assume that the set of predicates for a
+ <section id="ldpr-cli-openpreds" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpr-cli-openpreds"><span class="secno">4.3.1.9 </span><a title="LDP client" href="#dfn-ldp-client" class="internalDFN">LDP clients</a> <em class="rfc2119" title="SHOULD">SHOULD</em> always assume that the set of predicates for a
<abbr title="Linked Data Platform RDF Source">LDP-RS</abbr> of a particular type at an arbitrary server is open, in the
sense that different resources of the same type may not all have the
same set of predicates in their triples, and the set of predicates that
@@ -952,50 +952,51 @@
set.
</h5></section> <!-- Was 4.5.3 / #ldpr-ldpr-4_5_3 -->
- <section id="ldprs-gen-noinferencing" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldprs-gen-noinferencing"><span class="secno">4.3.1.10 </span><a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a>
+ <section id="ldprs-gen-noinferencing" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldprs-gen-noinferencing"><span class="secno">4.3.1.10 </span><a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a>
<em class="rfc2119" title="MUST NOT">MUST NOT</em> require LDP clients to implement inferencing in order to recognize the subset
of content defined by LDP. Other specifications built on top of LDP may require clients
- to implement inferencing [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-rdf11-concepts">rdf11-concepts</a></cite>]. The practical implication is that all content defined by LDP
+ to implement inferencing [<cite><a class="bibref" href="#bib-rdf11-concepts">rdf11-concepts</a></cite>]. The practical implication is that all content defined by LDP
must be explicitly represented, unless noted otherwise within this document.
</h5></section><!-- Was 4.2.11 / #ldpr-4_2_11 -->
<section id="ldpr-cli-preservetriples" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpr-cli-preservetriples"><span class="secno">4.3.1.11 </span>
- A <a title="LDP client" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-client" class="internalDFN">LDP client</a> <em class="rfc2119" title="MUST">MUST</em> preserve all triples retrieved from an <abbr title="Linked Data Platform RDF Source">LDP-RS</abbr> using HTTP <code>GET</code> that
+ A <a title="LDP client" href="#dfn-ldp-client" class="internalDFN">LDP client</a> <em class="rfc2119" title="MUST">MUST</em> preserve all triples retrieved from an <abbr title="Linked Data Platform RDF Source">LDP-RS</abbr> using HTTP <code>GET</code> that
it doesn’t change whether it understands the predicates or not, when
its intent is to perform an update using HTTP <code>PUT</code>. The use of HTTP
<code>PATCH</code> instead of HTTP <code>PUT</code> for update avoids this burden for clients
- [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-RFC5789">RFC5789</a></cite>].
+ [<cite><a class="bibref" href="#bib-RFC5789">RFC5789</a></cite>].
</h5></section> <!-- Was 4.5.5 / #ldpr-ldpr-4_5_5 -->
<section id="ldpr-cli-can-hint" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpr-cli-can-hint"><span class="secno">4.3.1.12 </span>
- <a title="LDP client" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-client" class="internalDFN">LDP clients</a> <em class="rfc2119" title="MAY">MAY</em>
+ <a title="LDP client" href="#dfn-ldp-client" class="internalDFN">LDP clients</a> <em class="rfc2119" title="MAY">MAY</em>
provide LDP-defined hints that allow servers to optimize the content of responses.
- <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#prefer-parameters" class="sectionRef sec-ref">section <span class="secno">7.2</span> <span class="sec-title">Preferences on the Prefer Request Header</span></a> defines hints that apply to
- <a title="Linked Data Platform RDF Source" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-rdf-source" class="internalDFN">LDP-RSs</a>.
+ <a href="#prefer-parameters" class="sectionRef sec-ref">section <span class="secno">7.2</span> <span class="sec-title">Preferences on the Prefer Request Header</span></a> defines hints that apply to
+ <a title="Linked Data Platform RDF Source" href="#dfn-linked-data-platform-rdf-source" class="internalDFN">LDP-RSs</a>.
</h5></section>
<section id="ldpr-cli-hints-ignorable" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpr-cli-hints-ignorable"><span class="secno">4.3.1.13 </span>
- <a title="LDP client" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-client" class="internalDFN">LDP clients</a> <em class="rfc2119" title="MUST">MUST</em>
+ <a title="LDP client" href="#dfn-ldp-client" class="internalDFN">LDP clients</a> <em class="rfc2119" title="MUST">MUST</em>
be capable of processing responses formed by an LDP server that ignores hints,
including LDP-defined hints.
</h5></section>
+ <div class="atrisk" id="atrisk-paging"><p class="atrisktext">Feature At Risk</p>
+ <p>The LDP Working Group proposes incorporation of the following clause to make LDP clients paging aware:</p>
<section id="ldpr-cli-paging" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpr-cli-paging"><span class="secno">4.3.1.14 </span>
- <div class="atrisk" id="atrisk-paging"><p class="atrisktext">Feature At Risk</p>
- <p>The LDP Working Group proposes incorporation of the following clause to make LDP clients paging aware:</p>
- <a title="LDP client" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-client" class="internalDFN">LDP clients</a> <em class="rfc2119" title="SHOULD">SHOULD</em>
+ <a title="LDP client" href="#dfn-ldp-client" class="internalDFN">LDP clients</a> <em class="rfc2119" title="SHOULD">SHOULD</em>
be capable of processing successful HTTP <code>GET</code> responses formed by an LDP server
that independently initiated paging, returning a page of representation instead of full resource
- representation [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-LDP-PAGING">LDP-PAGING</a></cite>].
- </div></h5>
+ representation [<cite><a class="bibref" href="#bib-LDP-PAGING">LDP-PAGING</a></cite>].
+ </h5>
</section>
+ </div>
</section> <!-- ldprs-general -->
<section id="ldprs-HTTP_GET" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h4 aria-level="3" role="heading" id="h4_ldprs-HTTP_GET"><span class="secno">4.3.2 </span>HTTP GET</h4>
- <section id="ldprs-get-turtle" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldprs-get-turtle"><span class="secno">4.3.2.1 </span><a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MUST">MUST</em> provide a <code>text/turtle</code>
- representation of the requested <a title="Linked Data Platform RDF Source" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-rdf-source" class="internalDFN"><abbr title="Linked Data Platform RDF Source">LDP-RS</abbr></a> [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-turtle">turtle</a></cite>].
+ <section id="ldprs-get-turtle" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldprs-get-turtle"><span class="secno">4.3.2.1 </span><a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MUST">MUST</em> provide a <code>text/turtle</code>
+ representation of the requested <a title="Linked Data Platform RDF Source" href="#dfn-linked-data-platform-rdf-source" class="internalDFN"><abbr title="Linked Data Platform RDF Source">LDP-RS</abbr></a> [<cite><a class="bibref" href="#bib-turtle">turtle</a></cite>].
</h5></section><!-- Was 4.3.3 / #ldpr-4_3_3 -->
</section> <!-- ldprs-HTTP_GET -->
@@ -1005,15 +1006,15 @@
<section id="ldpnr" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h3 aria-level="2" role="heading" id="h3_ldpnr"><span class="secno">4.4 </span>Non-<abbr title="Resource Description Framework">RDF</abbr> Source</h3>
-<p>The following section contains normative clauses for <a title="" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-non-rdf-source" class="internalDFN">Linked Data Platform Non-<abbr title="Resource Description Framework">RDF</abbr> Source</a>.</p>
+<p>The following section contains normative clauses for <a title="" href="#dfn-linked-data-platform-non-rdf-source" class="internalDFN">Linked Data Platform Non-<abbr title="Resource Description Framework">RDF</abbr> Source</a>.</p>
<section id="ldpnr-general" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h4 aria-level="3" role="heading" id="h4_ldpnr-general"><span class="secno">4.4.1 </span>General</h4>
- <section id="ldpnr-are-ldpr" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpnr-are-ldpr"><span class="secno">4.4.1.1 </span>Each <a title="Linked Data Platform Non-RDF Source" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-non-rdf-source" class="internalDFN">LDP Non-<abbr title="Resource Description Framework">RDF</abbr> Source</a> <em class="rfc2119" title="MUST">MUST</em> also be
- a conforming <a title="Linked Data Platform Resource" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-resource" class="internalDFN">LDP Resource</a> in <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpr-resource" class="sectionRef sec-ref">section <span class="secno">4.2</span> <span class="sec-title">Resource</span></a>.
- <a title="Linked Data Platform Non-RDF Source" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-non-rdf-source" class="internalDFN">LDP Non-<abbr title="Resource Description Framework">RDF</abbr> Source</a> may not be able to fully express their
- state using <abbr title="Resource Description Framework">RDF</abbr>. [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-rdf11-concepts">rdf11-concepts</a></cite>]
+ <section id="ldpnr-are-ldpr" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpnr-are-ldpr"><span class="secno">4.4.1.1 </span>Each <a title="Linked Data Platform Non-RDF Source" href="#dfn-linked-data-platform-non-rdf-source" class="internalDFN">LDP Non-<abbr title="Resource Description Framework">RDF</abbr> Source</a> <em class="rfc2119" title="MUST">MUST</em> also be
+ a conforming <a title="Linked Data Platform Resource" href="#dfn-linked-data-platform-resource" class="internalDFN">LDP Resource</a> in <a href="#ldpr-resource" class="sectionRef sec-ref">section <span class="secno">4.2</span> <span class="sec-title">Resource</span></a>.
+ <a title="Linked Data Platform Non-RDF Source" href="#dfn-linked-data-platform-non-rdf-source" class="internalDFN">LDP Non-<abbr title="Resource Description Framework">RDF</abbr> Source</a> may not be able to fully express their
+ state using <abbr title="Resource Description Framework">RDF</abbr>. [<cite><a class="bibref" href="#bib-rdf11-concepts">rdf11-concepts</a></cite>]
</h5></section>
</section> <!-- ldpnr Non-RDF Source-->
@@ -1040,7 +1041,7 @@
<li>Where can I GET a list of existing resources?</li>
<li>How do I get information about the members along with the container?</li>
<li>How can I ensure the resource data is easy to query?</li>
- <li>How is the order of the container entries expressed? [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-LDP-PAGING">LDP-PAGING</a></cite>]</li>
+ <li>How is the order of the container entries expressed? [<cite><a class="bibref" href="#bib-LDP-PAGING">LDP-PAGING</a></cite>]</li>
</ol>
<p>
This document defines the representation and behavior of containers
@@ -1048,10 +1049,10 @@
to support a variety of use cases, all that support a base set of capabilities.
The contents of a container is
defined by a set of triples in its representation (and state) called
- the <a title="Containment triples" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-containment-triples" class="internalDFN">containment triples</a> that follow a fixed pattern.
+ the <a title="Containment triples" href="#dfn-containment-triples" class="internalDFN">containment triples</a> that follow a fixed pattern.
Additional types of containers allow for the set of members of a container to be
defined by a set of triples in its representation called
- the <a title="Membership triples" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-membership-triples" class="internalDFN">membership triples</a> that follow a consistent pattern
+ the <a title="Membership triples" href="#dfn-membership-triples" class="internalDFN">membership triples</a> that follow a consistent pattern
(see the linked-to definition for the possible patterns).
The membership triples of a container all
have the same predicate, called the membership predicate,
@@ -1100,7 +1101,7 @@
A POST to this container will create a new resource
and add it to the list of contained resources by adding a new containment triple
to the container. This type of container is also referred to as
- <a title="" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-basic-container" class="internalDFN">Linked Data Platform Basic Container</a>.</p>
+ <a title="" href="#dfn-linked-data-platform-basic-container" class="internalDFN">Linked Data Platform Basic Container</a>.</p>
<p>Sometimes it is useful to use a subject
other than the container itself as the consistent membership value, and/or to use
@@ -1179,7 +1180,7 @@
<p>The essential structure of the container is
the same, but in this example, the consistent membership value
- (<a title="Membership triples" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-membership-triples" class="internalDFN">membership-constant-URI</a>, still in the subject position) is not the
+ (<a title="Membership triples" href="#dfn-membership-triples" class="internalDFN">membership-constant-URI</a>, still in the subject position) is not the
container itself – it is a separate net worth resource. The
membership predicates are <code>o:asset</code> and <code>o:liability</code> – predicates
from the domain model. A POST of an asset representation to the asset container will create a new
@@ -1193,12 +1194,12 @@
and <code>http://example.org/netWorth/nw1/liabilityContainer/</code> container
resources allows both assets and liabilities to be created.
</p>
- <p>This type of container is referred to as an <a title="Linked Data Platform Direct Container" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-direct-container" class="internalDFN">LDP Direct Container</a>.
- <a title="Linked Data Platform Direct Container" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-direct-container" class="internalDFN">LDP Direct Container</a> adds the concept of <a title="Membership" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-membership" class="internalDFN">membership</a>
- and flexibilty on how to specify the <a title="Membership triples" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-membership-triples" class="internalDFN">membership triples</a>.
+ <p>This type of container is referred to as an <a title="Linked Data Platform Direct Container" href="#dfn-linked-data-platform-direct-container" class="internalDFN">LDP Direct Container</a>.
+ <a title="Linked Data Platform Direct Container" href="#dfn-linked-data-platform-direct-container" class="internalDFN">LDP Direct Container</a> adds the concept of <a title="Membership" href="#dfn-membership" class="internalDFN">membership</a>
+ and flexibilty on how to specify the <a title="Membership triples" href="#dfn-membership-triples" class="internalDFN">membership triples</a>.
</p>
- <p>As seen in the <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpc-ex-membership-subj"><code>assetContainer/</code> example</a>,
+ <p>As seen in the <a href="#ldpc-ex-membership-subj"><code>assetContainer/</code> example</a>,
clients cannot correctly guess
at the membership triples, so the example includes this information in
triples whose subject is the <abbr title="Linked Data Platform Container">LDPC</abbr> resource itself.
@@ -1208,7 +1209,7 @@
representations. When doing this, a preference would be for <abbr title="Resource Description Framework">RDF</abbr> 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 [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-rdf11-concepts">rdf11-concepts</a></cite>]. Generally, the membership triples belong
+ would be represented within the liability and asset containers [<cite><a class="bibref" href="#bib-rdf11-concepts">rdf11-concepts</a></cite>]. Generally, the membership triples belong
to the representation of an <abbr title="Linked Data Platform RDF Source">LDP-RS</abbr> and the containment triples belong to the representation of the <abbr title="Linked Data Platform Container">LDPC</abbr>.
</p>
@@ -1248,13 +1249,13 @@
form <code>(<>, foaf:primaryTopic, topic-URI)</code> to inform the server which URI to use
(<code>topic-URI</code>) in the new membership triple.</p>
- <p>This type of container is also referred to as a <a title="Linked Data Platform Indirect Container" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-indirect-container" class="internalDFN">LDP Indirect Container</a>.
- It is similar to an <a title="Linked Data Platform Direct Container" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-direct-container" class="internalDFN">LDP Direct Container</a>
+ <p>This type of container is also referred to as a <a title="Linked Data Platform Indirect Container" href="#dfn-linked-data-platform-indirect-container" class="internalDFN">LDP Indirect Container</a>.
+ It is similar to an <a title="Linked Data Platform Direct Container" href="#dfn-linked-data-platform-direct-container" class="internalDFN">LDP Direct Container</a>
but it provides an indirection to add (via a create request) as member any resource,
such as a URI representing a real-world object,
that is different from the document that is created.</p>
- <p><a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#fig-ldpc-types" class="fig-ref">Fig. <span class="figno">3</span> <span class="fig-title">Class relationship of types of Linked Data Platform Containers</span></a> illustrates the 3 types: Container, Basic Container and Direct Container, along
+ <p><a href="#fig-ldpc-types" class="fig-ref">Fig. <span class="figno">3</span> <span class="fig-title">Class relationship of types of Linked Data Platform Containers</span></a> illustrates the 3 types: Container, Basic Container and Direct Container, along
with their class relationship to types of <abbr title="Linked Data Platform Resources">LDPRs</abbr>.</p>
<figure id="fig-ldpc-types">
@@ -1262,11 +1263,11 @@
<figcaption>Fig. <span class="figno">3</span> <span class="fig-title">Class relationship of types of Linked Data Platform Containers</span></figcaption>
</figure>
- <p>The following table illustrates some differences between <a title="membership" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-membership" class="internalDFN">membership</a> and
- <a title="containment" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-containment" class="internalDFN">containment</a> triples. For details on the normative behavior, see appropriate sections
+ <p>The following table illustrates some differences between <a title="membership" href="#dfn-membership" class="internalDFN">membership</a> and
+ <a title="containment" href="#dfn-containment" class="internalDFN">containment</a> triples. For details on the normative behavior, see appropriate sections
below.
</p>
- <table border="1" id="ldpc-mbrcntdiff">
+ <table style="border: 1px solid gray" id="ldpc-mbrcntdiff">
<thead><tr><th rowspan="2">Completed Request</th><th colspan="2">Effects</th></tr>
<tr class="oddrow"><th>Membership</th><th>Containment</th></tr></thead>
<tbody><tr><td><abbr title="Linked Data Platform Resource">LDPR</abbr> created in <abbr title="Linked Data Platform Basic Container">LDP-BC</abbr></td><td>New triple: (<abbr title="Linked Data Platform Container">LDPC</abbr>, ldp:contains, <abbr title="Linked Data Platform Resource">LDPR</abbr>)</td><td>Same</td></tr>
@@ -1287,7 +1288,7 @@
cases where clients need to access only the subset of the container's properties
that are unrelated to member resources and unrelated to contained documents, for
example to determine the membership triple pattern and membership predicate of an
- <abbr title="Linked Data Platform Direct Container">LDP-DC</abbr>. LDP calls these <a title="Empty-container triples" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-empty-container-triples" class="internalDFN">empty-container triples</a>,
+ <abbr title="Linked Data Platform Direct Container">LDP-DC</abbr>. LDP calls these <a title="Empty-container triples" href="#dfn-empty-container-triples" class="internalDFN">empty-container triples</a>,
because they are what remains when the container has zero members and zero contained resources.
Since retrieving the whole container representation to
get this information may be onerous for clients and cause unnecessary
@@ -1296,13 +1297,13 @@
subset of properties used to address other major clusters of use cases).
LDP adds parameters to the HTTP <code>Prefer</code> header's
<code>return=representation</code> preference for this
- (see <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#prefer-parameters" class="sectionRef sec-ref">section <span class="secno">7.2</span> <span class="sec-title">Preferences on the Prefer Request Header</span></a> for details).
+ (see <a href="#prefer-parameters" class="sectionRef sec-ref">section <span class="secno">7.2</span> <span class="sec-title">Preferences on the Prefer Request Header</span></a> for details).
</p>
<p>The example listed here only shows
a simple case where few empty-container triples are
retrieved. In real world situations more complex cases are likely, such as those that add other predicates to
containers, for example providing validation information and
- associating <abbr title="SPARQL Protocol and RDF Query Language">SPARQL</abbr> endpoints. [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-sparql11-query">sparql11-query</a></cite>]</p>
+ associating <abbr title="SPARQL Protocol and RDF Query Language">SPARQL</abbr> endpoints. [<cite><a class="bibref" href="#bib-sparql11-query">sparql11-query</a></cite>]</p>
<p>
Here is an example requesting the empty-container triples of a
container identified by the URL <code>http://example.org/container1/</code>.
@@ -1341,15 +1342,15 @@
<section id="ldpc-container" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h3 aria-level="2" role="heading" id="h3_ldpc-container"><span class="secno">5.2 </span>Container</h3>
-<p>The following section contains normative clauses for <a title="" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-container" class="internalDFN">Linked Data Platform Container</a>.</p>
+<p>The following section contains normative clauses for <a title="" href="#dfn-linked-data-platform-container" class="internalDFN">Linked Data Platform Container</a>.</p>
<section id="ldpc-general" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h4 aria-level="3" role="heading" id="h4_ldpc-general"><span class="secno">5.2.1 </span>General</h4>
<p>The Linked Data Platform does not define how clients
discover <dfn id="dfn-linked-data-platform-containers"><abbr title="Linked Data Platform Containers">LDPCs</abbr></dfn>.</p>
- <section id="ldpc-isldpr" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpc-isldpr"><span class="secno">5.2.1.1 </span>Each <a title="" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-container" class="internalDFN">Linked Data Platform Container</a> <em class="rfc2119" title="MUST">MUST</em> also be
- a conforming <a title="" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-rdf-source" class="internalDFN">Linked Data Platform <abbr title="Resource Description Framework">RDF</abbr> Source</a>. <a title="" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-client" class="internalDFN">LDP client</a>s <em class="rfc2119" title="MAY">MAY</em> infer the following triple:
+ <section id="ldpc-isldpr" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpc-isldpr"><span class="secno">5.2.1.1 </span>Each <a title="" href="#dfn-linked-data-platform-container" class="internalDFN">Linked Data Platform Container</a> <em class="rfc2119" title="MUST">MUST</em> also be
+ a conforming <a title="" href="#dfn-linked-data-platform-rdf-source" class="internalDFN">Linked Data Platform <abbr title="Resource Description Framework">RDF</abbr> Source</a>. <a title="" href="#dfn-ldp-client" class="internalDFN">LDP client</a>s <em class="rfc2119" title="MAY">MAY</em> infer the following triple:
whose subject is <code>ldp:Container</code>,
whose predicate is <code>rdfs:subClassOf</code>,
and whose object is <code>ldp:RDFSource</code>,
@@ -1357,16 +1358,16 @@
</h5></section><!-- Was 5.2.1 / #ldpc-5_2_1 -->
<section id="ldpc-typecontainer" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpc-typecontainer"><span class="secno">5.2.1.2 </span>The representation of an <abbr title="Linked Data Platform Container">LDPC</abbr> <em class="rfc2119" title="MAY">MAY</em> have an <code>rdf:type</code>
- of only one of <code>ldp:Container</code> for <a title="" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-container" class="internalDFN">Linked Data Platform Container</a>.
- Non-normative note: <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldp-rdfconcepts-extra-triples-types"><abbr title="Linked Data Platform Containers">LDPCs</abbr>
- might have additional types</a>, like any <a title="Linked Data Platform RDF Source" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-rdf-source" class="internalDFN"><abbr title="Linked Data Platform RDF Source">LDP-RS</abbr></a>.
+ of only one of <code>ldp:Container</code> for <a title="" href="#dfn-linked-data-platform-container" class="internalDFN">Linked Data Platform Container</a>.
+ Non-normative note: <a href="#ldp-rdfconcepts-extra-triples-types"><abbr title="Linked Data Platform Containers">LDPCs</abbr>
+ might have additional types</a>, like any <a title="Linked Data Platform RDF Source" href="#dfn-linked-data-platform-rdf-source" class="internalDFN"><abbr title="Linked Data Platform RDF Source">LDP-RS</abbr></a>.
</h5></section><!-- Was 5.2.7 / #ldpc-5_2_7 -->
<section id="ldpc-nordfcontainertypes" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpc-nordfcontainertypes"><span class="secno">5.2.1.3 </span><abbr title="Linked Data Platform Container">LDPC</abbr> representations <em class="rfc2119" title="SHOULD NOT">SHOULD NOT</em> use <abbr title="Resource Description Framework">RDF</abbr> container types <code>rdf:Bag</code>,
<code>rdf:Seq</code> or <code>rdf:List</code>.
</h5></section><!-- Was 5.2.8 / #ldpc-5_2_8 -->
- <section id="ldpc-linktypehdr" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpc-linktypehdr"><span class="secno">5.2.1.4 </span><a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a>
+ <section id="ldpc-linktypehdr" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpc-linktypehdr"><span class="secno">5.2.1.4 </span><a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a>
exposing <abbr title="Linked Data Platform Containers">LDPCs</abbr>
<em class="rfc2119" title="MUST">MUST</em> advertise their LDP support by exposing a HTTP <code>Link</code> header
with a target URI matching the type of container (see below) the
@@ -1374,25 +1375,25 @@
a link relation type of <code>type</code> (that is, <code>rel='type'</code>)
in all responses to requests made
to the <abbr title="Linked Data Platform Container">LDPC</abbr>'s HTTP <code>Request-URI</code>.
- <a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MAY">MAY</em> provide additional HTTP <code>Link: rel='type'</code> headers.
- The <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpr-gen-linktypehdr">notes on the corresponding <abbr title="Linked Data Platform Resource">LDPR</abbr> constraint</a> apply
+ <a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MAY">MAY</em> provide additional HTTP <code>Link: rel='type'</code> headers.
+ The <a href="#ldpr-gen-linktypehdr">notes on the corresponding <abbr title="Linked Data Platform Resource">LDPR</abbr> constraint</a> apply
equally to <abbr title="Linked Data Platform Containers">LDPCs</abbr>.
</h5>
<p>Valid container type URIs for <code>rel='type'</code> defined by this document are:
</p><ul>
- <li><code>http://www.w3.org/ns/ldp#BasicContainer</code> - for <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpbc">LDP Basic Containers</a></li>
- <li><code>http://www.w3.org/ns/ldp#DirectContainer</code> - for <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpdc">LDP Direct Containers</a></li>
- <li><code>http://www.w3.org/ns/ldp#IndirectContainer</code> - for <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpic">LDP Indirect Containers</a></li>
+ <li><code>http://www.w3.org/ns/ldp#BasicContainer</code> - for <a href="#ldpbc">LDP Basic Containers</a></li>
+ <li><code>http://www.w3.org/ns/ldp#DirectContainer</code> - for <a href="#ldpdc">LDP Direct Containers</a></li>
+ <li><code>http://www.w3.org/ns/ldp#IndirectContainer</code> - for <a href="#ldpic">LDP Indirect Containers</a></li>
</ul>
<p></p>
</section><!-- Was 5.2.11 / #ldpc-5_2_11 -->
- <section id="ldpc-prefer" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpc-prefer"><span class="secno">5.2.1.5 </span><a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a>
+ <section id="ldpc-prefer" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpc-prefer"><span class="secno">5.2.1.5 </span><a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a>
<em class="rfc2119" title="SHOULD">SHOULD</em> respect all of a client's LDP-defined hints, for example
- <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#prefer-parameters">which subsets of LDP-defined state</a>
+ <a href="#prefer-parameters">which subsets of LDP-defined state</a>
the client is interested in processing,
to influence the set of triples returned in representations of an <abbr title="Linked Data Platform Container">LDPC</abbr>,
- particularly for large <abbr title="Linked Data Platform Containers">LDPCs</abbr>. See also [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-LDP-PAGING">LDP-PAGING</a></cite>].
+ particularly for large <abbr title="Linked Data Platform Containers">LDPCs</abbr>. See also [<cite><a class="bibref" href="#bib-LDP-PAGING">LDP-PAGING</a></cite>].
</h5></section>
</section>
@@ -1400,8 +1401,8 @@
<section id="ldpc-HTTP_GET" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h4 aria-level="3" role="heading" id="h4_ldpc-HTTP_GET"><span class="secno">5.2.2 </span>HTTP GET</h4>
<p>
- Per <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpr-HTTP_GET" class="sectionRef sec-ref">section <span class="secno">4.2.2</span> <span class="sec-title">HTTP GET</span></a> the HTTP GET method is required and
- additional requirements can be found in <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpc-general" class="sectionRef sec-ref">section <span class="secno">5.2.1</span> <span class="sec-title">General</span></a>.
+ Per <a href="#ldpr-HTTP_GET" class="sectionRef sec-ref">section <span class="secno">4.2.2</span> <span class="sec-title">HTTP GET</span></a> the HTTP GET method is required and
+ additional requirements can be found in <a href="#ldpc-general" class="sectionRef sec-ref">section <span class="secno">5.2.1</span> <span class="sec-title">General</span></a>.
</p>
</section>
@@ -1409,19 +1410,19 @@
<section id="ldpc-HTTP_POST" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h4 aria-level="3" role="heading" id="h4_ldpc-HTTP_POST"><span class="secno">5.2.3 </span>HTTP POST</h4>
<p>
- Per [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-HTTP11">HTTP11</a></cite>], this HTTP method is optional and
- this specification does not require <a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> to support it.
+ Per [<cite><a class="bibref" href="#bib-HTTP11">HTTP11</a></cite>], this HTTP method is optional and
+ this specification does not require <a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> to support it.
When an LDP server supports this method,
this specification imposes the following new requirements for <abbr title="Linked Data Platform Containers">LDPCs</abbr>.
</p>
<p>
Any server-imposed constraints on creation or update
- <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpr-gen-pubclireqs">must be advertised</a> to clients.
+ <a href="#ldpr-gen-pubclireqs">must be advertised</a> to clients.
</p>
<section id="ldpc-post-created201" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpc-post-created201"><span class="secno">5.2.3.1 </span><abbr title="Linked Data Platform Container">LDPC</abbr> clients <em class="rfc2119" title="SHOULD">SHOULD</em> create member resources by submitting a representation as
- the entity body of the HTTP <code>POST</code> to a known <abbr title="Linked Data Platform Container">LDPC</abbr>. If the resource was created successfully, <a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MUST">MUST</em>
+ the entity body of the HTTP <code>POST</code> to a known <abbr title="Linked Data Platform Container">LDPC</abbr>. If the resource was created successfully, <a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MUST">MUST</em>
respond with status code 201 (Created) and the <code>Location</code>
header set to the new resource’s URL. Clients shall not expect any representation in the response
entity body on a 201 (Created) response.
@@ -1429,45 +1430,45 @@
<section id="ldpc-post-createdmbr-contains" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpc-post-createdmbr-contains"><span class="secno">5.2.3.2 </span>
When a successful HTTP <code>POST</code> request to an <abbr title="Linked Data Platform Container">LDPC</abbr> results in the creation of an <abbr title="Linked Data Platform Resource">LDPR</abbr>, a
- <a title="Containment triples" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-containment-triples" class="internalDFN">containment triple</a> <em class="rfc2119" title="MUST">MUST</em> be added to the state of <abbr title="Linked Data Platform Container">LDPC</abbr>. The
- <a title="Containment triples" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-containment-triples" class="internalDFN">containment triple</a> whose subject is the <abbr title="Linked Data Platform Container">LDPC</abbr> URI,
+ <a title="Containment triples" href="#dfn-containment-triples" class="internalDFN">containment triple</a> <em class="rfc2119" title="MUST">MUST</em> be added to the state of <abbr title="Linked Data Platform Container">LDPC</abbr>. The
+ <a title="Containment triples" href="#dfn-containment-triples" class="internalDFN">containment triple</a> whose subject is the <abbr title="Linked Data Platform Container">LDPC</abbr> URI,
whose predicate is <code>ldp:contains</code> and whose object is the URI for the newly created document (<abbr title="Linked Data Platform Resource">LDPR</abbr>).
The newly created <abbr title="Linked Data Platform Resource">LDPR</abbr> appears as a contained resource of the <abbr title="Linked Data Platform Container">LDPC</abbr> until the
newly created document is deleted or removed by other methods. Other triples may be added as well.
</h5></section>
- <section id="ldpc-post-createbins" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpc-post-createbins"><span class="secno">5.2.3.3 </span><a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MAY">MAY</em> accept an HTTP <code>POST</code> of non-<abbr title="Resource Description Framework">RDF</abbr> representations
- <a title="Linked Data Platform Non-RDF Source" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-non-rdf-source" class="internalDFN">(LDP-NRs)</a> for
- creation of any kind of resource, for example binary resources. See <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpc-post-acceptposthdr">the Accept-Post section</a> for
+ <section id="ldpc-post-createbins" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpc-post-createbins"><span class="secno">5.2.3.3 </span><a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MAY">MAY</em> accept an HTTP <code>POST</code> of non-<abbr title="Resource Description Framework">RDF</abbr> representations
+ <a title="Linked Data Platform Non-RDF Source" href="#dfn-linked-data-platform-non-rdf-source" class="internalDFN">(LDP-NRs)</a> for
+ creation of any kind of resource, for example binary resources. See <a href="#ldpc-post-acceptposthdr">the Accept-Post section</a> for
details on how clients can discover whether an <abbr title="Linked Data Platform Container">LDPC</abbr> supports this behavior.
</h5></section><!-- Was 5.4.3 / #ldpc-5_4_3 -->
- <section id="ldpc-post-createrdf" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpc-post-createrdf"><span class="secno">5.2.3.4 </span><a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> that successfully create a resource from a
+ <section id="ldpc-post-createrdf" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpc-post-createrdf"><span class="secno">5.2.3.4 </span><a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> that successfully create a resource from a
<abbr title="Resource Description Framework">RDF</abbr> representation in the request entity body <em class="rfc2119" title="MUST">MUST</em> honor the client's requested interaction model(s). The created resource
- can be thought of as an <abbr title="Resource Description Framework">RDF</abbr> <a href="http://www.w3.org/TR/rdf11-concepts/#dfn-named-graph">named graph</a> [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-rdf11-concepts">rdf11-concepts</a></cite>].
+ can be thought of as an <abbr title="Resource Description Framework">RDF</abbr> <a href="http://www.w3.org/TR/rdf11-concepts/#dfn-named-graph">named graph</a> [<cite><a class="bibref" href="#bib-rdf11-concepts">rdf11-concepts</a></cite>].
If any model cannot be honored, the server <em class="rfc2119" title="MUST">MUST</em> fail the request.
</h5><!-- Was 5.4.4 / #ldpc-5_4_4 -->
<ul>
- <li>If the request header <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpr-gen-linktypehdr">specifies an <abbr title="Linked Data Platform Resource">LDPR</abbr> interaction model</a>, then the server <em class="rfc2119" title="MUST">MUST</em> handle subsequent
+ <li>If the request header <a href="#ldpr-gen-linktypehdr">specifies an <abbr title="Linked Data Platform Resource">LDPR</abbr> interaction model</a>, then the server <em class="rfc2119" title="MUST">MUST</em> handle subsequent
requests to the newly created resource's URI as if it is an <abbr title="Linked Data Platform Resource">LDPR</abbr>.
(even if the content contains an <code>rdf:type</code> triple indicating a type of <abbr title="Linked Data Platform Container">LDPC</abbr>).</li>
- <li>If the request header <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpc-linktypehdr">specifies an <abbr title="Linked Data Platform Container">LDPC</abbr> interaction model</a>, then the server <em class="rfc2119" title="MUST">MUST</em> handle subsequent
+ <li>If the request header <a href="#ldpc-linktypehdr">specifies an <abbr title="Linked Data Platform Container">LDPC</abbr> interaction model</a>, then the server <em class="rfc2119" title="MUST">MUST</em> handle subsequent
requests to the newly created resource's URI as if it is an <abbr title="Linked Data Platform Container">LDPC</abbr>.
</li>
<li>This specification does not constrain the server's behavior in other cases.</li>
- <p>Note: A consequence of this is that <abbr title="Linked Data Platform Containers">LDPCs</abbr> can be used to create <abbr title="Linked Data Platform Containers">LDPCs</abbr>, if the server supports doing so.</p>
- </ul>
+ </ul>
+ <p>Note: A consequence of this is that <abbr title="Linked Data Platform Containers">LDPCs</abbr> can be used to create <abbr title="Linked Data Platform Containers">LDPCs</abbr>, if the server supports doing so.</p>
</section>
- <section id="ldpc-post-turtle" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpc-post-turtle"><span class="secno">5.2.3.5 </span><a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MUST">MUST</em> accept a request entity body with a request header
- of <code>Content-Type</code> with value of <code>text/turtle</code> [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-turtle">turtle</a></cite>].
+ <section id="ldpc-post-turtle" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpc-post-turtle"><span class="secno">5.2.3.5 </span><a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MUST">MUST</em> accept a request entity body with a request header
+ of <code>Content-Type</code> with value of <code>text/turtle</code> [<cite><a class="bibref" href="#bib-turtle">turtle</a></cite>].
</h5></section><!-- Was 5.4.5 / #ldpc-5_4_5 -->
- <section id="ldpc-post-contenttype" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpc-post-contenttype"><span class="secno">5.2.3.6 </span><a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="SHOULD">SHOULD</em> use the <code>Content-Type</code> request header
+ <section id="ldpc-post-contenttype" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpc-post-contenttype"><span class="secno">5.2.3.6 </span><a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="SHOULD">SHOULD</em> use the <code>Content-Type</code> request header
to determine the representation format when the request has an entity body.
</h5></section><!-- Was 5.4.6 / #ldpc-5_4_6 -->
- <section id="ldpc-post-rdfnullrel" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpc-post-rdfnullrel"><span class="secno">5.2.3.7 </span>In <abbr title="Resource Description Framework">RDF</abbr> representations, <a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MUST">MUST</em> interpret the null relative
+ <section id="ldpc-post-rdfnullrel" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpc-post-rdfnullrel"><span class="secno">5.2.3.7 </span>In <abbr title="Resource Description Framework">RDF</abbr> representations, <a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MUST">MUST</em> interpret the null relative
URI for the subject of triples in the <abbr title="Linked Data Platform Resource">LDPR</abbr> representation in the
request entity body as referring to the entity in the request body.
Commonly, that entity is the model for the “to be created” <abbr title="Linked Data Platform Resource">LDPR</abbr>, so
@@ -1476,37 +1477,37 @@
resource.
</h5></section><!-- Was 5.4.7 / #ldpc-5_4_7 -->
- <section id="ldpc-post-serverassignuri" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpc-post-serverassignuri"><span class="secno">5.2.3.8 </span><a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="SHOULD">SHOULD</em> assign the URI for the resource to be
- created using server application specific rules in the absence of a <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpc-post-slug">client hint</a>.
+ <section id="ldpc-post-serverassignuri" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpc-post-serverassignuri"><span class="secno">5.2.3.8 </span><a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="SHOULD">SHOULD</em> assign the URI for the resource to be
+ created using server application specific rules in the absence of a <a href="#ldpc-post-slug">client hint</a>.
</h5></section><!-- Was 5.4.8 / #ldpc-5_4_8 -->
- <section id="ldpc-post-mincontraints" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpc-post-mincontraints"><span class="secno">5.2.3.9 </span><a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="SHOULD">SHOULD</em> allow clients to create new resources without
+ <section id="ldpc-post-mincontraints" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpc-post-mincontraints"><span class="secno">5.2.3.9 </span><a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="SHOULD">SHOULD</em> allow clients to create new resources without
requiring detailed knowledge of application-specific constraints.
This is a consequence of the requirement to enable simple creation and modification of <abbr title="Linked Data Platform Resources">LDPRs</abbr>. LDP servers
- expose these application-specific constraints as described in <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpr-general" class="sectionRef sec-ref">section <span class="secno">4.2.1</span> <span class="sec-title">General</span></a>.
+ expose these application-specific constraints as described in <a href="#ldpr-general" class="sectionRef sec-ref">section <span class="secno">4.2.1</span> <span class="sec-title">General</span></a>.
</h5></section><!-- Was 5.4.9 / #ldpc-5_4_9 -->
- <section id="ldpc-post-slug" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpc-post-slug"><span class="secno">5.2.3.10 </span><a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MAY">MAY</em> allow clients to suggest the URI for a resource
- created through <code>POST</code>, using the HTTP <code>Slug</code> header as defined in [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-RFC5023">RFC5023</a></cite>]. LDP adds
+ <section id="ldpc-post-slug" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpc-post-slug"><span class="secno">5.2.3.10 </span><a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MAY">MAY</em> allow clients to suggest the URI for a resource
+ created through <code>POST</code>, using the HTTP <code>Slug</code> header as defined in [<cite><a class="bibref" href="#bib-RFC5023">RFC5023</a></cite>]. LDP adds
no new requirements to this usage, so its presence functions as a client hint to the server
providing a desired string to be incorporated into the server's final choice of resource URI.
</h5></section><!-- Was 5.4.10 / #ldpc-5_4_10 -->
- <section id="ldpc-post-dontreuseuris" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpc-post-dontreuseuris"><span class="secno">5.2.3.11 </span><a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> that allow member creation via <code>POST</code>
+ <section id="ldpc-post-dontreuseuris" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpc-post-dontreuseuris"><span class="secno">5.2.3.11 </span><a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> that allow member creation via <code>POST</code>
<em class="rfc2119" title="SHOULD NOT">SHOULD NOT</em> re-use URIs.
</h5></section><!-- Was 5.4.11 / #ldpc-5_4_11 -->
<section id="ldpc-post-createbinlinkmetahdr" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpc-post-createbinlinkmetahdr"><span class="secno">5.2.3.12 </span>Upon successful creation of an
- <a title="Linked Data Platform Non-RDF Source" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-non-rdf-source" class="internalDFN"><abbr title="Linked Data Platform Non-RDF Source">LDP-NR</abbr></a> (HTTP status code of
- 201-Created and URI indicated by <code>Location</code> response header), <a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MAY">MAY</em> create an associated
- <a title="Linked Data Platform RDF Source" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-rdf-source" class="internalDFN"><abbr title="Linked Data Platform RDF Source">LDP-RS</abbr></a>
- to contain data about the newly created <abbr title="Linked Data Platform Non-RDF Source">LDP-NR</abbr>. If an <abbr title="Linked Data Platform Container">LDPC</abbr> server creates this associated <a title="Linked Data Platform RDF Source" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-rdf-source" class="internalDFN"><abbr title="Linked Data Platform RDF Source">LDP-RS</abbr></a> it <em class="rfc2119" title="MUST">MUST</em> indicate
+ <a title="Linked Data Platform Non-RDF Source" href="#dfn-linked-data-platform-non-rdf-source" class="internalDFN"><abbr title="Linked Data Platform Non-RDF Source">LDP-NR</abbr></a> (HTTP status code of
+ 201-Created and URI indicated by <code>Location</code> response header), <a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MAY">MAY</em> create an associated
+ <a title="Linked Data Platform RDF Source" href="#dfn-linked-data-platform-rdf-source" class="internalDFN"><abbr title="Linked Data Platform RDF Source">LDP-RS</abbr></a>
+ to contain data about the newly created <abbr title="Linked Data Platform Non-RDF Source">LDP-NR</abbr>. If an <abbr title="Linked Data Platform Container">LDPC</abbr> server creates this associated <a title="Linked Data Platform RDF Source" href="#dfn-linked-data-platform-rdf-source" class="internalDFN"><abbr title="Linked Data Platform RDF Source">LDP-RS</abbr></a> it <em class="rfc2119" title="MUST">MUST</em> indicate
its location on the HTTP response using the HTTP <code>Link</code> response header with link relation <code>describedby</code>
- and <code>href</code> to be the URI of the associated <abbr title="Linked Data Platform RDF Source">LDP-RS</abbr> resource [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-RFC5988">RFC5988</a></cite>].
+ and <code>href</code> to be the URI of the associated <abbr title="Linked Data Platform RDF Source">LDP-RS</abbr> resource [<cite><a class="bibref" href="#bib-RFC5988">RFC5988</a></cite>].
</h5></section><!-- Was 5.4.12 / #ldpc-5_4_12 -->
- <section id="ldpc-post-acceptposthdr" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpc-post-acceptposthdr"><span class="secno">5.2.3.13 </span><a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> that support <code>POST</code> <em class="rfc2119" title="MUST">MUST</em>
- include an <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#header-accept-post"><code>Accept-Post</code> response header</a> on HTTP <code>OPTIONS</code>
+ <section id="ldpc-post-acceptposthdr" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpc-post-acceptposthdr"><span class="secno">5.2.3.13 </span><a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> that support <code>POST</code> <em class="rfc2119" title="MUST">MUST</em>
+ include an <a href="#header-accept-post"><code>Accept-Post</code> response header</a> on HTTP <code>OPTIONS</code>
responses, listing post document media type(s) supported by the server.
LDP only specifies the use of <code>POST</code> for the purpose of creating new resources, but a server
can accept <code>POST</code> requests with other semantics.
@@ -1515,7 +1516,7 @@
creation of a new resource; they must rely on out of band information for knowledge of which <code>POST</code> requests,
if any, will have the "create new resource" semantics.
This requirement on LDP servers is intentionally stronger than the one levied in the
- <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#header-accept-post">header registration</a>; it is unrealistic to expect all existing resources
+ <a href="#header-accept-post">header registration</a>; it is unrealistic to expect all existing resources
that support <code>POST</code> to suddenly return a new header or for all new specifications constraining
<code>POST</code> to be aware of its existence and require it, but it is a reasonable requirement for new
specifications such as LDP.
@@ -1526,25 +1527,25 @@
<section id="ldpc-HTTP_PUT" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h4 aria-level="3" role="heading" id="h4_ldpc-HTTP_PUT"><span class="secno">5.2.4 </span>HTTP PUT</h4>
<p>
- Per [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-HTTP11">HTTP11</a></cite>], this HTTP method is optional and
- this specification does not require <a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> to support it.
+ Per [<cite><a class="bibref" href="#bib-HTTP11">HTTP11</a></cite>], this HTTP method is optional and
+ this specification does not require <a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> to support it.
When an LDP server supports this method,
this specification imposes the following new requirements for <abbr title="Linked Data Platform Containers">LDPCs</abbr>.
</p>
<p>
Any server-imposed constraints on creation or update
- <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpr-gen-pubclireqs">must be advertised</a> to clients.
+ <a href="#ldpr-gen-pubclireqs">must be advertised</a> to clients.
</p>
- <section id="ldpc-put-mbrprops" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpc-put-mbrprops"><span class="secno">5.2.4.1 </span><a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="SHOULD NOT">SHOULD NOT</em> allow HTTP <code>PUT</code> to update an <abbr title="Linked Data Platform Container">LDPC</abbr>’s <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-containment-triples" class="internalDFN">containment triples</a>;
+ <section id="ldpc-put-mbrprops" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpc-put-mbrprops"><span class="secno">5.2.4.1 </span><a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="SHOULD NOT">SHOULD NOT</em> allow HTTP <code>PUT</code> to update an <abbr title="Linked Data Platform Container">LDPC</abbr>’s <a href="#dfn-containment-triples" class="internalDFN">containment triples</a>;
if the server receives such a request, it <em class="rfc2119" title="SHOULD">SHOULD</em> respond with a 409
(Conflict) status code.
</h5></section><!-- Was 5.5.1 / #ldpc-5_5_1 -->
- <section id="ldpc-put-create" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpc-put-create"><span class="secno">5.2.4.2 </span><a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> that allow <abbr title="Linked Data Platform Resource">LDPR</abbr> creation via <code>PUT</code>
+ <section id="ldpc-put-create" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpc-put-create"><span class="secno">5.2.4.2 </span><a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> that allow <abbr title="Linked Data Platform Resource">LDPR</abbr> creation via <code>PUT</code>
<em class="rfc2119" title="SHOULD NOT">SHOULD NOT</em> re-use URIs. For <abbr title="Resource Description Framework">RDF</abbr> representations (LDP-RSs),the created resource
- can be thought of as an <abbr title="Resource Description Framework">RDF</abbr> <a href="http://www.w3.org/TR/rdf11-concepts/#dfn-named-graph">named graph</a> [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-rdf11-concepts">rdf11-concepts</a></cite>].
+ can be thought of as an <abbr title="Resource Description Framework">RDF</abbr> <a href="http://www.w3.org/TR/rdf11-concepts/#dfn-named-graph">named graph</a> [<cite><a class="bibref" href="#bib-rdf11-concepts">rdf11-concepts</a></cite>].
</h5></section><!-- Was 5.5.4 / #ldpc-5_5_4 -->
</section>
@@ -1552,27 +1553,27 @@
<section id="ldpc-HTTP_DELETE" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h4 aria-level="3" role="heading" id="h4_ldpc-HTTP_DELETE"><span class="secno">5.2.5 </span>HTTP DELETE</h4>
<p>
- Per [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-HTTP11">HTTP11</a></cite>], this HTTP method is optional and
- this specification does not require <a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> to support it.
+ Per [<cite><a class="bibref" href="#bib-HTTP11">HTTP11</a></cite>], this HTTP method is optional and
+ this specification does not require <a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> to support it.
When an LDP server supports this method,
this specification imposes the following new requirements for <abbr title="Linked Data Platform Containers">LDPCs</abbr>.
</p>
<section id="ldpc-del-contremovesconttriple" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpc-del-contremovesconttriple"><span class="secno">5.2.5.1 </span>
- When an <abbr title="Linked Data Platform Resource">LDPR</abbr> identified by the object of a <a title="containment triples" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-containment-triples" class="internalDFN">containment triple</a> is deleted, the <abbr title="Linked Data Platform Container">LDPC</abbr> server <em class="rfc2119" title="MUST">MUST</em> also remove
+ When an <abbr title="Linked Data Platform Resource">LDPR</abbr> identified by the object of a <a title="containment triples" href="#dfn-containment-triples" class="internalDFN">containment triple</a> is deleted, the <abbr title="Linked Data Platform Container">LDPC</abbr> server <em class="rfc2119" title="MUST">MUST</em> also remove
the <abbr title="Linked Data Platform Resource">LDPR</abbr> from the containing <abbr title="Linked Data Platform Container">LDPC</abbr> by removing the corresponding containment triple.
</h5>
<blockquote>
- Non-normative note: The <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP server</a> might perform additional actions,
- as described in the <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldp-http-method-side-effects">normative references</a> like [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-HTTP11">HTTP11</a></cite>].
+ Non-normative note: The <a href="#dfn-ldp-server" class="internalDFN">LDP server</a> might perform additional actions,
+ as described in the <a href="#ldp-http-method-side-effects">normative references</a> like [<cite><a class="bibref" href="#bib-HTTP11">HTTP11</a></cite>].
For example, the server could perform additional cleanup tasks for resources it knows are no longer referenced or have not
been accessed for some period of time.
</blockquote>
</section><!-- Was 5.6.1 / #ldpc-5_6_1 -->
<section id="ldpc-del-contremovescontres" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpc-del-contremovescontres"><span class="secno">5.2.5.2 </span>
- When an <abbr title="Linked Data Platform Resource">LDPR</abbr> identified by the object of a <a title="containment triples" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-containment-triples" class="internalDFN">containment triple</a> is deleted, and the <abbr title="Linked Data Platform Container">LDPC</abbr> server
- created an associated <abbr title="Linked Data Platform RDF Source">LDP-RS</abbr> (see the <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpc-post-createbinlinkmetahdr"><abbr title="Linked Data Platform Container">LDPC</abbr> POST section</a>), the <abbr title="Linked Data Platform Container">LDPC</abbr> server <em class="rfc2119" title="MUST">MUST</em> also remove the associated <abbr title="Linked Data Platform RDF Source">LDP-RS</abbr> it created.
+ When an <abbr title="Linked Data Platform Resource">LDPR</abbr> identified by the object of a <a title="containment triples" href="#dfn-containment-triples" class="internalDFN">containment triple</a> is deleted, and the <abbr title="Linked Data Platform Container">LDPC</abbr> server
+ created an associated <abbr title="Linked Data Platform RDF Source">LDP-RS</abbr> (see the <a href="#ldpc-post-createbinlinkmetahdr"><abbr title="Linked Data Platform Container">LDPC</abbr> POST section</a>), the <abbr title="Linked Data Platform Container">LDPC</abbr> server <em class="rfc2119" title="MUST">MUST</em> also remove the associated <abbr title="Linked Data Platform RDF Source">LDP-RS</abbr> it created.
</h5></section><!-- Was 5.6.4 / #ldpc-5_6_4 -->
</section>
@@ -1581,30 +1582,30 @@
<h4 aria-level="3" role="heading" id="h4_ldpc-HTTP_HEAD"><span class="secno">5.2.6 </span>HTTP HEAD</h4>
<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" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> must also include HTTP headers
- on response to <code>OPTIONS</code>, see <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpr-HTTP_OPTIONS" class="sectionRef sec-ref">section <span class="secno">4.2.8</span> <span class="sec-title">HTTP OPTIONS</span></a>.
+ <code>HEAD</code> responses include the same headers as <code>GET</code> responses. Also <a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> must also include HTTP headers
+ on response to <code>OPTIONS</code>, see <a href="#ldpr-HTTP_OPTIONS" class="sectionRef sec-ref">section <span class="secno">4.2.8</span> <span class="sec-title">HTTP OPTIONS</span></a>.
Thus, implementers supporting <code>HEAD</code> should also carefully read the
- <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpc-HTTP_GET" class="sectionRef sec-ref">section <span class="secno">5.2.2</span> <span class="sec-title">HTTP GET</span></a> and <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpc-HTTP_OPTIONS" class="sectionRef sec-ref">section <span class="secno">5.2.8</span> <span class="sec-title">HTTP OPTIONS</span></a>.</p>
+ <a href="#ldpc-HTTP_GET" class="sectionRef sec-ref">section <span class="secno">5.2.2</span> <span class="sec-title">HTTP GET</span></a> and <a href="#ldpc-HTTP_OPTIONS" class="sectionRef sec-ref">section <span class="secno">5.2.8</span> <span class="sec-title">HTTP OPTIONS</span></a>.</p>
</section>
<section id="ldpc-HTTP_PATCH" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h4 aria-level="3" role="heading" id="h4_ldpc-HTTP_PATCH"><span class="secno">5.2.7 </span>HTTP PATCH</h4>
<p>
- Per [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-HTTP11">HTTP11</a></cite>], this HTTP method is optional and
- this specification does not require <a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> to support it.
+ Per [<cite><a class="bibref" href="#bib-HTTP11">HTTP11</a></cite>], this HTTP method is optional and
+ this specification does not require <a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> to support it.
When an LDP server supports this method,
this specification imposes the following new requirements for <abbr title="Linked Data Platform Containers">LDPCs</abbr>.
</p>
<p>
Any server-imposed constraints on <abbr title="Linked Data Platform Resource">LDPR</abbr> creation or update
- <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpr-gen-pubclireqs">must be advertised</a> to clients.
+ <a href="#ldpr-gen-pubclireqs">must be advertised</a> to clients.
</p>
<section id="ldpc-patch-req" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpc-patch-req"><span class="secno">5.2.7.1 </span>
- <a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> are <em class="rfc2119" title="RECOMMENDED">RECOMMENDED</em>
+ <a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> are <em class="rfc2119" title="RECOMMENDED">RECOMMENDED</em>
to support HTTP <code>PATCH</code> as the preferred method for
- updating an <abbr title="Linked Data Platform Container">LDPC</abbr>'s <a title="Empty-container triples" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-empty-container-triples" class="internalDFN">empty-container triples</a>.
+ updating an <abbr title="Linked Data Platform Container">LDPC</abbr>'s <a title="Empty-container triples" href="#dfn-empty-container-triples" class="internalDFN">empty-container triples</a>.
</h5></section><!-- Was 5.8.1 / #ldpc-5_8_1 -->
</section>
@@ -1614,13 +1615,13 @@
</p>
<section id="ldpc-options-linkmetahdr" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpc-options-linkmetahdr"><span class="secno">5.2.8.1 </span>When an <abbr title="Linked Data Platform Container">LDPC</abbr> server creates an
- <a title="Linked Data Platform Non-RDF Source" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-non-rdf-source" class="internalDFN"><abbr title="Linked Data Platform Non-RDF Source">LDP-NR</abbr></a> (for example, one whose
+ <a title="Linked Data Platform Non-RDF Source" href="#dfn-linked-data-platform-non-rdf-source" class="internalDFN"><abbr title="Linked Data Platform Non-RDF Source">LDP-NR</abbr></a> (for example, one whose
representation was HTTP <code>POST</code>ed to the <abbr title="Linked Data Platform Container">LDPC</abbr>)
- the LDP server might create an associated <a title="Linked Data Platform RDF Source" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-rdf-source" class="internalDFN"><abbr title="Linked Data Platform RDF Source">LDP-RS</abbr></a>
- to contain data about the non-<abbr title="Linked Data Platform Resource">LDPR</abbr> (see <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpc-post-createbinlinkmetahdr"><abbr title="Linked Data Platform Container">LDPC</abbr> POST section</a>).
+ the LDP server might create an associated <a title="Linked Data Platform RDF Source" href="#dfn-linked-data-platform-rdf-source" class="internalDFN"><abbr title="Linked Data Platform RDF Source">LDP-RS</abbr></a>
+ to contain data about the non-<abbr title="Linked Data Platform Resource">LDPR</abbr> (see <a href="#ldpc-post-createbinlinkmetahdr"><abbr title="Linked Data Platform Container">LDPC</abbr> POST section</a>).
For LDP-NRs that have this associated <abbr title="Linked Data Platform RDF Source">LDP-RS</abbr>, an <abbr title="Linked Data Platform Container">LDPC</abbr> server <em class="rfc2119" title="MUST">MUST</em> provide an HTTP <code>Link</code>
header whose target URI is the associated <abbr title="Linked Data Platform RDF Source">LDP-RS</abbr>, and whose link relation type is
- <code>describedby</code> [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-RFC5988">RFC5988</a></cite>].
+ <code>describedby</code> [<cite><a class="bibref" href="#bib-RFC5988">RFC5988</a></cite>].
</h5></section><!-- Was 5.9.2 / #ldpc-5_9_2 -->
</section> <!-- h2 -->
</section> <!-- ldpc-container -->
@@ -1628,15 +1629,15 @@
<section id="ldpbc" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h3 aria-level="2" role="heading" id="h3_ldpbc"><span class="secno">5.3 </span>Basic</h3>
-<p>The following section contains normative clauses for <a title="" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-basic-container" class="internalDFN">Linked Data Platform Basic Container</a>.</p>
+<p>The following section contains normative clauses for <a title="" href="#dfn-linked-data-platform-basic-container" class="internalDFN">Linked Data Platform Basic Container</a>.</p>
<section id="ldpbc-general" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h4 aria-level="3" role="heading" id="h4_ldpbc-general"><span class="secno">5.3.1 </span>General</h4>
-<section id="ldpbc-are-ldpcs" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpbc-are-ldpcs"><span class="secno">5.3.1.1 </span>Each <a title="Linked Data Platform Basic Container" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-basic-container" class="internalDFN">LDP Basic Container</a> <em class="rfc2119" title="MUST">MUST</em> also be
- a conforming <a title="Linked Data Platform Container" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-container" class="internalDFN">LDP Container</a> in <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpc-container" class="sectionRef sec-ref">section <span class="secno">5.2</span> <span class="sec-title">Container</span></a> along the
- following restrictions in this section. <a title="" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-client" class="internalDFN">LDP client</a>s <em class="rfc2119" title="MAY">MAY</em> infer the following triple:
+<section id="ldpbc-are-ldpcs" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpbc-are-ldpcs"><span class="secno">5.3.1.1 </span>Each <a title="Linked Data Platform Basic Container" href="#dfn-linked-data-platform-basic-container" class="internalDFN">LDP Basic Container</a> <em class="rfc2119" title="MUST">MUST</em> also be
+ a conforming <a title="Linked Data Platform Container" href="#dfn-linked-data-platform-container" class="internalDFN">LDP Container</a> in <a href="#ldpc-container" class="sectionRef sec-ref">section <span class="secno">5.2</span> <span class="sec-title">Container</span></a> along the
+ following restrictions in this section. <a title="" href="#dfn-ldp-client" class="internalDFN">LDP client</a>s <em class="rfc2119" title="MAY">MAY</em> infer the following triple:
whose subject is <code>ldp:BasicContainer</code>,
whose predicate is <code>rdfs:subClassOf</code>,
and whose object is <code>ldp:Container</code>,
@@ -1651,14 +1652,14 @@
<section id="ldpdc" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h3 aria-level="2" role="heading" id="h3_ldpdc"><span class="secno">5.4 </span>Direct</h3>
-<p>The following section contains normative clauses for <a title="" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-direct-container" class="internalDFN">Linked Data Platform Direct Container</a>.</p>
+<p>The following section contains normative clauses for <a title="" href="#dfn-linked-data-platform-direct-container" class="internalDFN">Linked Data Platform Direct Container</a>.</p>
<section id="ldpdc-general" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h4 aria-level="3" role="heading" id="h4_ldpdc-general"><span class="secno">5.4.1 </span>General</h4>
-<section id="ldpdc-are-ldpcs" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpdc-are-ldpcs"><span class="secno">5.4.1.1 </span>Each <a title="Linked Data Platform Direct Container" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-direct-container" class="internalDFN">LDP Direct Container</a> <em class="rfc2119" title="MUST">MUST</em> also be
- a conforming <a title="Linked Data Platform Container" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-container" class="internalDFN">LDP Container</a> in <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpc-container" class="sectionRef sec-ref">section <span class="secno">5.2</span> <span class="sec-title">Container</span></a> along the following
- restrictions. <a title="" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-client" class="internalDFN">LDP client</a>s <em class="rfc2119" title="MAY">MAY</em> infer the following triple:
+<section id="ldpdc-are-ldpcs" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpdc-are-ldpcs"><span class="secno">5.4.1.1 </span>Each <a title="Linked Data Platform Direct Container" href="#dfn-linked-data-platform-direct-container" class="internalDFN">LDP Direct Container</a> <em class="rfc2119" title="MUST">MUST</em> also be
+ a conforming <a title="Linked Data Platform Container" href="#dfn-linked-data-platform-container" class="internalDFN">LDP Container</a> in <a href="#ldpc-container" class="sectionRef sec-ref">section <span class="secno">5.2</span> <span class="sec-title">Container</span></a> along the following
+ restrictions. <a title="" href="#dfn-ldp-client" class="internalDFN">LDP client</a>s <em class="rfc2119" title="MAY">MAY</em> infer the following triple:
whose subject is <code>ldp:BasicContainer</code>,
whose predicate is <code>rdfs:subClassOf</code>,
and whose object is <code>ldp:Container</code>,
@@ -1666,21 +1667,21 @@
</h5></section>
<section id="ldpdc-mbrpred" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpdc-mbrpred"><span class="secno">5.4.1.2 </span>
- <a title="Linked Data Platform Direct Container" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-direct-container" class="internalDFN">LDP Direct Containers</a>
- <em class="rfc2119" title="SHOULD">SHOULD</em> use the <code>ldp:member</code> predicate as an <abbr title="Linked Data Platform Container">LDPC</abbr>'s <a title="Membership predicate" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-membership-predicate" class="internalDFN">membership predicate</a>
+ <a title="Linked Data Platform Direct Container" href="#dfn-linked-data-platform-direct-container" class="internalDFN">LDP Direct Containers</a>
+ <em class="rfc2119" title="SHOULD">SHOULD</em> use the <code>ldp:member</code> predicate as an <abbr title="Linked Data Platform Container">LDPC</abbr>'s <a title="Membership predicate" href="#dfn-membership-predicate" class="internalDFN">membership predicate</a>
if there is no obvious predicate from an application vocabulary to use..
The state of an <abbr title="Linked Data Platform Container">LDPC</abbr> includes information about which
- resources are its members, in the form of <a title="Membership triples" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-membership-triples" class="internalDFN">membership triples</a> that
+ resources are its members, in the form of <a title="Membership triples" href="#dfn-membership-triples" class="internalDFN">membership triples</a> that
follow a consistent pattern. The <abbr title="Linked Data Platform Container">LDPC</abbr>'s state contains enough information for clients to discern
- the <a title="Membership predicate" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-membership-predicate" class="internalDFN">membership predicate</a>, the other consistent membership
+ the <a title="Membership predicate" href="#dfn-membership-predicate" class="internalDFN">membership predicate</a>, the other consistent membership
value used in the container's membership triples (<var>membership-constant-URI</var>),
and the position (subject or object) where those URIs
- occurs in the <a title="Membership triples" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-membership-triples" class="internalDFN">membership triples</a>.
+ occurs in the <a title="Membership triples" href="#dfn-membership-triples" class="internalDFN">membership triples</a>.
Member resources can be
any kind of resource identified by a URI, <abbr title="Linked Data Platform Resource">LDPR</abbr> or otherwise.
</h5></section><!-- Was 5.2.3 / #ldpc-5_2_3 -->
-<section id="ldpdc-containres" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpdc-containres"><span class="secno">5.4.1.3 </span>Each <a title="Linked Data Platform Direct Container" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-direct-container" class="internalDFN">LDP Direct Container</a>
+<section id="ldpdc-containres" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpdc-containres"><span class="secno">5.4.1.3 </span>Each <a title="Linked Data Platform Direct Container" href="#dfn-linked-data-platform-direct-container" class="internalDFN">LDP Direct Container</a>
representation <em class="rfc2119" title="MUST">MUST</em> contain exactly one triple
whose subject is the <abbr title="Linked Data Platform Container">LDPC</abbr> URI,
whose predicate is the <code>ldp:membershipResource</code>,
@@ -1689,19 +1690,19 @@
</h5>
</section><!-- Was 5.2.4 / #ldpc-5_2_4 -->
-<section id="ldpdc-containtriples" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpdc-containtriples"><span class="secno">5.4.1.4 </span>Each <a title="Linked Data Platform Direct Container" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-direct-container" class="internalDFN">LDP Direct Container</a>
+<section id="ldpdc-containtriples" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpdc-containtriples"><span class="secno">5.4.1.4 </span>Each <a title="Linked Data Platform Direct Container" href="#dfn-linked-data-platform-direct-container" class="internalDFN">LDP Direct Container</a>
representation <em class="rfc2119" title="MUST">MUST</em> contain exactly one triple
whose subject is the <abbr title="Linked Data Platform Container">LDPC</abbr> URI,
and whose predicate is either <code>ldp:hasMemberRelation</code> or <code>ldp:isMemberOfRelation</code>.
The object of the triple is constrained by other sections, such as
- <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpdc-containtriple-relation" class="sectionRef">ldp:hasMemberRelation</a> or
- <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpdc-containtriple-byrelation" class="sectionRef">ldp:isMemberOfRelation</a>, based on the
- <a title="Membership triples" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-membership-triples" class="internalDFN">membership triple</a>
+ <a href="#ldpdc-containtriple-relation" class="sectionRef">ldp:hasMemberRelation</a> or
+ <a href="#ldpdc-containtriple-byrelation" class="sectionRef">ldp:isMemberOfRelation</a>, based on the
+ <a title="Membership triples" href="#dfn-membership-triples" class="internalDFN">membership triple</a>
pattern used by the container.
</h5><!-- Was 5.2.5 / #ldpc-5_2_5 -->
-<section id="ldpdc-containtriple-relation" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h6 class="normal" aria-level="5" role="heading" id="h6_ldpdc-containtriple-relation"><span class="secno">5.4.1.4.1 </span><a title="Linked Data Platform Direct Container" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-direct-container" class="internalDFN">LDP Direct Containers</a>
- whose <a title="Membership triples" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-membership-triples" class="internalDFN">membership triple</a>
+<section id="ldpdc-containtriple-relation" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h6 class="normal" aria-level="5" role="heading" id="h6_ldpdc-containtriple-relation"><span class="secno">5.4.1.4.1 </span><a title="Linked Data Platform Direct Container" href="#dfn-linked-data-platform-direct-container" class="internalDFN">LDP Direct Containers</a>
+ whose <a title="Membership triples" href="#dfn-membership-triples" class="internalDFN">membership triple</a>
pattern is <var>( membership-constant-URI , membership-predicate , member-derived-URI )</var> <em class="rfc2119" title="MUST">MUST</em>
contain exactly one triple
whose subject is the <abbr title="Linked Data Platform Container">LDPC</abbr> URI,
@@ -1710,8 +1711,8 @@
</h6>
</section><!-- Was 5.2.5.1 / #ldpc-5_2_5_1 -->
-<section id="ldpdc-containtriple-byrelation" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h6 class="normal" aria-level="5" role="heading" id="h6_ldpdc-containtriple-byrelation"><span class="secno">5.4.1.4.2 </span><a title="Linked Data Platform Direct Container" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-direct-container" class="internalDFN">LDP Direct Containers</a>
- whose <a title="Membership triples" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-membership-triples" class="internalDFN">membership triple</a>
+<section id="ldpdc-containtriple-byrelation" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h6 class="normal" aria-level="5" role="heading" id="h6_ldpdc-containtriple-byrelation"><span class="secno">5.4.1.4.2 </span><a title="Linked Data Platform Direct Container" href="#dfn-linked-data-platform-direct-container" class="internalDFN">LDP Direct Containers</a>
+ whose <a title="Membership triples" href="#dfn-membership-triples" class="internalDFN">membership triple</a>
pattern is <var>( member-derived-URI , membership-predicate , membership-constant-URI )</var> <em class="rfc2119" title="MUST">MUST</em>
contain exactly one triple
whose subject is the <abbr title="Linked Data Platform Container">LDPC</abbr> URI,
@@ -1721,7 +1722,7 @@
</section>
<section id="ldpdc-indirectmbr-basic" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpdc-indirectmbr-basic"><span class="secno">5.4.1.5 </span>
- <a title="Linked Data Platform Direct Container" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-direct-container" class="internalDFN">LDP Direct Containers</a>
+ <a title="Linked Data Platform Direct Container" href="#dfn-linked-data-platform-direct-container" class="internalDFN">LDP Direct Containers</a>
<em class="rfc2119" title="MUST">MUST</em> behave as if they
have a <var>( <abbr title="Linked Data Platform Container">LDPC</abbr> URI, <code>ldp:insertedContentRelation</code> , <code>ldp:MemberSubject</code> )</var>
triple, but LDP imposes no requirement to materialize such a triple in the <abbr title="Linked Data Platform Direct Container">LDP-DC</abbr> representation.
@@ -1740,7 +1741,7 @@
When a successful HTTP <code>POST</code> request to an <abbr title="Linked Data Platform Container">LDPC</abbr> results in the creation of an <abbr title="Linked Data Platform Resource">LDPR</abbr>,
the <abbr title="Linked Data Platform Container">LDPC</abbr> <em class="rfc2119" title="MUST">MUST</em> update its membership triples to reflect that addition, and the resulting
membership triple <em class="rfc2119" title="MUST">MUST</em> be consistent with any LDP-defined predicates it exposes.
- A <a title="Linked Data Platform Direct Container" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-direct-container" class="internalDFN">LDP Direct Container</a>'s membership triples <em class="rfc2119" title="MAY">MAY</em> also be modified via
+ A <a title="Linked Data Platform Direct Container" href="#dfn-linked-data-platform-direct-container" class="internalDFN">LDP Direct Container</a>'s membership triples <em class="rfc2119" title="MAY">MAY</em> also be modified via
through other means.
</h5></section><!-- Was 5.4.2 / #ldpc-5_4_2 -->
</section> <!-- ldpdc-HTTP_POST -->
@@ -1749,7 +1750,7 @@
<h4 aria-level="3" role="heading" id="h4_ldpdc-HTTP_DELETE"><span class="secno">5.4.3 </span>HTTP DELETE</h4>
<section id="ldpdc-del-contremovesmbrtriple" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpdc-del-contremovesmbrtriple"><span class="secno">5.4.3.1 </span>
- When an <abbr title="Linked Data Platform Resource">LDPR</abbr> identified by the object of a <a title="membership triples" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-membership-triples" class="internalDFN">membership triple</a> which was
+ When an <abbr title="Linked Data Platform Resource">LDPR</abbr> identified by the object of a <a title="membership triples" href="#dfn-membership-triples" class="internalDFN">membership triple</a> which was
originally created by the <abbr title="Linked Data Platform Direct Container">LDP-DC</abbr> is deleted, the <abbr title="Linked Data Platform Container">LDPC</abbr> server <em class="rfc2119" title="MUST">MUST</em> also remove
the corresponding membership triple..
</h5>
@@ -1762,14 +1763,14 @@
<section id="ldpic" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h3 aria-level="2" role="heading" id="h3_ldpic"><span class="secno">5.5 </span>Indirect</h3>
-<p>The following section contains normative clauses for <a title="" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-indirect-container" class="internalDFN">Linked Data Platform Indirect Container</a>.</p>
+<p>The following section contains normative clauses for <a title="" href="#dfn-linked-data-platform-indirect-container" class="internalDFN">Linked Data Platform Indirect Container</a>.</p>
<section id="ldpic-general" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h4 aria-level="3" role="heading" id="h4_ldpic-general"><span class="secno">5.5.1 </span>General</h4>
-<section id="ldpic-are-ldpcs" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpic-are-ldpcs"><span class="secno">5.5.1.1 </span>Each <a title="Linked Data Platform Indirect Container" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-indirect-container" class="internalDFN">LDP Indirect Container</a> <em class="rfc2119" title="MUST">MUST</em> also be
- a conforming <a title="Linked Data Platform Direct Container" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-direct-container" class="internalDFN">LDP Direct Container</a> in <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpdc" class="sectionRef sec-ref">section <span class="secno">5.4</span> <span class="sec-title">Direct</span></a> along the following
- restrictions. <a title="" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-client" class="internalDFN">LDP client</a>s <em class="rfc2119" title="MAY">MAY</em> infer the following triple:
+<section id="ldpic-are-ldpcs" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpic-are-ldpcs"><span class="secno">5.5.1.1 </span>Each <a title="Linked Data Platform Indirect Container" href="#dfn-linked-data-platform-indirect-container" class="internalDFN">LDP Indirect Container</a> <em class="rfc2119" title="MUST">MUST</em> also be
+ a conforming <a title="Linked Data Platform Direct Container" href="#dfn-linked-data-platform-direct-container" class="internalDFN">LDP Direct Container</a> in <a href="#ldpdc" class="sectionRef sec-ref">section <span class="secno">5.4</span> <span class="sec-title">Direct</span></a> along the following
+ restrictions. <a title="" href="#dfn-ldp-client" class="internalDFN">LDP client</a>s <em class="rfc2119" title="MAY">MAY</em> infer the following triple:
whose subject is <code>ldp:IndirectContainer</code>,
whose predicate is <code>rdfs:subClassOf</code>,
and whose object is <code>ldp:Container</code>,
@@ -1777,12 +1778,12 @@
</h5></section>
<section id="ldpic-indirectmbr" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_ldpic-indirectmbr"><span class="secno">5.5.1.2 </span>
- <a title="Linked Data Platform Indirect Container" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-linked-data-platform-indirect-container" class="internalDFN">LDP Indirect Containers</a>
+ <a title="Linked Data Platform Indirect Container" href="#dfn-linked-data-platform-indirect-container" class="internalDFN">LDP Indirect Containers</a>
<em class="rfc2119" title="MUST">MUST</em> contain exactly one triple whose
subject is the <abbr title="Linked Data Platform Container">LDPC</abbr> URI,
whose predicate is <code>ldp:insertedContentRelation</code>, and
whose object <var>ICR</var> describes how the <var>member-derived-URI</var> in
- the container's <a title="Membership triples" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-membership-triples" class="internalDFN">membership triples</a> is chosen.
+ the container's <a title="Membership triples" href="#dfn-membership-triples" class="internalDFN">membership triples</a> is chosen.
The <var>member-derived-URI</var> is taken from some triple
<var>( S, P, O )</var> in the document supplied by the client as input to the create request;
if <var>ICR</var>'s value is <var>P</var>, then the <var>member-derived-URI</var> is
@@ -1807,7 +1808,7 @@
whose subject is the container's URI,
whose predicate is <code>ldp:contains</code>, and
whose object is the newly created resource's URI (which will be different from
- the <var><a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpic-indirectmbr">member-derived URI</a></var> in this case).
+ the <var><a href="#ldpic-indirectmbr">member-derived URI</a></var> in this case).
This <code>ldp:contains</code> triple can be the only link from the container to the newly created
resource in certain cases.
</h5></section><!-- Was 5.4.15 / #ldpc-5_4_15 -->
@@ -1830,13 +1831,13 @@
<section id="specs-webarch" class="informative" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h3 aria-level="2" role="heading" id="h3_specs-webarch"><span class="secno">6.1 </span>Architecture of the World Wide Web</h3><p><em>This section is non-normative.</em></p>
-Reference: [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-WEBARCH">WEBARCH</a></cite>]
+Reference: [<cite><a class="bibref" href="#bib-WEBARCH">WEBARCH</a></cite>]
<section id="ldp-webarch-nonexcl-membership" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h4 class="normal" aria-level="3" role="heading" id="h4_ldp-webarch-nonexcl-membership"><span class="secno">6.1.1 </span><abbr title="Linked Data Platform Container">LDPC</abbr> membership is not exclusive; this means that the same resource
(<abbr title="Linked Data Platform Resource">LDPR</abbr> or not) can be a member of more than one <abbr title="Linked Data Platform Container">LDPC</abbr>.
</h4></section>
- <section id="ldp-webarch-uri-reuse" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h4 class="normal" aria-level="3" role="heading" id="h4_ldp-webarch-uri-reuse"><span class="secno">6.1.2 </span><a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> should not re-use URIs,
+ <section id="ldp-webarch-uri-reuse" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h4 class="normal" aria-level="3" role="heading" id="h4_ldp-webarch-uri-reuse"><span class="secno">6.1.2 </span><a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> should not re-use URIs,
regardless of the mechanism by which members are created (<code>POST</code>, <code>PUT</code>, etc.).
Certain specific cases exist where an <abbr title="Linked Data Platform Container">LDPC</abbr> server might delete a resource and then later re-use the
URI when it identifies the same resource, but only when consistent with Web architecture.
@@ -1848,53 +1849,53 @@
<section id="specs-http" class="informative" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h3 aria-level="2" role="heading" id="h3_specs-http"><span class="secno">6.2 </span>HTTP 1.1</h3><p><em>This section is non-normative.</em></p>
-Reference: [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-HTTP11">HTTP11</a></cite>]
+Reference: [<cite><a class="bibref" href="#bib-HTTP11">HTTP11</a></cite>]
- <section id="ldp-http-other-representations" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h4 class="normal" aria-level="3" role="heading" id="h4_ldp-http-other-representations"><span class="secno">6.2.1 </span><a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> can support representations beyond those
+ <section id="ldp-http-other-representations" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h4 class="normal" aria-level="3" role="heading" id="h4_ldp-http-other-representations"><span class="secno">6.2.1 </span><a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> can support representations beyond those
necessary to conform to this specification. These
could be other <abbr title="Resource Description Framework">RDF</abbr> formats, like N3 or NTriples, but non-<abbr title="Resource Description Framework">RDF</abbr> formats
- like HTML [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-HTML401">HTML401</a></cite>] and JSON [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-RFC4627">RFC4627</a></cite>] would likely be common.
- HTTP content negotiation ([<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-HTTP11">HTTP11</a></cite>] Section 12 - Content Negotiation) is used to select the format.
+ like HTML [<cite><a class="bibref" href="#bib-HTML401">HTML401</a></cite>] and JSON [<cite><a class="bibref" href="#bib-RFC4627">RFC4627</a></cite>] would likely be common.
+ HTTP content negotiation ([<cite><a class="bibref" href="#bib-HTTP11">HTTP11</a></cite>] Section 12 - Content Negotiation) is used to select the format.
</h4></section>
<section id="ldp-http-other-methods" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h4 class="normal" aria-level="3" role="heading" id="h4_ldp-http-other-methods"><span class="secno">6.2.2 </span><abbr title="Linked Data Platform Resources">LDPRs</abbr> can be created, updated and deleted using methods not defined in
this document, for example through application-specific means, <abbr title="SPARQL Protocol and RDF Query Language">SPARQL</abbr>
- UPDATE, etc. [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-SPARQL-UPDATE">SPARQL-UPDATE</a></cite>], as long as those methods do not conflict with this specification's
+ UPDATE, etc. [<cite><a class="bibref" href="#bib-SPARQL-UPDATE">SPARQL-UPDATE</a></cite>], as long as those methods do not conflict with this specification's
normative requirements.
</h4></section>
- <section id="ldp-http-delete-uri-reuse" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h4 class="normal" aria-level="3" role="heading" id="h4_ldp-http-delete-uri-reuse"><span class="secno">6.2.3 </span><a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a>
+ <section id="ldp-http-delete-uri-reuse" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h4 class="normal" aria-level="3" role="heading" id="h4_ldp-http-delete-uri-reuse"><span class="secno">6.2.3 </span><a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a>
remove the resource identified by the <code>Request-URI</code> in response to a successful HTTP <code>DELETE</code> request.
After such a request, a subsequent HTTP <code>GET</code> on the same
<code>Request-URI</code> usually results in a 404 (Not found) or 410 (Gone) status
code, although HTTP allows others.
</h4></section>
- <section id="ldp-http-method-side-effects" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h4 class="normal" aria-level="3" role="heading" id="h4_ldp-http-method-side-effects"><span class="secno">6.2.4 </span><a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> can alter the state of other resources
- as a result of any HTTP request, especially when non-safe methods are used ([<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-HTTP11">HTTP11</a></cite>] section 9.1).
+ <section id="ldp-http-method-side-effects" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h4 class="normal" aria-level="3" role="heading" id="h4_ldp-http-method-side-effects"><span class="secno">6.2.4 </span><a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> can alter the state of other resources
+ as a result of any HTTP request, especially when non-safe methods are used ([<cite><a class="bibref" href="#bib-HTTP11">HTTP11</a></cite>] section 9.1).
For example, it is acceptable for the server to
remove triples from other resources whose subject or object is the
deleted resource as the result of a successful HTTP <code>DELETE</code> request.
- It is also acceptable and common for <a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> to
+ It is also acceptable and common for <a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> to
not do this – the server's behavior can vary, so LDP clients cannot depend on it.
</h4></section>
- <section id="ldp-http-patch-allowed" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h4 class="normal" aria-level="3" role="heading" id="h4_ldp-http-patch-allowed"><span class="secno">6.2.5 </span><a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> can implement HTTP <code>PATCH</code>
+ <section id="ldp-http-patch-allowed" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h4 class="normal" aria-level="3" role="heading" id="h4_ldp-http-patch-allowed"><span class="secno">6.2.5 </span><a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> can implement HTTP <code>PATCH</code>
to allow modifications,
especially partial replacement, of their resources. No
- minimal set of patch document formats is mandated by this document or by the definition of <code>PATCH</code> [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-RFC5789">RFC5789</a></cite>].
+ minimal set of patch document formats is mandated by this document or by the definition of <code>PATCH</code> [<cite><a class="bibref" href="#bib-RFC5789">RFC5789</a></cite>].
</h4></section>
<section id="ldp-http-content-sniffing" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h4 class="normal" aria-level="3" role="heading" id="h4_ldp-http-content-sniffing"><span class="secno">6.2.6 </span>
When the <code>Content-Type</code> request header is absent from a request,
- <a title="LDP server" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP servers</a> might infer the content type by inspecting the entity body contents [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-HTTP11">HTTP11</a></cite>].
+ <a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> might infer the content type by inspecting the entity body contents [<cite><a class="bibref" href="#bib-HTTP11">HTTP11</a></cite>].
</h4></section>
</section>
<section id="specs-rdf" class="informative" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<h3 aria-level="2" role="heading" id="h3_specs-rdf"><span class="secno">6.3 </span><abbr title="Resource Description Framework">RDF</abbr></h3><p><em>This section is non-normative.</em></p>
-Reference: [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-rdf11-concepts">rdf11-concepts</a></cite>]
+Reference: [<cite><a class="bibref" href="#bib-rdf11-concepts">rdf11-concepts</a></cite>]
<section id="ldp-rdfconcepts-extra-triples-any" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h4 class="normal" aria-level="3" role="heading" id="h4_ldp-rdfconcepts-extra-triples-any"><span class="secno">6.3.1 </span>The state of an <abbr title="Linked Data Platform Resource">LDPR</abbr>
can have triples with any subject(s). The URL used to retrieve the
@@ -1905,7 +1906,7 @@
can include an arbitrary number of
additional triples whose subjects are the members of the container,
or that are from the representations of the members (if they have <abbr title="Resource Description Framework">RDF</abbr>
- representations). This allows an <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-ldp-server" class="internalDFN">LDP server</a> to provide clients with
+ representations). This allows an <a href="#dfn-ldp-server" class="internalDFN">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.
</h4></section>
@@ -1929,7 +1930,7 @@
<ul>
<li>The addition of <code>Accept-Post</code> in this specification is pending
advancement of an <a href="https://datatracker.ietf.org/doc/draft-wilde-accept-post/">IETF draft</a>
- that would fully include it, based on the Accept-Patch header's design from [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-RFC5789">RFC5789</a></cite>]. Once LDP is in
+ that would fully include it, based on the Accept-Patch header's design from [<cite><a class="bibref" href="#bib-RFC5789">RFC5789</a></cite>]. Once LDP is in
Candidate Recommendation, the LDP WG will make an assessment based on the status at IETF
working with the <abbr title="World Wide Web Consortium">W3C</abbr> Director.</li>
</ul>
@@ -1937,15 +1938,15 @@
<p>This specification introduces a new HTTP response header <code>Accept-Post</code> used
to specify the document formats accepted by the server on HTTP <code>POST</code> requests.
- It is modelled after the <code>Accept-Patch</code> header defined in [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-RFC5789">RFC5789</a></cite>].
+ It is modelled after the <code>Accept-Patch</code> header defined in [<cite><a class="bibref" href="#bib-RFC5789">RFC5789</a></cite>].
</p>
<section id="header-accept-post-1" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h4 class="normal" aria-level="3" role="heading" id="h4_header-accept-post-1"><span class="secno">7.1.1 </span>The syntax for <code>Accept-Post</code>, using
- the ABNF syntax defined in Section 2.1 of [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-HTTP11">HTTP11</a></cite>], is:</h4>
+ the ABNF syntax defined in Section 2.1 of [<cite><a class="bibref" href="#bib-HTTP11">HTTP11</a></cite>], is:</h4>
<blockquote><code>Accept-Post = "Accept-Post" ":" 1#media-type</code>
<p>
The <code>Accept-Post</code> header specifies a comma-separated list of media-
- types (with optional parameters) as defined by [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-HTTP11">HTTP11</a></cite>], Section 3.7.
+ types (with optional parameters) as defined by [<cite><a class="bibref" href="#bib-HTTP11">HTTP11</a></cite>], Section 3.7.
</p>
</blockquote>
</section><!-- Was 6.1.1 / #header-accept-post-1 -->
@@ -1964,7 +1965,7 @@
<div>
<blockquote>
<p>
- The Accept-Post response header must be added to the permanent registry (see [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-RFC3864">RFC3864</a></cite>]).
+ The Accept-Post response header must be added to the permanent registry (see [<cite><a class="bibref" href="#bib-RFC3864">RFC3864</a></cite>]).
</p>
<p>
Header field name: Accept-Post
@@ -1996,7 +1997,7 @@
</div>
<p>This specification introduces new parameters on the HTTP <code>Prefer</code> request header's
- <code>return=representation</code> preference [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-Prefer">Prefer</a></cite>], used optionally by clients to
+ <code>return=representation</code> preference [<cite><a class="bibref" href="#bib-Prefer">Prefer</a></cite>], used optionally by clients to
supply a hint to help the server form a response that is most appropriate to
the client's needs. The LDP-defined parameters suggest the portion(s) of a resource's state that the
client application is interested in and, if received, is likely to be
@@ -2010,14 +2011,14 @@
<p>
Non-normative note: LDP server implementers should carefully consider the effects of these
- preferences on caching, as described in section 2 of [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-Prefer">Prefer</a></cite>].
+ preferences on caching, as described in section 2 of [<cite><a class="bibref" href="#bib-Prefer">Prefer</a></cite>].
</p>
<p>
- Non-normative note: [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-Prefer">Prefer</a></cite>] recommends that server implementers include a
+ Non-normative note: [<cite><a class="bibref" href="#bib-Prefer">Prefer</a></cite>] recommends that server implementers include a
<code>Preference-Applied</code> response header when the client cannot otherwise determine the server's
behavior with respect to honoring hints from the response content.
- <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#prefer-examples">Examples</a> illustrates some cases where the header is unnecessary.
+ <a href="#prefer-examples">Examples</a> illustrates some cases where the header is unnecessary.
</p>
</section> <!-- Prefer summary -->
@@ -2030,20 +2031,20 @@
would like included in a representation.
The syntax for the <code>include</code> parameter of the
HTTP <code>Prefer</code> request header's
- <code>return=representation</code> preference [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-Prefer">Prefer</a></cite>] is:</h5>
+ <code>return=representation</code> preference [<cite><a class="bibref" href="#bib-Prefer">Prefer</a></cite>] is:</h5>
<blockquote>
<code>include-parameter = "include" *WSP "=" *WSP ldp-uri-list</code>
<p>
- Where <code>WSP</code> is whitespace [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-RFC5234">RFC5234</a></cite>], and
+ Where <code>WSP</code> is whitespace [<cite><a class="bibref" href="#bib-RFC5234">RFC5234</a></cite>], and
<code>ldp-uri-list</code> is a double-quoted blank-delimited unordered set of URIs whose ABNF is given below.
- The generic preference BNF [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-Prefer">Prefer</a></cite>] allows either a quoted string or a token as the value of a
+ The generic preference BNF [<cite><a class="bibref" href="#bib-Prefer">Prefer</a></cite>] allows either a quoted string or a token as the value of a
preference parameter; LDP assigns a meaning to the value only when it is a quoted string of
the form:
</p>
<code>ldp-uri-list = DQUOTE *WSP URI *[ 1*WSP URI ] *WSP DQUOTE</code>
<p>
- where <code>DQUOTE</code> is a double quote [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-RFC5234">RFC5234</a></cite>], and <code>URI</code> is an absolute URI with an optional
- fragment component [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-RFC3986">RFC3986</a></cite>].
+ where <code>DQUOTE</code> is a double quote [<cite><a class="bibref" href="#bib-RFC5234">RFC5234</a></cite>], and <code>URI</code> is an absolute URI with an optional
+ fragment component [<cite><a class="bibref" href="#bib-RFC3986">RFC3986</a></cite>].
</p>
</blockquote>
</section>
@@ -2053,11 +2054,11 @@
would like omitted from a representation.
The syntax for the <code>omit</code> parameter of the
HTTP <code>Prefer</code> request header's
- <code>return=representation</code> preference [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-Prefer">Prefer</a></cite>] is:</h5>
+ <code>return=representation</code> preference [<cite><a class="bibref" href="#bib-Prefer">Prefer</a></cite>] is:</h5>
<blockquote>
<code>omit-parameter = "omit" *WSP "=" *WSP ldp-uri-list</code>
<p>
- Where <code>WSP</code> and <code>ldp-uri-list</code> are defined as above for <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#prefer-include">include</a>.
+ Where <code>WSP</code> and <code>ldp-uri-list</code> are defined as above for <a href="#prefer-include">include</a>.
</p>
</blockquote>
</section>
@@ -2066,7 +2067,7 @@
When LDP servers receive a request with conflicting hints, this specification imposes
no requirements on their behavior. They are free to reject the request, process it
applying some subset of the hints, or anything else appropriate to the server.
- [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-Prefer">Prefer</a></cite>] suggests treating similar requests as though none of the conflicting
+ [<cite><a class="bibref" href="#bib-Prefer">Prefer</a></cite>] suggests treating similar requests as though none of the conflicting
preferences were specified.
</h5>
</section>
@@ -2074,18 +2075,18 @@
<section id="prefer-uris" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h5 class="normal" aria-level="4" role="heading" id="h5_prefer-uris"><span class="secno">7.2.2.4 </span>
This specification defines the following URIs for clients to use with <code>include</code>
and <code>omit</code> parameters. It assigns no meaning to other URIs, although
- other specifications <em class="rfc2119" title="MAY">MAY</em> do so.
+ other specifications <em class="rfc2119" title="MAY">MAY</em> do so.</h5>
<table class="indented">
<tbody><tr>
- <td> <a title="Containment triples" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-containment-triples" class="internalDFN">Containment triples </a></td>
+ <td> <a title="Containment triples" href="#dfn-containment-triples" class="internalDFN">Containment triples </a></td>
<td> <code>http://www.w3.org/ns/ldp#PreferContainment</code> </td>
</tr>
<tr>
- <td> <a title="Membership triples" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-membership-triples" class="internalDFN">Membership triples </a></td>
+ <td> <a title="Membership triples" href="#dfn-membership-triples" class="internalDFN">Membership triples </a></td>
<td> <code>http://www.w3.org/ns/ldp#PreferMembership</code> </td>
</tr>
<tr>
- <td> <a title="Empty-container triples" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-empty-container-triples" class="internalDFN">Empty-container triples</a>
+ <td> <a title="Empty-container triples" href="#dfn-empty-container-triples" class="internalDFN">Empty-container triples</a>
</td>
<td> <code>http://www.w3.org/ns/ldp#PreferEmptyContainer</code> </td>
</tr>
@@ -2098,8 +2099,6 @@
could be defined.
</p>
</blockquote>
-
- </h5>
</section>
</section> <!-- Prefer specification -->
@@ -2170,7 +2169,7 @@
<code>Prefer: return=representation; omit="http://www.w3.org/ns/ldp#PreferMembership http://www.w3.org/ns/ldp#PreferContainment"</code>. Note: <strong>Treating the two as equivalent is not recommended.</strong> While today this
<code>omit</code> parameter value is equivalent to the preceding <code>include</code> parameter value,
they may not be equivalent in the future
- due to the definition of <a title="Empty-container triples" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#dfn-empty-container-triples" class="internalDFN">empty-container triples</a>.
+ due to the definition of <a title="Empty-container triples" href="#dfn-empty-container-triples" class="internalDFN">empty-container triples</a>.
Clients should preferentially use the <code>include</code> parameter, as it more precisely communicates their needs.
</p>
<p>
@@ -2209,7 +2208,7 @@
the header would still be required for the client to know that the <code>303</code> response entity
is a representation of the resource identified by the <code>Location</code> URI
instead of a short hypertext note (one with a hyperlink to
- the same URI reference provided in the <code>Location</code> header field [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-HTTPBIS-SEMANTICS">HTTPBIS-SEMANTICS</a></cite>]).
+ the same URI reference provided in the <code>Location</code> header field [<cite><a class="bibref" href="#bib-HTTPBIS-SEMANTICS">HTTPBIS-SEMANTICS</a></cite>]).
</p>
<div class="example"><div class="example-title"><span>Example 12</span></div><pre class="example"># The following is the representation of
@@ -2308,7 +2307,7 @@
</div>
</section>
-</section> <!-- status code defns -->
+</section> -->
<section class="informative" id="security" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
<!--OddPage--><h2 aria-level="1" role="heading" id="h2_security"><span class="secno">8. </span>Security Considerations</h2><p><em>This section is non-normative.</em></p>
@@ -2345,7 +2344,7 @@
<li>Defined sub-types of ldp:Resource : <abbr title="Resource Description Framework">RDF</abbr> Source and non-<abbr title="Resource Description Framework">RDF</abbr> Source</li>
<li>Improved membership predicate names, changed vocabulary terms</li>
<li>Reorganized conformance clauses based on type of resource</li>
- <li>Moved paging and sorting capability into a separate document [<cite><a class="bibref" href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-LDP-PAGING">LDP-PAGING</a></cite>]</li>
+ <li>Moved paging and sorting capability into a separate document [<cite><a class="bibref" href="#bib-LDP-PAGING">LDP-PAGING</a></cite>]</li>
<li>Removed non-member property mechanism and replaced with usage of Prefer header</li>
<li>Added support for client requested interaction models on containers</li>
<li>Move restatements of HTTP et al. out of normative sections</li>