20-July-2014 update of test coverage
authorSteve Speicher <sspeiche@gmail.com>
Sun, 20 Jul 2014 20:11:42 -0400
changeset 717 7350cee7ab89
parent 716 a76f182b5d2c
child 718 958507744485
20-July-2014 update of test coverage
tests/reports/ldp-earl-manifest-client-only.jsonld
tests/reports/ldp-earl-manifest-client-only.ttl
tests/reports/ldp-earl-manifest.jsonld
tests/reports/ldp-earl-manifest.ttl
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/tests/reports/ldp-earl-manifest-client-only.jsonld	Sun Jul 20 20:11:42 2014 -0400
@@ -0,0 +1,1060 @@
+{
+  "@graph" : [ {
+    "@id" : "_:t104",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t11",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t111",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t130",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t138",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t144",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t150",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t153",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t154",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t155",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t156",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t158",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t159",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t17",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t25",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t27",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t33",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t50",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t62",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t63",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t78",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t81",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t83",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t84",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t85",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t92",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t98",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "ldpt:BasicContainer-AllowMultipleRdfTypes",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-18T15:57:05.197Z"
+    },
+    "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",
+    "seeAlso" : "http://www.w3.org/TR/ldp#ldp-cli-multitype",
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-AllowMultipleRdfTypes",
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t62",
+    "conformanceLevel" : "ldpt:MUST",
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "declaredTestCase" : "ldpt:RdfSource-AllowMultipleRdfTypes",
+    "ldpt:steps" : {
+      "@list" : [ "Given a client and a known RDF Source at a given URL", "Via some means, alter the rdf:type of the RDF Source by adding another rdf:type. Note it may be implementation dependent on what the server will allow and also when changed, what different behavior the client will have", "Verify that the client continues to operate as expected" ]
+    },
+    "testMethod" : "ldpt:clientOnly"
+  }, {
+    "@id" : "ldpt:BasicContainer-AllowResponsesFromServer",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-18T15:57:05.202Z"
+    },
+    "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",
+    "seeAlso" : "http://www.w3.org/TR/ldp#ldpr-cli-hints-ignorable",
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-AllowResponsesFromServer",
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t27",
+    "conformanceLevel" : "ldpt:MUST",
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "declaredTestCase" : "ldpt:RdfSource-AllowResponsesFromServer",
+    "ldpt:steps" : {
+      "@list" : [ "Determine certain hints that your server would ignore", "Form a client request that uses this hint", "Execute the request and analyze the result", "Verify that client processes request as expected" ]
+    },
+    "testMethod" : "ldpt:clientOnly"
+  }, {
+    "@id" : "ldpt:BasicContainer-ChangeRdfTypeValue",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-18T15:57:05.198Z"
+    },
+    "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",
+    "seeAlso" : "http://www.w3.org/TR/ldp#ldpr-cli-typeschange",
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-ChangeRdfTypeValue",
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t84",
+    "conformanceLevel" : "ldpt:MUST",
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "declaredTestCase" : "ldpt:RdfSource-ChangeRdfTypeValue",
+    "ldpt:steps" : {
+      "@list" : [ "Given a client and a known RDF Source at a given URL", "Via some means, alter the rdf:type of the RDF Source by adding or removing a rdf:type triple. Note it may be implementation dependent on what the server will allow and also when changed, what different behavior the client will have", "Verify that the client continues to operate as expected" ]
+    },
+    "testMethod" : "ldpt:clientOnly"
+  }, {
+    "@id" : "ldpt:BasicContainer-ClientMayProvideHints",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-18T15:57:05.204Z"
+    },
+    "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",
+    "seeAlso" : "http://www.w3.org/TR/ldp#ldpr-cli-can-hint",
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-ClientMayProvideHints",
+    "reviewStatus" : "td:unreviewed",
+    "specificationReference" : "_:t92",
+    "conformanceLevel" : "ldpt:MAY",
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "declaredTestCase" : "ldpt:RdfSource-ClientMayProvideHints",
+    "ldpt:steps" : {
+      "@list" : [ "Given a URL to a known RDF Source", "Configure the client application, if needed, to use the Prefer header to omit either containment or membership triples", "Use the client to send the GET request", "Monitor to ensure the server receives the hint", "Monitor to ensure the server honors the hing", "Verify the client behavior receives the optimized response" ]
+    },
+    "testMethod" : "ldpt:clientOnly"
+  }, {
+    "@id" : "ldpt:BasicContainer-ClientPostToCreate",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-18T15:57:05.188Z"
+    },
+    "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",
+    "seeAlso" : "http://www.w3.org/TR/ldp#ldpc-post-created201",
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-ClientPostToCreate",
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t33",
+    "conformanceLevel" : "ldpt:SHOULD",
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "declaredTestCase" : "ldpt:CommonContainer-ClientPostToCreate",
+    "ldpt:steps" : {
+      "@list" : [ "Given a container URL and POST is supported", "Monitor the client's request to ensure a POST request is sent", "Verify the response has a response status code of 201-Created and Location header with URL of created resource" ]
+    },
+    "testMethod" : "ldpt:clientOnly"
+  }, {
+    "@id" : "ldpt:BasicContainer-GetResourcePreservesTriples",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-18T15:57:05.201Z"
+    },
+    "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",
+    "seeAlso" : "http://www.w3.org/TR/ldp#ldpr-cli-preservetriples",
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-GetResourcePreservesTriples",
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t50",
+    "conformanceLevel" : "ldpt:MUST",
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "declaredTestCase" : "ldpt:RdfSource-GetResourcePreservesTriples",
+    "ldpt:steps" : {
+      "@list" : [ "Given a URL for a RDF Source, have client fetch a representation", "Observe the results of the fetch, either by application provided means or monitoring the network", "Given the client application interface, modify a limited amount of the resource", "Initiate action to save resource back to server", "Monitor request compare represetention sent, versus what was received and delta should only be changes made" ]
+    },
+    "testMethod" : "ldpt:clientOnly"
+  }, {
+    "@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.",
+    "entries" : {
+      "@list" : [ "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.",
+    "entries" : {
+      "@list" : [ "ldpt:BasicContainer-AllowMultipleRdfTypes", "ldpt:BasicContainer-ChangeRdfTypeValue", "ldpt:BasicContainer-GetResourcePreservesTriples", "ldpt:BasicContainer-AllowResponsesFromServer" ]
+    },
+    "mf:name" : "BasicContainer (MUST)"
+  }, {
+    "@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.",
+    "entries" : {
+      "@list" : [ "ldpt:BasicContainer-ClientPostToCreate", "ldpt:BasicContainer-ServerOpen" ]
+    },
+    "mf:name" : "BasicContainer (SHOULD)"
+  }, {
+    "@id" : "ldpt:BasicContainer-ServerOpen",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-18T15:57:05.199Z"
+    },
+    "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",
+    "seeAlso" : "http://www.w3.org/TR/ldp#ldpr-cli-openpreds",
+    "mf:action" : "",
+    "mf:name" : "BasicContainer-ServerOpen",
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t138",
+    "conformanceLevel" : "ldpt:SHOULD",
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
+    "declaredTestCase" : "ldpt:RdfSource-ServerOpen",
+    "ldpt:steps" : {
+      "@list" : [ "Given a client and a known RDF Source at a given URL", "Via some means, alter the rdf:type of the RDF Source (either adding, changing or removing).  Note it may be implementation dependent on what the server will allow and also when changed, what different behavior the client will have", "Verify that the client continues to operate as expected" ]
+    },
+    "testMethod" : "ldpt:clientOnly"
+  }, {
+    "@id" : "ldpt:DirectContainer-AllowMultipleRdfTypes",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-18T15:57:05.222Z"
+    },
+    "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",
+    "seeAlso" : "http://www.w3.org/TR/ldp#ldp-cli-multitype",
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-AllowMultipleRdfTypes",
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t130",
+    "conformanceLevel" : "ldpt:MUST",
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "declaredTestCase" : "ldpt:RdfSource-AllowMultipleRdfTypes",
+    "ldpt:steps" : {
+      "@list" : [ "Given a client and a known RDF Source at a given URL", "Via some means, alter the rdf:type of the RDF Source by adding another rdf:type. Note it may be implementation dependent on what the server will allow and also when changed, what different behavior the client will have", "Verify that the client continues to operate as expected" ]
+    },
+    "testMethod" : "ldpt:clientOnly"
+  }, {
+    "@id" : "ldpt:DirectContainer-AllowResponsesFromServer",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-18T15:57:05.227Z"
+    },
+    "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",
+    "seeAlso" : "http://www.w3.org/TR/ldp#ldpr-cli-hints-ignorable",
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-AllowResponsesFromServer",
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t155",
+    "conformanceLevel" : "ldpt:MUST",
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "declaredTestCase" : "ldpt:RdfSource-AllowResponsesFromServer",
+    "ldpt:steps" : {
+      "@list" : [ "Determine certain hints that your server would ignore", "Form a client request that uses this hint", "Execute the request and analyze the result", "Verify that client processes request as expected" ]
+    },
+    "testMethod" : "ldpt:clientOnly"
+  }, {
+    "@id" : "ldpt:DirectContainer-ChangeRdfTypeValue",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-18T15:57:05.223Z"
+    },
+    "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",
+    "seeAlso" : "http://www.w3.org/TR/ldp#ldpr-cli-typeschange",
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-ChangeRdfTypeValue",
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t11",
+    "conformanceLevel" : "ldpt:MUST",
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "declaredTestCase" : "ldpt:RdfSource-ChangeRdfTypeValue",
+    "ldpt:steps" : {
+      "@list" : [ "Given a client and a known RDF Source at a given URL", "Via some means, alter the rdf:type of the RDF Source by adding or removing a rdf:type triple. Note it may be implementation dependent on what the server will allow and also when changed, what different behavior the client will have", "Verify that the client continues to operate as expected" ]
+    },
+    "testMethod" : "ldpt:clientOnly"
+  }, {
+    "@id" : "ldpt:DirectContainer-ClientMayProvideHints",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-18T15:57:05.229Z"
+    },
+    "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",
+    "seeAlso" : "http://www.w3.org/TR/ldp#ldpr-cli-can-hint",
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-ClientMayProvideHints",
+    "reviewStatus" : "td:unreviewed",
+    "specificationReference" : "_:t154",
+    "conformanceLevel" : "ldpt:MAY",
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "declaredTestCase" : "ldpt:RdfSource-ClientMayProvideHints",
+    "ldpt:steps" : {
+      "@list" : [ "Given a URL to a known RDF Source", "Configure the client application, if needed, to use the Prefer header to omit either containment or membership triples", "Use the client to send the GET request", "Monitor to ensure the server receives the hint", "Monitor to ensure the server honors the hing", "Verify the client behavior receives the optimized response" ]
+    },
+    "testMethod" : "ldpt:clientOnly"
+  }, {
+    "@id" : "ldpt:DirectContainer-ClientPostToCreate",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-18T15:57:05.215Z"
+    },
+    "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",
+    "seeAlso" : "http://www.w3.org/TR/ldp#ldpc-post-created201",
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-ClientPostToCreate",
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t104",
+    "conformanceLevel" : "ldpt:SHOULD",
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "declaredTestCase" : "ldpt:CommonContainer-ClientPostToCreate",
+    "ldpt:steps" : {
+      "@list" : [ "Given a container URL and POST is supported", "Monitor the client's request to ensure a POST request is sent", "Verify the response has a response status code of 201-Created and Location header with URL of created resource" ]
+    },
+    "testMethod" : "ldpt:clientOnly"
+  }, {
+    "@id" : "ldpt:DirectContainer-GetResourcePreservesTriples",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-18T15:57:05.226Z"
+    },
+    "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",
+    "seeAlso" : "http://www.w3.org/TR/ldp#ldpr-cli-preservetriples",
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-GetResourcePreservesTriples",
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t81",
+    "conformanceLevel" : "ldpt:MUST",
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "declaredTestCase" : "ldpt:RdfSource-GetResourcePreservesTriples",
+    "ldpt:steps" : {
+      "@list" : [ "Given a URL for a RDF Source, have client fetch a representation", "Observe the results of the fetch, either by application provided means or monitoring the network", "Given the client application interface, modify a limited amount of the resource", "Initiate action to save resource back to server", "Monitor request compare represetention sent, versus what was received and delta should only be changes made" ]
+    },
+    "testMethod" : "ldpt:clientOnly"
+  }, {
+    "@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.",
+    "entries" : {
+      "@list" : [ "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.",
+    "entries" : {
+      "@list" : [ "ldpt:DirectContainer-AllowMultipleRdfTypes", "ldpt:DirectContainer-ChangeRdfTypeValue", "ldpt:DirectContainer-GetResourcePreservesTriples", "ldpt:DirectContainer-AllowResponsesFromServer" ]
+    },
+    "mf:name" : "DirectContainer (MUST)"
+  }, {
+    "@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.",
+    "entries" : {
+      "@list" : [ "ldpt:DirectContainer-ClientPostToCreate", "ldpt:DirectContainer-ServerOpen" ]
+    },
+    "mf:name" : "DirectContainer (SHOULD)"
+  }, {
+    "@id" : "ldpt:DirectContainer-ServerOpen",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-18T15:57:05.224Z"
+    },
+    "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",
+    "seeAlso" : "http://www.w3.org/TR/ldp#ldpr-cli-openpreds",
+    "mf:action" : "",
+    "mf:name" : "DirectContainer-ServerOpen",
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t83",
+    "conformanceLevel" : "ldpt:SHOULD",
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
+    "declaredTestCase" : "ldpt:RdfSource-ServerOpen",
+    "ldpt:steps" : {
+      "@list" : [ "Given a client and a known RDF Source at a given URL", "Via some means, alter the rdf:type of the RDF Source (either adding, changing or removing).  Note it may be implementation dependent on what the server will allow and also when changed, what different behavior the client will have", "Verify that the client continues to operate as expected" ]
+    },
+    "testMethod" : "ldpt:clientOnly"
+  }, {
+    "@id" : "ldpt:IndirectContainer-AllowMultipleRdfTypes",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-18T15:57:05.246Z"
+    },
+    "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",
+    "seeAlso" : "http://www.w3.org/TR/ldp#ldp-cli-multitype",
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-AllowMultipleRdfTypes",
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t144",
+    "conformanceLevel" : "ldpt:MUST",
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "declaredTestCase" : "ldpt:RdfSource-AllowMultipleRdfTypes",
+    "ldpt:steps" : {
+      "@list" : [ "Given a client and a known RDF Source at a given URL", "Via some means, alter the rdf:type of the RDF Source by adding another rdf:type. Note it may be implementation dependent on what the server will allow and also when changed, what different behavior the client will have", "Verify that the client continues to operate as expected" ]
+    },
+    "testMethod" : "ldpt:clientOnly"
+  }, {
+    "@id" : "ldpt:IndirectContainer-AllowResponsesFromServer",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-18T15:57:05.251Z"
+    },
+    "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",
+    "seeAlso" : "http://www.w3.org/TR/ldp#ldpr-cli-hints-ignorable",
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-AllowResponsesFromServer",
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t156",
+    "conformanceLevel" : "ldpt:MUST",
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "declaredTestCase" : "ldpt:RdfSource-AllowResponsesFromServer",
+    "ldpt:steps" : {
+      "@list" : [ "Determine certain hints that your server would ignore", "Form a client request that uses this hint", "Execute the request and analyze the result", "Verify that client processes request as expected" ]
+    },
+    "testMethod" : "ldpt:clientOnly"
+  }, {
+    "@id" : "ldpt:IndirectContainer-ChangeRdfTypeValue",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-18T15:57:05.247Z"
+    },
+    "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",
+    "seeAlso" : "http://www.w3.org/TR/ldp#ldpr-cli-typeschange",
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-ChangeRdfTypeValue",
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t63",
+    "conformanceLevel" : "ldpt:MUST",
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "declaredTestCase" : "ldpt:RdfSource-ChangeRdfTypeValue",
+    "ldpt:steps" : {
+      "@list" : [ "Given a client and a known RDF Source at a given URL", "Via some means, alter the rdf:type of the RDF Source by adding or removing a rdf:type triple. Note it may be implementation dependent on what the server will allow and also when changed, what different behavior the client will have", "Verify that the client continues to operate as expected" ]
+    },
+    "testMethod" : "ldpt:clientOnly"
+  }, {
+    "@id" : "ldpt:IndirectContainer-ClientMayProvideHints",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-18T15:57:05.253Z"
+    },
+    "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",
+    "seeAlso" : "http://www.w3.org/TR/ldp#ldpr-cli-can-hint",
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-ClientMayProvideHints",
+    "reviewStatus" : "td:unreviewed",
+    "specificationReference" : "_:t158",
+    "conformanceLevel" : "ldpt:MAY",
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "declaredTestCase" : "ldpt:RdfSource-ClientMayProvideHints",
+    "ldpt:steps" : {
+      "@list" : [ "Given a URL to a known RDF Source", "Configure the client application, if needed, to use the Prefer header to omit either containment or membership triples", "Use the client to send the GET request", "Monitor to ensure the server receives the hint", "Monitor to ensure the server honors the hing", "Verify the client behavior receives the optimized response" ]
+    },
+    "testMethod" : "ldpt:clientOnly"
+  }, {
+    "@id" : "ldpt:IndirectContainer-ClientPostToCreate",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-18T15:57:05.239Z"
+    },
+    "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",
+    "seeAlso" : "http://www.w3.org/TR/ldp#ldpc-post-created201",
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-ClientPostToCreate",
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t159",
+    "conformanceLevel" : "ldpt:SHOULD",
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "declaredTestCase" : "ldpt:CommonContainer-ClientPostToCreate",
+    "ldpt:steps" : {
+      "@list" : [ "Given a container URL and POST is supported", "Monitor the client's request to ensure a POST request is sent", "Verify the response has a response status code of 201-Created and Location header with URL of created resource" ]
+    },
+    "testMethod" : "ldpt:clientOnly"
+  }, {
+    "@id" : "ldpt:IndirectContainer-GetResourcePreservesTriples",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-18T15:57:05.25Z"
+    },
+    "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",
+    "seeAlso" : "http://www.w3.org/TR/ldp#ldpr-cli-preservetriples",
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-GetResourcePreservesTriples",
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t78",
+    "conformanceLevel" : "ldpt:MUST",
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "declaredTestCase" : "ldpt:RdfSource-GetResourcePreservesTriples",
+    "ldpt:steps" : {
+      "@list" : [ "Given a URL for a RDF Source, have client fetch a representation", "Observe the results of the fetch, either by application provided means or monitoring the network", "Given the client application interface, modify a limited amount of the resource", "Initiate action to save resource back to server", "Monitor request compare represetention sent, versus what was received and delta should only be changes made" ]
+    },
+    "testMethod" : "ldpt:clientOnly"
+  }, {
+    "@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.",
+    "entries" : {
+      "@list" : [ "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.",
+    "entries" : {
+      "@list" : [ "ldpt:IndirectContainer-AllowMultipleRdfTypes", "ldpt:IndirectContainer-ChangeRdfTypeValue", "ldpt:IndirectContainer-GetResourcePreservesTriples", "ldpt:IndirectContainer-AllowResponsesFromServer" ]
+    },
+    "mf:name" : "IndirectContainer (MUST)"
+  }, {
+    "@id" : "ldpt:IndirectContainer-SHOULDManifest",
+    "http://purl.org/dc/elements/1.1/title" : "IndirectContainer (SHOULD)",
+    "rdf:type" : {
+      "@id" : "mf:Manifest"
+    },
+    "rdfs:comment" : "LDP Indirect Container tests. SHOULD conformance tests.",
+    "entries" : {
+      "@list" : [ "ldpt:IndirectContainer-ClientPostToCreate", "ldpt:IndirectContainer-ServerOpen" ]
+    },
+    "mf:name" : "IndirectContainer (SHOULD)"
+  }, {
+    "@id" : "ldpt:IndirectContainer-ServerOpen",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-18T15:57:05.249Z"
+    },
+    "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" : "IndirectContainer-ServerOpen",
+    "seeAlso" : "http://www.w3.org/TR/ldp#ldpr-cli-openpreds",
+    "mf:action" : "",
+    "mf:name" : "IndirectContainer-ServerOpen",
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t150",
+    "conformanceLevel" : "ldpt:SHOULD",
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.IndirectContainerTest",
+    "declaredTestCase" : "ldpt:RdfSource-ServerOpen",
+    "ldpt:steps" : {
+      "@list" : [ "Given a client and a known RDF Source at a given URL", "Via some means, alter the rdf:type of the RDF Source (either adding, changing or removing).  Note it may be implementation dependent on what the server will allow and also when changed, what different behavior the client will have", "Verify that the client continues to operate as expected" ]
+    },
+    "testMethod" : "ldpt:clientOnly"
+  }, {
+    "@id" : "ldpt:MemberResource-AllowMultipleRdfTypes",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-18T15:57:05.038Z"
+    },
+    "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" : "MemberResource-AllowMultipleRdfTypes",
+    "seeAlso" : "http://www.w3.org/TR/ldp#ldp-cli-multitype",
+    "mf:action" : "",
+    "mf:name" : "MemberResource-AllowMultipleRdfTypes",
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t153",
+    "conformanceLevel" : "ldpt:MUST",
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.MemberResourceTest",
+    "declaredTestCase" : "ldpt:RdfSource-AllowMultipleRdfTypes",
+    "ldpt:steps" : {
+      "@list" : [ "Given a client and a known RDF Source at a given URL", "Via some means, alter the rdf:type of the RDF Source by adding another rdf:type. Note it may be implementation dependent on what the server will allow and also when changed, what different behavior the client will have", "Verify that the client continues to operate as expected" ]
+    },
+    "testMethod" : "ldpt:clientOnly"
+  }, {
+    "@id" : "ldpt:MemberResource-AllowResponsesFromServer",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-18T15:57:05.156Z"
+    },
+    "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" : "MemberResource-AllowResponsesFromServer",
+    "seeAlso" : "http://www.w3.org/TR/ldp#ldpr-cli-hints-ignorable",
+    "mf:action" : "",
+    "mf:name" : "MemberResource-AllowResponsesFromServer",
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t98",
+    "conformanceLevel" : "ldpt:MUST",
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.MemberResourceTest",
+    "declaredTestCase" : "ldpt:RdfSource-AllowResponsesFromServer",
+    "ldpt:steps" : {
+      "@list" : [ "Determine certain hints that your server would ignore", "Form a client request that uses this hint", "Execute the request and analyze the result", "Verify that client processes request as expected" ]
+    },
+    "testMethod" : "ldpt:clientOnly"
+  }, {
+    "@id" : "ldpt:MemberResource-ChangeRdfTypeValue",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-18T15:57:05.152Z"
+    },
+    "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" : "MemberResource-ChangeRdfTypeValue",
+    "seeAlso" : "http://www.w3.org/TR/ldp#ldpr-cli-typeschange",
+    "mf:action" : "",
+    "mf:name" : "MemberResource-ChangeRdfTypeValue",
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t25",
+    "conformanceLevel" : "ldpt:MUST",
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.MemberResourceTest",
+    "declaredTestCase" : "ldpt:RdfSource-ChangeRdfTypeValue",
+    "ldpt:steps" : {
+      "@list" : [ "Given a client and a known RDF Source at a given URL", "Via some means, alter the rdf:type of the RDF Source by adding or removing a rdf:type triple. Note it may be implementation dependent on what the server will allow and also when changed, what different behavior the client will have", "Verify that the client continues to operate as expected" ]
+    },
+    "testMethod" : "ldpt:clientOnly"
+  }, {
+    "@id" : "ldpt:MemberResource-ClientMayProvideHints",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-18T15:57:05.159Z"
+    },
+    "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" : "MemberResource-ClientMayProvideHints",
+    "seeAlso" : "http://www.w3.org/TR/ldp#ldpr-cli-can-hint",
+    "mf:action" : "",
+    "mf:name" : "MemberResource-ClientMayProvideHints",
+    "reviewStatus" : "td:unreviewed",
+    "specificationReference" : "_:t17",
+    "conformanceLevel" : "ldpt:MAY",
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.MemberResourceTest",
+    "declaredTestCase" : "ldpt:RdfSource-ClientMayProvideHints",
+    "ldpt:steps" : {
+      "@list" : [ "Given a URL to a known RDF Source", "Configure the client application, if needed, to use the Prefer header to omit either containment or membership triples", "Use the client to send the GET request", "Monitor to ensure the server receives the hint", "Monitor to ensure the server honors the hing", "Verify the client behavior receives the optimized response" ]
+    },
+    "testMethod" : "ldpt:clientOnly"
+  }, {
+    "@id" : "ldpt:MemberResource-GetResourcePreservesTriples",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-18T15:57:05.154Z"
+    },
+    "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" : "MemberResource-GetResourcePreservesTriples",
+    "seeAlso" : "http://www.w3.org/TR/ldp#ldpr-cli-preservetriples",
+    "mf:action" : "",
+    "mf:name" : "MemberResource-GetResourcePreservesTriples",
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t85",
+    "conformanceLevel" : "ldpt:MUST",
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.MemberResourceTest",
+    "declaredTestCase" : "ldpt:RdfSource-GetResourcePreservesTriples",
+    "ldpt:steps" : {
+      "@list" : [ "Given a URL for a RDF Source, have client fetch a representation", "Observe the results of the fetch, either by application provided means or monitoring the network", "Given the client application interface, modify a limited amount of the resource", "Initiate action to save resource back to server", "Monitor request compare represetention sent, versus what was received and delta should only be changes made" ]
+    },
+    "testMethod" : "ldpt:clientOnly"
+  }, {
+    "@id" : "ldpt:MemberResource-ServerOpen",
+    "dcterms:date" : {
+      "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
+      "@value" : "2014-07-18T15:57:05.153Z"
+    },
+    "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" : "MemberResource-ServerOpen",
+    "seeAlso" : "http://www.w3.org/TR/ldp#ldpr-cli-openpreds",
+    "mf:action" : "",
+    "mf:name" : "MemberResource-ServerOpen",
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t111",
+    "conformanceLevel" : "ldpt:SHOULD",
+    "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.MemberResourceTest",
+    "declaredTestCase" : "ldpt:RdfSource-ServerOpen",
+    "ldpt:steps" : {
+      "@list" : [ "Given a client and a known RDF Source at a given URL", "Via some means, alter the rdf:type of the RDF Source (either adding, changing or removing).  Note it may be implementation dependent on what the server will allow and also when changed, what different behavior the client will have", "Verify that the client continues to operate as expected" ]
+    },
+    "testMethod" : "ldpt:clientOnly"
+  }, {
+    "@id" : "ldpt:RDFSource-MAYManifest",
+    "http://purl.org/dc/elements/1.1/title" : "RDFSource (MAY)",
+    "rdf:type" : {
+      "@id" : "mf:Manifest"
+    },
+    "rdfs:comment" : "LDP RDF Source tests. MAY conformance tests.",
+    "entries" : {
+      "@list" : [ "ldpt:MemberResource-ClientMayProvideHints" ]
+    },
+    "mf:name" : "RDFSource (MAY)"
+  }, {
+    "@id" : "ldpt:RDFSource-MUSTManifest",
+    "http://purl.org/dc/elements/1.1/title" : "RDFSource (MUST)",
+    "rdf:type" : {
+      "@id" : "mf:Manifest"
+    },
+    "rdfs:comment" : "LDP RDF Source tests. MUST conformance tests.",
+    "entries" : {
+      "@list" : [ "ldpt:MemberResource-AllowMultipleRdfTypes", "ldpt:MemberResource-ChangeRdfTypeValue", "ldpt:MemberResource-GetResourcePreservesTriples", "ldpt:MemberResource-AllowResponsesFromServer" ]
+    },
+    "mf:name" : "RDFSource (MUST)"
+  }, {
+    "@id" : "ldpt:RDFSource-SHOULDManifest",
+    "http://purl.org/dc/elements/1.1/title" : "RDFSource (SHOULD)",
+    "rdf:type" : {
+      "@id" : "mf:Manifest"
+    },
+    "rdfs:comment" : "LDP RDF Source tests. SHOULD conformance tests.",
+    "entries" : {
+      "@list" : [ "ldpt:MemberResource-ServerOpen" ]
+    },
+    "mf:name" : "RDFSource (SHOULD)"
+  } ],
+  "@context" : {
+    "rest" : {
+      "@id" : "http://www.w3.org/1999/02/22-rdf-syntax-ns#rest",
+      "@type" : "@id"
+    },
+    "first" : {
+      "@id" : "http://www.w3.org/1999/02/22-rdf-syntax-ns#first",
+      "@type" : "@id"
+    },
+    "includesText" : {
+      "@id" : "http://www.w3.org/2006/03/test-description#includesText",
+      "@type" : "@id"
+    },
+    "seeAlso" : {
+      "@id" : "http://www.w3.org/2000/01/rdf-schema#seeAlso",
+      "@type" : "@id"
+    },
+    "declaredTestCase" : {
+      "@id" : "http://www.w3c.org/ns/ldp/test#declaredTestCase",
+      "@type" : "@id"
+    },
+    "reviewStatus" : {
+      "@id" : "http://www.w3.org/2006/03/test-description#reviewStatus",
+      "@type" : "@id"
+    },
+    "declaredInClass" : {
+      "@id" : "http://www.w3c.org/ns/ldp/test#declaredInClass",
+      "@type" : "@id"
+    },
+    "specificationReference" : {
+      "@id" : "http://www.w3.org/2006/03/test-description#specificationReference",
+      "@type" : "@id"
+    },
+    "steps" : {
+      "@id" : "http://www.w3c.org/ns/ldp/test#steps",
+      "@type" : "@id"
+    },
+    "date" : {
+      "@id" : "http://purl.org/dc/terms/date",
+      "@type" : "@id"
+    },
+    "name" : {
+      "@id" : "http://www.w3.org/2001/sw/DataAccess/tests/test-manifest#name",
+      "@type" : "@id"
+    },
+    "label" : {
+      "@id" : "http://www.w3.org/2000/01/rdf-schema#label",
+      "@type" : "@id"
+    },
+    "action" : {
+      "@id" : "http://www.w3.org/2001/sw/DataAccess/tests/test-manifest#action",
+      "@type" : "@id"
+    },
+    "comment" : {
+      "@id" : "http://www.w3.org/2000/01/rdf-schema#comment",
+      "@type" : "@id"
+    },
+    "conformanceLevel" : {
+      "@id" : "http://www.w3c.org/ns/ldp/test#conformanceLevel",
+      "@type" : "@id"
+    },
+    "testMethod" : {
+      "@id" : "http://www.w3c.org/ns/ldp/test#testMethod",
+      "@type" : "@id"
+    },
+    "subject" : {
+      "@id" : "http://purl.org/dc/terms/subject",
+      "@type" : "@id"
+    },
+    "entries" : {
+      "@id" : "http://www.w3.org/2001/sw/DataAccess/tests/test-manifest#entries",
+      "@type" : "@id"
+    },
+    "title" : {
+      "@id" : "http://purl.org/dc/elements/1.1/title",
+      "@type" : "@id"
+    },
+    "rdft" : "http://www.w3.org/ns/rdftest#",
+    "rdfs" : "http://www.w3.org/2000/01/rdf-schema#",
+    "earl" : "http://www.w3.org/ns/earl#",
+    "foaf" : "http://xmlns.com/foaf/0.1/",
+    "rdf" : "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
+    "mf" : "http://www.w3.org/2001/sw/DataAccess/tests/test-manifest#",
+    "td" : "http://www.w3.org/2006/03/test-description#",
+    "doap" : "http://usefulinc.com/ns/doap#",
+    "dcterms" : "http://purl.org/dc/terms/",
+    "ldpt" : "http://www.w3c.org/ns/ldp/test#"
+  }
+}
\ No newline at end of file
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/tests/reports/ldp-earl-manifest-client-only.ttl	Sun Jul 20 20:11:42 2014 -0400
@@ -0,0 +1,646 @@
[email protected] rdft:  <http://www.w3.org/ns/rdftest#> .
[email protected] rdfs:  <http://www.w3.org/2000/01/rdf-schema#> .
[email protected] earl:  <http://www.w3.org/ns/earl#> .
[email protected] foaf:  <http://xmlns.com/foaf/0.1/> .
[email protected] rdf:   <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
[email protected] td:    <http://www.w3.org/2006/03/test-description#> .
[email protected] mf:    <http://www.w3.org/2001/sw/DataAccess/tests/test-manifest#> .
[email protected] doap:  <http://usefulinc.com/ns/doap#> .
[email protected] ldpt:  <http://www.w3c.org/ns/ldp/test#> .
[email protected] dcterms: <http://purl.org/dc/terms/> .
+
+ldpt:MemberResource-ChangeRdfTypeValue
+        a                          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                 "MemberResource-ChangeRdfTypeValue" ;
+        rdfs:seeAlso               <http://www.w3.org/TR/ldp#ldpr-cli-typeschange> ;
+        dcterms:date               "2014-07-18T15:57:05.152Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+        dcterms:subject            "MUST" ;
+        mf:action                  "" ;
+        mf:name                    "MemberResource-ChangeRdfTypeValue" ;
+        td:reviewStatus            td:approved ;
+        td:specificationReference  [ a                td:Excerpt ;
+                                     rdfs:seeAlso     <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."^^<http://www.w3.org/2001/XMLSchema#string>
+                                   ] ;
+        ldpt:conformanceLevel      ldpt:MUST ;
+        ldpt:declaredInClass       "org.w3.ldp.testsuite.test.MemberResourceTest" ;
+        ldpt:declaredTestCase      ldpt:RdfSource-ChangeRdfTypeValue ;
+        ldpt:steps                 ( "Given a client and a known RDF Source at a given URL" "Via some means, alter the rdf:type of the RDF Source by adding or removing a rdf:type triple. Note it may be implementation dependent on what the server will allow and also when changed, what different behavior the client will have" "Verify that the client continues to operate as expected" ) ;
+        ldpt:testMethod            ldpt:clientOnly .
+
+ldpt:BasicContainer-ClientPostToCreate
+        a                          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               <http://www.w3.org/TR/ldp#ldpc-post-created201> ;
+        dcterms:date               "2014-07-18T15:57:05.188Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+        dcterms:subject            "SHOULD" ;
+        mf:action                  "" ;
+        mf:name                    "BasicContainer-ClientPostToCreate" ;
+        td:reviewStatus            td:approved ;
+        td:specificationReference  [ a                td:Excerpt ;
+                                     rdfs:seeAlso     <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."^^<http://www.w3.org/2001/XMLSchema#string>
+                                   ] ;
+        ldpt:conformanceLevel      ldpt:SHOULD ;
+        ldpt:declaredInClass       "org.w3.ldp.testsuite.test.BasicContainerTest" ;
+        ldpt:declaredTestCase      ldpt:CommonContainer-ClientPostToCreate ;
+        ldpt:steps                 ( "Given a container URL and POST is supported" "Monitor the client's request to ensure a POST request is sent" "Verify the response has a response status code of 201-Created and Location header with URL of created resource" ) ;
+        ldpt:testMethod            ldpt:clientOnly .
+
+ldpt:RDFSource-SHOULDManifest
+        a             mf:Manifest ;
+        rdfs:comment  "LDP RDF Source tests. SHOULD conformance tests." ;
+        <http://purl.org/dc/elements/1.1/title>
+                "RDFSource (SHOULD)" ;
+        mf:entries    ( ldpt:MemberResource-ServerOpen ) ;
+        mf:name       "RDFSource (SHOULD)" .
+
+ldpt:IndirectContainer-MAYManifest
+        a             mf:Manifest ;
+        rdfs:comment  "LDP Indirect Container tests. MAY conformance tests." ;
+        <http://purl.org/dc/elements/1.1/title>
+                "IndirectContainer (MAY)" ;
+        mf:entries    ( ldpt:IndirectContainer-ClientMayProvideHints ) ;
+        mf:name       "IndirectContainer (MAY)" .
+
+ldpt:BasicContainer-GetResourcePreservesTriples
+        a                          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               <http://www.w3.org/TR/ldp#ldpr-cli-preservetriples> ;
+        dcterms:date               "2014-07-18T15:57:05.201Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+        dcterms:subject            "MUST" ;
+        mf:action                  "" ;
+        mf:name                    "BasicContainer-GetResourcePreservesTriples" ;
+        td:reviewStatus            td:approved ;
+        td:specificationReference  [ a                td:Excerpt ;
+                                     rdfs:seeAlso     <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]. "^^<http://www.w3.org/2001/XMLSchema#string>
+                                   ] ;
+        ldpt:conformanceLevel      ldpt:MUST ;
+        ldpt:declaredInClass       "org.w3.ldp.testsuite.test.BasicContainerTest" ;
+        ldpt:declaredTestCase      ldpt:RdfSource-GetResourcePreservesTriples ;
+        ldpt:steps                 ( "Given a URL for a RDF Source, have client fetch a representation" "Observe the results of the fetch, either by application provided means or monitoring the network" "Given the client application interface, modify a limited amount of the resource" "Initiate action to save resource back to server" "Monitor request compare represetention sent, versus what was received and delta should only be changes made" ) ;
+        ldpt:testMethod            ldpt:clientOnly .
+
+ldpt:IndirectContainer-GetResourcePreservesTriples
+        a                          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               <http://www.w3.org/TR/ldp#ldpr-cli-preservetriples> ;
+        dcterms:date               "2014-07-18T15:57:05.25Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+        dcterms:subject            "MUST" ;
+        mf:action                  "" ;
+        mf:name                    "IndirectContainer-GetResourcePreservesTriples" ;
+        td:reviewStatus            td:approved ;
+        td:specificationReference  [ a                td:Excerpt ;
+                                     rdfs:seeAlso     <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]. "^^<http://www.w3.org/2001/XMLSchema#string>
+                                   ] ;
+        ldpt:conformanceLevel      ldpt:MUST ;
+        ldpt:declaredInClass       "org.w3.ldp.testsuite.test.IndirectContainerTest" ;
+        ldpt:declaredTestCase      ldpt:RdfSource-GetResourcePreservesTriples ;
+        ldpt:steps                 ( "Given a URL for a RDF Source, have client fetch a representation" "Observe the results of the fetch, either by application provided means or monitoring the network" "Given the client application interface, modify a limited amount of the resource" "Initiate action to save resource back to server" "Monitor request compare represetention sent, versus what was received and delta should only be changes made" ) ;
+        ldpt:testMethod            ldpt:clientOnly .
+
+ldpt:DirectContainer-GetResourcePreservesTriples
+        a                          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               <http://www.w3.org/TR/ldp#ldpr-cli-preservetriples> ;
+        dcterms:date               "2014-07-18T15:57:05.226Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+        dcterms:subject            "MUST" ;
+        mf:action                  "" ;
+        mf:name                    "DirectContainer-GetResourcePreservesTriples" ;
+        td:reviewStatus            td:approved ;
+        td:specificationReference  [ a                td:Excerpt ;
+                                     rdfs:seeAlso     <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]. "^^<http://www.w3.org/2001/XMLSchema#string>
+                                   ] ;
+        ldpt:conformanceLevel      ldpt:MUST ;
+        ldpt:declaredInClass       "org.w3.ldp.testsuite.test.DirectContainerTest" ;
+        ldpt:declaredTestCase      ldpt:RdfSource-GetResourcePreservesTriples ;
+        ldpt:steps                 ( "Given a URL for a RDF Source, have client fetch a representation" "Observe the results of the fetch, either by application provided means or monitoring the network" "Given the client application interface, modify a limited amount of the resource" "Initiate action to save resource back to server" "Monitor request compare represetention sent, versus what was received and delta should only be changes made" ) ;
+        ldpt:testMethod            ldpt:clientOnly .
+
+ldpt:IndirectContainer-SHOULDManifest
+        a             mf:Manifest ;
+        rdfs:comment  "LDP Indirect Container tests. SHOULD conformance tests." ;
+        <http://purl.org/dc/elements/1.1/title>
+                "IndirectContainer (SHOULD)" ;
+        mf:entries    ( ldpt:IndirectContainer-ClientPostToCreate ldpt:IndirectContainer-ServerOpen ) ;
+        mf:name       "IndirectContainer (SHOULD)" .
+
+ldpt:DirectContainer-ServerOpen
+        a                          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               <http://www.w3.org/TR/ldp#ldpr-cli-openpreds> ;
+        dcterms:date               "2014-07-18T15:57:05.224Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+        dcterms:subject            "SHOULD" ;
+        mf:action                  "" ;
+        mf:name                    "DirectContainer-ServerOpen" ;
+        td:reviewStatus            td:approved ;
+        td:specificationReference  [ a                td:Excerpt ;
+                                     rdfs:seeAlso     <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."^^<http://www.w3.org/2001/XMLSchema#string>
+                                   ] ;
+        ldpt:conformanceLevel      ldpt:SHOULD ;
+        ldpt:declaredInClass       "org.w3.ldp.testsuite.test.DirectContainerTest" ;
+        ldpt:declaredTestCase      ldpt:RdfSource-ServerOpen ;
+        ldpt:steps                 ( "Given a client and a known RDF Source at a given URL" "Via some means, alter the rdf:type of the RDF Source (either adding, changing or removing).  Note it may be implementation dependent on what the server will allow and also when changed, what different behavior the client will have" "Verify that the client continues to operate as expected" ) ;
+        ldpt:testMethod            ldpt:clientOnly .
+
+ldpt:MemberResource-GetResourcePreservesTriples
+        a                          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                 "MemberResource-GetResourcePreservesTriples" ;
+        rdfs:seeAlso               <http://www.w3.org/TR/ldp#ldpr-cli-preservetriples> ;
+        dcterms:date               "2014-07-18T15:57:05.154Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+        dcterms:subject            "MUST" ;
+        mf:action                  "" ;
+        mf:name                    "MemberResource-GetResourcePreservesTriples" ;
+        td:reviewStatus            td:approved ;
+        td:specificationReference  [ a                td:Excerpt ;
+                                     rdfs:seeAlso     <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]. "^^<http://www.w3.org/2001/XMLSchema#string>
+                                   ] ;
+        ldpt:conformanceLevel      ldpt:MUST ;
+        ldpt:declaredInClass       "org.w3.ldp.testsuite.test.MemberResourceTest" ;
+        ldpt:declaredTestCase      ldpt:RdfSource-GetResourcePreservesTriples ;
+        ldpt:steps                 ( "Given a URL for a RDF Source, have client fetch a representation" "Observe the results of the fetch, either by application provided means or monitoring the network" "Given the client application interface, modify a limited amount of the resource" "Initiate action to save resource back to server" "Monitor request compare represetention sent, versus what was received and delta should only be changes made" ) ;
+        ldpt:testMethod            ldpt:clientOnly .
+
+ldpt:BasicContainer-ClientMayProvideHints
+        a                          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               <http://www.w3.org/TR/ldp#ldpr-cli-can-hint> ;
+        dcterms:date               "2014-07-18T15:57:05.204Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+        dcterms:subject            "MAY" ;
+        mf:action                  "" ;
+        mf:name                    "BasicContainer-ClientMayProvideHints" ;
+        td:reviewStatus            td:unreviewed ;
+        td:specificationReference  [ a                td:Excerpt ;
+                                     rdfs:seeAlso     <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. "^^<http://www.w3.org/2001/XMLSchema#string>
+                                   ] ;
+        ldpt:conformanceLevel      ldpt:MAY ;
+        ldpt:declaredInClass       "org.w3.ldp.testsuite.test.BasicContainerTest" ;
+        ldpt:declaredTestCase      ldpt:RdfSource-ClientMayProvideHints ;
+        ldpt:steps                 ( "Given a URL to a known RDF Source" "Configure the client application, if needed, to use the Prefer header to omit either containment or membership triples" "Use the client to send the GET request" "Monitor to ensure the server receives the hint" "Monitor to ensure the server honors the hing" "Verify the client behavior receives the optimized response" ) ;
+        ldpt:testMethod            ldpt:clientOnly .
+
+ldpt:MemberResource-AllowResponsesFromServer
+        a                          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                 "MemberResource-AllowResponsesFromServer" ;
+        rdfs:seeAlso               <http://www.w3.org/TR/ldp#ldpr-cli-hints-ignorable> ;
+        dcterms:date               "2014-07-18T15:57:05.156Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+        dcterms:subject            "MUST" ;
+        mf:action                  "" ;
+        mf:name                    "MemberResource-AllowResponsesFromServer" ;
+        td:reviewStatus            td:approved ;
+        td:specificationReference  [ a                td:Excerpt ;
+                                     rdfs:seeAlso     <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."^^<http://www.w3.org/2001/XMLSchema#string>
+                                   ] ;
+        ldpt:conformanceLevel      ldpt:MUST ;
+        ldpt:declaredInClass       "org.w3.ldp.testsuite.test.MemberResourceTest" ;
+        ldpt:declaredTestCase      ldpt:RdfSource-AllowResponsesFromServer ;
+        ldpt:steps                 ( "Determine certain hints that your server would ignore" "Form a client request that uses this hint" "Execute the request and analyze the result" "Verify that client processes request as expected" ) ;
+        ldpt:testMethod            ldpt:clientOnly .
+
+ldpt:IndirectContainer-ChangeRdfTypeValue
+        a                          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               <http://www.w3.org/TR/ldp#ldpr-cli-typeschange> ;
+        dcterms:date               "2014-07-18T15:57:05.247Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+        dcterms:subject            "MUST" ;
+        mf:action                  "" ;
+        mf:name                    "IndirectContainer-ChangeRdfTypeValue" ;
+        td:reviewStatus            td:approved ;
+        td:specificationReference  [ a                td:Excerpt ;
+                                     rdfs:seeAlso     <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."^^<http://www.w3.org/2001/XMLSchema#string>
+                                   ] ;
+        ldpt:conformanceLevel      ldpt:MUST ;
+        ldpt:declaredInClass       "org.w3.ldp.testsuite.test.IndirectContainerTest" ;
+        ldpt:declaredTestCase      ldpt:RdfSource-ChangeRdfTypeValue ;
+        ldpt:steps                 ( "Given a client and a known RDF Source at a given URL" "Via some means, alter the rdf:type of the RDF Source by adding or removing a rdf:type triple. Note it may be implementation dependent on what the server will allow and also when changed, what different behavior the client will have" "Verify that the client continues to operate as expected" ) ;
+        ldpt:testMethod            ldpt:clientOnly .
+
+ldpt:DirectContainer-MUSTManifest
+        a             mf:Manifest ;
+        rdfs:comment  "LDP Direct Container tests. MUST conformance tests." ;
+        <http://purl.org/dc/elements/1.1/title>
+                "DirectContainer (MUST)" ;
+        mf:entries    ( ldpt:DirectContainer-AllowMultipleRdfTypes ldpt:DirectContainer-ChangeRdfTypeValue ldpt:DirectContainer-GetResourcePreservesTriples ldpt:DirectContainer-AllowResponsesFromServer ) ;
+        mf:name       "DirectContainer (MUST)" .
+
+ldpt:BasicContainer-SHOULDManifest
+        a             mf:Manifest ;
+        rdfs:comment  "LDP Basic Container tests. SHOULD conformance tests." ;
+        <http://purl.org/dc/elements/1.1/title>
+                "BasicContainer (SHOULD)" ;
+        mf:entries    ( ldpt:BasicContainer-ClientPostToCreate ldpt:BasicContainer-ServerOpen ) ;
+        mf:name       "BasicContainer (SHOULD)" .
+
+ldpt:BasicContainer-AllowMultipleRdfTypes
+        a                          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               <http://www.w3.org/TR/ldp#ldp-cli-multitype> ;
+        dcterms:date               "2014-07-18T15:57:05.197Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+        dcterms:subject            "MUST" ;
+        mf:action                  "" ;
+        mf:name                    "BasicContainer-AllowMultipleRdfTypes" ;
+        td:reviewStatus            td:approved ;
+        td:specificationReference  [ a                td:Excerpt ;
+                                     rdfs:seeAlso     <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."^^<http://www.w3.org/2001/XMLSchema#string>
+                                   ] ;
+        ldpt:conformanceLevel      ldpt:MUST ;
+        ldpt:declaredInClass       "org.w3.ldp.testsuite.test.BasicContainerTest" ;
+        ldpt:declaredTestCase      ldpt:RdfSource-AllowMultipleRdfTypes ;
+        ldpt:steps                 ( "Given a client and a known RDF Source at a given URL" "Via some means, alter the rdf:type of the RDF Source by adding another rdf:type. Note it may be implementation dependent on what the server will allow and also when changed, what different behavior the client will have" "Verify that the client continues to operate as expected" ) ;
+        ldpt:testMethod            ldpt:clientOnly .
+
+ldpt:DirectContainer-ClientPostToCreate
+        a                          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               <http://www.w3.org/TR/ldp#ldpc-post-created201> ;
+        dcterms:date               "2014-07-18T15:57:05.215Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+        dcterms:subject            "SHOULD" ;
+        mf:action                  "" ;
+        mf:name                    "DirectContainer-ClientPostToCreate" ;
+        td:reviewStatus            td:approved ;
+        td:specificationReference  [ a                td:Excerpt ;
+                                     rdfs:seeAlso     <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."^^<http://www.w3.org/2001/XMLSchema#string>
+                                   ] ;
+        ldpt:conformanceLevel      ldpt:SHOULD ;
+        ldpt:declaredInClass       "org.w3.ldp.testsuite.test.DirectContainerTest" ;
+        ldpt:declaredTestCase      ldpt:CommonContainer-ClientPostToCreate ;
+        ldpt:steps                 ( "Given a container URL and POST is supported" "Monitor the client's request to ensure a POST request is sent" "Verify the response has a response status code of 201-Created and Location header with URL of created resource" ) ;
+        ldpt:testMethod            ldpt:clientOnly .
+
+ldpt:IndirectContainer-MUSTManifest
+        a             mf:Manifest ;
+        rdfs:comment  "LDP Indirect Container tests. MUST conformance tests." ;
+        <http://purl.org/dc/elements/1.1/title>
+                "IndirectContainer (MUST)" ;
+        mf:entries    ( ldpt:IndirectContainer-AllowMultipleRdfTypes ldpt:IndirectContainer-ChangeRdfTypeValue ldpt:IndirectContainer-GetResourcePreservesTriples ldpt:IndirectContainer-AllowResponsesFromServer ) ;
+        mf:name       "IndirectContainer (MUST)" .
+
+ldpt:BasicContainer-ServerOpen
+        a                          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               <http://www.w3.org/TR/ldp#ldpr-cli-openpreds> ;
+        dcterms:date               "2014-07-18T15:57:05.199Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+        dcterms:subject            "SHOULD" ;
+        mf:action                  "" ;
+        mf:name                    "BasicContainer-ServerOpen" ;
+        td:reviewStatus            td:approved ;
+        td:specificationReference  [ a                td:Excerpt ;
+                                     rdfs:seeAlso     <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."^^<http://www.w3.org/2001/XMLSchema#string>
+                                   ] ;
+        ldpt:conformanceLevel      ldpt:SHOULD ;
+        ldpt:declaredInClass       "org.w3.ldp.testsuite.test.BasicContainerTest" ;
+        ldpt:declaredTestCase      ldpt:RdfSource-ServerOpen ;
+        ldpt:steps                 ( "Given a client and a known RDF Source at a given URL" "Via some means, alter the rdf:type of the RDF Source (either adding, changing or removing).  Note it may be implementation dependent on what the server will allow and also when changed, what different behavior the client will have" "Verify that the client continues to operate as expected" ) ;
+        ldpt:testMethod            ldpt:clientOnly .
+
+ldpt:BasicContainer-ChangeRdfTypeValue
+        a                          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               <http://www.w3.org/TR/ldp#ldpr-cli-typeschange> ;
+        dcterms:date               "2014-07-18T15:57:05.198Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+        dcterms:subject            "MUST" ;
+        mf:action                  "" ;
+        mf:name                    "BasicContainer-ChangeRdfTypeValue" ;
+        td:reviewStatus            td:approved ;
+        td:specificationReference  [ a                td:Excerpt ;
+                                     rdfs:seeAlso     <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."^^<http://www.w3.org/2001/XMLSchema#string>
+                                   ] ;
+        ldpt:conformanceLevel      ldpt:MUST ;
+        ldpt:declaredInClass       "org.w3.ldp.testsuite.test.BasicContainerTest" ;
+        ldpt:declaredTestCase      ldpt:RdfSource-ChangeRdfTypeValue ;
+        ldpt:steps                 ( "Given a client and a known RDF Source at a given URL" "Via some means, alter the rdf:type of the RDF Source by adding or removing a rdf:type triple. Note it may be implementation dependent on what the server will allow and also when changed, what different behavior the client will have" "Verify that the client continues to operate as expected" ) ;
+        ldpt:testMethod            ldpt:clientOnly .
+
+ldpt:MemberResource-ServerOpen
+        a                          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                 "MemberResource-ServerOpen" ;
+        rdfs:seeAlso               <http://www.w3.org/TR/ldp#ldpr-cli-openpreds> ;
+        dcterms:date               "2014-07-18T15:57:05.153Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+        dcterms:subject            "SHOULD" ;
+        mf:action                  "" ;
+        mf:name                    "MemberResource-ServerOpen" ;
+        td:reviewStatus            td:approved ;
+        td:specificationReference  [ a                td:Excerpt ;
+                                     rdfs:seeAlso     <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."^^<http://www.w3.org/2001/XMLSchema#string>
+                                   ] ;
+        ldpt:conformanceLevel      ldpt:SHOULD ;
+        ldpt:declaredInClass       "org.w3.ldp.testsuite.test.MemberResourceTest" ;
+        ldpt:declaredTestCase      ldpt:RdfSource-ServerOpen ;
+        ldpt:steps                 ( "Given a client and a known RDF Source at a given URL" "Via some means, alter the rdf:type of the RDF Source (either adding, changing or removing).  Note it may be implementation dependent on what the server will allow and also when changed, what different behavior the client will have" "Verify that the client continues to operate as expected" ) ;
+        ldpt:testMethod            ldpt:clientOnly .
+
+ldpt:DirectContainer-SHOULDManifest
+        a             mf:Manifest ;
+        rdfs:comment  "LDP Direct Container tests. SHOULD conformance tests." ;
+        <http://purl.org/dc/elements/1.1/title>
+                "DirectContainer (SHOULD)" ;
+        mf:entries    ( ldpt:DirectContainer-ClientPostToCreate ldpt:DirectContainer-ServerOpen ) ;
+        mf:name       "DirectContainer (SHOULD)" .
+
+ldpt:BasicContainer-AllowResponsesFromServer
+        a                          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               <http://www.w3.org/TR/ldp#ldpr-cli-hints-ignorable> ;
+        dcterms:date               "2014-07-18T15:57:05.202Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+        dcterms:subject            "MUST" ;
+        mf:action                  "" ;
+        mf:name                    "BasicContainer-AllowResponsesFromServer" ;
+        td:reviewStatus            td:approved ;
+        td:specificationReference  [ a                td:Excerpt ;
+                                     rdfs:seeAlso     <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."^^<http://www.w3.org/2001/XMLSchema#string>
+                                   ] ;
+        ldpt:conformanceLevel      ldpt:MUST ;
+        ldpt:declaredInClass       "org.w3.ldp.testsuite.test.BasicContainerTest" ;
+        ldpt:declaredTestCase      ldpt:RdfSource-AllowResponsesFromServer ;
+        ldpt:steps                 ( "Determine certain hints that your server would ignore" "Form a client request that uses this hint" "Execute the request and analyze the result" "Verify that client processes request as expected" ) ;
+        ldpt:testMethod            ldpt:clientOnly .
+
+ldpt:DirectContainer-ClientMayProvideHints
+        a                          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               <http://www.w3.org/TR/ldp#ldpr-cli-can-hint> ;
+        dcterms:date               "2014-07-18T15:57:05.229Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+        dcterms:subject            "MAY" ;
+        mf:action                  "" ;
+        mf:name                    "DirectContainer-ClientMayProvideHints" ;
+        td:reviewStatus            td:unreviewed ;
+        td:specificationReference  [ a                td:Excerpt ;
+                                     rdfs:seeAlso     <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. "^^<http://www.w3.org/2001/XMLSchema#string>
+                                   ] ;
+        ldpt:conformanceLevel      ldpt:MAY ;
+        ldpt:declaredInClass       "org.w3.ldp.testsuite.test.DirectContainerTest" ;
+        ldpt:declaredTestCase      ldpt:RdfSource-ClientMayProvideHints ;
+        ldpt:steps                 ( "Given a URL to a known RDF Source" "Configure the client application, if needed, to use the Prefer header to omit either containment or membership triples" "Use the client to send the GET request" "Monitor to ensure the server receives the hint" "Monitor to ensure the server honors the hing" "Verify the client behavior receives the optimized response" ) ;
+        ldpt:testMethod            ldpt:clientOnly .
+
+ldpt:DirectContainer-AllowResponsesFromServer
+        a                          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               <http://www.w3.org/TR/ldp#ldpr-cli-hints-ignorable> ;
+        dcterms:date               "2014-07-18T15:57:05.227Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+        dcterms:subject            "MUST" ;
+        mf:action                  "" ;
+        mf:name                    "DirectContainer-AllowResponsesFromServer" ;
+        td:reviewStatus            td:approved ;
+        td:specificationReference  [ a                td:Excerpt ;
+                                     rdfs:seeAlso     <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."^^<http://www.w3.org/2001/XMLSchema#string>
+                                   ] ;
+        ldpt:conformanceLevel      ldpt:MUST ;
+        ldpt:declaredInClass       "org.w3.ldp.testsuite.test.DirectContainerTest" ;
+        ldpt:declaredTestCase      ldpt:RdfSource-AllowResponsesFromServer ;
+        ldpt:steps                 ( "Determine certain hints that your server would ignore" "Form a client request that uses this hint" "Execute the request and analyze the result" "Verify that client processes request as expected" ) ;
+        ldpt:testMethod            ldpt:clientOnly .
+
+ldpt:BasicContainer-MAYManifest
+        a             mf:Manifest ;
+        rdfs:comment  "LDP Basic Container tests. MAY conformance tests." ;
+        <http://purl.org/dc/elements/1.1/title>
+                "BasicContainer (MAY)" ;
+        mf:entries    ( ldpt:BasicContainer-ClientMayProvideHints ) ;
+        mf:name       "BasicContainer (MAY)" .
+
+ldpt:MemberResource-ClientMayProvideHints
+        a                          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                 "MemberResource-ClientMayProvideHints" ;
+        rdfs:seeAlso               <http://www.w3.org/TR/ldp#ldpr-cli-can-hint> ;
+        dcterms:date               "2014-07-18T15:57:05.159Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+        dcterms:subject            "MAY" ;
+        mf:action                  "" ;
+        mf:name                    "MemberResource-ClientMayProvideHints" ;
+        td:reviewStatus            td:unreviewed ;
+        td:specificationReference  [ a                td:Excerpt ;
+                                     rdfs:seeAlso     <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. "^^<http://www.w3.org/2001/XMLSchema#string>
+                                   ] ;
+        ldpt:conformanceLevel      ldpt:MAY ;
+        ldpt:declaredInClass       "org.w3.ldp.testsuite.test.MemberResourceTest" ;
+        ldpt:declaredTestCase      ldpt:RdfSource-ClientMayProvideHints ;
+        ldpt:steps                 ( "Given a URL to a known RDF Source" "Configure the client application, if needed, to use the Prefer header to omit either containment or membership triples" "Use the client to send the GET request" "Monitor to ensure the server receives the hint" "Monitor to ensure the server honors the hing" "Verify the client behavior receives the optimized response" ) ;
+        ldpt:testMethod            ldpt:clientOnly .
+
+ldpt:IndirectContainer-ClientMayProvideHints
+        a                          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               <http://www.w3.org/TR/ldp#ldpr-cli-can-hint> ;
+        dcterms:date               "2014-07-18T15:57:05.253Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+        dcterms:subject            "MAY" ;
+        mf:action                  "" ;
+        mf:name                    "IndirectContainer-ClientMayProvideHints" ;
+        td:reviewStatus            td:unreviewed ;
+        td:specificationReference  [ a                td:Excerpt ;
+                                     rdfs:seeAlso     <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. "^^<http://www.w3.org/2001/XMLSchema#string>
+                                   ] ;
+        ldpt:conformanceLevel      ldpt:MAY ;
+        ldpt:declaredInClass       "org.w3.ldp.testsuite.test.IndirectContainerTest" ;
+        ldpt:declaredTestCase      ldpt:RdfSource-ClientMayProvideHints ;
+        ldpt:steps                 ( "Given a URL to a known RDF Source" "Configure the client application, if needed, to use the Prefer header to omit either containment or membership triples" "Use the client to send the GET request" "Monitor to ensure the server receives the hint" "Monitor to ensure the server honors the hing" "Verify the client behavior receives the optimized response" ) ;
+        ldpt:testMethod            ldpt:clientOnly .
+
+ldpt:DirectContainer-MAYManifest
+        a             mf:Manifest ;
+        rdfs:comment  "LDP Direct Container tests. MAY conformance tests." ;
+        <http://purl.org/dc/elements/1.1/title>
+                "DirectContainer (MAY)" ;
+        mf:entries    ( ldpt:DirectContainer-ClientMayProvideHints ) ;
+        mf:name       "DirectContainer (MAY)" .
+
+ldpt:DirectContainer-AllowMultipleRdfTypes
+        a                          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               <http://www.w3.org/TR/ldp#ldp-cli-multitype> ;
+        dcterms:date               "2014-07-18T15:57:05.222Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+        dcterms:subject            "MUST" ;
+        mf:action                  "" ;
+        mf:name                    "DirectContainer-AllowMultipleRdfTypes" ;
+        td:reviewStatus            td:approved ;
+        td:specificationReference  [ a                td:Excerpt ;
+                                     rdfs:seeAlso     <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."^^<http://www.w3.org/2001/XMLSchema#string>
+                                   ] ;
+        ldpt:conformanceLevel      ldpt:MUST ;
+        ldpt:declaredInClass       "org.w3.ldp.testsuite.test.DirectContainerTest" ;
+        ldpt:declaredTestCase      ldpt:RdfSource-AllowMultipleRdfTypes ;
+        ldpt:steps                 ( "Given a client and a known RDF Source at a given URL" "Via some means, alter the rdf:type of the RDF Source by adding another rdf:type. Note it may be implementation dependent on what the server will allow and also when changed, what different behavior the client will have" "Verify that the client continues to operate as expected" ) ;
+        ldpt:testMethod            ldpt:clientOnly .
+
+ldpt:IndirectContainer-ClientPostToCreate
+        a                          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               <http://www.w3.org/TR/ldp#ldpc-post-created201> ;
+        dcterms:date               "2014-07-18T15:57:05.239Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+        dcterms:subject            "SHOULD" ;
+        mf:action                  "" ;
+        mf:name                    "IndirectContainer-ClientPostToCreate" ;
+        td:reviewStatus            td:approved ;
+        td:specificationReference  [ a                td:Excerpt ;
+                                     rdfs:seeAlso     <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."^^<http://www.w3.org/2001/XMLSchema#string>
+                                   ] ;
+        ldpt:conformanceLevel      ldpt:SHOULD ;
+        ldpt:declaredInClass       "org.w3.ldp.testsuite.test.IndirectContainerTest" ;
+        ldpt:declaredTestCase      ldpt:CommonContainer-ClientPostToCreate ;
+        ldpt:steps                 ( "Given a container URL and POST is supported" "Monitor the client's request to ensure a POST request is sent" "Verify the response has a response status code of 201-Created and Location header with URL of created resource" ) ;
+        ldpt:testMethod            ldpt:clientOnly .
+
+ldpt:MemberResource-AllowMultipleRdfTypes
+        a                          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                 "MemberResource-AllowMultipleRdfTypes" ;
+        rdfs:seeAlso               <http://www.w3.org/TR/ldp#ldp-cli-multitype> ;
+        dcterms:date               "2014-07-18T15:57:05.038Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+        dcterms:subject            "MUST" ;
+        mf:action                  "" ;
+        mf:name                    "MemberResource-AllowMultipleRdfTypes" ;
+        td:reviewStatus            td:approved ;
+        td:specificationReference  [ a                td:Excerpt ;
+                                     rdfs:seeAlso     <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."^^<http://www.w3.org/2001/XMLSchema#string>
+                                   ] ;
+        ldpt:conformanceLevel      ldpt:MUST ;
+        ldpt:declaredInClass       "org.w3.ldp.testsuite.test.MemberResourceTest" ;
+        ldpt:declaredTestCase      ldpt:RdfSource-AllowMultipleRdfTypes ;
+        ldpt:steps                 ( "Given a client and a known RDF Source at a given URL" "Via some means, alter the rdf:type of the RDF Source by adding another rdf:type. Note it may be implementation dependent on what the server will allow and also when changed, what different behavior the client will have" "Verify that the client continues to operate as expected" ) ;
+        ldpt:testMethod            ldpt:clientOnly .
+
+ldpt:IndirectContainer-AllowResponsesFromServer
+        a                          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               <http://www.w3.org/TR/ldp#ldpr-cli-hints-ignorable> ;
+        dcterms:date               "2014-07-18T15:57:05.251Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+        dcterms:subject            "MUST" ;
+        mf:action                  "" ;
+        mf:name                    "IndirectContainer-AllowResponsesFromServer" ;
+        td:reviewStatus            td:approved ;
+        td:specificationReference  [ a                td:Excerpt ;
+                                     rdfs:seeAlso     <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."^^<http://www.w3.org/2001/XMLSchema#string>
+                                   ] ;
+        ldpt:conformanceLevel      ldpt:MUST ;
+        ldpt:declaredInClass       "org.w3.ldp.testsuite.test.IndirectContainerTest" ;
+        ldpt:declaredTestCase      ldpt:RdfSource-AllowResponsesFromServer ;
+        ldpt:steps                 ( "Determine certain hints that your server would ignore" "Form a client request that uses this hint" "Execute the request and analyze the result" "Verify that client processes request as expected" ) ;
+        ldpt:testMethod            ldpt:clientOnly .
+
+ldpt:IndirectContainer-AllowMultipleRdfTypes
+        a                          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               <http://www.w3.org/TR/ldp#ldp-cli-multitype> ;
+        dcterms:date               "2014-07-18T15:57:05.246Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+        dcterms:subject            "MUST" ;
+        mf:action                  "" ;
+        mf:name                    "IndirectContainer-AllowMultipleRdfTypes" ;
+        td:reviewStatus            td:approved ;
+        td:specificationReference  [ a                td:Excerpt ;
+                                     rdfs:seeAlso     <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."^^<http://www.w3.org/2001/XMLSchema#string>
+                                   ] ;
+        ldpt:conformanceLevel      ldpt:MUST ;
+        ldpt:declaredInClass       "org.w3.ldp.testsuite.test.IndirectContainerTest" ;
+        ldpt:declaredTestCase      ldpt:RdfSource-AllowMultipleRdfTypes ;
+        ldpt:steps                 ( "Given a client and a known RDF Source at a given URL" "Via some means, alter the rdf:type of the RDF Source by adding another rdf:type. Note it may be implementation dependent on what the server will allow and also when changed, what different behavior the client will have" "Verify that the client continues to operate as expected" ) ;
+        ldpt:testMethod            ldpt:clientOnly .
+
+ldpt:IndirectContainer-ServerOpen
+        a                          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                 "IndirectContainer-ServerOpen" ;
+        rdfs:seeAlso               <http://www.w3.org/TR/ldp#ldpr-cli-openpreds> ;
+        dcterms:date               "2014-07-18T15:57:05.249Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+        dcterms:subject            "SHOULD" ;
+        mf:action                  "" ;
+        mf:name                    "IndirectContainer-ServerOpen" ;
+        td:reviewStatus            td:approved ;
+        td:specificationReference  [ a                td:Excerpt ;
+                                     rdfs:seeAlso     <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."^^<http://www.w3.org/2001/XMLSchema#string>
+                                   ] ;
+        ldpt:conformanceLevel      ldpt:SHOULD ;
+        ldpt:declaredInClass       "org.w3.ldp.testsuite.test.IndirectContainerTest" ;
+        ldpt:declaredTestCase      ldpt:RdfSource-ServerOpen ;
+        ldpt:steps                 ( "Given a client and a known RDF Source at a given URL" "Via some means, alter the rdf:type of the RDF Source (either adding, changing or removing).  Note it may be implementation dependent on what the server will allow and also when changed, what different behavior the client will have" "Verify that the client continues to operate as expected" ) ;
+        ldpt:testMethod            ldpt:clientOnly .
+
+ldpt:BasicContainer-MUSTManifest
+        a             mf:Manifest ;
+        rdfs:comment  "LDP Basic Container tests. MUST conformance tests." ;
+        <http://purl.org/dc/elements/1.1/title>
+                "BasicContainer (MUST)" ;
+        mf:entries    ( ldpt:BasicContainer-AllowMultipleRdfTypes ldpt:BasicContainer-ChangeRdfTypeValue ldpt:BasicContainer-GetResourcePreservesTriples ldpt:BasicContainer-AllowResponsesFromServer ) ;
+        mf:name       "BasicContainer (MUST)" .
+
+ldpt:RDFSource-MAYManifest
+        a             mf:Manifest ;
+        rdfs:comment  "LDP RDF Source tests. MAY conformance tests." ;
+        <http://purl.org/dc/elements/1.1/title>
+                "RDFSource (MAY)" ;
+        mf:entries    ( ldpt:MemberResource-ClientMayProvideHints ) ;
+        mf:name       "RDFSource (MAY)" .
+
+ldpt:DirectContainer-ChangeRdfTypeValue
+        a                          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               <http://www.w3.org/TR/ldp#ldpr-cli-typeschange> ;
+        dcterms:date               "2014-07-18T15:57:05.223Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+        dcterms:subject            "MUST" ;
+        mf:action                  "" ;
+        mf:name                    "DirectContainer-ChangeRdfTypeValue" ;
+        td:reviewStatus            td:approved ;
+        td:specificationReference  [ a                td:Excerpt ;
+                                     rdfs:seeAlso     <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."^^<http://www.w3.org/2001/XMLSchema#string>
+                                   ] ;
+        ldpt:conformanceLevel      ldpt:MUST ;
+        ldpt:declaredInClass       "org.w3.ldp.testsuite.test.DirectContainerTest" ;
+        ldpt:declaredTestCase      ldpt:RdfSource-ChangeRdfTypeValue ;
+        ldpt:steps                 ( "Given a client and a known RDF Source at a given URL" "Via some means, alter the rdf:type of the RDF Source by adding or removing a rdf:type triple. Note it may be implementation dependent on what the server will allow and also when changed, what different behavior the client will have" "Verify that the client continues to operate as expected" ) ;
+        ldpt:testMethod            ldpt:clientOnly .
+
+ldpt:RDFSource-MUSTManifest
+        a             mf:Manifest ;
+        rdfs:comment  "LDP RDF Source tests. MUST conformance tests." ;
+        <http://purl.org/dc/elements/1.1/title>
+                "RDFSource (MUST)" ;
+        mf:entries    ( ldpt:MemberResource-AllowMultipleRdfTypes ldpt:MemberResource-ChangeRdfTypeValue ldpt:MemberResource-GetResourcePreservesTriples ldpt:MemberResource-AllowResponsesFromServer ) ;
+        mf:name       "RDFSource (MUST)" .
--- a/tests/reports/ldp-earl-manifest.jsonld	Fri Jul 18 17:00:28 2014 +0200
+++ b/tests/reports/ldp-earl-manifest.jsonld	Sun Jul 20 20:11:42 2014 -0400
@@ -1,2322 +1,1612 @@
 {
   "@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" : "_:t1",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_: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. "
+    "seeAlso" : "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" : "_: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"
-    },
+    "seeAlso" : "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" : "_:t105",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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"
-    },
+    "@id" : "_:t106",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t107",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t110",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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"
-    },
+    "@id" : "_:t117",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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"
-    },
+    "@id" : "_:t119",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t120",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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"
-    },
+    "seeAlso" : "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" : "_:t124",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t125",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t126",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t127",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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]."
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "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" : "_: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"
-    },
+    "seeAlso" : "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" : "_:t138",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t141",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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"
-    },
+    "seeAlso" : "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" : "_:t143",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t144",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t147",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "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" : "_:t149",
     "rdf:type" : {
       "@id" : "td:Excerpt"
     },
