| Test Suite Name | Revision | Report Date | Skipped Tests | MUST Requirements | SHOULD Requirements | MAY Requirements |
|---|---|---|---|---|---|---|
| W3C Linked Data Platform Test Suite | 11-Apr-2017 | Wed May 31 16:16:55 CEST 2017 | (35/236) of the total tests. | 129/156 Passed 0/156 Failed 27/156 Skipped |
53/61 Passed 0/61 Failed 8/61 Skipped |
19/19 Passed 0/19 Failed 0/19 Skipped |
| Failed Test Cases | Groups | Description of Test Method |
|---|
| Skipped Test Cases | Groups | Description of Test Method |
|---|---|---|
| IndirectContainer-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. |
| 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. |
| 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-IsHttp11Manual | [MANUAL, MUST] | LDP servers MUST at least be HTTP/1.1 conformant servers [HTTP11]. |
| 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. |
| IndirectContainer-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. |
| IndirectContainer-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]. |
| 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. |
| IndirectContainer-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. |
| IndirectContainer-IsHttp11Manual | [MANUAL, MUST] | LDP servers MUST at least be HTTP/1.1 conformant servers [HTTP11]. |
| DirectContainer-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-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-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-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. |
| DirectContainer-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. |
| IndirectContainer-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. |
| DirectContainer-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. |
| DirectContainer-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. |
| DirectContainer-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. |
| DirectContainer-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. |
| DirectContainer-IsHttp11Manual | [MANUAL, MUST] | LDP servers MUST at least be HTTP/1.1 conformant servers [HTTP11]. |
| IndirectContainer-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-IsHttp11Manual | [MANUAL, MUST] | LDP servers MUST at least be HTTP/1.1 conformant servers [HTTP11]. |
| 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. |
| Passed Test Cases | Groups | Description of Test 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-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-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. |
| IndirectContainer-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) |
| IndirectContainer-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. |
| NonRDFSource-Options | [MUST] | LDP servers MUST support the HTTP OPTIONS method. |
| BasicContainer-RestrictUriReUseSlug | [SHOULD] | LDP servers that allow member creation via POST SHOULD NOT re-use URIs. |
| IndirectContainer-PutToCreate | [MAY] | LDP servers MAY choose to allow the creation of new resources using HTTP PUT. |
| 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. |
| DirectContainer-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]. |
| IndirectContainer-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-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]. |
| IndirectContainer-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. |
| IndirectContainer-Head | [MUST] | LDP servers MUST support the HTTP HEAD method. |
| DirectContainer-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. |
| IndirectContainer-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. |
| DirectContainer-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]. |
| DirectContainer-ETagHeadersGet | [MUST] | LDP server responses MUST use entity tags (either weak or strong ones) as response ETag header values. |
| DirectContainer-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. |
| IndirectContainer-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. |
| DirectContainer-RestrictUriReUseNoSlug | [SHOULD] | LDP servers that allow member creation via POST SHOULD NOT re-use URIs. |
| IndirectContainer-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. |
| 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 |
| IndirectContainer-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. |
| DirectContainer-PutToCreate | [MAY] | LDP servers MAY choose to allow the creation of new resources using HTTP PUT. |
| IndirectContainer-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]. |
| DirectContainer-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. |
| 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. |
| DirectContainer-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-ETagHeadersHead | [MUST] | LDP server responses MUST use entity tags (either weak or strong ones) as response ETag header values. |
| 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. |
| IndirectContainer-ContentTypeHeader | [SHOULD] | LDP servers SHOULD use the Content-Type request header to determine the representation format when the request has an entity body. |
| DirectContainer-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. |
| DirectContainer-DeleteResourceUpdatesTriples | [MUST] | 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. |
| 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) |
| IndirectContainer-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-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. |
| DirectContainer-MemberResourceTriple | [MUST] | 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. |
| DirectContainer-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-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-NoRdfBagSeqOrList | [SHOULD] | LDPC representations SHOULD NOT use RDF container types rdf:Bag, rdf:Seq or rdf:List. |
| BasicContainer-ETagHeadersGet | [MUST] | LDP server responses MUST use entity tags (either weak or strong ones) as response ETag header values. |
| MemberResource-TypeRdfSource | [MAY] | The representation of a LDP-RS MAY have an rdf:type of ldp:RDFSource for Linked Data Platform RDF Source. |
| DirectContainer-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. |
| DirectContainer-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. |
| 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. |
| 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. |
| IndirectContainer-NoRdfBagSeqOrList | [SHOULD] | LDPC representations SHOULD NOT use RDF container types rdf:Bag, rdf:Seq or rdf:List. |
| IndirectContainer-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]. |
| 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-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. |
| 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. |
| 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. |
| DirectContainer-HttpLinkHeader | [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. |
| DirectContainer-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. |
| DirectContainer-NoRdfBagSeqOrList | [SHOULD] | LDPC representations SHOULD NOT use RDF container types rdf:Bag, rdf:Seq or rdf:List. |
| 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]. |
| IndirectContainer-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]. |
| DirectContainer-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]. |
| 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. |
| DirectContainer-ActAsIfInsertedContentRelationTripleExists | [MUST] | 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. |
| BasicContainer-TypeRdfSource | [MAY] | The representation of a LDP-RS MAY have an rdf:type of ldp:RDFSource for Linked Data Platform RDF Source. |
| 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. |
| 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-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. |
| 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. |
| BasicContainer-ContentTypeHeader | [SHOULD] | LDP servers SHOULD use the Content-Type request header to determine the representation format when the request has an entity body. |
| DirectContainer-GetResponseHeaders | [MUST] | LDP servers MUST support the HTTP response headers defined in section 4.2.8 HTTP OPTIONS. |
| DirectContainer-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-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. |
| DirectContainer-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. |
| DirectContainer-Head | [MUST] | LDP servers MUST support the HTTP HEAD method. |
| NonRDFSource-Head | [MUST] | LDP servers MUST support the HTTP HEAD method. |
| BasicContainer-ETagHeadersHead | [MUST] | LDP server responses MUST use entity tags (either weak or strong ones) as response ETag header values. |
| DirectContainer-Options | [MUST] | LDP servers MUST support the HTTP OPTIONS method. |
| IndirectContainer-AcceptTurtle | [MUST] | LDP servers MUST accept a request entity body with a request header of Content-Type with value of text/turtle [turtle]. |
| DirectContainer-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. |
| 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-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]. |
| IndirectContainer-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. |
| 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-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-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) |
| 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. |
| 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. |
| DirectContainer-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]. |
| IndirectContainer-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]. |
| IndirectContainer-GetResponseHeaders | [MUST] | LDP servers MUST support the HTTP response headers defined in section 4.2.8 HTTP OPTIONS. |
| 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. |
| DirectContainer-UseMemberPredicate | [ldpMember, SHOULD] | 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. |
| IndirectContainer-PatchMethod | [SHOULD] | LDP servers are RECOMMENDED to support HTTP PATCH as the preferred method for updating an LDPC's empty-container triples. |
| IndirectContainer-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. |
| IndirectContainer-RestrictUriReUseSlug | [SHOULD] | LDP servers that allow member creation via POST SHOULD NOT re-use URIs. |
| BasicContainer-PatchMethod | [SHOULD] | LDP servers are RECOMMENDED to support HTTP PATCH as the preferred method for updating an LDPC's empty-container triples. |
| IndirectContainer-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-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-AcceptTurtle | [MUST] | LDP servers MUST accept a request entity body with a request header of Content-Type with value of text/turtle [turtle]. |
| 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]. |
| IndirectContainer-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-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. |
| 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-ETagHeadersGet | [MUST] | LDP server responses MUST use entity tags (either weak or strong ones) as response ETag header values. |
| IndirectContainer-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-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. |
| IndirectContainer-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. |
| DirectContainer-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. |
| IndirectContainer-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-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. |
| DirectContainer-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. |
| DirectContainer-PatchMethod | [SHOULD] | LDP servers are RECOMMENDED to support HTTP PATCH as the preferred method for updating an LDPC's empty-container triples. |
| DirectContainer-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. |
| 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. |
| 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. |
| 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. |
| IndirectContainer-TypeRdfSource | [MAY] | The representation of a LDP-RS MAY have an rdf:type of ldp:RDFSource for Linked Data Platform RDF Source. |
| BasicContainer-Head | [MUST] | LDP servers MUST support the HTTP HEAD method. |
| DirectContainer-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]. |
| IndirectContainer-ContainerHasInsertedContentRelation WG Approval Pending |
[MUST] | 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. |
| 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-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-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. |
| IndirectContainer-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-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]. |
| DirectContainer-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. |
| IndirectContainer-GetResourceAsTurtleNoAccept | [SHOULD] | LDP servers should respond with a text/turtle representation of the requested LDP-RS whenever the Accept request header is absent [turtle]. |
| 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. |
| DirectContainer-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. |
| BasicContainer-RestrictUriReUseNoSlug | [SHOULD] | LDP servers that allow member creation via POST SHOULD NOT re-use URIs. |
| DirectContainer-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-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. |
| 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. |
| DirectContainer-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. |
| IndirectContainer-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-ETagHeadersHead | [MUST] | LDP server responses MUST use entity tags (either weak or strong ones) as response ETag header values. |
| IndirectContainer-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-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-PutToCreate | [MAY] | LDP servers MAY choose to allow the creation of new resources using HTTP PUT. |
| DirectContainer-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]. |
| DirectContainer-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]. |
| IndirectContainer-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-GetResponseHeaders | [MUST] | LDP servers MUST support the HTTP response headers defined in section 4.2.8 HTTP OPTIONS. |
| 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. |
| DirectContainer-PostResourceUpdatesTriples | [MUST] | 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. |
| DirectContainer-ETagHeadersHead | [MUST] | LDP server responses MUST use entity tags (either weak or strong ones) as response ETag header values. |
| 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. |
| IndirectContainer-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. |
| 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. |
| 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]. |
| 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]. |
| 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]. |
| IndirectContainer-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. |
| IndirectContainer-ETagHeadersHead | [MUST] | LDP server responses MUST use entity tags (either weak or strong ones) as response ETag header values. |
| IndirectContainer-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]. |
| DirectContainer-PreferMembershipTriples | [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]. |
| IndirectContainer-Options | [MUST] | LDP servers MUST support the HTTP OPTIONS method. |
| 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-ETagHeadersGet | [MUST] | LDP server responses MUST use entity tags (either weak or strong ones) as response ETag header values. |
| IndirectContainer-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. |
| IndirectContainer-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-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-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. |
| NonRDFSource-GetResource | [MUST] | LDP servers MUST support the HTTP GET Method for LDPRs |
| DirectContainer-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]. |
| BasicContainer-Options | [MUST] | LDP servers MUST support the HTTP OPTIONS method. |
| DirectContainer-ContentTypeHeader | [SHOULD] | LDP servers SHOULD use the Content-Type request header to determine the representation format when the request has an entity body. |
| 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. |
| DirectContainer-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-GetResponseHeaders | [MUST] | LDP servers MUST support the HTTP response headers defined in section 4.2.8 HTTP OPTIONS. |
| 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]. |
| DirectContainer-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-GetResponseHeaders | [MUST] | LDP servers MUST support the HTTP response headers defined in section 4.2.8 HTTP OPTIONS. |
| IndirectContainer-RestrictUriReUseNoSlug | [SHOULD] | LDP servers that allow member creation via POST SHOULD NOT re-use URIs. |
| DirectContainer-TypeRdfSource | [MAY] | The representation of a LDP-RS MAY have an rdf:type of ldp:RDFSource for Linked Data Platform RDF Source. |
| 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. |
| IndirectContainer-ETagHeadersGet | [MUST] | LDP server responses MUST use entity tags (either weak or strong ones) as response ETag header values. |
| IndirectContainer-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. |
| DirectContainer-AcceptTurtle | [MUST] | LDP servers MUST accept a request entity body with a request header of Content-Type with value of text/turtle [turtle]. |
| MemberResource-Head | [MUST] | LDP servers MUST support the HTTP HEAD method. |
| 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]. |
| DirectContainer-RestrictUriReUseSlug | [SHOULD] | LDP servers that allow member creation via POST SHOULD NOT re-use URIs. |
| 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-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. |
| DirectContainer-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) |
| IndirectContainer-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-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. |
| 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. |
| DirectContainer-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. |
| IndirectContainer-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]. |
| IndirectContainer-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. |
| 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. |
| MemberResource-Options | [MUST] | LDP servers MUST support the HTTP OPTIONS method. |
| DirectContainer-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-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]. |
| IndirectContainer-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. |
| DirectContainer-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. |
| IndirectContainer-PostResource WG Approval Pending |
[MUST] | 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. |
| DirectContainer-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. |
| 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. |
| DirectContainer-MemberRelationOrIsMemberOfRelationTripleExists | [MUST] | 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. |
| Indirectly Tested Test Cases | Overall Test Result | Description of Test Method |
|---|---|---|
| BasicContainer-ConformsContainerRdfResource | Passed | Each Linked Data Platform Container MUST also be a conforming Linked Data Platform RDF Source. |
| BasicContainer-ConformsRdfSourceLdpResource | Passed | 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. |
| DirectContainer-ConformsRdfSourceLdpResource | Passed | 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. |
| IndirectContainer-ConformsRdfSourceLdpResource | Passed | 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. |
| MemberResource-ConformsRdfSourceLdpResource | Passed | 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. |
| DirectContainer-ConformsDcLdpContainer | Passed | Each LDP Direct Container MUST also be a conforming LDP Container in section 5.2 Container along the following restrictions. |
| DirectContainer-ConformsContainerRdfResource | Passed | Each Linked Data Platform Container MUST also be a conforming Linked Data Platform RDF Source. |
| IndirectContainer-ConformsContainerRdfResource | Passed | Each Linked Data Platform Container MUST also be a conforming Linked Data Platform RDF Source. |
| BasicContainer-ConformsBcLdpContainer | Passed | Each LDP Basic Container MUST also be a conforming LDP Container in section 5.2 Container along with the following restrictions in this section. |
| [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
| [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
| [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
| [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
| [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
| [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
| [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
| [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
| [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
| [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
| [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
| [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
| [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
| [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
| [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
| [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
| [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
| [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#ldpdc-are-ldpcs
Description: Each LDP Direct Container MUST also be a conforming LDP Container in section 5.2 Container along the following restrictions.
Requirement Level: MUST
| [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
| [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
| [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
| [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
| [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
| [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
| [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
| [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
| [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
| [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
| [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
| [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
| [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
| [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
| [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
| [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
| [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
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
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
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
Parameters: http://purl.org/dc/terms/contributor
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
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
Reference URI: http://www.w3.org/TR/ldp#ldpr-options-must
Description: LDP servers MUST support the HTTP OPTIONS method.
Requirement Level: MUST
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
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
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
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
Parameters: http://purl.org/dc/terms/contributor
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
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
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
Reference URI: http://www.w3.org/TR/ldp#ldpr-head-must
Description: LDP servers MUST support the HTTP HEAD method.
Requirement Level: MUST
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
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
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
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
Parameters: http://192.168.2.16:8080/proxy/coap://192.168.2.16:5688/bc-asres/
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
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
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
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
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
NOTE: Covers only part of the specification requirement. DirectContainerTest.testHttpLinkHeader and BasicContainerTest.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
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
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
Parameters: http://192.168.2.16:8080/proxy/coap://192.168.2.16:5688/bc-asres/
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
Parameters: http://purl.org/dc/terms/contributor
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
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
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
Parameters: http://purl.org/dc/terms/contributor
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
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
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
Reference URI: http://www.w3.org/TR/ldp#ldpdc-del-contremovesmbrtriple
Description: 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.
Requirement Level: MUST
Parameters: http://purl.org/dc/terms/contributor
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
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
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
Reference URI: http://www.w3.org/TR/ldp#ldpdc-containres
Description: 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.
Requirement Level: MUST
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
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
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
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
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
Parameters: http://purl.org/dc/terms/contributor
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
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
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
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
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
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
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
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
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
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
NOTE: Covers only part of the specification requirement. IndirectContainerTest.testContainerSupportsHttpLinkHeader and BasicContainerTest.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
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
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
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
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
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
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
Reference URI: http://www.w3.org/TR/ldp#ldpdc-indirectmbr-basic
Description: 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.
Requirement Level: MUST
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
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
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
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
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
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
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
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
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
Parameters: http://purl.org/dc/terms/contributor
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
Reference URI: http://www.w3.org/TR/ldp#ldpr-head-must
Description: LDP servers MUST support the HTTP HEAD method.
Requirement Level: MUST
Reference URI: http://www.w3.org/TR/ldp#ldpr-head-must
Description: LDP servers MUST support the HTTP HEAD method.
Requirement Level: MUST
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
Reference URI: http://www.w3.org/TR/ldp#ldpr-options-must
Description: LDP servers MUST support the HTTP OPTIONS method.
Requirement Level: MUST
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
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
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
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
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
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
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
Parameters: http://purl.org/dc/terms/contributor
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
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
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
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
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
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
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
Reference URI: http://www.w3.org/TR/ldp#ldpdc-mbrpred
Description: 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.
Requirement Level: ldpMember SHOULD
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
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
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
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
Parameters: http://192.168.2.16:8080/proxy/coap://192.168.2.16:5688/bc-asres/
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
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
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
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
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
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
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
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
Parameters: http://192.168.2.16:8080/proxy/coap://192.168.2.16:5688/bc-asres/
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
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
Parameters: http://purl.org/dc/terms/contributor
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
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
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
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
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
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
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
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
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
Parameters: http://purl.org/dc/terms/contributor
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
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
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
Reference URI: http://www.w3.org/TR/ldp#ldpr-head-must
Description: LDP servers MUST support the HTTP HEAD method.
Requirement Level: MUST
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
Reference URI: http://www.w3.org/TR/ldp#ldpic-indirectmbr
Description: 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.
Requirement Level: MUST
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
Parameters: http://192.168.2.16:8080/proxy/coap://192.168.2.16:5688/bc-asres/
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
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
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
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
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
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
Parameters: http://purl.org/dc/terms/contributor
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
Reference URI: http://www.w3.org/TR/ldp#ldpdc-post-createdmbr-member
Description: 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.
Requirement Level: MUST
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
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
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
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
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
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
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
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
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
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
NOTE: Covers only part of the specification requirement.
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
Reference URI: http://www.w3.org/TR/ldp#ldpr-options-must
Description: LDP servers MUST support the HTTP OPTIONS method.
Requirement Level: MUST
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
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
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
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
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
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
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
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
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
Reference URI: http://www.w3.org/TR/ldp#ldpr-options-must
Description: LDP servers MUST support the HTTP OPTIONS method.
Requirement Level: MUST
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
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
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
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
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
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
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
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
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
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
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
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
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
Reference URI: http://www.w3.org/TR/ldp#ldpr-head-must
Description: LDP servers MUST support the HTTP HEAD method.
Requirement Level: MUST
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
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
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
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
Parameters: http://purl.org/dc/terms/contributor
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
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
Parameters: http://192.168.2.16:8080/proxy/coap://192.168.2.16:5688/bc-asres/
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
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
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
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
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
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
Reference URI: http://www.w3.org/TR/ldp#ldpr-options-must
Description: LDP servers MUST support the HTTP OPTIONS method.
Requirement Level: MUST
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
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
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
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
Reference URI: http://www.w3.org/TR/ldp#ldpic-post-indirectmbrrel
Description: 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.
Requirement Level: MUST
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
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
Reference URI: http://www.w3.org/TR/ldp#ldpdc-containtriples
Description: 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.
Requirement Level: MUST