cavendish
cavendish copied to clipboard
A LDP Implementation backed by BlazeGraph
``` {"date"=>"Tue, 04 Apr 2017 17:20:00 GMT", "link"=> "; rel=\"type\", ; rel=\"type\", ; rel=\"timemap\"", "etag"=>"W/\"25f3807ea9ce2bc0978e15b9ca2e7c5f\"", "allow"=>"GET,HEAD,OPTIONS,PATCH,POST,PUT", "accept-post"=>"text/turtle,application/ld+json", "accept-patch"=>"application/sparql-update", "content-type"=>"text/turtle", "transfer-encoding"=>"chunked", "server"=>"Jetty(9.3.6.v20151106)"} ```
It was removed to figure out jetty.xml, and should be returned.
- Required to build
Verify support for external content using message/external with URL and local-file access-types: * message/external-body spec: https://www.w3.org/Protocols/rfc1341/7_3_Message.html * access-type=url spec: https://tools.ietf.org/rfc/rfc2017.txt
When creating a resource with an empty Slug, the server doesn't replies and the connection stays open and nothing happens, is that behaviour normal ?
The `Accept-Post` is missing from the response header in a POST request to a container, as said [here](https://www.w3.org/TR/ldp/#ldpc-post-acceptposthdr) in the LDP Standard, this header should be included
Edit README to make mvn install requirement clear
- versioned resource interaction model - container of unmodifiable Memento resources as versions - version container is a Memento timemap (including application/link-format serialization) - vary response by datetime