-    "rdfs:seeAlso" : {
-      "@id" : "http://www.w3.org/TR/ldp#ldpr-get-options"
-    },
+    "seeAlso" : "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" : "_:t15",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t158",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t16",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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"
-    },
+    "@id" : "_:t163",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t164",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_: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)"
+    "seeAlso" : "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" : "_:t166",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "http://www.w3.org/TR/ldp#ldpr-head-must",
+    "td:includesText" : "LDP servers MUST support the HTTP HEAD method. "
+  }, {
+    "@id" : "_:t169",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t17",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_: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"
-    },
+    "seeAlso" : "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" : "_:t175",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t18",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t180",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t181",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t19",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "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" : "_:t191",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t194",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t197",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t198",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t2",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "http://www.w3.org/TR/ldp#ldpr-gen-http",
+    "td:includesText" : "LDP servers MUST at least be HTTP/1.1 conformant servers [HTTP11]."
+  }, {
+    "@id" : "_:t20",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "http://www.w3.org/TR/ldp#ldpr-head-must",
+    "td:includesText" : "LDP servers MUST support the HTTP HEAD method. "
   }, {
     "@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."
+    "seeAlso" : "http://www.w3.org/TR/ldp#ldpr-get-must",
+    "td:includesText" : "LDP servers MUST support the HTTP GET Method for LDPRs"
   }, {
     "@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]. "
+    "seeAlso" : "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" : "_:t209",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t21",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t211",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t218",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t219",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_: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)"
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "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" : "_:t224",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t225",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_: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"
-    },
+    "seeAlso" : "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" : "_:t229",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t230",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "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" : "_:t24",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_: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"
-    },
+    "seeAlso" : "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" : "_:t243",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t246",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t247",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "http://www.w3.org/TR/ldp#ldpr-options-must",
+    "td:includesText" : "LDP servers MUST support the HTTP OPTIONS method. "
+  }, {
+    "@id" : "_:t253",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t256",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t259",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "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" : "_: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"
-    },
+    "seeAlso" : "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."
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "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" : "_: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"
-    },
+    "seeAlso" : "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" : "_:t275",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_: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"
-    },
+    "seeAlso" : "http://www.w3.org/TR/ldp#ldpr-options-must",
+    "td:includesText" : "LDP servers MUST support the HTTP OPTIONS method. "
+  }, {
+    "@id" : "_:t280",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t281",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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."
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "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" : "_:t295",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t297",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t3",
     "rdf:type" : {
       "@id" : "td:Excerpt"
     },
-    "rdfs:seeAlso" : {
-      "@id" : "http://www.w3.org/TR/ldp#ldpr-options-must"
-    },
+    "seeAlso" : "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" : "_:t304",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "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" : "_:t306",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t309",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t31",
     "rdf:type" : {
       "@id" : "td:Excerpt"
     },
-    "rdfs:seeAlso" : {
-      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-simpleupdate"
-    },
+    "seeAlso" : "http://www.w3.org/TR/ldp#ldpr-gen-http",
+    "td:includesText" : "LDP servers MUST at least be HTTP/1.1 conformant servers [HTTP11]."
+  }, {
+    "@id" : "_:t312",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t315",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t318",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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."
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "http://www.w3.org/TR/ldp#ldpr-gen-http",
+    "td:includesText" : "LDP servers MUST at least be HTTP/1.1 conformant servers [HTTP11]."
   }, {
     "@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. "
+    "seeAlso" : "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" : "_:t326",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t328",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t331",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t333",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "http://www.w3.org/TR/ldp#ldpr-head-must",
+    "td:includesText" : "LDP servers MUST support the HTTP HEAD method. "
+  }, {
+    "@id" : "_:t335",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t336",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_: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. "
+    "seeAlso" : "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" : "_:t349",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t35",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t354",
     "rdf:type" : {
       "@id" : "td:Excerpt"
     },
-    "rdfs:seeAlso" : {
-      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-http"
-    },
+    "seeAlso" : "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" : "_:t359",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t360",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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. "
+    "seeAlso" : "http://www.w3.org/TR/ldp#ldpr-head-must",
+    "td:includesText" : "LDP servers MUST support the HTTP HEAD method. "
+  }, {
+    "@id" : "_:t365",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_: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. "
+    "seeAlso" : "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" : "_:t371",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t372",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "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" : "_:t375",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t379",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t380",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t382",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t383",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t385",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t386",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_: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]."
+    "seeAlso" : "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" : "_:t393",
     "rdf:type" : {
       "@id" : "td:Excerpt"
     },
-    "rdfs:seeAlso" : {
-      "@id" : "http://www.w3.org/TR/ldp#ldpr-put-precond"
-    },
+    "seeAlso" : "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" : "_:t394",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "http://www.w3.org/TR/ldp#ldpr-options-must",
+    "td:includesText" : "LDP servers MUST support the HTTP OPTIONS method. "
   }, {
     "@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. "
+    "seeAlso" : "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" : "_: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]."
+    "seeAlso" : "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" : "_:t4",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t40",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t400",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "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" : "_: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. "
+    "seeAlso" : "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" : "_:t407",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t408",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t409",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t41",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "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" : "_:t414",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_: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]. "
+    "seeAlso" : "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" : "_: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"
-    },
+    "seeAlso" : "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" : "_:t419",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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."
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "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" : "_:t428",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "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" : "_: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"
-    },
+    "seeAlso" : "http://www.w3.org/TR/ldp#ldpr-gen-http",
     "td:includesText" : "LDP servers MUST at least be HTTP/1.1 conformant servers [HTTP11]."
   }, {
+    "@id" : "_:t435",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t439",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t44",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "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" : "_: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"
-    },
+    "seeAlso" : "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" : "_:t446",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t453",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "http://www.w3.org/TR/ldp#ldpr-options-must",
+    "td:includesText" : "LDP servers MUST support the HTTP OPTIONS method. "
+  }, {
+    "@id" : "_:t454",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t455",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "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" : "_:t457",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "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" : "_:t463",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t464",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t465",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t466",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "http://www.w3.org/TR/ldp#ldpr-gen-http",
+    "td:includesText" : "LDP servers MUST at least be HTTP/1.1 conformant servers [HTTP11]."
+  }, {
+    "@id" : "_:t467",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "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" : "_:t47",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_: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. "
+    "seeAlso" : "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" : "_: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. "
+    "seeAlso" : "http://www.w3.org/TR/ldp#ldpr-gen-http",
+    "td:includesText" : "LDP servers MUST at least be HTTP/1.1 conformant servers [HTTP11]."
+  }, {
+    "@id" : "_:t472",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "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" : "_:t474",
     "rdf:type" : {
       "@id" : "td:Excerpt"
     },
-    "rdfs:seeAlso" : {
-      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-etags"
-    },
+    "seeAlso" : "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."
+    "seeAlso" : "http://www.w3.org/TR/ldp#ldpr-gen-http",
+    "td:includesText" : "LDP servers MUST at least be HTTP/1.1 conformant servers [HTTP11]."
   }, {
     "@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."
+    "seeAlso" : "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" : "_: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. "
+    "seeAlso" : "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" : "_: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]."
+    "seeAlso" : "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" : "_: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"
-    },
+    "seeAlso" : "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" : "_:t482",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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."
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "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" : "_:t488",
     "rdf:type" : {
       "@id" : "td:Excerpt"
     },
