LDP Test Suite Summary

Overall Coverage Bar Charts

Passed TestsFailed TestsSkipped Tests</svg>
NonRDFSourceTestMemberResourceTestBasicContainerTest</svg>

Test Suite NameRevisionReport DateSkipped TestsMUST RequirementsSHOULD RequirementsMAY Requirements
LDP Test Suite199d3cdFri Dec 06 15:11:35 UTC 2019(30/112) of the total tests.53/76 Passed
1/76 Failed
22/76 Skipped
12/25 Passed
5/25 Failed
8/25 Skipped
8/11 Passed
3/11 Failed
0/11 Skipped

Included Groups for LDP Test Suite

Excluded Groups for LDP Test Suite

No groups of this type found in the test suite

Methods called

Go To Skipped Tests
Go To Passed Tests
Go To Indirect Tests

Failed Test CasesGroupsDescription of Test Method
BasicContainer-RdfTypeLdpContainer[MAY]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.
BasicContainer-PostContainer[MUST]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.
BasicContainer-RestrictUriReUseSlug[SHOULD]LDP servers that allow member creation via POST SHOULD NOT re-use URIs.
BasicContainer-TypeRdfSource[MAY]The representation of a LDP-RS MAY have an rdf:type of ldp:RDFSource for Linked Data Platform RDF Source.
NonRDFSource-PostResourceAndGetFromContainer[MAY]LDP servers may accept an HTTP POST of non-RDF representations (LDP-NRs) for creation of any kind of resource, for example binary resources.
BasicContainer-RejectPutModifyingContainmentTriples[SHOULD]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.
BasicContainer-RestrictPutReUseUri[SHOULD]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].
BasicContainer-PreferContainmentTriples[SHOULD]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].
BasicContainer-ContainsRdfType[SHOULD]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.

Back to Top


Skipped Test CasesGroupsDescription of Test Method
MemberResource-ReUseVocabularies[MANUAL, SHOULD]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.
BasicContainer-RelativeUriResolutionPut[MUST]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.
BasicContainer-PutReadOnlyProperties4xxStatus[MUST]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)
MemberResource-PutPropertiesNotPersisted[MUST]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].
BasicContainer-PublishConstraintsUnknownProp[MUST]LDP servers MUST publish any constraints on LDP clients’ ability to create or update LDPRs, by adding a Link header with rel='http://www.w3.org/ns/ldp#constrainedBy' [RFC5988] to all responses to requests which fail due to violation of those constraints.
BasicContainer-RequestedInteractionModelHeaders[MUST]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.
BasicContainer-UseStandardVocabularies[MANUAL, SHOULD]LDP-RSs predicates SHOULD use standard vocabularies such as Dublin Core [DC-TERMS], RDF [rdf11-concepts] and RDF Schema [rdf-schema], whenever possible.
MemberResource-PutReadOnlyProperties4xxStatus[MUST]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)
BasicContainer-PutReplacesResource[MUST]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.
BasicContainer-ResponsePropertiesNotPersisted[SHOULD]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.
BasicContainer-PutSimpleUpdate[MUST]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.
BasicContainer-PutPropertiesNotPersisted[MUST]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].
MemberResource-PublishConstraintsReadOnlyProp[MUST]LDP servers MUST publish any constraints on LDP clients’ ability to create or update LDPRs, by adding a Link header with rel='http://www.w3.org/ns/ldp#constrainedBy' [RFC5988] to all responses to requests which fail due to violation of those constraints.
MemberResource-PublishConstraintsUnknownProp[MUST]LDP servers MUST publish any constraints on LDP clients’ ability to create or update LDPRs, by adding a Link header with rel='http://www.w3.org/ns/ldp#constrainedBy' [RFC5988] to all responses to requests which fail due to violation of those constraints.
BasicContainer-PublishConstraintsReadOnlyProp[MUST]LDP servers MUST publish any constraints on LDP clients’ ability to create or update LDPRs, by adding a Link header with rel='http://www.w3.org/ns/ldp#constrainedBy' [RFC5988] to all responses to requests which fail due to violation of those constraints.
BasicContainer-4xxErrorHasResponseBody[SHOULD]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.
MemberResource-UseStandardVocabularies[MANUAL, SHOULD]LDP-RSs predicates SHOULD use standard vocabularies such as Dublin Core [DC-TERMS], RDF [rdf11-concepts] and RDF Schema [rdf-schema], whenever possible.
MemberResource-4xxErrorHasResponseBody[SHOULD]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.
MemberResource-ResponsePropertiesNotPersisted[SHOULD]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.
BasicContainer-RestrictClientInference[MANUAL, MUST]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.
NonRDFSource-IsHttp11Manual[MANUAL, MUST]LDP servers MUST at least be HTTP/1.1 conformant servers [HTTP11].
BasicContainer-ReUseVocabularies[MANUAL, SHOULD]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.
BasicContainer-RequestedInteractionModelCreateNotAllowed[MUST]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.
MemberResource-RestrictClientInference[MANUAL, MUST]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.
MemberResource-IsHttp11Manual[MANUAL, MUST]LDP servers MUST at least be HTTP/1.1 conformant servers [HTTP11].
BasicContainer-IsHttp11Manual[MANUAL, MUST]LDP servers MUST at least be HTTP/1.1 conformant servers [HTTP11].

Back to Top


