Fixed minor spelling/grammar and validation problems
authorsspeiche
Thu, 17 Jul 2014 13:48:27 -0400
changeset 715 57bb75a0204a
parent 714 d6b3d3929c79
child 716 a76f182b5d2c
Fixed minor spelling/grammar and validation problems
ldp-paging.html
tests/reports/ldp-earl-manifest.jsonld
tests/reports/ldp-earl-manifest.ttl
--- a/ldp-paging.html	Tue Jul 15 16:48:39 2014 -0400
+++ b/ldp-paging.html	Thu Jul 17 13:48:27 2014 -0400
@@ -314,7 +314,7 @@
 	<p>
 		When a <a>paged resource</a> is also an LDPC, some additional efficiencies become possible in cases
 		where the server predictably assigns members to pages and is able to communicate its assignment
-		algorithm to clients.  <a href="#ldpc" class="sectionRef"></a> defines a facility to communicate 
+		algorithm to clients.  The <a href="#ldpc" class="sectionRef"></a> defines a facility is to communicate 
 		the sort order of member-to-page assignments, to handle that common implementation algorithm.
 	</p>
 	<p>
@@ -426,7 +426,7 @@
 	<dt><dfn>first page link</dfn></dt>
 	<dd>A link to the first <a title="In-sequence page resource">in-sequence page resource</a> <var>P<sub>1 (first)</sub></var>
 	of a <a title="Paged resource">paged resource</a> <var>P</var>.  The first page is the one that a LDP paging server
-	redirects to (<code>303</code> response) or provides the representation of (<code>2NN response</code>) in response
+	redirects to (<code>303</code> response) or provides the representation of (<code>2NN</code> response) in response
 	to a retrieval request for the <a>paged resource</a>'s URI; it is, in that sense, nearest to the <a>paged resource</a> <var>P</var>.
 	Syntactically, a
 	HTTP <code>Link &lt;<var>P<sub>1</sub></var>&gt;; rel='first'</code>
@@ -514,12 +514,13 @@
 
 <ul>
   <li><a href="#intro" class="sectionRef"></a>: <b>non-normative</b></li>
-  <li><a href="#terms" class="sectionRef"></a></li>
+  <li><a href="#terms" class="sectionRef"></a>
 	<ul>
 	  <li><a href="#terms-from-ldp" class="sectionRef"></a>: <b>non-normative</b></li>
 	  <li><a href="#terms-from-paging" class="sectionRef"></a>: <b>normative</b></li>
 	  <li><a href="#conventions" class="sectionRef"></a>: <b>normative</b></li>
 	</ul>
+  </li>
   <li><a href="#conformance" class="sectionRef"></a>: <b>normative</b></li>
   <li><a href="#ldpp-ex-mx" class="sectionRef"></a>: <b>non-normative</b></li>
   <li><a href="#ldppclient" class="sectionRef"></a>: <b>normative</b></li>
@@ -1113,7 +1114,7 @@
 	
 	<section id="ldpp-client-4xxok"><h2 class="normal"><a title="LDP Paging client">LDP Paging clients</a> MUST NOT
 		assume that any <a title="In-sequence page resource">in-sequence page resource's</a> <a title="paging link">paging links</a>
-		will always be accessible.  
+		will always be accessible.</h2>
 		<blockquote><em>Non-normative note:</em> 
 		Such an assumption would 
 		conflict with a server's ability to <a href="#ldpr-pagingGET-sequences-change">remove pages from a sequence</a> 
@@ -1125,7 +1126,7 @@
 		<a href="#ldpr-notify-changes">state has <i>not</i> changed</a> 
 		while the client was traversing its <a title="In-sequence page resource">pages</a>.
 		</blockquote>
-	</h2>
+	
 	</section>
 	
 	<section id="ldpp-client-paging-incomplete"><h2 class="normal"><a title="LDP Paging client">LDP Paging clients</a>  
@@ -1162,13 +1163,10 @@
 		request header with a 
 		<code>return=representation</code> preference that includes a
 		<code>page-size</code> parameter whose value adheres to the following syntax:
-		</h2>
-		<pre><code>
-		page-size-parameter = "page-size" *WSP "=" *WSP DQUOTE *WSP 1*DIGIT 1*WSP 1*units *WSP DQUOTE
-		units               = rdf-triples / extension-units
-		rdf-triples         = "rdf-triples"   ; units = RDF triples
-		extension-units     = token           ; other units allowed for future extensibility
-		</code></pre>
+		<pre><code>page-size-parameter = "page-size" *WSP "=" *WSP DQUOTE *WSP 1*DIGIT 1*WSP 1*units *WSP DQUOTE
+units               = rdf-triples / extension-units
+rdf-triples         = "rdf-triples"   ; units = RDF triples
+extension-units     = token           ; other units allowed for future extensibility</code></pre>
 		<blockquote>
 		<p>
 		<code>WSP</code> is whitespace [[!RFC5234]], 
@@ -1269,10 +1267,10 @@
 	</h2></section>
 
 	<section id="ldpp-prefer"><h2 class="normal"><a title="LDP Paging server">LDP Paging servers</a>
-		SHOULD respect all of a client's <a href="#ldpp-hints">LDP-Paging-defined hints</a>, for example 
+		SHOULD respect all of a client's <a href="#ldpp-hints">LDP Paging defined hints</a>, for example 
 		<a href="#ldpp-hints">the largest page size</a>
 		the client is interested in processing,
-		to influence the amount of data returned in representations.  
+		to influence the amount of data returned in representations.</h2> 
 	<blockquote>
 		<em>Non-normative note</em>: LDP server implementers should carefully consider the effects of these
 		preferences on caching, as described in section 2 of [[!RFC7240]].
@@ -1282,7 +1280,7 @@
 		<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.
 	</blockquote>
-	</h2></section>
+	</section>
 
 	<section id="ldpp-prefer-unrecognized"><h2 class="normal">
 		<a title="LDP Paging server">LDP Paging servers</a> MAY 
@@ -1346,7 +1344,7 @@
 		then the client has a complete view of its state as given by the negotiated response media type
 		<em>at the point in time when the final page was retrieved</em>.  
 		If the <a>paged resource</a> <em>does</em> change during the traversal, then only the portions that
-		were actually updated will differ; the client has no LDP Paging-provided means for knowing in what
+		were actually updated will differ; the client has no LDP Paging provided means for knowing in what
 		way(s) its view differs from that of the server in this case.  
 		</blockquote>
 		<blockquote><em>Non-normative note:</em> 
@@ -1408,6 +1406,7 @@
 		and a corresponding parameter value identical to the ETag [[!RFC7232]]
 		of the <a>paged resource</a>.
 		For example: <code>Link: &lt;http://example.org/customer-relations&gt;; rel='canonical'; etag="customer-relations-v1"</code>
+		</h2>
 		<blockquote><em>Non-normative note:</em> 
 		If the <code>rel='canonical'; etag="..."</code> value changes as the client retrieves pages, 
 		for example the value accompanying the first page's representation is <code>rel='canonical'; etag="v1"</code> 
@@ -1415,7 +1414,7 @@
 		the client can detect that the <a>paged resource</a>'s state has changed.
 		Some clients will ignore such changes, but others may choose to react to them, for example by restarting the traversal.
 		</blockquote>
-	</h2></section>
+	</section>
 
 	<section id="ldpr-pagingGET-sequences-change"><h2 class="normal">
 		<a title="LDP Paging server">LDP Paging servers</a> MAY
@@ -1499,7 +1498,7 @@
 			initiate paging unless the client has indicated it understands paging.
 			The only standard means defined by LDP paging for a client to signal a server that the client
 			understands paging is via the <a href="#ldpp-hints">client preference</a> defined for this purpose;
-			other implementation-specific means could also be used.
+			other implementation-specific means could also be used.</h2>
 			<blockquote>
 				<em>Non-normative note:</em>
 				<a title="LDP Paging server">LDP Paging servers</a> could choose to make any resource
@@ -1513,7 +1512,7 @@
 				status code concludes that it now has the <em>entire</em> representation of the paged resource's state (instead
 				of only having a representation of the subset assigned to the first page).
 			</blockquote>
-		</h2></section>
+		</section>
 
 </section>
 
@@ -1639,7 +1638,7 @@
 	<p>
 		As you can see, the <code>ldp:ContainerSortCriteria</code> predicate has been added.
 		The <code>ldp:ContainerSortCriteria</code> 
-		predicate asserts that the <code>o:value</code> predicate will used	<em>when the container is paged</em>
+		predicate asserts that the <code>o:value</code> predicate will be used <em>when the container is paged</em>
 		to assign sets of members to pages in ascending order.  
 		<em>Since the resource above was not paged, in this instance it conveys no useful information
 		to the client.</em>
@@ -1742,8 +1741,8 @@
 		sort criterion</em>, illustrating that this criterion applies only to the 
 		sorting of "assigning members to pages", not
 		to the ordering within any single page's representation.
-		Typically those representations are generated by libraries like Jena,
-		whose serializers do not provide ordering of this variety.
+		Typically those representations have not guarantee of ordering and are generated by libraries,
+		whose serializers do not provide a way to control how the order is conveyed.
 	</p>
 	<p>
 		It is up to the domain model
@@ -1822,14 +1821,14 @@
 		open standardized values, any value can be used.
 		When the <code>ldp:containerSortCollation</code> triple is absent and the 
 		<a title="page-ordering values">page-ordering values</a> are strings or simple literals [[!sparql11-query]], the
-		resulting order is as defined by SPARQL SELECT’s ORDER BY clause 
+		resulting order is as defined by SPARQL <code>SELECT</code>’s <code>ORDER BY</code> clause 
 		[[!sparql11-query]] using two-argument <code>fn:compare</code>, that is, 
 		it behaves as if <code>http://www.w3.org/2005/xpath-functions/collation/codepoint</code> 
 		was the specified collation.
 		When the <code>ldp:containerSortCollation</code> triple is present and the 
 		<a title="page-ordering values">page-ordering values</a> are strings or simple literals 
 		[[!sparql11-query]], the
-		resulting order is as defined by SPARQL SELECT’s ORDER BY clause 
+		resulting order is as defined by SPARQL <code>SELECT</code>’s <code>ORDER BY</code> clause 
 		[[!sparql11-query]] using three-argument <code>fn:compare</code>, that is, the 
 		specified collation.
 		The <code>ldp:containerSortCollation</code> triple MUST be omitted for comparisons
@@ -1998,6 +1997,7 @@
 <!-- <blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-paging-20140930/">Candidate Recommendation Draft</a></em></blockquote> wah -->
 <!-- <blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-paging-20140730/">Last Call Draft</a></em></blockquote> -->
 <ul>
+	<li>2014-07-17 - Fixed minor spelling/grammar and validation problems (SS)</li>
 	<li>2014-07-15 - Final updates hopefully before LC2 draft issued (JA) </li>
 	<li>2014-07-09 - Fix Ashok's emailed comments (JA) </li>
 	<li>2014-07-09 - Clean up clients chapter, references, non/normative section listing in conformance, kitchen sink (JA) </li>
@@ -2006,7 +2006,7 @@
 	<li>2014-07-07 - Clients must consent to/invite paging per 20140630 resolution 2 (JA) </li>
 	<li>2014-07-07 - Rename single-page resource to in-sequence page resource per 20140630 resolution 3 (JA) </li>
 	<li>2014-06-10 - Use http-bis and Prefer RFC numbers, adjust BNF to match bis changes (JA) </li>