-    "rdfs:seeAlso" : {
-      "@id" : "http://www.w3.org/TR/ldp#ldpr-gen-pubclireqs"
-    },
+    "seeAlso" : "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" : "_:t489",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "http://www.w3.org/TR/ldp#ldpr-gen-http",
+    "td:includesText" : "LDP servers MUST at least be HTTP/1.1 conformant servers [HTTP11]."
   }, {
     "@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."
+    "seeAlso" : "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" : "_: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"
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "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" : "_: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. "
+    "seeAlso" : "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" : "_:t5",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "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" : "_:t502",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t503",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "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" : "_: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. "
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "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" : "_: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]."
+    "seeAlso" : "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" : "_:t52",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "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" : "_: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]."
+    "seeAlso" : "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" : "_:t62",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t63",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t64",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t7",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "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" : "_: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. "
+    "seeAlso" : "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" : "_:t74",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_: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. "
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "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" : "_: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. "
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "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" : "_: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. "
+    "seeAlso" : "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" : "_: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."
+    "seeAlso" : "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" : "_: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. "
+    "seeAlso" : "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" : "_:t92",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_: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]. "
+    "seeAlso" : "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" : "_:t98",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "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" : "_:t99",
+    "rdf:type" : {
+      "@id" : "td:Excerpt"
+    },
+    "seeAlso" : "http://www.w3.org/TR/ldp#ldpr-head-must",
+    "td:includesText" : "LDP servers MUST support the HTTP HEAD method. "
   }, {
     "@id" : "ldpt:BasicContainer-4xxErrorHasResponseBody",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.157Z"
+      "@value" : "2014-07-20T21:33:29.601Z"
     },
     "dcterms:subject" : "SHOULD",
     "rdf:type" : {
@@ -2324,29 +1614,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:unreviewed",
+    "specificationReference" : "_:t496",
+    "conformanceLevel" : "ldpt:SHOULD",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:RdfSource-4xxErrorHasResponseBody"
-    }
+    "declaredTestCase" : "ldpt:RdfSource-4xxErrorHasResponseBody",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/RdfSourceTest.html#test4xxErrorHasResponseBody()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-AcceptPatchHeader",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.165Z"
+      "@value" : "2014-07-20T21:33:29.613Z"
     },
     "dcterms:subject" : "MUST",
     "rdf:type" : {
@@ -2354,29 +1636,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t26",
+    "conformanceLevel" : "ldpt:MUST",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:CommonResource-AcceptPatchHeader"
-    }
+    "declaredTestCase" : "ldpt:CommonResource-AcceptPatchHeader",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/CommonResourceTest.html#testAcceptPatchHeader()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-AcceptPostResponseHeader",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.138Z"
+      "@value" : "2014-07-20T21:33:29.584Z"
     },
     "dcterms:subject" : "MUST",
     "rdf:type" : {
@@ -2384,29 +1658,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t5",
+    "conformanceLevel" : "ldpt:MUST",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:CommonContainer-AcceptPostResponseHeader"
-    }
+    "declaredTestCase" : "ldpt:CommonContainer-AcceptPostResponseHeader",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/CommonContainerTest.html#testAcceptPostResponseHeader()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-AcceptTurtle",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.133Z"
+      "@value" : "2014-07-20T21:33:29.579Z"
     },
     "dcterms:subject" : "MUST",
     "rdf:type" : {
@@ -2414,179 +1680,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t82",
+    "conformanceLevel" : "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"
-    }
+    "declaredTestCase" : "ldpt:CommonContainer-AcceptTurtle",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/CommonContainerTest.html#testAcceptTurtle()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-ConditionFailedStatusCode",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.163Z"
+      "@value" : "2014-07-20T21:33:29.61Z"
     },
     "dcterms:subject" : "MUST",
     "rdf:type" : {
@@ -2594,29 +1702,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t20",
+    "conformanceLevel" : "ldpt:MUST",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:CommonResource-ConditionFailedStatusCode"
-    }
+    "declaredTestCase" : "ldpt:CommonResource-ConditionFailedStatusCode",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/CommonResourceTest.html#testConditionFailedStatusCode()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-ContainerSupportsHttpLinkHeader",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.128Z"
+      "@value" : "2014-07-20T21:33:29.572Z"
     },
     "dcterms:subject" : "MUST",
     "rdf:type" : {
@@ -2624,59 +1724,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t218",
+    "conformanceLevel" : "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"
-    }
+    "declaredTestCase" : "ldpt:BasicContainer-ContainerSupportsHttpLinkHeader",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/BasicContainerTest.html#testContainerSupportsHttpLinkHeader()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-ContainsRdfType",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.147Z"
+      "@value" : "2014-07-20T21:33:29.592Z"
     },
     "dcterms:subject" : "SHOULD",
     "rdf:type" : {
@@ -2684,29 +1746,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t41",
+    "conformanceLevel" : "ldpt:SHOULD",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:RdfSource-ContainsRdfType"
-    }
+    "declaredTestCase" : "ldpt:RdfSource-ContainsRdfType",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/RdfSourceTest.html#testContainsRdfType()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-ContentTypeHeader",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.134Z"
+      "@value" : "2014-07-20T21:33:29.579Z"
     },
     "dcterms:subject" : "SHOULD",
     "rdf:type" : {
@@ -2714,29 +1768,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:unreviewed",
+    "specificationReference" : "_:t410",
+    "conformanceLevel" : "ldpt:SHOULD",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:CommonContainer-ContentTypeHeader"
-    }
+    "declaredTestCase" : "ldpt:CommonContainer-ContentTypeHeader",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/CommonContainerTest.html#testContentTypeHeader()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-CreateWithoutConstraints",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.136Z"
+      "@value" : "2014-07-20T21:33:29.582Z"
     },
     "dcterms:subject" : "SHOULD",
     "rdf:type" : {
@@ -2744,29 +1790,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t383",
+    "conformanceLevel" : "ldpt:SHOULD",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:CommonContainer-CreateWithoutConstraints"
-    }
+    "declaredTestCase" : "ldpt:CommonContainer-CreateWithoutConstraints",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/CommonContainerTest.html#testCreateWithoutConstraints()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-DeleteRemovesContainmentTriple",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.14Z"
+      "@value" : "2014-07-20T21:33:29.586Z"
     },
     "dcterms:subject" : "MUST",
     "rdf:type" : {
@@ -2774,29 +1812,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t304",
+    "conformanceLevel" : "ldpt:MUST",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:CommonContainer-DeleteRemovesContainmentTriple"
-    }
+    "declaredTestCase" : "ldpt:CommonContainer-DeleteRemovesContainmentTriple",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/CommonContainerTest.html#testDeleteRemovesContainmentTriple()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-ETagHeadersGet",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.16Z"
+      "@value" : "2014-07-20T21:33:29.606Z"
     },
     "dcterms:subject" : "MUST",
     "rdf:type" : {
@@ -2804,29 +1834,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:unreviewed",
+    "specificationReference" : "_:t474",
+    "conformanceLevel" : "ldpt:MUST",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:CommonResource-ETagHeadersGet"
-    }
+    "declaredTestCase" : "ldpt:CommonResource-ETagHeadersGet",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/CommonResourceTest.html#testETagHeadersGet()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-ETagHeadersHead",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.161Z"
+      "@value" : "2014-07-20T21:33:29.607Z"
     },
     "dcterms:subject" : "MUST",
     "rdf:type" : {
@@ -2834,29 +1856,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t339",
+    "conformanceLevel" : "ldpt:MUST",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:CommonResource-ETagHeadersHead"
-    }
+    "declaredTestCase" : "ldpt:CommonResource-ETagHeadersHead",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/CommonResourceTest.html#testETagHeadersHead()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-GetResource",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.146Z"
+      "@value" : "2014-07-20T21:33:29.592Z"
     },
     "dcterms:subject" : "MUST",
     "rdf:type" : {
@@ -2864,29 +1878,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t202",
+    "conformanceLevel" : "ldpt:MUST",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:RdfSource-GetResource"
-    }
+    "declaredTestCase" : "ldpt:RdfSource-GetResource",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/RdfSourceTest.html#testGetResource()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-GetResourceAcceptTurtle",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.153Z"
+      "@value" : "2014-07-20T21:33:29.598Z"
     },
     "dcterms:subject" : "MUST",
     "rdf:type" : {
@@ -2894,59 +1900,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t489",
+    "conformanceLevel" : "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"
-    }
+    "declaredTestCase" : "ldpt:RdfSource-GetResourceAcceptTurtle",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/RdfSourceTest.html#testGetResourceAcceptTurtle()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-GetResponseHeaders",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.162Z"
+      "@value" : "2014-07-20T21:33:29.608Z"
     },
     "dcterms:subject" : "MUST",
     "rdf:type" : {
@@ -2954,29 +1922,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t194",
+    "conformanceLevel" : "ldpt:MUST",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:CommonResource-GetResponseHeaders"
-    }
+    "declaredTestCase" : "ldpt:CommonResource-GetResponseHeaders",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/CommonResourceTest.html#testGetResponseHeaders()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-Head",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.165Z"
+      "@value" : "2014-07-20T21:33:29.613Z"
     },
     "dcterms:subject" : "MUST",
     "rdf:type" : {
@@ -2984,59 +1944,43 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t99",
+    "conformanceLevel" : "ldpt:MUST",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:CommonResource-Head"
-    }
+    "declaredTestCase" : "ldpt:CommonResource-Head",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/CommonResourceTest.html#testHead()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-IsHttp11Manual",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.159Z"
-    },
-    "dcterms:subject" : "MUST",
+      "@value" : "2014-07-20T21:33:29.605Z"
+    },
+    "dcterms:subject" : "MUST, MANUAL",
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t360",
+    "conformanceLevel" : [ "ldpt:MUST", "ldpt:MANUAL" ],
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:CommonResource-IsHttp11Manual"
-    }
+    "declaredTestCase" : "ldpt:CommonResource-IsHttp11Manual",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/CommonResourceTest.html#testIsHttp11Manual()",
+    "testMethod" : "ldpt:manual"
   }, {
     "@id" : "ldpt:BasicContainer-IsHttp11Server",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.159Z"
+      "@value" : "2014-07-20T21:33:29.603Z"
     },
     "dcterms:subject" : "MUST",
     "rdf:type" : {
@@ -3044,29 +1988,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:unreviewed",
+    "specificationReference" : "_:t2",
+    "conformanceLevel" : "ldpt:MUST",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:CommonResource-IsHttp11Server"
-    }
+    "declaredTestCase" : "ldpt:CommonResource-IsHttp11Server",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/CommonResourceTest.html#testIsHttp11Server()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-JsonLdRepresentation",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.154Z"
+      "@value" : "2014-07-20T21:33:29.599Z"
     },
     "dcterms:subject" : "SHOULD",
     "rdf:type" : {
@@ -3074,29 +2010,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:unreviewed",
+    "specificationReference" : "_:t133",
+    "conformanceLevel" : "ldpt:SHOULD",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:RdfSource-JsonLdRepresentation"
-    }
+    "declaredTestCase" : "ldpt:RdfSource-JsonLdRepresentation",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/RdfSourceTest.html#testJsonLdRepresentation()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-LdpLinkHeader",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.161Z"
+      "@value" : "2014-07-20T21:33:29.607Z"
     },
     "dcterms:subject" : "MUST",
     "rdf:type" : {
@@ -3104,24 +2032,16 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t446",
+    "conformanceLevel" : "ldpt:MUST",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:CommonResource-LdpLinkHeader"
-    }
+    "declaredTestCase" : "ldpt:CommonResource-LdpLinkHeader",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/CommonResourceTest.html#testLdpLinkHeader()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-MAYManifest",
     "http://purl.org/dc/elements/1.1/title" : "BasicContainer (MAY)",