Passed Test CasesGroupsDescription of Test Method
NonRDFSource-PreconditionRequiredStatusCode[MUST]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].
NonRDFSource-PostResourceGetBinary[MAY]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.
BasicContainer-PutRequiresIfMatch[SHOULD]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.
MemberResource-PutReplacesResource[MUST]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.
BasicContainer-RelativeUriResolutionPost[MUST]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.
NonRDFSource-AcceptPatchHeader[MUST]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.
NonRDFSource-ETagHeadersGet[MUST]LDP server responses MUST use entity tags (either weak or strong ones) as response ETag header values.
BasicContainer-PostJsonLd[MUST]LDP servers SHOULD accept a request entity body with a request header of Content-Type with value of application/ld+json [JSON-LD].
BasicContainer-AcceptPostResponseHeader[MUST]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.
MemberResource-OptionsAllowHeader[MUST]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.
BasicContainer-AcceptPatchHeader[MUST]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.
BasicContainer-ContentTypeHeader[SHOULD]LDP servers SHOULD use the Content-Type request header to determine the representation format when the request has an entity body.
NonRDFSource-ConditionFailedStatusCode[MUST]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].
NonRDFSource-GetResource[MUST]LDP servers MUST support the HTTP GET Method for LDPRs
BasicContainer-CreateWithoutConstraints[SHOULD]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.
MemberResource-GetResource[MUST]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.
BasicContainer-DeleteRemovesContainmentTriple[MUST]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.
MemberResource-PreconditionRequiredStatusCode[MUST]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].
MemberResource-GetResourceAcceptTurtle[MUST]LDP servers must respond with a Turtle representation of the requested LDP-RS when the request includes an Accept header specifying text/turtle, unless HTTP content negotiation requires a different outcome [turtle].
NonRDFSource-PostResourceGetMetadataAndBinary[MAY]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.
BasicContainer-PutToCreate[MAY]LDP servers MAY choose to allow the creation of new resources using HTTP PUT.
BasicContainer-NullRelativeUriPost[MUST]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.
BasicContainer-RestrictUriReUseNoSlug[SHOULD]LDP servers that allow member creation via POST SHOULD NOT re-use URIs.
NonRDFSource-Head[MUST]LDP servers MUST support the HTTP HEAD method.
MemberResource-PutBadETag[MUST]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].
MemberResource-PutSimpleUpdate[MUST]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.
NonRDFSource-OptionsAllowHeader[MUST]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.
BasicContainer-PostNoSlug[SHOULD]LDP servers SHOULD assign the URI for the resource to be created using server application specific rules in the absence of a client hint.
MemberResource-Options[MUST]LDP servers MUST support the HTTP OPTIONS method.
BasicContainer-PatchMethod[SHOULD]LDP servers are RECOMMENDED to support HTTP PATCH as the preferred method for updating an LDPC's empty-container triples.
MemberResource-ETagHeadersHead[MUST]LDP server responses MUST use entity tags (either weak or strong ones) as response ETag header values.
NonRDFSource-ETagHeadersHead[MUST]LDP server responses MUST use entity tags (either weak or strong ones) as response ETag header values.
BasicContainer-PostResponseStatusAndLocation[MUST]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.
MemberResource-LdpLinkHeader[MUST]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.
BasicContainer-ConditionFailedStatusCode[MUST]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].
BasicContainer-GetResponseHeaders[MUST]LDP servers MUST support the HTTP response headers defined in section 4.2.8 HTTP OPTIONS.
BasicContainer-ETagHeadersGet[MUST]LDP server responses MUST use entity tags (either weak or strong ones) as response ETag header values.
NonRDFSource-PostResourceAndCheckLink[MAY]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.
NonRDFSource-OptionsHasSameLinkHeader[MUST]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
BasicContainer-NoRdfBagSeqOrList[SHOULD]LDPC representations SHOULD NOT use RDF container types rdf:Bag, rdf:Seq or rdf:List.
MemberResource-GetResponseHeaders[MUST]LDP servers MUST support the HTTP response headers defined in section 4.2.8 HTTP OPTIONS.
BasicContainer-GetResourceAsTurtleNoAccept[SHOULD]LDP servers should respond with a text/turtle representation of the requested LDP-RS whenever the Accept request header is absent [turtle].
BasicContainer-ContainerSupportsHttpLinkHeader[MUST]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.
NonRDFSource-Options[MUST]LDP servers MUST support the HTTP OPTIONS method.
BasicContainer-ServerHonorsSlug[MAY]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.
NonRDFSource-PutRequiresIfMatch[SHOULD]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.
BasicContainer-OptionsAllowHeader[MUST]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.
MemberResource-PutRequiresIfMatch[SHOULD]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.
BasicContainer-LdpLinkHeader[MUST]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.
NonRDFSource-DeleteNonRDFSourceDeletesAssociatedResource[MUST]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.
BasicContainer-Head[MUST]LDP servers MUST support the HTTP HEAD method.
BasicContainer-GetResource[MUST]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.
MemberResource-Head[MUST]LDP servers MUST support the HTTP HEAD method.
MemberResource-JsonLdRepresentation[MUST] LDP servers must respond with a application/ld+json representation of the requested LDP-RS when the request includes an Accept header, unless content negotiation or Turtle support requires a different outcome [JSON-LD].
BasicContainer-PreconditionRequiredStatusCode[MUST]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].
MemberResource-ETagHeadersGet[MUST]LDP server responses MUST use entity tags (either weak or strong ones) as response ETag header values.
MemberResource-ConditionFailedStatusCode[MUST]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].
BasicContainer-Options[MUST]LDP servers MUST support the HTTP OPTIONS method.
NonRDFSource-LdpLinkHeader[MUST]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.
MemberResource-AcceptPatchHeader[MUST]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.
MemberResource-ContainsRdfType[SHOULD]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.
NonRDFSource-PostNonRDFSource[MAY]LDP servers may accept an HTTP POST of non-RDF representations (LDP-NRs) for creation of any kind of resource, for example binary resources.
BasicContainer-PutBadETag[MUST]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].
BasicContainer-GetResourceAcceptTurtle[MUST]LDP servers must respond with a Turtle representation of the requested LDP-RS when the request includes an Accept header specifying text/turtle, unless HTTP content negotiation requires a different outcome [turtle].
NonRDFSource-PutBadETag[MUST]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].
BasicContainer-ETagHeadersHead[MUST]LDP server responses MUST use entity tags (either weak or strong ones) as response ETag header values.
MemberResource-GetResourceAsTurtleNoAccept[SHOULD]LDP servers should respond with a text/turtle representation of the requested LDP-RS whenever the Accept request header is absent [turtle].
MemberResource-TypeRdfSource[MAY]The representation of a LDP-RS MAY have an rdf:type of ldp:RDFSource for Linked Data Platform RDF Source.
NonRDFSource-GetResponseHeaders[MUST]LDP servers MUST support the HTTP response headers defined in section 4.2.8 HTTP OPTIONS.
BasicContainer-JsonLdRepresentation[MUST] LDP servers must respond with a application/ld+json representation of the requested LDP-RS when the request includes an Accept header, unless content negotiation or Turtle support requires a different outcome [JSON-LD].
MemberResource-RelativeUriResolutionPut[MUST]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.
BasicContainer-AcceptTurtle[MUST]LDP servers MUST accept a request entity body with a request header of Content-Type with value of text/turtle [turtle].
NonRDFSource-PostResourceAndCheckAssociatedResource[MAY]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.

Back to Top

Indirectly Tested Test CasesOverall Test ResultDescription of Test Method
BasicContainer-ConformsContainerRdfResourcePassedEach Linked Data Platform Container MUST also be a conforming Linked Data Platform RDF Source.
BasicContainer-ConformsRdfSourceLdpResourcePassedEach LDP RDF Source MUST also be a conforming LDP Resource as defined in section 4.2 Resource, along with the restrictions in this section.
BasicContainer-ConformsBcLdpContainerFailedEach LDP Basic Container MUST also be a conforming LDP Container in section 5.2 Container along with the following restrictions in this section.
MemberResource-ConformsRdfSourceLdpResourcePassedEach LDP RDF Source MUST also be a conforming LDP Resource as defined in section 4.2 Resource, along with the restrictions in this section.

Back to Top

Test Method Details

BasicContainer-RdfTypeLdpContainer

[FAILED TEST]
java.lang.AssertionError: LDPC does not have an rdf:type of ldp:Container expected [true] but found [false] at org.w3.ldp.testsuite.test.CommonContainerTest.testRdfTypeLdpContainer(CommonContainerTest.java:793) at org.w3.ldp.testsuite.LdpTestSuite.run(LdpTestSuite.java:378) at org.w3.ldp.testsuite.LdpTestSuite.executeTestSuite(LdpTestSuite.java:414) at org.w3.ldp.testsuite.LdpTestSuite.executeTestSuite(LdpTestSuite.java:406) at org.w3.ldp.testsuite.RunLdpTestSuite.main(RunLdpTestSuite.java:26) ... Removed 25 stack frames

