--- a/tests/reports/ldp-earl-manifest.ttl Mon Jul 07 12:40:42 2014 -0400
+++ b/tests/reports/ldp-earl-manifest.ttl Mon Jul 07 14:20:54 2014 -0400
@@ -14,7 +14,7 @@
rdfs:comment "LDP servers MAY choose to allow the creation of new resources using HTTP PUT." ;
rdfs:label "CommonContainer-PutToCreate" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpr-put-create> ;
- dcterms:date "2014-07-07T15:39:43.525Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.456Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MAY" ;
mf:action "" ;
mf:name "CommonContainer-PutToCreate" ;
@@ -30,7 +30,7 @@
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 "RdfSource-PutReplacesResource" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpr-put-replaceall> ;
- dcterms:date "2014-07-07T15:39:43.507Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.437Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "RdfSource-PutReplacesResource" ;
@@ -46,7 +46,7 @@
rdfs:comment "LDP servers are RECOMMENDED to support HTTP PATCH as the preferred method for updating an LDPC's empty-container triples. " ;
rdfs:label "CommonContainer-PatchMethod" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpc-patch-req> ;
- dcterms:date "2014-07-07T15:39:43.541Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.471Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "SHOULD" ;
mf:action "" ;
mf:name "CommonContainer-PatchMethod" ;
@@ -62,7 +62,7 @@
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 "CommonResource-LdpLinkHeader" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpr-gen-linktypehdr> ;
- dcterms:date "2014-07-07T15:39:43.492Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.422Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "CommonResource-LdpLinkHeader" ;
@@ -82,7 +82,7 @@
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 "RdfSource-PublishConstraintsReadOnlyProp" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpr-gen-pubclireqs> ;
- dcterms:date "2014-07-07T15:39:43.52Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.45Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "RdfSource-PublishConstraintsReadOnlyProp" ;
@@ -98,7 +98,7 @@
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 "CommonContainer-RdfTypeLdpContainer" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpc-typecontainer> ;
- dcterms:date "2014-07-07T15:39:43.541Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.472Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MAY" ;
mf:action "" ;
mf:name "CommonContainer-RdfTypeLdpContainer" ;
@@ -114,7 +114,7 @@
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 "CommonResource-PutBadETag" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpr-put-precond> ;
- dcterms:date "2014-07-07T15:39:43.498Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.428Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "CommonResource-PutBadETag" ;
@@ -130,7 +130,7 @@
rdfs:comment "When a successful HTTP POST request to an LDPC results in the creation of an LDPR, the LDPC MUST update its membership triples to reflect that addition, and the resulting membership triple MUST be consistent with any LDP-defined predicates it exposes." ;
rdfs:label "DirectContainer-PostResourceUpdatesTriples" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpdc-post-createdmbr-member> ;
- dcterms:date "2014-07-07T15:39:43.56Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.488Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "DirectContainer-PostResourceUpdatesTriples" ;
@@ -146,7 +146,7 @@
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 "CommonContainer-RequestedInteractionModelCreateNotAllowed" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpc-post-createrdf> ;
- dcterms:date "2014-07-07T15:39:43.531Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.462Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "CommonContainer-RequestedInteractionModelCreateNotAllowed" ;
@@ -162,7 +162,7 @@
rdfs:comment "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." ;
rdfs:label "NonRDFSource-PostResourceGetBinary" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpr-gen-binary> ;
- dcterms:date "2014-07-07T15:39:43.55Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.48Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MAY, NON-RDF" ;
mf:action "" ;
mf:name "NonRDFSource-PostResourceGetBinary" ;
@@ -178,7 +178,7 @@
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 "CommonContainer-AcceptPostResponseHeader" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpc-post-acceptposthdr> ;
- dcterms:date "2014-07-07T15:39:43.538Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.468Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "CommonContainer-AcceptPostResponseHeader" ;
@@ -194,7 +194,7 @@
rdfs:comment "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." ;
rdfs:label "NonRDFSource-DeleteNonRDFSourceDeletesAssociatedResource" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpc-del-contremovescontres> ;
- dcterms:date "2014-07-07T15:39:43.554Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.482Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST, NON-RDF" ;
mf:action "" ;
mf:name "NonRDFSource-DeleteNonRDFSourceDeletesAssociatedResource" ;
@@ -210,7 +210,7 @@
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 "RdfSource-RelativeUriResolutionPut" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpr-gen-defbaseuri> ;
- dcterms:date "2014-07-07T15:39:43.506Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.436Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "RdfSource-RelativeUriResolutionPut" ;
@@ -226,7 +226,7 @@
rdfs:comment "LDP servers MUST support the HTTP OPTIONS method. " ;
rdfs:label "CommonResource-Options" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpr-options-must> ;
- dcterms:date "2014-07-07T15:39:43.5Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.43Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "CommonResource-Options" ;
@@ -242,7 +242,7 @@
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 "RdfSource-ReUseVocabularies" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldprs-gen-reusevocab> ;
- dcterms:date "2014-07-07T15:39:43.509Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.439Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "SHOULD" ;
mf:action "" ;
mf:name "RdfSource-ReUseVocabularies" ;
@@ -258,7 +258,7 @@
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 "CommonContainer-RequestedInteractionModelHeaders" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpc-post-createrdf> ;
- dcterms:date "2014-07-07T15:39:43.532Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.463Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "CommonContainer-RequestedInteractionModelHeaders" ;
@@ -274,7 +274,7 @@
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 "RdfSource-4xxErrorHasResponseBody" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldprs-put-servermanagedprops> ;
- dcterms:date "2014-07-07T15:39:43.522Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.453Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "SHOULD" ;
mf:action "" ;
mf:name "RdfSource-4xxErrorHasResponseBody" ;
@@ -290,7 +290,7 @@
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 "RdfSource-RestrictClientInference" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldprs-gen-noinferencing> ;
- dcterms:date "2014-07-07T15:39:43.513Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.443Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "RdfSource-RestrictClientInference" ;
@@ -306,7 +306,7 @@
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 "RdfSource-ResponsePropertiesNotPersisted" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldprs-put-failed> ;
- dcterms:date "2014-07-07T15:39:43.524Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.454Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "SHOULD" ;
mf:action "" ;
mf:name "RdfSource-ResponsePropertiesNotPersisted" ;
@@ -322,7 +322,7 @@
rdfs:comment "LDP servers exposing LDPCs MUST advertise their LDP support by exposing a HTTP Link header with a target URI matching the type of container (see below) the server supports, and a link relation type of type (that is, rel='type') in all responses to requests made to the LDPC's HTTP Request-URI." ;
rdfs:label "DirectContainer-HttpLinkHeader" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpc-linktypehdr> ;
- dcterms:date "2014-07-07T15:39:43.557Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.485Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "DirectContainer-HttpLinkHeader" ;
@@ -338,7 +338,7 @@
rdfs:comment "When an LDPR identified by the object of a membership triple which was originally created by the LDP-DC is deleted, the LDPC server MUST also remove the corresponding membership triple." ;
rdfs:label "DirectContainer-DeleteResourceUpdatesTriples" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpdc-del-contremovesmbrtriple> ;
- dcterms:date "2014-07-07T15:39:43.56Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.489Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "DirectContainer-DeleteResourceUpdatesTriples" ;
@@ -354,7 +354,7 @@
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 "RdfSource-ContainsRdfType" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldprs-gen-atleast1rdftype> ;
- dcterms:date "2014-07-07T15:39:43.508Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.438Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "SHOULD" ;
mf:action "" ;
mf:name "RdfSource-ContainsRdfType" ;
@@ -370,7 +370,7 @@
rdfs:comment "LDP servers that allow member creation via POST SHOULD NOT re-use URIs." ;
rdfs:label "CommonContainer-RestrictUriReUseNoSlug" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpc-post-dontreuseuris> ;
- dcterms:date "2014-07-07T15:39:43.537Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.468Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "SHOULD" ;
mf:action "" ;
mf:name "CommonContainer-RestrictUriReUseNoSlug" ;
@@ -386,7 +386,7 @@
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 "CommonContainer-PostNoSlug" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpc-post-serverassignuri> ;
- dcterms:date "2014-07-07T15:39:43.535Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.466Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "SHOULD" ;
mf:action "" ;
mf:name "CommonContainer-PostNoSlug" ;
@@ -402,7 +402,7 @@
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 "RdfSource-PutReadOnlyProperties4xxStatus" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldprs-put-servermanagedprops> ;
- dcterms:date "2014-07-07T15:39:43.522Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.452Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "RdfSource-PutReadOnlyProperties4xxStatus" ;
@@ -418,7 +418,7 @@
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 "CommonContainer-PostResponseStatusAndLocation" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpc-post-created201> ;
- dcterms:date "2014-07-07T15:39:43.529Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.46Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "CommonContainer-PostResponseStatusAndLocation" ;
@@ -434,7 +434,7 @@
rdfs:comment "LDP servers may accept an HTTP POST of non-RDF representations (LDP-NRs) for creation of any kind of resource, for example binary resources." ;
rdfs:label "NonRDFSource-PostResourceAndGetFromContainer" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpc-post-createbins> ;
- dcterms:date "2014-07-07T15:39:43.549Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.479Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MAY, NON-RDF" ;
mf:action "" ;
mf:name "NonRDFSource-PostResourceAndGetFromContainer" ;
@@ -450,7 +450,7 @@
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 "CommonContainer-CreateWithoutConstraints" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpc-post-mincontraints> ;
- dcterms:date "2014-07-07T15:39:43.535Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.466Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "SHOULD" ;
mf:action "" ;
mf:name "CommonContainer-CreateWithoutConstraints" ;
@@ -466,7 +466,7 @@
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 "CommonContainer-ServerHonorsSlug" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpc-post-slug> ;
- dcterms:date "2014-07-07T15:39:43.542Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.473Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MAY" ;
mf:action "" ;
mf:name "CommonContainer-ServerHonorsSlug" ;
@@ -482,7 +482,7 @@
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 "RdfSource-PublishConstraintsUnknownProp" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpr-gen-pubclireqs> ;
- dcterms:date "2014-07-07T15:39:43.521Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.451Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "RdfSource-PublishConstraintsUnknownProp" ;
@@ -498,7 +498,7 @@
rdfs:comment "LDP servers exposing LDPCs MUST advertise their LDP support by exposing a HTTP Link header with a target URI matching the type of container (see below) the server supports, and a link relation type of type (that is, rel='type') in all responses to requests made to the LDPC's HTTP Request-URI." ;
rdfs:label "IndirectContainer-ContainerSupportsHttpLinkHeader" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpc-linktypehdr> ;
- dcterms:date "2014-07-07T15:39:43.561Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.49Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "IndirectContainer-ContainerSupportsHttpLinkHeader" ;
@@ -514,7 +514,7 @@
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 "CommonContainer-PostJsonLd" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpc-post-jsonld> ;
- dcterms:date "2014-07-07T15:39:43.543Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.473Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "SHOULD" ;
mf:action "" ;
mf:name "CommonContainer-PostJsonLd" ;
@@ -530,7 +530,7 @@
rdfs:comment "LDP servers SHOULD respect all of a client's LDP-defined hints, for example which subsets of LDP-defined state the client is interested in processing, to influence the set of triples returned in representations of an LDPC, particularly for large LDPCs. See also [LDP-PAGING]." ;
rdfs:label "DirectContainer-PreferMembershipTriples" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpc-prefer> ;
- dcterms:date "2014-07-07T15:39:43.561Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.489Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "SHOULD" ;
mf:action "" ;
mf:name "DirectContainer-PreferMembershipTriples" ;
@@ -546,7 +546,7 @@
rdfs:comment "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." ;
rdfs:label "NonRDFSource-PostResourceAndCheckLink" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpnr-type> ;
- dcterms:date "2014-07-07T15:39:43.552Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.481Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MAY, NON-RDF" ;
mf:action "" ;
mf:name "NonRDFSource-PostResourceAndCheckLink" ;
@@ -562,7 +562,7 @@
rdfs:comment "LDP servers MUST support the HTTP response headers defined in section 4.2.8 HTTP OPTIONS. " ;
rdfs:label "CommonResource-GetResponseHeaders" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpr-get-options> ;
- dcterms:date "2014-07-07T15:39:43.493Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.423Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "CommonResource-GetResponseHeaders" ;
@@ -578,7 +578,7 @@
rdfs:comment "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" ;
rdfs:label "NonRDFSource-OptionsHasSameLinkHeader" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpc-options-linkmetahdr> ;
- dcterms:date "2014-07-07T15:39:43.554Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.483Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST, NON-RDF" ;
mf:action "" ;
mf:name "NonRDFSource-OptionsHasSameLinkHeader" ;
@@ -594,7 +594,7 @@
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 "CommonResource-AcceptPatchHeader" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpr-patch-acceptpatch> ;
- dcterms:date "2014-07-07T15:39:43.499Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.43Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "CommonResource-AcceptPatchHeader" ;
@@ -610,7 +610,7 @@
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 "CommonResource-PreconditionRequiredStatusCode" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpr-put-precond> ;
- dcterms:date "2014-07-07T15:39:43.497Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.427Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "CommonResource-PreconditionRequiredStatusCode" ;
@@ -626,7 +626,7 @@
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 <http://www.w3.org/TR/ldp#ldpdc-indirectmbr-basic> ;
- dcterms:date "2014-07-07T15:39:43.559Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.487Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "DirectContainer-ActAsIfInsertedContentRelationTripleExists" ;
@@ -642,7 +642,7 @@
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 "CommonResource-OptionsAllowHeader" ;
rdfs:seeAlso <http://www.w3.org/TR/ldpldpr-options-allow> ;
- dcterms:date "2014-07-07T15:39:43.501Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.431Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "CommonResource-OptionsAllowHeader" ;
@@ -658,7 +658,7 @@
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 "RdfSource-PutPropertiesNotPersisted" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldprs-put-failed> ;
- dcterms:date "2014-07-07T15:39:43.523Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.454Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "RdfSource-PutPropertiesNotPersisted" ;
@@ -674,7 +674,7 @@
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 "CommonContainer-ClientPostToCreate" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpc-post-created201> ;
- dcterms:date "2014-07-07T15:39:43.529Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.46Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "SHOULD" ;
mf:action "" ;
mf:name "CommonContainer-ClientPostToCreate" ;
@@ -690,7 +690,7 @@
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 "RdfSource-ClientMayProvideHints" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpr-cli-can-hint> ;
- dcterms:date "2014-07-07T15:39:43.516Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.446Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MAY" ;
mf:action "" ;
mf:name "RdfSource-ClientMayProvideHints" ;
@@ -706,7 +706,7 @@
rdfs:comment "LDPCs whose ldp:insertedContentRelation triple has an object other than ldp:MemberSubject and that create new resources MUST add a triple to the container whose subject is the container's URI, whose predicate is ldp:contains, and whose object is the newly created resource's URI (which will be different from the member-derived URI in this case). This ldp:contains triple can be the only link from the container to the newly created resource in certain cases." ;
rdfs:label "IndirectContainer-PostResource" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpic-post-indirectmbrrel> ;
- dcterms:date "2014-07-07T15:39:43.563Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.492Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "IndirectContainer-PostResource" ;
@@ -722,7 +722,7 @@
rdfs:comment "LDP servers SHOULD offer a application/ld+json representation of the requested LDP-RS [JSON-LD]. " ;
rdfs:label "RdfSource-JsonLdRepresentation" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldprs-get-jsonld> ;
- dcterms:date "2014-07-07T15:39:43.517Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.447Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "SHOULD" ;
mf:action "" ;
mf:name "RdfSource-JsonLdRepresentation" ;
@@ -738,7 +738,7 @@
rdfs:comment "Each LDP Direct Container representation MUST contain exactly one triple whose subject is the LDPC URI, whose predicate is the ldp:membershipResource, and whose object is the LDPC's membership-constant-URI. Commonly the LDPC's URI is the membership-constant-URI, but LDP does not require this." ;
rdfs:label "DirectContainer-MemberResourceTriple" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpdc-containres> ;
- dcterms:date "2014-07-07T15:39:43.558Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.486Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "DirectContainer-MemberResourceTriple" ;
@@ -754,7 +754,7 @@
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 "CommonContainer-RejectPutModifyingContainmentTriples" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpc-put-mbrprops> ;
- dcterms:date "2014-07-07T15:39:43.538Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.469Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "SHOULD" ;
mf:action "" ;
mf:name "CommonContainer-RejectPutModifyingContainmentTriples" ;
@@ -770,7 +770,7 @@
rdfs:comment "LDP servers may accept an HTTP POST of non-RDF representations (LDP-NRs) for creation of any kind of resource, for example binary resources." ;
rdfs:label "NonRDFSource-PostNonRDFSource" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpc-post-createbins> ;
- dcterms:date "2014-07-07T15:39:43.548Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.478Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MAY, NON-RDF" ;
mf:action "" ;
mf:name "NonRDFSource-PostNonRDFSource" ;
@@ -786,7 +786,7 @@
rdfs:comment "LDP server responses MUST use entity tags (either weak or strong ones) as response ETag header values." ;
rdfs:label "CommonResource-ETagHeadersGet" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpr-gen-etags> ;
- dcterms:date "2014-07-07T15:39:43.489Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.419Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "CommonResource-ETagHeadersGet" ;
@@ -802,7 +802,7 @@
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 "CommonContainer-PreferContainmentTriples" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpc-prefer> ;
- dcterms:date "2014-07-07T15:39:43.527Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.458Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "SHOULD" ;
mf:action "" ;
mf:name "CommonContainer-PreferContainmentTriples" ;
@@ -818,7 +818,7 @@
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 "RdfSource-GetResource" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldprs-gen-rdf> ;
- dcterms:date "2014-07-07T15:39:43.507Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.438Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "RdfSource-GetResource" ;
@@ -834,7 +834,7 @@
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 "CommonResource-ConditionFailedStatusCode" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpr-put-precond> ;
- dcterms:date "2014-07-07T15:39:43.495Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.426Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "CommonResource-ConditionFailedStatusCode" ;
@@ -850,7 +850,7 @@
rdfs:comment "Each LDP Indirect Container MUST also be a conforming LDP Direct Container in section 5.4 Direct along the following restrictions." ;
rdfs:label "IndirectContainer-CreateIndirectContainer" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpic-are-ldpcs> ;
- dcterms:date "2014-07-07T15:39:43.562Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.491Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "IndirectContainer-CreateIndirectContainer" ;
@@ -866,7 +866,7 @@
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 "CommonContainer-ContentTypeHeader" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpc-post-contenttype> ;
- dcterms:date "2014-07-07T15:39:43.533Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.464Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "SHOULD" ;
mf:action "" ;
mf:name "CommonContainer-ContentTypeHeader" ;
@@ -882,7 +882,7 @@
rdfs:comment "LDP servers that allow member creation via POST SHOULD NOT re-use URIs." ;
rdfs:label "CommonContainer-RestrictUriReUseSlug" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpc-post-dontreuseuris> ;
- dcterms:date "2014-07-07T15:39:43.536Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.467Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "SHOULD" ;
mf:action "" ;
mf:name "CommonContainer-RestrictUriReUseSlug" ;
@@ -898,7 +898,7 @@
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 "CommonContainer-NullRelativeUri" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpc-post-rdfnullrel> ;
- dcterms:date "2014-07-07T15:39:43.534Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.465Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "CommonContainer-NullRelativeUri" ;
@@ -914,7 +914,7 @@
rdfs:comment "LDP Indirect Containers MUST contain exactly one triple whose subject is the LDPC URI, whose predicate is ldp:insertedContentRelation, and whose object ICR describes how the member-derived-URI in the container's membership triples is chosen." ;
rdfs:label "IndirectContainer-ContainsLdpcUri" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpic-indirectmbr> ;
- dcterms:date "2014-07-07T15:39:43.563Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.491Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "IndirectContainer-ContainsLdpcUri" ;
@@ -930,7 +930,7 @@
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 "RdfSource-AllowMultipleRdfTypes" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldp-cli-multitype> ;
- dcterms:date "2014-07-07T15:39:43.51Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.441Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "RdfSource-AllowMultipleRdfTypes" ;
@@ -946,7 +946,7 @@
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 "RdfSource-ChangeRdfTypeValue" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpr-cli-typeschange> ;
- dcterms:date "2014-07-07T15:39:43.511Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.441Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "RdfSource-ChangeRdfTypeValue" ;
@@ -962,7 +962,7 @@
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 <http://www.w3.org/TR/ldp#ldpbc-are-ldpcs> ;
- dcterms:date "2014-07-07T15:39:43.556Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.484Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "BasicContainer-ContainerTypeIsBasicContainer" ;
@@ -978,7 +978,7 @@
rdfs:comment "LDP server responses MUST use entity tags (either weak or strong ones) as response ETag header values." ;
rdfs:label "CommonResource-ETagHeadersHead" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpr-gen-etags> ;
- dcterms:date "2014-07-07T15:39:43.49Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.421Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "CommonResource-ETagHeadersHead" ;
@@ -994,7 +994,7 @@
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 "CommonContainer-RestrictPutReUseUri" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpc-put-create> ;
- dcterms:date "2014-07-07T15:39:43.539Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.47Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "SHOULD" ;
mf:action "" ;
mf:name "CommonContainer-RestrictPutReUseUri" ;
@@ -1010,7 +1010,7 @@
rdfs:comment "LDP servers MUST at least be HTTP/1.1 conformant servers [HTTP11]." ;
rdfs:label "CommonResource-IsHttp11Server" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpr-gen-http> ;
- dcterms:date "2014-07-07T15:39:43.488Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.418Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "CommonResource-IsHttp11Server" ;
@@ -1026,7 +1026,7 @@
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 "CommonContainer-DeleteRemovesContainmentTriple" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpc-del-contremovesconttriple> ;
- dcterms:date "2014-07-07T15:39:43.54Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.47Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "CommonContainer-DeleteRemovesContainmentTriple" ;
@@ -1042,7 +1042,7 @@
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 "RdfSource-UseStandardVocabularies" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldprs-gen-reusevocabsuchas> ;
- dcterms:date "2014-07-07T15:39:43.51Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.44Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "SHOULD" ;
mf:action "" ;
mf:name "RdfSource-UseStandardVocabularies" ;
@@ -1058,7 +1058,7 @@
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 "CommonContainer-AcceptTurtle" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpc-post-turtle> ;
- dcterms:date "2014-07-07T15:39:43.532Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.463Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "CommonContainer-AcceptTurtle" ;
@@ -1074,7 +1074,7 @@
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 "CommonResource-PutRequiresIfMatch" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpr-put-precond> ;
- dcterms:date "2014-07-07T15:39:43.494Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.424Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "SHOULD" ;
mf:action "" ;
mf:name "CommonResource-PutRequiresIfMatch" ;
@@ -1090,7 +1090,7 @@
rdfs:comment "LDP clients MUST be capable of processing responses formed by an LDP server that ignores hints, including LDP-defined hints." ;
rdfs:label "RdfSource-AllowResponsesFromServer" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpr-cli-hints-ignorable> ;
- dcterms:date "2014-07-07T15:39:43.514Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.445Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "RdfSource-AllowResponsesFromServer" ;
@@ -1106,7 +1106,7 @@
rdfs:comment "Each LDP Direct Container representation must contain exactly one triple whose subject is the LDPC URI, and whose predicate is either ldp:hasMemberRelation or ldp:isMemberOfRelation. The object of the triple is constrained by other sections, such as ldp:hasMemberRelation or ldp:isMemberOfRelation, based on the membership triple pattern used by the container." ;
rdfs:label "DirectContainer-MemberRelationOrIsMemberOfRelationTripleExists" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpdc-containtriples> ;
- dcterms:date "2014-07-07T15:39:43.559Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.487Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "DirectContainer-MemberRelationOrIsMemberOfRelationTripleExists" ;
@@ -1122,7 +1122,7 @@
rdfs:comment "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." ;
rdfs:label "NonRDFSource-PostResourceAndCheckAssociatedResource" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpc-post-createbinlinkmetahdr> ;
- dcterms:date "2014-07-07T15:39:43.553Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.481Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MAY, NON-RDF" ;
mf:action "" ;
mf:name "NonRDFSource-PostResourceAndCheckAssociatedResource" ;
@@ -1138,7 +1138,7 @@
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 <http://www.w3.org/TR/ldp#ldpc-linktypehdr> ;
- dcterms:date "2014-07-07T15:39:43.555Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.484Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "BasicContainer-ContainerSupportsHttpLinkHeader" ;
@@ -1154,7 +1154,7 @@
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 "RdfSource-GetResourceAcceptTurtle" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldprs-get-turtle> ;
- dcterms:date "2014-07-07T15:39:43.515Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.445Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "RdfSource-GetResourceAcceptTurtle" ;
@@ -1170,7 +1170,7 @@
rdfs:comment "LDP servers MUST support the HTTP HEAD method. " ;
rdfs:label "CommonResource-Head" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpr-head-must> ;
- dcterms:date "2014-07-07T15:39:43.499Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.429Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "CommonResource-Head" ;
@@ -1186,7 +1186,7 @@
rdfs:comment "LDPC representations SHOULD NOT use RDF container types rdf:Bag, rdf:Seq or rdf:List." ;
rdfs:label "CommonContainer-NoRdfBagSeqOrList" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpc-nordfcontainertypes> ;
- dcterms:date "2014-07-07T15:39:43.527Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.457Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "SHOULD" ;
mf:action "" ;
mf:name "CommonContainer-NoRdfBagSeqOrList" ;
@@ -1202,7 +1202,7 @@
rdfs:comment "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." ;
rdfs:label "NonRDFSource-PostResourceGetMetadataAndBinary" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpnr-are-ldpr> ;
- dcterms:date "2014-07-07T15:39:43.551Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.48Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MAY, NON-RDF" ;
mf:action "" ;
mf:name "NonRDFSource-PostResourceGetMetadataAndBinary" ;
@@ -1218,7 +1218,7 @@
rdfs:comment "LDP servers MUST at least be HTTP/1.1 conformant servers [HTTP11]." ;
rdfs:label "CommonResource-IsHttp11Manual" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpr-gen-http> ;
- dcterms:date "2014-07-07T15:39:43.488Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.418Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "CommonResource-IsHttp11Manual" ;
@@ -1234,7 +1234,7 @@
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 "RdfSource-ServerOpen" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpr-cli-openpreds> ;
- dcterms:date "2014-07-07T15:39:43.512Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.442Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "SHOULD" ;
mf:action "" ;
mf:name "RdfSource-ServerOpen" ;
@@ -1250,7 +1250,7 @@
rdfs:comment "LDP servers MUST support the HTTP GET Method for LDPRs" ;
rdfs:label "CommonResource-GetResource" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpr-get-must> ;
- dcterms:date "2014-07-07T15:39:43.38Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.283Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "CommonResource-GetResource" ;
@@ -1266,7 +1266,7 @@
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 "RdfSource-GetResourcePreservesTriples" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpr-cli-preservetriples> ;
- dcterms:date "2014-07-07T15:39:43.514Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.444Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "RdfSource-GetResourcePreservesTriples" ;
@@ -1282,7 +1282,7 @@
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 "CommonContainer-RelativeUriResolutionPost" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpr-gen-defbaseuri> ;
- dcterms:date "2014-07-07T15:39:43.526Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.457Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "CommonContainer-RelativeUriResolutionPost" ;
@@ -1298,7 +1298,7 @@
rdfs:comment "LDP Direct Containers SHOULD use the ldp:member predicate as an LDPC's membership predicate if there is no obvious predicate from an application vocabulary to use." ;
rdfs:label "DirectContainer-UseMemberPredicate" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpdc-mbrpred> ;
- dcterms:date "2014-07-07T15:39:43.557Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.486Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "SHOULD, ldpMember" ;
mf:action "" ;
mf:name "DirectContainer-UseMemberPredicate" ;
@@ -1314,7 +1314,7 @@
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 "CommonContainer-PostContainer" ;
rdfs:seeAlso <http://www.w3.org/TR/ldp#ldpc-post-createdmbr-contains> ;
- dcterms:date "2014-07-07T15:39:43.53Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
+ dcterms:date "2014-07-07T18:19:32.461Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
dcterms:subject "MUST" ;
mf:action "" ;
mf:name "CommonContainer-PostContainer" ;