@@ -3129,18 +2049,8 @@
       "@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"
-      } ]
+    "entries" : {
+      "@list" : [ "ldpt:BasicContainer-PutToCreate", "ldpt:BasicContainer-RdfTypeLdpContainer", "ldpt:BasicContainer-ServerHonorsSlug", "ldpt:BasicContainer-TypeRdfSource" ]
     },
     "mf:name" : "BasicContainer (MAY)"
   }, {
@@ -3150,91 +2060,15 @@
       "@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"
-      } ]
+    "entries" : {
+      "@list" : [ "ldpt:BasicContainer-ContainerSupportsHttpLinkHeader", "ldpt:BasicContainer-RelativeUriResolutionPost", "ldpt:BasicContainer-PostResponseStatusAndLocation", "ldpt:BasicContainer-PostContainer", "ldpt:BasicContainer-RequestedInteractionModelCreateNotAllowed", "ldpt:BasicContainer-RequestedInteractionModelHeaders", "ldpt:BasicContainer-AcceptTurtle", "ldpt:BasicContainer-NullRelativeUriPost", "ldpt:BasicContainer-AcceptPostResponseHeader", "ldpt:BasicContainer-DeleteRemovesContainmentTriple", "ldpt:BasicContainer-RelativeUriResolutionPut", "ldpt:BasicContainer-PutReplacesResource", "ldpt:BasicContainer-PutSimpleUpdate", "ldpt:BasicContainer-GetResource", "ldpt:BasicContainer-RestrictClientInference", "ldpt:BasicContainer-GetResourceAcceptTurtle", "ldpt:BasicContainer-PublishConstraintsReadOnlyProp", "ldpt:BasicContainer-PublishConstraintsUnknownProp", "ldpt:BasicContainer-PutReadOnlyProperties4xxStatus", "ldpt:BasicContainer-PutPropertiesNotPersisted", "ldpt:BasicContainer-IsHttp11Server", "ldpt:BasicContainer-IsHttp11Manual", "ldpt:BasicContainer-ETagHeadersGet", "ldpt:BasicContainer-ETagHeadersHead", "ldpt:BasicContainer-LdpLinkHeader", "ldpt:BasicContainer-GetResponseHeaders", "ldpt:BasicContainer-ConditionFailedStatusCode", "ldpt:BasicContainer-PreconditionRequiredStatusCode", "ldpt:BasicContainer-PutBadETag", "ldpt:BasicContainer-Head", "ldpt:BasicContainer-AcceptPatchHeader", "ldpt:BasicContainer-Options", "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"
+      "@value" : "2014-07-20T21:33:29.575Z"
     },
     "dcterms:subject" : "SHOULD",
     "rdf:type" : {
@@ -3242,29 +2076,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t444",
+    "conformanceLevel" : "ldpt:SHOULD",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:CommonContainer-NoRdfBagSeqOrList"
-    }
+    "declaredTestCase" : "ldpt:CommonContainer-NoRdfBagSeqOrList",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/CommonContainerTest.html#testNoRdfBagSeqOrList()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-NullRelativeUriPost",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.135Z"
+      "@value" : "2014-07-20T21:33:29.58Z"
     },
     "dcterms:subject" : "MUST",
     "rdf:type" : {
@@ -3272,29 +2098,32 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t386",
+    "conformanceLevel" : "ldpt:MUST",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:CommonContainer-NullRelativeUriPost"
-    }
+    "declaredTestCase" : "ldpt:CommonContainer-NullRelativeUriPost",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/CommonContainerTest.html#testNullRelativeUriPost()",
+    "testMethod" : "ldpt:automated"
+  }, {
+    "@id" : "ldpt:BasicContainer-OTHERManifest",
+    "http://purl.org/dc/elements/1.1/title" : "BasicContainer (OTHER)",
+    "rdf:type" : {
+      "@id" : "mf:Manifest"
+    },
+    "rdfs:comment" : "LDP Basic Container tests. No official conformance status.",
+    "entries" : {
+      "@list" : [ "ldpt:BasicContainer-ReUseVocabularies", "ldpt:BasicContainer-UseStandardVocabularies", "ldpt:BasicContainer-RestrictClientInference", "ldpt:BasicContainer-IsHttp11Manual" ]
+    },
+    "mf:name" : "BasicContainer (OTHER)"
   }, {
     "@id" : "ldpt:BasicContainer-Options",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.166Z"
+      "@value" : "2014-07-20T21:33:29.614Z"
     },
     "dcterms:subject" : "MUST",
     "rdf:type" : {
@@ -3302,29 +2131,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t3",
+    "conformanceLevel" : "ldpt:MUST",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:CommonResource-Options"
-    }
+    "declaredTestCase" : "ldpt:CommonResource-Options",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/CommonResourceTest.html#testOptions()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-OptionsAllowHeader",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.166Z"
+      "@value" : "2014-07-20T21:33:29.615Z"
     },
     "dcterms:subject" : "MUST",
     "rdf:type" : {
@@ -3332,29 +2153,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t405",
+    "conformanceLevel" : "ldpt:MUST",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:CommonResource-OptionsAllowHeader"
-    }
+    "declaredTestCase" : "ldpt:CommonResource-OptionsAllowHeader",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/CommonResourceTest.html#testOptionsAllowHeader()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-PatchMethod",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.14Z"
+      "@value" : "2014-07-20T21:33:29.586Z"
     },
     "dcterms:subject" : "SHOULD",
     "rdf:type" : {
@@ -3362,29 +2175,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t409",
+    "conformanceLevel" : "ldpt:SHOULD",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:CommonContainer-PatchMethod"
-    }
+    "declaredTestCase" : "ldpt:CommonContainer-PatchMethod",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/CommonContainerTest.html#testPatchMethod()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-PostContainer",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.131Z"
+      "@value" : "2014-07-20T21:33:29.577Z"
     },
     "dcterms:subject" : "MUST",
     "rdf:type" : {
@@ -3392,29 +2197,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t468",
+    "conformanceLevel" : "ldpt:MUST",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:CommonContainer-PostContainer"
-    }
+    "declaredTestCase" : "ldpt:CommonContainer-PostContainer",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/CommonContainerTest.html#testPostContainer()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-PostJsonLd",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.142Z"
+      "@value" : "2014-07-20T21:33:29.589Z"
     },
     "dcterms:subject" : "SHOULD",
     "rdf:type" : {
@@ -3422,29 +2219,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:unreviewed",
+    "specificationReference" : "_:t486",
+    "conformanceLevel" : "ldpt:SHOULD",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:CommonContainer-PostJsonLd"
-    }
+    "declaredTestCase" : "ldpt:CommonContainer-PostJsonLd",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/CommonContainerTest.html#testPostJsonLd()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-PostNoSlug",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.135Z"
+      "@value" : "2014-07-20T21:33:29.581Z"
     },
     "dcterms:subject" : "SHOULD",
     "rdf:type" : {
@@ -3452,29 +2241,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:unreviewed",
+    "specificationReference" : "_:t290",
+    "conformanceLevel" : "ldpt:SHOULD",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:CommonContainer-PostNoSlug"
-    }
+    "declaredTestCase" : "ldpt:CommonContainer-PostNoSlug",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/CommonContainerTest.html#testPostNoSlug()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-PostResponseStatusAndLocation",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.131Z"
+      "@value" : "2014-07-20T21:33:29.576Z"
     },
     "dcterms:subject" : "MUST",
     "rdf:type" : {
@@ -3482,29 +2263,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t372",
+    "conformanceLevel" : "ldpt:MUST",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:CommonContainer-PostResponseStatusAndLocation"
-    }
+    "declaredTestCase" : "ldpt:CommonContainer-PostResponseStatusAndLocation",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/CommonContainerTest.html#testPostResponseStatusAndLocation()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-PreconditionRequiredStatusCode",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.164Z"
+      "@value" : "2014-07-20T21:33:29.611Z"
     },
     "dcterms:subject" : "MUST",
     "rdf:type" : {
@@ -3512,29 +2285,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t379",
+    "conformanceLevel" : "ldpt:MUST",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:CommonResource-PreconditionRequiredStatusCode"
-    }
+    "declaredTestCase" : "ldpt:CommonResource-PreconditionRequiredStatusCode",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/CommonResourceTest.html#testPreconditionRequiredStatusCode()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-PreferContainmentTriples",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.143Z"
+      "@value" : "2014-07-20T21:33:29.575Z"
     },
     "dcterms:subject" : "SHOULD",
     "rdf:type" : {
@@ -3542,29 +2307,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:unreviewed",
+    "specificationReference" : "_:t17",
+    "conformanceLevel" : "ldpt:SHOULD",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:CommonContainer-PreferContainmentTriples"
-    }
+    "declaredTestCase" : "ldpt:CommonContainer-PreferContainmentTriples",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/CommonContainerTest.html#testPreferContainmentTriples()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-PublishConstraintsReadOnlyProp",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.155Z"
+      "@value" : "2014-07-20T21:33:29.599Z"
     },
     "dcterms:subject" : "MUST",
     "rdf:type" : {
@@ -3572,29 +2329,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:unreviewed",
+    "specificationReference" : "_:t439",
+    "conformanceLevel" : "ldpt:MUST",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:RdfSource-PublishConstraintsReadOnlyProp"
-    }
+    "declaredTestCase" : "ldpt:RdfSource-PublishConstraintsReadOnlyProp",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/RdfSourceTest.html#testPublishConstraintsReadOnlyProp()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-PublishConstraintsUnknownProp",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.156Z"
+      "@value" : "2014-07-20T21:33:29.6Z"
     },
     "dcterms:subject" : "MUST",
     "rdf:type" : {
@@ -3602,29 +2351,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:unreviewed",
+    "specificationReference" : "_:t501",
+    "conformanceLevel" : "ldpt:MUST",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:RdfSource-PublishConstraintsUnknownProp"
-    }
+    "declaredTestCase" : "ldpt:RdfSource-PublishConstraintsUnknownProp",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/RdfSourceTest.html#testPublishConstraintsUnknownProp()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-PutBadETag",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.164Z"
+      "@value" : "2014-07-20T21:33:29.612Z"
     },
     "dcterms:subject" : "MUST",
     "rdf:type" : {
@@ -3632,29 +2373,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t393",
+    "conformanceLevel" : "ldpt:MUST",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:CommonResource-PutBadETag"
-    }
+    "declaredTestCase" : "ldpt:CommonResource-PutBadETag",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/CommonResourceTest.html#testPutBadETag()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-PutPropertiesNotPersisted",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.157Z"
+      "@value" : "2014-07-20T21:33:29.602Z"
     },
     "dcterms:subject" : "MUST",
     "rdf:type" : {
@@ -3662,29 +2395,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:unreviewed",
+    "specificationReference" : "_:t175",
+    "conformanceLevel" : "ldpt:MUST",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:RdfSource-PutPropertiesNotPersisted"
-    }
+    "declaredTestCase" : "ldpt:RdfSource-PutPropertiesNotPersisted",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/RdfSourceTest.html#testPutPropertiesNotPersisted()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-PutReadOnlyProperties4xxStatus",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.156Z"
+      "@value" : "2014-07-20T21:33:29.601Z"
     },
     "dcterms:subject" : "MUST",
     "rdf:type" : {
@@ -3692,29 +2417,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:unreviewed",
+    "specificationReference" : "_:t322",
+    "conformanceLevel" : "ldpt:MUST",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:RdfSource-PutReadOnlyProperties4xxStatus"
-    }
+    "declaredTestCase" : "ldpt:RdfSource-PutReadOnlyProperties4xxStatus",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/RdfSourceTest.html#testPutReadOnlyProperties4xxStatus()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-PutReplacesResource",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.145Z"
+      "@value" : "2014-07-20T21:33:29.59Z"
     },
     "dcterms:subject" : "MUST",
     "rdf:type" : {
@@ -3722,29 +2439,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t256",
+    "conformanceLevel" : "ldpt:MUST",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:RdfSource-PutReplacesResource"
-    }
+    "declaredTestCase" : "ldpt:RdfSource-PutReplacesResource",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/RdfSourceTest.html#testPutReplacesResource()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-PutRequiresIfMatch",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.162Z"
+      "@value" : "2014-07-20T21:33:29.609Z"
     },
     "dcterms:subject" : "SHOULD",
     "rdf:type" : {
@@ -3752,29 +2461,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t131",
+    "conformanceLevel" : "ldpt:SHOULD",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:CommonResource-PutRequiresIfMatch"
-    }
+    "declaredTestCase" : "ldpt:CommonResource-PutRequiresIfMatch",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/CommonResourceTest.html#testPutRequiresIfMatch()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-PutSimpleUpdate",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.146Z"
+      "@value" : "2014-07-20T21:33:29.591Z"
     },
     "dcterms:subject" : "MUST",
     "rdf:type" : {
@@ -3782,29 +2483,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:unreviewed",
+    "specificationReference" : "_:t211",
+    "conformanceLevel" : "ldpt:MUST",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:RdfSource-PutSimpleUpdate"
-    }
+    "declaredTestCase" : "ldpt:RdfSource-PutSimpleUpdate",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/RdfSourceTest.html#testPutSimpleUpdate()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-PutToCreate",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.13Z"
+      "@value" : "2014-07-20T21:33:29.573Z"
     },
     "dcterms:subject" : "MAY",
     "rdf:type" : {
@@ -3812,29 +2505,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t397",
+    "conformanceLevel" : "ldpt:MAY",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:CommonContainer-PutToCreate"
-    }
+    "declaredTestCase" : "ldpt:CommonContainer-PutToCreate",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/CommonContainerTest.html#testPutToCreate()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-RdfTypeLdpContainer",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.141Z"
+      "@value" : "2014-07-20T21:33:29.587Z"
     },
     "dcterms:subject" : "MAY",
     "rdf:type" : {
@@ -3842,59 +2527,46 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:unreviewed",
+    "specificationReference" : "_:t164",
+    "conformanceLevel" : "ldpt:MAY",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:CommonContainer-RdfTypeLdpContainer"
-    }
+    "declaredTestCase" : "ldpt:CommonContainer-RdfTypeLdpContainer",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/CommonContainerTest.html#testRdfTypeLdpContainer()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-ReUseVocabularies",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.148Z"
-    },
-    "dcterms:subject" : "SHOULD",
+      "@value" : "2014-07-20T21:33:29.595Z"
+    },
+    "dcterms:subject" : "SHOULD, MANUAL",
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t105",
+    "conformanceLevel" : [ "ldpt:MANUAL", "ldpt:SHOULD" ],
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:RdfSource-ReUseVocabularies"
-    }
+    "declaredTestCase" : "ldpt:RdfSource-ReUseVocabularies",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/RdfSourceTest.html#testReUseVocabularies()",
+    "ldpt:steps" : {
+      "@list" : [ "Given a URL for a RDF Source, perform a GET using an RDF content type", "Inspect the content to ensure standard terms are used.  For example, if things like ex:label or ex:title are used, instead of DCTERMS or RDFS, then the test should fail." ]
+    },
+    "testMethod" : "ldpt:manual"
   }, {
     "@id" : "ldpt:BasicContainer-RejectPutModifyingContainmentTriples",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.138Z"
+      "@value" : "2014-07-20T21:33:29.584Z"
     },
     "dcterms:subject" : "SHOULD",
     "rdf:type" : {
@@ -3902,29 +2574,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t226",
+    "conformanceLevel" : "ldpt:SHOULD",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:CommonContainer-RejectPutModifyingContainmentTriples"
-    }
+    "declaredTestCase" : "ldpt:CommonContainer-RejectPutModifyingContainmentTriples",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/CommonContainerTest.html#testRejectPutModifyingContainmentTriples()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-RelativeUriResolutionPost",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.13Z"
+      "@value" : "2014-07-20T21:33:29.574Z"
     },
     "dcterms:subject" : "MUST",
     "rdf:type" : {
@@ -3932,29 +2596,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:unreviewed",
+    "specificationReference" : "_:t191",
+    "conformanceLevel" : "ldpt:MUST",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:CommonContainer-RelativeUriResolutionPost"
-    }
+    "declaredTestCase" : "ldpt:CommonContainer-RelativeUriResolutionPost",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/CommonContainerTest.html#testRelativeUriResolutionPost()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-RelativeUriResolutionPut",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.144Z"
+      "@value" : "2014-07-20T21:33:29.59Z"
     },
     "dcterms:subject" : "MUST",
     "rdf:type" : {
@@ -3962,29 +2618,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:unreviewed",
+    "specificationReference" : "_:t349",
+    "conformanceLevel" : "ldpt:MUST",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:RdfSource-RelativeUriResolutionPut"
-    }
+    "declaredTestCase" : "ldpt:RdfSource-RelativeUriResolutionPut",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/RdfSourceTest.html#testRelativeUriResolutionPut()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-RequestedInteractionModelCreateNotAllowed",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.132Z"
+      "@value" : "2014-07-20T21:33:29.577Z"
     },
     "dcterms:subject" : "MUST",
     "rdf:type" : {
@@ -3992,29 +2640,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:unreviewed",
+    "specificationReference" : "_:t246",
+    "conformanceLevel" : "ldpt:MUST",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:CommonContainer-RequestedInteractionModelCreateNotAllowed"
-    }
+    "declaredTestCase" : "ldpt:CommonContainer-RequestedInteractionModelCreateNotAllowed",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/CommonContainerTest.html#testRequestedInteractionModelCreateNotAllowed()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-RequestedInteractionModelHeaders",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.133Z"
+      "@value" : "2014-07-20T21:33:29.578Z"
     },
     "dcterms:subject" : "MUST",
     "rdf:type" : {
@@ -4022,29 +2662,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:unreviewed",
+    "specificationReference" : "_:t373",
+    "conformanceLevel" : "ldpt:MUST",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:CommonContainer-RequestedInteractionModelHeaders"
-    }
+    "declaredTestCase" : "ldpt:CommonContainer-RequestedInteractionModelHeaders",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/CommonContainerTest.html#testRequestedInteractionModelHeaders()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-ResponsePropertiesNotPersisted",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.158Z"
+      "@value" : "2014-07-20T21:33:29.603Z"
     },
     "dcterms:subject" : "SHOULD",
     "rdf:type" : {
@@ -4052,59 +2684,46 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:unreviewed",
+    "specificationReference" : "_:t268",
+    "conformanceLevel" : "ldpt:SHOULD",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:RdfSource-ResponsePropertiesNotPersisted"
-    }
+    "declaredTestCase" : "ldpt:RdfSource-ResponsePropertiesNotPersisted",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/RdfSourceTest.html#testResponsePropertiesNotPersisted()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-RestrictClientInference",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.151Z"
-    },
-    "dcterms:subject" : "MUST",
+      "@value" : "2014-07-20T21:33:29.597Z"
+    },
+    "dcterms:subject" : "MUST, MANUAL",
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t198",
+    "conformanceLevel" : [ "ldpt:MANUAL", "ldpt:MUST" ],
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:RdfSource-RestrictClientInference"
-    }
+    "declaredTestCase" : "ldpt:RdfSource-RestrictClientInference",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/RdfSourceTest.html#testRestrictClientInference()",
+    "ldpt:steps" : {
+      "@list" : [ "Perform a GET on a URL for the reource requesting an RDF content type", "Inspect the results (both headers and content) for missing terms.  Additionally could run an inferencing tool and compare results, seeing if needed informationshould have been explicitly listed by the server." ]
+    },
+    "testMethod" : "ldpt:manual"
   }, {
     "@id" : "ldpt:BasicContainer-RestrictPutReUseUri",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.139Z"
+      "@value" : "2014-07-20T21:33:29.585Z"
     },
     "dcterms:subject" : "SHOULD",
     "rdf:type" : {
@@ -4112,29 +2731,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t505",
+    "conformanceLevel" : "ldpt:SHOULD",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:CommonContainer-RestrictPutReUseUri"
-    }
+    "declaredTestCase" : "ldpt:CommonContainer-RestrictPutReUseUri",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/CommonContainerTest.html#testRestrictPutReUseUri()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-RestrictUriReUseNoSlug",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.137Z"
+      "@value" : "2014-07-20T21:33:29.583Z"
     },
     "dcterms:subject" : "SHOULD",
     "rdf:type" : {
@@ -4142,29 +2753,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t443",
+    "conformanceLevel" : "ldpt:SHOULD",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:CommonContainer-RestrictUriReUseNoSlug"
-    }
+    "declaredTestCase" : "ldpt:CommonContainer-RestrictUriReUseNoSlug",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/CommonContainerTest.html#testRestrictUriReUseNoSlug()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-RestrictUriReUseSlug",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.137Z"
+      "@value" : "2014-07-20T21:33:29.582Z"
     },
     "dcterms:subject" : "SHOULD",
     "rdf:type" : {
@@ -4172,24 +2775,16 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t142",
+    "conformanceLevel" : "ldpt:SHOULD",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:CommonContainer-RestrictUriReUseSlug"
-    }
+    "declaredTestCase" : "ldpt:CommonContainer-RestrictUriReUseSlug",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/CommonContainerTest.html#testRestrictUriReUseSlug()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-SHOULDManifest",
     "http://purl.org/dc/elements/1.1/title" : "BasicContainer (SHOULD)",