Reference URI: http://www.w3.org/TR/ldp#ldpc-typecontainer

Description: 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.

Requirement Level: MAY

Back to Top

BasicContainer-PostContainer

[FAILED TEST]
java.lang.AssertionError: Container <http://127.0.0.1/basic> does not have a containment triple for newly created resource <http://127.0.0.1/basic/905eab50-5b10-44eb-aea8-591c8d80d559>. expected [true] but found [false] at org.w3.ldp.testsuite.test.CommonContainerTest.testPostContainer(CommonContainerTest.java:284) at org.w3.ldp.testsuite.LdpTestSuite.run(LdpTestSuite.java:378) at org.w3.ldp.testsuite.LdpTestSuite.executeTestSuite(LdpTestSuite.java:414) at org.w3.ldp.testsuite.LdpTestSuite.executeTestSuite(LdpTestSuite.java:406) at org.w3.ldp.testsuite.RunLdpTestSuite.main(RunLdpTestSuite.java:26) ... Removed 25 stack frames

Reference URI: http://www.w3.org/TR/ldp#ldpc-post-createdmbr-contains

Description: 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.

Requirement Level: MUST

Back to Top

BasicContainer-RestrictUriReUseSlug

[FAILED TEST]
java.lang.AssertionError: Server reused URIs for POSTed resources. at org.w3.ldp.testsuite.test.CommonContainerTest.testRestrictUriReUse(CommonContainerTest.java:923) at org.w3.ldp.testsuite.test.CommonContainerTest.testRestrictUriReUseSlug(CommonContainerTest.java:594) at org.w3.ldp.testsuite.LdpTestSuite.run(LdpTestSuite.java:378) at org.w3.ldp.testsuite.LdpTestSuite.executeTestSuite(LdpTestSuite.java:414) at org.w3.ldp.testsuite.LdpTestSuite.executeTestSuite(LdpTestSuite.java:406) at org.w3.ldp.testsuite.RunLdpTestSuite.main(RunLdpTestSuite.java:26) ... Removed 24 stack frames

NOTE: Covers only part of the specification requirement. testRestrictUriReUseNoSlug covers the rest.

Reference URI: http://www.w3.org/TR/ldp#ldpc-post-dontreuseuris

Description: LDP servers that allow member creation via POST SHOULD NOT re-use URIs.

Requirement Level: SHOULD

Back to Top

BasicContainer-TypeRdfSource

[FAILED TEST]
java.lang.AssertionError: LDP-RS representation does not have rdf:type ldp:RDFSource expected [true] but found [false] at org.w3.ldp.testsuite.test.RdfSourceTest.testTypeRdfSource(RdfSourceTest.java:208) at org.w3.ldp.testsuite.LdpTestSuite.run(LdpTestSuite.java:378) at org.w3.ldp.testsuite.LdpTestSuite.executeTestSuite(LdpTestSuite.java:414) at org.w3.ldp.testsuite.LdpTestSuite.executeTestSuite(LdpTestSuite.java:406) at org.w3.ldp.testsuite.RunLdpTestSuite.main(RunLdpTestSuite.java:26) ... Removed 25 stack frames

Reference URI: http://www.w3.org/TR/ldp#ldprs-rdftype

Description: The representation of a LDP-RS MAY have an rdf:type of ldp:RDFSource for Linked Data Platform RDF Source.

Requirement Level: MAY

Back to Top

NonRDFSource-PostResourceAndGetFromContainer

[FAILED TEST]
java.lang.AssertionError: expected [true] but found [false] at org.w3.ldp.testsuite.test.NonRDFSourceTest.testPostResourceAndGetFromContainer(NonRDFSourceTest.java:158) at org.w3.ldp.testsuite.LdpTestSuite.run(LdpTestSuite.java:378) at org.w3.ldp.testsuite.LdpTestSuite.executeTestSuite(LdpTestSuite.java:414) at org.w3.ldp.testsuite.LdpTestSuite.executeTestSuite(LdpTestSuite.java:406) at org.w3.ldp.testsuite.RunLdpTestSuite.main(RunLdpTestSuite.java:26) ... Removed 26 stack frames

NOTE: Covers only part of the specification requirement. testPostNonRDFSource covers the rest.

Reference URI: http://www.w3.org/TR/ldp#ldpc-post-createbins

Description: LDP servers may accept an HTTP POST of non-RDF representations (LDP-NRs) for creation of any kind of resource, for example binary resources.

Requirement Level: MAY

Back to Top

BasicContainer-RejectPutModifyingContainmentTriples

[FAILED TEST]
java.lang.AssertionError: 1 expectation failed. Expected status code not between 200 and 209 doesn't match actual status code <204>. at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrap.callConstructor(ConstructorSite.java:84) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallConstructor(CallSiteArray.java:60) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:235) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:247) at com.jayway.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure.validate(ResponseSpecificationImpl.groovy:598) at com.jayway.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure$validate$1.call(Unknown Source) at com.jayway.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1597) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1210) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1019) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:810) at com.jayway.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy) at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:48) at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:58) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:182) at com.jayway.restassured.internal.RequestSpecificationImpl.put(RequestSpecificationImpl.groovy:168) at com.jayway.restassured.internal.RequestSpecificationImpl.put(RequestSpecificationImpl.groovy) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1210) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1019) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:810) at com.jayway.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy) at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:133) at com.jayway.restassured.internal.ResponseSpecificationImpl.put(ResponseSpecificationImpl.groovy:297) at com.jayway.restassured.internal.ResponseSpecificationImpl.put(ResponseSpecificationImpl.groovy) at org.w3.ldp.testsuite.test.CommonContainerTest.testRejectPutModifyingContainmentTriples(CommonContainerTest.java:662) at org.w3.ldp.testsuite.LdpTestSuite.run(LdpTestSuite.java:378) at org.w3.ldp.testsuite.LdpTestSuite.executeTestSuite(LdpTestSuite.java:414) at org.w3.ldp.testsuite.LdpTestSuite.executeTestSuite(LdpTestSuite.java:406) at org.w3.ldp.testsuite.RunLdpTestSuite.main(RunLdpTestSuite.java:26) ... Removed 37 stack frames

Reference URI: http://www.w3.org/TR/ldp#ldpc-put-mbrprops

Description: 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.

Requirement Level: SHOULD

Back to Top

BasicContainer-RestrictPutReUseUri

