LDP readied for PR
authorSteve Speicher <sspeiche@gmail.com>
Thu, 11 Dec 2014 08:38:57 -0500
changeset 921 c79dd6f48a29
parent 920 6e705e6cd210
child 922 cb6efb8c91bf
LDP readied for PR
TR/PR-ldp-20141211/Overview.html
TR/PR-ldp-20141211/images/ldpc-basic.png
TR/PR-ldp-20141211/images/ldpc-hierarchy.png
TR/PR-ldp-20141211/images/ldpc1.png
TR/PR-ldp-20141211/images/ldpr1.png
TR/PR-ldp-20141211/images/ldpr2.png
TR/PR-ldp-20141211/ldp.ttl
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/TR/PR-ldp-20141211/Overview.html	Thu Dec 11 08:38:57 2014 -0500
@@ -0,0 +1,2999 @@
+<!DOCTYPE html>
+<html lang="en" dir="ltr" typeof="bibo:Document w3p:PR" about="" property="dcterms:language" content="en">
+<head>
+    <title>Linked Data Platform 1.0</title>
+    <meta http-equiv="Content-Type" content="text/html;charset=utf-8">
+        <!-- Test coverage: The following allows the spec to be annotated with information
+         from the test suite to help with understanding the coverage of each requirement. -->
+    <style>/* --- EXAMPLES --- */
+div.example-title {
+    min-width: 7.5em;
+    color: #b9ab2d;
+}
+div.example-title span {
+    text-transform: uppercase;   
+}
+aside.example, div.example, div.illegal-example {
+    padding: 0.5em;
+    margin: 1em 0;
+    position: relative;
+    clear: both;
+}
+div.illegal-example { color: red }
+div.illegal-example p { color: black }
+aside.example, div.example {
+    padding: .5em;
+    border-left-width: .5em;
+    border-left-style: solid;
+    border-color: #e0cb52;
+    background: #fcfaee;    
+}
+
+aside.example div.example {
+    border-left-width: .1em;
+    border-color: #999;
+    background: #fff;
+}
+aside.example div.example div.example-title {
+    color: #999;
+}
+</style><style>/* --- ISSUES/NOTES --- */
+div.issue-title, div.note-title {
+    padding-right:  1em;
+    min-width: 7.5em;
+    color: #b9ab2d;
+}
+div.issue-title { color: #e05252; }
+div.note-title { color: #2b2; }
+div.issue-title span, div.note-title span {
+    text-transform: uppercase;
+}
+div.note, div.issue {
+    margin-top: 1em;
+    margin-bottom: 1em;
+}
+.note > p:first-child, .issue > p:first-child { margin-top: 0 }
+.issue, .note {
+    padding: .5em;
+    border-left-width: .5em;
+    border-left-style: solid;
+}
+div.issue, div.note {
+    padding: 1em 1.2em 0.5em;
+    margin: 1em 0;
+    position: relative;
+    clear: both;
+}
+span.note, span.issue { padding: .1em .5em .15em; }
+
+.issue {
+    border-color: #e05252;
+    background: #fbe9e9;
+}
+.note {
+    border-color: #52e052;
+    background: #e9fbe9;
+}
+
+
+</style>
+    <style type="text/css" media="print">
+        .coverage {
+            page-break-inside: avoid;
+        }
+    </style>
+    
+    <!-- 
+      === NOTA BENE ===
+      For the three scripts below, if your spec resides on dev.w3 you can check them
+      out in the same tree and use relative links so that they'll work offline,
+     -->
+     
+    
+    <style type="text/css">
+    	div.rule {padding-top: 1em;}
+    	div.ldp-issue-open {
+	    	border-color: #E05252;
+			background: #FBE9E9;
+			padding: 0.5em;
+			margin: 1em 0;
+			position: relative;
+			clear: both;
+			border-left-width: .5em;
+			border-left-style: solid;
+    	}
+    	div.ldp-issue-pending {
+	    	border-color: #FAF602;
+			background: #F7F6BC;
+			padding: 0.5em;
+			margin: 1em 0;
+			position: relative;
+			clear: both;
+			border-left-width: .5em;
+			border-left-style: solid;
+    	}
+    	div.ldp-issue-closed {
+	    	border-color: #009900;
+			background: #BCF7CF;
+			padding: 0.5em;
+			margin: 1em 0;
+			position: relative;
+			clear: both;
+			border-left-width: .5em;
+			border-left-style: solid;
+    	}
+    	div.ldp-issue-title {
+    	    color: #E05252;
+    	    padding-right: 1em;
+            min-width: 7.5em;
+    	}
+		.atrisk {
+			padding:    1em;
+			margin: 1em 0em 0em;
+			border: 1px solid #f00;
+			background: #ffc;
+		}
+		.atrisktext {
+			/* content:    "Feature At Risk"; */
+			display:    block;
+			width:  150px;
+			margin: -1.5em 0 0.5em 0;
+			font-weight:    bold;
+			border: 1px solid #f00;
+			background: #fff;
+			padding:    3px 1em;
+		}
+		.normal { 
+			font-weight: normal;
+			font: normal 100% sans-serif;
+		}
+		.indented { 
+			margin-left: +3em;
+		}
+		tr:nth-of-type(odd),.oddrow { 
+			background:#F2F2F2; /* light grey, just enough to differentiate from white */
+		}
+		td { 
+			padding:0 +1ex 0 +1ex; /* add a bit of space from rule/edge to text */
+		}
+		
+    </style>
+    <style type="text/css" media="all">
+    	code {
+    	    font-weight:bold;
+			font-size:larger;
+    	}
+		 /* ReSpec uses color ff4500 for code elements, which does not print well on some black & white printers
+		    and is a little hard to read for some folks even on-line. 
+			The default code font size was also somewhat too small/hard to read.
+		*/
+    </style>
+  <style>/*****************************************************************
+ * ReSpec 3 CSS
+ * Robin Berjon - http://berjon.com/
+ *****************************************************************/
+
+/* --- INLINES --- */
+em.rfc2119 { 
+    text-transform:     lowercase;
+    font-variant:       small-caps;
+    font-style:         normal;
+    color:              #900;
+}
+
+h1 acronym, h2 acronym, h3 acronym, h4 acronym, h5 acronym, h6 acronym, a acronym,
+h1 abbr, h2 abbr, h3 abbr, h4 abbr, h5 abbr, h6 abbr, a abbr {
+    border: none;
+}
+
+dfn {
+    font-weight:    bold;
+}
+
+a.internalDFN {
+    color:  inherit;
+    border-bottom:  1px solid #99c;
+    text-decoration:    none;
+}
+
+a.externalDFN {
+    color:  inherit;
+    border-bottom:  1px dotted #ccc;
+    text-decoration:    none;
+}
+
+a.bibref {
+    text-decoration:    none;
+}
+
+cite .bibref {
+    font-style: normal;
+}
+
+code {
+    color:  #C83500;
+}
+
+/* --- TOC --- */
+.toc a, .tof a {
+    text-decoration:    none;
+}
+
+a .secno, a .figno {
+    color:  #000;
+}
+
+ul.tof, ol.tof {
+    list-style: none outside none;
+}
+
+.caption {
+    margin-top: 0.5em;
+    font-style:   italic;
+}
+
+/* --- TABLE --- */
+table.simple {
+    border-spacing: 0;
+    border-collapse:    collapse;
+    border-bottom:  3px solid #005a9c;
+}
+
+.simple th {
+    background: #005a9c;
+    color:  #fff;
+    padding:    3px 5px;
+    text-align: left;
+}
+
+.simple th[scope="row"] {
+    background: inherit;
+    color:  inherit;
+    border-top: 1px solid #ddd;
+}
+
+.simple td {
+    padding:    3px 10px;
+    border-top: 1px solid #ddd;
+}
+
+.simple tr:nth-child(even) {
+    background: #f0f6ff;
+}
+
+/* --- DL --- */
+.section dd > p:first-child {
+    margin-top: 0;
+}
+
+.section dd > p:last-child {
+    margin-bottom: 0;
+}
+
+.section dd {
+    margin-bottom:  1em;
+}
+
+.section dl.attrs dd, .section dl.eldef dd {
+    margin-bottom:  0;
+}
+
[email protected] print {
+    .removeOnSave {
+        display: none;
+    }
+}
+</style><link rel="stylesheet" href="https://www.w3.org/StyleSheets/TR/W3C-PR"><!--[if lt IE 9]><script src='https://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]--></head>
+<body class="h-entry" role="document" id="respecDocument"><div class="head" role="contentinfo" id="respecHeader">
+  <p>
+      
+        
+            <a href="http://www.w3.org/"><img width="72" height="48" src="https://www.w3.org/Icons/w3c_home" alt="W3C"></a>
+        
+      
+  </p>
+  <h1 class="title p-name" id="title" property="dcterms:title">Linked Data Platform 1.0</h1>
+  
+  <h2 property="dcterms:issued" datatype="xsd:dateTime" content="2014-12-11T05:00:00.000Z" id="w3c-proposed-recommendation-11-december-2014"><abbr title="World Wide Web Consortium">W3C</abbr> Proposed Recommendation <time class="dt-published" datetime="2014-12-11">11 December 2014</time></h2>
+  <dl>
+    
+      <dt>This version:</dt>
+      <dd><a class="u-url" href="http://www.w3.org/TR/2014/PR-ldp-20141211/">http://www.w3.org/TR/2014/PR-ldp-20141211/</a></dd>
+      <dt>Latest published version:</dt>
+      <dd><a href="http://www.w3.org/TR/ldp/">http://www.w3.org/TR/ldp/</a></dd>
+    
+    
+      <dt>Latest editor's draft:</dt>
+      <dd><a href="http://www.w3.org/2012/ldp/hg/ldp.html">http://www.w3.org/2012/ldp/hg/ldp.html</a></dd>
+    
+    
+      <dt>Test suite:</dt>
+      <dd><a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/tests/ldp-testsuite.html">https://dvcs.w3.org/hg/ldpwg/raw-file/default/tests/ldp-testsuite.html</a></dd>
+    
+    
+      <dt>Implementation report:</dt>
+      <dd><a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/tests/reports/ldp.html">https://dvcs.w3.org/hg/ldpwg/raw-file/default/tests/reports/ldp.html</a></dd>
+    
+    
+    
+    
+      <dt>Previous version:</dt>
+      <dd><a rel="dcterms:replaces" href="http://www.w3.org/TR/2014/WD-ldp-20140916/">http://www.w3.org/TR/2014/WD-ldp-20140916/</a></dd>
+    
+    
+    <dt>Editors:</dt>
+    <dd class="p-author h-card vcard" rel="bibo:editor" inlist=""><span typeof="foaf:Person"><a class="u-url url p-name fn" rel="foaf:homepage" property="foaf:name" content="Steve Speicher" href="http://stevespeicher.blogspot.com">Steve Speicher</a>, <a rel="foaf:workplaceHomepage" class="p-org org h-org h-card" href="http://ibm.com/">IBM Corporation</a></span>
+</dd>
+<dd class="p-author h-card vcard" rel="bibo:editor" inlist=""><span typeof="foaf:Person"><a class="u-url url p-name fn" rel="foaf:homepage" property="foaf:name" content="John Arwe" href="https://www.ibm.com/developerworks/mydeveloperworks/groups/service/html/allcommunities?userid=120000CAW7">John Arwe</a>, <a rel="foaf:workplaceHomepage" class="p-org org h-org h-card" href="http://ibm.com/">IBM Corporation</a></span>
+</dd>
+<dd class="p-author h-card vcard" rel="bibo:editor" inlist=""><span typeof="foaf:Person"><a class="u-url url p-name fn" rel="foaf:homepage" property="foaf:name" content="Ashok Malhotra" href="mailto:[email protected]">Ashok Malhotra</a>, <a rel="foaf:workplaceHomepage" class="p-org org h-org h-card" href="http://www.oracle.com">Oracle Corporation</a></span>
+</dd>
+
+    
+    
+  </dl>
+  
+  
+  
+  
+    
+      <p class="copyright">
+        <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</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.
+        
+        <abbr title="World Wide Web Consortium">W3C</abbr> <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
+        <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and
+        
+          <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a>
+        
+        rules apply.
+      </p>
+    
+  
+  <hr>
+</div>
+<section id="abstract" class="introductory" property="dcterms:abstract" datatype="" typeof="bibo:Chapter" resource="#abstract" rel="bibo:Chapter"><h2 role="heading" id="h2_abstract">Abstract</h2><p>
+Linked Data Platform (LDP) defines a set of rules for HTTP operations on web resources, some based on 
+<abbr title="Resource Description Framework">RDF</abbr>, to provide an architecture for read-write Linked Data on the web.
+</p></section><section id="sotd" class="introductory" typeof="bibo:Chapter" resource="#sotd" rel="bibo:Chapter"><h2 role="heading" id="h2_sotd">Status of This Document</h2>
+  
+    
+      
+        <p>
+          <em>This section describes the status of this document at the time of its publication.
+          Other documents may supersede this document. A list of current <abbr title="World Wide Web Consortium">W3C</abbr> publications and the
+          latest revision of this technical report can be found in the <a href="http://www.w3.org/TR/"><abbr title="World Wide Web Consortium">W3C</abbr> technical reports index</a> at
+          http://www.w3.org/TR/.</em>
+        </p>
+        
+        
+   <p>
+   	 This is the Proposed Recommendation working draft where the Working Group has received community feedback,
+   	 addressed all raised issues, produced a test suite and received implementation feedback. 
+   	 For changes since last publication, see <a href="#history" class="sectionRef sec-ref">section <span class="secno">B.</span> <span class="sec-title">Change History</span></a>. 
+	 A test suite is available at [<cite><a class="bibref" href="#bib-LDP-Tests">LDP-Tests</a></cite>].
+   </p>
+ 
+        
+        <p>
+          This document was published by the <a href="http://www.w3.org/2012/ldp">Linked Data Platform Working Group</a> as a Proposed Recommendation.
+          
+            This document is intended to become a <abbr title="World Wide Web Consortium">W3C</abbr> Recommendation.
+          
+          
+          
+          
+          
+          
+              The <abbr title="World Wide Web Consortium">W3C</abbr> Membership and other interested parties are invited to review the document and
+              send comments to
+              <a rel="discussion" href="mailto:[email protected]">[email protected]</a> 
+              (<a href="mailto:[email protected]?subject=subscribe">subscribe</a>,
+              <a href="http://lists.w3.org/Archives/Public/public-ldp-comments/">archives</a>)
+              through 08 January 2015. Advisory Committee Representatives should consult their
+              <a href="https://www.w3.org/2002/09/wbs/myQuestionnaires">WBS questionnaires</a>. 
+              Note that substantive technical comments were expected during the Last Call review
+              period that ended 07 October 2014.
+          
+        </p>
+        
+          <p>
+            Please see the Working Group's  <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/tests/reports/ldp.html">implementation
+            report</a>.
+          </p>
+        
+        
+        
+          <p>
+            Publication as a Proposed Recommendation does not imply endorsement by the <abbr title="World Wide Web Consortium">W3C</abbr>
+            Membership. This is a draft document and may be updated, replaced or obsoleted by other
+            documents at any time. It is inappropriate to cite this document as other than work in
+            progress.
+          </p>
+        
+        
+        
+        <p>
+          
+            This document was produced by a group operating under the 
+            <a id="sotd_patent" about="" rel="w3p:patentRules" href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 <abbr title="World Wide Web Consortium">W3C</abbr> Patent
+            Policy</a>.
+          
+          
+          
+            
+              <abbr title="World Wide Web Consortium">W3C</abbr> maintains a <a href="http://www.w3.org/2004/01/pp-impl/55082/status" rel="disclosure">public list of any patent
+              disclosures</a> 
+            
+            made in connection with the deliverables of the group; that page also includes
+            instructions for disclosing a patent. An individual who has actual knowledge of a patent
+            which the individual believes contains
+            <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential
+            Claim(s)</a> must disclose the information in accordance with
+            <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section
+            6 of the <abbr title="World Wide Web Consortium">W3C</abbr> Patent Policy</a>.
+          
+          
+        </p>
+        
+          <p>
+            This document is governed by the  <a id="w3c_process_revision" href="http://www.w3.org/2005/10/Process-20051014/">14 October 2005 <abbr title="World Wide Web Consortium">W3C</abbr> Process Document</a>.
+          </p>
+        
+        
+      
+    
+  
+</section><section id="toc"><h2 class="introductory" 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="#link-relations" class="tocxref"><span class="secno">8. </span>Link Relations</a><ul class="toc"><li class="tocline"><a href="#link-relation-describedby" class="tocxref"><span class="secno">8.1 </span>describedby</a></li></ul></li><li class="tocline"><a href="#security" class="tocxref"><span class="secno">9. </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>
+ 
+ 
+<section class="informative" id="intro" typeof="bibo:Chapter" resource="#intro" rel="bibo:Chapter">
+<!--OddPage--><h2 role="heading" id="h2_intro"><span class="secno">1. </span>Introduction</h2><p><em>This section is non-normative.</em></p>
+	<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="#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>
+		<li>When someone looks up a URI, provide useful information, using the standards
+			(<abbr title="Resource Description Framework">RDF</abbr>*, <abbr title="SPARQL Protocol and RDF Query Language">SPARQL</abbr>)
+		</li>
+		<li>Include links to other URIs, so that they can discover more things</li>
+	</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="#dfn-linked-data-platform-resource" class="internalDFN">Linked Data Platform Resources</a>.
+	<a href="http://www.w3.org/TR/ldp-primer/" class="external" title="Linked Data Platform 1.0 Primer" rel="nofollow">LDP Primer</a> 
+	provides an entry-level introduction with many examples in the context of a fictional application.
+	<a href="http://www.w3.org/TR/ldp-bp/" class="external" title="LDP Best Practices and Guidelines" rel="nofollow">LDP Best Practices and Guidelines</a> 
+			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="#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 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="#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="#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="#terms" rel="bibo:Chapter">
+<!--OddPage--><h2 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="#bib-WEBARCH">WEBARCH</a></cite>] and 
+	Hyper-text Transfer Protocol ([<cite><a class="bibref" href="#bib-RFC7230">RFC7230</a></cite>], [<cite><a class="bibref" href="#bib-RFC7231">RFC7231</a></cite>], [<cite><a class="bibref" href="#bib-RFC7232">RFC7232</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="#bib-WEBARCH">WEBARCH</a></cite>].
+		<p></p></dd>
+							
+	<dt>Linked Data</dt>
+	<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 one or more HTTP requests [<cite><a class="bibref" href="#bib-RFC7230">RFC7230</a></cite>].<p></p></dd>
+	
+	<dt>Server</dt>
+	<dd>A program that accepts connections in order to service HTTP requests by sending HTTP responses. 
+		<p>
+		The terms "client" and "server" refer only to the roles that these programs perform for a particular connection.  
+		The same program might act as a client on some connections and a server on others.
+		</p>
+		<p>
+		HTTP enables the use of intermediaries to satisfy requests through a
+		chain of connections.  There are three common forms of HTTP
+		intermediary: proxy, gateway, and tunnel.  In some cases, a single
+		intermediary might act as an origin server, proxy, gateway, or
+		tunnel, switching behavior based on the nature of each request.
+		[<cite><a class="bibref" href="#bib-RFC7230">RFC7230</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="#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="#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> graph. 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="#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="#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>.
+	For example, these can be 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>A <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="#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="#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="#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="#dfn-linked-data-platform-container" class="internalDFN"><abbr title="Linked Data Platform Container">LDPC</abbr></a> that adds the concept of <a title="Membership" href="#dfn-membership" class="internalDFN">membership</a>, allowing 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="#dfn-linked-data-platform-container" class="internalDFN"><abbr title="Linked Data Platform Container">LDPC</abbr></a> 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>
+	that is also 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>
+	<dd>The relationship linking an <abbr title="Linked Data Platform Container">LDPC</abbr> and its member <abbr title="Linked Data Platform Resources">LDPRs</abbr>, 
+	which can be different resources than its <a title="Containment" href="#dfn-containment" class="internalDFN">contained</a> documents.  
+	The <abbr title="Linked Data Platform Container">LDPC</abbr> often assists with managing the membership triples, whether or not the <abbr title="Linked Data Platform Container">LDPC</abbr>'s
+	URI occurs in them.
+	<p></p></dd>
+
+	<dt><dfn id="dfn-membership-triples">Membership triples</dfn></dt>
+	<dd>A set of triples that lists an <abbr title="Linked Data Platform Container">LDPC</abbr>'s members.
+		A <abbr title="Linked Data Platform Container">LDPC</abbr>'s membership triples all have one of the following patterns:
+		<table class="indented">
+		<tbody><tr>
+		<td style="background:#DDDDDD"> <var>membership-constant-URI</var> </td>
+		<td style="background:#FFFFFF"> <var>membership-predicate</var> </td>
+		<td style="background:#CCFFFF"> <var>member-derived-URI</var> </td>
+		</tr>
+		<tr>
+		<td style="background:#CCFFFF"> <var>member-derived-URI</var> </td>
+		<td style="background:#FFFFFF"> <var>membership-predicate</var> </td>
+		<td style="background:#DDDDDD"> <var>membership-constant-URI</var> </td>
+		</tr>
+		</tbody></table>
+		The difference between the two is simply which position member-derived-URI occupies, which is usually
+		driven by the choice of <var>membership-predicate</var>.  Most predicates have a natural forward direction
+		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="#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
+		for the <var>member-derived-URI</var> based on the client's input to the 
+		creation process.</p>
+	<p></p></dd>
+	
+	<dt><dfn id="dfn-membership-predicate">Membership predicate</dfn></dt>
+	<dd>The predicate of all an <abbr title="Linked Data Platform Container">LDPC</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>
+	<dd>The relationship binding an <abbr title="Linked Data Platform Container">LDPC</abbr> to <abbr title="Linked Data Platform Resources">LDPRs</abbr> whose lifecycle it controls and is aware of.  The
+	lifecycle of the contained <abbr title="Linked Data Platform Resource">LDPR</abbr> is limited by the lifecycle of the containing <abbr title="Linked Data Platform Container">LDPC</abbr>;
+	that is, a contained <abbr title="Linked Data Platform Resource">LDPR</abbr> cannot be created (through LDP-defined means) before its containing <abbr title="Linked Data Platform Container">LDPC</abbr> exists.
+	<p></p></dd>
+
+	<dt><dfn id="dfn-containment-triples">Containment triples</dfn></dt>
+	<dd>
+	A set of triples, maintained by the <abbr title="Linked Data Platform Container">LDPC</abbr>, that lists documents created by the <abbr title="Linked Data Platform Container">LDPC</abbr> but not yet deleted.
+	These triples <strong>always</strong> have the form: <var>( <abbr title="Linked Data Platform Container">LDPC</abbr> URI, ldp:contains , document-URI )</var>.
+	<p></p></dd>
+
+	<dt><dfn id="dfn-minimal-container-triples">Minimal-container triples</dfn></dt>
+	<dd>
+	The portion of an <abbr title="Linked Data Platform Container">LDPC</abbr>'s triples that would be present when the container is empty.  Currently, this definition
+	is equivalent to all the <abbr title="Linked Data Platform Container">LDPC</abbr>'s triples minus its containment triples, 
+	and minus its membership triples (if either are considered part of its state), 
+	but if future versions of LDP define additional classes of triples then this definition
+	would expand to subtract out those classes as well.
+	<p></p></dd>
+
+	<dt><dfn id="dfn-ldp-server-managed-triples">LDP-server-managed triples</dfn></dt>
+	<dd>
+	The portion of an LDP's triples whose behavior is constrained directly by this specification; for example,
+	membership triples and containment triples.  This portion of resources' content does <em>not</em>
+	include constraints imposed outside of LDP, for example by other specifications that the server 
+	happens to support, or by <a href="#ldpr-gen-pubclireqs">server implementation decisions</a>.
+	<p></p></dd>
+  </dl>
+
+<section id="conventions" typeof="bibo:Chapter" resource="#conventions" rel="bibo:Chapter">
+<h3 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="#bib-turtle">turtle</a></cite>].</p>
+	<p>Commonly used namespace prefixes:</p>
+	<pre style="word-wrap: break-word; white-space: pre-wrap;">	@prefix dcterms: &lt;http://purl.org/dc/terms/&gt;.
+	@prefix foaf:    &lt;http://xmlns.com/foaf/0.1/&gt;.
+	@prefix rdf:     &lt;http://www.w3.org/1999/02/22-rdf-syntax-ns#&gt;.
+	@prefix ldp:     &lt;http://www.w3.org/ns/ldp#&gt;.
+	@prefix xsd:     &lt;http://www.w3.org/2001/XMLSchema#&gt;.</pre>
+</section>
+</section>
+    
+<section id="conformance" typeof="bibo:Chapter" resource="#conformance" rel="bibo:Chapter"><!--OddPage--><h2 role="heading" id="h2_conformance"><span class="secno">3. </span>Conformance</h2>
+<p>
+  As well as sections marked as non-normative, all authoring guidelines, diagrams, examples,
+  and notes in this specification are non-normative. Everything else in this specification is
+  normative.
+</p>
+<p id="respecRFC2119">The key words <em class="rfc2119" title="MAY">MAY</em>, <em class="rfc2119" title="MUST">MUST</em>, <em class="rfc2119" title="MUST NOT">MUST NOT</em>, <em class="rfc2119" title="RECOMMENDED">RECOMMENDED</em>, <em class="rfc2119" title="SHOULD">SHOULD</em>, and <em class="rfc2119" title="SHOULD NOT">SHOULD NOT</em> are 
+  to be interpreted as described in [<cite><a class="bibref" href="#bib-RFC2119">RFC2119</a></cite>].
+</p>
+
+
+<p>The status of the sections of Linked Data Platform 1.0 (this document) is as follows:</p>
+<ul>
+  <li>1. Introduction: <b>non-normative</b></li>
+  <li>2. Terminology: <b>normative</b></li>
+  <li>3. Conformance: <b>normative</b></li>
+  <li>4. Linked Data Platform Resources: <b>normative</b></li>
+  <li>5. Linked Data Platform Containers: <b>normative</b></li>
+  <li>6. Notable information from normative references: <b>non-normative</b></li>
+  <li>7. HTTP Header Definitions: <b>normative</b></li>
+  <li>8. Security Considerations: <b>non-normative</b></li>
+  <li>A. Acknowledgements: <b>non-normative</b></li> 
+  <li>B. Change History: <b>non-normative</b></li>
+  <li>C.1 Normative references: <b>normative</b></li>
+  <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="#bib-RFC7230">RFC7230</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="#bib-RFC7230">RFC7230</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>
+
+<section id="ldpr" typeof="bibo:Chapter" resource="#ldpr" rel="bibo:Chapter">
+<!--OddPage--><h2 role="heading" id="h2_ldpr"><span class="secno">4. </span>Linked Data Platform Resources</h2>
+
+<section class="informative" id="ldpr-informative" typeof="bibo:Chapter" resource="#ldpr-informative" rel="bibo:Chapter">
+<h3 role="heading" id="h3_ldpr-informative"><span class="secno">4.1 </span>Introduction</h3><p><em>This section is non-normative.</em></p>
+	<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="#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="#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>
+	<ul>
+		<li>What resource representations should be used?</li>
+		<li>How is optimistic collision detection handled for updates?</li>
+		<li>What should client expectations be for changes to linked-to resources,
+				such as type changes?</li>
+		<li>How can the server make it easy for the client to create resources?</li>
+		<li>How	do I GET the representation of a large resource broken up into pages?</li>
+	</ul>
+	<p>Additional non-normative guidance is available in the <a href="http://www.w3.org/TR/ldp-bp/" class="external" title="LDP Best Practices and Guidelines" rel="nofollow">LDP Best Practices and Guidelines</a> that addresses
+		questions such as:</p>
+	<ul>
+		<li>What literal value types should be used?</li>
+		<li>Are there some typical vocabularies that should be reused?</li>
+		<li>What guidelines exist when interacting with <abbr title="Linked Data Platform Resources">LDPRs</abbr> that are common but are not universal enough to specify normatively?</li>
+	</ul>
+	<p>The following sections define the conformance rules for LDP servers when serving <abbr title="Linked Data Platform Resources">LDPRs</abbr>.
+	</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="#bib-LDP-PAGING">LDP-PAGING</a></cite>].
+	</p>
+	<p>A LDP server can manage 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 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="#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>
+    <figure id="fig-ldpr-types">
+        <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="#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>
+     </figure>
+	
+</section>
+
+<section id="ldpr-resource" typeof="bibo:Chapter" resource="#ldpr-resource" rel="bibo:Chapter">
+<h3 role="heading" id="h3_ldpr-resource"><span class="secno">4.2 </span>Resource</h3>
+
+<section id="ldpr-general" typeof="bibo:Chapter" resource="#ldpr-general" rel="bibo:Chapter">
+<h4 role="heading" id="h4_ldpr-general"><span class="secno">4.2.1 </span>General</h4>
+		
+	<section id="ldpr-gen-http" typeof="bibo:Chapter" resource="#ldpr-gen-http" rel="bibo:Chapter"><h5 class="normal" 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-RFC7230">RFC7230</a></cite>].
+	</h5></section><!-- Was 4.2.1 / #ldpr-4_2_1 -->
+	
+	<section id="ldpr-gen-binary" typeof="bibo:Chapter" resource="#ldpr-gen-binary" rel="bibo:Chapter"><h5 class="normal" 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 <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="#ldpr-gen-etags" rel="bibo:Chapter"><h5 class="normal" 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, for responses that contain resource representations or
+		successful responses to HTTP <code>HEAD</code> requests.
+	</h5></section><!-- Was 4.2.8 / #ldpr-4_2_8 -->
+	
+	<section id="ldpr-gen-linktypehdr" typeof="bibo:Chapter" resource="#ldpr-gen-linktypehdr" rel="bibo:Chapter"><h5 class="normal" 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
+		a link relation type of <code>type</code> (that is, <code>rel='type'</code>)
+		in all responses to requests made 
+		to an <abbr title="Linked Data Platform Resource">LDPR</abbr>'s HTTP <code>Request-URI</code> [<cite><a class="bibref" href="#bib-RFC5988">RFC5988</a></cite>]. 
+	</h5></section><!-- Was 4.2.10 / #ldpr-4_2_10 -->
+	<blockquote>
+		<p>
+		Note: 
+		The HTTP <code>Link</code> header is the method by which servers assert their support for the LDP specification 
+		on a specific resource in a way that clients can inspect dynamically at run-time.   
+		This is <strong>not</strong> equivalent to the
+		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 the 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="#ldpr-gen-etags">has Etags</a>, <a href="#ldpr-options-must">supports OPTIONS</a>, and so on,
+		which is not true of all Web resources.
+		</p>
+		<p>
+		Note: 
+		<a href="#ldpr-gen-binary">A LDP server can host a mixture of LDP-RSs and LDP-NRs</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="#ldpr-gen-defbaseuri" rel="bibo:Chapter"><h5 class="normal" 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="#ldpr-gen-pubclireqs" rel="bibo:Chapter"><h5 class="normal" 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
+		an appropriate context URI,
+		a link relation of <code>http://www.w3.org/ns/ldp#constrainedBy</code>,
+		and a target URI identifying a set of constraints
+		[<cite><a class="bibref" href="#bib-RFC5988">RFC5988</a></cite>], to all responses to requests that 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.
+		The same <code>Link</code> header <em class="rfc2119" title="MAY">MAY</em> be provided on other responses.  LDP neither 
+		defines nor constrains the representation of the link's target resource.  Natural language 
+		constraint documents are therefore permitted, 
+		although machine-readable ones facilitate better client interactions.
+		The appropriate context URI can vary based on the request's semantics and method;
+		unless the response is otherwise
+		constrained, the default (the effective request URI) <em class="rfc2119" title="SHOULD">SHOULD</em> be used.
+	</h5></section><!-- Was 4.2.13 / #ldpr-4_2_13 -->
+
+</section>
+
+<section id="ldpr-HTTP_GET" typeof="bibo:Chapter" resource="#ldpr-HTTP_GET" rel="bibo:Chapter">
+<h4 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="#ldpr-get-must" rel="bibo:Chapter"><h5 class="normal" 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="#ldpr-get-options" rel="bibo:Chapter"><h5 class="normal" 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> for the HTTP <code>GET</code> method.
+	</h5></section><!-- Was 4.3.2 / #ldpr-4_3_2 -->
+	
+</section>
+
+<section id="ldpr-HTTP_POST" typeof="bibo:Chapter" resource="#ldpr-HTTP_POST" rel="bibo:Chapter">
+<h4 role="heading" id="h4_ldpr-HTTP_POST"><span class="secno">4.2.3 </span>HTTP POST</h4>
+	<p>
+		Per [<cite><a class="bibref" href="#bib-RFC7231">RFC7231</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 a 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="#ldpc-HTTP_POST" class="sectionRef sec-ref">section <span class="secno">5.2.3</span> <span class="sec-title">HTTP POST</span></a>) to a <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="#ldpr-gen-pubclireqs">must be advertised</a> to clients.
+
+	</p>
+</section>
+
+<section id="ldpr-HTTP_PUT" typeof="bibo:Chapter" resource="#ldpr-HTTP_PUT" rel="bibo:Chapter">
+<h4 role="heading" id="h4_ldpr-HTTP_PUT"><span class="secno">4.2.4 </span>HTTP PUT</h4>
+	<p>
+		Per [<cite><a class="bibref" href="#bib-RFC7231">RFC7231</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 a 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="#ldpr-gen-pubclireqs">must be advertised</a> to clients.
+	</p>
+		
+	<section id="ldpr-put-replaceall" typeof="bibo:Chapter" resource="#ldpr-put-replaceall" rel="bibo:Chapter"><h5 class="normal" 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="#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="#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MAY">MAY</em> ignore <a title="LDP-server-managed triples" href="#dfn-ldp-server-managed-triples" class="internalDFN">LDP-server-managed properties</a>,
+		and <em class="rfc2119" title="MAY">MAY</em> ignore other properties such as <code>dcterms:modified</code> 
+		and <code>dcterms:creator</code> if they are <a href="#ldpr-gen-pubclireqs">handled specially by the server</a>
+		(for example, if the server overrides the value or supplies a default value).
+		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="#ldpr-put-simpleupdate" rel="bibo:Chapter"><h5 class="normal" 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 <a href="#ldpr-gen-pubclireqs">server-specific constraints</a>.  
+		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 -->	
+
+	<section id="ldprs-put-servermanagedprops" typeof="bibo:Chapter" resource="#ldprs-put-servermanagedprops" rel="bibo:Chapter"><h5 class="normal" 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 <a href="#ldpr-gen-pubclireqs">the server does not allow clients to modify</a>, 
+		<a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MUST">MUST</em> 
+		fail the request by responding with a 4xx range status code (typically
+		409 Conflict). 
+		<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.
+	</h5></section><!-- Was 4.5.1.1 / #ldpr-4_5_1_1 -->
+	<blockquote>
+		Non-normative note: Clients might provide properties equivalent to those already in the resource's state,
+		e.g. as part of a GET/update representation/PUT sequence, and those PUT requests are intended to work as long as the 
+		<a title="LDP-server-managed triples" href="#dfn-ldp-server-managed-triples" class="internalDFN">LDP-server-managed properties</a>
+		are identical on the GET response and the subsequent PUT request.
+		This is in contrast to other cases like 
+		<a href="#ldpr-put-replaceall">write-once properties that the server does not allow clients to modify once set</a>; 
+		properties like this are under client and/or server control but are not constrained by LDP, 
+		so they are not <a href="#dfn-ldp-server-managed-triples" class="internalDFN">LDP-server-managed triples</a>.  
+	</blockquote>
+	
+	<section id="ldprs-put-failed" typeof="bibo:Chapter" resource="#ldprs-put-failed" rel="bibo:Chapter"><h5 class="normal" 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="#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-RFC7231">RFC7231</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="#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="#ldpr-put-precond" rel="bibo:Chapter"><h5 class="normal" 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="#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="#bib-RFC7232">RFC7232</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="#ldpr-put-create" rel="bibo:Chapter"><h5 class="normal" 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>
+		
+<section id="ldpr-HTTP_DELETE" typeof="bibo:Chapter" resource="#ldpr-HTTP_DELETE" rel="bibo:Chapter">
+<h4 role="heading" id="h4_ldpr-HTTP_DELETE"><span class="secno">4.2.5 </span>HTTP DELETE</h4>
+	<p>
+		Per [<cite><a class="bibref" href="#bib-RFC7231">RFC7231</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 a LDP server supports this method, 
+		this specification imposes no new blanket requirements for <abbr title="Linked Data Platform Resources">LDPRs</abbr>.
+	</p>
+		
+	<p>Additional requirements on HTTP <code>DELETE</code> for <abbr title="Linked Data Platform Resources">LDPRs</abbr> within containers can be found in
+	<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>
+
+<section id="ldpr-HTTP_HEAD" typeof="bibo:Chapter" resource="#ldpr-HTTP_HEAD" rel="bibo:Chapter">
+<h4 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="#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="#ldpr-head-must" rel="bibo:Chapter"><h5 class="normal" 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="#ldpr-HTTP_PATCH" rel="bibo:Chapter">
+<h4 role="heading" id="h4_ldpr-HTTP_PATCH"><span class="secno">4.2.7 </span>HTTP PATCH</h4>
+	<p>
+		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 a 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="#ldpr-gen-pubclireqs">must be advertised</a> to clients.
+	</p>
+	
+	<section id="ldpr-patch-acceptpatch" typeof="bibo:Chapter" resource="#ldpr-patch-acceptpatch" rel="bibo:Chapter"><h5 class="normal" 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 -->
+
+</section>
+
+<section id="ldpr-HTTP_OPTIONS" typeof="bibo:Chapter" resource="#ldpr-HTTP_OPTIONS" rel="bibo:Chapter">
+<h4 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="#bib-RFC7231">RFC7231</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="#ldpr-options-must" rel="bibo:Chapter"><h5 class="normal" 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="#ldpr-options-allow" rel="bibo:Chapter"><h5 class="normal" 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 -->
+
+</section> <!-- h2 -->
+
+</section> <!-- ldpr-resource -->
+
+<section id="ldprs" typeof="bibo:Chapter" resource="#ldprs" rel="bibo:Chapter">
+<h3 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="#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="#ldprs-general" rel="bibo:Chapter">
+<h4 role="heading" id="h4_ldprs-general"><span class="secno">4.3.1 </span>General</h4>
+
+	<section id="ldprs-are-ldpr" typeof="bibo:Chapter" resource="#ldprs-are-ldpr" rel="bibo:Chapter"><h5 class="normal" 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> as defined in <a href="#ldpr-resource" class="sectionRef sec-ref">section <span class="secno">4.2</span> <span class="sec-title">Resource</span></a>, along with the
+		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: one
+		whose subject is the <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>, 
+		whose predicate is <code>rdf:type</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="#ldprs-gen-atleast1rdftype" rel="bibo:Chapter"><h5 class="normal" 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="#ldprs-rdftype" rel="bibo:Chapter"><h5 class="normal" role="heading" id="h5_ldprs-rdftype"><span class="secno">4.3.1.3 </span>The representation of a <abbr title="Linked Data Platform RDF Source">LDP-RS</abbr> <em class="rfc2119" title="MAY">MAY</em> have an <code>rdf:type</code>
+		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="#ldprs-gen-rdf" rel="bibo:Chapter"><h5 class="normal" 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="#ldprs-gen-reusevocab" rel="bibo:Chapter"><h5 class="normal" 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="#ldprs-gen-reusevocabsuchas" rel="bibo:Chapter"><h5 class="normal" 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="#ldp-cli-multitype" rel="bibo:Chapter"><h5 class="normal" 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="#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 <code>rdf:type</code> triples with different objects.
+	</h5></section> <!-- Was 4.3.5 / #ldpr-4_3_5 -->
+	
+	<section id="ldpr-cli-typeschange" typeof="bibo:Chapter" resource="#ldpr-cli-typeschange" rel="bibo:Chapter"><h5 class="normal" 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="#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="#ldpr-cli-openpreds" rel="bibo:Chapter"><h5 class="normal" 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
+		are used in the state of any one <abbr title="Linked Data Platform RDF Source">LDP-RS</abbr> is not limited to any pre-defined
+		set.
+	</h5></section> <!-- Was 4.5.3 / #ldpr-ldpr-4_5_3 -->
+		
+	<section id="ldprs-gen-noinferencing" typeof="bibo:Chapter" resource="#ldprs-gen-noinferencing" rel="bibo:Chapter"><h5 class="normal" 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="#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="#ldpr-cli-preservetriples" rel="bibo:Chapter"><h5 class="normal" role="heading" id="h5_ldpr-cli-preservetriples"><span class="secno">4.3.1.11 </span>
+		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 a <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="#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="#ldpr-cli-can-hint" rel="bibo:Chapter"><h5 class="normal" role="heading" id="h5_ldpr-cli-can-hint"><span class="secno">4.3.1.12 </span>
+		<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="#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="#ldpr-cli-hints-ignorable" rel="bibo:Chapter"><h5 class="normal" role="heading" id="h5_ldpr-cli-hints-ignorable"><span class="secno">4.3.1.13 </span>
+		<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 a LDP server that ignores hints,
+		including LDP-defined hints.
+	</h5></section>
+	
+</section> <!-- ldprs-general -->
+
+<section id="ldprs-HTTP_GET" typeof="bibo:Chapter" resource="#ldprs-HTTP_GET" rel="bibo:Chapter">
+<h4 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="#ldprs-get-turtle" rel="bibo:Chapter"><h5 class="normal" 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> 
+		respond with a Turtle
+		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> when
+		the request includes an <code>Accept</code> header specifying <code>text/turtle</code>, 
+		unless HTTP content negotiation <em>requires</em> a different outcome 
+		[<cite><a class="bibref" href="#bib-turtle">turtle</a></cite>].
+		</h5>
+		<blockquote>
+		<em>Non-normative note: </em>
+		In other words, Turtle must be returned by <a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> 
+		in the usual case clients would expect (client requests it) 
+		as well as cases where the client requests Turtle or other media type(s), content negotiation results in a tie,
+		and Turtle is one of the tying media types.
+		For example, if the <code>Accept</code> header lists <code>text/turtle</code> as one of several media types with the
+		highest relative quality
+		factor (<code>q=</code> value), <a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> must respond with Turtle.
+		HTTP servers in general are not required to resolve ties in this way, or to support Turtle at all, but
+		<a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> are.
+		On the other hand, if Turtle is one of several requested media types,
+		but another media type the server supports has a higher relative quality factor,
+		standard HTTP content negotiation rules apply and the server (LDP or not) would not respond with Turtle.
+		</blockquote>
+	</section><!-- Was 4.3.3 / #ldpr-4_3_3 -->
+
+	<section id="ldprs-get-conneg" typeof="bibo:Chapter" resource="#ldprs-get-conneg" rel="bibo:Chapter"><h5 class="normal" role="heading" id="h5_ldprs-get-conneg"><span class="secno">4.3.2.2 </span><a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="SHOULD">SHOULD</em>
+		respond with 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> whenever 
+		the <code>Accept</code> request header is absent [<cite><a class="bibref" href="#bib-turtle">turtle</a></cite>].  
+	</h5></section><!-- new -->
+
+	<section id="ldprs-get-jsonld" typeof="bibo:Chapter" resource="#ldprs-get-jsonld" rel="bibo:Chapter"><h5 class="normal" role="heading" id="h5_ldprs-get-jsonld"><span class="secno">4.3.2.3 </span><a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> <em class="rfc2119" title="MUST">MUST</em> 
+		respond with a <code>application/ld+json</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>
+		when the request includes an <code>Accept</code> header, unless content negotiation 
+		or <a href="#ldprs-get-turtle">Turtle support</a>
+		<em>requires</em> a different outcome [<cite><a class="bibref" href="#bib-JSON-LD">JSON-LD</a></cite>].
+	</h5></section><!-- new -->
+
+</section> <!-- ldprs-HTTP_GET -->
+
+</section> <!-- ldprs RDF Source-->
+
+<section id="ldpnr" typeof="bibo:Chapter" resource="#ldpnr" rel="bibo:Chapter">
+<h3 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="#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="#ldpnr-general" rel="bibo:Chapter">
+<h4 role="heading" id="h4_ldpnr-general"><span class="secno">4.4.1 </span>General</h4>
+
+	<section id="ldpnr-are-ldpr" typeof="bibo:Chapter" resource="#ldpnr-are-ldpr" rel="bibo:Chapter"><h5 class="normal" 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> Sources</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 id="ldpnr-type" typeof="bibo:Chapter" resource="#ldpnr-type" rel="bibo:Chapter"><h5 class="normal" role="heading" id="h5_ldpnr-type"><span class="secno">4.4.1.2 </span><a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> exposing an <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="MAY">MAY</em> advertise this by exposing a HTTP <code>Link</code> header
+		with a target URI of <code>http://www.w3.org/ns/ldp#NonRDFSource</code>, and
+		a link relation type of <code>type</code> (that is, <code>rel='type'</code>)
+		in responses to requests made 
+		to the <abbr title="Linked Data Platform Non-RDF Source">LDP-NR</abbr>'s HTTP <code>Request-URI</code> [<cite><a class="bibref" href="#bib-RFC5988">RFC5988</a></cite>].  
+	</h5></section>
+
+</section> <!-- ldpnr Non-RDF Source-->
+
+</section>
+
+</section> <!-- ldpr h1 -->
+
+<section id="ldpc" typeof="bibo:Chapter" resource="#ldpc" rel="bibo:Chapter">
+<!--OddPage--><h2 role="heading" id="h2_ldpc"><span class="secno">5. </span>Linked Data Platform Containers</h2>
+
+<section class="informative" id="ldpc-informative" typeof="bibo:Chapter" resource="#ldpc-informative" rel="bibo:Chapter">		
+<h3 role="heading" id="h3_ldpc-informative"><span class="secno">5.1 </span>Introduction</h3><p><em>This section is non-normative.</em></p>
+	<p>Many HTTP applications and sites have organizing
+		concepts that partition the overall space of resources into smaller
+		containers. Blog posts are grouped into blogs, wiki pages are grouped
+		into wikis, and products are grouped into catalogs. Each resource
+		created in the application or site is created within an instance of
+		one of these container-like entities, and users can list the existing
+		artifacts within one. Containers answer some basic questions, which
+		are:</p>
+	<ol>
+		<li>To which URLs can I POST to create new resources?</li>
+		<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="#bib-LDP-PAGING">LDP-PAGING</a></cite>]</li>
+	</ol>
+	<p>
+		This document defines the representation and behavior of containers
+		that address these issues. There are multiple types of containers defined
+		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="#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="#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, 
+		and either the subject or the object is also a consistent value
+		– the remaining position of the membership
+		triples (the one that varies) define the members of the container. 
+		In the simplest cases, the
+		consistent value will be the <abbr title="Linked Data Platform Container">LDPC</abbr> resource's URI, but it does not
+		have to be. The membership predicate is also variable and will often
+		be a predicate from the server application vocabulary or the <code>ldp:member</code> predicate.
+	</p>
+	<p>In LDP 1.0, there exists a way for clients to request responses that contain only
+	partial representations of the containers.  Applications may define additional means
+	by which the response representations contain a filtered set of data and including (or excluding)
+	additional details, those means are application-specific and not defined in this document.</p>
+	<p>This document includes a set of guidelines for
+		creating new resources and adding them to the list of
+		resources linked to a container. It goes on to explain how to learn about a set of related
+		resources, regardless of how they were created or added to the container's membership.
+		It also defines behavior when resources created using a container are later deleted;
+		deleting containers removes membership information and
+		possibly performs some cleanup tasks on unreferenced member resources.</p>
+
+	<p>The following illustrates a very simple
+		container with only three members and some information about the
+		container (the fact that it is a container and a brief title):</p>
+
+<em>Request</em> to <code>http://example.org/c1/</code>:
+<div class="example"><div class="example-title"><span>Example 1</span></div><pre class="example" id="ldpc-ex-simple-req">GET /c1/ HTTP/1.1
+Host: example.org
+Accept: text/turtle</pre></div>
+
+<em>Response:</em>
+<div class="example"><div class="example-title"><span>Example 2</span></div><pre class="example" id="ldpc-ex-simple">HTTP/1.1 200 OK
+Content-Type: text/turtle
+Date: Thu, 12 Jun 2014 18:26:59 GMT
+ETag: "8caab0784220148bfe98b738d5bb6d13"
+Accept-Post: text/turtle, application/ld+json
+Allow: POST,GET,OPTIONS,HEAD,PUT
+Link: &lt;http://www.w3.org/ns/ldp#BasicContainer&gt;; rel="type",
+      &lt;http://www.w3.org/ns/ldp#Resource&gt;; rel="type"
+Transfer-Encoding: chunked
+<!-- @base <http://example.org/c1></http:>. -->
[email protected] dcterms: &lt;http://purl.org/dc/terms/&gt;.
[email protected] ldp: &lt;http://www.w3.org/ns/ldp#&gt;.
+
+&lt;http://example.org/c1/&gt;
+   a ldp:BasicContainer;
+   dcterms:title "A very simple container";
+   ldp:contains &lt;r1&gt;, &lt;r2&gt;, &lt;r3&gt;.</pre></div>
+ 
+ <!-- TODO: consider if basic container diagram helps, if so...add for other cases too
+   	<figure id="fig-ldpc-basic">
+        <img src="images/ldpc-basic.png" alt="Sample Linked Data Platform Basic Container" />
+        <figcaption>Sample of Linked Data Platform Basic Container</figcaption>
+    </figure>
+     -->
+
+	<p>The preceding example is very straightforward: there are containment triples
+	whose subject is the container, whose predicate is  
+	<code>ldp:contains</code>, and whose objects are the URIs of the contained resources,
+	and there is no distinction between member resources and contained resources. 
+	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 called a
+	<a title="" href="#dfn-linked-data-platform-basic-container" class="internalDFN">Linked Data Platform Basic Container</a>.  </p>
+
+	<p>
+	Sometimes you have to build on existing models incrementally, so you have fewer degrees of
+	freedom in the resource model.  In these situations, it can be useful to help clients map
+	LDP patterns onto existing vocabularies, or to include members not created via the container; 
+	<a title="Linked Data Platform Direct Container" href="#dfn-linked-data-platform-direct-container" class="internalDFN">LDP Direct Containers</a>
+	meet those kinds of needs.  Direct Containers allow membership triples to use a subject
+	other than the container itself as the consistent membership value, and/or to use
+	a  predicate from an application's domain model as the membership predicate. Let's
+	start with a pre-existing domain resource for a person's net worth, as illustrated below:</p>
+			
+<em>Request</em> to <code>http://example.org/netWorth/nw1/</code>:
+<div class="example"><div class="example-title"><span>Example 3</span></div><pre class="example" id="ldpc-ex-membership-partial-req">GET /netWorth/nw1/ HTTP/1.1
+Host: example.org
+Accept: text/turtle</pre></div>
+
+<em>Response:</em>
+<div class="example"><div class="example-title"><span>Example 4</span></div><pre class="example" id="ldpc-ex-membership-partial">HTTP/1.1 200 OK
+Content-Type: text/turtle
+Date: Thu, 12 Jun 2014 18:26:59 GMT
+ETag: "0f6b5bd8dc1f754a1238a53b1da34f6b"
+Link: &lt;http://www.w3.org/ns/ldp#RDFSource&gt;; rel="type",
+      &lt;http://www.w3.org/ns/ldp#Resource&gt;; rel="type"
+Allow: GET,OPTIONS,HEAD,PUT,DELETE
+Transfer-Encoding: chunked
+<!-- @base <http://example.org/netWorth/nw1></http:>. -->
[email protected] ldp: &lt;http://www.w3.org/ns/ldp#&gt;.
[email protected] o: &lt;http://example.org/ontology#&gt;.
+
+&lt;http://example.org/netWorth/nw1/&gt;
+   a o:NetWorth;
+   o:netWorthOf &lt;http://example.org/users/JohnZSmith&gt;;
+   o:asset 
+      &lt;assets/a1&gt;,
+      &lt;assets/a2&gt;;
+   o:liability 
+      &lt;liabilities/l1&gt;,
+      &lt;liabilities/l2&gt;,
+      &lt;liabilities/l3&gt;.</pre></div>
+	<p>
+	In the preceding example, there is a <code>rdf:type</code> of <code>o:NetWorth</code> indicating the
+	resource represents an instance of a person's net worth and a <code>o:netWorthOf</code> predicate indicating 
+	the associated person.  There are two sets of same-subject, same-predicate triples; one for assets and
+	one for liabilities.  Existing domain-specific applications exist that depend on those types and 
+	predicates, so changing them <em>incompatibly</em> would be frowned upon.
+	</p>
+	
+	<p>
+	It would be helpful to be able to use LDP patterns to manage the assets and liabilities-related triples.
+	Doing so using a Basic Container would require duplicating much of the information with different types and
+	predicates, which would be onerous for large resources.  <a title="Linked Data Platform Direct Container" href="#dfn-linked-data-platform-direct-container" class="internalDFN">Direct Containers</a>
+	provide a middle ground, by giving LDP clients a way to map existing domain-specific resources to LDP's
+	types and interaction models.  
+	In this specific example, 
+	it would be helpful to be able to manage the assets and liabilities triples consistently, for example
+	by using LDP containers.
+	One way to do this is to create two containers, one to manage assets and another liabilities, 
+	as separate HTTP resources.  Existing clients have no need to interact with those containers,
+	whereas LDP-enabled clients now have container URLs that they can interact with.  The existing
+	resource remains unchanged so that existing clients continue to function normally.
+	This is illustrated in the set of related examples, one example per HTTP resource, starting with
+	the <abbr title="Linked Data Platform RDF Source">LDP-RS</abbr> example from before:
+	</p>
+	
+<em>Request</em> to <code>http://example.org/netWorth/nw1/</code>:
+<div class="example"><div class="example-title"><span>Example 5</span></div><pre class="example" id="ldpc-ex-membership-full-req">GET /netWorth/nw1/ HTTP/1.1
+Host: example.org
+Accept: text/turtle</pre></div>
+
+<em>Response:</em>
+<div class="example"><div class="example-title"><span>Example 6</span></div><pre class="example" id="ldpc-ex-membership-full">HTTP/1.1 200 OK
+Content-Type: text/turtle
+Date: Thu, 12 Jun 2014 18:26:59 GMT
+ETag: "0f6b5bd8dc1f754a1238a53b1da34f6b"
+Link: &lt;http://www.w3.org/ns/ldp#RDFSource&gt;; rel="type",
+      &lt;http://www.w3.org/ns/ldp#Resource&gt;; rel="type"
+Allow: GET,OPTIONS,HEAD,PUT,DELETE
+Transfer-Encoding: chunked
+<!-- @base <http://example.org/netWorth/nw1></http:>. -->
[email protected] ldp: &lt;http://www.w3.org/ns/ldp#&gt;.
[email protected] o: &lt;http://example.org/ontology#&gt;.
+
+&lt;http://example.org/netWorth/nw1/&gt;
+   a o:NetWorth;
+   o:netWorthOf &lt;http://example.org/users/JohnZSmith&gt;;
+   o:asset 
+      &lt;assets/a1&gt;,
+      &lt;assets/a2&gt;;
+   o:liability 
+      &lt;liabilities/l1&gt;,
+      &lt;liabilities/l2&gt;,
+      &lt;liabilities/l3&gt;.</pre></div>
+
+
+	<p>The structure of the net worth resource is completely unchanged, so any existing 
+	domain-specific applications continue to work without impact.
+	LDP clients, on the other hand, have no way to understand that the asset and
+	liability triples correspond in any way to LDP containers.  For that, they need the
+	next two resources.
+	</p>
+	<p>The first container is a <a title="Linked Data Platform Direct Container" href="#dfn-linked-data-platform-direct-container" class="internalDFN">LDP Direct Container</a> to manage assets.  
+	Direct Containers add the concept of <a title="Membership" href="#dfn-membership" class="internalDFN">membership</a>
+	and flexibility on how to specify the <a title="Membership triples" href="#dfn-membership-triples" class="internalDFN">membership triples</a>.
+	</p>
+
+<em>Request</em> to <code>http://example.org/netWorth/nw1/assets/</code>:
+<div class="example"><div class="example-title"><span>Example 7</span></div><pre class="example" id="ldpc-ex-membership-subj-req">GET /netWorth/nw1/assets/ HTTP/1.1
+Host: example.org
+Accept: text/turtle</pre></div>
+
+<em>Response:</em>
+<div class="example"><div class="example-title"><span>Example 8</span></div><pre class="example" id="ldpc-ex-membership-subj">HTTP/1.1 200 OK
+Content-Type: text/turtle
+Date: Thu, 12 Jun 2014 18:26:59 GMT
+ETag: "6df36eef2631a1795bfe9ab76760ea75"
+Accept-Post: text/turtle, application/ld+json
+Allow: POST,GET,OPTIONS,HEAD
+Link: &lt;http://www.w3.org/ns/ldp#DirectContainer&gt;; rel="type",
+      &lt;http://www.w3.org/ns/ldp#Resource&gt;; rel="type"
+Transfer-Encoding: chunked
+<!-- @base <http://example.org/netWorth/nw1/assets></http:>. -->      
[email protected] ldp: &lt;http://www.w3.org/ns/ldp#&gt;.
[email protected] dcterms: &lt;http://purl.org/dc/terms/&gt;.
[email protected] o: &lt;http://example.org/ontology#&gt;.
+
+&lt;http://example.org/netWorth/nw1/assets/&gt;
+   a ldp:DirectContainer;
+   dcterms:title "The assets of JohnZSmith";
+   ldp:membershipResource &lt;http://example.org/netWorth/nw1/&gt;;
+   ldp:hasMemberRelation o:asset;
+   ldp:contains &lt;a1&gt;, &lt;a2&gt;.</pre></div>
+
+	<p>
+	In the preceding asset container, the consistent membership value 
+	(<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 the (separate) net worth resource. The
+	membership predicate is <code>o:asset</code>,
+	from the domain model. A POST of an asset representation to the asset container will create a new
+	asset and add it to net-worth's list of	assets by adding a new membership triple
+	to the resource and a containment triple to the container. 
+	</p>
+
+	<p>The second container is a <a title="Linked Data Platform Direct Container" href="#dfn-linked-data-platform-direct-container" class="internalDFN">LDP Direct Container</a> to manage liabilities.  
+	</p>
+<em>Request</em> to <code>http://example.org/netWorth/nw1/liabilities/</code>:
+<div class="example"><div class="example-title"><span>Example 9</span></div><pre class="example" id="ldpc-ex-membership-full-liabcont-req">GET /netWorth/nw1/liabilities/ HTTP/1.1
+Host: example.org
+Accept: text/turtle</pre></div>
+
+<em>Response:</em>
+<div class="example"><div class="example-title"><span>Example 10</span></div><pre class="example" id="ldpc-ex-membership-full-liabcont">HTTP/1.1 200 OK
+Content-Type: text/turtle
+Date: Thu, 12 Jun 2014 18:26:59 GMT
+ETag: "9f50da01f792281ddcfebe9788372d07"
+Link: &lt;http://www.w3.org/ns/ldp#DirectContainer&gt;; rel="type",
+      &lt;http://www.w3.org/ns/ldp#Resource&gt;; rel="type"
+Accept-Post: text/turtle, application/ld+json
+Allow: POST,GET,OPTIONS,HEAD
+Transfer-Encoding: chunked
+<!-- @base <http://example.org/netWorth/nw1/liabilities></http:>. -->
[email protected] ldp: &lt;http://www.w3.org/ns/ldp#&gt;.
[email protected] dcterms: &lt;http://purl.org/dc/terms/&gt;.
[email protected] o: &lt;http://example.org/ontology#&gt;.
+
+&lt;http://example.org/netWorth/nw1/liabilities/&gt;
+   a ldp:DirectContainer;
+   dcterms:title "The liabilities of JohnZSmith";
+   ldp:membershipResource &lt;http://example.org/netWorth/nw1/&gt;;
+   ldp:hasMemberRelation o:liability;
+   ldp:contains &lt;l1&gt;, &lt;l2&gt;, &lt;l3&gt;.</pre></div>
+
+	<p>
+	The preceding liability container is completely analogous to the asset container above, simply
+	managing liabilities instead of assets and using the <code>o:liability</code> predicate.
+	</p>
+	<p>
+	To add a another liability, a client would POST something like this to the liability container:
+	</p>
+
+<em>Request</em> to <code>http://example.org/netWorth/nw1/liabilities/</code>:
+<div class="example"><div class="example-title"><span>Example 11</span></div><pre class="example" id="ldpc-ex-membership-add-new-liability-req">POST /netWorth/nw1/liabilities/ HTTP/1.1
+Host: example.org
+Accept: text/turtle
+Content-Type: text/turtle
+Content-Length: 63
+<!-- @base is here only so it's easier to paste into validators for checking -->
[email protected] o: &lt;http://example.org/ontology#&gt;.
+
+&lt;&gt;
+   a o:Liability.
+   # plus any other properties that the domain says liabilities have</pre></div>
+
+<em>Response:</em>
+<div class="example"><div class="example-title"><span>Example 12</span></div><pre class="example" id="ldpc-ex-membership-add-new-liability">HTTP/1.1 201 Created
+Location: http://example.org/netWorth/nw1/liabilities/l4
+Date: Thu, 12 Jun 2014 19:56:13 GMT
+Link: &lt;http://www.w3.org/ns/ldp#DirectContainer&gt;; rel="type",
+      &lt;http://www.w3.org/ns/ldp#Resource&gt;; rel="type"</pre></div>
+
+	<p>
+	Assuming the server successfully processes this request and assigns the URI
+	<code>&lt;http://example.org/netWorth/nw1/liabilities/l4&gt;</code> to the 
+	newly created liability resource, at least two new triples would be added.
+	</p>
+	<ol>
+	<li>In the net worth resource, <code>&lt;http://example.org/netWorth/nw1/&gt; o:liability &lt;liabilities/l4&gt;</code></li>
+	<li>In the liability container, <code>&lt;http://example.org/netWorth/nw1/liabilities/&gt; ldp:contains &lt;l4&gt;</code>.</li>
+	</ol>
+
+	<p>
+	You might wonder why we chose to create two new containers instead of making
+	<code>http://example.org/netWorth/nw1/</code> itself a container.
+	A single net worth container would be a fine design if <code>http://example.org/netWorth/nw1/</code>
+	had only assets or only liabilities (basically: only a single predicate to manage), 
+	but since it has separate predicates for assets and liabilities an ambiguity arises:
+	it is unspecified whether a client's creation request (POST)
+	should add a new <code>o:asset</code> or <code>o:liability</code> triple. 
+	Having separate <code>http://example.org/netWorth/nw1/assets/</code> 
+	and <code>http://example.org/netWorth/nw1/liabilities/</code> containers
+	allows both assets and liabilities to be created 
+	and linked to the net-worth resource using the appropriate predicate.  Similar ambiguities arise
+	if the client wishes to list the members and/or contained resources.
+	</p>
+	
+	<p>Continuing in the multiple containers direction, we will now extend our net worth example to add a container for
+	advisors (people) that have managed the assets and liabilities.  We have decided
+	to identify these advisors with URLs that contain a fragment (hash) to represent
+	these real-world resources, not the documents that describe them.</p>
+
+<em>Request</em> to <code>http://example.org/netWorth/nw1/</code>:
+<div class="example"><div class="example-title"><span>Example 13</span></div><pre class="example" id="ldpc-ex-membership-full-elab-req">GET /netWorth/nw1/ HTTP/1.1
+Host: example.org
+Accept: text/turtle</pre></div>
+
+<em>Response:</em>
+<div class="example"><div class="example-title"><span>Example 14</span></div><pre class="example" id="ldpc-ex-membership-full-elab">HTTP/1.1 200 OK
+Content-Type: text/turtle
+Date: Thu, 12 Jun 2014 18:26:59 GMT
+ETag: "e8d129f45ca31848fb56213844a32b49"
+Link: &lt;http://www.w3.org/ns/ldp#DirectContainer&gt;; rel="type",
+      &lt;http://www.w3.org/ns/ldp#Resource&gt;; rel="type"
+Allow: GET,OPTIONS,HEAD,PUT,DELETE
+Transfer-Encoding: chunked
+<!-- @base <http://example.org/netWorth/nw1></http:>. -->
[email protected] ldp: &lt;http://www.w3.org/ns/ldp#&gt;.
[email protected] dcterms: &lt;http://purl.org/dc/terms/&gt;.
[email protected] foaf: &lt;http://xmlns.com/foaf/0.1/&gt;.
[email protected] o: &lt;http://example.org/ontology#&gt;.
+
+&lt;http://example.org/netWorth/nw1/&gt;
+   a o:NetWorth;
+   o:netWorthOf &lt;http://example.org/users/JohnZSmith&gt;;
+   o:advisor
+   	 &lt;advisors/bob#me&gt;,     # URI of a person
+   	 &lt;advisors/marsha#me&gt;.
+   	 
+&lt;advisors/&gt;
+   a ldp:IndirectContainer;
+   dcterms:title "The asset advisors of JohnZSmith";
+   ldp:membershipResource &lt;&gt;;
+   ldp:hasMemberRelation o:advisor;
+   ldp:insertedContentRelation foaf:primaryTopic;
+   ldp:contains
+   	 &lt;advisors/bob&gt;,     # URI of a document a.k.a. an information resource
+   	 &lt;advisors/marsha&gt;.  # describing a person</pre></div>	
+	
+	<p>To handle this type of indirection, the triple with predicate of <code>ldp:insertedContentRelation</code> and object of 
+	<code>foaf:primaryTopic</code> informs clients that when POSTing to this container, they need to include a triple of the
+	form <code>(&lt;&gt;, 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 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 a member any resource, 
+	including a URI representing a real-world object.  Create requests to 
+	<a title="Linked Data Platform Direct Container" href="#dfn-linked-data-platform-direct-container" class="internalDFN">LDP Direct Containers</a> 
+	can only add information resources [<cite><a class="bibref" href="#bib-WEBARCH">WEBARCH</a></cite>] - the documents they create - as members.
+	</p>
+
+	<p>
+	To add a another advisor, a client would POST something like this to the advisors container:
+	</p>
+<em>Request</em> to <code>http://example.org/netWorth/nw1/advisors/</code>:
+<div class="example"><div class="example-title"><span>Example 15</span></div><pre class="example" id="ldpc-ex-membership-add-new-advisor-req">POST /netWorth/nw1/advisors/ HTTP/1.1
+Host: example.org
+Accept: text/turtle
+Content-Type: text/turtle
+Slug: george
+Content-Length: 72
+<!-- @base <http://example.org/netWorth/nw1/advisors/george>. -->
[email protected] foaf: &lt;http://xmlns.com/foaf/0.1/&gt;.
[email protected] o: &lt;http://example.org/ontology#&gt;.
+&lt;&gt;
+   a o:Advisor;
+   foaf:primaryTopic &lt;#me&gt;.
+   # plus any other properties that the domain says advisors have</pre></div>
+
+<em>Response:</em>
+<div class="example"><div class="example-title"><span>Example 16</span></div><pre class="example" id="ldpc-ex-membership-add-new-advisor">HTTP/1.1 201 Created
+Location: http://example.org/netWorth/nw1/advisors/george
+Date: Thu, 12 Jun 2014 19:56:13 GMT
+Link: &lt;http://www.w3.org/ns/ldp#RDFSource&gt;; rel="type",
+      &lt;http://www.w3.org/ns/ldp#Resource&gt;; rel="type"</pre></div>
+
+	<p>
+	Assuming the server successfully processes this request and assigns the URI
+	<code>&lt;http://example.org/netWorth/nw1/advisors/george&gt;</code> to the 
+	newly created advisor resource, at least two new triples would be added.
+	</p>
+	<ol>
+	<li>In the net worth resource, <code>&lt;http://example.org/netWorth/nw1/&gt; o:advisor &lt;advisors/george#me&gt;</code></li>
+	<li>In the advisors container, <code>&lt;http://example.org/netWorth/nw1/advisors/&gt; ldp:contains &lt;george&gt;</code></li>
+	</ol>
+
+	<p>In summary, <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 LDP-defined container types: Basic, Direct, and Indirect, along
+	with their class relationship to types of <abbr title="Linked Data Platform Resources">LDPRs</abbr>.</p>
+	
+	 <figure id="fig-ldpc-types">
+        <img src="images/ldpc-hierarchy.png" alt="Types of Linked Data Platform Containers">
+        <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="#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 style="border: 1px solid gray" id="ldpc-mbrcntdiff">
+		<thead><tr><th rowspan="2">Completed Request</th><th style="background:#FFFFFF;" 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>
+		<tr><td><abbr title="Linked Data Platform Resource">LDPR</abbr> created in <abbr title="Linked Data Platform Direct Container">LDP-DC</abbr></td><td>New triple links <abbr title="Linked Data Platform RDF Source">LDP-RS</abbr> to created <abbr title="Linked Data Platform Resource">LDPR</abbr>. <abbr title="Linked Data Platform RDF Source">LDP-RS</abbr> URI may be same as <abbr title="Linked Data Platform Direct Container">LDP-DC</abbr></td>
+			<td>New triple: (<abbr title="Linked Data Platform Container">LDPC</abbr>, ldp:contains, <abbr title="Linked Data Platform Resource">LDPR</abbr>)</td></tr>
+		<tr><td><abbr title="Linked Data Platform Resource">LDPR</abbr> created in <abbr title="Linked Data Platform Indirect Container">LDP-IC</abbr></td><td>New triple links <abbr title="Linked Data Platform RDF Source">LDP-RS</abbr> to content indicated URI</td>
+			<td>New triple: (<abbr title="Linked Data Platform Container">LDPC</abbr>, ldp:contains, <abbr title="Linked Data Platform Resource">LDPR</abbr>)</td></tr>
+		<tr><td><abbr title="Linked Data Platform Resource">LDPR</abbr> is deleted</td><td>Membership triple may be removed</td><td>(<abbr title="Linked Data Platform Container">LDPC</abbr>, ldp:contains, <abbr title="Linked Data Platform Resource">LDPR</abbr>) triple is removed
+			</td></tr>
+		<tr><td><abbr title="Linked Data Platform Container">LDPC</abbr> is deleted</td><td>Triples and member resources may be removed</td><td>Triples of form 
+			(<abbr title="Linked Data Platform Container">LDPC</abbr>, ldp:contains, <abbr title="Linked Data Platform Resource">LDPR</abbr>) and contained <abbr title="Linked Data Platform Resources">LDPRs</abbr> may be removed</td></tr>
+	</tbody></table>
+
+<section id="ldpc-get_minimal-container_props" typeof="bibo:Chapter" resource="#ldpc-get_minimal-container_props" rel="bibo:Chapter"><h4 class="normal" role="heading" id="h4_ldpc-get_minimal-container_props"><span class="secno">5.1.1 </span>Retrieving Only Minimal-Container Triples
+	</h4><!-- Was 5.1.1 / #ldpc-get_minimal-container_props -->
+	<p>The representation of a container
+		that has many members will be large. There are several important
+		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="Minimal-container triples" href="#dfn-minimal-container-triples" class="internalDFN">minimal-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
+		overhead on servers, we define a way to retrieve only
+		these property values (and more generally, a way to retrieve only the 
+		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="#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 minimal-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="#bib-sparql11-query">sparql11-query</a></cite>]</p>
+	<p>
+		Here is an example requesting the minimal-container triples of a
+		container identified by the URL <code>http://example.org/container1/</code>.
+	</p>
+<p id="ldpc-ex-minimal-container"><em>Request</em> to <code>http://example.org/container1/</code>:</p>
+<div class="example"><div class="example-title"><span>Example 17</span></div><pre class="example">GET /container1/ HTTP/1.1
+Host: example.org
+Accept: text/turtle
+Prefer: return=representation; include="http://www.w3.org/ns/ldp#PreferMinimalContainer"</pre></div>
+<p><em>Response:</em></p>
+<div class="example"><div class="example-title"><span>Example 18</span></div><pre class="example">HTTP/1.1 200 OK
+Content-Type: text/turtle
+ETag: "_87e52ce291112"
+Link: &lt;http://www.w3.org/ns/ldp#DirectContainer&gt;; rel="type",
+      &lt;http://www.w3.org/ns/ldp#Resource&gt;; rel="type"
+Accept-Post: text/turtle, application/ld+json
+Allow: POST,GET,OPTIONS,HEAD
+Preference-Applied: return=representation
+Transfer-Encoding: chunked
+
[email protected] dcterms: &lt;http://purl.org/dc/terms/&gt;.
[email protected] ldp: &lt;http://www.w3.org/ns/ldp#&gt;.
+
+&lt;http://example.org/container1/&gt;
+   a ldp:DirectContainer;
+   dcterms:title "A Linked Data Platform Container of Acme Resources";
+   ldp:membershipResource &lt;http://example.org/container1/&gt;;
+   ldp:hasMemberRelation ldp:member;
+   ldp:insertedContentRelation ldp:MemberSubject;
+   dcterms:publisher &lt;http://acme.com/&gt;.</pre></div>
+   
+	<p>
+		LDP recommends using PATCH to update these properties, if necessary.  It provides no facility
+		for updating them via PUT without replacing the entire container's state.
+	</p>
+	</section><!-- ldpc-get_minimal-container_props -->
+
+</section>
+
+<section id="ldpc-container" typeof="bibo:Chapter" resource="#ldpc-container" rel="bibo:Chapter">
+<h3 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="#dfn-linked-data-platform-container" class="internalDFN">Linked Data Platform Container</a>.</p>
+
+<section id="ldpc-general" typeof="bibo:Chapter" resource="#ldpc-general" rel="bibo:Chapter">
+<h4 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="#ldpc-isldpr" rel="bibo:Chapter"><h5 class="normal" 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: one
+	whose subject is the <a title="Linked Data Platform Container" href="#dfn-linked-data-platform-container" class="internalDFN"><abbr title="Linked Data Platform Container">LDPC</abbr></a>, 
+	whose predicate is <code>rdf:type</code>, 
+	and whose object is <code>ldp:RDFSource</code>, 
+	but there is no requirement to materialize this triple in the <abbr title="Linked Data Platform Container">LDPC</abbr> representation.
+	</h5></section><!-- Was 5.2.1 / #ldpc-5_2_1 -->
+		
+	<section id="ldpc-typecontainer" typeof="bibo:Chapter" resource="#ldpc-typecontainer" rel="bibo:Chapter"><h5 class="normal" role="heading" id="h5_ldpc-typecontainer"><span class="secno">5.2.1.2 </span>The representation of a <abbr title="Linked Data Platform Container">LDPC</abbr> <em class="rfc2119" title="MAY">MAY</em> have an <code>rdf:type</code>
+		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="#ldpc-nordfcontainertypes" rel="bibo:Chapter"><h5 class="normal" 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="#ldpc-linktypehdr" rel="bibo:Chapter"><h5 class="normal" 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
+		server supports, and
+		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="#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>
+	<blockquote>
+	<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="#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>
+	</blockquote>
+	</section><!-- Was 5.2.11 / #ldpc-5_2_11 -->
+	
+	<section id="ldpc-prefer" typeof="bibo:Chapter" resource="#ldpc-prefer" rel="bibo:Chapter"><h5 class="normal" 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="#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 a <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="#bib-LDP-PAGING">LDP-PAGING</a></cite>].
+	</h5></section>
+	
+</section>
+
+<section id="ldpc-HTTP_GET" typeof="bibo:Chapter" resource="#ldpc-HTTP_GET" rel="bibo:Chapter">	
+<h4 role="heading" id="h4_ldpc-HTTP_GET"><span class="secno">5.2.2 </span>HTTP GET</h4>
+	<p>
+		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>
+
+<section id="ldpc-HTTP_POST" typeof="bibo:Chapter" resource="#ldpc-HTTP_POST" rel="bibo:Chapter">
+<h4 role="heading" id="h4_ldpc-HTTP_POST"><span class="secno">5.2.3 </span>HTTP POST</h4>
+	<p>
+		Per [<cite><a class="bibref" href="#bib-RFC7231">RFC7231</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 a 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="#ldpr-gen-pubclireqs">must be advertised</a> to clients.
+	</p>
+		
+	<section id="ldpc-post-created201" typeof="bibo:Chapter" resource="#ldpc-post-created201" rel="bibo:Chapter"><h5 class="normal" role="heading" id="h5_ldpc-post-created201"><span class="secno">5.2.3.1 </span>LDP 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="#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.
+	</h5></section><!-- Was 5.4.1 / #ldpc-5_4_1 -->
+
+	<section id="ldpc-post-createdmbr-contains" typeof="bibo:Chapter" resource="#ldpc-post-createdmbr-contains" rel="bibo:Chapter"><h5 class="normal" 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 a <abbr title="Linked Data Platform Container">LDPC</abbr> results in the creation of a <abbr title="Linked Data Platform Resource">LDPR</abbr>, a 
+		<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 the <abbr title="Linked Data Platform Container">LDPC</abbr>
+		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>).  Other triples may be added as well.
+		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. 
+	</h5></section>
+	
+	<section id="ldpc-post-createbins" typeof="bibo:Chapter" resource="#ldpc-post-createbins" rel="bibo:Chapter"><h5 class="normal" 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 a <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="#ldpc-post-createrdf" rel="bibo:Chapter"><h5 class="normal" 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). 
+		If any requested interaction 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 -->
+	<blockquote>
+	<ul>
+	<li>If the request header specifies <a href="#ldpr-gen-linktypehdr">a <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 a <abbr title="Linked Data Platform Resource">LDPR</abbr>.
+	When the
+	server treats the resource as a <abbr title="Linked Data Platform Resource">LDPR</abbr>, then clients can only depend upon behaviors defined by <abbr title="Linked Data Platform Resources">LDPRs</abbr>, 
+	even if the content contains an <code>rdf:type</code> triple indicating a type of <abbr title="Linked Data Platform Container">LDPC</abbr>.
+	That is, if the server's statement conflicts with the content's, the server's statement wins.</li>
+	<li>If the request header specifies <a href="#ldpc-linktypehdr">a <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 a <abbr title="Linked Data Platform Container">LDPC</abbr>.
+	</li>
+	<li>This specification does not constrain the server's behavior in other cases.</li>
+	</ul>
+	<p>Clients use the same syntax, that is <code>HTTP Link</code> headers, to specify the desired interaction model
+		when creating a resource as servers use to advertise it on responses.
+	</p>
+	<p>Note: A consequence of <a href="#ldpc-post-createrdf">this</a> 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>
+	<p>Non-normative note: LDP assumes that the interaction model of a resource is fixed when the resource is created,
+	    and this is reflected in the language of the bullets.  If an implementation were to extend LDP by allowing the
+		interaction model to vary after creation, that is viewed as a compatible extension to LDP and the statements 
+		above would constrain the default interaction model rather than saying that no other behavior is possible.
+	</p>
+	</blockquote>
+	</section>
+	
+	<section id="ldpc-post-turtle" typeof="bibo:Chapter" resource="#ldpc-post-turtle" rel="bibo:Chapter"><h5 class="normal" 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> 
+		that allow creation of <a title="Linked Data Platform RDF Source" href="#dfn-linked-data-platform-rdf-source" class="internalDFN">LDP-RSs</a> via POST <em class="rfc2119" title="MUST">MUST</em> 
+		allow clients to create new members by enclosing a request entity body with a 
+	    <code>Content-Type</code> request header whose value is <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="#ldpc-post-contenttype" rel="bibo:Chapter"><h5 class="normal" 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 request representation's 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="#ldpc-post-rdfnullrel" rel="bibo:Chapter"><h5 class="normal" role="heading" id="h5_ldpc-post-rdfnullrel"><span class="secno">5.2.3.7 </span><a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a>  
+		creating a <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> via POST <em class="rfc2119" title="MUST">MUST</em> 
+		interpret the null relative
+		URI for the subject of triples in the <abbr title="Linked Data Platform RDF Source">LDP-RS</abbr> representation in the
+		request entity body as identifying 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
+		triples whose subject is the null relative URI result in
+		triples in the created resource whose subject is the created
+		resource.  
+	</h5></section><!-- Was 5.4.7 / #ldpc-5_4_7 -->	
+	<!-- TODO: add link to "relative URIs on post-create are dangerous" -->	
+	
+	<section id="ldpc-post-serverassignuri" typeof="bibo:Chapter" resource="#ldpc-post-serverassignuri" rel="bibo:Chapter"><h5 class="normal" 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="#ldpc-post-mincontraints" rel="bibo:Chapter"><h5 class="normal" 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="#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="#ldpc-post-slug" rel="bibo:Chapter"><h5 class="normal" 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="#ldpc-post-dontreuseuris" rel="bibo:Chapter"><h5 class="normal" 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="#ldpc-post-createbinlinkmetahdr" rel="bibo:Chapter"><h5 class="normal" 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="#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 a LDP 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 in the response by adding a HTTP <code>Link</code> header with 
+	a context URI identifying the newly created <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> (instead of the effective request URI),
+	a link relation value of <code>describedby</code>,
+	and a target URI identifying 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="#ldpc-post-acceptposthdr" rel="bibo:Chapter"><h5 class="normal" 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 <code>POST</code> request 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.  
+		While "POST to create" is a common interaction pattern, LDP clients are not guaranteed, even when 
+		making requests to a LDP server, that every successful <code>POST</code> request will result in the 
+		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="#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.
+	</h5></section><!-- Was 5.4.13 / #ldpc-5_4_13 -->
+	
+	<section id="ldpc-post-jsonld" typeof="bibo:Chapter" resource="#ldpc-post-jsonld" rel="bibo:Chapter"><h5 class="normal" role="heading" id="h5_ldpc-post-jsonld"><span class="secno">5.2.3.14 </span><a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> 
+		that allow creation of <a title="Linked Data Platform RDF Source" href="#dfn-linked-data-platform-rdf-source" class="internalDFN">LDP-RSs</a> via POST <em class="rfc2119" title="MUST">MUST</em> 
+		allow clients to create new members by enclosing a request entity body with a 
+	    <code>Content-Type</code> request header whose value is <code>application/ld+json</code> [<cite><a class="bibref" href="#bib-JSON-LD">JSON-LD</a></cite>].
+	</h5></section><!-- new -->
+	
+</section>
+
+<section id="ldpc-HTTP_PUT" typeof="bibo:Chapter" resource="#ldpc-HTTP_PUT" rel="bibo:Chapter">
+<h4 role="heading" id="h4_ldpc-HTTP_PUT"><span class="secno">5.2.4 </span>HTTP PUT</h4>
+	<p>
+		Per [<cite><a class="bibref" href="#bib-RFC7231">RFC7231</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 a 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="#ldpr-gen-pubclireqs">must be advertised</a> to clients.
+	</p>
+		
+	<section id="ldpc-put-mbrprops" typeof="bibo:Chapter" resource="#ldpc-put-mbrprops" rel="bibo:Chapter"><h5 class="normal" 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 a <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="#ldpc-put-create" rel="bibo:Chapter"><h5 class="normal" 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.  
+	</h5></section><!-- Was 5.5.4 / #ldpc-5_5_4 -->
+	
+</section>
+
+<section id="ldpc-HTTP_DELETE" typeof="bibo:Chapter" resource="#ldpc-HTTP_DELETE" rel="bibo:Chapter">
+<h4 role="heading" id="h4_ldpc-HTTP_DELETE"><span class="secno">5.2.5 </span>HTTP DELETE</h4>
+	<p>
+		Per [<cite><a class="bibref" href="#bib-RFC7231">RFC7231</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 a 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="#ldpc-del-contremovesconttriple" rel="bibo:Chapter"><h5 class="normal" role="heading" id="h5_ldpc-del-contremovesconttriple"><span class="secno">5.2.5.1 </span>
+		When a <a title="containment" href="#dfn-containment" class="internalDFN">contained <abbr title="Linked Data Platform Resource">LDPR</abbr></a> is deleted, the <abbr title="Linked Data Platform Container">LDPC</abbr> server <em class="rfc2119" title="MUST">MUST</em> also remove 
+		the corresponding containment triple, which has the effect of removing the deleted <abbr title="Linked Data Platform Resource">LDPR</abbr> from the containing <abbr title="Linked Data Platform Container">LDPC</abbr>.
+	</h5>
+	<blockquote>
+		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-RFC7231">RFC7231</a></cite>]. 
+		For example, the server could remove membership triples referring to the deleted <abbr title="Linked Data Platform Resource">LDPR</abbr>, 
+		perform additional cleanup tasks for resources it knows are no longer referenced or have not
+		been accessed for some period of time, and so on.
+	</blockquote>
+	</section><!-- Was 5.6.1 / #ldpc-5_6_1 -->
+	
+	<section id="ldpc-del-contremovescontres" typeof="bibo:Chapter" resource="#ldpc-del-contremovescontres" rel="bibo:Chapter"><h5 class="normal" role="heading" id="h5_ldpc-del-contremovescontres"><span class="secno">5.2.5.2 </span>
+	When a <a title="containment triples" href="#dfn-containment-triples" class="internalDFN">contained <abbr title="Linked Data Platform Resource">LDPR</abbr></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 delete 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>
+
+<section id="ldpc-HTTP_HEAD" typeof="bibo:Chapter" resource="#ldpc-HTTP_HEAD" rel="bibo:Chapter">
+<h4 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 recommends that
+		<code>HEAD</code> responses include the same headers as <code>GET</code> responses. 
+		<a title="LDP server" href="#dfn-ldp-server" class="internalDFN">LDP servers</a> must also include HTTP headers
+		on responses 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="#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="#ldpc-HTTP_PATCH" rel="bibo:Chapter">
+<h4 role="heading" id="h4_ldpc-HTTP_PATCH"><span class="secno">5.2.7 </span>HTTP PATCH</h4>
+	<p>
+		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 a 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="#ldpr-gen-pubclireqs">must be advertised</a> to clients.
+	</p>
+		
+	<section id="ldpc-patch-req" typeof="bibo:Chapter" resource="#ldpc-patch-req" rel="bibo:Chapter"><h5 class="normal" role="heading" id="h5_ldpc-patch-req"><span class="secno">5.2.7.1 </span>
+		<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 a <abbr title="Linked Data Platform Container">LDPC</abbr>'s <a title="Minimal-container triples" href="#dfn-minimal-container-triples" class="internalDFN">minimal-container triples</a>.
+	</h5></section><!-- Was 5.8.1 / #ldpc-5_8_1 -->
+</section>
+
+<section id="ldpc-HTTP_OPTIONS" typeof="bibo:Chapter" resource="#ldpc-HTTP_OPTIONS" rel="bibo:Chapter">
+<h4 role="heading" id="h4_ldpc-HTTP_OPTIONS"><span class="secno">5.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 Containers">LDPCs</abbr>.
+		Note that support for this method is required for <abbr title="Linked Data Platform Containers">LDPCs</abbr>, since <a href="#ldpr-HTTP_OPTIONS">it is required for <abbr title="Linked Data Platform Resources">LDPRs</abbr></a> and 
+		<a href="#ldpc-isldpr"><abbr title="Linked Data Platform Containers">LDPCs</abbr> adhere to <abbr title="Linked Data Platform RDF Source">LDP-RS</abbr> requirements</a>.
+		</p>
+
+	<section id="ldpc-options-linkmetahdr" typeof="bibo:Chapter" resource="#ldpc-options-linkmetahdr" rel="bibo:Chapter"><h5 class="normal" role="heading" id="h5_ldpc-options-linkmetahdr"><span class="secno">5.2.8.1 </span>
+	When responding to requests whose <code>request-URI</code> is a 
+	<a href="#ldpc-post-createbinlinkmetahdr"><abbr title="Linked Data Platform Non-RDF Source">LDP-NR</abbr> with an associated <abbr title="Linked Data Platform RDF Source">LDP-RS</abbr></a>, 
+	a <abbr title="Linked Data Platform Container">LDPC</abbr> server <em class="rfc2119" title="MUST">MUST</em> provide the same HTTP <code>Link</code>
+	response header as is <a href="#ldpc-post-createbinlinkmetahdr">required in the create response</a>.
+	</h5></section><!-- Was 5.9.2 / #ldpc-5_9_2 -->
+</section> <!-- h2 -->
+</section> <!-- ldpc-container -->
+
+<section id="ldpbc" typeof="bibo:Chapter" resource="#ldpbc" rel="bibo:Chapter">
+<h3 role="heading" id="h3_ldpbc"><span class="secno">5.3 </span>Basic</h3>
+
+<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="#ldpbc-general" rel="bibo:Chapter">
+<h4 role="heading" id="h4_ldpbc-general"><span class="secno">5.3.1 </span>General</h4>
+
+<section id="ldpbc-are-ldpcs" typeof="bibo:Chapter" resource="#ldpbc-are-ldpcs" rel="bibo:Chapter"><h5 class="normal" 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 with 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 the <a title="Linked Data Platform Basic Container" href="#dfn-linked-data-platform-basic-container" class="internalDFN">LDP Basic Container</a>, 
+	whose predicate is <code>rdf:type</code>, 
+	and whose object is <code>ldp:Container</code>, 
+	but there is no requirement to materialize this triple in the <abbr title="Linked Data Platform Basic Container">LDP-BC</abbr> representation.
+</h5></section>
+
+</section> <!-- ldpbc General -->
+
+</section> <!-- ldpbc Basic -->
+
+
+<section id="ldpdc" typeof="bibo:Chapter" resource="#ldpdc" rel="bibo:Chapter">
+<h3 role="heading" id="h3_ldpdc"><span class="secno">5.4 </span>Direct</h3>
+
+<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="#ldpdc-general" rel="bibo:Chapter">
+<h4 role="heading" id="h4_ldpdc-general"><span class="secno">5.4.1 </span>General</h4>
+
+<section id="ldpdc-are-ldpcs" typeof="bibo:Chapter" resource="#ldpdc-are-ldpcs" rel="bibo:Chapter"><h5 class="normal" 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 the <a title="Linked Data Platform Direct Container" href="#dfn-linked-data-platform-direct-container" class="internalDFN">LDP Direct Container</a>, 
+	whose predicate is <code>rdf:type</code>, 
+	and whose object is <code>ldp:Container</code>, 
+	but there is no requirement to materialize this triple in the <abbr title="Linked Data Platform Direct Container">LDP-DC</abbr> representation.
+</h5></section>
+
+<section id="ldpdc-mbrpred" typeof="bibo:Chapter" resource="#ldpdc-mbrpred" rel="bibo:Chapter"><h5 class="normal" role="heading" id="h5_ldpdc-mbrpred"><span class="secno">5.4.1.2 </span>
+	<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 a <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 a <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="#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="#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="#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="#ldpdc-containres" rel="bibo:Chapter"><h5 class="normal" 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>, 
+	and whose object is the <abbr title="Linked Data Platform Container">LDPC</abbr>'s <var>membership-constant-URI</var>.
+	Commonly the <abbr title="Linked Data Platform Container">LDPC</abbr>'s URI is the <var>membership-constant-URI</var>, but LDP does not require this.
+</h5>
+</section><!-- Was 5.2.4 / #ldpc-5_2_4 -->
+
+<section id="ldpdc-containtriples" typeof="bibo:Chapter" resource="#ldpdc-containtriples" rel="bibo:Chapter"><h5 class="normal" 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="#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="#ldpdc-containtriple-relation" rel="bibo:Chapter"><h6 class="normal" 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, 
+	whose predicate is <code>ldp:hasMemberRelation</code>, 
+	and whose object is the URI of <var>membership-predicate</var>.
+</h6>
+</section><!-- Was 5.2.5.1 / #ldpc-5_2_5_1 -->
+	
+<section id="ldpdc-containtriple-byrelation" typeof="bibo:Chapter" resource="#ldpdc-containtriple-byrelation" rel="bibo:Chapter"><h6 class="normal" 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, 
+	whose predicate is <code>ldp:isMemberOfRelation</code>, 
+	and whose object is the URI of <var>membership-predicate</var>.
+</h6></section><!-- Was 5.2.5.2 / #ldpc-5_2_5_2 -->
+</section>
+	
+<section id="ldpdc-indirectmbr-basic" typeof="bibo:Chapter" resource="#ldpdc-indirectmbr-basic" rel="bibo:Chapter"><h5 class="normal" role="heading" id="h5_ldpdc-indirectmbr-basic"><span class="secno">5.4.1.5 </span>
+	<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.
+	The value <code>ldp:MemberSubject</code> means that the 
+	<var>member-derived-URI</var> is the URI assigned by the server to a 
+	document it creates; for example, if the client POSTs content to a container
+	that causes the container to create a new <abbr title="Linked Data Platform Resource">LDPR</abbr>, <code>ldp:MemberSubject</code> says
+	that the <var>member-derived-URI</var> is the URI assigned to the newly created <abbr title="Linked Data Platform Resource">LDPR</abbr>.
+</h5></section>
+
+</section> <!-- ldpdc-general -->
+
+<section id="ldpdc-HTTP_POST" typeof="bibo:Chapter" resource="#ldpdc-HTTP_POST" rel="bibo:Chapter">
+<h4 role="heading" id="h4_ldpdc-HTTP_POST"><span class="secno">5.4.2 </span>HTTP POST</h4>
+	<section id="ldpdc-post-createdmbr-member" typeof="bibo:Chapter" resource="#ldpdc-post-createdmbr-member" rel="bibo:Chapter"><h5 class="normal" role="heading" id="h5_ldpdc-post-createdmbr-member"><span class="secno">5.4.2.1 </span>
+		When a successful HTTP <code>POST</code> request to a <abbr title="Linked Data Platform Container">LDPC</abbr> results in the creation of a <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="#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 -->
+
+<section id="ldpdc-HTTP_DELETE" typeof="bibo:Chapter" resource="#ldpdc-HTTP_DELETE" rel="bibo:Chapter">
+<h4 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="#ldpdc-del-contremovesmbrtriple" rel="bibo:Chapter"><h5 class="normal" role="heading" id="h5_ldpdc-del-contremovesmbrtriple"><span class="secno">5.4.3.1 </span>
+		When a <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>
+	</section><!-- Was 5.6.1 / #ldpc-5_6_1 -->
+
+</section> <!-- ldpdc-HTTP_DELETE -->
+
+</section> <!-- ldpdc Direct -->
+
+<section id="ldpic" typeof="bibo:Chapter" resource="#ldpic" rel="bibo:Chapter">
+<h3 role="heading" id="h3_ldpic"><span class="secno">5.5 </span>Indirect</h3>
+	
+<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="#ldpic-general" rel="bibo:Chapter">
+<h4 role="heading" id="h4_ldpic-general"><span class="secno">5.5.1 </span>General</h4>
+
+<section id="ldpic-are-ldpcs" typeof="bibo:Chapter" resource="#ldpic-are-ldpcs" rel="bibo:Chapter"><h5 class="normal" 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> as described in <a href="#ldpdc" class="sectionRef sec-ref">section <span class="secno">5.4</span> <span class="sec-title">Direct</span></a>, along with 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: one 
+	whose subject is <a title="Linked Data Platform Indirect Container" href="#dfn-linked-data-platform-indirect-container" class="internalDFN">LDP Indirect Container</a>, 
+	whose predicate is <code>rdf:type</code>, 
+	and whose object is <code>ldp:Container</code>, 
+	but there is no requirement to materialize this triple in the <abbr title="Linked Data Platform Indirect Container">LDP-IC</abbr> representation.
+</h5></section>
+
+<section id="ldpic-indirectmbr" typeof="bibo:Chapter" resource="#ldpic-indirectmbr" rel="bibo:Chapter"><h5 class="normal" role="heading" id="h5_ldpic-indirectmbr"><span class="secno">5.5.1.2 </span>
+	<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="#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
+	<var>O</var>.  LDP does not define the behavior when more than one triple containing 
+	the predicate <var>P</var> is present in the client's input.
+	For example, if the client POSTs <abbr title="Resource Description Framework">RDF</abbr> content to a container
+	that causes the container to create a new <abbr title="Linked Data Platform RDF Source">LDP-RS</abbr>, and that content contains the triple 
+	<var>( &lt;&gt; , foaf:primaryTopic , bob#me )</var>
+	<code>foaf:primaryTopic</code> says
+	that the <var>member-derived-URI</var> is <var>bob#me</var>.  
+	One consequence of this definition is that indirect container member creation is only 
+	well-defined by LDP when the document supplied by the client as input to the create request
+	has an <abbr title="Resource Description Framework">RDF</abbr> media type.
+	</h5>
+</section><!-- Was 5.2.10 / #ldpc-5_2_10 -->
+</section> <!-- ldpic General -->
+
+<section id="ldpic-HTTP_POST" typeof="bibo:Chapter" resource="#ldpic-HTTP_POST" rel="bibo:Chapter">
+<h4 role="heading" id="h4_ldpic-HTTP_POST"><span class="secno">5.5.2 </span>HTTP POST</h4>
+	<section id="ldpic-post-indirectmbrrel" typeof="bibo:Chapter" resource="#ldpic-post-indirectmbrrel" rel="bibo:Chapter"><h5 class="normal" role="heading" id="h5_ldpic-post-indirectmbrrel"><span class="secno">5.5.2.1 </span><abbr title="Linked Data Platform Containers">LDPCs</abbr> 
+		whose <code>ldp:insertedContentRelation</code> triple has an object
+		<strong>other than</strong> <code>ldp:MemberSubject</code> 
+		and that create new resources 
+		<em class="rfc2119" title="MUST">MUST</em> add a triple to the container
+		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="#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 -->
+</section> <!-- ldpic HTTP_POST -->
+
+</section> <!-- ldpic Indirect -->
+
+</section> <!-- h1 LDPC -->
+
+
+<section id="base-specs" class="informative" typeof="bibo:Chapter" resource="#base-specs" rel="bibo:Chapter">
+<!--OddPage--><h2 role="heading" id="h2_base-specs"><span class="secno">6. </span>Notable information from normative references</h2><p><em>This section is non-normative.</em></p>
+<p>
+While readers, and especially implementers, of LDP are assumed to understand the information in its normative 
+references, the working group has found that certain points are particularly important to understand.
+For those thoroughly familiar with the referenced specifications, these points might seem obvious, yet
+experience has shown that few non-experts find all of them obvious.  This section enumerates these topics; 
+it is simply re-stating (non-normatively) information locatable via the normative references.
+</p>
+
+<section id="specs-webarch" class="informative" typeof="bibo:Chapter" resource="#specs-webarch" rel="bibo:Chapter">
+<h3 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="#bib-WEBARCH">WEBARCH</a></cite>]
+
+	<section id="ldp-webarch-nonexcl-membership" typeof="bibo:Chapter" resource="#ldp-webarch-nonexcl-membership" rel="bibo:Chapter"><h4 class="normal" 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="#ldp-webarch-uri-reuse" rel="bibo:Chapter"><h4 class="normal" 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 a <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.
+		While it is difficult to provide absolute implementation guarantees of non-reuse in all failure
+		scenarios, re-using URIs creates ambiguities for clients that are best avoided.
+	</h4></section>
+
+</section> 
+
+<section id="specs-http" class="informative" typeof="bibo:Chapter" resource="#specs-http" rel="bibo:Chapter">
+<h3 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="#bib-RFC7230">RFC7230</a></cite>], [<cite><a class="bibref" href="#bib-RFC7231">RFC7231</a></cite>], [<cite><a class="bibref" href="#bib-RFC7232">RFC7232</a></cite>]
+
+	<section id="ldp-http-other-representations" typeof="bibo:Chapter" resource="#ldp-http-other-representations" rel="bibo:Chapter"><h4 class="normal" 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="#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-RFC7231">RFC7231</a></cite>] Section 3.4 - Content Negotiation) is used to select the format.
+	</h4></section>
+	
+	<section id="ldp-http-other-methods" typeof="bibo:Chapter" resource="#ldp-http-other-methods" rel="bibo:Chapter"><h4 class="normal" 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="#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="#ldp-http-delete-uri-reuse" rel="bibo:Chapter"><h4 class="normal" 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="#ldp-http-method-side-effects" rel="bibo:Chapter"><h4 class="normal" 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-RFC7231">RFC7231</a></cite>] section 4.2.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="#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="#ldp-http-patch-allowed" rel="bibo:Chapter"><h4 class="normal" 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="#bib-RFC5789">RFC5789</a></cite>].
+	</h4></section>
+	
+	<section id="ldp-http-content-sniffing" typeof="bibo:Chapter" resource="#ldp-http-content-sniffing" rel="bibo:Chapter"><h4 class="normal" 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="#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-RFC7231">RFC7231</a></cite>] section 3.1.1.5).
+	</h4></section>
+
+</section> 
+
+<section id="specs-rdf" class="informative" typeof="bibo:Chapter" resource="#specs-rdf" rel="bibo:Chapter">
+<h3 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="#bib-rdf11-concepts">rdf11-concepts</a></cite>]
+
+	<section id="ldp-rdfconcepts-extra-triples-any" typeof="bibo:Chapter" resource="#ldp-rdfconcepts-extra-triples-any" rel="bibo:Chapter"><h4 class="normal" role="heading" id="h4_ldp-rdfconcepts-extra-triples-any"><span class="secno">6.3.1 </span>The state of a <abbr title="Linked Data Platform Resource">LDPR</abbr> 
+		can have triples with any subject(s).  The URL used to retrieve the
+		representation of a <abbr title="Linked Data Platform Resource">LDPR</abbr> need not be the subject of any of its triples.
+	</h4></section>
+	
+	<section id="ldp-rdfconcepts-extra-triples-members" typeof="bibo:Chapter" resource="#ldp-rdfconcepts-extra-triples-members" rel="bibo:Chapter"><h4 class="normal" role="heading" id="h4_ldp-rdfconcepts-extra-triples-members"><span class="secno">6.3.2 </span>The representation of a <abbr title="Linked Data Platform Container">LDPC</abbr>
+		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="#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>
+	
+	<section id="ldp-rdfconcepts-extra-triples-types" typeof="bibo:Chapter" resource="#ldp-rdfconcepts-extra-triples-types" rel="bibo:Chapter"><h4 class="normal" role="heading" id="h4_ldp-rdfconcepts-extra-triples-types"><span class="secno">6.3.3 </span>The state of a <abbr title="Linked Data Platform Resource">LDPR</abbr> can have more than one
+		triple with an <code>rdf:type</code> predicate.
+	</h4></section>
+
+</section> 
+
+</section> <!-- Base specs -->
+
+<section id="http-header-definitions">
+<!--OddPage--><h2 role="heading" id="h2_http-header-definitions"><span class="secno">7. </span>HTTP Header Definitions</h2>
+     
+<section id="header-accept-post" typeof="bibo:Chapter" resource="#header-accept-post" rel="bibo:Chapter">
+<h3 role="heading" id="h3_header-accept-post"><span class="secno">7.1 </span>The Accept-Post Response Header</h3>
+
+	<div class="note"><div class="note-title" aria-level="2" role="heading" id="h_note_1"><span>Note</span></div><div class="">
+		<p>The LDP Working Group proposes incorporation of the features described in this section.</p>
+		<p>The <code>Accept-Post</code> header has applicability beyond LDP as outlined in this
+		<a href="https://datatracker.ietf.org/doc/draft-wilde-accept-post/">IETF draft</a> [<cite><a class="bibref" href="#bib-Accept-Post">Accept-Post</a></cite>].
+		</p>
+	</div></div>
+		
+	<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="#bib-RFC5789">RFC5789</a></cite>].
+	</p>
+   
+	<section id="header-accept-post-1" typeof="bibo:Chapter" resource="#header-accept-post-1" rel="bibo:Chapter"><h4 class="normal" 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 1.2 of [<cite><a class="bibref" href="#bib-RFC7231">RFC7231</a></cite>], is:</h4>
+		<blockquote><code>Accept-Post = "Accept-Post" ":" # media-range </code>
+		<p>
+		The <code>Accept-Post</code> header specifies a comma-separated list of media 
+		ranges (with optional parameters) as defined by [<cite><a class="bibref" href="#bib-RFC7231">RFC7231</a></cite>], Section 5.3.2.  
+		The <code>Accept-Post</code> header, in effect, uses the same syntax as the 
+		HTTP <code>Accept</code> header minus the optional <code>accept-params</code> BNF production,
+		since the latter does not apply to <code>Accept-Post</code>.
+		</p>
+		</blockquote>
+	</section><!-- Was 6.1.1 / #header-accept-post-1 -->
+
+	<section id="header-accept-post-2" typeof="bibo:Chapter" resource="#header-accept-post-2" rel="bibo:Chapter"><h4 class="normal" role="heading" id="h4_header-accept-post-2"><span class="secno">7.1.2 </span>
+		The <code>Accept-Post</code> HTTP header <em class="rfc2119" title="SHOULD">SHOULD</em> appear in the <code>OPTIONS</code> response for any resource
+		that supports the use of the <code>POST</code> method.  The presence of the
+		<code>Accept-Post</code> header in response to any method is an implicit
+		indication that <code>POST</code> is allowed on the resource identified by the
+		<code>Request-URI</code>.  The presence of a specific document format in
+		this header indicates that that specific format is allowed on <code>POST</code> requests to the
+		resource identified by the <code>Request-URI</code>.
+	</h4></section><!-- Was 6.1.2 / #header-accept-post-2 -->
+	
+	<section id="header-accept-post-iana" typeof="bibo:Chapter" resource="#header-accept-post-iana" rel="bibo:Chapter"><h4 class="normal" role="heading" id="h4_header-accept-post-iana"><span class="secno">7.1.3 </span>IANA Registration Template</h4>
+	<div>
+	<blockquote>
+	<p>
+	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
+	</p>
+	<p>
+	Applicable Protocol:  HTTP
+	</p>
+	<p>
+	Author/Change controller:  <abbr title="World Wide Web Consortium">W3C</abbr>
+	</p>
+	<p>
+	Specification document:  this specification
+	</p>
+	</blockquote>
+	</div>
+	</section><!-- Was 6.1.3 / #header-accept-post-iana -->
+
+</section>
+     
+<section id="prefer-parameters" typeof="bibo:Chapter" resource="#prefer-parameters" rel="bibo:Chapter">
+<h3 role="heading" id="h3_prefer-parameters"><span class="secno">7.2 </span>Preferences on the Prefer Request Header</h3>
+
+<section id="prefer-summary" typeof="bibo:Chapter" resource="#prefer-summary" rel="bibo:Chapter">
+<h4 role="heading" id="h4_prefer-summary"><span class="secno">7.2.1 </span>Summary</h4>
+	
+	<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="#bib-RFC7240">RFC7240</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 
+	processed.  LDP Containers with large numbers of associated documents 
+	and/or members will have large representations, and many client 
+	applications may be interested in processing only a subset of the <abbr title="Linked Data Platform Container">LDPC</abbr>'s 
+	information (for example, only membership triples or only containment triples), 
+	resulting in a potentially large savings in server, client, 
+	and network processing.  
+	</p>
+	
+	<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="#bib-RFC7240">RFC7240</a></cite>].
+	</p>
+
+	<p>
+	Non-normative note: [<cite><a class="bibref" href="#bib-RFC7240">RFC7240</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="#prefer-examples">Examples</a> illustrate some cases where the header is unnecessary.
+	</p>
+
+</section> <!-- Prefer summary -->
+
+<section id="prefer-rules" typeof="bibo:Chapter" resource="#prefer-rules" rel="bibo:Chapter">
+<h4 role="heading" id="h4_prefer-rules"><span class="secno">7.2.2 </span>Specification</h4>
+
+	<section id="prefer-include" typeof="bibo:Chapter" resource="#prefer-include" rel="bibo:Chapter"><h5 class="normal" role="heading" id="h5_prefer-include"><span class="secno">7.2.2.1 </span>
+		The <code>include</code> hint defines a subset of a <abbr title="Linked Data Platform Resource">LDPR</abbr>'s content that a client
+		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="#bib-RFC7240">RFC7240</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="#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="#bib-RFC7240">RFC7240</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="#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>
+
+	<section id="prefer-omit" typeof="bibo:Chapter" resource="#prefer-omit" rel="bibo:Chapter"><h5 class="normal" role="heading" id="h5_prefer-omit"><span class="secno">7.2.2.2 </span>
+		The <code>omit</code> hint defines a subset of a <abbr title="Linked Data Platform Resource">LDPR</abbr>'s content that a client
+		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="#bib-RFC7240">RFC7240</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="#prefer-include">include</a>.
+		</p>
+		</blockquote>
+	</section>
+
+	<section id="prefer-conflicts" typeof="bibo:Chapter" resource="#prefer-conflicts" rel="bibo:Chapter"><h5 class="normal" role="heading" id="h5_prefer-conflicts"><span class="secno">7.2.2.3 </span>
+		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="#bib-RFC7240">RFC7240</a></cite>] suggests treating similar requests as though none of the conflicting
+		preferences were specified.
+		</h5>
+	</section>
+
+	<section id="prefer-uris" typeof="bibo:Chapter" resource="#prefer-uris" rel="bibo:Chapter"><h5 class="normal" 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.</h5>
+		<table class="indented">
+		<tbody><tr>
+		<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="#dfn-membership-triples" class="internalDFN">Membership triples </a></td>
+		<td> <code>http://www.w3.org/ns/ldp#PreferMembership</code> </td>
+		</tr>
+		<tr>
+		<td rowspan="3"> <a title="Minimal-container triples" href="#dfn-minimal-container-triples" class="internalDFN">Minimal-container triples</a>
+		</td>
+		<td> <code>http://www.w3.org/ns/ldp#PreferMinimalContainer</code> </td>
+		</tr>
+		<tr>
+		<td>&nbsp;&nbsp;&nbsp;&nbsp; or the equivalent but deprecated term </td>
+		</tr>
+		<tr>
+		<td> 
+		<code>http://www.w3.org/ns/ldp#PreferEmptyContainer</code> </td>
+		</tr>
+		</tbody></table>
+		<blockquote>
+		<p>
+		Non-normative note: all currently defined URIs are only coherent for LDP-RSs, 
+		and in fact only for <abbr title="Linked Data Platform Containers">LDPCs</abbr>, however in
+		the future it is possible that additional URIs with other scopes of applicability
+		could be defined.
+		</p>
+		</blockquote>
+	</section>
+
+</section> <!-- Prefer specification -->
+<section id="prefer-examples" class="informative" typeof="bibo:Chapter" resource="#prefer-examples" rel="bibo:Chapter">
+<h4 role="heading" id="h4_prefer-examples"><span class="secno">7.2.3 </span>Examples</h4><p><em>This section is non-normative.</em></p>
+	<p>
+	If we assume a container like
+	the one below:
+	</p>
+<div class="example"><div class="example-title"><span>Example 19</span></div><pre class="example" id="prefer-examples-direct"># The following is the representation of
+#   http://example.org/netWorth/nw1/assets/
+<!-- @base is here only so it's easier to paste into validators for checking -->
+# @base &lt;http://example.org/netWorth/nw1/assets/&gt;.
[email protected] dcterms: &lt;http://purl.org/dc/terms/&gt;.
[email protected] ldp: &lt;http://www.w3.org/ns/ldp#&gt;.
[email protected] o: &lt;http://example.org/ontology#&gt;.
+
+&lt;&gt;
+   a ldp:DirectContainer;
+   dcterms:title "The assets of JohnZSmith";
+   ldp:membershipResource &lt;http://example.org/netWorth/nw1/&gt;;
+   ldp:hasMemberRelation o:asset;
+   ldp:insertedContentRelation ldp:MemberSubject.
+
+&lt;http://example.org/netWorth/nw1/&gt;
+   a o:NetWorth;
+   o:asset &lt;a1&gt;, &lt;a3&gt;, &lt;a2&gt;.
+
+&lt;a1&gt;
+   a o:Stock;
+   o:marketValue 100.00 .
+&lt;a2&gt;
+   a o:Cash;
+   o:marketValue 50.00 .
+&lt;a3&gt;
+   a o:RealEstateHolding;
+   o:marketValue 300000 .</pre></div>
+
+	<p id="prefer-examples-direct-minimal-container-only1">
+	Clients interested only in information about the container 
+	(for example, which membership predicate it uses) might use this hint on a <code>GET</code> request:
+	<code>Prefer: return=representation; include="http://www.w3.org/ns/ldp#PreferMinimalContainer"</code>
+	</p>
+	<p>
+	A server that honors this hint would return a following response containing the HTTP header 
+	<code>Preference-Applied: return=representation</code> 
+	and this representation:
+	</p>
+	
+<em>Request</em> to <code>http://example.org/netWorth/nw1/assets/</code>:
+<div class="example"><div class="example-title"><span>Example 20</span></div><pre class="example">GET /netWorth/nw1/assets/ HTTP/1.1
+Host: example.org
+Accept: text/turtle
+Prefer: return=representation; include="http://www.w3.org/ns/ldp#PreferMinimalContainer"</pre></div>
+<em>Response:</em>
+<div class="example"><div class="example-title"><span>Example 21</span></div><pre class="example">HTTP/1.1 200 OK
+Content-Type: text/turtle
+ETag: "_87e52ce291112"
+Link: &lt;http://www.w3.org/ns/ldp#DirectContainer&gt;; rel="type",
+      &lt;http://www.w3.org/ns/ldp#Resource&gt;; rel="type"
+Accept-Post: text/turtle, application/ld+json
+Allow: POST,GET,OPTIONS,HEAD
+Preference-Applied: return=representation
+Transfer-Encoding: chunked
+<!-- @base &lt;http://example.org/netWorth/nw1/assets/&gt;. -->
[email protected] dcterms: &lt;http://purl.org/dc/terms/&gt;.
[email protected] ldp: &lt;http://www.w3.org/ns/ldp#&gt;.
[email protected] o: &lt;http://example.org/ontology#&gt;.
+
+&lt;http://example.org/netWorth/nw1/assets/&gt;
+   a ldp:DirectContainer;
+   dcterms:title "The assets of JohnZSmith";
+   ldp:membershipResource &lt;http://example.org/netWorth/nw1/&gt;;
+   ldp:hasMemberRelation o:asset;
+   ldp:insertedContentRelation ldp:MemberSubject.</pre></div>
+
+	<p id="prefer-examples-direct-minimal-container-only2">
+	Clients interested only in information about the container 
+	(same as before) might use this hint instead:
+	<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="Minimal-container triples" href="#dfn-minimal-container-triples" class="internalDFN">minimal-container triples</a>.
+	Clients should preferentially use the <code>include</code> parameter, as it more precisely communicates their needs.
+	</p>
+	<p>
+	A <strong>LDP 1.0</strong> server that honors this hint would return the following response.  Servers
+	implementing later versions of LDP might return substantively different responses.
+	</p>
+	
+<em>Request</em> to <code>http://example.org/netWorth/nw1/assets/</code>:
+<div class="example"><div class="example-title"><span>Example 22</span></div><pre class="example">GET /netWorth/nw1/assets/ HTTP/1.1
+Host: example.org
+Accept: text/turtle
+Prefer: return=representation; omit="http://www.w3.org/ns/ldp#PreferMembership http://www.w3.org/ns/ldp#PreferContainment"</pre></div>
+<em>Response:</em>
+<div class="example"><div class="example-title"><span>Example 23</span></div><pre class="example">HTTP/1.1 200 OK
+Content-Type: text/turtle
+ETag: "_87e52ce291112"
+Link: &lt;http://www.w3.org/ns/ldp#DirectContainer&gt;; rel="type",
+      &lt;http://www.w3.org/ns/ldp#Resource&gt;; rel="type"
+Accept-Post: text/turtle, application/ld+json
+Allow: POST,GET,OPTIONS,HEAD
+Preference-Applied: return=representation 
+Transfer-Encoding: chunked
+<!-- @base &lt;http://example.org/netWorth/nw1/assets/&gt;. -->
[email protected] dcterms: &lt;http://purl.org/dc/terms/&gt;.
[email protected] ldp: &lt;http://www.w3.org/ns/ldp#&gt;.
[email protected] o: &lt;http://example.org/ontology#&gt;.
+
+&lt;http://example.org/netWorth/nw1/assets/&gt;
+   a ldp:DirectContainer;
+   dcterms:title "The assets of JohnZSmith";
+   ldp:membershipResource &lt;http://example.org/netWorth/nw1/&gt;;
+   ldp:hasMemberRelation o:asset;
+   ldp:insertedContentRelation ldp:MemberSubject.</pre></div>
+
+	<p id="prefer-examples-direct-membershiponly">
+	Clients interested only in information about the container 
+	(for example, which membership predicate it uses) and its membership might use this hint on a <code>GET</code> request:
+	<code>Prefer: return=representation; include="http://www.w3.org/ns/ldp#PreferMembership http://www.w3.org/ns/ldp#PreferMinimalContainer"</code>.
+	</p>
+	<p>
+	A server that honors this hint would return 
+	(at least) the following response, and perhaps only this (it might
+	well omit containment triples if they are not specifically requested).  
+	In cases like this example, where a client can detect from the content that its hints were honored
+	(the presence of the predicates <code>dcterms:title</code> and <code>o:asset</code> demonstrate this in the representation below), 
+	there is no need for the server to include a <code>Preference-Applied</code> response header 
+	in many common cases like a <code>200 (OK)</code> response.  In other cases, like status code <code>303</code>,
+	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="#bib-RFC7231">RFC7231</a></cite>]).
+	</p>
+	
+<em>Request</em> to <code>http://example.org/netWorth/nw1/assets/</code>:
+<div class="example"><div class="example-title"><span>Example 24</span></div><pre class="example">GET /netWorth/nw1/assets/ HTTP/1.1
+Host: example.org
+Accept: text/turtle
+Prefer: return=representation; include="http://www.w3.org/ns/ldp#PreferMembership http://www.w3.org/ns/ldp#PreferMinimalContainer"</pre></div>
+<em>Response:</em>
+<div class="example"><div class="example-title"><span>Example 25</span></div><pre class="example">HTTP/1.1 200 OK
+Content-Type: text/turtle
+ETag: "_87e52ce291112"
+Link: &lt;http://www.w3.org/ns/ldp#DirectContainer&gt;; rel="type",
+      &lt;http://www.w3.org/ns/ldp#Resource&gt;; rel="type"
+Accept-Post: text/turtle, application/ld+json
+Allow: POST,GET,OPTIONS,HEAD
+Preference-Applied: return=representation
+Transfer-Encoding: chunked
+<!-- @base &lt;http://example.org/netWorth/nw1/assets/&gt;. -->
[email protected] dcterms: &lt;http://purl.org/dc/terms/&gt;.
[email protected] ldp: &lt;http://www.w3.org/ns/ldp#&gt;.
[email protected] o: &lt;http://example.org/ontology#&gt;.
+
+&lt;http://example.org/netWorth/nw1/assets/&gt;
+   a ldp:DirectContainer;
+   dcterms:title "The assets of JohnZSmith";
+   ldp:membershipResource &lt;http://example.org/netWorth/nw1/&gt;;
+   ldp:hasMemberRelation o:asset;
+   ldp:insertedContentRelation ldp:MemberSubject.
+
+&lt;http://example.org/netWorth/nw1/&gt;
+   a o:NetWorth;
+   o:asset &lt;a1&gt;, &lt;a3&gt;, &lt;a2&gt;.</pre></div>
+
+	</section> <!-- Prefer examples -->
+
+</section> <!-- Prefer defns -->
+</section> <!-- Header defns -->
+
+<section id="link-relations" typeof="bibo:Chapter" resource="#link-relations" rel="bibo:Chapter">
+<!--OddPage--><h2 role="heading" id="h2_link-relations"><span class="secno">8. </span>Link Relations</h2>
+<p>
+	The intent is that these link relations will be registered with IANA per [<cite><a class="bibref" href="#bib-RFC5988">RFC5988</a></cite>] section 6.2.1.
+</p>
+<section id="link-relation-describedby" typeof="bibo:Chapter" resource="#link-relation-describedby" rel="bibo:Chapter">
+<h3 role="heading" id="h3_link-relation-describedby"><span class="secno">8.1 </span>describedby</h3>
+<p>
+	The contents of this section were originally taken from [<cite><a class="bibref" href="#bib-POWDER">POWDER</a></cite>] appendix D, and then modified to comply with the current registration template.
+	The pre-LDP IANA link relation registry entry for 
+	<code>describedby</code> refers to a different section of [<cite><a class="bibref" href="#bib-POWDER">POWDER</a></cite>] that was substantively updated in 
+	<a href="http://www.w3.org/2007/powder/powder-errata#describedby">an erratum</a>, and that section was not
+	actually the normative definition of the link relation.  Since we expect no update to [<cite><a class="bibref" href="#bib-POWDER">POWDER</a></cite>] that incorporates the erratum 
+	or fixes the registry link, this superseding registration approach is being taken.
+</p>
+<p>The following Link Relationship will be submitted to IANA for review, approval, and inclusion in the IANA Link Relations registry.</p>
+<dl>
+<dt>Relation Name:</dt>
+<dd><code>describedby</code></dd>
+<dt>Description:</dt>
+<dd>
+The relationship <code>A describedby B</code> asserts that resource B provides a description of resource A. There are no constraints on the format or representation of either A or B, neither are there any further constraints on either resource. 
+</dd>
+<dt>Reference:</dt>
+<dd>
+	The <abbr title="World Wide Web Consortium">W3C</abbr> <a href="http://www.w3.org/TR/ldp/">Linked Data Platform specification</a>.
+</dd>
+<dt>Notes:</dt>
+<dd>
+    Descriptions of resources may be socially sensitive, may require processing to be understood and may or may not not be accurate. Consumers of descriptive resources should be aware of the source and chain of custody of the data. Security considerations for URIs (Section 7 of RFC 3986) and IRIs (Section 8 of RFC 3987) apply to the extent that describing resources may affect consumers' decisions about how or whether to retrieve those resources.
+</dd>
+</dl>
+</section>
+</section>
+
+<section class="informative" id="security" typeof="bibo:Chapter" resource="#security" rel="bibo:Chapter">
+<!--OddPage--><h2 role="heading" id="h2_security"><span class="secno">9. </span>Security Considerations</h2><p><em>This section is non-normative.</em></p>
+<p>As with any protocol that is implemented leveraging HTTP, implementations should take advantage of the many 
+security-related facilities associated with it and are not required to carry out LDP operations 
+that may be in contradistinction to a particular security policy in place. For example, when faced with an 
+unauthenticated request to replace system critical <abbr title="Resource Description Framework">RDF</abbr> statements in a graph through the PUT method, applications may
+consider responding with the 401 status code (Unauthorized), indicating that the appropriate authorization 
+is required. In cases where authentication is provided fails to meet the requirements of a particular access control 
+policy, the 403 status code (Forbidden) can be sent back to the client to indicate this failure to meet the
+access control policy.</p>
+</section>
+
+<section class="appendix informative" id="acknowledgements">
+<!--OddPage--><h2 role="heading" id="h2_acknowledgements"><span class="secno">A. </span>Acknowledgements</h2><p><em>This section is non-normative.</em></p>
+     
+  <p>The following people have been instrumental in providing thoughts, feedback,
+reviews, content, criticism and input in the creation of this specification:</p>
+
+  <p style="margin-left: 3em;">
+  Alexandre Bertails, Andrei Sambra, Andy Seaborne, Antonis Loizou,  Arnaud Le Hors, Ashok Malhotra, 
+  Bart van Leeuwen, Cody Burleson, David Wood, Eric Prud'hommeaux, Erik Wilde, Henry Story, John Arwe, 
+  Kevin Page, Kingsley Idehen, Mark Baker, Martin P. Nally, Miel Vander Sande, Miguel Esteban Gutiérrez, 
+  Nandana Mihindukulasooriya, Olivier Berger, Pierre-Antoine Champin, Raúl García Castro, Reza B'Far, 
+  Richard Cyganiak, Rob Sanderson, Roger Menday, Ruben Verborgh, Sandro Hawke, Serena Villata, Sergio Fernandez, 
+  Steve Battle, Steve Speicher, Ted Thibodeau, Tim Berners-Lee, Yves Lafon
+  </p>
+
+</section>
+
+<section class="appendix informative" id="history" typeof="bibo:Chapter" resource="#history" rel="bibo:Chapter">
+<!--OddPage--><h2 role="heading" id="h2_history"><span class="secno">B. </span>Change History</h2><p><em>This section is non-normative.</em></p>
+<p>The change history is up to the editors to insert a brief summary of
+changes, ordered by most recent changes first and with heading from which
+public draft it has been changed from.
+</p>
+
+
+<h2 id="summary">Summary</h2>
+<p>Summary of notable changes from the <a href="http://www.w3.org/TR/2014/WD-ldp-20140916/">previous public working draft</a>.</p>
+<ul>
+	<li>No longer AT RISK: Indirect Containers, JSON-LD and Accept-Post</li>
+	<li>AT RISK that was removed: client should requirement to handle server-initiated paging</li>
+	<li>Improvements to sections about LDP-server-managed triples and client requested interaction models</li>
+</ul> 
+
+
+<!-- 
+<h2>Summary</h2>
+<p>Summary of notable changes from the <a href="http://www.w3.org/TR/2014/CR-ldp-20140619/">previous public working draft</a>.</p>
+<ul>
+	<li>Indirect containers are AT RISK for removal</li>
+	<li>Turtle is no longer required for an LDP-RS when the Accept header is absent</li>
+	<li>JSON-LD is required for an LDP-RS and LDPC create via POST, AT RISK</li>
+	<li>Changed the link relation used to articulate request constraints that a client has likely violated</li>
+</ul> 
+ -->
+
+<!-- 
+<h2>Detailed history</h2> -->
+<!-- <blockquote><em><a href="http://www.w3.org/TR/2014/CR-ldp-20140619/">Candidate Recommendation Draft</a></em></blockquote> -->
+<!-- 
+<ul>
+	<li>2014-10-20 - Prepare PR draft (SS)</li>
+	<li>2014-10-20 - Removed at-risk label for Accept-Post, leaving a note about references and dependency (SS)</li>
+	<li>2014-10-20 - Removed at-risk label for Indirect Containers (SS)</li>
+	<li>2014-10-20 - Removed at-risk label for json-ld requirement (SS)</li>
+	<li>2014-10-20 - Removed at-risk feature that clients should be prepared to handle server-initiated paging (SS)</li>
+	<li>2014-10-20 - Define LDP-server-managed for Robert Sanderson thread (JA)</li>
+	<li>2014-10-20 - Update LDPC-Post adding non-normative note for Miguel thread (JA)</li>
+	<li>2014-10-20 - Update LDPC-Post bullet 1 with non-normative text for James Leigh thread (JA)</li>
+	<li>2014-09-25 - Included non-norm content to container intro to add clarity on application-specific extensions (SS)</li>
+</ul>
+<blockquote><em><a href="http://www.w3.org/TR/2014/WD-ldp-20140916">Last Call Working Draft 3</a></em></blockquote>
+<ul>
+	<li>2014-09-12 - Fix example 14 relative URIs per Rob Sanderson's email ... add advisors/ to contained documents (JA) </li>
+	<li>2014-09-10 - Fix examples per Rob Sanderson's email ... /nw1 &gt; /nw1/ (JA) </li>
+	<li>2014-09-10 - Wafer thin change to Turtle-required words, lest the chair fetchez la vache (JA) </li>
+	<li>2014-09-09 - Re-factor Turtle/JSON-LD required words for readability and completeness (JA) </li>
+	<li>2014-09-08 - Add link to Best Practices now that it has been published (JA) </li>
+	<li>2014-09-08 - Indirect containers (at risk) (JA) </li>
+	<li>2014-09-08 - Should return Turtle if Accept is absent, JSON-LD required (at risk), clarify creates  (JA) </li>
+	<li>2014-09-08 - Changed the constraints link relation to ldp#constrainedBy, per today's mtg resolution  (JA) </li>
+	<li>2014-09-08 - Clarify that Turtle/JSON-LD on LDPC POST are required only when the semantic is "create new member" (JA) </li>
+	<li>2014-09-08 - Constraints 4xx responses remind them to choose context URI consciously (JA) </li>
+	<li>2014-09-08 - LDP-NR creation clarify context URI needed is not the default, per today's mtg resolution (JA) </li>
+	<li>2014-08-04 - Fuss with o:value in examples for Sandro to remain consistent with Paging spec (JA) </li>
+	<li>2014-07-20 - Added test coverage utility to annotate spec with test cases covering them, to be removed before publishing (SS)</li>
+</ul>
+
+<blockquote><em><a href="http://www.w3.org/TR/2014/CR-ldp-20140619">Candidate Recommendation Draft</a></em></blockquote>
+<ul>
+	<li>2014-07-28 - Clarified syntax used by clients to request specific interaction model (JA) </li>
+	<li>2014-06-16 - Updated examples in Prefer section to be in request/response format (SS) </li>
+	<li>2014-06-16 - Updated examples in container sections to be in request/response format (SS) </li>
+	<li>2014-06-10 - Use http-bis and Prefer RFC numbers, adjust BNF to match bis changes (JA) </li>
+	<li>2014-06-05 - Fixed LC1 date in change history pseudo-heading, was 2014 (JA) </li>
+	<li>2014-05-19 - Revert membership definition to be about LDPCs, not LDP-RS's (JA) </li>
+	<li>2014-05-09 - Respond to Joe Ross's LC2 comments (JA) </li>
+	<li>2014-04-28 - Added usage for ldp:NonLDPSource (SS) </li>
+	<li>2014-04-28 - Clarify MUST etags on responses with representations and HEAD (SS) </li>
+	<li>2014-04-17 - Add should for json-ld per today's WG resolution (JA) </li>
+	<li>2014-04-16 - Update narrative on net worth example (#s 2-5, section 5.1, at time of writing) (JA) </li>
+	<li>2014-04-16 - Clarify language of 5.2.5.1/2 (JA) </li>
+	<li>2014-04-16 - Clarify definitions of membership and containment triples (JA) </li>
+	<li>2014-04-15 - Rename empty-container triples to minimal-container triples (JA) </li>
+	<li>2014-04-15 - Add describedby chapter (JA) </li>
+	<li>2014-04-15 - Removal of named graph references (JA) </li>
+	<li>2014-04-15 - Fixed typos (JA) </li>
+	<li>2014-04-15 - Fixed LC-2840 clarity on "burden of constraint" (SS) </li>
+	<li>2014-03-30 - Updated references to RFC5988 to first time Link header is used (SS) </li>
+	<li>2014-03-29 - Fixed error in Example 8 (SS) </li>
+	<li>2014-03-28 - Fixed copy-paste error in 5.4.1.1 (SS) </li>
+	<li>2014-03-28 - Set publication status and history for post 2nd LC edits (SS) </li>
+</ul>
+
+<blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-20140311/">Last Call Draft (2014-03-11)</a></em></blockquote>
+<ul>
+	<li>2014-03-03 - Must use LDPC subtypes for rel='type', per 20140303 resln (SS) </li>
+	<li>2014-03-03 - Removed LDP-BC clauses that introduce membership (SS) </li>
+	<li>2014-03-03 - Tweaked LDPR PUT clauses to better match new defn of LDPR (SS) </li>
+	<li>2014-03-03 - Folded #ldpclients section into #ldprs (SS) </li>
+	<li>2014-03-01 - Split out different kinds of LDPRs into their own subsection (SS)</li>
+	<li>2014-02-28 - Combined rules for container triples (SS) </li>
+	<li>2014-02-28 - Split out different kinds of LDPCs into their own subsection (SS)</li>
+	<li>2014-02-24 - Corrected rel=meta to be rel=describedby (SS) </li>
+	<li>2014-02-24 - Adjusted term membership triples and membership predicate (SS) </li>
+	<li>2014-02-24 - Removed 6.3.1 LDPC GET requirement and put in general clause (SS) </li>
+	<li>2014-02-20 - Changed LDPC SHOULD NOT put (6.5.1) to be about containment (SS) </li>
+	<li>2014-02-20 - Removed rule on PATCH create, as it doesn't add any substantive over RFC5789 (SS) </li>
+	<li>2014-02-18 - Factored out paging and sorting into separate spec LDP-Paging (SS) </li>
+	<li>2014-02-18 - Reference cleanup and tweak LDP-RS term (SS) </li>
+	<li>2014-02-17 - Reference to RDF Document into terms (SS) </li>
+	<li>2014-02-17 - Adopted container hierarchy and merged Indirect Container into Container (SS) </li>
+	<li>2014-02-17 - Adopted new resource types: LDP RDF Source (LDP-RS) (was LDP RDF Resource) and LDP Non-RDF Source (LDP-NR) (was LDP Binary Resource) (SS)</li>
+	<li>2014-02-17 - Adopted new predicate names: ldp:membershipResource, ldp:hasMemberRelation and ldp:isMemberOfRelation (SS) </li>
+	<li>2014-02-12 - Updated LDPR Post reference to Put, which had implied that clients could PUT (to an LDPC) to create an LDPR (JA)</li>
+	<li>2014-02-12 - Updated containerResource on examples 6 and 7, section 6.1, in resp to public-ldp email (JA)</li>
+	<li>2014-02-12 - Updated LDP-IC definition per email thread (JA)</li>
+	<li>2014-02-11 - Updated LDPC create ldp:contains (errant MAY to MUST, resolving conflicting statements) (JA)</li>
+	<li>2014-02-10 - Removed LDPR Paging HTTP OPTIONS section (no longer needed) and more cleanup of todos (SS)</li>
+	<li>2014-02-10 - Updated LDPC DELETE language and cleanup todos (SS)</li>
+	<li>2014-02-10 - Resolved a few editoral TODO's (JA)</li>
+	<li>2014-02-08 - Put final stake in heart of 'informative' (waves to Sandro), update boilerplate for readability per Arnaud (JA)</li>
+	<li>2014-02-08 - ACTION-132: Use Prefer in place of non-member properties resource (JA)</li>
+	<li>2014-02-08 - Add Prefer header examples, define new URIs from -126 in ttl, tweak acks per Arnaud email (JA)</li>
+	<li>2014-02-07 - ACTION-126: Add Prefer header (JA)</li>
+	<li>2014-02-07 - LDP-BCs use ldp:contains not ldp:member (JA)</li>
+	<li>2014-02-07 - Simplified some of the container examples (SS)</li>
+	<li>2014-02-06 - partial first pass at arnaud's email comments (JA)</li>
+	<li>2014-02-06 - fixing containment def, adding containment triples to terminology (JA)</li>
+	<li>2014-02-06 - fixing POST to create containment/membership triples, which was mangled (JA)</li>
+	<li>2014-02-06 - fully aligning SS changes with http://www.w3.org/2012/ldp/wiki/Containers for basic containers, allowing them to omit the standard predicates in representations despite requiring behavior consistent with the presence of those triples (JA)</li>
+	<li>2014-02-06 - editorial fixes (JA)</li>
+	<li>2014-02-06 - ACTION-127 (complete) use the TAG's new [23]xx code; if that code is not sufficiently through IETF process by CR, we will use a 303 (JA)</li>
+	<li>2014-02-05 - ACTION-133 Get rid of ldp:created which is subsumed by ldp:contains (SS)</li>
+	<li>2014-02-04 - ACTION-124 LDPR-RR as named graphs  (SS)</li>
+	<li>2014-02-04 - ACTION-120 (complete) Updated LDPC general, GET and POST sections (SS)</li>
+	<li>2014-02-04 - ACTION-120 (Part 3) Added ldp:member (SS)</li>
+	<li>2014-02-04 - ACTION-120 (Part 2) Added concepts of containers (basic, direct and indirect) to LDPC intro (SS)</li>
+	<li>2014-01-30 - ACTION-120 (Part 1) Added concepts of containers (basic, direct and indirect) (SS)</li>
+	<li>2014-01-30 - ACTION-123 Added concepts of LDP-RDF-Resource and LDP-Binary-Resource (SS)</li>
+	<li>2014-01-29 - Fix up conformance section to use new LDP client section (SS)</li>
+	<li>2014-01-21 - Updated reference to LDP BP&amp;G editor's draft and added ref to LDP-UCR (SS)</li>
+	<li>2014-01-21 - Removed redudant reqs that have been moved to #ldpclient (SS)</li>
+	<li>2014-01-21 - Fixed formating with &gt;h2 formatting (SS)</li>
+	<li>2014-01-21 - Put reference to <a href="#base-specs">base-specs</a> into intro section (SS)</li>
+	<li>2014-01-17 - First attempt at correcting section ordering and anchors (SS)</li>
+	<li>2014-01-02 - ACTION-122 Updated 4.2.10, 5.4.4, example 8 + added 5.2.11 requiring rel=type for interaction model (JA)</li>
+	<li>2014-01-02 - ACTION-119 Added 5.4.15 requiring ldp:created for indirect containers (JA)</li>
+	<li>2013-11-27 - ACTION-101 Added informative security section (SS)</li>
+	<li>2013-11-27 - ACTION-100 Added informative note to Ordering section that containers can be nested (SS)</li>
+	<li>2013-11-18 - Various editorial and validation fixes (SS)</li>
+    <li>2013-11-12 - Clean up some remnants of inlining (JA)</li>
+    <li>2013-11-12 - Clean up some overly specific language (implications that POST is the only way to create members, etc) (JA)</li>
+    <li>2013-11-12 - Resolve ACTION-112 Update spec to reflect 10/28 resolution for Issue-81 part 1: new predicate names (JA)</li>
+    <li>2013-11-12 - Fix respec messages that only show up on remote server, hit paging examples to remove appearance of inlining (JA)</li>
+    <li>2013-11-11 - Resolve ACTION-113 Update spec to reflect 11/04 resolution to remove 303 and have client use first/next links to detect paging (JA)</li>
+    <li>2013-10-25 - Resolve ACTION-105 Update spec to reflect 9/30 resolution moving Paging links to HTTP headers (JA)</li>
+    <li>2013-10-25 - Resolve ACTION-110 Update spec to reflect 10/21 resolution for normative changes to align vanilla/chocolate (JA)</li>
+    <li>2013-10-22 - Resolve ACTION-109 Update spec to reflect 10/21 resolution for ignoring triples on PUT (JA)</li>
+    <li>2013-10-22 - Resolve ACTION-107 Update spec to reflect 10/07 resolution on 5.6.2 LDPC deletion (JA)</li>
+    <li>2013-10-22 - Resolve ACTION-102 Make 4.6.2 informative, clarify that it re-states what http allows, and in fact it applies to all methods not just delete. (JA)</li>
+    <li>2013-10-22 - Resolve ACTION-103 Change SHOULD to MUST in 4.10.2.3 "LDPR servers that initiate paging SHOULD respond to request ..." (JA)</li>
+    <li>2013-10-22 - Resolve ACTION-108 move restatements of HTTP et al. out of normative sections (JA)</li>
+    <li>2013-10-22 - Resolve ACTION-106 5.3.5 MUST -&gt; SHOULD (JA)</li>
+    <li>2013-10-21 - Mock up status code 209 Related Content (JA)</li>
+    <li>2013-10-01 - Mock up new section for rules declared to be non-normative restatements of info from other specs (JA)</li>
+    <li>2013-10-01 - Revising terminology - membership triples and friends (JA)</li>
+    <li>2013-10-01 - Revising introduction (JA)</li>
+    <li>2013-10-01 - Conformance section drafting + mock up "LDP Clients" section as part of that (JA)</li>
+    <li>2013-09-23 - Remove client/server-initiated paging terms (JA)</li>
+    <li>2013-09-17 - Change must to MUST in 5.6.4 (SS)</li>
+	<li>2013-09-17 - Removed "at-risk" inlining feature from spec, <a href="https://www.w3.org/2012/ldp/track/actions/98">ACTION-98</a> (SS)</li>
+	<li>2013-09-17 - Fixed vanishing section ref problem (SS)</li>
+	<li>2013-08-19 - Basic preparation for edits unto LC draft (SS)</li>
+</ul>
+
+<blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-20130730/">Last Call Draft (2013-07-30)</a></em></blockquote>
+<ul>
+	<li>2013-07-24 - Moved 4.7.2 (from HEAD) to 4.3.2 (GET), shifted rest of GET section by one (SS)</li>
+	<li>2013-07-24 - Moved 4.10.2.5-&gt;4.10.2.4.3,4.10.2.6-&gt;4.10.2.4.1,4.10.2.7-&gt;4.10.2.4.2 and added samples (SS)</li>
+	<li>2013-07-24 - Changed ldp:ascending-&gt;ldp:Ascending, ldp:descending-&gt;ldp:Descending, ldp:non-member-resource -&gt;ldp:nonMemberResource (SS)</li>
+	<li>2013-07-24 - Added term &quot;Page resource&quot; (SS)</li>
+	<li>2013-07-24 - Removed 5.4.8.1 and added 4.2.12 to better handle base/rel URI (SS)</li>
+    <li>2013-07-23 - Added informative <a href="#ldpr-informative" class="sectionRef"></a>, therefore shifting all sections by one 4.1-&gt;4.2, etc (SS)</li>
+	<li>2013-07-23 - Changed <a href="#header-accept-post" class="sectionRef"></a> to at risk as possibly moving to IETF (SS)</li>
+	<li>2013-07-23 - ISSUE-53 4.2.3 changed MUST to SHOULD (SS)</li>
+	<li>2013-07-22 - ISSUE-53 4.2.2 changed MUST to SHOULD (SS)</li>
+	<li>2013-07-17 - Various updates from suggests from <a href="http://lists.w3.org/Archives/Public/public-ldp-wg/2013Jul/0067.html">Raúl</a> (SS)</li>
+	<li>2013-07-15 - Inserted ldp:insertedContentRelation into examples (SS)</li>
+	<li>2013-07-15 - ISSUE-79 ldp:contains =&gt; ldp:created  (JA)</li>
+	<li>2013-07-11 - Improving working in #ldpr-Paging to remove container references (SS)</li>
+	<li>2013-07-11 - Removed 4.1.5, section number fixup:4.1.8-13-&gt;6-11, 4.9.2.* fixup, 5.3.7-10-&gt;\2-5 (SS)</li>
+	<li>2013-07-11 - Removed all stubbed out sections 5.1.3, 5.3.2-6 (SS)</li>
+	<li>2013-07-11 - Various editorial clean up items from editor todo list (SS)</li>
+	<li>2013-07-11 - Removed closed issues that required no new spec changes: 50, 56, 16, 19, 17 (SS)</li>
+	<li>2013-07-11 - ISSUE-51 Added how an LDPR can show which LDPC is it in (SS)</li>
+	<li>2013-07-10 - Removed closed issues that required no new spec changes: 18, 35, 20 (SS)</li>
+	<li>2013-07-10 - ISSUE-44 move section 4.1.7 (relationships are simple RDF links) to guidance (SS)</li>
+	<li>2013-07-10 - ISSUE-72 take 2 - added ldp:MemberSubject to handle default case (SS)</li>
+	<li>2013-07-10 - ISSUE-72 adding 5.2.10 for ldp:insertedContentRelation (SS)</li>
+	<li>2013-07-09 - ISSUE-58 inlining - actions 87-89 inclusive  (JA)</li>
+	<li>2013-07-08 - Moved 5.7.* sections out of HEAD and into OPTIONS as 5.9.*, added 4.6.2 (SS)</li>
+	<li>2013-07-08 - ISSUE-15 Inserted 5.4.12, 5.6.4, 5.7.2 to describe link-relation meta usage (SS)</li>
+	<li>2013-07-08 - ISSUE-79 ldp:contains  (JA)</li>
+	<li>2013-07-08 - ISSUE-80 Accept-Post (JA)</li>
+	<li>2013-07-08 - ISSUE-32 Must support options (JA)</li>
+	<li>2013-07-08 - ISSUE-78 No client inferencing  (JA)</li>
+	<li>2013-07-08 - ISSUE-77 Move "must have rdf:type explicitly" to Best Practices  (JA)</li>
+	<li>2013-07-08 - ISSUE-57 Knowing it's an LDP server  (JA)</li>
+	<li>2013-07-01 - ISSUE-33 Moved 5.1.3 Paging (LDPC) to 4.8 (LDPR) (SS)</li>
+	<li>2013-06-18 - ISSUE-75 5.2.5 membershipxxx predicates required, per 2013-06-18 F2F resolution (JA)</li>
+	<li>2013-06-18 - ISSUE-63 End of 5.3 + example rewritten for 2013-06-18 F2F resolution (JA)</li>
+	<li>2013-06-15 - ISSUE-14 End of 5.3 + example rewritten for ascending/descending sorts with optional collation (JA)</li>
+	<li>2013-06-13 - ISSUE-54 New 5.4.8.1 to set base URI on create for relative URI resolution (SS)</li>
+	<li>2013-06-10 - ISSUE-74 4.4.2 require 428 Condition Required status code when appropriate; SS adding 6585 to biblio (JA)</li>
+	<li>2013-06-05 - ISSUE-64 Remove ?non-member-properties; 5.1.2, 5.3.2, 5.5.2 (JA)</li>
+	<li>2013-05-21 - ISSUE-35 Re-use of URIs on create; 5.2.9, 5.4.11, 5.5.4 (JA)</li>
+	<li>2013-05-21 - ISSUE-43 Slug in LDPC POSTs; 5.4.8, 5.4.10 (JA)</li>
+	<li>2013-05-21 - ISSUE-65 Remove firstPage in favor of Link rel=first, mostly hits 5.3.3/5.3.4 (JA)</li>
+	<li>2013-05-17 - ISSUE-13 Updated 5.2.3 to say any resource can be in an LDPC and inserted 5.5.3 on rejecting member data on PUT to LDPC (SS)</li>
+	<li>2013-05-17 - Tweaks to Terminology section for LDPR and LDPC (SS)</li>
+	<li>2013-05-17 - ISSUE-9 Moved section 4.1.7 out of spec to the <a href="http://www.w3.org/2012/ldp/wiki/Deployment_Guide#Servers_should_serve_up_canonical_URLs">deployment guide</a> (SS)</li>
+	<li>2013-05-15 - Updated wording for 5.2.2 from to be more clear (SS)</li>
+	<li>2013-05-13 - ISSUE-49 Moved section 4.1.4 out of spec to the <a href="http://www.w3.org/2012/ldp/wiki/Deployment_Guide#Predicate_URIs_SHOULD_be_HTTP_URLs">deployment guide</a>. (SS)</li>
+	<li>2013-05-08 - Removed closed issues 5, 7, 55 and 38 as the don't require edits. Added 64 and 65. (SS)</li>
+	<li>2013-05-08 - ISSUE-59 5.3.2 limited rdf:type of ldp:Container, removed 5.6.3, reworded 5.6.2, updated 1. (SS)</li>
+	<li>2013-04-15 - ISSUE-21 Added ldp:containedByRelation to 5.2.5 &amp; 5.5.2, created 5.2.5.1 &amp; 5.3.5.2 to indicate difference. (SS)</li>
+	<li>2013-04-15 - ISSUE-39 Moved informative text from 5.4.5 into 5.4.1, shifted subsections .6-.10 (SS)</li>
+	<li>2013-04-15 - Expanded on wording for 4.3 to be more consistent (SS)</li>
+	<li>2013-04-08 - Fixed two old references to BPR (SS)</li>
+	<li>2013-03-17 - Inserted examples 2&amp;3, a more complete NetWorth resource (SS)</li>
+	<li>2013-03-15 - Update LDPC glossary term based on Cody's feedback (SS)</li>
+	<li>2013-03-15 - Additional fix in 5.2.2 for ISSUE-34 (SS)</li>
+	<li>2013-03-15 - Remove reference to closed issues that don't require edits: ISSUE-27 &amp; ISSUE-45 (SS)</li>
+	<li>2013-03-14 - General prep for 3rd draft, cleanup and a little restructure (SS)</li>
+</ul>
+
+<blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-20130307/">Second Public Working Draft</a></em></blockquote>
+<ul>
+	<li>2013-03-14 - Fixed up broken fragments and typos before publication (SS)</li>
+	<li>2013-03-04 - Comments received from David Wood: 5.3.7 &amp; 5.1.3 clarity, other minor edits (part 2)  (SS)</li>
+	<li>2013-03-04 - Comments received from David Wood: abstract, paging informative (part 1)  (SS)</li>
+	<li>2013-03-04 - ISSUE-36 - Added informative text regarding creationg of containers in 5.4.4 (SS)</li>
+ 	<li>2013-03-04 - ISSUE-12 - Added section 4.7.3 not to allow PATCH for create (SS)</li>
+	<li>2013-03-03 - Adjustments to language about different container behavior (SS)</li>
+	<li>2013-03-02 - Adding trailing '/' on Container URLs to help with readability based on WG suggestion (SS)</li>
+	<li>2013-02-26 - Updated Acknowledgements section (SS)</li>
+	<li>2013-02-25 - ISSUE-29 - Use relative URIs in examples (SS)</li>
+	<li>2013-02-25 - ISSUE-31 - Added a more complete conformance section, motived by SPARQL 1.1 (SS)</li>
+	<li>2013-02-25 - Updating some simple formatting, reorganizing open issues and todos. (SS) </li>
+	<li>2013-02-15 - ISSUE-34 - Aggregration: 5.6.1 and 5.6.2 updated for review. (JA) </li>
+	<li>2013-02-13 - ISSUE-42 - 4.8 Common Properties moved to 
+			<a href="http://www.w3.org/2012/ldp/wiki/Deployment_Guide#Re-use_established_linked_data_vocabularies_instead_of_.28re-.29inventing_duplicates">Deploment Guide</a> 
+			(JA) </li>
+	<li>2013-02-12 - Fixed up previous publication links (SS) </li>
+	<li>2013-02-12 - ISSUE-10 - 4.1.12 to be MUST use entity tags (either weak or strong ones) (SS) </li>
+	<li>2013-02-12 - ISSUE-11 - 4.4.1 Relaxed the MUST ignore dc:modified/creator to MAY (SS) </li>
+	<li>2013-01-16 - ISSUE-25 Updated introduction. 5.2.2 changed to MUST NOT be in multiple containers. Flipped 5.6.1/2 as 
+	first rule leads to 2nd. 5.6.2(was .1) Delete LDPC MUST also delete members. (SS)</li>
+	<li>2013-01-16 - Added new issues ranging from 26-43. Removed closed/deferred issues: 2 &amp; 3 (SS)</li>
+	<li>2012-12-28 - Fixed Typos.  Separated some compound rules like 4.1.5.  Rewording for clarity: 4.1.10, 
+	Text being repeated in several places centralized and cross-linked.  Made printed code output easier to read
+	on black &amp; white printers.  Exposed terms defined in-line under LDPC as Terminology (tentatively).  Removed non-normative
+	qualifer from section 5.2.  Added "several" editors' to-dos.(JA)</li>
+	<li>2012-11-05 - minor rewording from ISSUE-24</li>
+	<li>2012-11-03 - ISSUE-22, ISSUE-23: changed sections 4.2.3 and 5.4.7. Removed closed issues. (SS)</li>
+	<li>2012-11-03 - ISSUE-24 Delete the phrase in 4.5.1 that nays "until ...Request URI" 
+	and adding a sentence, "Clients should note that servers may reuse a Request-URI under some circumstances."</li>
+	<li>2012-11-03 - ISSUE-6 Removed section 4.1.9.  Shifted up sections .10 through .13.</li>
+	<li>2012-11-01 - Fixed minor typo and added some notes (SS)</li>
+</ul>
+
+<blockquote><em><a href="http://www.w3.org/TR/2012/WD-ldp-20121025/">First Public Working Draft</a></em></blockquote>
+<ul>
+	<li>2012-10-15 - ISSUE-8 Changed references from LDBP to LDP, removed definition for "profile" and new namespace (SS)</li>	
+	<li>2012-10-15 - Included additional open ISSUES from Oct 15 WG meeting: 22, 23, 24 (SS)</li>
+	<li>2012-10-14 - Added open ISSUES and formating to prep for public working draft (SS)</li>
+	<li>2012-09-20 - Sent pull request re LINKED-DATA and added suggestion for <code>ldp</code> namespace (SS)</li>
+	<li>2012-09-19 - Repairing references and forward reference to biblio.js updates (SS)</li>
+	<li>2012-09-19 - Fixed rdfs:label range to be rdfs:Literal (SS)</li>
+	<li>2012-09-19 - ISSUE-1 Define Turtle as the required serialization format for LDP (SS)</li>
+	<li>2012-09-18 - Initial ReSpec'ing of <a href="http://www.w3.org/Submission/ldbp/">Member Submission - Linked Data Basic Profile 1.0</a> (SS)</li>
+	<li>2012-09-18 - Fixed up some links and worked on references, work left to do. (SS)</li>
+</ul>
+<blockquote><em><a href="http://www.w3.org/Submission/2012/SUBM-ldbp-20120326/">Submission</a></em></blockquote>
+ -->
+</section>
+
+  
+    
+  
+
+<section id="references" class="appendix" typeof="bibo:Chapter" resource="#references" rel="bibo:Chapter"><!--OddPage--><h2 role="heading" id="h2_references"><span class="secno">C. </span>References</h2><section id="normative-references" typeof="bibo:Chapter" resource="#normative-references" rel="bibo:Chapter"><h3 role="heading" id="h3_normative-references"><span class="secno">C.1 </span>Normative references</h3><dl class="bibliography" about=""><dt id="bib-DC-TERMS">[DC-TERMS]</dt><dd rel="dcterms:requires">Dublin Core Metadata Initiative. <a href="http://dublincore.org/documents/2010/10/11/dcmi-terms/"><cite>Dublin Core Metadata Initiative Terms, version 1.1.</cite></a> 11 October 2010. DCMI Recommendation. URL: <a href="http://dublincore.org/documents/2010/10/11/dcmi-terms/">http://dublincore.org/documents/2010/10/11/dcmi-terms/</a>.
+</dd><dt id="bib-JSON-LD">[JSON-LD]</dt><dd rel="dcterms:requires">Manu Sporny; Gregg Kellogg; Markus Lanthaler. <a href="http://www.w3.org/TR/json-ld/"><cite>JSON-LD 1.0</cite></a>. 16 January 2014. W3C Recommendation. URL: <a href="http://www.w3.org/TR/json-ld/">http://www.w3.org/TR/json-ld/</a>
+</dd><dt id="bib-RFC2119">[RFC2119]</dt><dd rel="dcterms:requires">S. Bradner. <a href="https://tools.ietf.org/html/rfc2119"><cite>Key words for use in RFCs to Indicate Requirement Levels</cite></a>. March 1997. Best Current Practice. URL: <a href="https://tools.ietf.org/html/rfc2119">https://tools.ietf.org/html/rfc2119</a>
+</dd><dt id="bib-RFC3864">[RFC3864]</dt><dd rel="dcterms:requires">G. Klyne; M. Nottingham; J. Mogul. <a href="https://tools.ietf.org/html/rfc3864"><cite>Registration Procedures for Message Header Fields</cite></a>. September 2004. Best Current Practice. URL: <a href="https://tools.ietf.org/html/rfc3864">https://tools.ietf.org/html/rfc3864</a>
+</dd><dt id="bib-RFC3986">[RFC3986]</dt><dd rel="dcterms:requires">T. Berners-Lee; R. Fielding; L. Masinter. <a href="https://tools.ietf.org/html/rfc3986"><cite>Uniform Resource Identifier (URI): Generic Syntax</cite></a>. January 2005. Internet Standard. URL: <a href="https://tools.ietf.org/html/rfc3986">https://tools.ietf.org/html/rfc3986</a>
+</dd><dt id="bib-RFC3987">[RFC3987]</dt><dd rel="dcterms:requires">M. Duerst; M. Suignard. <a href="https://tools.ietf.org/html/rfc3987"><cite>Internationalized Resource Identifiers (IRIs)</cite></a>. January 2005. Proposed Standard. URL: <a href="https://tools.ietf.org/html/rfc3987">https://tools.ietf.org/html/rfc3987</a>
+</dd><dt id="bib-RFC5023">[RFC5023]</dt><dd rel="dcterms:requires">J. Gregorio, Ed.; B. de hOra, Ed.. <a href="https://tools.ietf.org/html/rfc5023"><cite>The Atom Publishing Protocol</cite></a>. October 2007. Proposed Standard. URL: <a href="https://tools.ietf.org/html/rfc5023">https://tools.ietf.org/html/rfc5023</a>
+</dd><dt id="bib-RFC5234">[RFC5234]</dt><dd rel="dcterms:requires">D. Crocker, Ed.; P. Overell. <a href="https://tools.ietf.org/html/rfc5234"><cite>Augmented BNF for Syntax Specifications: ABNF</cite></a>. January 2008. Internet Standard. URL: <a href="https://tools.ietf.org/html/rfc5234">https://tools.ietf.org/html/rfc5234</a>
+</dd><dt id="bib-RFC5789">[RFC5789]</dt><dd rel="dcterms:requires">L. Dusseault; J. Snell. <a href="https://tools.ietf.org/html/rfc5789"><cite>PATCH Method for HTTP</cite></a>. March 2010. Proposed Standard. URL: <a href="https://tools.ietf.org/html/rfc5789">https://tools.ietf.org/html/rfc5789</a>
+</dd><dt id="bib-RFC5988">[RFC5988]</dt><dd rel="dcterms:requires">M. Nottingham. <a href="https://tools.ietf.org/html/rfc5988"><cite>Web Linking</cite></a>. October 2010. Proposed Standard. URL: <a href="https://tools.ietf.org/html/rfc5988">https://tools.ietf.org/html/rfc5988</a>
+</dd><dt id="bib-RFC6585">[RFC6585]</dt><dd rel="dcterms:requires">M. Nottingham; R. Fielding. <a href="https://tools.ietf.org/html/rfc6585"><cite>Additional HTTP Status Codes</cite></a>. April 2012. Proposed Standard. URL: <a href="https://tools.ietf.org/html/rfc6585">https://tools.ietf.org/html/rfc6585</a>
+</dd><dt id="bib-RFC7230">[RFC7230]</dt><dd rel="dcterms:requires">R. Fielding, Ed.; J. Reschke, Ed.. <a href="https://tools.ietf.org/html/rfc7230"><cite>Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</cite></a>. June 2014. Proposed Standard. URL: <a href="https://tools.ietf.org/html/rfc7230">https://tools.ietf.org/html/rfc7230</a>
+</dd><dt id="bib-RFC7231">[RFC7231]</dt><dd rel="dcterms:requires">R. Fielding, Ed.; J. Reschke, Ed.. <a href="https://tools.ietf.org/html/rfc7231"><cite>Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</cite></a>. June 2014. Proposed Standard. URL: <a href="https://tools.ietf.org/html/rfc7231">https://tools.ietf.org/html/rfc7231</a>
+</dd><dt id="bib-RFC7232">[RFC7232]</dt><dd rel="dcterms:requires">R. Fielding, Ed.; J. Reschke, Ed.. <a href="https://tools.ietf.org/html/rfc7232"><cite>Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</cite></a>. June 2014. Proposed Standard. URL: <a href="https://tools.ietf.org/html/rfc7232">https://tools.ietf.org/html/rfc7232</a>
+</dd><dt id="bib-RFC7240">[RFC7240]</dt><dd rel="dcterms:requires">J. Snell. <a href="https://tools.ietf.org/html/rfc7240"><cite>Prefer Header for HTTP</cite></a>. June 2014. Proposed Standard. URL: <a href="https://tools.ietf.org/html/rfc7240">https://tools.ietf.org/html/rfc7240</a>
+</dd><dt id="bib-WEBARCH">[WEBARCH]</dt><dd rel="dcterms:requires">Ian Jacobs; Norman Walsh. <a href="http://www.w3.org/TR/webarch/"><cite>Architecture of the World Wide Web, Volume One</cite></a>. 15 December 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/webarch/">http://www.w3.org/TR/webarch/</a>
+</dd><dt id="bib-rdf-schema">[rdf-schema]</dt><dd rel="dcterms:requires">Dan Brickley; Ramanathan Guha. <a href="http://www.w3.org/TR/rdf-schema/"><cite>RDF Schema 1.1</cite></a>. 25 February 2014. W3C Recommendation. URL: <a href="http://www.w3.org/TR/rdf-schema/">http://www.w3.org/TR/rdf-schema/</a>
+</dd><dt id="bib-rdf11-concepts">[rdf11-concepts]</dt><dd rel="dcterms:requires">Richard Cyganiak; David Wood; Markus Lanthaler. <a href="http://www.w3.org/TR/rdf11-concepts/"><cite>RDF 1.1 Concepts and Abstract Syntax</cite></a>. 25 February 2014. W3C Recommendation. URL: <a href="http://www.w3.org/TR/rdf11-concepts/">http://www.w3.org/TR/rdf11-concepts/</a>
+</dd><dt id="bib-turtle">[turtle]</dt><dd rel="dcterms:requires">Eric Prud'hommeaux; Gavin Carothers. <a href="http://www.w3.org/TR/turtle/"><cite>RDF 1.1 Turtle</cite></a>. 25 February 2014. W3C Recommendation. URL: <a href="http://www.w3.org/TR/turtle/">http://www.w3.org/TR/turtle/</a>
+</dd></dl></section><section id="informative-references" typeof="bibo:Chapter" resource="#informative-references" rel="bibo:Chapter"><h3 role="heading" id="h3_informative-references"><span class="secno">C.2 </span>Informative references</h3><dl class="bibliography" about=""><dt id="bib-Accept-Post">[Accept-Post]</dt><dd rel="dcterms:references">J. Arwe; S. Speicher; E. Wilde. <a href="http://tools.ietf.org/html/draft-wilde-accept-post"><cite>The Accept-Post HTTP Header</cite></a>. Internet Draft. URL: <a href="http://tools.ietf.org/html/draft-wilde-accept-post">http://tools.ietf.org/html/draft-wilde-accept-post</a>
+</dd><dt id="bib-HTML401">[HTML401]</dt><dd rel="dcterms:references">Dave Raggett; Arnaud Le Hors; Ian Jacobs. <a href="http://www.w3.org/TR/html401"><cite>HTML 4.01 Specification</cite></a>. 24 December 1999. W3C Recommendation. URL: <a href="http://www.w3.org/TR/html401">http://www.w3.org/TR/html401</a>
+</dd><dt id="bib-LDP-PAGING">[LDP-PAGING]</dt><dd rel="dcterms:references">S. Speicher; J. Arwe; A. Malhotra. <a href="http://www.w3.org/TR/ldp-paging/"><cite>Linked Data Platform Paging</cite></a>. Candidate Recommendation. URL: <a href="http://www.w3.org/TR/ldp-paging/">http://www.w3.org/TR/ldp-paging/</a>
+</dd><dt id="bib-LDP-Tests">[LDP-Tests]</dt><dd rel="dcterms:references">R. Garcia-Castro; F. Serena. <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/tests/ldp-testsuite.html"><cite>Linked Data Platform 1.0 Test Cases</cite></a>. Editor's Draft of Working Group Note. URL: <a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/tests/ldp-testsuite.html">https://dvcs.w3.org/hg/ldpwg/raw-file/default/tests/ldp-testsuite.html</a>
+</dd><dt id="bib-LDP-UCR">[LDP-UCR]</dt><dd rel="dcterms:references">Steve Battle; Steve Speicher. <a href="http://www.w3.org/TR/ldp-ucr/"><cite>Linked Data Platform Use Cases and Requirements</cite></a>. 13 March 2014. W3C Note. URL: <a href="http://www.w3.org/TR/ldp-ucr/">http://www.w3.org/TR/ldp-ucr/</a>
+</dd><dt id="bib-LINKED-DATA">[LINKED-DATA]</dt><dd rel="dcterms:references">Tim Berners-Lee. <a href="http://www.w3.org/DesignIssues/LinkedData.html"><cite>Linked Data Design Issues</cite></a>. 27 July 2006. W3C-Internal Document. URL: <a href="http://www.w3.org/DesignIssues/LinkedData.html">http://www.w3.org/DesignIssues/LinkedData.html</a>
+</dd><dt id="bib-POWDER">[POWDER]</dt><dd rel="dcterms:references">Phil Archer; Kevin Smith; Andrea Perego. <a href="http://www.w3.org/TR/2009/REC-powder-dr-20090901/"><cite>Protocol for Web Description Resources (POWDER): Description Resources</cite></a>. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2009/REC-powder-dr-20090901/">http://www.w3.org/TR/2009/REC-powder-dr-20090901/</a>
+</dd><dt id="bib-RFC4627">[RFC4627]</dt><dd rel="dcterms:references">D. Crockford. <a href="https://tools.ietf.org/html/rfc4627"><cite>The application/json Media Type for JavaScript Object Notation (JSON)</cite></a>. July 2006. Informational. URL: <a href="https://tools.ietf.org/html/rfc4627">https://tools.ietf.org/html/rfc4627</a>
+</dd><dt id="bib-SPARQL-UPDATE">[SPARQL-UPDATE]</dt><dd rel="dcterms:references">Paul Gearon; Alexandre Passant; Axel Polleres. <a href="http://www.w3.org/TR/sparql11-update/"><cite>SPARQL 1.1 Update</cite></a>. 21 March 2013. W3C Recommendation. URL: <a href="http://www.w3.org/TR/sparql11-update/">http://www.w3.org/TR/sparql11-update/</a>
+</dd><dt id="bib-sparql11-query">[sparql11-query]</dt><dd rel="dcterms:references">Steven Harris; Andy Seaborne. <a href="http://www.w3.org/TR/sparql11-query/"><cite>SPARQL 1.1 Query Language</cite></a>. 21 March 2013. W3C Recommendation. URL: <a href="http://www.w3.org/TR/sparql11-query/">http://www.w3.org/TR/sparql11-query/</a>
+</dd></dl></section></section></body></html>
\ No newline at end of file
Binary file TR/PR-ldp-20141211/images/ldpc-basic.png has changed
Binary file TR/PR-ldp-20141211/images/ldpc-hierarchy.png has changed
Binary file TR/PR-ldp-20141211/images/ldpc1.png has changed
Binary file TR/PR-ldp-20141211/images/ldpr1.png has changed
Binary file TR/PR-ldp-20141211/images/ldpr2.png has changed
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/TR/PR-ldp-20141211/ldp.ttl	Thu Dec 11 08:38:57 2014 -0500
@@ -0,0 +1,183 @@
+# See details within this document for linkage to specification and purpose.
+# This ontology file is a non-normative supporting document.
[email protected] rdfs: <http://www.w3.org/2000/01/rdf-schema#>.
[email protected] owl: <http://www.w3.org/2002/07/owl#>.
[email protected] rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>.
[email protected] dcterms: <http://purl.org/dc/terms/>.
[email protected] vs: <http://www.w3.org/2003/06/sw-vocab-status/ns#> .
[email protected] : <http://www.w3.org/ns/ldp#>.
+
+:
+	a owl:Ontology;
+    dcterms:description "All vocabulary URIs defined in the Linked Data Platform (LDP) namespace.";
+	dcterms:title "The W3C Linked Data Platform (LDP) Vocabulary";
+	rdfs:label "W3C Linked Data Platform (LDP)";
+	rdfs:comment "This ontology provides an informal representation of the concepts and terms
+	as defined in the LDP specification.  Consult the LDP specification for normative reference.";
+	rdfs:seeAlso <http://www.w3.org/2012/ldp>,
+		<http://www.w3.org/TR/ldp-ucr/>,
+		<http://www.w3.org/TR/ldp/>,
+		<http://www.w3.org/2011/09/LinkedData/>.
+		
+:Resource
+    a rdfs:Class;
+	rdfs:comment "A HTTP-addressable resource whose lifecycle is managed by a LDP server.";
+	vs:term_status "unstable";
+	rdfs:isDefinedBy :;
+	rdfs:label "Resource".
+
+:RDFSource
+    a rdfs:Class;
+    rdfs:subClassOf :Resource;
+	rdfs:comment "A Linked Data Platform Resource (LDPR) whose state is represented as 
+		RDF.";
+	vs:term_status "unstable";
+	rdfs:isDefinedBy :;
+	rdfs:label "RDFSource".
+
+:NonRDFSource
+    a rdfs:Class;
+    rdfs:subClassOf :Resource;
+	rdfs:comment "A Linked Data Platform Resource (LDPR) whose state is NOT represented as
+		RDF.";
+	vs:term_status "unstable";
+	rdfs:isDefinedBy :;
+	rdfs:label "NonRDFSource".
+	
+:Container
+    a rdfs:Class;
+	rdfs:subClassOf :RDFSource;
+	rdfs:comment "A Linked Data Platform RDF Source (LDP-RS) that also conforms to 
+	additional patterns and conventions for managing membership.
+	Readers should refer to the specification defining this ontology for the list of 
+	behaviors associated with it.";
+	vs:term_status "unstable";
+	rdfs:isDefinedBy :;
+	rdfs:label "Container".
+
+:BasicContainer
+    a rdfs:Class;
+	rdfs:subClassOf :Container;
+	rdfs:comment "An LDPC that uses a predefined predicate to simply link to its contained resources.";
+	vs:term_status "unstable";
+	rdfs:isDefinedBy :;
+	rdfs:label "BasicContainer".
+
+:DirectContainer
+    a rdfs:Class;
+	rdfs:subClassOf :Container;
+	rdfs:comment "An LDPC that is similar to a LDP-DC but it allows an indirection with the ability to 
+    	list as member a resource, such as a URI representing a real-world object, that is different 
+    	from the resource that is created";
+	vs:term_status "unstable";
+	rdfs:isDefinedBy :;
+	rdfs:label "DirectContainer".
+
+:IndirectContainer
+    a rdfs:Class;
+	rdfs:subClassOf :Container;
+	rdfs:comment "An LDPC that has the flexibility of choosing what form the membership triples take.";
+	vs:term_status "unstable";
+	rdfs:isDefinedBy :;
+	rdfs:label "IndirectContainer".
+		
+:hasMemberRelation
+	a rdf:Property;
+	rdfs:comment "Indicates which predicate is used in membership triples, and that the membership triple pattern is < membership-constant-URI , object-of-hasMemberRelation, member-URI >.";
+	vs:term_status "unstable";
+	rdfs:domain :Container;
+	rdfs:isDefinedBy :;
+	rdfs:label "hasMemberRelation";
+	rdfs:range rdf:Property.
+
+:isMemberOfRelation
+	a rdf:Property;
+	rdfs:comment "Indicates which predicate is used in membership triples, and that the membership triple pattern is < member-URI , object-of-isMemberOfRelation, membership-constant-URI >.";
+	vs:term_status "unstable";
+	rdfs:domain :Container;
+	rdfs:isDefinedBy :;
+	rdfs:label "isMemmberOfRelation";
+	rdfs:range rdf:Property.
+	
+:membershipResource
+	a rdf:Property;
+	rdfs:comment "Indicates the membership-constant-URI in a membership triple.  Depending upon the membership triple pattern a container uses, as indicated by the presence of ldp:hasMemberRelation or ldp:isMemberOfRelation, the membership-constant-URI might occupy either the subject or object position in membership triples.";
+	vs:term_status "unstable";
+	rdfs:domain :Container;
+	rdfs:isDefinedBy :;
+	rdfs:label "membershipResource";
+	rdfs:range rdf:Property.
+	
+:insertedContentRelation
+	a rdf:Property;
+	rdfs:comment "Indicates which triple in a creation request should be used as the member-URI value in the membership triple added when the creation request is successful.";
+	vs:term_status "unstable";
+	rdfs:domain :Container;
+	rdfs:isDefinedBy :;
+	rdfs:label "insertedContentRelation";
+	rdfs:range rdf:Property.
+
+:member
+	a rdf:Property;
+	rdfs:comment "LDP servers should use this predicate as the membership predicate if there is no obvious predicate from an application vocabulary to use.";
+	vs:term_status "unstable";
+	rdfs:domain :Resource;
+	rdfs:isDefinedBy :;
+	rdfs:label "member";
+	rdfs:range rdfs:Resource.
+
+:contains
+	a rdf:Property;
+	rdfs:comment "Links a container with resources created through the container.";
+	vs:term_status "unstable";
+	rdfs:domain :Container;
+	rdfs:isDefinedBy :;
+	rdfs:label "contains";
+	rdfs:range rdfs:Resource.
+
+:MemberSubject
+	a rdf:Description;		# individual
+	rdfs:comment "Used to indicate default and typical behavior for ldp:insertedContentRelation, where the member-URI value in the membership triple added when a creation request is successful is the URI assigned to the newly created resource.";
+	vs:term_status "unstable";
+	rdfs:isDefinedBy :;
+	rdfs:label "MemberSubject".
+
+:PreferContainment
+ 	a rdf:Description;		# individual
+	rdfs:comment "URI identifying a LDPC's containment triples, for example to allow clients to express interest in receiving them.";
+	vs:term_status "unstable";
+	rdfs:isDefinedBy :;
+	rdfs:label "PreferContainment".
+
+:PreferMembership
+ 	a rdf:Description;		# individual
+	rdfs:comment "URI identifying a LDPC's membership triples, for example to allow clients to express interest in receiving them.";
+	vs:term_status "unstable";
+	rdfs:isDefinedBy :;
+	rdfs:label "PreferMembership".
+
+:PreferEmptyContainer
+ 	a rdf:Description;		# individual
+	rdfs:comment "Archaic alias for ldp:PreferMinimalContainer";
+	vs:term_status "deprecated";
+	rdfs:isDefinedBy :;
+	rdfs:sameAs :PreferMinimalContainer;
+	rdfs:seeAlso :PreferMinimalContainer;
+	rdfs:label "PreferEmptyContainer".
+
+:PreferMinimalContainer
+ 	a rdf:Description;		# individual
+	rdfs:comment "URI identifying the subset of a LDPC's triples present in an empty LDPC, for example to allow clients to express interest in receiving them.  Currently this excludes containment and membership triples, but in the future other exclusions might be added.  This definition is written to automatically exclude those new classes of triples.";
+	vs:term_status "unstable";
+	rdfs:isDefinedBy :;
+	rdfs:label "PreferMinimalContainer".
+
+:constrainedBy
+	a rdf:Property;
+	rdfs:comment "Links a resource with constraints that the server requires requests like creation and update to conform to.";
+	vs:term_status "unstable";
+	rdfs:domain :Resource;
+	rdfs:isDefinedBy :;
+	rdfs:label "constrainedBy";
+	rdfs:range rdfs:Resource.
+