LDP-CoAP LDN implementation report and test results

Description of a project

Project
LDP-CoAP
Implementation type
receiver
Maintainer
http://sisinflab.poliba.it

Dataset

Identifier
da9f3df0-4ad8-11e7-a741-cb560322e93d
Published
Creator
http://sisinflab.poliba.it
Note
PRCU test also passed in case of RDF body with implementation-specific constraints

Test results

Report
Outcome Test Mode Info
✔
Passed
✗
Failed
?
Cannot tell
⌙
Inapplicable
○
Untested
✔ Accepts OPTIONS requests. [source] automatic
✔ Advertises acceptable content types with Accept-Post in response to OPTIONS request. [source] automatic Accept-Post: text/turtle,application/ld+json
✔ Accept-Post includes application/ld+json. [source] automatic
✔ Accepts POST requests. [source] automatic HTTP 201
✔ Succeeds when the content type includes a profile parameter. [source] automatic
⌙ Fails to process notifications if implementation-specific constraints are not met. [source] automatic
✔ Responds to POST requests with Content-Type: application/ld+json with status code 201 Created or 202 Accepted. [source] automatic HTTP 201
✔ Returns a Location header in response to successful POST requests. [source] automatic Location: http://193.204.49.226:3000/proxy/coap://192.168.2.16:5688/inbox/873cf580-4ad8-11e7-a741-cb560322e93d.jsonld found and can be retrieved.
✔ Restricts list of notification URIs (eg. according to access control). [source] semiAuto
✔ Lists notification URIs with ldp:contains. [source] automatic Found 1 notification.
✔ Inbox has type ldp:Container. [source] automatic Found in Link header: http://www.w3.org/ns/ldp#BasicContainer, http://www.w3.org/ns/ldp#Container
✔ Advertises constraints with ldp:constrainedBy. [source] automatic Found: http://sisinflab.poliba.it/swottools/ldp-coap/ldp-report.html
✔ Returns JSON-LD on GET requests. [source] automatic
✔ Notifications are available as JSON-LD. [source] automatic http://193.204.49.226:3000/proxy/coap://192.168.2.16:5688/inbox/simple-notification: Accept: application/ld+json => Content-Type: application/ld+json can be serialized as JSON-LD
✔ When requested with no Accept header or */*, notifications are still returned as RDF. [source] automatic http://193.204.49.226:3000/proxy/coap://192.168.2.16:5688/inbox/simple-notification: Accept: */* => Content-Type: text/turtle can be serialized as JSON-LD, http://193.204.49.226:3000/proxy/coap://192.168.2.16:5688/inbox/simple-notification: No Accept => Content-Type: text/turtle can be serialized as JSON-LD