[FAILED TEST]
java.lang.AssertionError: 1 expectation failed. Expected status code not between 200 and 209 doesn't match actual status code <201>. at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrap.callConstructor(ConstructorSite.java:84) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:247) at com.jayway.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure.validate(ResponseSpecificationImpl.groovy:598) at com.jayway.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure$validate$1.call(Unknown Source) at com.jayway.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1597) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1210) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1019) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:810) at com.jayway.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy) at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:48) at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:58) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:182) at com.jayway.restassured.internal.RequestSpecificationImpl.put(RequestSpecificationImpl.groovy:168) at com.jayway.restassured.internal.RequestSpecificationImpl.put(RequestSpecificationImpl.groovy) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1210) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1019) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:810) at com.jayway.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy) at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:133) at com.jayway.restassured.internal.ResponseSpecificationImpl.put(ResponseSpecificationImpl.groovy:297) at com.jayway.restassured.internal.ResponseSpecificationImpl.put(ResponseSpecificationImpl.groovy) at org.w3.ldp.testsuite.test.CommonContainerTest.testRestrictPutReUseUri(CommonContainerTest.java:694) at org.w3.ldp.testsuite.LdpTestSuite.run(LdpTestSuite.java:378) at org.w3.ldp.testsuite.LdpTestSuite.executeTestSuite(LdpTestSuite.java:414) at org.w3.ldp.testsuite.LdpTestSuite.executeTestSuite(LdpTestSuite.java:406) at org.w3.ldp.testsuite.RunLdpTestSuite.main(RunLdpTestSuite.java:26) ... Removed 37 stack frames

Reference URI: http://www.w3.org/TR/ldp#ldpc-put-create

Description: 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].

Requirement Level: SHOULD

Back to Top

BasicContainer-PreferContainmentTriples

[FAILED TEST]
java.lang.AssertionError: Container does not have containment triples expected [true] but found [false] at org.w3.ldp.testsuite.test.CommonContainerTest.testPreferContainmentTriples(CommonContainerTest.java:184) at org.w3.ldp.testsuite.LdpTestSuite.run(LdpTestSuite.java:378) at org.w3.ldp.testsuite.LdpTestSuite.executeTestSuite(LdpTestSuite.java:414) at org.w3.ldp.testsuite.LdpTestSuite.executeTestSuite(LdpTestSuite.java:406) at org.w3.ldp.testsuite.RunLdpTestSuite.main(RunLdpTestSuite.java:26) ... Removed 25 stack frames

Reference URI: http://www.w3.org/TR/ldp#ldpc-prefer

Description: 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].

Requirement Level: SHOULD

Back to Top

BasicContainer-ContainsRdfType

[FAILED TEST]
java.lang.AssertionError: LDP-RS representation has no explicit rdf:type expected [true] but found [false] at org.w3.ldp.testsuite.test.RdfSourceTest.testContainsRdfType(RdfSourceTest.java:194) at org.w3.ldp.testsuite.LdpTestSuite.run(LdpTestSuite.java:378) at org.w3.ldp.testsuite.LdpTestSuite.executeTestSuite(LdpTestSuite.java:414) at org.w3.ldp.testsuite.LdpTestSuite.executeTestSuite(LdpTestSuite.java:406) at org.w3.ldp.testsuite.RunLdpTestSuite.main(RunLdpTestSuite.java:26) ... Removed 25 stack frames

Reference URI: http://www.w3.org/TR/ldp#ldprs-gen-atleast1rdftype

Description: 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.

Requirement Level: SHOULD

Back to Top

MemberResource-ReUseVocabularies

[SKIPPED TEST]
This requirement or recommendation must be tested manually. It is difficult or impossible to write automated tests for and is not part of the testsuite.

How to Run testReUseVocabularies

Reference URI: http://www.w3.org/TR/ldp#ldprs-gen-reusevocab

Description: 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.

Requirement Level: MANUAL SHOULD

Back to Top

BasicContainer-RelativeUriResolutionPut

[SKIPPED TEST]
Skipping test because there are restrictions on PUT content for this resource. The requirement needs to be tested manually.

Parameters:

Reference URI: http://www.w3.org/TR/ldp#ldpr-gen-defbaseuri

Description: 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.

Requirement Level: MUST

Back to Top

BasicContainer-PutReadOnlyProperties4xxStatus

[SKIPPED TEST]
Skipping test because we have no read-only properties to PUT. Server-managed properties are specified using the "read-only-prop" command-line parameter.

Parameters:

NOTE: Covers only part of the specification requirement. test4xxErrorHasResponseBody covers the rest.

Reference URI: http://www.w3.org/TR/ldp#ldprs-put-servermanagedprops

Description: 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)

Requirement Level: MUST

Back to Top

MemberResource-PutPropertiesNotPersisted

[SKIPPED TEST]
Skipping test because PUT request was successful.

NOTE: Covers only part of the specification requirement. testResponsePropertiesNotPersisted covers the rest.

Reference URI: http://www.w3.org/TR/ldp#ldprs-put-failed

Description: 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].

Requirement Level: MUST

Back to Top

BasicContainer-PublishConstraintsUnknownProp

[SKIPPED TEST]
Skipping test because PUT request was successful.

NOTE: Covers only part of the specification requirement. testPublishConstraintsReadOnlyProp covers the rest.

Reference URI: http://www.w3.org/TR/ldp#ldpr-gen-pubclireqs

Description: LDP servers MUST publish any constraints on LDP clients’ ability to create or update LDPRs, by adding a Link header with rel='http://www.w3.org/ns/ldp#constrainedBy' [RFC5988] to all responses to requests which fail due to violation of those constraints.

Requirement Level: MUST

Back to Top

BasicContainer-RequestedInteractionModelHeaders

[SKIPPED TEST]
containerAsResource is null

Parameters:

NOTE: Covers only part of the specification requirement. testRequestedInteractionModelCreateNotAllowed covers the rest.

Reference URI: http://www.w3.org/TR/ldp#ldpc-post-createrdf

Description: 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.

Requirement Level: MUST

Back to Top

BasicContainer-UseStandardVocabularies

[SKIPPED TEST]
This requirement or recommendation must be tested manually. It is difficult or impossible to write automated tests for and is not part of the testsuite.

How to Run testUseStandardVocabularies

Reference URI: http://www.w3.org/TR/ldp#ldprs-gen-reusevocabsuchas

Description: LDP-RSs predicates SHOULD use standard vocabularies such as Dublin Core [DC-TERMS], RDF [rdf11-concepts] and RDF Schema [rdf-schema], whenever possible.

Requirement Level: MANUAL SHOULD

Back to Top

MemberResource-PutReadOnlyProperties4xxStatus

[SKIPPED TEST]
Skipping test because we have no read-only properties to PUT. Server-managed properties are specified using the "read-only-prop" command-line parameter.

Parameters:

NOTE: Covers only part of the specification requirement. test4xxErrorHasResponseBody covers the rest.

Reference URI: http://www.w3.org/TR/ldp#ldprs-put-servermanagedprops

Description: 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)

Requirement Level: MUST

Back to Top

BasicContainer-PutReplacesResource

[SKIPPED TEST]
Skipping test because there are restrictions on PUT content for this resource. The requirement needs to be tested manually.

Reference URI: http://www.w3.org/TR/ldp#ldpr-put-replaceall

Description: 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.

Requirement Level: MUST

Back to Top

BasicContainer-ResponsePropertiesNotPersisted

[SKIPPED TEST]
Skipping test because PUT request was successful.

NOTE: Covers only part of the specification requirement. testPutPropertiesNotPersisted covers the rest.

Reference URI: http://www.w3.org/TR/ldp#ldprs-put-failed

Description: 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.

Requirement Level: SHOULD

Back to Top

BasicContainer-PutSimpleUpdate

[SKIPPED TEST]
Skipping test because there are restrictions on PUT content for this resource. The requirement needs to be tested manually.