@@ -4197,55 +2792,15 @@
       "@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"
-      } ]
+    "entries" : {
+      "@list" : [ "ldpt:BasicContainer-NoRdfBagSeqOrList", "ldpt:BasicContainer-PreferContainmentTriples", "ldpt:BasicContainer-ContentTypeHeader", "ldpt:BasicContainer-PostNoSlug", "ldpt:BasicContainer-CreateWithoutConstraints", "ldpt:BasicContainer-RestrictUriReUseSlug", "ldpt:BasicContainer-RestrictUriReUseNoSlug", "ldpt:BasicContainer-RejectPutModifyingContainmentTriples", "ldpt:BasicContainer-RestrictPutReUseUri", "ldpt:BasicContainer-PatchMethod", "ldpt:BasicContainer-PostJsonLd", "ldpt:BasicContainer-ContainsRdfType", "ldpt:BasicContainer-ReUseVocabularies", "ldpt:BasicContainer-UseStandardVocabularies", "ldpt:BasicContainer-JsonLdRepresentation", "ldpt:BasicContainer-4xxErrorHasResponseBody", "ldpt:BasicContainer-ResponsePropertiesNotPersisted", "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"
+      "@value" : "2014-07-20T21:33:29.588Z"
     },
     "dcterms:subject" : "MAY",
     "rdf:type" : {
@@ -4253,59 +2808,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:unreviewed",
+    "specificationReference" : "_:t87",
+    "conformanceLevel" : "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"
-    }
+    "declaredTestCase" : "ldpt:CommonContainer-ServerHonorsSlug",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/CommonContainerTest.html#testServerHonorsSlug()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-TypeRdfSource",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.147Z"
+      "@value" : "2014-07-20T21:33:29.594Z"
     },
     "dcterms:subject" : "MAY",
     "rdf:type" : {
@@ -4313,59 +2830,46 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:unreviewed",
+    "specificationReference" : "_:t55",
+    "conformanceLevel" : "ldpt:MAY",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:RdfSource-TypeRdfSource"
-    }
+    "declaredTestCase" : "ldpt:RdfSource-TypeRdfSource",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/RdfSourceTest.html#testTypeRdfSource()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:BasicContainer-UseStandardVocabularies",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.149Z"
-    },
-    "dcterms:subject" : "SHOULD",
+      "@value" : "2014-07-20T21:33:29.596Z"
+    },
+    "dcterms:subject" : "SHOULD, MANUAL",
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t63",
+    "conformanceLevel" : [ "ldpt:MANUAL", "ldpt:SHOULD" ],
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.BasicContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:RdfSource-UseStandardVocabularies"
-    }
+    "declaredTestCase" : "ldpt:RdfSource-UseStandardVocabularies",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/RdfSourceTest.html#testUseStandardVocabularies()",
+    "ldpt:steps" : {
+      "@list" : [ "Given a URL for a RDF Source, perform a GET using an RDF content type", "Inspect the content to ensure standard terms are used.  For example, if things like ex:label or ex:title are used, instead of DCTERMS or RDFS, then the test should fail." ]
+    },
+    "testMethod" : "ldpt:manual"
   }, {
     "@id" : "ldpt:DirectContainer-4xxErrorHasResponseBody",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.225Z"
+      "@value" : "2014-07-20T21:33:29.669Z"
     },
     "dcterms:subject" : "SHOULD",
     "rdf:type" : {
@@ -4373,29 +2877,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:unreviewed",
+    "specificationReference" : "_:t326",
+    "conformanceLevel" : "ldpt:SHOULD",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:RdfSource-4xxErrorHasResponseBody"
-    }
+    "declaredTestCase" : "ldpt:RdfSource-4xxErrorHasResponseBody",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/RdfSourceTest.html#test4xxErrorHasResponseBody()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:DirectContainer-AcceptPatchHeader",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.232Z"
+      "@value" : "2014-07-20T21:33:29.678Z"
     },
     "dcterms:subject" : "MUST",
     "rdf:type" : {
@@ -4403,29 +2899,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t456",
+    "conformanceLevel" : "ldpt:MUST",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:CommonResource-AcceptPatchHeader"
-    }
+    "declaredTestCase" : "ldpt:CommonResource-AcceptPatchHeader",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/CommonResourceTest.html#testAcceptPatchHeader()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:DirectContainer-AcceptPostResponseHeader",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.204Z"
+      "@value" : "2014-07-20T21:33:29.654Z"
     },
     "dcterms:subject" : "MUST",
     "rdf:type" : {
@@ -4433,29 +2921,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t143",
+    "conformanceLevel" : "ldpt:MUST",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:CommonContainer-AcceptPostResponseHeader"
-    }
+    "declaredTestCase" : "ldpt:CommonContainer-AcceptPostResponseHeader",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/CommonContainerTest.html#testAcceptPostResponseHeader()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:DirectContainer-AcceptTurtle",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.2Z"
+      "@value" : "2014-07-20T21:33:29.65Z"
     },
     "dcterms:subject" : "MUST",
     "rdf:type" : {
@@ -4463,29 +2943,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t24",
+    "conformanceLevel" : "ldpt:MUST",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:CommonContainer-AcceptTurtle"
-    }
+    "declaredTestCase" : "ldpt:CommonContainer-AcceptTurtle",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/CommonContainerTest.html#testAcceptTurtle()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:DirectContainer-ActAsIfInsertedContentRelationTripleExists",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.194Z"
+      "@value" : "2014-07-20T21:33:29.641Z"
     },
     "dcterms:subject" : "MUST",
     "rdf:type" : {
@@ -4493,179 +2965,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:unreviewed",
+    "specificationReference" : "_:t359",
+    "conformanceLevel" : "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"
-    }
+    "declaredTestCase" : "ldpt:DirectContainer-ActAsIfInsertedContentRelationTripleExists",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/DirectContainerTest.html#testActAsIfInsertedContentRelationTripleExists()",
+    "testMethod" : "ldpt:notImplemented"
   }, {
     "@id" : "ldpt:DirectContainer-ConditionFailedStatusCode",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.23Z"
+      "@value" : "2014-07-20T21:33:29.676Z"
     },
     "dcterms:subject" : "MUST",
     "rdf:type" : {
@@ -4673,29 +2987,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t419",
+    "conformanceLevel" : "ldpt:MUST",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:CommonResource-ConditionFailedStatusCode"
-    }
+    "declaredTestCase" : "ldpt:CommonResource-ConditionFailedStatusCode",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/CommonResourceTest.html#testConditionFailedStatusCode()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:DirectContainer-ContainsRdfType",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.214Z"
+      "@value" : "2014-07-20T21:33:29.661Z"
     },
     "dcterms:subject" : "SHOULD",
     "rdf:type" : {
@@ -4703,29 +3009,21 @@
     },
     "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"
-    },
+    "seeAlso" : "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"
-    },
+    "reviewStatus" : "td:approved",
+    "specificationReference" : "_:t407",
+    "conformanceLevel" : "ldpt:SHOULD",
     "ldpt:declaredInClass" : "org.w3.ldp.testsuite.test.DirectContainerTest",
-    "ldpt:declaredTestCase" : {
-      "@id" : "ldpt:RdfSource-ContainsRdfType"
-    }
+    "declaredTestCase" : "ldpt:RdfSource-ContainsRdfType",
+    "documentation" : "http://w3c.github.io/ldp-testsuite/api/java/org/w3/ldp/testsuite/test/RdfSourceTest.html#testContainsRdfType()",
+    "testMethod" : "ldpt:automated"
   }, {
     "@id" : "ldpt:DirectContainer-ContentTypeHeader",
     "dcterms:date" : {
       "@type" : "http://www.w3.org/2001/XMLSchema#dateTime",
-      "@value" : "2014-07-16T15:17:40.2Z"
+      "@value" : "2014-07-20T21:33:29.65Z"
     },
     "dcterms:subject" : "SHOULD",
     "rdf:type" : {
@@ -4733,29 +3031,21 @@
     },
     "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" : {