Carbon LDP LDN implementation report and test results

Description of a project

Project
Carbon LDP
Implementation type
receiver
Maintainer
https://carbonldp.com/

Dataset

Identifier
4a6982c0-fddc-11e6-9cdc-c5ba5d2e04f7
Published
Creator
https://carbonldp.com/

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: application/ld+json, text/turtle
✔ 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
✔ 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: https://carbonldp.base22.io/apps/ldn/2398aea0-fddc-11e6-9cdc-c5ba5d2e04f7jsonld/ found and can be retrieved.
✔ Restricts list of notification URIs (eg. according to access control). [source] semiAuto Test manually.
✔ Lists notification URIs with ldp:contains. [source] automatic Found 4 notifications.
✔ Returns JSON-LD on GET requests. [source] automatic
✔ 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 Not found.
✔ Notifications are available as JSON-LD. [source] automatic https://carbonldp.base22.io/apps/ldn/auth-tokens/: Accept: application/ld+json => Content-Type: application/ld+json can be serialized as JSON-LD, https://carbonldp.base22.io/apps/ldn/auth-tickets/: Accept: application/ld+json => Content-Type: application/ld+json can be serialized as JSON-LD, https://carbonldp.base22.io/apps/ldn/roles/: Accept: application/ld+json => Content-Type: application/ld+json can be serialized as JSON-LD, https://carbonldp.base22.io/apps/ldn/agents/: 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 https://carbonldp.base22.io/apps/ldn/auth-tokens/: Accept: */* => Content-Type: text/turtle can be serialized as JSON-LD, https://carbonldp.base22.io/apps/ldn/auth-tokens/: No Accept => Content-Type: text/turtle can be serialized as JSON-LD, https://carbonldp.base22.io/apps/ldn/auth-tickets/: Accept: */* => Content-Type: text/turtle can be serialized as JSON-LD, https://carbonldp.base22.io/apps/ldn/auth-tickets/: No Accept => Content-Type: text/turtle can be serialized as JSON-LD, https://carbonldp.base22.io/apps/ldn/roles/: Accept: */* => Content-Type: text/turtle can be serialized as JSON-LD, https://carbonldp.base22.io/apps/ldn/roles/: No Accept => Content-Type: text/turtle can be serialized as JSON-LD, https://carbonldp.base22.io/apps/ldn/agents/: Accept: */* => Content-Type: text/turtle can be serialized as JSON-LD, https://carbonldp.base22.io/apps/ldn/agents/: No Accept => Content-Type: text/turtle can be serialized as JSON-LD
✔ Fails to process notifications if implementation-specific constraints are not met. [source] automatic