Reference URI: http://www.w3.org/TR/ldp#ldpr-put-simpleupdate

Description: 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.

Requirement Level: MUST

Back to Top

BasicContainer-PutPropertiesNotPersisted

[SKIPPED TEST]
Skipping test because PUT request was successful.

NOTE: Covers only part of the specification requirement. testResponsePropertiesNotPersisted covers the rest.

Reference URI: http://www.w3.org/TR/ldp#ldprs-put-failed

Description: 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].

Requirement Level: MUST

Back to Top

MemberResource-PublishConstraintsReadOnlyProp

[SKIPPED TEST]
Skipping test because we have no read-only properties to PUT. Server-managed properties are specified using the "read-only-prop" command-line parameter.

Parameters:

NOTE: Covers only part of the specification requirement. testPublishConstraintsUnknownProp covers the rest.

Reference URI: http://www.w3.org/TR/ldp#ldpr-gen-pubclireqs

Description: LDP servers MUST publish any constraints on LDP clients’ ability to create or update LDPRs, by adding a Link header with rel='http://www.w3.org/ns/ldp#constrainedBy' [RFC5988] to all responses to requests which fail due to violation of those constraints.

Requirement Level: MUST

Back to Top

MemberResource-PublishConstraintsUnknownProp

[SKIPPED TEST]
Skipping test because PUT request was successful.

NOTE: Covers only part of the specification requirement. testPublishConstraintsReadOnlyProp covers the rest.

Reference URI: http://www.w3.org/TR/ldp#ldpr-gen-pubclireqs

Description: LDP servers MUST publish any constraints on LDP clients’ ability to create or update LDPRs, by adding a Link header with rel='http://www.w3.org/ns/ldp#constrainedBy' [RFC5988] to all responses to requests which fail due to violation of those constraints.

Requirement Level: MUST

Back to Top

BasicContainer-PublishConstraintsReadOnlyProp

[SKIPPED TEST]
Skipping test because we have no read-only properties to PUT. Server-managed properties are specified using the "read-only-prop" command-line parameter.

Parameters:

NOTE: Covers only part of the specification requirement. testPublishConstraintsUnknownProp covers the rest.

Reference URI: http://www.w3.org/TR/ldp#ldpr-gen-pubclireqs

Description: LDP servers MUST publish any constraints on LDP clients’ ability to create or update LDPRs, by adding a Link header with rel='http://www.w3.org/ns/ldp#constrainedBy' [RFC5988] to all responses to requests which fail due to violation of those constraints.

Requirement Level: MUST

Back to Top

BasicContainer-ConformsContainerRdfResource

[SKIPPED TEST]
Covered indirectly by the MUST tests defined in RdfSourceTest class

Test Case is covered Indirectly by the following:

Reference URI: http://www.w3.org/TR/ldp#ldpc-isldpr

Description: Each Linked Data Platform Container MUST also be a conforming Linked Data Platform RDF Source.

Requirement Level: MUST

Back to Top

BasicContainer-4xxErrorHasResponseBody

[SKIPPED TEST]
Skipping test because we have no read-only properties to PUT. Server-managed properties are specified using the "read-only-prop" command-line parameter.

Parameters:

NOTE: Covers only part of the specification requirement. testPutReadOnlyProperties4xxStatus covers the rest.

Reference URI: http://www.w3.org/TR/ldp#ldprs-put-servermanagedprops

Description: 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.

Requirement Level: SHOULD

Back to Top

MemberResource-UseStandardVocabularies

[SKIPPED TEST]
This requirement or recommendation must be tested manually. It is difficult or impossible to write automated tests for and is not part of the testsuite.

How to Run testUseStandardVocabularies

Reference URI: http://www.w3.org/TR/ldp#ldprs-gen-reusevocabsuchas

Description: LDP-RSs predicates SHOULD use standard vocabularies such as Dublin Core [DC-TERMS], RDF [rdf11-concepts] and RDF Schema [rdf-schema], whenever possible.

Requirement Level: MANUAL SHOULD

Back to Top

MemberResource-4xxErrorHasResponseBody

[SKIPPED TEST]
Skipping test because we have no read-only properties to PUT. Server-managed properties are specified using the "read-only-prop" command-line parameter.

Parameters:

NOTE: Covers only part of the specification requirement. testPutReadOnlyProperties4xxStatus covers the rest.

Reference URI: http://www.w3.org/TR/ldp#ldprs-put-servermanagedprops

Description: 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.

Requirement Level: SHOULD

Back to Top

MemberResource-ResponsePropertiesNotPersisted

[SKIPPED TEST]
Skipping test because PUT request was successful.

NOTE: Covers only part of the specification requirement. testPutPropertiesNotPersisted covers the rest.

Reference URI: http://www.w3.org/TR/ldp#ldprs-put-failed

Description: 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.

Requirement Level: SHOULD

Back to Top

BasicContainer-RestrictClientInference

[SKIPPED TEST]
This requirement or recommendation must be tested manually. It is difficult or impossible to write automated tests for and is not part of the testsuite.

How to Run testRestrictClientInference

Reference URI: http://www.w3.org/TR/ldp#ldprs-gen-noinferencing

Description: 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.

Requirement Level: MANUAL MUST

Back to Top

BasicContainer-ConformsRdfSourceLdpResource

[SKIPPED TEST]
Covered indirectly by the MUST tests defined in CommonResourceTest class

Test Case is covered Indirectly by the following:

Reference URI: http://www.w3.org/TR/ldp#ldprs-are-ldpr

Description: Each LDP RDF Source MUST also be a conforming LDP Resource as defined in section 4.2 Resource, along with the restrictions in this section.

Requirement Level: MUST

Back to Top

NonRDFSource-IsHttp11Manual

[SKIPPED TEST]
This requirement or recommendation must be tested manually. It is difficult or impossible to write automated tests for and is not part of the testsuite.

NOTE: Covers only part of the specification requirement. testIsHttp11Server covers the rest.

Reference URI: http://www.w3.org/TR/ldp#ldpr-gen-http

Description: LDP servers MUST at least be HTTP/1.1 conformant servers [HTTP11].

Requirement Level: MANUAL MUST

Back to Top

BasicContainer-ReUseVocabularies

[SKIPPED TEST]
This requirement or recommendation must be tested manually. It is difficult or impossible to write automated tests for and is not part of the testsuite.

How to Run testReUseVocabularies

Reference URI: http://www.w3.org/TR/ldp#ldprs-gen-reusevocab

Description: 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.

Requirement Level: MANUAL SHOULD

Back to Top

BasicContainer-ConformsBcLdpContainer

[SKIPPED TEST]
Covered indirectly by the MUST tests defined in CommonContainerTest class

Test Case is covered Indirectly by the following:

Reference URI: http://www.w3.org/TR/ldp#ldpbc-are-ldpcs

Description: Each LDP Basic Container MUST also be a conforming LDP Container in section 5.2 Container along with the following restrictions in this section.

Requirement Level: MUST

Back to Top

BasicContainer-RequestedInteractionModelCreateNotAllowed

[SKIPPED TEST]
containerAsResource is null

