You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONSTRAINED_BY.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,9 +6,9 @@ This file documents constraints imposed by `RDF::LDP`, `Rack:LDP` middleware, an
6
6
RDF Types
7
7
---------
8
8
9
-
The `RDF::LDP` core does not set types for resources. Complying with [LDP 4.3.1.2](http://www.w3.org/TR/ldp/#h-ldprs-gen-atleast1rdftype) is left to the client (or the server implementer). Interaction models are expressed as Link headers, and the client may infer rdf:types in accordance with the specification.
9
+
The `RDF::LDP` core does not set types for resources. Complying with [LDP 4.3.1.2](https://www.w3.org/TR/ldp/#h-ldprs-gen-atleast1rdftype) is left to the client (or the server implementer). Interaction models are expressed as Link headers, and the client may infer rdf:types in accordance with the specification.
10
10
11
-
Similarly, we do not enforce the recommendation of [LDP 5.2.1.3](http://www.w3.org/TR/ldp/#h-ldpc-nordfcontainertypes) for containers not to have type ` rdf:Bag`, `rdf:Seq` or `rdf:List`. This is left to the client (or server implementer) to manage.
11
+
Similarly, we do not enforce the recommendation of [LDP 5.2.1.3](https://www.w3.org/TR/ldp/#h-ldpc-nordfcontainertypes) for containers not to have type ` rdf:Bag`, `rdf:Seq` or `rdf:List`. This is left to the client (or server implementer) to manage.
12
12
13
13
POST/PUT Requests
14
14
------------------
@@ -47,7 +47,7 @@ For Indirect Contianers with an `ldp:insertedContentRelation` other than `ldp:Me
47
47
Named Graphs
48
48
-------------
49
49
50
-
Serializations supporting quads are allowed in POST and PUT requests. Graph names are ignored, and the file is treated as a single graph representing the resource. This behavior is seen as in compliance with [4.2.4.1](http://www.w3.org/TR/ldp/#h-ldpr-put-replaceall).
50
+
Serializations supporting quads are allowed in POST and PUT requests. Graph names are ignored, and the file is treated as a single graph representing the resource. This behavior is seen as in compliance with [4.2.4.1](https://www.w3.org/TR/ldp/#h-ldpr-put-replaceall).
51
51
52
52
HTTP PATCH
53
53
-----------
@@ -56,4 +56,4 @@ We currently support HTTP PATCH with the LDPatch and SPARQL Update formats. PATC
56
56
57
57
----
58
58
59
-
Linking to this document fulfills [Section 4.2.1.6](http://www.w3.org/TR/ldp#h-ldpr-gen-pubclireqs) of the LDP specification. Implementers of servers based on `RDF::LDP` and `Rack::LDP` are advised to create their own documents to clarify how these constraints effect their own services.
59
+
Linking to this document fulfills [Section 4.2.1.6](https://www.w3.org/TR/ldp#h-ldpr-gen-pubclireqs) of the LDP specification. Implementers of servers based on `RDF::LDP` and `Rack::LDP` are advised to create their own documents to clarify how these constraints effect their own services.
0 commit comments