-	<li>2014-05-22 - Spec membership & containment triples on same page (JA) </li>
+	<li>2014-05-22 - Spec membership &amp; containment triples on same page (JA) </li>
 	<li>2014-05-22 - Spec syntax for page size hint; still need to wrap more text and examples around it (JA) </li>
 	<li>2014-05-20 - Spec Sandro's proposal, choose link relation for detection of paged resource changes (JA) </li>
 	<li>2014-05-19 - Rewrote non-normative parts, cleaned up terminology, ordering undefined when paging non-LDPC LDPRs (JA) </li>
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/tests/reports/ldp-earl-manifest.jsonld	Thu Jul 17 13:48:27 2014 -0400
@@ -0,0 +1,10775 @@
+{
+  "@graph" : [ {
+    "@id" : "_:t10",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-http"
+    },
+    "td:includesText" : "LDP servers MUST at least be HTTP/1.1 conformant servers [HTTP11]."
+  }, {
+    "@id" : "_:t100",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-gen-reusevocabsuchas"
+    },
+    "td:includesText" : "LDP-RSs predicates SHOULD use standard vocabularies such as Dublin Core [DC-TERMS], RDF [rdf11-concepts] and RDF Schema [rdf-schema], whenever possible."
+  }, {
+    "@id" : "_:t102",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-options-allow"
+    },
+    "td:includesText" : "LDP servers MUST indicate their support for HTTP Methods by responding to a HTTP OPTIONS request on the LDPR’s URL with the HTTP Method tokens in the HTTP response header Allow. "
+  }, {
+    "@id" : "_:t103",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-options-must"
+    },
+    "td:includesText" : "LDP servers MUST support the HTTP OPTIONS method. "
+  }, {
+    "@id" : "_:t104",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-head-must"
+    },
+    "td:includesText" : "LDP servers MUST support the HTTP HEAD method. "
+  }, {
+    "@id" : "_:t109",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpic-are-ldpcs"
+    },
+    "td:includesText" : "Each LDP Indirect Container MUST also be a conforming LDP Direct Container in section 5.4 Direct along the following restrictions."
+  }, {
+    "@id" : "_:t11",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-put-mbrprops"
+    },
+    "td:includesText" : "LDP servers SHOULD NOT allow HTTP PUT to update an LDPC’s containment triples; if the server receives such a request, it SHOULD respond with a 409 (Conflict) status code."
+  }, {
+    "@id" : "_:t111",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-gen-reusevocab"
+    },
+    "td:includesText" : "LDP-RSs SHOULD 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."
+  }, {
+    "@id" : "_:t112",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-put-failed"
+    },
+    "td:includesText" : "LDP servers SHOULD 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 section 4.2.1 General."
+  }, {
+    "@id" : "_:t113",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-http"
+    },
+    "td:includesText" : "LDP servers MUST at least be HTTP/1.1 conformant servers [HTTP11]."
+  }, {
+    "@id" : "_:t114",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-cli-typeschange"
+    },
+    "td:includesText" : "In the absence of special knowledge of the application or domain, LDP clients MUST assume that the rdf:type values of a given LDP-RS can change over time."
+  }, {
+    "@id" : "_:t115",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-precond"
+    },
+    "td:includesText" : "LDP servers MUST respond with status code 412 (Condition Failed) if ETags fail to match when there are no other errors with the request [HTTP11]. LDP servers that require conditional requests MUST respond with status code 428 (Precondition Required) when the absence of a precondition is the only reason for rejecting the request [RFC6585]."
+  }, {
+    "@id" : "_:t116",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-created201"
+    },
+    "td:includesText" : "If the resource was created successfully, LDP servers MUST respond with status code 201 (Created) and the Location header set to the new resource’s URL. Clients shall not expect any representation in the response entity body on a 201 (Created) response."
+  }, {
+    "@id" : "_:t121",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-options-linkmetahdr"
+    },
+    "td:includesText" : "When responding to requests whose request-URI is a LDP-NR with anassociated LDP-RS, a LDPC server must provide the same HTTP Link responseheader as is required in the create response"
+  }, {
+    "@id" : "_:t122",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-precond"
+    },
+    "td:includesText" : "LDP servers MUST respond with status code 412 (Condition Failed) if ETags fail to match when there are no other errors with the request [HTTP11]. LDP servers that require conditional requests MUST respond with status code 428 (Precondition Required) when the absence of a precondition is the only reason for rejecting the request [RFC6585]."
+  }, {
+    "@id" : "_:t123",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-cli-typeschange"
+    },
+    "td:includesText" : "In the absence of special knowledge of the application or domain, LDP clients MUST assume that the rdf:type values of a given LDP-RS can change over time."
+  }, {
+    "@id" : "_:t128",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-createrdf"
+    },
+    "td:includesText" : "LDP servers that successfully create a resource from a RDF representation in the request entity body MUST honor the client's requested interaction model(s). The created resource can be thought of as an RDF named graph [rdf11-concepts]. If any model cannot be honored, the server MUST fail the request."
+  }, {
+    "@id" : "_:t129",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-contenttype"
+    },
+    "td:includesText" : "LDP servers SHOULD use the Content-Type request header to determine the representation format when the request has an entity body."
+  }, {
+    "@id" : "_:t130",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpic-indirectmbr"
+    },
+    "td:includesText" : "LDP Indirect Containers MUST contain exactly one triple whose subject is the LDPC URI, whose predicate is ldp:insertedContentRelation, and whose object ICR describes how the member-derived-URI in the container's membership triples is chosen."
+  }, {
+    "@id" : "_:t131",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-precond"
+    },
+    "td:includesText" : "LDP servers MUST respond with status code 412 (Condition Failed) if ETags fail to match when there are no other errors with the request [HTTP11]. LDP servers that require conditional requests MUST respond with status code 428 (Precondition Required) when the absence of a precondition is the only reason for rejecting the request [RFC6585]."
+  }, {
+    "@id" : "_:t132",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-precond"
+    },
+    "td:includesText" : "LDP clients SHOULD use the HTTP If-Match header and HTTP ETags to ensure it isn’t modifying a resource that has changed since the client last retrieved its representation. LDP servers SHOULD require the HTTP If-Match header and HTTP ETags to detect collisions."
+  }, {
+    "@id" : "_:t133",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-contenttype"
+    },
+    "td:includesText" : "LDP servers SHOULD use the Content-Type request header to determine the representation format when the request has an entity body."
+  }, {
+    "@id" : "_:t134",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-head-must"
+    },
+    "td:includesText" : "LDP servers MUST support the HTTP HEAD method. "
+  }, {
+    "@id" : "_:t139",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-put-failed"
+    },
+    "td:includesText" : "LDP servers SHOULD 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 section 4.2.1 General."
+  }, {
+    "@id" : "_:t14",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-http"
+    },
+    "td:includesText" : "LDP servers MUST at least be HTTP/1.1 conformant servers [HTTP11]."
+  }, {
+    "@id" : "_:t142",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-acceptposthdr"
+    },
+    "td:includesText" : "LDP servers that support POST MUST include an Accept-Post response header on HTTP OPTIONS responses, listing post document media type(s) supported by the server."
+  }, {
+    "@id" : "_:t145",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-dontreuseuris"
+    },
+    "td:includesText" : "LDP servers that allow member creation via POST SHOULD NOT re-use URIs."
+  }, {
+    "@id" : "_:t148",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-createbins"
+    },
+    "td:includesText" : "LDP servers may accept an HTTP POST of non-RDF representations (LDP-NRs) for creation of any kind of resource, for example binary resources."
+  }, {
+    "@id" : "_:t149",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-get-options"
+    },
+    "td:includesText" : "LDP servers MUST support the HTTP response headers defined in section 4.2.8 HTTP OPTIONS. "
+  }, {
+    "@id" : "_:t150",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-gen-atleast1rdftype"
+    },
+    "td:includesText" : "LDP-RSs representations SHOULD have at least one rdf:type set explicitly. This makes the representations much more useful to client applications that don’t support inferencing."
+  }, {
+    "@id" : "_:t151",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-put-mbrprops"
+    },
+    "td:includesText" : "LDP servers SHOULD NOT allow HTTP PUT to update an LDPC’s containment triples; if the server receives such a request, it SHOULD respond with a 409 (Conflict) status code."
+  }, {
+    "@id" : "_:t152",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-cli-preservetriples"
+    },
+    "td:includesText" : "A LDP client MUST preserve all triples retrieved from an LDP-RS using HTTP GET that it doesn’t change whether it understands the predicates or not, when its intent is to perform an update using HTTP PUT. The use of HTTP PATCH instead of HTTP PUT for update avoids this burden for clients [RFC5789]. "
+  }, {
+    "@id" : "_:t153",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-mincontraints"
+    },
+    "td:includesText" : "LDP servers SHOULD 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 LDPRs. LDP servers expose these application-specific constraints as described in section 4.2.1 General."
+  }, {
+    "@id" : "_:t156",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-rdftype"
+    },
+    "td:includesText" : "The representation of a LDP-RS MAY have an rdf:type of ldp:RDFSource for Linked Data Platform RDF Source."
+  }, {
+    "@id" : "_:t161",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-http"
+    },
+    "td:includesText" : "LDP servers MUST at least be HTTP/1.1 conformant servers [HTTP11]."
+  }, {
+    "@id" : "_:t162",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-head-must"
+    },
+    "td:includesText" : "LDP servers MUST support the HTTP HEAD method. "
+  }, {
+    "@id" : "_:t165",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-cli-hints-ignorable"
+    },
+    "td:includesText" : "LDP clients MUST be capable of processing responses formed by an LDP server that ignores hints, including LDP-defined hints."
+  }, {
+    "@id" : "_:t170",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-gen-noinferencing"
+    },
+    "td:includesText" : "LDP servers MUST NOT 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 [rdf11-concepts]. The practical implication is that all content defined by LDP must be explicitly represented, unless noted otherwise within this document."
+  }, {
+    "@id" : "_:t173",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-put-servermanagedprops"
+    },
+    "td:includesText" : "If an otherwise valid HTTP PUT request is received that attempts to change properties the server does not allow clients to modify, LDP servers MUST respond with a 4xx range status code (typically 409 Conflict)"
+  }, {
+    "@id" : "_:t174",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-get-turtle"
+    },
+    "td:includesText" : "LDP servers must provide a text/turtle representation of the requested LDP-RS whenever HTTP content negotiation does not force another outcome [turtle]. In other words, if the server receives a GET request whose Request-URI identifies a LDP-RS, and either text/turtle has the highest relative quality factor (q= value) in the Accept request header or that header is absent, then an LDP server has to respond with Turtle."
+  }, {
+    "@id" : "_:t179",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-get-turtle"
+    },
+    "td:includesText" : "LDP servers must provide a text/turtle representation of the requested LDP-RS whenever HTTP content negotiation does not force another outcome [turtle]. In other words, if the server receives a GET request whose Request-URI identifies a LDP-RS, and either text/turtle has the highest relative quality factor (q= value) in the Accept request header or that header is absent, then an LDP server has to respond with Turtle."
+  }, {
+    "@id" : "_:t186",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-dontreuseuris"
+    },
+    "td:includesText" : "LDP servers that allow member creation via POST SHOULD NOT re-use URIs."
+  }, {
+    "@id" : "_:t187",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpdc-containtriples"
+    },
+    "td:includesText" : "Each LDP Direct Container representation must contain exactly one triple whose subject is the LDPC URI, and whose predicate is either ldp:hasMemberRelation or ldp:isMemberOfRelation. The object of the triple is constrained by other sections, such as ldp:hasMemberRelation or ldp:isMemberOfRelation, based on the membership triple pattern used by the container."
+  }, {
+    "@id" : "_:t188",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-serverassignuri"
+    },
+    "td:includesText" : "LDP servers SHOULD assign the URI for the resource to be created using server application specific rules in the absence of a client hint."
+  }, {
+    "@id" : "_:t189",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-put-failed"
+    },
+    "td:includesText" : "If an otherwise valid HTTP PUT request is received that contains properties the server chooses not to persist, e.g. unknown content, LDP servers MUST respond with an appropriate 4xx range status code [HTTP11]."
+  }, {
+    "@id" : "_:t190",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-options-must"
+    },
+    "td:includesText" : "LDP servers MUST support the HTTP OPTIONS method. "
+  }, {
+    "@id" : "_:t199",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-pubclireqs"
+    },
+    "td:includesText" : "LDP servers MUST publish any constraints on LDP clients’ ability to create or update LDPRs, by adding a Link header with rel='describedby' [RFC5988] to all responses to requests which fail due to violation of those constraints."
+  }, {
+    "@id" : "_:t202",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-cli-typeschange"
+    },
+    "td:includesText" : "In the absence of special knowledge of the application or domain, LDP clients MUST assume that the rdf:type values of a given LDP-RS can change over time."
+  }, {
+    "@id" : "_:t203",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-gen-noinferencing"
+    },
+    "td:includesText" : "LDP servers MUST NOT 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 [rdf11-concepts]. The practical implication is that all content defined by LDP must be explicitly represented, unless noted otherwise within this document."
+  }, {
+    "@id" : "_:t204",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-gen-rdf"
+    },
+    "td:includesText" : "LDP servers MUST provide an RDF representation for LDP-RSs. The HTTP Request-URI of the LDP-RS is typically the subject of most triples in the response."
+  }, {
+    "@id" : "_:t205",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-slug"
+    },
+    "td:includesText" : "LDP servers MAY allow clients to suggest the URI for a resource created through POST, using the HTTP Slug header as defined in [RFC5023]. 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."
+  }, {
+    "@id" : "_:t206",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpdc-del-contremovesmbrtriple"
+    },
+    "td:includesText" : "When an LDPR identified by the object of a membership triple which was originally created by the LDP-DC is deleted, the LDPC server MUST also remove the corresponding membership triple."
+  }, {
+    "@id" : "_:t217",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-get-jsonld"
+    },
+    "td:includesText" : "LDP servers SHOULD offer a application/ld+json representation of the requested LDP-RS [JSON-LD]. "
+  }, {
+    "@id" : "_:t222",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-put-servermanagedprops"
+    },
+    "td:includesText" : "If an otherwise valid HTTP PUT request is received that attempts to change properties the server does not allow clients to modify, LDP servers MUST respond with a 4xx range status code (typically 409 Conflict)"
+  }, {
+    "@id" : "_:t223",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-simpleupdate"
+    },
+    "td:includesText" : "LDP servers SHOULD allow clients to update resources without requiring detailed knowledge of server-specific constraints. This is a consequence of the requirement to enable simple creation and modification of LDPRs."
+  }, {
+    "@id" : "_:t226",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-createdmbr-contains"
+    },
+    "td:includesText" : "When a successful HTTP POST request to an LDPC results in the creation of an LDPR, a containment triple MUST be added to the state of LDPC."
+  }, {
+    "@id" : "_:t227",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-http"
+    },
+    "td:includesText" : "LDP servers MUST at least be HTTP/1.1 conformant servers [HTTP11]."
+  }, {
+    "@id" : "_:t23",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-get-options"
+    },
+    "td:includesText" : "LDP servers MUST support the HTTP response headers defined in section 4.2.8 HTTP OPTIONS. "
+  }, {
+    "@id" : "_:t234",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-createbins"
+    },
+    "td:includesText" : "LDP servers may accept an HTTP POST of non-RDF representations (LDP-NRs) for creation of any kind of resource, for example binary resources."
+  }, {
+    "@id" : "_:t235",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-create"
+    },
+    "td:includesText" : "LDP servers MAY choose to allow the creation of new resources using HTTP PUT."
+  }, {
+    "@id" : "_:t236",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-put-mbrprops"
+    },
+    "td:includesText" : "LDP servers SHOULD NOT allow HTTP PUT to update an LDPC’s containment triples; if the server receives such a request, it SHOULD respond with a 409 (Conflict) status code."
+  }, {
+    "@id" : "_:t237",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-put-create"
+    },
+    "td:includesText" : "LDP servers that allow LDPR creation via PUT SHOULD NOT re-use URIs. For RDF representations (LDP-RSs),the created resource can be thought of as an RDF named graph [rdf11-concepts]."
+  }, {
+    "@id" : "_:t238",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-precond"
+    },
+    "td:includesText" : "LDP servers MUST respond with status code 412 (Condition Failed) if ETags fail to match when there are no other errors with the request [HTTP11]. LDP servers that require conditional requests MUST respond with status code 428 (Precondition Required) when the absence of a precondition is the only reason for rejecting the request [RFC6585]."
+  }, {
+    "@id" : "_:t239",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-etags"
+    },
+    "td:includesText" : "LDP server responses MUST use entity tags (either weak or strong ones) as response ETag header values."
+  }, {
+    "@id" : "_:t242",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpnr-are-ldpr"
+    },
+    "td:includesText" : "Each LDP Non-RDF Source must also be a conforming LDP Resource. LDP Non-RDF Sources may not be able to fully express their state using RDF."
+  }, {
+    "@id" : "_:t245",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-etags"
+    },
+    "td:includesText" : "LDP server responses MUST use entity tags (either weak or strong ones) as response ETag header values."
+  }, {
+    "@id" : "_:t248",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-nordfcontainertypes"
+    },
+    "td:includesText" : "LDPC representations SHOULD NOT use RDF container types rdf:Bag, rdf:Seq or rdf:List."
+  }, {
+    "@id" : "_:t251",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-rdftype"
+    },
+    "td:includesText" : "The representation of a LDP-RS MAY have an rdf:type of ldp:RDFSource for Linked Data Platform RDF Source."
+  }, {
+    "@id" : "_:t252",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-defbaseuri"
+    },
+    "td:includesText" : "LDP servers MUST assign the default base-URI for [RFC3987] relative-URI resolution to be the HTTP Request-URI when the resource already exists, and to the URI of the created resource when the request results in the creation of a new resource."
+  }, {
+    "@id" : "_:t255",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-defbaseuri"
+    },
+    "td:includesText" : "LDP servers MUST assign the default base-URI for [RFC3987] relative-URI resolution to be the HTTP Request-URI when the resource already exists, and to the URI of the created resource when the request results in the creation of a new resource."
+  }, {
+    "@id" : "_:t26",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-options-must"
+    },
+    "td:includesText" : "LDP servers MUST support the HTTP OPTIONS method. "
+  }, {
+    "@id" : "_:t260",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-replaceall"
+    },
+    "td:includesText" : "If a HTTP PUT is accepted on an existing resource, LDP servers MUST replace the entire persistent state of the identified resource with the entity representation in the body of the request."
+  }, {
+    "@id" : "_:t261",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-linktypehdr"
+    },
+    "td:includesText" : "LDP servers exposing LDPCs MUST advertise their LDP support by exposing a HTTP Link header with a target URI matching the type of container (see below) the server supports, and a link relation type of type (that is, rel='type') in all responses to requests made to the LDPC's HTTP Request-URI."
+  }, {
+    "@id" : "_:t262",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-del-contremovesconttriple"
+    },
+    "td:includesText" : "When an LDPR identified by the object of a containment triple is deleted, the LDPC server MUST also remove the LDPR from the containing LDPC by removing the corresponding containment triple."
+  }, {
+    "@id" : "_:t265",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-gen-reusevocabsuchas"
+    },
+    "td:includesText" : "LDP-RSs predicates SHOULD use standard vocabularies such as Dublin Core [DC-TERMS], RDF [rdf11-concepts] and RDF Schema [rdf-schema], whenever possible."
+  }, {
+    "@id" : "_:t266",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-put-failed"
+    },
+    "td:includesText" : "LDP servers SHOULD 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 section 4.2.1 General."
+  }, {
+    "@id" : "_:t267",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-put-failed"
+    },
+    "td:includesText" : "If an otherwise valid HTTP PUT request is received that contains properties the server chooses not to persist, e.g. unknown content, LDP servers MUST respond with an appropriate 4xx range status code [HTTP11]."
+  }, {
+    "@id" : "_:t268",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-gen-reusevocabsuchas"
+    },
+    "td:includesText" : "LDP-RSs predicates SHOULD use standard vocabularies such as Dublin Core [DC-TERMS], RDF [rdf11-concepts] and RDF Schema [rdf-schema], whenever possible."
+  }, {
+    "@id" : "_:t269",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-precond"
+    },
+    "td:includesText" : "LDP clients SHOULD use the HTTP If-Match header and HTTP ETags to ensure it isn’t modifying a resource that has changed since the client last retrieved its representation. LDP servers SHOULD require the HTTP If-Match header and HTTP ETags to detect collisions."
+  }, {
+    "@id" : "_:t27",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-etags"
+    },
+    "td:includesText" : "LDP server responses MUST use entity tags (either weak or strong ones) as response ETag header values."
+  }, {
+    "@id" : "_:t270",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-cli-hints-ignorable"
+    },
+    "td:includesText" : "LDP clients MUST be capable of processing responses formed by an LDP server that ignores hints, including LDP-defined hints."
+  }, {
+    "@id" : "_:t273",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-precond"
+    },
+    "td:includesText" : "LDP servers MUST respond with status code 412 (Condition Failed) if ETags fail to match when there are no other errors with the request [HTTP11]. LDP servers that require conditional requests MUST respond with status code 428 (Precondition Required) when the absence of a precondition is the only reason for rejecting the request [RFC6585]."
+  }, {
+    "@id" : "_:t278",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-createbinlinkmetahdr"
+    },
+    "td:includesText" : "Upon successful creation of an LDP-NR (HTTP status code of 201-Created and URI indicated by Location response header), LDP servers may create an associated LDP-RS to contain data about the newly created LDP-NR. If a LDP server creates this associated LDP-RS it must indicate its location on the HTTP response using the HTTP Link response header with link relation describedby and href to be the URI of the associated LDP-RS resource."
+  }, {
+    "@id" : "_:t279",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-createrdf"
+    },
+    "td:includesText" : "LDP servers that successfully create a resource from a RDF representation in the request entity body MUST honor the client's requested interaction model(s). The created resource can be thought of as an RDF named graph [rdf11-concepts]. If any model cannot be honored, the server MUST fail the request."
+  }, {
+    "@id" : "_:t28",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-pubclireqs"
+    },
+    "td:includesText" : "LDP servers MUST publish any constraints on LDP clients’ ability to create or update LDPRs, by adding a Link header with rel='describedby' [RFC5988] to all responses to requests which fail due to violation of those constraints."
+  }, {
+    "@id" : "_:t282",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-createrdf"
+    },
+    "td:includesText" : "LDP servers that successfully create a resource from a RDF representation in the request entity body MUST honor the client's requested interaction model(s). The created resource can be thought of as an RDF named graph [rdf11-concepts]. If any model cannot be honored, the server MUST fail the request."
+  }, {
+    "@id" : "_:t283",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-turtle"
+    },
+    "td:includesText" : "LDP servers MUST accept a request entity body with a request header of Content-Type with value of text/turtle [turtle]."
+  }, {
+    "@id" : "_:t284",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-prefer"
+    },
+    "td:includesText" : "LDP servers SHOULD respect all of a client's LDP-defined hints, for example which subsets of LDP-defined state the client is interested in processing, to influence the set of triples returned in representations of an LDPC, particularly for large LDPCs. See also [LDP-PAGING]."
+  }, {
+    "@id" : "_:t285",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-createrdf"
+    },
+    "td:includesText" : "LDP servers that successfully create a resource from a RDF representation in the request entity body MUST honor the client's requested interaction model(s). The created resource can be thought of as an RDF named graph [rdf11-concepts]. If any model cannot be honored, the server MUST fail the request."
+  }, {
+    "@id" : "_:t286",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-precond"
+    },
+    "td:includesText" : "LDP servers MUST respond with status code 412 (Condition Failed) if ETags fail to match when there are no other errors with the request [HTTP11]. LDP servers that require conditional requests MUST respond with status code 428 (Precondition Required) when the absence of a precondition is the only reason for rejecting the request [RFC6585]."
+  }, {
+    "@id" : "_:t287",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-linktypehdr"
+    },
+    "td:includesText" : "LDP servers exposing LDPRs MUST advertise their LDP support by exposing a HTTP Link header with a target URI of http://www.w3.org/ns/ldp#Resource, and a link relation type of type (that is, rel='type') in all responses to requests made to the LDPR's HTTP Request-URI."
+  }, {
+    "@id" : "_:t29",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-contenttype"
+    },
+    "td:includesText" : "LDP servers SHOULD use the Content-Type request header to determine the representation format when the request has an entity body."
+  }, {
+    "@id" : "_:t290",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-gen-rdf"
+    },
+    "td:includesText" : "LDP servers MUST provide an RDF representation for LDP-RSs. The HTTP Request-URI of the LDP-RS is typically the subject of most triples in the response."
+  }, {
+    "@id" : "_:t291",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-precond"
+    },
+    "td:includesText" : "LDP servers MUST respond with status code 412 (Condition Failed) if ETags fail to match when there are no other errors with the request [HTTP11]. LDP servers that require conditional requests MUST respond with status code 428 (Precondition Required) when the absence of a precondition is the only reason for rejecting the request [RFC6585]."
+  }, {
+    "@id" : "_:t298",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-precond"
+    },
+    "td:includesText" : "LDP servers MUST respond with status code 412 (Condition Failed) if ETags fail to match when there are no other errors with the request [HTTP11]. LDP servers that require conditional requests MUST respond with status code 428 (Precondition Required) when the absence of a precondition is the only reason for rejecting the request [RFC6585]."
+  }, {
+    "@id" : "_:t299",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-dontreuseuris"
+    },
+    "td:includesText" : "LDP servers that allow member creation via POST SHOULD NOT re-use URIs."
+  }, {
+    "@id" : "_:t3",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-options-must"
+    },
+    "td:includesText" : "LDP servers MUST support the HTTP OPTIONS method. "
+  }, {
+    "@id" : "_:t300",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-etags"
+    },
+    "td:includesText" : "LDP server responses MUST use entity tags (either weak or strong ones) as response ETag header values."
+  }, {
+    "@id" : "_:t301",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-cli-preservetriples"
+    },
+    "td:includesText" : "A LDP client MUST preserve all triples retrieved from an LDP-RS using HTTP GET that it doesn’t change whether it understands the predicates or not, when its intent is to perform an update using HTTP PUT. The use of HTTP PATCH instead of HTTP PUT for update avoids this burden for clients [RFC5789]. "
+  }, {
+    "@id" : "_:t302",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-cli-openpreds"
+    },
+    "td:includesText" : "LDP clients SHOULD always assume that the set of predicates for a LDP-RS 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 LDP-RS is not limited to any pre-defined set."
+  }, {
+    "@id" : "_:t305",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-put-failed"
+    },
+    "td:includesText" : "LDP servers SHOULD 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 section 4.2.1 General."
+  }, {
+    "@id" : "_:t31",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-simpleupdate"
+    },
+    "td:includesText" : "LDP servers SHOULD allow clients to update resources without requiring detailed knowledge of server-specific constraints. This is a consequence of the requirement to enable simple creation and modification of LDPRs."
+  }, {
+    "@id" : "_:t314",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-create"
+    },
+    "td:includesText" : "LDP servers MAY choose to allow the creation of new resources using HTTP PUT."
+  }, {
+    "@id" : "_:t317",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-cli-preservetriples"
+    },
+    "td:includesText" : "A LDP client MUST preserve all triples retrieved from an LDP-RS using HTTP GET that it doesn’t change whether it understands the predicates or not, when its intent is to perform an update using HTTP PUT. The use of HTTP PATCH instead of HTTP PUT for update avoids this burden for clients [RFC5789]. "
+  }, {
+    "@id" : "_:t319",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-etags"
+    },
+    "td:includesText" : "LDP server responses MUST use entity tags (either weak or strong ones) as response ETag header values."
+  }, {
+    "@id" : "_:t32",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-nordfcontainertypes"
+    },
+    "td:includesText" : "LDPC representations SHOULD NOT use RDF container types rdf:Bag, rdf:Seq or rdf:List."
+  }, {
+    "@id" : "_:t320",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-jsonld"
+    },
+    "td:includesText" : "LDP servers SHOULD accept a request entity body with a request header of Content-Type with value of application/ld+json [JSON-LD]."
+  }, {
+    "@id" : "_:t321",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-gen-atleast1rdftype"
+    },
+    "td:includesText" : "LDP-RSs representations SHOULD have at least one rdf:type set explicitly. This makes the representations much more useful to client applications that don’t support inferencing."
+  }, {
+    "@id" : "_:t322",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-pubclireqs"
+    },
+    "td:includesText" : "LDP servers MUST publish any constraints on LDP clients’ ability to create or update LDPRs, by adding a Link header with rel='describedby' [RFC5988] to all responses to requests which fail due to violation of those constraints."
+  }, {
+    "@id" : "_:t323",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-cli-preservetriples"
+    },
+    "td:includesText" : "A LDP client MUST preserve all triples retrieved from an LDP-RS using HTTP GET that it doesn’t change whether it understands the predicates or not, when its intent is to perform an update using HTTP PUT. The use of HTTP PATCH instead of HTTP PUT for update avoids this burden for clients [RFC5789]. "
+  }, {
+    "@id" : "_:t324",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-linktypehdr"
+    },
+    "td:includesText" : "LDP servers exposing LDPRs MUST advertise their LDP support by exposing a HTTP Link header with a target URI of http://www.w3.org/ns/ldp#Resource, and a link relation type of type (that is, rel='type') in all responses to requests made to the LDPR's HTTP Request-URI."
+  }, {
+    "@id" : "_:t329",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldp-cli-multitype"
+    },
+    "td:includesText" : "In the absence of special knowledge of the application or domain, LDP clients MUST assume that any LDP-RS can have multiple values for rdf:type."
+  }, {
+    "@id" : "_:t33",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-patch-acceptpatch"
+    },
+    "td:includesText" : "LDP servers that support PATCH MUST include an Accept-Patch HTTP response header [RFC5789] on HTTP OPTIONS requests, listing patch document media type(s) supported by the server. "
+  }, {
+    "@id" : "_:t334",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-createdmbr-contains"
+    },
+    "td:includesText" : "When a successful HTTP POST request to an LDPC results in the creation of an LDPR, a containment triple MUST be added to the state of LDPC."
+  }, {
+    "@id" : "_:t337",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-put-servermanagedprops"
+    },
+    "td:includesText" : "If an otherwise valid HTTP PUT request is received that attempts to change properties the server does not allow clients to modify, LDP servers MUST respond with a 4xx range status code (typically 409 Conflict)"
+  }, {
+    "@id" : "_:t338",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-mincontraints"
+    },
+    "td:includesText" : "LDP servers SHOULD 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 LDPRs. LDP servers expose these application-specific constraints as described in section 4.2.1 General."
+  }, {
+    "@id" : "_:t339",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-put-servermanagedprops"
+    },
+    "td:includesText" : "LDP servers SHOULD 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."
+  }, {
+    "@id" : "_:t340",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-options-allow"
+    },
+    "td:includesText" : "LDP servers MUST indicate their support for HTTP Methods by responding to a HTTP OPTIONS request on the LDPR’s URL with the HTTP Method tokens in the HTTP response header Allow. "
+  }, {
+    "@id" : "_:t341",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-head-must"
+    },
+    "td:includesText" : "LDP servers MUST support the HTTP HEAD method. "
+  }, {
+    "@id" : "_:t344",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-replaceall"
+    },
+    "td:includesText" : "If a HTTP PUT is accepted on an existing resource, LDP servers MUST replace the entire persistent state of the identified resource with the entity representation in the body of the request."
+  }, {
+    "@id" : "_:t345",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-turtle"
+    },
+    "td:includesText" : "LDP servers MUST accept a request entity body with a request header of Content-Type with value of text/turtle [turtle]."
+  }, {
+    "@id" : "_:t351",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-precond"
+    },
+    "td:includesText" : "LDP clients SHOULD use the HTTP If-Match header and HTTP ETags to ensure it isn’t modifying a resource that has changed since the client last retrieved its representation. LDP servers SHOULD require the HTTP If-Match header and HTTP ETags to detect collisions."
+  }, {
+    "@id" : "_:t352",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-precond"
+    },
+    "td:includesText" : "LDP servers MUST respond with status code 412 (Condition Failed) if ETags fail to match when there are no other errors with the request [HTTP11]. LDP servers that require conditional requests MUST respond with status code 428 (Precondition Required) when the absence of a precondition is the only reason for rejecting the request [RFC6585]."
+  }, {
+    "@id" : "_:t353",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-get-options"
+    },
+    "td:includesText" : "LDP servers MUST support the HTTP response headers defined in section 4.2.8 HTTP OPTIONS. "
+  }, {
+    "@id" : "_:t354",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-http"
+    },
+    "td:includesText" : "LDP servers MUST at least be HTTP/1.1 conformant servers [HTTP11]."
+  }, {
+    "@id" : "_:t355",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-patch-req"
+    },
+    "td:includesText" : "LDP servers are RECOMMENDED to support HTTP PATCH as the preferred method for updating an LDPC's empty-container triples. "
+  }, {
+    "@id" : "_:t356",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-cli-can-hint"
+    },
+    "td:includesText" : "LDP clients MAY provide LDP-defined hints that allow servers to optimize the content of responses. section 7.2 Preferences on the Prefer Request Header defines hints that apply to LDP-RSs. "
+  }, {
+    "@id" : "_:t36",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-nordfcontainertypes"
+    },
+    "td:includesText" : "LDPC representations SHOULD NOT use RDF container types rdf:Bag, rdf:Seq or rdf:List."
+  }, {
+    "@id" : "_:t361",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-patch-req"
+    },
+    "td:includesText" : "LDP servers are RECOMMENDED to support HTTP PATCH as the preferred method for updating an LDPC's empty-container triples. "
+  }, {
+    "@id" : "_:t370",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-patch-acceptpatch"
+    },
+    "td:includesText" : "LDP servers that support PATCH MUST include an Accept-Patch HTTP response header [RFC5789] on HTTP OPTIONS requests, listing patch document media type(s) supported by the server. "
+  }, {
+    "@id" : "_:t373",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-get-turtle"
+    },
+    "td:includesText" : "LDP servers must provide a text/turtle representation of the requested LDP-RS whenever HTTP content negotiation does not force another outcome [turtle]. In other words, if the server receives a GET request whose Request-URI identifies a LDP-RS, and either text/turtle has the highest relative quality factor (q= value) in the Accept request header or that header is absent, then an LDP server has to respond with Turtle."
+  }, {
+    "@id" : "_:t374",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-pubclireqs"
+    },
+    "td:includesText" : "LDP servers MUST publish any constraints on LDP clients’ ability to create or update LDPRs, by adding a Link header with rel='describedby' [RFC5988] to all responses to requests which fail due to violation of those constraints."
+  }, {
+    "@id" : "_:t377",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-pubclireqs"
+    },
+    "td:includesText" : "LDP servers MUST publish any constraints on LDP clients’ ability to create or update LDPRs, by adding a Link header with rel='describedby' [RFC5988] to all responses to requests which fail due to violation of those constraints."
+  }, {
+    "@id" : "_:t381",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-http"
+    },
+    "td:includesText" : "LDP servers MUST at least be HTTP/1.1 conformant servers [HTTP11]."
+  }, {
+    "@id" : "_:t387",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-linktypehdr"
+    },
+    "td:includesText" : "LDP servers exposing LDPCs MUST advertise their LDP support by exposing a HTTP Link header with a target URI matching the type of container (see below) the server supports, and a link relation type of type (that is, rel='type') in all responses to requests made to the LDPC's HTTP Request-URI."
+  }, {
+    "@id" : "_:t388",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-dontreuseuris"
+    },
+    "td:includesText" : "LDP servers that allow member creation via POST SHOULD NOT re-use URIs."
+  }, {
+    "@id" : "_:t389",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-precond"
+    },
+    "td:includesText" : "LDP servers MUST respond with status code 412 (Condition Failed) if ETags fail to match when there are no other errors with the request [HTTP11]. LDP servers that require conditional requests MUST respond with status code 428 (Precondition Required) when the absence of a precondition is the only reason for rejecting the request [RFC6585]."
+  }, {
+    "@id" : "_:t393",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-precond"
+    },
+    "td:includesText" : "LDP servers MUST respond with status code 412 (Condition Failed) if ETags fail to match when there are no other errors with the request [HTTP11]. LDP servers that require conditional requests MUST respond with status code 428 (Precondition Required) when the absence of a precondition is the only reason for rejecting the request [RFC6585]."
+  }, {
+    "@id" : "_:t395",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-gen-atleast1rdftype"
+    },
+    "td:includesText" : "LDP-RSs representations SHOULD have at least one rdf:type set explicitly. This makes the representations much more useful to client applications that don’t support inferencing."
+  }, {
+    "@id" : "_:t396",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-patch-req"
+    },
+    "td:includesText" : "LDP servers are RECOMMENDED to support HTTP PATCH as the preferred method for updating an LDPC's empty-container triples. "
+  }, {
+    "@id" : "_:t397",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-slug"
+    },
+    "td:includesText" : "LDP servers MAY allow clients to suggest the URI for a resource created through POST, using the HTTP Slug header as defined in [RFC5023]. 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."
+  }, {
+    "@id" : "_:t399",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldp-cli-multitype"
+    },
+    "td:includesText" : "In the absence of special knowledge of the application or domain, LDP clients MUST assume that any LDP-RS can have multiple values for rdf:type."
+  }, {
+    "@id" : "_:t401",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-prefer"
+    },
+    "td:includesText" : "LDP servers SHOULD respect all of a client's LDP-defined hints, for example which subsets of LDP-defined state the client is interested in processing, to influence the set of triples returned in representations of an LDPC, particularly for large LDPCs. See also [LDP-PAGING]."
+  }, {
+    "@id" : "_:t405",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpic-post-indirectmbrrel"
+    },
+    "td:includesText" : "LDPCs whose ldp:insertedContentRelation triple has an object other than ldp:MemberSubject and that create new resources MUST add a triple to the container whose subject is the container's URI, whose predicate is ldp:contains, and whose object is the newly created resource's URI (which will be different from the member-derived URI in this case). This ldp:contains triple can be the only link from the container to the newly created resource in certain cases."
+  }, {
+    "@id" : "_:t406",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-patch-acceptpatch"
+    },
+    "td:includesText" : "LDP servers that support PATCH MUST include an Accept-Patch HTTP response header [RFC5789] on HTTP OPTIONS requests, listing patch document media type(s) supported by the server. "
+  }, {
+    "@id" : "_:t410",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-rdfnullrel"
+    },
+    "td:includesText" : "In RDF representations, LDP servers MUST interpret the null relative URI for the subject of triples in the LDPR representation in the request entity body as referring to the entity in the request body. Commonly, that entity is the model for the “to be created” LDPR, so triples whose subject is the null relative URI will usually result in triples in the created resource whose subject is the created resource."
+  }, {
+    "@id" : "_:t412",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-put-servermanagedprops"
+    },
+    "td:includesText" : "If an otherwise valid HTTP PUT request is received that attempts to change properties the server does not allow clients to modify, LDP servers MUST respond with a 4xx range status code (typically 409 Conflict)"
+  }, {
+    "@id" : "_:t413",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-linktypehdr"
+    },
+    "td:includesText" : "LDP servers exposing LDPRs MUST advertise their LDP support by exposing a HTTP Link header with a target URI of http://www.w3.org/ns/ldp#Resource, and a link relation type of type (that is, rel='type') in all responses to requests made to the LDPR's HTTP Request-URI."
+  }, {
+    "@id" : "_:t415",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-get-jsonld"
+    },
+    "td:includesText" : "LDP servers SHOULD offer a application/ld+json representation of the requested LDP-RS [JSON-LD]. "
+  }, {
+    "@id" : "_:t417",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-gen-reusevocab"
+    },
+    "td:includesText" : "LDP-RSs SHOULD 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."
+  }, {
+    "@id" : "_:t418",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-http"
+    },
+    "td:includesText" : "LDP servers MUST at least be HTTP/1.1 conformant servers [HTTP11]."
+  }, {
+    "@id" : "_:t420",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-precond"
+    },
+    "td:includesText" : "LDP servers MUST respond with status code 412 (Condition Failed) if ETags fail to match when there are no other errors with the request [HTTP11]. LDP servers that require conditional requests MUST respond with status code 428 (Precondition Required) when the absence of a precondition is the only reason for rejecting the request [RFC6585]."
+  }, {
+    "@id" : "_:t421",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-createdmbr-contains"
+    },
+    "td:includesText" : "When a successful HTTP POST request to an LDPC results in the creation of an LDPR, a containment triple MUST be added to the state of LDPC."
+  }, {
+    "@id" : "_:t422",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-turtle"
+    },
+    "td:includesText" : "LDP servers MUST accept a request entity body with a request header of Content-Type with value of text/turtle [turtle]."
+  }, {
+    "@id" : "_:t423",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-precond"
+    },
+    "td:includesText" : "LDP clients SHOULD use the HTTP If-Match header and HTTP ETags to ensure it isn’t modifying a resource that has changed since the client last retrieved its representation. LDP servers SHOULD require the HTTP If-Match header and HTTP ETags to detect collisions."
+  }, {
+    "@id" : "_:t427",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-defbaseuri"
+    },
+    "td:includesText" : "LDP servers MUST assign the default base-URI for [RFC3987] relative-URI resolution to be the HTTP Request-URI when the resource already exists, and to the URI of the created resource when the request results in the creation of a new resource."
+  }, {
+    "@id" : "_:t429",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-put-servermanagedprops"
+    },
+    "td:includesText" : "LDP servers SHOULD 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."
+  }, {
+    "@id" : "_:t43",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-linktypehdr"
+    },
+    "td:includesText" : "LDP servers exposing LDPCs MUST advertise their LDP support by exposing a HTTP Link header with a target URI matching the type of container (see below) the server supports, and a link relation type of type (that is, rel='type') in all responses to requests made to the LDPC's HTTP Request-URI."
+  }, {
+    "@id" : "_:t430",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-mincontraints"
+    },
+    "td:includesText" : "LDP servers SHOULD 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 LDPRs. LDP servers expose these application-specific constraints as described in section 4.2.1 General."
+  }, {
+    "@id" : "_:t431",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-defbaseuri"
+    },
+    "td:includesText" : "LDP servers MUST assign the default base-URI for [RFC3987] relative-URI resolution to be the HTTP Request-URI when the resource already exists, and to the URI of the created resource when the request results in the creation of a new resource."
+  }, {
+    "@id" : "_:t432",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldp-cli-multitype"
+    },
+    "td:includesText" : "In the absence of special knowledge of the application or domain, LDP clients MUST assume that any LDP-RS can have multiple values for rdf:type."
+  }, {
+    "@id" : "_:t433",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-options-allow"
+    },
+    "td:includesText" : "LDP servers MUST indicate their support for HTTP Methods by responding to a HTTP OPTIONS request on the LDPR’s URL with the HTTP Method tokens in the HTTP response header Allow. "
+  }, {
+    "@id" : "_:t434",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-precond"
+    },
+    "td:includesText" : "LDP servers MUST respond with status code 412 (Condition Failed) if ETags fail to match when there are no other errors with the request [HTTP11]. LDP servers that require conditional requests MUST respond with status code 428 (Precondition Required) when the absence of a precondition is the only reason for rejecting the request [RFC6585]."
+  }, {
+    "@id" : "_:t441",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-jsonld"
+    },
+    "td:includesText" : "LDP servers SHOULD accept a request entity body with a request header of Content-Type with value of application/ld+json [JSON-LD]."
+  }, {
+    "@id" : "_:t442",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-http"
+    },
+    "td:includesText" : "LDP servers MUST at least be HTTP/1.1 conformant servers [HTTP11]."
+  }, {
+    "@id" : "_:t443",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-gen-reusevocab"
+    },
+    "td:includesText" : "LDP-RSs SHOULD 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."
+  }, {
+    "@id" : "_:t444",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpdc-indirectmbr-basic"
+    },
+    "td:includesText" : "LDP Direct Containers MUST behave as if they have a (LDPC URI, ldp:insertedContentRelation , ldp:MemberSubject) triple, but LDP imposes no requirement to materialize such a triple in the LDP-DC representation."
+  }, {
+    "@id" : "_:t445",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-cli-openpreds"
+    },
+    "td:includesText" : "LDP clients SHOULD always assume that the set of predicates for a LDP-RS 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 LDP-RS is not limited to any pre-defined set."
+  }, {
+    "@id" : "_:t450",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-rdfnullrel"
+    },
+    "td:includesText" : "In RDF representations, LDP servers MUST interpret the null relative URI for the subject of triples in the LDPR representation in the request entity body as referring to the entity in the request body. Commonly, that entity is the model for the “to be created” LDPR, so triples whose subject is the null relative URI will usually result in triples in the created resource whose subject is the created resource."
+  }, {
+    "@id" : "_:t452",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-precond"
+    },
+    "td:includesText" : "LDP servers MUST respond with status code 412 (Condition Failed) if ETags fail to match when there are no other errors with the request [HTTP11]. LDP servers that require conditional requests MUST respond with status code 428 (Precondition Required) when the absence of a precondition is the only reason for rejecting the request [RFC6585]."
+  }, {
+    "@id" : "_:t456",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-put-create"
+    },
+    "td:includesText" : "LDP servers that allow LDPR creation via PUT SHOULD NOT re-use URIs. For RDF representations (LDP-RSs),the created resource can be thought of as an RDF named graph [rdf11-concepts]."
+  }, {
+    "@id" : "_:t458",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-precond"
+    },
+    "td:includesText" : "LDP clients SHOULD use the HTTP If-Match header and HTTP ETags to ensure it isn’t modifying a resource that has changed since the client last retrieved its representation. LDP servers SHOULD require the HTTP If-Match header and HTTP ETags to detect collisions."
+  }, {
+    "@id" : "_:t459",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-rdftype"
+    },
+    "td:includesText" : "The representation of a LDP-RS MAY have an rdf:type of ldp:RDFSource for Linked Data Platform RDF Source."
+  }, {
+    "@id" : "_:t460",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-put-create"
+    },
+    "td:includesText" : "LDP servers that allow LDPR creation via PUT SHOULD NOT re-use URIs. For RDF representations (LDP-RSs),the created resource can be thought of as an RDF named graph [rdf11-concepts]."
+  }, {
+    "@id" : "_:t461",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-linktypehdr"
+    },
+    "td:includesText" : "LDP servers exposing LDPRs MUST advertise their LDP support by exposing a HTTP Link header with a target URI of http://www.w3.org/ns/ldp#Resource, and a link relation type of type (that is, rel='type') in all responses to requests made to the LDPR's HTTP Request-URI."
+  }, {
+    "@id" : "_:t462",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-cli-hints-ignorable"
+    },
+    "td:includesText" : "LDP clients MUST be capable of processing responses formed by an LDP server that ignores hints, including LDP-defined hints."
+  }, {
+    "@id" : "_:t468",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-gen-rdf"
+    },
+    "td:includesText" : "LDP servers MUST provide an RDF representation for LDP-RSs. The HTTP Request-URI of the LDP-RS is typically the subject of most triples in the response."
+  }, {
+    "@id" : "_:t469",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-put-servermanagedprops"
+    },
+    "td:includesText" : "LDP servers SHOULD 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."
+  }, {
+    "@id" : "_:t470",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-cli-can-hint"
+    },
+    "td:includesText" : "LDP clients MAY provide LDP-defined hints that allow servers to optimize the content of responses. section 7.2 Preferences on the Prefer Request Header defines hints that apply to LDP-RSs. "
+  }, {
+    "@id" : "_:t471",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-patch-acceptpatch"
+    },
+    "td:includesText" : "LDP servers that support PATCH MUST include an Accept-Patch HTTP response header [RFC5789] on HTTP OPTIONS requests, listing patch document media type(s) supported by the server. "
+  }, {
+    "@id" : "_:t473",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-get-turtle"
+    },
+    "td:includesText" : "LDP servers must provide a text/turtle representation of the requested LDP-RS whenever HTTP content negotiation does not force another outcome [turtle]. In other words, if the server receives a GET request whose Request-URI identifies a LDP-RS, and either text/turtle has the highest relative quality factor (q= value) in the Accept request header or that header is absent, then an LDP server has to respond with Turtle."
+  }, {
+    "@id" : "_:t474",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-etags"
+    },
+    "td:includesText" : "LDP server responses MUST use entity tags (either weak or strong ones) as response ETag header values."
+  }, {
+    "@id" : "_:t475",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-options-allow"
+    },
+    "td:includesText" : "LDP servers MUST indicate their support for HTTP Methods by responding to a HTTP OPTIONS request on the LDPR’s URL with the HTTP Method tokens in the HTTP response header Allow. "
+  }, {
+    "@id" : "_:t476",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-cli-openpreds"
+    },
+    "td:includesText" : "LDP clients SHOULD always assume that the set of predicates for a LDP-RS 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 LDP-RS is not limited to any pre-defined set."
+  }, {
+    "@id" : "_:t477",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpnr-type"
+    },
+    "td:includesText" : "LDP servers exposing an LDP Non-RDF Source may advertise this by exposing a HTTP Link header with a target URI of http://www.w3.org/ns/ldp#NonRDFSource, and a link relation type of type (that is, rel='type') in responses to requests made to the LDP-NR's HTTP Request-URI."
+  }, {
+    "@id" : "_:t478",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-replaceall"
+    },
+    "td:includesText" : "If a HTTP PUT is accepted on an existing resource, LDP servers MUST replace the entire persistent state of the identified resource with the entity representation in the body of the request."
+  }, {
+    "@id" : "_:t479",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-created201"
+    },
+    "td:includesText" : "LDPC clients SHOULD create member resources by submitting a representation as the entity body of the HTTP POST to a known LDPC."
+  }, {
+    "@id" : "_:t48",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-patch-acceptpatch"
+    },
+    "td:includesText" : "LDP servers that support PATCH MUST include an Accept-Patch HTTP response header [RFC5789] on HTTP OPTIONS requests, listing patch document media type(s) supported by the server. "
+  }, {
+    "@id" : "_:t480",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-jsonld"
+    },
+    "td:includesText" : "LDP servers SHOULD accept a request entity body with a request header of Content-Type with value of application/ld+json [JSON-LD]."
+  }, {
+    "@id" : "_:t481",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-prefer"
+    },
+    "td:includesText" : "LDP servers SHOULD respect all of a client's LDP-defined hints, for example which subsets of LDP-defined state the client is interested in processing, to influence the set of triples returned in representations of an LDPC, particularly for large LDPCs. See also [LDP-PAGING]."
+  }, {
+    "@id" : "_:t483",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-etags"
+    },
+    "td:includesText" : "LDP server responses MUST use entity tags (either weak or strong ones) as response ETag header values."
+  }, {
+    "@id" : "_:t484",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-put-servermanagedprops"
+    },
+    "td:includesText" : "LDP servers SHOULD 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."
+  }, {
+    "@id" : "_:t485",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-replaceall"
+    },
+    "td:includesText" : "If a HTTP PUT is accepted on an existing resource, LDP servers MUST replace the entire persistent state of the identified resource with the entity representation in the body of the request."
+  }, {
+    "@id" : "_:t486",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-get-jsonld"
+    },
+    "td:includesText" : "LDP servers SHOULD offer a application/ld+json representation of the requested LDP-RS [JSON-LD]. "
+  }, {
+    "@id" : "_:t487",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-gen-rdf"
+    },
+    "td:includesText" : "LDP servers MUST provide an RDF representation for LDP-RSs. The HTTP Request-URI of the LDP-RS is typically the subject of most triples in the response."
+  }, {
+    "@id" : "_:t488",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-pubclireqs"
+    },
+    "td:includesText" : "LDP servers MUST publish any constraints on LDP clients’ ability to create or update LDPRs, by adding a Link header with rel='describedby' [RFC5988] to all responses to requests which fail due to violation of those constraints."
+  }, {
+    "@id" : "_:t490",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-defbaseuri"
+    },
+    "td:includesText" : "LDP servers MUST assign the default base-URI for [RFC3987] relative-URI resolution to be the HTTP Request-URI when the resource already exists, and to the URI of the created resource when the request results in the creation of a new resource."
+  }, {
+    "@id" : "_:t491",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-gen-reusevocab"
+    },
+    "td:includesText" : "LDP-RSs SHOULD 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."
+  }, {
+    "@id" : "_:t492",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-defbaseuri"
+    },
+    "td:includesText" : "LDP servers MUST assign the default base-URI for [RFC3987] relative-URI resolution to be the HTTP Request-URI when the resource already exists, and to the URI of the created resource when the request results in the creation of a new resource."
+  }, {
+    "@id" : "_:t493",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-linktypehdr"
+    },
+    "td:includesText" : "LDP servers exposing LDPRs MUST advertise their LDP support by exposing a HTTP Link header with a target URI of http://www.w3.org/ns/ldp#Resource, and a link relation type of type (that is, rel='type') in all responses to requests made to the LDPR's HTTP Request-URI."
+  }, {
+    "@id" : "_:t494",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-get-must"
+    },
+    "td:includesText" : "LDP servers MUST support the HTTP GET Method for LDPRs"
+  }, {
+    "@id" : "_:t495",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-serverassignuri"
+    },
+    "td:includesText" : "LDP servers SHOULD assign the URI for the resource to be created using server application specific rules in the absence of a client hint."
+  }, {
+    "@id" : "_:t496",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-gen-noinferencing"
+    },
+    "td:includesText" : "LDP servers MUST NOT 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 [rdf11-concepts]. The practical implication is that all content defined by LDP must be explicitly represented, unless noted otherwise within this document."
+  }, {
+    "@id" : "_:t497",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpdc-mbrpred"
+    },
+    "td:includesText" : "LDP Direct Containers SHOULD use the ldp:member predicate as an LDPC's membership predicate if there is no obvious predicate from an application vocabulary to use."
+  }, {
+    "@id" : "_:t498",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-etags"
+    },
+    "td:includesText" : "LDP server responses MUST use entity tags (either weak or strong ones) as response ETag header values."
+  }, {
+    "@id" : "_:t499",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldp-cli-multitype"
+    },
+    "td:includesText" : "In the absence of special knowledge of the application or domain, LDP clients MUST assume that any LDP-RS can have multiple values for rdf:type."
+  }, {
+    "@id" : "_:t500",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-typecontainer"
+    },
+    "td:includesText" : "The representation of a LDPC MAY have an rdf:type of ldp:Container for Linked Data Platform Container. Non-normative note: LDPCs might have additional types, like any LDP-RS. "
+  }, {
+    "@id" : "_:t501",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-acceptposthdr"
+    },
+    "td:includesText" : "LDP servers that support POST MUST include an Accept-Post response header on HTTP OPTIONS responses, listing post document media type(s) supported by the server."
+  }, {
+    "@id" : "_:t504",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-gen-noinferencing"
+    },
+    "td:includesText" : "LDP servers MUST NOT 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 [rdf11-concepts]. The practical implication is that all content defined by LDP must be explicitly represented, unless noted otherwise within this document."
+  }, {
+    "@id" : "_:t505",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-createrdf"
+    },
+    "td:includesText" : "LDP servers that successfully create a resource from a RDF representation in the request entity body MUST honor the client's requested interaction model(s). The created resource can be thought of as an RDF named graph [rdf11-concepts]. If any model cannot be honored, the server MUST fail the request."
+  }, {
+    "@id" : "_:t506",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-cli-can-hint"
+    },
+    "td:includesText" : "LDP clients MAY provide LDP-defined hints that allow servers to optimize the content of responses. section 7.2 Preferences on the Prefer Request Header defines hints that apply to LDP-RSs. "
+  }, {
+    "@id" : "_:t507",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-rdfnullrel"
+    },
+    "td:includesText" : "In RDF representations, LDP servers MUST interpret the null relative URI for the subject of triples in the LDPR representation in the request entity body as referring to the entity in the request body. Commonly, that entity is the model for the “to be created” LDPR, so triples whose subject is the null relative URI will usually result in triples in the created resource whose subject is the created resource."
+  }, {
+    "@id" : "_:t508",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-dontreuseuris"
+    },
+    "td:includesText" : "LDP servers that allow member creation via POST SHOULD NOT re-use URIs."
+  }, {
+    "@id" : "_:t509",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpdc-containres"
+    },
+    "td:includesText" : "Each LDP Direct Container representation MUST contain exactly one triple whose subject is the LDPC URI, whose predicate is the ldp:membershipResource, and whose object is the LDPC's membership-constant-URI. Commonly the LDPC's URI is the membership-constant-URI, but LDP does not require this."
+  }, {
+    "@id" : "_:t511",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-typecontainer"
+    },
+    "td:includesText" : "The representation of a LDPC MAY have an rdf:type of ldp:Container for Linked Data Platform Container. Non-normative note: LDPCs might have additional types, like any LDP-RS. "
+  }, {
+    "@id" : "_:t512",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-cli-typeschange"
+    },
+    "td:includesText" : "In the absence of special knowledge of the application or domain, LDP clients MUST assume that the rdf:type values of a given LDP-RS can change over time."
+  }, {
+    "@id" : "_:t513",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-pubclireqs"
+    },
+    "td:includesText" : "LDP servers MUST publish any constraints on LDP clients’ ability to create or update LDPRs, by adding a Link header with rel='describedby' [RFC5988] to all responses to requests which fail due to violation of those constraints."
+  }, {
+    "@id" : "_:t514",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpbc-are-ldpcs"
+    },
+    "td:includesText" : "Each LDP Basic Container MUST also be a conforming LDP Container in section 5.2 Container along the following restrictions in this section."
+  }, {
+    "@id" : "_:t515",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-del-contremovescontres"
+    },
+    "td:includesText" : "When a contained LDPR is deleted, and the LDPC server created anassociated LDP-RS (see the LDPC POST section), the LDPC server must alsodelete the associated LDP-RS it created."
+  }, {
+    "@id" : "_:t516",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-created201"
+    },
+    "td:includesText" : "LDPC clients SHOULD create member resources by submitting a representation as the entity body of the HTTP POST to a known LDPC."
+  }, {
+    "@id" : "_:t517",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-put-failed"
+    },
+    "td:includesText" : "If an otherwise valid HTTP PUT request is received that contains properties the server chooses not to persist, e.g. unknown content, LDP servers MUST respond with an appropriate 4xx range status code [HTTP11]."
+  }, {
+    "@id" : "_:t518",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-precond"
+    },
+    "td:includesText" : "LDP servers MUST respond with status code 412 (Condition Failed) if ETags fail to match when there are no other errors with the request [HTTP11]. LDP servers that require conditional requests MUST respond with status code 428 (Precondition Required) when the absence of a precondition is the only reason for rejecting the request [RFC6585]."
+  }, {
+    "@id" : "_:t519",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-cli-hints-ignorable"
+    },
+    "td:includesText" : "LDP clients MUST be capable of processing responses formed by an LDP server that ignores hints, including LDP-defined hints."
+  }, {
+    "@id" : "_:t520",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-etags"
+    },
+    "td:includesText" : "LDP server responses MUST use entity tags (either weak or strong ones) as response ETag header values."
+  }, {
+    "@id" : "_:t521",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-del-contremovesconttriple"
+    },
+    "td:includesText" : "When an LDPR identified by the object of a containment triple is deleted, the LDPC server MUST also remove the LDPR from the containing LDPC by removing the corresponding containment triple."
+  }, {
+    "@id" : "_:t522",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-options-must"
+    },
+    "td:includesText" : "LDP servers MUST support the HTTP OPTIONS method. "
+  }, {
+    "@id" : "_:t523",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-serverassignuri"
+    },
+    "td:includesText" : "LDP servers SHOULD assign the URI for the resource to be created using server application specific rules in the absence of a client hint."
+  }, {
+    "@id" : "_:t53",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-put-failed"
+    },
+    "td:includesText" : "If an otherwise valid HTTP PUT request is received that contains properties the server chooses not to persist, e.g. unknown content, LDP servers MUST respond with an appropriate 4xx range status code [HTTP11]."
+  }, {
+    "@id" : "_:t54",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-create"
+    },
+    "td:includesText" : "LDP servers MAY choose to allow the creation of new resources using HTTP PUT."
+  }, {
+    "@id" : "_:t55",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-createrdf"
+    },
+    "td:includesText" : "LDP servers that successfully create a resource from a RDF representation in the request entity body MUST honor the client's requested interaction model(s). The created resource can be thought of as an RDF named graph [rdf11-concepts]. If any model cannot be honored, the server MUST fail the request."
+  }, {
+    "@id" : "_:t56",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-gen-atleast1rdftype"
+    },
+    "td:includesText" : "LDP-RSs representations SHOULD have at least one rdf:type set explicitly. This makes the representations much more useful to client applications that don’t support inferencing."
+  }, {
+    "@id" : "_:t57",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-created201"
+    },
+    "td:includesText" : "If the resource was created successfully, LDP servers MUST respond with status code 201 (Created) and the Location header set to the new resource’s URL. Clients shall not expect any representation in the response entity body on a 201 (Created) response."
+  }, {
+    "@id" : "_:t58",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-pubclireqs"
+    },
+    "td:includesText" : "LDP servers MUST publish any constraints on LDP clients’ ability to create or update LDPRs, by adding a Link header with rel='describedby' [RFC5988] to all responses to requests which fail due to violation of those constraints."
+  }, {
+    "@id" : "_:t59",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-gen-reusevocabsuchas"
+    },
+    "td:includesText" : "LDP-RSs predicates SHOULD use standard vocabularies such as Dublin Core [DC-TERMS], RDF [rdf11-concepts] and RDF Schema [rdf-schema], whenever possible."
+  }, {
+    "@id" : "_:t6",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpdc-post-createdmbr-member"
+    },
+    "td:includesText" : "When a successful HTTP POST request to an LDPC results in the creation of an LDPR, the LDPC MUST update its membership triples to reflect that addition, and the resulting membership triple MUST be consistent with any LDP-defined predicates it exposes."
+  }, {
+    "@id" : "_:t60",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-rdftype"
+    },
+    "td:includesText" : "The representation of a LDP-RS MAY have an rdf:type of ldp:RDFSource for Linked Data Platform RDF Source."
+  }, {
+    "@id" : "_:t61",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-etags"
+    },
+    "td:includesText" : "LDP server responses MUST use entity tags (either weak or strong ones) as response ETag header values."
+  }, {
+    "@id" : "_:t66",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-prefer"
+    },
+    "td:includesText" : "LDP servers SHOULD respect all of a client's LDP-defined hints, for example which subsets of LDP-defined state the client is interested in processing, to influence the set of triples returned in representations of an LDPC, particularly for large LDPCs. See also [LDP-PAGING]."
+  }, {
+    "@id" : "_:t71",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-binary"
+    },
+    "td:includesText" : "LDP servers may host a mixture of LDP-RSs and LDP-NRs. For example, it is common for LDP servers to need to host binary or text resources that do not have useful RDF representations."
+  }, {
+    "@id" : "_:t72",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-created201"
+    },
+    "td:includesText" : "If the resource was created successfully, LDP servers MUST respond with status code 201 (Created) and the Location header set to the new resource’s URL. Clients shall not expect any representation in the response entity body on a 201 (Created) response."
+  }, {
+    "@id" : "_:t73",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-del-contremovesconttriple"
+    },
+    "td:includesText" : "When an LDPR identified by the object of a containment triple is deleted, the LDPC server MUST also remove the LDPR from the containing LDPC by removing the corresponding containment triple."
+  }, {
+    "@id" : "_:t76",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-typecontainer"
+    },
+    "td:includesText" : "The representation of a LDPC MAY have an rdf:type of ldp:Container for Linked Data Platform Container. Non-normative note: LDPCs might have additional types, like any LDP-RS. "
+  }, {
+    "@id" : "_:t77",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-cli-can-hint"
+    },
+    "td:includesText" : "LDP clients MAY provide LDP-defined hints that allow servers to optimize the content of responses. section 7.2 Preferences on the Prefer Request Header defines hints that apply to LDP-RSs. "
+  }, {
+    "@id" : "_:t78",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-defbaseuri"
+    },
+    "td:includesText" : "LDP servers MUST assign the default base-URI for [RFC3987] relative-URI resolution to be the HTTP Request-URI when the resource already exists, and to the URI of the created resource when the request results in the creation of a new resource."
+  }, {
+    "@id" : "_:t79",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-simpleupdate"
+    },
+    "td:includesText" : "LDP servers SHOULD allow clients to update resources without requiring detailed knowledge of server-specific constraints. This is a consequence of the requirement to enable simple creation and modification of LDPRs."
+  }, {
+    "@id" : "_:t8",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-acceptposthdr"
+    },
+    "td:includesText" : "LDP servers that support POST MUST include an Accept-Post response header on HTTP OPTIONS responses, listing post document media type(s) supported by the server."
+  }, {
+    "@id" : "_:t80",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-head-must"
+    },
+    "td:includesText" : "LDP servers MUST support the HTTP HEAD method. "
+  }, {
+    "@id" : "_:t81",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-get-options"
+    },
+    "td:includesText" : "LDP servers MUST support the HTTP response headers defined in section 4.2.8 HTTP OPTIONS. "
+  }, {
+    "@id" : "_:t82",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-cli-openpreds"
+    },
+    "td:includesText" : "LDP clients SHOULD always assume that the set of predicates for a LDP-RS 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 LDP-RS is not limited to any pre-defined set."
+  }, {
+    "@id" : "_:t87",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-get-options"
+    },
+    "td:includesText" : "LDP servers MUST support the HTTP response headers defined in section 4.2.8 HTTP OPTIONS. "
+  }, {
+    "@id" : "_:t88",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-http"
+    },
+    "td:includesText" : "LDP servers MUST at least be HTTP/1.1 conformant servers [HTTP11]."
+  }, {
+    "@id" : "_:t9",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-dontreuseuris"
+    },
+    "td:includesText" : "LDP servers that allow member creation via POST SHOULD NOT re-use URIs."
+  }, {
+    "@id" : "_:t91",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-created201"
+    },
+    "td:includesText" : "LDPC clients SHOULD create member resources by submitting a representation as the entity body of the HTTP POST to a known LDPC."
+  }, {
+    "@id" : "_:t94",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-slug"
+    },
+    "td:includesText" : "LDP servers MAY allow clients to suggest the URI for a resource created through POST, using the HTTP Slug header as defined in [RFC5023]. 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."
+  }, {
+    "@id" : "_:t95",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-simpleupdate"
+    },
+    "td:includesText" : "LDP servers SHOULD allow clients to update resources without requiring detailed knowledge of server-specific constraints. This is a consequence of the requirement to enable simple creation and modification of LDPRs."
+  }, {
+    "@id" : "_:t96",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-options-allow"
+    },
+    "td:includesText" : "LDP servers MUST indicate their support for HTTP Methods by responding to a HTTP OPTIONS request on the LDPR’s URL with the HTTP Method tokens in the HTTP response header Allow. "
+  }, {
+    "@id" : "_:t97",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-get-jsonld"
+    },
+    "td:includesText" : "LDP servers SHOULD offer a application/ld+json representation of the requested LDP-RS [JSON-LD]. "
+  }, {
+    "@id" : "ldpt:BasicContainer-4xxErrorHasResponseBody",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.157Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers SHOULD 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.",
+    "rdfs:label" : "BasicContainer-4xxErrorHasResponseBody",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-put-servermanagedprops"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-4xxErrorHasResponseBody",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t484"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-4xxErrorHasResponseBody"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-AcceptPatchHeader",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.165Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers that support PATCH MUST include an Accept-Patch HTTP response header [RFC5789] on HTTP OPTIONS requests, listing patch document media type(s) supported by the server. ",
+    "rdfs:label" : "BasicContainer-AcceptPatchHeader",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-patch-acceptpatch"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-AcceptPatchHeader",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t33"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonResource-AcceptPatchHeader"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-AcceptPostResponseHeader",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.138Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers that support POST MUST include an Accept-Post response header on HTTP OPTIONS responses, listing post document media type(s) supported by the server.",
+    "rdfs:label" : "BasicContainer-AcceptPostResponseHeader",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-acceptposthdr"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-AcceptPostResponseHeader",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t8"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-AcceptPostResponseHeader"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-AcceptTurtle",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.133Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST accept a request entity body with a request header of Content-Type with value of text/turtle [turtle].",
+    "rdfs:label" : "BasicContainer-AcceptTurtle",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-turtle"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-AcceptTurtle",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t422"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-AcceptTurtle"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-AllowMultipleRdfTypes",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.149Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "In the absence of special knowledge of the application or domain, LDP clients MUST assume that any LDP-RS can have multiple values for rdf:type.",
+    "rdfs:label" : "BasicContainer-AllowMultipleRdfTypes",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldp-cli-multitype"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-AllowMultipleRdfTypes",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t499"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-AllowMultipleRdfTypes"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-AllowResponsesFromServer",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.153Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP clients MUST be capable of processing responses formed by an LDP server that ignores hints, including LDP-defined hints.",
+    "rdfs:label" : "BasicContainer-AllowResponsesFromServer",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-cli-hints-ignorable"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-AllowResponsesFromServer",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t165"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-AllowResponsesFromServer"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-ChangeRdfTypeValue",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.15Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "In the absence of special knowledge of the application or domain, LDP clients MUST assume that the rdf:type values of a given LDP-RS can change over time.",
+    "rdfs:label" : "BasicContainer-ChangeRdfTypeValue",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-cli-typeschange"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-ChangeRdfTypeValue",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t114"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-ChangeRdfTypeValue"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-ClientMayProvideHints",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.154Z"
+    },
+    "dcterms:subject" : "MAY",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP clients MAY provide LDP-defined hints that allow servers to optimize the content of responses. section 7.2 Preferences on the Prefer Request Header defines hints that apply to LDP-RSs. ",
+    "rdfs:label" : "BasicContainer-ClientMayProvideHints",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-cli-can-hint"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-ClientMayProvideHints",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t77"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MAY"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-ClientMayProvideHints"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-ClientPostToCreate",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.144Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDPC clients SHOULD create member resources by submitting a representation as the entity body of the HTTP POST to a known LDPC.",
+    "rdfs:label" : "BasicContainer-ClientPostToCreate",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-created201"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-ClientPostToCreate",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t479"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-ClientPostToCreate"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-ConditionFailedStatusCode",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.163Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST respond with status code 412 (Condition Failed) if ETags fail to match when there are no other errors with the request [HTTP11]. LDP servers that require conditional requests MUST respond with status code 428 (Precondition Required) when the absence of a precondition is the only reason for rejecting the request [RFC6585].",
+    "rdfs:label" : "BasicContainer-ConditionFailedStatusCode",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-precond"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-ConditionFailedStatusCode",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t298"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonResource-ConditionFailedStatusCode"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-ContainerSupportsHttpLinkHeader",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.128Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers exposing LDPCs MUST advertise their LDP support by exposing a HTTP Link header with a target URI matching the type of container (see below) the server supports, and a link relation type of type (that is, rel='type') in all responses to requests made to the LDPC's HTTP Request-URI.",
+    "rdfs:label" : "BasicContainer-ContainerSupportsHttpLinkHeader",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-linktypehdr"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-ContainerSupportsHttpLinkHeader",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t387"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:BasicContainer-ContainerSupportsHttpLinkHeader"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-ContainerTypeIsBasicContainer",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.129Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "Each LDP Basic Container MUST also be a conforming LDP Container in section 5.2 Container along the following restrictions in this section.",
+    "rdfs:label" : "BasicContainer-ContainerTypeIsBasicContainer",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpbc-are-ldpcs"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-ContainerTypeIsBasicContainer",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t514"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:BasicContainer-ContainerTypeIsBasicContainer"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-ContainsRdfType",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.147Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP-RSs representations SHOULD have at least one rdf:type set explicitly. This makes the representations much more useful to client applications that don’t support inferencing.",
+    "rdfs:label" : "BasicContainer-ContainsRdfType",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-gen-atleast1rdftype"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-ContainsRdfType",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t321"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-ContainsRdfType"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-ContentTypeHeader",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.134Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers SHOULD use the Content-Type request header to determine the representation format when the request has an entity body.",
+    "rdfs:label" : "BasicContainer-ContentTypeHeader",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-contenttype"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-ContentTypeHeader",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t133"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-ContentTypeHeader"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-CreateWithoutConstraints",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.136Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers SHOULD 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 LDPRs. LDP servers expose these application-specific constraints as described in section 4.2.1 General.",
+    "rdfs:label" : "BasicContainer-CreateWithoutConstraints",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-mincontraints"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-CreateWithoutConstraints",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t338"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-CreateWithoutConstraints"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-DeleteRemovesContainmentTriple",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.14Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "When an LDPR identified by the object of a containment triple is deleted, the LDPC server MUST also remove the LDPR from the containing LDPC by removing the corresponding containment triple.",
+    "rdfs:label" : "BasicContainer-DeleteRemovesContainmentTriple",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-del-contremovesconttriple"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-DeleteRemovesContainmentTriple",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t521"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-DeleteRemovesContainmentTriple"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-ETagHeadersGet",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.16Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP server responses MUST use entity tags (either weak or strong ones) as response ETag header values.",
+    "rdfs:label" : "BasicContainer-ETagHeadersGet",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-etags"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-ETagHeadersGet",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t483"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonResource-ETagHeadersGet"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-ETagHeadersHead",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.161Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP server responses MUST use entity tags (either weak or strong ones) as response ETag header values.",
+    "rdfs:label" : "BasicContainer-ETagHeadersHead",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-etags"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-ETagHeadersHead",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t239"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonResource-ETagHeadersHead"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-GetResource",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.146Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST provide an RDF representation for LDP-RSs. The HTTP Request-URI of the LDP-RS is typically the subject of most triples in the response.",
+    "rdfs:label" : "BasicContainer-GetResource",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-gen-rdf"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-GetResource",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t204"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-GetResource"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-GetResourceAcceptTurtle",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.153Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers must provide a text/turtle representation of the requested LDP-RS whenever HTTP content negotiation does not force another outcome [turtle]. In other words, if the server receives a GET request whose Request-URI identifies a LDP-RS, and either text/turtle has the highest relative quality factor (q= value) in the Accept request header or that header is absent, then an LDP server has to respond with Turtle.",
+    "rdfs:label" : "BasicContainer-GetResourceAcceptTurtle",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-get-turtle"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-GetResourceAcceptTurtle",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t179"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-GetResourceAcceptTurtle"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-GetResourcePreservesTriples",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.152Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "A LDP client MUST preserve all triples retrieved from an LDP-RS using HTTP GET that it doesn’t change whether it understands the predicates or not, when its intent is to perform an update using HTTP PUT. The use of HTTP PATCH instead of HTTP PUT for update avoids this burden for clients [RFC5789]. ",
+    "rdfs:label" : "BasicContainer-GetResourcePreservesTriples",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-cli-preservetriples"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-GetResourcePreservesTriples",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t317"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-GetResourcePreservesTriples"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-GetResponseHeaders",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.162Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST support the HTTP response headers defined in section 4.2.8 HTTP OPTIONS. ",
+    "rdfs:label" : "BasicContainer-GetResponseHeaders",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-get-options"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-GetResponseHeaders",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t87"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonResource-GetResponseHeaders"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-Head",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.165Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST support the HTTP HEAD method. ",
+    "rdfs:label" : "BasicContainer-Head",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-head-must"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-Head",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t104"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonResource-Head"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-IsHttp11Manual",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.159Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST at least be HTTP/1.1 conformant servers [HTTP11].",
+    "rdfs:label" : "BasicContainer-IsHttp11Manual",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-http"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-IsHttp11Manual",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t381"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonResource-IsHttp11Manual"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-IsHttp11Server",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.159Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST at least be HTTP/1.1 conformant servers [HTTP11].",
+    "rdfs:label" : "BasicContainer-IsHttp11Server",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-http"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-IsHttp11Server",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t14"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonResource-IsHttp11Server"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-JsonLdRepresentation",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.154Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers SHOULD offer a application/ld+json representation of the requested LDP-RS [JSON-LD]. ",
+    "rdfs:label" : "BasicContainer-JsonLdRepresentation",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-get-jsonld"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-JsonLdRepresentation",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t415"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-JsonLdRepresentation"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-LdpLinkHeader",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.161Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers exposing LDPRs MUST advertise their LDP support by exposing a HTTP Link header with a target URI of http://www.w3.org/ns/ldp#Resource, and a link relation type of type (that is, rel='type') in all responses to requests made to the LDPR's HTTP Request-URI.",
+    "rdfs:label" : "BasicContainer-LdpLinkHeader",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-linktypehdr"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-LdpLinkHeader",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t461"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonResource-LdpLinkHeader"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-MAYManifest",
+    "http://purl.org/dc/elements/1.1/title" : "BasicContainer (MAY)",
+    "rdf:type" : {
+      "@id" : "mf:Manifest"
+    },
+    "rdfs:comment" : "LDP Basic Container tests. MAY conformance tests.",
+    "mf:entries" : {
+      "@list" : [ {
+        "@id" : "ldpt:BasicContainer-PutToCreate"
+      }, {
+        "@id" : "ldpt:BasicContainer-RdfTypeLdpContainer"
+      }, {
+        "@id" : "ldpt:BasicContainer-ServerHonorsSlug"
+      }, {
+        "@id" : "ldpt:BasicContainer-TypeRdfSource"
+      }, {
+        "@id" : "ldpt:BasicContainer-ClientMayProvideHints"
+      } ]
+    },
+    "mf:name" : "BasicContainer (MAY)"
+  }, {
+    "@id" : "ldpt:BasicContainer-MUSTManifest",
+    "http://purl.org/dc/elements/1.1/title" : "BasicContainer (MUST)",
+    "rdf:type" : {
+      "@id" : "mf:Manifest"
+    },
+    "rdfs:comment" : "LDP Basic Container tests. MUST conformance tests.",
+    "mf:entries" : {
+      "@list" : [ {
+        "@id" : "ldpt:BasicContainer-ContainerSupportsHttpLinkHeader"
+      }, {
+        "@id" : "ldpt:BasicContainer-ContainerTypeIsBasicContainer"
+      }, {
+        "@id" : "ldpt:BasicContainer-RelativeUriResolutionPost"
+      }, {
+        "@id" : "ldpt:BasicContainer-PostResponseStatusAndLocation"
+      }, {
+        "@id" : "ldpt:BasicContainer-PostContainer"
+      }, {
+        "@id" : "ldpt:BasicContainer-RequestedInteractionModelCreateNotAllowed"
+      }, {
+        "@id" : "ldpt:BasicContainer-RequestedInteractionModelHeaders"
+      }, {
+        "@id" : "ldpt:BasicContainer-AcceptTurtle"
+      }, {
+        "@id" : "ldpt:BasicContainer-NullRelativeUriPost"
+      }, {
+        "@id" : "ldpt:BasicContainer-AcceptPostResponseHeader"
+      }, {
+        "@id" : "ldpt:BasicContainer-DeleteRemovesContainmentTriple"
+      }, {
+        "@id" : "ldpt:BasicContainer-RelativeUriResolutionPut"
+      }, {
+        "@id" : "ldpt:BasicContainer-PutReplacesResource"
+      }, {
+        "@id" : "ldpt:BasicContainer-PutSimpleUpdate"
+      }, {
+        "@id" : "ldpt:BasicContainer-GetResource"
+      }, {
+        "@id" : "ldpt:BasicContainer-AllowMultipleRdfTypes"
+      }, {
+        "@id" : "ldpt:BasicContainer-ChangeRdfTypeValue"
+      }, {
+        "@id" : "ldpt:BasicContainer-RestrictClientInference"
+      }, {
+        "@id" : "ldpt:BasicContainer-GetResourcePreservesTriples"
+      }, {
+        "@id" : "ldpt:BasicContainer-AllowResponsesFromServer"
+      }, {
+        "@id" : "ldpt:BasicContainer-GetResourceAcceptTurtle"
+      }, {
+        "@id" : "ldpt:BasicContainer-PublishConstraintsReadOnlyProp"
+      }, {
+        "@id" : "ldpt:BasicContainer-PublishConstraintsUnknownProp"
+      }, {
+        "@id" : "ldpt:BasicContainer-PutReadOnlyProperties4xxStatus"
+      }, {
+        "@id" : "ldpt:BasicContainer-PutPropertiesNotPersisted"
+      }, {
+        "@id" : "ldpt:BasicContainer-IsHttp11Server"
+      }, {
+        "@id" : "ldpt:BasicContainer-IsHttp11Manual"
+      }, {
+        "@id" : "ldpt:BasicContainer-ETagHeadersGet"
+      }, {
+        "@id" : "ldpt:BasicContainer-ETagHeadersHead"
+      }, {
+        "@id" : "ldpt:BasicContainer-LdpLinkHeader"
+      }, {
+        "@id" : "ldpt:BasicContainer-GetResponseHeaders"
+      }, {
+        "@id" : "ldpt:BasicContainer-ConditionFailedStatusCode"
+      }, {
+        "@id" : "ldpt:BasicContainer-PreconditionRequiredStatusCode"
+      }, {
+        "@id" : "ldpt:BasicContainer-PutBadETag"
+      }, {
+        "@id" : "ldpt:BasicContainer-Head"
+      }, {
+        "@id" : "ldpt:BasicContainer-AcceptPatchHeader"
+      }, {
+        "@id" : "ldpt:BasicContainer-Options"
+      }, {
+        "@id" : "ldpt:BasicContainer-OptionsAllowHeader"
+      } ]
+    },
+    "mf:name" : "BasicContainer (MUST)"
+  }, {
+    "@id" : "ldpt:BasicContainer-NoRdfBagSeqOrList",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.142Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDPC representations SHOULD NOT use RDF container types rdf:Bag, rdf:Seq or rdf:List.",
+    "rdfs:label" : "BasicContainer-NoRdfBagSeqOrList",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-nordfcontainertypes"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-NoRdfBagSeqOrList",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t36"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-NoRdfBagSeqOrList"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-NullRelativeUriPost",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.135Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "In RDF representations, LDP servers MUST interpret the null relative URI for the subject of triples in the LDPR representation in the request entity body as referring to the entity in the request body. Commonly, that entity is the model for the “to be created” LDPR, so triples whose subject is the null relative URI will usually result in triples in the created resource whose subject is the created resource.",
+    "rdfs:label" : "BasicContainer-NullRelativeUriPost",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-rdfnullrel"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-NullRelativeUriPost",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t410"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-NullRelativeUriPost"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-Options",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.166Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST support the HTTP OPTIONS method. ",
+    "rdfs:label" : "BasicContainer-Options",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-options-must"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-Options",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t3"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonResource-Options"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-OptionsAllowHeader",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.166Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST indicate their support for HTTP Methods by responding to a HTTP OPTIONS request on the LDPR’s URL with the HTTP Method tokens in the HTTP response header Allow. ",
+    "rdfs:label" : "BasicContainer-OptionsAllowHeader",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-options-allow"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-OptionsAllowHeader",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t340"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonResource-OptionsAllowHeader"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-PatchMethod",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.14Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers are RECOMMENDED to support HTTP PATCH as the preferred method for updating an LDPC's empty-container triples. ",
+    "rdfs:label" : "BasicContainer-PatchMethod",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-patch-req"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-PatchMethod",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t355"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-PatchMethod"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-PostContainer",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.131Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "When a successful HTTP POST request to an LDPC results in the creation of an LDPR, a containment triple MUST be added to the state of LDPC.",
+    "rdfs:label" : "BasicContainer-PostContainer",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-createdmbr-contains"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-PostContainer",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t421"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-PostContainer"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-PostJsonLd",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.142Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers SHOULD accept a request entity body with a request header of Content-Type with value of application/ld+json [JSON-LD].",
+    "rdfs:label" : "BasicContainer-PostJsonLd",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-jsonld"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-PostJsonLd",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t480"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-PostJsonLd"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-PostNoSlug",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.135Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers SHOULD assign the URI for the resource to be created using server application specific rules in the absence of a client hint.",
+    "rdfs:label" : "BasicContainer-PostNoSlug",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-serverassignuri"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-PostNoSlug",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t495"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-PostNoSlug"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-PostResponseStatusAndLocation",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.131Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "If the resource was created successfully, LDP servers MUST respond with status code 201 (Created) and the Location header set to the new resource’s URL. Clients shall not expect any representation in the response entity body on a 201 (Created) response.",
+    "rdfs:label" : "BasicContainer-PostResponseStatusAndLocation",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-created201"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-PostResponseStatusAndLocation",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t72"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-PostResponseStatusAndLocation"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-PreconditionRequiredStatusCode",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.164Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST respond with status code 412 (Condition Failed) if ETags fail to match when there are no other errors with the request [HTTP11]. LDP servers that require conditional requests MUST respond with status code 428 (Precondition Required) when the absence of a precondition is the only reason for rejecting the request [RFC6585].",
+    "rdfs:label" : "BasicContainer-PreconditionRequiredStatusCode",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-precond"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-PreconditionRequiredStatusCode",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t291"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonResource-PreconditionRequiredStatusCode"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-PreferContainmentTriples",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.143Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers SHOULD respect all of a client's LDP-defined hints, for example which subsets of LDP-defined state the client is interested in processing, to influence the set of triples returned in representations of an LDPC, particularly for large LDPCs. See also [LDP-PAGING].",
+    "rdfs:label" : "BasicContainer-PreferContainmentTriples",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-prefer"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-PreferContainmentTriples",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t401"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-PreferContainmentTriples"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-PublishConstraintsReadOnlyProp",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.155Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST publish any constraints on LDP clients’ ability to create or update LDPRs, by adding a Link header with rel='describedby' [RFC5988] to all responses to requests which fail due to violation of those constraints.",
+    "rdfs:label" : "BasicContainer-PublishConstraintsReadOnlyProp",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-pubclireqs"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-PublishConstraintsReadOnlyProp",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t377"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-PublishConstraintsReadOnlyProp"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-PublishConstraintsUnknownProp",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.156Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST publish any constraints on LDP clients’ ability to create or update LDPRs, by adding a Link header with rel='describedby' [RFC5988] to all responses to requests which fail due to violation of those constraints.",
+    "rdfs:label" : "BasicContainer-PublishConstraintsUnknownProp",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-pubclireqs"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-PublishConstraintsUnknownProp",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t513"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-PublishConstraintsUnknownProp"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-PutBadETag",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.164Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST respond with status code 412 (Condition Failed) if ETags fail to match when there are no other errors with the request [HTTP11]. LDP servers that require conditional requests MUST respond with status code 428 (Precondition Required) when the absence of a precondition is the only reason for rejecting the request [RFC6585].",
+    "rdfs:label" : "BasicContainer-PutBadETag",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-precond"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-PutBadETag",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t420"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonResource-PutBadETag"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-PutPropertiesNotPersisted",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.157Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "If an otherwise valid HTTP PUT request is received that contains properties the server chooses not to persist, e.g. unknown content, LDP servers MUST respond with an appropriate 4xx range status code [HTTP11].",
+    "rdfs:label" : "BasicContainer-PutPropertiesNotPersisted",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-put-failed"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-PutPropertiesNotPersisted",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t53"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-PutPropertiesNotPersisted"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-PutReadOnlyProperties4xxStatus",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.156Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "If an otherwise valid HTTP PUT request is received that attempts to change properties the server does not allow clients to modify, LDP servers MUST respond with a 4xx range status code (typically 409 Conflict)",
+    "rdfs:label" : "BasicContainer-PutReadOnlyProperties4xxStatus",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-put-servermanagedprops"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-PutReadOnlyProperties4xxStatus",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t222"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-PutReadOnlyProperties4xxStatus"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-PutReplacesResource",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.145Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "If a HTTP PUT is accepted on an existing resource, LDP servers MUST replace the entire persistent state of the identified resource with the entity representation in the body of the request.",
+    "rdfs:label" : "BasicContainer-PutReplacesResource",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-replaceall"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-PutReplacesResource",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t260"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-PutReplacesResource"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-PutRequiresIfMatch",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.162Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP clients SHOULD use the HTTP If-Match header and HTTP ETags to ensure it isn’t modifying a resource that has changed since the client last retrieved its representation. LDP servers SHOULD require the HTTP If-Match header and HTTP ETags to detect collisions.",
+    "rdfs:label" : "BasicContainer-PutRequiresIfMatch",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-precond"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-PutRequiresIfMatch",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t132"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonResource-PutRequiresIfMatch"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-PutSimpleUpdate",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.146Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers SHOULD allow clients to update resources without requiring detailed knowledge of server-specific constraints. This is a consequence of the requirement to enable simple creation and modification of LDPRs.",
+    "rdfs:label" : "BasicContainer-PutSimpleUpdate",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-simpleupdate"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-PutSimpleUpdate",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t95"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-PutSimpleUpdate"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-PutToCreate",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.13Z"
+    },
+    "dcterms:subject" : "MAY",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MAY choose to allow the creation of new resources using HTTP PUT.",
+    "rdfs:label" : "BasicContainer-PutToCreate",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-create"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-PutToCreate",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t235"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MAY"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-PutToCreate"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-RdfTypeLdpContainer",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.141Z"
+    },
+    "dcterms:subject" : "MAY",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "The representation of a LDPC MAY have an rdf:type of ldp:Container for Linked Data Platform Container. Non-normative note: LDPCs might have additional types, like any LDP-RS. ",
+    "rdfs:label" : "BasicContainer-RdfTypeLdpContainer",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-typecontainer"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-RdfTypeLdpContainer",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t500"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MAY"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-RdfTypeLdpContainer"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-ReUseVocabularies",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.148Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP-RSs SHOULD 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.",
+    "rdfs:label" : "BasicContainer-ReUseVocabularies",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-gen-reusevocab"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-ReUseVocabularies",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t111"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-ReUseVocabularies"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-RejectPutModifyingContainmentTriples",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.138Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers SHOULD NOT allow HTTP PUT to update an LDPC’s containment triples; if the server receives such a request, it SHOULD respond with a 409 (Conflict) status code.",
+    "rdfs:label" : "BasicContainer-RejectPutModifyingContainmentTriples",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-put-mbrprops"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-RejectPutModifyingContainmentTriples",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t151"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-RejectPutModifyingContainmentTriples"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-RelativeUriResolutionPost",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.13Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST assign the default base-URI for [RFC3987] relative-URI resolution to be the HTTP Request-URI when the resource already exists, and to the URI of the created resource when the request results in the creation of a new resource.",
+    "rdfs:label" : "BasicContainer-RelativeUriResolutionPost",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-defbaseuri"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-RelativeUriResolutionPost",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t490"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-RelativeUriResolutionPost"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-RelativeUriResolutionPut",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.144Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST assign the default base-URI for [RFC3987] relative-URI resolution to be the HTTP Request-URI when the resource already exists, and to the URI of the created resource when the request results in the creation of a new resource.",
+    "rdfs:label" : "BasicContainer-RelativeUriResolutionPut",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-defbaseuri"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-RelativeUriResolutionPut",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t255"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-RelativeUriResolutionPut"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-RequestedInteractionModelCreateNotAllowed",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.132Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers that successfully create a resource from a RDF representation in the request entity body MUST honor the client's requested interaction model(s). The created resource can be thought of as an RDF named graph [rdf11-concepts]. If any model cannot be honored, the server MUST fail the request.",
+    "rdfs:label" : "BasicContainer-RequestedInteractionModelCreateNotAllowed",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-createrdf"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-RequestedInteractionModelCreateNotAllowed",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t505"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-RequestedInteractionModelCreateNotAllowed"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-RequestedInteractionModelHeaders",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.133Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers that successfully create a resource from a RDF representation in the request entity body MUST honor the client's requested interaction model(s). The created resource can be thought of as an RDF named graph [rdf11-concepts]. If any model cannot be honored, the server MUST fail the request.",
+    "rdfs:label" : "BasicContainer-RequestedInteractionModelHeaders",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-createrdf"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-RequestedInteractionModelHeaders",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t285"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-RequestedInteractionModelHeaders"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-ResponsePropertiesNotPersisted",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.158Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers SHOULD 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 section 4.2.1 General.",
+    "rdfs:label" : "BasicContainer-ResponsePropertiesNotPersisted",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-put-failed"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-ResponsePropertiesNotPersisted",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t266"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-ResponsePropertiesNotPersisted"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-RestrictClientInference",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.151Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST NOT 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 [rdf11-concepts]. The practical implication is that all content defined by LDP must be explicitly represented, unless noted otherwise within this document.",
+    "rdfs:label" : "BasicContainer-RestrictClientInference",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-gen-noinferencing"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-RestrictClientInference",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t203"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-RestrictClientInference"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-RestrictPutReUseUri",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.139Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers that allow LDPR creation via PUT SHOULD NOT re-use URIs. For RDF representations (LDP-RSs),the created resource can be thought of as an RDF named graph [rdf11-concepts].",
+    "rdfs:label" : "BasicContainer-RestrictPutReUseUri",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-put-create"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-RestrictPutReUseUri",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t460"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-RestrictPutReUseUri"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-RestrictUriReUseNoSlug",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.137Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers that allow member creation via POST SHOULD NOT re-use URIs.",
+    "rdfs:label" : "BasicContainer-RestrictUriReUseNoSlug",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-dontreuseuris"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-RestrictUriReUseNoSlug",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t186"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-RestrictUriReUseNoSlug"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-RestrictUriReUseSlug",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.137Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers that allow member creation via POST SHOULD NOT re-use URIs.",
+    "rdfs:label" : "BasicContainer-RestrictUriReUseSlug",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-dontreuseuris"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-RestrictUriReUseSlug",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t508"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-RestrictUriReUseSlug"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-SHOULDManifest",
+    "http://purl.org/dc/elements/1.1/title" : "BasicContainer (SHOULD)",
+    "rdf:type" : {
+      "@id" : "mf:Manifest"
+    },
+    "rdfs:comment" : "LDP Basic Container tests. SHOULD conformance tests.",
+    "mf:entries" : {
+      "@list" : [ {
+        "@id" : "ldpt:BasicContainer-ContentTypeHeader"
+      }, {
+        "@id" : "ldpt:BasicContainer-PostNoSlug"
+      }, {
+        "@id" : "ldpt:BasicContainer-CreateWithoutConstraints"
+      }, {
+        "@id" : "ldpt:BasicContainer-RestrictUriReUseSlug"
+      }, {
+        "@id" : "ldpt:BasicContainer-RestrictUriReUseNoSlug"
+      }, {
+        "@id" : "ldpt:BasicContainer-RejectPutModifyingContainmentTriples"
+      }, {
+        "@id" : "ldpt:BasicContainer-RestrictPutReUseUri"
+      }, {
+        "@id" : "ldpt:BasicContainer-PatchMethod"
+      }, {
+        "@id" : "ldpt:BasicContainer-PostJsonLd"
+      }, {
+        "@id" : "ldpt:BasicContainer-NoRdfBagSeqOrList"
+      }, {
+        "@id" : "ldpt:BasicContainer-PreferContainmentTriples"
+      }, {
+        "@id" : "ldpt:BasicContainer-ClientPostToCreate"
+      }, {
+        "@id" : "ldpt:BasicContainer-ContainsRdfType"
+      }, {
+        "@id" : "ldpt:BasicContainer-ReUseVocabularies"
+      }, {
+        "@id" : "ldpt:BasicContainer-UseStandardVocabularies"
+      }, {
+        "@id" : "ldpt:BasicContainer-ServerOpen"
+      }, {
+        "@id" : "ldpt:BasicContainer-JsonLdRepresentation"
+      }, {
+        "@id" : "ldpt:BasicContainer-4xxErrorHasResponseBody"
+      }, {
+        "@id" : "ldpt:BasicContainer-ResponsePropertiesNotPersisted"
+      }, {
+        "@id" : "ldpt:BasicContainer-PutRequiresIfMatch"
+      } ]
+    },
+    "mf:name" : "BasicContainer (SHOULD)"
+  }, {
+    "@id" : "ldpt:BasicContainer-ServerHonorsSlug",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.141Z"
+    },
+    "dcterms:subject" : "MAY",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MAY allow clients to suggest the URI for a resource created through POST, using the HTTP Slug header as defined in [RFC5023]. 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.",
+    "rdfs:label" : "BasicContainer-ServerHonorsSlug",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-slug"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-ServerHonorsSlug",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t94"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MAY"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-ServerHonorsSlug"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-ServerOpen",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.151Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP clients SHOULD always assume that the set of predicates for a LDP-RS 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 LDP-RS is not limited to any pre-defined set.",
+    "rdfs:label" : "BasicContainer-ServerOpen",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-cli-openpreds"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-ServerOpen",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t82"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-ServerOpen"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-TypeRdfSource",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.147Z"
+    },
+    "dcterms:subject" : "MAY",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "The representation of a LDP-RS MAY have an rdf:type of ldp:RDFSource for Linked Data Platform RDF Source.",
+    "rdfs:label" : "BasicContainer-TypeRdfSource",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-rdftype"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-TypeRdfSource",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t60"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MAY"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-TypeRdfSource"
+    }
+  }, {
+    "@id" : "ldpt:BasicContainer-UseStandardVocabularies",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.149Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP-RSs predicates SHOULD use standard vocabularies such as Dublin Core [DC-TERMS], RDF [rdf11-concepts] and RDF Schema [rdf-schema], whenever possible.",
+    "rdfs:label" : "BasicContainer-UseStandardVocabularies",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-gen-reusevocabsuchas"
+    },
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-UseStandardVocabularies",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t268"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-UseStandardVocabularies"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-4xxErrorHasResponseBody",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.225Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers SHOULD 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.",
+    "rdfs:label" : "DirectContainer-4xxErrorHasResponseBody",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-put-servermanagedprops"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-4xxErrorHasResponseBody",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t339"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-4xxErrorHasResponseBody"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-AcceptPatchHeader",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.232Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers that support PATCH MUST include an Accept-Patch HTTP response header [RFC5789] on HTTP OPTIONS requests, listing patch document media type(s) supported by the server. ",
+    "rdfs:label" : "DirectContainer-AcceptPatchHeader",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-patch-acceptpatch"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-AcceptPatchHeader",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t471"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonResource-AcceptPatchHeader"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-AcceptPostResponseHeader",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.204Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers that support POST MUST include an Accept-Post response header on HTTP OPTIONS responses, listing post document media type(s) supported by the server.",
+    "rdfs:label" : "DirectContainer-AcceptPostResponseHeader",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-acceptposthdr"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-AcceptPostResponseHeader",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t142"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-AcceptPostResponseHeader"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-AcceptTurtle",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.2Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST accept a request entity body with a request header of Content-Type with value of text/turtle [turtle].",
+    "rdfs:label" : "DirectContainer-AcceptTurtle",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-turtle"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-AcceptTurtle",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t283"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-AcceptTurtle"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-ActAsIfInsertedContentRelationTripleExists",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.194Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP Direct Containers MUST behave as if they have a (LDPC URI, ldp:insertedContentRelation , ldp:MemberSubject) triple, but LDP imposes no requirement to materialize such a triple in the LDP-DC representation.",
+    "rdfs:label" : "DirectContainer-ActAsIfInsertedContentRelationTripleExists",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpdc-indirectmbr-basic"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-ActAsIfInsertedContentRelationTripleExists",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t444"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:DirectContainer-ActAsIfInsertedContentRelationTripleExists"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-AllowMultipleRdfTypes",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.217Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "In the absence of special knowledge of the application or domain, LDP clients MUST assume that any LDP-RS can have multiple values for rdf:type.",
+    "rdfs:label" : "DirectContainer-AllowMultipleRdfTypes",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldp-cli-multitype"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-AllowMultipleRdfTypes",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t329"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-AllowMultipleRdfTypes"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-AllowResponsesFromServer",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.22Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP clients MUST be capable of processing responses formed by an LDP server that ignores hints, including LDP-defined hints.",
+    "rdfs:label" : "DirectContainer-AllowResponsesFromServer",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-cli-hints-ignorable"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-AllowResponsesFromServer",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t270"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-AllowResponsesFromServer"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-ChangeRdfTypeValue",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.217Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "In the absence of special knowledge of the application or domain, LDP clients MUST assume that the rdf:type values of a given LDP-RS can change over time.",
+    "rdfs:label" : "DirectContainer-ChangeRdfTypeValue",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-cli-typeschange"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-ChangeRdfTypeValue",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t123"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-ChangeRdfTypeValue"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-ClientMayProvideHints",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.221Z"
+    },
+    "dcterms:subject" : "MAY",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP clients MAY provide LDP-defined hints that allow servers to optimize the content of responses. section 7.2 Preferences on the Prefer Request Header defines hints that apply to LDP-RSs. ",
+    "rdfs:label" : "DirectContainer-ClientMayProvideHints",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-cli-can-hint"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-ClientMayProvideHints",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t470"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MAY"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-ClientMayProvideHints"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-ClientPostToCreate",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.211Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDPC clients SHOULD create member resources by submitting a representation as the entity body of the HTTP POST to a known LDPC.",
+    "rdfs:label" : "DirectContainer-ClientPostToCreate",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-created201"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-ClientPostToCreate",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t516"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-ClientPostToCreate"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-ConditionFailedStatusCode",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.23Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST respond with status code 412 (Condition Failed) if ETags fail to match when there are no other errors with the request [HTTP11]. LDP servers that require conditional requests MUST respond with status code 428 (Precondition Required) when the absence of a precondition is the only reason for rejecting the request [RFC6585].",
+    "rdfs:label" : "DirectContainer-ConditionFailedStatusCode",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-precond"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-ConditionFailedStatusCode",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t434"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonResource-ConditionFailedStatusCode"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-ContainsRdfType",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.214Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP-RSs representations SHOULD have at least one rdf:type set explicitly. This makes the representations much more useful to client applications that don’t support inferencing.",
+    "rdfs:label" : "DirectContainer-ContainsRdfType",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-gen-atleast1rdftype"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-ContainsRdfType",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t56"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-ContainsRdfType"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-ContentTypeHeader",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.2Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers SHOULD use the Content-Type request header to determine the representation format when the request has an entity body.",
+    "rdfs:label" : "DirectContainer-ContentTypeHeader",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-contenttype"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-ContentTypeHeader",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t129"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-ContentTypeHeader"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-CreateWithoutConstraints",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.202Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers SHOULD 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 LDPRs. LDP servers expose these application-specific constraints as described in section 4.2.1 General.",
+    "rdfs:label" : "DirectContainer-CreateWithoutConstraints",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-mincontraints"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-CreateWithoutConstraints",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t430"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-CreateWithoutConstraints"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-DeleteRemovesContainmentTriple",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.206Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "When an LDPR identified by the object of a containment triple is deleted, the LDPC server MUST also remove the LDPR from the containing LDPC by removing the corresponding containment triple.",
+    "rdfs:label" : "DirectContainer-DeleteRemovesContainmentTriple",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-del-contremovesconttriple"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-DeleteRemovesContainmentTriple",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t262"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-DeleteRemovesContainmentTriple"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-DeleteResourceUpdatesTriples",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.195Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "When an LDPR identified by the object of a membership triple which was originally created by the LDP-DC is deleted, the LDPC server MUST also remove the corresponding membership triple.",
+    "rdfs:label" : "DirectContainer-DeleteResourceUpdatesTriples",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpdc-del-contremovesmbrtriple"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-DeleteResourceUpdatesTriples",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t206"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:DirectContainer-DeleteResourceUpdatesTriples"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-ETagHeadersGet",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.227Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP server responses MUST use entity tags (either weak or strong ones) as response ETag header values.",
+    "rdfs:label" : "DirectContainer-ETagHeadersGet",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-etags"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-ETagHeadersGet",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t474"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonResource-ETagHeadersGet"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-ETagHeadersHead",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.228Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP server responses MUST use entity tags (either weak or strong ones) as response ETag header values.",
+    "rdfs:label" : "DirectContainer-ETagHeadersHead",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-etags"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-ETagHeadersHead",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t245"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonResource-ETagHeadersHead"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-GetResource",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.214Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST provide an RDF representation for LDP-RSs. The HTTP Request-URI of the LDP-RS is typically the subject of most triples in the response.",
+    "rdfs:label" : "DirectContainer-GetResource",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-gen-rdf"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-GetResource",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t487"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-GetResource"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-GetResourceAcceptTurtle",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.22Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers must provide a text/turtle representation of the requested LDP-RS whenever HTTP content negotiation does not force another outcome [turtle]. In other words, if the server receives a GET request whose Request-URI identifies a LDP-RS, and either text/turtle has the highest relative quality factor (q= value) in the Accept request header or that header is absent, then an LDP server has to respond with Turtle.",
+    "rdfs:label" : "DirectContainer-GetResourceAcceptTurtle",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-get-turtle"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-GetResourceAcceptTurtle",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t174"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-GetResourceAcceptTurtle"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-GetResourcePreservesTriples",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.219Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "A LDP client MUST preserve all triples retrieved from an LDP-RS using HTTP GET that it doesn’t change whether it understands the predicates or not, when its intent is to perform an update using HTTP PUT. The use of HTTP PATCH instead of HTTP PUT for update avoids this burden for clients [RFC5789]. ",
+    "rdfs:label" : "DirectContainer-GetResourcePreservesTriples",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-cli-preservetriples"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-GetResourcePreservesTriples",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t323"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-GetResourcePreservesTriples"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-GetResponseHeaders",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.229Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST support the HTTP response headers defined in section 4.2.8 HTTP OPTIONS. ",
+    "rdfs:label" : "DirectContainer-GetResponseHeaders",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-get-options"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-GetResponseHeaders",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t81"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonResource-GetResponseHeaders"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-Head",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.232Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST support the HTTP HEAD method. ",
+    "rdfs:label" : "DirectContainer-Head",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-head-must"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-Head",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t134"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonResource-Head"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-HttpLinkHeader",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.192Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers exposing LDPCs MUST advertise their LDP support by exposing a HTTP Link header with a target URI matching the type of container (see below) the server supports, and a link relation type of type (that is, rel='type') in all responses to requests made to the LDPC's HTTP Request-URI.",
+    "rdfs:label" : "DirectContainer-HttpLinkHeader",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-linktypehdr"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-HttpLinkHeader",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t261"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:DirectContainer-HttpLinkHeader"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-IsHttp11Manual",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.227Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST at least be HTTP/1.1 conformant servers [HTTP11].",
+    "rdfs:label" : "DirectContainer-IsHttp11Manual",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-http"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-IsHttp11Manual",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t354"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonResource-IsHttp11Manual"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-IsHttp11Server",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.226Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST at least be HTTP/1.1 conformant servers [HTTP11].",
+    "rdfs:label" : "DirectContainer-IsHttp11Server",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-http"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-IsHttp11Server",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t10"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonResource-IsHttp11Server"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-JsonLdRepresentation",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.221Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers SHOULD offer a application/ld+json representation of the requested LDP-RS [JSON-LD]. ",
+    "rdfs:label" : "DirectContainer-JsonLdRepresentation",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-get-jsonld"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-JsonLdRepresentation",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t486"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-JsonLdRepresentation"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-LdpLinkHeader",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.229Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers exposing LDPRs MUST advertise their LDP support by exposing a HTTP Link header with a target URI of http://www.w3.org/ns/ldp#Resource, and a link relation type of type (that is, rel='type') in all responses to requests made to the LDPR's HTTP Request-URI.",
+    "rdfs:label" : "DirectContainer-LdpLinkHeader",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-linktypehdr"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-LdpLinkHeader",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t493"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonResource-LdpLinkHeader"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-MAYManifest",
+    "http://purl.org/dc/elements/1.1/title" : "DirectContainer (MAY)",
+    "rdf:type" : {
+      "@id" : "mf:Manifest"
+    },
+    "rdfs:comment" : "LDP Direct Container tests. MAY conformance tests.",
+    "mf:entries" : {
+      "@list" : [ {
+        "@id" : "ldpt:DirectContainer-PutToCreate"
+      }, {
+        "@id" : "ldpt:DirectContainer-RdfTypeLdpContainer"
+      }, {
+        "@id" : "ldpt:DirectContainer-ServerHonorsSlug"
+      }, {
+        "@id" : "ldpt:DirectContainer-TypeRdfSource"
+      }, {
+        "@id" : "ldpt:DirectContainer-ClientMayProvideHints"
+      } ]
+    },
+    "mf:name" : "DirectContainer (MAY)"
+  }, {
+    "@id" : "ldpt:DirectContainer-MUSTManifest",
+    "http://purl.org/dc/elements/1.1/title" : "DirectContainer (MUST)",
+    "rdf:type" : {
+      "@id" : "mf:Manifest"
+    },
+    "rdfs:comment" : "LDP Direct Container tests. MUST conformance tests.",
+    "mf:entries" : {
+      "@list" : [ {
+        "@id" : "ldpt:DirectContainer-HttpLinkHeader"
+      }, {
+        "@id" : "ldpt:DirectContainer-MemberResourceTriple"
+      }, {
+        "@id" : "ldpt:DirectContainer-MemberRelationOrIsMemberOfRelationTripleExists"
+      }, {
+        "@id" : "ldpt:DirectContainer-ActAsIfInsertedContentRelationTripleExists"
+      }, {
+        "@id" : "ldpt:DirectContainer-PostResourceUpdatesTriples"
+      }, {
+        "@id" : "ldpt:DirectContainer-DeleteResourceUpdatesTriples"
+      }, {
+        "@id" : "ldpt:DirectContainer-RelativeUriResolutionPost"
+      }, {
+        "@id" : "ldpt:DirectContainer-PostResponseStatusAndLocation"
+      }, {
+        "@id" : "ldpt:DirectContainer-PostContainer"
+      }, {
+        "@id" : "ldpt:DirectContainer-RequestedInteractionModelCreateNotAllowed"
+      }, {
+        "@id" : "ldpt:DirectContainer-RequestedInteractionModelHeaders"
+      }, {
+        "@id" : "ldpt:DirectContainer-AcceptTurtle"
+      }, {
+        "@id" : "ldpt:DirectContainer-NullRelativeUriPost"
+      }, {
+        "@id" : "ldpt:DirectContainer-AcceptPostResponseHeader"
+      }, {
+        "@id" : "ldpt:DirectContainer-DeleteRemovesContainmentTriple"
+      }, {
+        "@id" : "ldpt:DirectContainer-RelativeUriResolutionPut"
+      }, {
+        "@id" : "ldpt:DirectContainer-PutReplacesResource"
+      }, {
+        "@id" : "ldpt:DirectContainer-PutSimpleUpdate"
+      }, {
+        "@id" : "ldpt:DirectContainer-GetResource"
+      }, {
+        "@id" : "ldpt:DirectContainer-AllowMultipleRdfTypes"
+      }, {
+        "@id" : "ldpt:DirectContainer-ChangeRdfTypeValue"
+      }, {
+        "@id" : "ldpt:DirectContainer-RestrictClientInference"
+      }, {
+        "@id" : "ldpt:DirectContainer-GetResourcePreservesTriples"
+      }, {
+        "@id" : "ldpt:DirectContainer-AllowResponsesFromServer"
+      }, {
+        "@id" : "ldpt:DirectContainer-GetResourceAcceptTurtle"
+      }, {
+        "@id" : "ldpt:DirectContainer-PublishConstraintsReadOnlyProp"
+      }, {
+        "@id" : "ldpt:DirectContainer-PublishConstraintsUnknownProp"
+      }, {
+        "@id" : "ldpt:DirectContainer-PutReadOnlyProperties4xxStatus"
+      }, {
+        "@id" : "ldpt:DirectContainer-PutPropertiesNotPersisted"
+      }, {
+        "@id" : "ldpt:DirectContainer-IsHttp11Server"
+      }, {
+        "@id" : "ldpt:DirectContainer-IsHttp11Manual"
+      }, {
+        "@id" : "ldpt:DirectContainer-ETagHeadersGet"
+      }, {
+        "@id" : "ldpt:DirectContainer-ETagHeadersHead"
+      }, {
+        "@id" : "ldpt:DirectContainer-LdpLinkHeader"
+      }, {
+        "@id" : "ldpt:DirectContainer-GetResponseHeaders"
+      }, {
+        "@id" : "ldpt:DirectContainer-ConditionFailedStatusCode"
+      }, {
+        "@id" : "ldpt:DirectContainer-PreconditionRequiredStatusCode"
+      }, {
+        "@id" : "ldpt:DirectContainer-PutBadETag"
+      }, {
+        "@id" : "ldpt:DirectContainer-Head"
+      }, {
+        "@id" : "ldpt:DirectContainer-AcceptPatchHeader"
+      }, {
+        "@id" : "ldpt:DirectContainer-Options"
+      }, {
+        "@id" : "ldpt:DirectContainer-OptionsAllowHeader"
+      } ]
+    },
+    "mf:name" : "DirectContainer (MUST)"
+  }, {
+    "@id" : "ldpt:DirectContainer-MemberRelationOrIsMemberOfRelationTripleExists",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.194Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "Each LDP Direct Container representation must contain exactly one triple whose subject is the LDPC URI, and whose predicate is either ldp:hasMemberRelation or ldp:isMemberOfRelation. The object of the triple is constrained by other sections, such as ldp:hasMemberRelation or ldp:isMemberOfRelation, based on the membership triple pattern used by the container.",
+    "rdfs:label" : "DirectContainer-MemberRelationOrIsMemberOfRelationTripleExists",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpdc-containtriples"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-MemberRelationOrIsMemberOfRelationTripleExists",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t187"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:DirectContainer-MemberRelationOrIsMemberOfRelationTripleExists"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-MemberResourceTriple",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.193Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "Each LDP Direct Container representation MUST contain exactly one triple whose subject is the LDPC URI, whose predicate is the ldp:membershipResource, and whose object is the LDPC's membership-constant-URI. Commonly the LDPC's URI is the membership-constant-URI, but LDP does not require this.",
+    "rdfs:label" : "DirectContainer-MemberResourceTriple",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpdc-containres"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-MemberResourceTriple",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t509"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:DirectContainer-MemberResourceTriple"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-NoRdfBagSeqOrList",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.209Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDPC representations SHOULD NOT use RDF container types rdf:Bag, rdf:Seq or rdf:List.",
+    "rdfs:label" : "DirectContainer-NoRdfBagSeqOrList",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-nordfcontainertypes"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-NoRdfBagSeqOrList",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t32"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-NoRdfBagSeqOrList"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-NullRelativeUriPost",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.201Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "In RDF representations, LDP servers MUST interpret the null relative URI for the subject of triples in the LDPR representation in the request entity body as referring to the entity in the request body. Commonly, that entity is the model for the “to be created” LDPR, so triples whose subject is the null relative URI will usually result in triples in the created resource whose subject is the created resource.",
+    "rdfs:label" : "DirectContainer-NullRelativeUriPost",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-rdfnullrel"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-NullRelativeUriPost",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t450"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-NullRelativeUriPost"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-OTHERManifest",
+    "http://purl.org/dc/elements/1.1/title" : "DirectContainer (OTHER)",
+    "rdf:type" : {
+      "@id" : "mf:Manifest"
+    },
+    "rdfs:comment" : "LDP Direct Container tests. No official conformance status.",
+    "mf:entries" : {
+      "@list" : [ {
+        "@id" : "ldpt:DirectContainer-UseMemberPredicate"
+      } ]
+    },
+    "mf:name" : "DirectContainer (OTHER)"
+  }, {
+    "@id" : "ldpt:DirectContainer-Options",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.233Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST support the HTTP OPTIONS method. ",
+    "rdfs:label" : "DirectContainer-Options",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-options-must"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-Options",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t103"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonResource-Options"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-OptionsAllowHeader",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.233Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST indicate their support for HTTP Methods by responding to a HTTP OPTIONS request on the LDPR’s URL with the HTTP Method tokens in the HTTP response header Allow. ",
+    "rdfs:label" : "DirectContainer-OptionsAllowHeader",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-options-allow"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-OptionsAllowHeader",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t433"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonResource-OptionsAllowHeader"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-PatchMethod",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.206Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers are RECOMMENDED to support HTTP PATCH as the preferred method for updating an LDPC's empty-container triples. ",
+    "rdfs:label" : "DirectContainer-PatchMethod",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-patch-req"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-PatchMethod",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t361"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-PatchMethod"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-PostContainer",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.198Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "When a successful HTTP POST request to an LDPC results in the creation of an LDPR, a containment triple MUST be added to the state of LDPC.",
+    "rdfs:label" : "DirectContainer-PostContainer",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-createdmbr-contains"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-PostContainer",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t226"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-PostContainer"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-PostJsonLd",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.208Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers SHOULD accept a request entity body with a request header of Content-Type with value of application/ld+json [JSON-LD].",
+    "rdfs:label" : "DirectContainer-PostJsonLd",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-jsonld"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-PostJsonLd",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t320"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-PostJsonLd"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-PostNoSlug",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.201Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers SHOULD assign the URI for the resource to be created using server application specific rules in the absence of a client hint.",
+    "rdfs:label" : "DirectContainer-PostNoSlug",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-serverassignuri"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-PostNoSlug",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t523"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-PostNoSlug"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-PostResourceUpdatesTriples",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.195Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "When a successful HTTP POST request to an LDPC results in the creation of an LDPR, the LDPC MUST update its membership triples to reflect that addition, and the resulting membership triple MUST be consistent with any LDP-defined predicates it exposes.",
+    "rdfs:label" : "DirectContainer-PostResourceUpdatesTriples",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpdc-post-createdmbr-member"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-PostResourceUpdatesTriples",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t6"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:DirectContainer-PostResourceUpdatesTriples"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-PostResponseStatusAndLocation",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.198Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "If the resource was created successfully, LDP servers MUST respond with status code 201 (Created) and the Location header set to the new resource’s URL. Clients shall not expect any representation in the response entity body on a 201 (Created) response.",
+    "rdfs:label" : "DirectContainer-PostResponseStatusAndLocation",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-created201"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-PostResponseStatusAndLocation",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t57"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-PostResponseStatusAndLocation"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-PreconditionRequiredStatusCode",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.231Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST respond with status code 412 (Condition Failed) if ETags fail to match when there are no other errors with the request [HTTP11]. LDP servers that require conditional requests MUST respond with status code 428 (Precondition Required) when the absence of a precondition is the only reason for rejecting the request [RFC6585].",
+    "rdfs:label" : "DirectContainer-PreconditionRequiredStatusCode",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-precond"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-PreconditionRequiredStatusCode",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t286"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonResource-PreconditionRequiredStatusCode"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-PreferContainmentTriples",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.209Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers SHOULD respect all of a client's LDP-defined hints, for example which subsets of LDP-defined state the client is interested in processing, to influence the set of triples returned in representations of an LDPC, particularly for large LDPCs. See also [LDP-PAGING].",
+    "rdfs:label" : "DirectContainer-PreferContainmentTriples",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-prefer"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-PreferContainmentTriples",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t66"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-PreferContainmentTriples"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-PreferMembershipTriples",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.196Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers SHOULD respect all of a client's LDP-defined hints, for example which subsets of LDP-defined state the client is interested in processing, to influence the set of triples returned in representations of an LDPC, particularly for large LDPCs. See also [LDP-PAGING].",
+    "rdfs:label" : "DirectContainer-PreferMembershipTriples",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-prefer"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-PreferMembershipTriples",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t284"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:DirectContainer-PreferMembershipTriples"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-PublishConstraintsReadOnlyProp",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.223Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST publish any constraints on LDP clients’ ability to create or update LDPRs, by adding a Link header with rel='describedby' [RFC5988] to all responses to requests which fail due to violation of those constraints.",
+    "rdfs:label" : "DirectContainer-PublishConstraintsReadOnlyProp",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-pubclireqs"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-PublishConstraintsReadOnlyProp",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t374"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-PublishConstraintsReadOnlyProp"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-PublishConstraintsUnknownProp",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.223Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST publish any constraints on LDP clients’ ability to create or update LDPRs, by adding a Link header with rel='describedby' [RFC5988] to all responses to requests which fail due to violation of those constraints.",
+    "rdfs:label" : "DirectContainer-PublishConstraintsUnknownProp",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-pubclireqs"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-PublishConstraintsUnknownProp",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t28"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-PublishConstraintsUnknownProp"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-PutBadETag",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.231Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST respond with status code 412 (Condition Failed) if ETags fail to match when there are no other errors with the request [HTTP11]. LDP servers that require conditional requests MUST respond with status code 428 (Precondition Required) when the absence of a precondition is the only reason for rejecting the request [RFC6585].",
+    "rdfs:label" : "DirectContainer-PutBadETag",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-precond"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-PutBadETag",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t122"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonResource-PutBadETag"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-PutPropertiesNotPersisted",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.225Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "If an otherwise valid HTTP PUT request is received that contains properties the server chooses not to persist, e.g. unknown content, LDP servers MUST respond with an appropriate 4xx range status code [HTTP11].",
+    "rdfs:label" : "DirectContainer-PutPropertiesNotPersisted",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-put-failed"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-PutPropertiesNotPersisted",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t189"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-PutPropertiesNotPersisted"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-PutReadOnlyProperties4xxStatus",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.224Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "If an otherwise valid HTTP PUT request is received that attempts to change properties the server does not allow clients to modify, LDP servers MUST respond with a 4xx range status code (typically 409 Conflict)",
+    "rdfs:label" : "DirectContainer-PutReadOnlyProperties4xxStatus",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-put-servermanagedprops"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-PutReadOnlyProperties4xxStatus",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t337"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-PutReadOnlyProperties4xxStatus"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-PutReplacesResource",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.212Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "If a HTTP PUT is accepted on an existing resource, LDP servers MUST replace the entire persistent state of the identified resource with the entity representation in the body of the request.",
+    "rdfs:label" : "DirectContainer-PutReplacesResource",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-replaceall"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-PutReplacesResource",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t344"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-PutReplacesResource"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-PutRequiresIfMatch",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.23Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP clients SHOULD use the HTTP If-Match header and HTTP ETags to ensure it isn’t modifying a resource that has changed since the client last retrieved its representation. LDP servers SHOULD require the HTTP If-Match header and HTTP ETags to detect collisions.",
+    "rdfs:label" : "DirectContainer-PutRequiresIfMatch",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-precond"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-PutRequiresIfMatch",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t423"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonResource-PutRequiresIfMatch"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-PutSimpleUpdate",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.213Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers SHOULD allow clients to update resources without requiring detailed knowledge of server-specific constraints. This is a consequence of the requirement to enable simple creation and modification of LDPRs.",
+    "rdfs:label" : "DirectContainer-PutSimpleUpdate",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-simpleupdate"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-PutSimpleUpdate",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t223"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-PutSimpleUpdate"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-PutToCreate",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.196Z"
+    },
+    "dcterms:subject" : "MAY",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MAY choose to allow the creation of new resources using HTTP PUT.",
+    "rdfs:label" : "DirectContainer-PutToCreate",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-create"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-PutToCreate",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t54"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MAY"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-PutToCreate"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-RdfTypeLdpContainer",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.207Z"
+    },
+    "dcterms:subject" : "MAY",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "The representation of a LDPC MAY have an rdf:type of ldp:Container for Linked Data Platform Container. Non-normative note: LDPCs might have additional types, like any LDP-RS. ",
+    "rdfs:label" : "DirectContainer-RdfTypeLdpContainer",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-typecontainer"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-RdfTypeLdpContainer",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t511"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MAY"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-RdfTypeLdpContainer"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-ReUseVocabularies",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.216Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP-RSs SHOULD 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.",
+    "rdfs:label" : "DirectContainer-ReUseVocabularies",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-gen-reusevocab"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-ReUseVocabularies",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t491"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-ReUseVocabularies"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-RejectPutModifyingContainmentTriples",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.204Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers SHOULD NOT allow HTTP PUT to update an LDPC’s containment triples; if the server receives such a request, it SHOULD respond with a 409 (Conflict) status code.",
+    "rdfs:label" : "DirectContainer-RejectPutModifyingContainmentTriples",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-put-mbrprops"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-RejectPutModifyingContainmentTriples",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t11"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-RejectPutModifyingContainmentTriples"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-RelativeUriResolutionPost",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.197Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST assign the default base-URI for [RFC3987] relative-URI resolution to be the HTTP Request-URI when the resource already exists, and to the URI of the created resource when the request results in the creation of a new resource.",
+    "rdfs:label" : "DirectContainer-RelativeUriResolutionPost",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-defbaseuri"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-RelativeUriResolutionPost",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t492"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-RelativeUriResolutionPost"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-RelativeUriResolutionPut",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.211Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST assign the default base-URI for [RFC3987] relative-URI resolution to be the HTTP Request-URI when the resource already exists, and to the URI of the created resource when the request results in the creation of a new resource.",
+    "rdfs:label" : "DirectContainer-RelativeUriResolutionPut",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-defbaseuri"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-RelativeUriResolutionPut",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t252"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-RelativeUriResolutionPut"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-RequestedInteractionModelCreateNotAllowed",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.199Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers that successfully create a resource from a RDF representation in the request entity body MUST honor the client's requested interaction model(s). The created resource can be thought of as an RDF named graph [rdf11-concepts]. If any model cannot be honored, the server MUST fail the request.",
+    "rdfs:label" : "DirectContainer-RequestedInteractionModelCreateNotAllowed",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-createrdf"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-RequestedInteractionModelCreateNotAllowed",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t55"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-RequestedInteractionModelCreateNotAllowed"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-RequestedInteractionModelHeaders",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.199Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers that successfully create a resource from a RDF representation in the request entity body MUST honor the client's requested interaction model(s). The created resource can be thought of as an RDF named graph [rdf11-concepts]. If any model cannot be honored, the server MUST fail the request.",
+    "rdfs:label" : "DirectContainer-RequestedInteractionModelHeaders",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-createrdf"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-RequestedInteractionModelHeaders",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t282"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-RequestedInteractionModelHeaders"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-ResponsePropertiesNotPersisted",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.226Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers SHOULD 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 section 4.2.1 General.",
+    "rdfs:label" : "DirectContainer-ResponsePropertiesNotPersisted",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-put-failed"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-ResponsePropertiesNotPersisted",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t112"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-ResponsePropertiesNotPersisted"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-RestrictClientInference",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.219Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST NOT 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 [rdf11-concepts]. The practical implication is that all content defined by LDP must be explicitly represented, unless noted otherwise within this document.",
+    "rdfs:label" : "DirectContainer-RestrictClientInference",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-gen-noinferencing"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-RestrictClientInference",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t496"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-RestrictClientInference"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-RestrictPutReUseUri",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.205Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers that allow LDPR creation via PUT SHOULD NOT re-use URIs. For RDF representations (LDP-RSs),the created resource can be thought of as an RDF named graph [rdf11-concepts].",
+    "rdfs:label" : "DirectContainer-RestrictPutReUseUri",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-put-create"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-RestrictPutReUseUri",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t456"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-RestrictPutReUseUri"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-RestrictUriReUseNoSlug",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.203Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers that allow member creation via POST SHOULD NOT re-use URIs.",
+    "rdfs:label" : "DirectContainer-RestrictUriReUseNoSlug",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-dontreuseuris"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-RestrictUriReUseNoSlug",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t299"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-RestrictUriReUseNoSlug"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-RestrictUriReUseSlug",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.202Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers that allow member creation via POST SHOULD NOT re-use URIs.",
+    "rdfs:label" : "DirectContainer-RestrictUriReUseSlug",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-dontreuseuris"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-RestrictUriReUseSlug",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t145"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-RestrictUriReUseSlug"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-SHOULDManifest",
+    "http://purl.org/dc/elements/1.1/title" : "DirectContainer (SHOULD)",
+    "rdf:type" : {
+      "@id" : "mf:Manifest"
+    },
+    "rdfs:comment" : "LDP Direct Container tests. SHOULD conformance tests.",
+    "mf:entries" : {
+      "@list" : [ {
+        "@id" : "ldpt:DirectContainer-UseMemberPredicate"
+      }, {
+        "@id" : "ldpt:DirectContainer-PreferMembershipTriples"
+      }, {
+        "@id" : "ldpt:DirectContainer-ContentTypeHeader"
+      }, {
+        "@id" : "ldpt:DirectContainer-PostNoSlug"
+      }, {
+        "@id" : "ldpt:DirectContainer-CreateWithoutConstraints"
+      }, {
+        "@id" : "ldpt:DirectContainer-RestrictUriReUseSlug"
+      }, {
+        "@id" : "ldpt:DirectContainer-RestrictUriReUseNoSlug"
+      }, {
+        "@id" : "ldpt:DirectContainer-RejectPutModifyingContainmentTriples"
+      }, {
+        "@id" : "ldpt:DirectContainer-RestrictPutReUseUri"
+      }, {
+        "@id" : "ldpt:DirectContainer-PatchMethod"
+      }, {
+        "@id" : "ldpt:DirectContainer-PostJsonLd"
+      }, {
+        "@id" : "ldpt:DirectContainer-NoRdfBagSeqOrList"
+      }, {
+        "@id" : "ldpt:DirectContainer-PreferContainmentTriples"
+      }, {
+        "@id" : "ldpt:DirectContainer-ClientPostToCreate"
+      }, {
+        "@id" : "ldpt:DirectContainer-ContainsRdfType"
+      }, {
+        "@id" : "ldpt:DirectContainer-ReUseVocabularies"
+      }, {
+        "@id" : "ldpt:DirectContainer-UseStandardVocabularies"
+      }, {
+        "@id" : "ldpt:DirectContainer-ServerOpen"
+      }, {
+        "@id" : "ldpt:DirectContainer-JsonLdRepresentation"
+      }, {
+        "@id" : "ldpt:DirectContainer-4xxErrorHasResponseBody"
+      }, {
+        "@id" : "ldpt:DirectContainer-ResponsePropertiesNotPersisted"
+      }, {
+        "@id" : "ldpt:DirectContainer-PutRequiresIfMatch"
+      } ]
+    },
+    "mf:name" : "DirectContainer (SHOULD)"
+  }, {
+    "@id" : "ldpt:DirectContainer-ServerHonorsSlug",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.207Z"
+    },
+    "dcterms:subject" : "MAY",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MAY allow clients to suggest the URI for a resource created through POST, using the HTTP Slug header as defined in [RFC5023]. 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.",
+    "rdfs:label" : "DirectContainer-ServerHonorsSlug",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-slug"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-ServerHonorsSlug",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t205"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MAY"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-ServerHonorsSlug"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-ServerOpen",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.218Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP clients SHOULD always assume that the set of predicates for a LDP-RS 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 LDP-RS is not limited to any pre-defined set.",
+    "rdfs:label" : "DirectContainer-ServerOpen",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-cli-openpreds"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-ServerOpen",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t445"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-ServerOpen"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-TypeRdfSource",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.215Z"
+    },
+    "dcterms:subject" : "MAY",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "The representation of a LDP-RS MAY have an rdf:type of ldp:RDFSource for Linked Data Platform RDF Source.",
+    "rdfs:label" : "DirectContainer-TypeRdfSource",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-rdftype"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-TypeRdfSource",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t251"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MAY"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-TypeRdfSource"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-UseMemberPredicate",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.193Z"
+    },
+    "dcterms:subject" : "SHOULD, ldpMember",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP Direct Containers SHOULD use the ldp:member predicate as an LDPC's membership predicate if there is no obvious predicate from an application vocabulary to use.",
+    "rdfs:label" : "DirectContainer-UseMemberPredicate",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpdc-mbrpred"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-UseMemberPredicate",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t497"
+    },
+    "ldpt:conformanceLevel" : [ {
+      "@id" : "ldpt:SHOULD"
+    }, {
+      "@id" : "ldpt:ldpMember"
+    } ],
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:DirectContainer-UseMemberPredicate"
+    }
+  }, {
+    "@id" : "ldpt:DirectContainer-UseStandardVocabularies",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.216Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP-RSs predicates SHOULD use standard vocabularies such as Dublin Core [DC-TERMS], RDF [rdf11-concepts] and RDF Schema [rdf-schema], whenever possible.",
+    "rdfs:label" : "DirectContainer-UseStandardVocabularies",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-gen-reusevocabsuchas"
+    },
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-UseStandardVocabularies",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t265"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-UseStandardVocabularies"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-4xxErrorHasResponseBody",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.29Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers SHOULD 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.",
+    "rdfs:label" : "IndirectContainer-4xxErrorHasResponseBody",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-put-servermanagedprops"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-4xxErrorHasResponseBody",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t429"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-4xxErrorHasResponseBody"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-AcceptPatchHeader",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.297Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers that support PATCH MUST include an Accept-Patch HTTP response header [RFC5789] on HTTP OPTIONS requests, listing patch document media type(s) supported by the server. ",
+    "rdfs:label" : "IndirectContainer-AcceptPatchHeader",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-patch-acceptpatch"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-AcceptPatchHeader",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t370"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonResource-AcceptPatchHeader"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-AcceptPostResponseHeader",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.273Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers that support POST MUST include an Accept-Post response header on HTTP OPTIONS responses, listing post document media type(s) supported by the server.",
+    "rdfs:label" : "IndirectContainer-AcceptPostResponseHeader",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-acceptposthdr"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-AcceptPostResponseHeader",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t501"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-AcceptPostResponseHeader"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-AcceptTurtle",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.27Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST accept a request entity body with a request header of Content-Type with value of text/turtle [turtle].",
+    "rdfs:label" : "IndirectContainer-AcceptTurtle",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-turtle"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-AcceptTurtle",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t345"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-AcceptTurtle"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-AllowMultipleRdfTypes",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.284Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "In the absence of special knowledge of the application or domain, LDP clients MUST assume that any LDP-RS can have multiple values for rdf:type.",
+    "rdfs:label" : "IndirectContainer-AllowMultipleRdfTypes",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldp-cli-multitype"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-AllowMultipleRdfTypes",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t399"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-AllowMultipleRdfTypes"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-AllowResponsesFromServer",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.286Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP clients MUST be capable of processing responses formed by an LDP server that ignores hints, including LDP-defined hints.",
+    "rdfs:label" : "IndirectContainer-AllowResponsesFromServer",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-cli-hints-ignorable"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-AllowResponsesFromServer",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t519"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-AllowResponsesFromServer"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-ChangeRdfTypeValue",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.284Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "In the absence of special knowledge of the application or domain, LDP clients MUST assume that the rdf:type values of a given LDP-RS can change over time.",
+    "rdfs:label" : "IndirectContainer-ChangeRdfTypeValue",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-cli-typeschange"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-ChangeRdfTypeValue",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t202"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-ChangeRdfTypeValue"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-ClientMayProvideHints",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.287Z"
+    },
+    "dcterms:subject" : "MAY",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP clients MAY provide LDP-defined hints that allow servers to optimize the content of responses. section 7.2 Preferences on the Prefer Request Header defines hints that apply to LDP-RSs. ",
+    "rdfs:label" : "IndirectContainer-ClientMayProvideHints",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-cli-can-hint"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-ClientMayProvideHints",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t506"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MAY"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-ClientMayProvideHints"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-ClientPostToCreate",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.279Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDPC clients SHOULD create member resources by submitting a representation as the entity body of the HTTP POST to a known LDPC.",
+    "rdfs:label" : "IndirectContainer-ClientPostToCreate",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-created201"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-ClientPostToCreate",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t91"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-ClientPostToCreate"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-ConditionFailedStatusCode",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.295Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST respond with status code 412 (Condition Failed) if ETags fail to match when there are no other errors with the request [HTTP11]. LDP servers that require conditional requests MUST respond with status code 428 (Precondition Required) when the absence of a precondition is the only reason for rejecting the request [RFC6585].",
+    "rdfs:label" : "IndirectContainer-ConditionFailedStatusCode",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-precond"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-ConditionFailedStatusCode",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t131"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonResource-ConditionFailedStatusCode"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-ContainerSupportsHttpLinkHeader",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.264Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers exposing LDPCs MUST advertise their LDP support by exposing a HTTP Link header with a target URI matching the type of container (see below) the server supports, and a link relation type of type (that is, rel='type') in all responses to requests made to the LDPC's HTTP Request-URI.",
+    "rdfs:label" : "IndirectContainer-ContainerSupportsHttpLinkHeader",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-linktypehdr"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-ContainerSupportsHttpLinkHeader",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t43"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:IndirectContainer-ContainerSupportsHttpLinkHeader"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-ContainsLdpcUri",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.265Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP Indirect Containers MUST contain exactly one triple whose subject is the LDPC URI, whose predicate is ldp:insertedContentRelation, and whose object ICR describes how the member-derived-URI in the container's membership triples is chosen.",
+    "rdfs:label" : "IndirectContainer-ContainsLdpcUri",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpic-indirectmbr"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-ContainsLdpcUri",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t130"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:IndirectContainer-ContainsLdpcUri"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-ContainsRdfType",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.282Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP-RSs representations SHOULD have at least one rdf:type set explicitly. This makes the representations much more useful to client applications that don’t support inferencing.",
+    "rdfs:label" : "IndirectContainer-ContainsRdfType",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-gen-atleast1rdftype"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-ContainsRdfType",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t150"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-ContainsRdfType"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-ContentTypeHeader",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.27Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers SHOULD use the Content-Type request header to determine the representation format when the request has an entity body.",
+    "rdfs:label" : "IndirectContainer-ContentTypeHeader",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-contenttype"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-ContentTypeHeader",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t29"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-ContentTypeHeader"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-CreateIndirectContainer",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.264Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "Each LDP Indirect Container MUST also be a conforming LDP Direct Container in section 5.4 Direct along the following restrictions.",
+    "rdfs:label" : "IndirectContainer-CreateIndirectContainer",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpic-are-ldpcs"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-CreateIndirectContainer",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t109"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:IndirectContainer-CreateIndirectContainer"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-CreateWithoutConstraints",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.272Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers SHOULD 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 LDPRs. LDP servers expose these application-specific constraints as described in section 4.2.1 General.",
+    "rdfs:label" : "IndirectContainer-CreateWithoutConstraints",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-mincontraints"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-CreateWithoutConstraints",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t153"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-CreateWithoutConstraints"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-DeleteRemovesContainmentTriple",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.275Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "When an LDPR identified by the object of a containment triple is deleted, the LDPC server MUST also remove the LDPR from the containing LDPC by removing the corresponding containment triple.",
+    "rdfs:label" : "IndirectContainer-DeleteRemovesContainmentTriple",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-del-contremovesconttriple"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-DeleteRemovesContainmentTriple",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t73"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-DeleteRemovesContainmentTriple"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-ETagHeadersGet",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.292Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP server responses MUST use entity tags (either weak or strong ones) as response ETag header values.",
+    "rdfs:label" : "IndirectContainer-ETagHeadersGet",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-etags"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-ETagHeadersGet",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t520"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonResource-ETagHeadersGet"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-ETagHeadersHead",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.293Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP server responses MUST use entity tags (either weak or strong ones) as response ETag header values.",
+    "rdfs:label" : "IndirectContainer-ETagHeadersHead",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-etags"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-ETagHeadersHead",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t319"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonResource-ETagHeadersHead"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-GetResource",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.282Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST provide an RDF representation for LDP-RSs. The HTTP Request-URI of the LDP-RS is typically the subject of most triples in the response.",
+    "rdfs:label" : "IndirectContainer-GetResource",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-gen-rdf"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-GetResource",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t468"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-GetResource"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-GetResourceAcceptTurtle",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.287Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers must provide a text/turtle representation of the requested LDP-RS whenever HTTP content negotiation does not force another outcome [turtle]. In other words, if the server receives a GET request whose Request-URI identifies a LDP-RS, and either text/turtle has the highest relative quality factor (q= value) in the Accept request header or that header is absent, then an LDP server has to respond with Turtle.",
+    "rdfs:label" : "IndirectContainer-GetResourceAcceptTurtle",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-get-turtle"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-GetResourceAcceptTurtle",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t373"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-GetResourceAcceptTurtle"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-GetResourcePreservesTriples",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.286Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "A LDP client MUST preserve all triples retrieved from an LDP-RS using HTTP GET that it doesn’t change whether it understands the predicates or not, when its intent is to perform an update using HTTP PUT. The use of HTTP PATCH instead of HTTP PUT for update avoids this burden for clients [RFC5789]. ",
+    "rdfs:label" : "IndirectContainer-GetResourcePreservesTriples",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-cli-preservetriples"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-GetResourcePreservesTriples",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t301"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-GetResourcePreservesTriples"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-GetResponseHeaders",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.294Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST support the HTTP response headers defined in section 4.2.8 HTTP OPTIONS. ",
+    "rdfs:label" : "IndirectContainer-GetResponseHeaders",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-get-options"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-GetResponseHeaders",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t23"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonResource-GetResponseHeaders"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-Head",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.296Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST support the HTTP HEAD method. ",
+    "rdfs:label" : "IndirectContainer-Head",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-head-must"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-Head",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t341"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonResource-Head"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-IsHttp11Manual",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.292Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST at least be HTTP/1.1 conformant servers [HTTP11].",
+    "rdfs:label" : "IndirectContainer-IsHttp11Manual",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-http"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-IsHttp11Manual",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t442"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonResource-IsHttp11Manual"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-IsHttp11Server",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.291Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST at least be HTTP/1.1 conformant servers [HTTP11].",
+    "rdfs:label" : "IndirectContainer-IsHttp11Server",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-http"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-IsHttp11Server",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t113"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonResource-IsHttp11Server"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-JsonLdRepresentation",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.288Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers SHOULD offer a application/ld+json representation of the requested LDP-RS [JSON-LD]. ",
+    "rdfs:label" : "IndirectContainer-JsonLdRepresentation",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-get-jsonld"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-JsonLdRepresentation",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t217"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-JsonLdRepresentation"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-LdpLinkHeader",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.293Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers exposing LDPRs MUST advertise their LDP support by exposing a HTTP Link header with a target URI of http://www.w3.org/ns/ldp#Resource, and a link relation type of type (that is, rel='type') in all responses to requests made to the LDPR's HTTP Request-URI.",
+    "rdfs:label" : "IndirectContainer-LdpLinkHeader",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-linktypehdr"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-LdpLinkHeader",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t287"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonResource-LdpLinkHeader"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-MAYManifest",
+    "http://purl.org/dc/elements/1.1/title" : "IndirectContainer (MAY)",
+    "rdf:type" : {
+      "@id" : "mf:Manifest"
+    },
+    "rdfs:comment" : "LDP Indirect Container tests. MAY conformance tests.",
+    "mf:entries" : {
+      "@list" : [ {
+        "@id" : "ldpt:IndirectContainer-PutToCreate"
+      }, {
+        "@id" : "ldpt:IndirectContainer-RdfTypeLdpContainer"
+      }, {
+        "@id" : "ldpt:IndirectContainer-ServerHonorsSlug"
+      }, {
+        "@id" : "ldpt:IndirectContainer-TypeRdfSource"
+      }, {
+        "@id" : "ldpt:IndirectContainer-ClientMayProvideHints"
+      } ]
+    },
+    "mf:name" : "IndirectContainer (MAY)"
+  }, {
+    "@id" : "ldpt:IndirectContainer-MUSTManifest",
+    "http://purl.org/dc/elements/1.1/title" : "IndirectContainer (MUST)",
+    "rdf:type" : {
+      "@id" : "mf:Manifest"
+    },
+    "rdfs:comment" : "LDP Indirect Container tests. MUST conformance tests.",
+    "mf:entries" : {
+      "@list" : [ {
+        "@id" : "ldpt:IndirectContainer-ContainerSupportsHttpLinkHeader"
+      }, {
+        "@id" : "ldpt:IndirectContainer-CreateIndirectContainer"
+      }, {
+        "@id" : "ldpt:IndirectContainer-ContainsLdpcUri"
+      }, {
+        "@id" : "ldpt:IndirectContainer-PostResource"
+      }, {
+        "@id" : "ldpt:IndirectContainer-RelativeUriResolutionPost"
+      }, {
+        "@id" : "ldpt:IndirectContainer-PostResponseStatusAndLocation"
+      }, {
+        "@id" : "ldpt:IndirectContainer-PostContainer"
+      }, {
+        "@id" : "ldpt:IndirectContainer-RequestedInteractionModelCreateNotAllowed"
+      }, {
+        "@id" : "ldpt:IndirectContainer-RequestedInteractionModelHeaders"
+      }, {
+        "@id" : "ldpt:IndirectContainer-AcceptTurtle"
+      }, {
+        "@id" : "ldpt:IndirectContainer-NullRelativeUriPost"
+      }, {
+        "@id" : "ldpt:IndirectContainer-AcceptPostResponseHeader"
+      }, {
+        "@id" : "ldpt:IndirectContainer-DeleteRemovesContainmentTriple"
+      }, {
+        "@id" : "ldpt:IndirectContainer-RelativeUriResolutionPut"
+      }, {
+        "@id" : "ldpt:IndirectContainer-PutReplacesResource"
+      }, {
+        "@id" : "ldpt:IndirectContainer-PutSimpleUpdate"
+      }, {
+        "@id" : "ldpt:IndirectContainer-GetResource"
+      }, {
+        "@id" : "ldpt:IndirectContainer-AllowMultipleRdfTypes"
+      }, {
+        "@id" : "ldpt:IndirectContainer-ChangeRdfTypeValue"
+      }, {
+        "@id" : "ldpt:IndirectContainer-RestrictClientInference"
+      }, {
+        "@id" : "ldpt:IndirectContainer-GetResourcePreservesTriples"
+      }, {
+        "@id" : "ldpt:IndirectContainer-AllowResponsesFromServer"
+      }, {
+        "@id" : "ldpt:IndirectContainer-GetResourceAcceptTurtle"
+      }, {
+        "@id" : "ldpt:IndirectContainer-PublishConstraintsReadOnlyProp"
+      }, {
+        "@id" : "ldpt:IndirectContainer-PublishConstraintsUnknownProp"
+      }, {
+        "@id" : "ldpt:IndirectContainer-PutReadOnlyProperties4xxStatus"
+      }, {
+        "@id" : "ldpt:IndirectContainer-PutPropertiesNotPersisted"
+      }, {
+        "@id" : "ldpt:IndirectContainer-IsHttp11Server"
+      }, {
+        "@id" : "ldpt:IndirectContainer-IsHttp11Manual"
+      }, {
+        "@id" : "ldpt:IndirectContainer-ETagHeadersGet"
+      }, {
+        "@id" : "ldpt:IndirectContainer-ETagHeadersHead"
+      }, {
+        "@id" : "ldpt:IndirectContainer-LdpLinkHeader"
+      }, {
+        "@id" : "ldpt:IndirectContainer-GetResponseHeaders"
+      }, {
+        "@id" : "ldpt:IndirectContainer-ConditionFailedStatusCode"
+      }, {
+        "@id" : "ldpt:IndirectContainer-PreconditionRequiredStatusCode"
+      }, {
+        "@id" : "ldpt:IndirectContainer-PutBadETag"
+      }, {
+        "@id" : "ldpt:IndirectContainer-Head"
+      }, {
+        "@id" : "ldpt:IndirectContainer-AcceptPatchHeader"
+      }, {
+        "@id" : "ldpt:IndirectContainer-Options"
+      }, {
+        "@id" : "ldpt:IndirectContainer-OptionsAllowHeader"
+      } ]
+    },
+    "mf:name" : "IndirectContainer (MUST)"
+  }, {
+    "@id" : "ldpt:IndirectContainer-NoRdfBagSeqOrList",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.278Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDPC representations SHOULD NOT use RDF container types rdf:Bag, rdf:Seq or rdf:List.",
+    "rdfs:label" : "IndirectContainer-NoRdfBagSeqOrList",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-nordfcontainertypes"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-NoRdfBagSeqOrList",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t248"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-NoRdfBagSeqOrList"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-NullRelativeUriPost",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.271Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "In RDF representations, LDP servers MUST interpret the null relative URI for the subject of triples in the LDPR representation in the request entity body as referring to the entity in the request body. Commonly, that entity is the model for the “to be created” LDPR, so triples whose subject is the null relative URI will usually result in triples in the created resource whose subject is the created resource.",
+    "rdfs:label" : "IndirectContainer-NullRelativeUriPost",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-rdfnullrel"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-NullRelativeUriPost",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t507"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-NullRelativeUriPost"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-Options",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.297Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST support the HTTP OPTIONS method. ",
+    "rdfs:label" : "IndirectContainer-Options",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-options-must"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-Options",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t190"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonResource-Options"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-OptionsAllowHeader",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.298Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST indicate their support for HTTP Methods by responding to a HTTP OPTIONS request on the LDPR’s URL with the HTTP Method tokens in the HTTP response header Allow. ",
+    "rdfs:label" : "IndirectContainer-OptionsAllowHeader",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-options-allow"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-OptionsAllowHeader",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t475"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonResource-OptionsAllowHeader"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-PatchMethod",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.276Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers are RECOMMENDED to support HTTP PATCH as the preferred method for updating an LDPC's empty-container triples. ",
+    "rdfs:label" : "IndirectContainer-PatchMethod",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-patch-req"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-PatchMethod",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t396"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-PatchMethod"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-PostContainer",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.268Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "When a successful HTTP POST request to an LDPC results in the creation of an LDPR, a containment triple MUST be added to the state of LDPC.",
+    "rdfs:label" : "IndirectContainer-PostContainer",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-createdmbr-contains"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-PostContainer",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t334"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-PostContainer"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-PostJsonLd",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.277Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers SHOULD accept a request entity body with a request header of Content-Type with value of application/ld+json [JSON-LD].",
+    "rdfs:label" : "IndirectContainer-PostJsonLd",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-jsonld"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-PostJsonLd",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t441"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-PostJsonLd"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-PostNoSlug",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.271Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers SHOULD assign the URI for the resource to be created using server application specific rules in the absence of a client hint.",
+    "rdfs:label" : "IndirectContainer-PostNoSlug",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-serverassignuri"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-PostNoSlug",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t188"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-PostNoSlug"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-PostResource",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.266Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDPCs whose ldp:insertedContentRelation triple has an object other than ldp:MemberSubject and that create new resources MUST add a triple to the container whose subject is the container's URI, whose predicate is ldp:contains, and whose object is the newly created resource's URI (which will be different from the member-derived URI in this case). This ldp:contains triple can be the only link from the container to the newly created resource in certain cases.",
+    "rdfs:label" : "IndirectContainer-PostResource",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpic-post-indirectmbrrel"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-PostResource",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t405"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:IndirectContainer-PostResource"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-PostResponseStatusAndLocation",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.267Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "If the resource was created successfully, LDP servers MUST respond with status code 201 (Created) and the Location header set to the new resource’s URL. Clients shall not expect any representation in the response entity body on a 201 (Created) response.",
+    "rdfs:label" : "IndirectContainer-PostResponseStatusAndLocation",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-created201"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-PostResponseStatusAndLocation",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t116"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-PostResponseStatusAndLocation"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-PreconditionRequiredStatusCode",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.295Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST respond with status code 412 (Condition Failed) if ETags fail to match when there are no other errors with the request [HTTP11]. LDP servers that require conditional requests MUST respond with status code 428 (Precondition Required) when the absence of a precondition is the only reason for rejecting the request [RFC6585].",
+    "rdfs:label" : "IndirectContainer-PreconditionRequiredStatusCode",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-precond"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-PreconditionRequiredStatusCode",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t452"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonResource-PreconditionRequiredStatusCode"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-PreferContainmentTriples",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.278Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers SHOULD respect all of a client's LDP-defined hints, for example which subsets of LDP-defined state the client is interested in processing, to influence the set of triples returned in representations of an LDPC, particularly for large LDPCs. See also [LDP-PAGING].",
+    "rdfs:label" : "IndirectContainer-PreferContainmentTriples",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-prefer"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-PreferContainmentTriples",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t481"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-PreferContainmentTriples"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-PublishConstraintsReadOnlyProp",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.288Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST publish any constraints on LDP clients’ ability to create or update LDPRs, by adding a Link header with rel='describedby' [RFC5988] to all responses to requests which fail due to violation of those constraints.",
+    "rdfs:label" : "IndirectContainer-PublishConstraintsReadOnlyProp",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-pubclireqs"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-PublishConstraintsReadOnlyProp",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t488"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-PublishConstraintsReadOnlyProp"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-PublishConstraintsUnknownProp",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.289Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST publish any constraints on LDP clients’ ability to create or update LDPRs, by adding a Link header with rel='describedby' [RFC5988] to all responses to requests which fail due to violation of those constraints.",
+    "rdfs:label" : "IndirectContainer-PublishConstraintsUnknownProp",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-pubclireqs"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-PublishConstraintsUnknownProp",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t58"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-PublishConstraintsUnknownProp"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-PutBadETag",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.296Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST respond with status code 412 (Condition Failed) if ETags fail to match when there are no other errors with the request [HTTP11]. LDP servers that require conditional requests MUST respond with status code 428 (Precondition Required) when the absence of a precondition is the only reason for rejecting the request [RFC6585].",
+    "rdfs:label" : "IndirectContainer-PutBadETag",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-precond"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-PutBadETag",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t273"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonResource-PutBadETag"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-PutPropertiesNotPersisted",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.29Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "If an otherwise valid HTTP PUT request is received that contains properties the server chooses not to persist, e.g. unknown content, LDP servers MUST respond with an appropriate 4xx range status code [HTTP11].",
+    "rdfs:label" : "IndirectContainer-PutPropertiesNotPersisted",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-put-failed"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-PutPropertiesNotPersisted",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t267"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-PutPropertiesNotPersisted"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-PutReadOnlyProperties4xxStatus",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.289Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "If an otherwise valid HTTP PUT request is received that attempts to change properties the server does not allow clients to modify, LDP servers MUST respond with a 4xx range status code (typically 409 Conflict)",
+    "rdfs:label" : "IndirectContainer-PutReadOnlyProperties4xxStatus",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-put-servermanagedprops"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-PutReadOnlyProperties4xxStatus",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t412"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-PutReadOnlyProperties4xxStatus"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-PutReplacesResource",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.281Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "If a HTTP PUT is accepted on an existing resource, LDP servers MUST replace the entire persistent state of the identified resource with the entity representation in the body of the request.",
+    "rdfs:label" : "IndirectContainer-PutReplacesResource",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-replaceall"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-PutReplacesResource",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t485"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-PutReplacesResource"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-PutRequiresIfMatch",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.294Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP clients SHOULD use the HTTP If-Match header and HTTP ETags to ensure it isn’t modifying a resource that has changed since the client last retrieved its representation. LDP servers SHOULD require the HTTP If-Match header and HTTP ETags to detect collisions.",
+    "rdfs:label" : "IndirectContainer-PutRequiresIfMatch",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-precond"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-PutRequiresIfMatch",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t351"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonResource-PutRequiresIfMatch"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-PutSimpleUpdate",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.281Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers SHOULD allow clients to update resources without requiring detailed knowledge of server-specific constraints. This is a consequence of the requirement to enable simple creation and modification of LDPRs.",
+    "rdfs:label" : "IndirectContainer-PutSimpleUpdate",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-simpleupdate"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-PutSimpleUpdate",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t79"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-PutSimpleUpdate"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-PutToCreate",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.266Z"
+    },
+    "dcterms:subject" : "MAY",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MAY choose to allow the creation of new resources using HTTP PUT.",
+    "rdfs:label" : "IndirectContainer-PutToCreate",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-create"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-PutToCreate",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t314"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MAY"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-PutToCreate"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-RdfTypeLdpContainer",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.276Z"
+    },
+    "dcterms:subject" : "MAY",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "The representation of a LDPC MAY have an rdf:type of ldp:Container for Linked Data Platform Container. Non-normative note: LDPCs might have additional types, like any LDP-RS. ",
+    "rdfs:label" : "IndirectContainer-RdfTypeLdpContainer",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-typecontainer"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-RdfTypeLdpContainer",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t76"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MAY"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-RdfTypeLdpContainer"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-ReUseVocabularies",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.283Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP-RSs SHOULD 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.",
+    "rdfs:label" : "IndirectContainer-ReUseVocabularies",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldprs-gen-reusevocab"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-ReUseVocabularies",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t417"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-ReUseVocabularies"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-RejectPutModifyingContainmentTriples",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.274Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers SHOULD NOT allow HTTP PUT to update an LDPC’s containment triples; if the server receives such a request, it SHOULD respond with a 409 (Conflict) status code.",
+    "rdfs:label" : "IndirectContainer-RejectPutModifyingContainmentTriples",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-put-mbrprops"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-RejectPutModifyingContainmentTriples",
+    "td:reviewStatus" : {
+      "@id" : "td:approved"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t236"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:SHOULD"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-RejectPutModifyingContainmentTriples"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-RelativeUriResolutionPost",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.267Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST assign the default base-URI for [RFC3987] relative-URI resolution to be the HTTP Request-URI when the resource already exists, and to the URI of the created resource when the request results in the creation of a new resource.",
+    "rdfs:label" : "IndirectContainer-RelativeUriResolutionPost",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-defbaseuri"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-RelativeUriResolutionPost",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t431"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-RelativeUriResolutionPost"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-RelativeUriResolutionPut",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.279Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers MUST assign the default base-URI for [RFC3987] relative-URI resolution to be the HTTP Request-URI when the resource already exists, and to the URI of the created resource when the request results in the creation of a new resource.",
+    "rdfs:label" : "IndirectContainer-RelativeUriResolutionPut",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-defbaseuri"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-RelativeUriResolutionPut",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t427"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:RdfSource-RelativeUriResolutionPut"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-RequestedInteractionModelCreateNotAllowed",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.268Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers that successfully create a resource from a RDF representation in the request entity body MUST honor the client's requested interaction model(s). The created resource can be thought of as an RDF named graph [rdf11-concepts]. If any model cannot be honored, the server MUST fail the request.",
+    "rdfs:label" : "IndirectContainer-RequestedInteractionModelCreateNotAllowed",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-createrdf"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-RequestedInteractionModelCreateNotAllowed",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t128"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-RequestedInteractionModelCreateNotAllowed"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-RequestedInteractionModelHeaders",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.269Z"
+    },
+    "dcterms:subject" : "MUST",
+    "rdf:type" : {
+      "@id" : "earl:TestCase"
+    },
+    "rdfs:comment" : "LDP servers that successfully create a resource from a RDF representation in the request entity body MUST honor the client's requested interaction model(s). The created resource can be thought of as an RDF named graph [rdf11-concepts]. If any model cannot be honored, the server MUST fail the request.",
+    "rdfs:label" : "IndirectContainer-RequestedInteractionModelHeaders",
+    "rdfs:seeAlso" : {
+      "@id" : "http://www.w3.org/TR/ldp#ldpc-post-createrdf"
+    },
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-RequestedInteractionModelHeaders",
+    "td:reviewStatus" : {
+      "@id" : "td:unreviewed"
+    },
+    "td:specificationReference" : {
+      "@id" : "_:t279"
+    },
+    "ldpt:conformanceLevel" : {
+      "@id" : "ldpt:MUST"
+    },
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "ldpt:declaredTestCase" : {
+      "@id" : "ldpt:CommonContainer-RequestedInteractionModelHeaders"
+    }
+  }, {
+    "@id" : "ldpt:IndirectContainer-ResponsePropertiesNotPersisted",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-16T15:17:40.291Z"
+    },
+    "dcterms:subject" : "SHOULD",
+    "rdf:type" : {