Parameters:

NOTE: Covers only part of the specification requirement. testRequestedInteractionModelHeaders covers the rest.

Reference URI: http://www.w3.org/TR/ldp#ldpc-post-createrdf

Description: 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.

Requirement Level: MUST

Back to Top

MemberResource-ConformsRdfSourceLdpResource

[SKIPPED TEST]
Covered indirectly by the MUST tests defined in CommonResourceTest class

Test Case is covered Indirectly by the following:

Reference URI: http://www.w3.org/TR/ldp#ldprs-are-ldpr

Description: Each LDP RDF Source MUST also be a conforming LDP Resource as defined in section 4.2 Resource, along with the restrictions in this section.

Requirement Level: MUST

Back to Top

MemberResource-RestrictClientInference

[SKIPPED TEST]
This requirement or recommendation must be tested manually. It is difficult or impossible to write automated tests for and is not part of the testsuite.

How to Run testRestrictClientInference

Reference URI: http://www.w3.org/TR/ldp#ldprs-gen-noinferencing

Description: 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.

Requirement Level: MANUAL MUST

Back to Top

MemberResource-IsHttp11Manual

[SKIPPED TEST]
This requirement or recommendation must be tested manually. It is difficult or impossible to write automated tests for and is not part of the testsuite.

NOTE: Covers only part of the specification requirement. testIsHttp11Server covers the rest.

Reference URI: http://www.w3.org/TR/ldp#ldpr-gen-http

Description: LDP servers MUST at least be HTTP/1.1 conformant servers [HTTP11].

Requirement Level: MANUAL MUST

Back to Top

BasicContainer-IsHttp11Manual

[SKIPPED TEST]
This requirement or recommendation must be tested manually. It is difficult or impossible to write automated tests for and is not part of the testsuite.

NOTE: Covers only part of the specification requirement. testIsHttp11Server covers the rest.

Reference URI: http://www.w3.org/TR/ldp#ldpr-gen-http

Description: LDP servers MUST at least be HTTP/1.1 conformant servers [HTTP11].

Requirement Level: MANUAL MUST

Back to Top

NonRDFSource-PreconditionRequiredStatusCode

NOTE: Covers only part of the specification requirement. testConditionFailedStatusCode, testPutBadETagand testPutRequiresIfMatch covers the rest.

Reference URI: http://www.w3.org/TR/ldp#ldpr-put-precond

Description: 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].

Requirement Level: MUST

Back to Top

NonRDFSource-PostResourceGetBinary

Reference URI: http://www.w3.org/TR/ldp#ldpr-gen-binary

Description: 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.

Requirement Level: MAY

Back to Top

BasicContainer-PutRequiresIfMatch

NOTE: Covers only part of the specification requirement. testConditionFailedStatusCode, testPreconditionRequiredStatusCode and testPutBadETag covers the rest.

Reference URI: http://www.w3.org/TR/ldp#ldpr-put-precond

Description: 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.

Requirement Level: SHOULD

Back to Top

MemberResource-PutReplacesResource

Reference URI: http://www.w3.org/TR/ldp#ldpr-put-replaceall

Description: 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.

Requirement Level: MUST

Back to Top

BasicContainer-RelativeUriResolutionPost

Parameters:

NOTE: Covers only part of the specification requirement.

Reference URI: http://www.w3.org/TR/ldp#ldpr-gen-defbaseuri

Description: 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.

Requirement Level: MUST

Back to Top

NonRDFSource-AcceptPatchHeader

Reference URI: http://www.w3.org/TR/ldp#ldpr-patch-acceptpatch

Description: 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.

Requirement Level: MUST

Back to Top

NonRDFSource-ETagHeadersGet

NOTE: Covers only part of the specification requirement. testETagHeadersHead covers the rest.

Reference URI: http://www.w3.org/TR/ldp#ldpr-gen-etags

Description: LDP server responses MUST use entity tags (either weak or strong ones) as response ETag header values.

Requirement Level: MUST

Back to Top

BasicContainer-PostJsonLd

Reference URI: http://www.w3.org/TR/ldp#ldpc-post-jsonld

Description: LDP servers SHOULD accept a request entity body with a request header of Content-Type with value of application/ld+json [JSON-LD].

Requirement Level: MUST

Back to Top

BasicContainer-AcceptPostResponseHeader

Reference URI: http://www.w3.org/TR/ldp#ldpc-post-acceptposthdr

Description: 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.

Requirement Level: MUST

Back to Top

MemberResource-OptionsAllowHeader

Reference URI: http://www.w3.org/TR/ldp#ldpr-options-allow

Description: 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.

Requirement Level: MUST

Back to Top

BasicContainer-AcceptPatchHeader

Reference URI: http://www.w3.org/TR/ldp#ldpr-patch-acceptpatch

Description: 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.

Requirement Level: MUST

Back to Top

BasicContainer-ContentTypeHeader

Reference URI: http://www.w3.org/TR/ldp#ldpc-post-contenttype

Description: LDP servers SHOULD use the Content-Type request header to determine the representation format when the request has an entity body.

Requirement Level: SHOULD

Back to Top

NonRDFSource-ConditionFailedStatusCode

NOTE: Covers only part of the specification requirement. testPutBadETag, testPreconditionRequiredStatusCode and testPutRequiresIfMatch covers the rest.

Reference URI: http://www.w3.org/TR/ldp#ldpr-put-precond

Description: 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].

Requirement Level: MUST

Back to Top

NonRDFSource-GetResource

Reference URI: http://www.w3.org/TR/ldp#ldpr-get-must

Description: LDP servers MUST support the HTTP GET Method for LDPRs

Requirement Level: MUST

Back to Top

BasicContainer-CreateWithoutConstraints

Reference URI: http://www.w3.org/TR/ldp#ldpc-post-mincontraints

Description: 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.

Requirement Level: SHOULD

Back to Top

MemberResource-GetResource

Reference URI: http://www.w3.org/TR/ldp#ldprs-gen-rdf

Description: 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.

Requirement Level: MUST

Back to Top

BasicContainer-DeleteRemovesContainmentTriple

Reference URI: http://www.w3.org/TR/ldp#ldpc-del-contremovesconttriple

Description: 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.

Requirement Level: MUST

Back to Top

MemberResource-PreconditionRequiredStatusCode

NOTE: Covers only part of the specification requirement. testConditionFailedStatusCode, testPutBadETagand testPutRequiresIfMatch covers the rest.

Reference URI: http://www.w3.org/TR/ldp#ldpr-put-precond

Description: 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].

Requirement Level: MUST

Back to Top

MemberResource-GetResourceAcceptTurtle

Reference URI: http://www.w3.org/TR/ldp#ldprs-get-turtle

Description: LDP servers must respond with a Turtle representation of the requested LDP-RS when the request includes an Accept header specifying text/turtle, unless HTTP content negotiation requires a different outcome [turtle].

Requirement Level: MUST

Back to Top

NonRDFSource-PostResourceGetMetadataAndBinary

Reference URI: http://www.w3.org/TR/ldp#ldpnr-are-ldpr

Description: 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.

Requirement Level: MAY

Back to Top

BasicContainer-PutToCreate

Reference URI: http://www.w3.org/TR/ldp#ldpr-put-create

Description: LDP servers MAY choose to allow the creation of new resources using HTTP PUT.

Requirement Level: MAY

Back to Top

BasicContainer-NullRelativeUriPost

Reference URI: http://www.w3.org/TR/ldp#ldpc-post-rdfnullrel

Description: 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.

Requirement Level: MUST

Back to Top

BasicContainer-RestrictUriReUseNoSlug

NOTE: Covers only part of the specification requirement. testRestrictUriReUseSlug covers the rest.

Reference URI: http://www.w3.org/TR/ldp#ldpc-post-dontreuseuris

Description: LDP servers that allow member creation via POST SHOULD NOT re-use URIs.

Requirement Level: SHOULD

Back to Top

NonRDFSource-Head

Reference URI: http://www.w3.org/TR/ldp#ldpr-head-must

Description: LDP servers MUST support the HTTP HEAD method.

Requirement Level: MUST

Back to Top

MemberResource-PutBadETag

NOTE: Covers only part of the specification requirement. testConditionFailedStatusCode, testPreconditionRequiredStatusCode and testPutRequiresIfMatch covers the rest.

Reference URI: http://www.w3.org/TR/ldp#ldpr-put-precond

Description: 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].

Requirement Level: MUST

Back to Top

MemberResource-PutSimpleUpdate

Reference URI: http://www.w3.org/TR/ldp#ldpr-put-simpleupdate

Description: 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.

Requirement Level: MUST

Back to Top

NonRDFSource-OptionsAllowHeader

Reference URI: http://www.w3.org/TR/ldp#ldpr-options-allow

Description: 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.

Requirement Level: MUST

Back to Top

BasicContainer-PostNoSlug

Reference URI: http://www.w3.org/TR/ldp#ldpc-post-serverassignuri

Description: LDP servers SHOULD assign the URI for the resource to be created using server application specific rules in the absence of a client hint.

Requirement Level: SHOULD

Back to Top

MemberResource-Options

Reference URI: http://www.w3.org/TR/ldp#ldpr-options-must

Description: LDP servers MUST support the HTTP OPTIONS method.

Requirement Level: MUST

Back to Top

BasicContainer-PatchMethod

Reference URI: http://www.w3.org/TR/ldp#ldpc-patch-req

Description: LDP servers are RECOMMENDED to support HTTP PATCH as the preferred method for updating an LDPC's empty-container triples.

Requirement Level: SHOULD

Back to Top

MemberResource-ETagHeadersHead

NOTE: Covers only part of the specification requirement. testETagHeadersGet covers the rest.

Reference URI: http://www.w3.org/TR/ldp#ldpr-gen-etags

Description: LDP server responses MUST use entity tags (either weak or strong ones) as response ETag header values.

Requirement Level: MUST

Back to Top

NonRDFSource-ETagHeadersHead

NOTE: Covers only part of the specification requirement. testETagHeadersGet covers the rest.

Reference URI: http://www.w3.org/TR/ldp#ldpr-gen-etags

Description: LDP server responses MUST use entity tags (either weak or strong ones) as response ETag header values.

Requirement Level: MUST

Back to Top

BasicContainer-PostResponseStatusAndLocation

Reference URI: http://www.w3.org/TR/ldp#ldpc-post-created201

Description: 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.

Requirement Level: MUST

Back to Top

MemberResource-LdpLinkHeader

Reference URI: http://www.w3.org/TR/ldp#ldpr-gen-linktypehdr

Description: 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.

Requirement Level: MUST

Back to Top

BasicContainer-ConditionFailedStatusCode

NOTE: Covers only part of the specification requirement. testPutBadETag, testPreconditionRequiredStatusCode and testPutRequiresIfMatch covers the rest.

Reference URI: http://www.w3.org/TR/ldp#ldpr-put-precond

Description: 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].

Requirement Level: MUST

Back to Top

BasicContainer-GetResponseHeaders

Reference URI: http://www.w3.org/TR/ldp#ldpr-get-options

Description: LDP servers MUST support the HTTP response headers defined in section 4.2.8 HTTP OPTIONS.

Requirement Level: MUST

Back to Top

BasicContainer-ETagHeadersGet

NOTE: Covers only part of the specification requirement. testETagHeadersHead covers the rest.

Reference URI: http://www.w3.org/TR/ldp#ldpr-gen-etags

Description: LDP server responses MUST use entity tags (either weak or strong ones) as response ETag header values.

Requirement Level: MUST

Back to Top

NonRDFSource-PostResourceAndCheckLink

Reference URI: http://www.w3.org/TR/ldp#ldpnr-type

Description: 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.

Requirement Level: MAY

Back to Top

NonRDFSource-OptionsHasSameLinkHeader

Reference URI: http://www.w3.org/TR/ldp#ldpc-options-linkmetahdr

Description: 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

Requirement Level: MUST

Back to Top

BasicContainer-NoRdfBagSeqOrList

Reference URI: http://www.w3.org/TR/ldp#ldpc-nordfcontainertypes

Description: LDPC representations SHOULD NOT use RDF container types rdf:Bag, rdf:Seq or rdf:List.

Requirement Level: SHOULD

Back to Top

MemberResource-GetResponseHeaders

Reference URI: http://www.w3.org/TR/ldp#ldpr-get-options

Description: LDP servers MUST support the HTTP response headers defined in section 4.2.8 HTTP OPTIONS.

Requirement Level: MUST

Back to Top

BasicContainer-GetResourceAsTurtleNoAccept

Reference URI: http://www.w3.org/TR/ldp#ldprs-get-conneg

Description: LDP servers should respond with a text/turtle representation of the requested LDP-RS whenever the Accept request header is absent [turtle].

Requirement Level: SHOULD

Back to Top

BasicContainer-ContainerSupportsHttpLinkHeader

NOTE: Covers only part of the specification requirement. DirectContainerTest.testHttpLinkHeader and IndirectContainerTest.testContainerSupportsHttpLinkHeader covers the rest.

Reference URI: http://www.w3.org/TR/ldp#ldpc-linktypehdr

Description: 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.

Requirement Level: MUST

Back to Top

NonRDFSource-Options

Reference URI: http://www.w3.org/TR/ldp#ldpr-options-must

Description: LDP servers MUST support the HTTP OPTIONS method.

Requirement Level: MUST

Back to Top

BasicContainer-ServerHonorsSlug

Reference URI: http://www.w3.org/TR/ldp#ldpc-post-slug

Description: 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.

Requirement Level: MAY

Back to Top

NonRDFSource-PutRequiresIfMatch

NOTE: Covers only part of the specification requirement. testConditionFailedStatusCode, testPreconditionRequiredStatusCode and testPutBadETag covers the rest.

Reference URI: http://www.w3.org/TR/ldp#ldpr-put-precond

Description: 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.

Requirement Level: SHOULD

Back to Top

BasicContainer-OptionsAllowHeader

Reference URI: http://www.w3.org/TR/ldp#ldpr-options-allow

Description: 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.

Requirement Level: MUST

Back to Top

MemberResource-PutRequiresIfMatch

NOTE: Covers only part of the specification requirement. testConditionFailedStatusCode, testPreconditionRequiredStatusCode and testPutBadETag covers the rest.

Reference URI: http://www.w3.org/TR/ldp#ldpr-put-precond

Description: 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.

Requirement Level: SHOULD

Back to Top

BasicContainer-LdpLinkHeader

Reference URI: http://www.w3.org/TR/ldp#ldpr-gen-linktypehdr

Description: 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.

Requirement Level: MUST

Back to Top

NonRDFSource-DeleteNonRDFSourceDeletesAssociatedResource

Reference URI: http://www.w3.org/TR/ldp#ldpc-del-contremovescontres

Description: 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.

Requirement Level: MUST

Back to Top

BasicContainer-Head

Reference URI: http://www.w3.org/TR/ldp#ldpr-head-must

Description: LDP servers MUST support the HTTP HEAD method.

Requirement Level: MUST

Back to Top

BasicContainer-GetResource

Reference URI: http://www.w3.org/TR/ldp#ldprs-gen-rdf

Description: 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.

Requirement Level: MUST

Back to Top

MemberResource-Head

Reference URI: http://www.w3.org/TR/ldp#ldpr-head-must

Description: LDP servers MUST support the HTTP HEAD method.

Requirement Level: MUST

Back to Top

MemberResource-JsonLdRepresentation

Reference URI: http://www.w3.org/TR/ldp#ldprs-get-jsonld

Description: LDP servers must respond with a application/ld+json representation of the requested LDP-RS when the request includes an Accept header, unless content negotiation or Turtle support requires a different outcome [JSON-LD].

Requirement Level: MUST

Back to Top

BasicContainer-PreconditionRequiredStatusCode

NOTE: Covers only part of the specification requirement. testConditionFailedStatusCode, testPutBadETagand testPutRequiresIfMatch covers the rest.

Reference URI: http://www.w3.org/TR/ldp#ldpr-put-precond

Description: 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].

Requirement Level: MUST

Back to Top

MemberResource-ETagHeadersGet

NOTE: Covers only part of the specification requirement. testETagHeadersHead covers the rest.

Reference URI: http://www.w3.org/TR/ldp#ldpr-gen-etags

Description: LDP server responses MUST use entity tags (either weak or strong ones) as response ETag header values.

Requirement Level: MUST

Back to Top

MemberResource-ConditionFailedStatusCode

NOTE: Covers only part of the specification requirement. testPutBadETag, testPreconditionRequiredStatusCode and testPutRequiresIfMatch covers the rest.

Reference URI: http://www.w3.org/TR/ldp#ldpr-put-precond

Description: 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].

Requirement Level: MUST

Back to Top

BasicContainer-Options

Reference URI: http://www.w3.org/TR/ldp#ldpr-options-must

Description: LDP servers MUST support the HTTP OPTIONS method.

Requirement Level: MUST

Back to Top

NonRDFSource-LdpLinkHeader

Reference URI: http://www.w3.org/TR/ldp#ldpr-gen-linktypehdr

Description: 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.

Requirement Level: MUST

Back to Top

MemberResource-AcceptPatchHeader

Reference URI: http://www.w3.org/TR/ldp#ldpr-patch-acceptpatch

Description: 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.

Requirement Level: MUST

Back to Top

MemberResource-ContainsRdfType

Reference URI: http://www.w3.org/TR/ldp#ldprs-gen-atleast1rdftype

Description: 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.

Requirement Level: SHOULD

Back to Top

NonRDFSource-PostNonRDFSource

NOTE: Covers only part of the specification requirement. testPostResourceAndGetFromContainer covers the rest.

Reference URI: http://www.w3.org/TR/ldp#ldpc-post-createbins

Description: LDP servers may accept an HTTP POST of non-RDF representations (LDP-NRs) for creation of any kind of resource, for example binary resources.

Requirement Level: MAY

Back to Top

BasicContainer-PutBadETag

NOTE: Covers only part of the specification requirement. testConditionFailedStatusCode, testPreconditionRequiredStatusCode and testPutRequiresIfMatch covers the rest.

Reference URI: http://www.w3.org/TR/ldp#ldpr-put-precond

Description: 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].

Requirement Level: MUST

Back to Top

BasicContainer-GetResourceAcceptTurtle

Reference URI: http://www.w3.org/TR/ldp#ldprs-get-turtle

Description: LDP servers must respond with a Turtle representation of the requested LDP-RS when the request includes an Accept header specifying text/turtle, unless HTTP content negotiation requires a different outcome [turtle].

Requirement Level: MUST

Back to Top

NonRDFSource-PutBadETag

NOTE: Covers only part of the specification requirement. testConditionFailedStatusCode, testPreconditionRequiredStatusCode and testPutRequiresIfMatch covers the rest.

Reference URI: http://www.w3.org/TR/ldp#ldpr-put-precond

Description: 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].

Requirement Level: MUST

Back to Top

BasicContainer-ETagHeadersHead

NOTE: Covers only part of the specification requirement. testETagHeadersGet covers the rest.

Reference URI: http://www.w3.org/TR/ldp#ldpr-gen-etags

Description: LDP server responses MUST use entity tags (either weak or strong ones) as response ETag header values.

Requirement Level: MUST

Back to Top

MemberResource-GetResourceAsTurtleNoAccept

Reference URI: http://www.w3.org/TR/ldp#ldprs-get-conneg

Description: LDP servers should respond with a text/turtle representation of the requested LDP-RS whenever the Accept request header is absent [turtle].

Requirement Level: SHOULD

Back to Top

MemberResource-TypeRdfSource

Reference URI: http://www.w3.org/TR/ldp#ldprs-rdftype

Description: The representation of a LDP-RS MAY have an rdf:type of ldp:RDFSource for Linked Data Platform RDF Source.

Requirement Level: MAY

Back to Top

NonRDFSource-GetResponseHeaders

Reference URI: http://www.w3.org/TR/ldp#ldpr-get-options

Description: LDP servers MUST support the HTTP response headers defined in section 4.2.8 HTTP OPTIONS.

Requirement Level: MUST

Back to Top

BasicContainer-JsonLdRepresentation

Reference URI: http://www.w3.org/TR/ldp#ldprs-get-jsonld

Description: LDP servers must respond with a application/ld+json representation of the requested LDP-RS when the request includes an Accept header, unless content negotiation or Turtle support requires a different outcome [JSON-LD].

Requirement Level: MUST

Back to Top

MemberResource-RelativeUriResolutionPut

Parameters:

Reference URI: http://www.w3.org/TR/ldp#ldpr-gen-defbaseuri

Description: 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.

Requirement Level: MUST

Back to Top

BasicContainer-AcceptTurtle

Reference URI: http://www.w3.org/TR/ldp#ldpc-post-turtle

Description: LDP servers MUST accept a request entity body with a request header of Content-Type with value of text/turtle [turtle].

Requirement Level: MUST

Back to Top

NonRDFSource-PostResourceAndCheckAssociatedResource

Reference URI: http://www.w3.org/TR/ldp#ldpc-post-createbinlinkmetahdr

Description: 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.

Requirement Level: MAY

Back to Top