SCTA inbox receiver LDN implementation report and test results

Description of a project

Project
SCTA inbox receiver
Implementation type
receiver
Maintainer
http://jeffreycwitt.com/#me

Dataset

Identifier
1036f850-fb8c-11e6-8de6-4d841750ffc3
Published
Creator
http://jeffreycwitt.com/#me
Note
Test pass on instance where post should be accepted.

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: http://inbox.scta.info/notifications/125?resourceid=http://scta.info/resource/lectio1 found and can be retrieved.
⌙ Restricts list of notification URIs (eg. according to access control). [source] semiAuto Test manually.
✔ Returns JSON-LD on GET requests. [source] automatic
✔ Inbox has type ldp:Container. [source] automatic Found in body: http://www.w3.org/ns/ldp#Container
⌙ Advertises constraints with ldp:constrainedBy. [source] automatic Not found.
✔ Lists notification URIs with ldp:contains. [source] automatic Found 4 notifications.
✔ Notifications are available as JSON-LD. [source] automatic http://inbox.scta.info/notifications/1?resourceid=http://scta.info/resource/lectio1: Accept: application/ld+json => Content-Type: application/ld+json can be serialized as JSON-LD, http://inbox.scta.info/notifications/122?resourceid=http://scta.info/resource/lectio1: Accept: application/ld+json => Content-Type: application/ld+json can be serialized as JSON-LD, http://inbox.scta.info/notifications/124?resourceid=http://scta.info/resource/lectio1: Accept: application/ld+json => Content-Type: application/ld+json can be serialized as JSON-LD, http://inbox.scta.info/notifications/125?resourceid=http://scta.info/resource/lectio1: 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://inbox.scta.info/notifications/1?resourceid=http://scta.info/resource/lectio1: Accept: */* => Content-Type: application/ld+json can be serialized as JSON-LD, http://inbox.scta.info/notifications/1?resourceid=http://scta.info/resource/lectio1: No Accept => Content-Type: application/ld+json can be serialized as JSON-LD, http://inbox.scta.info/notifications/122?resourceid=http://scta.info/resource/lectio1: Accept: */* => Content-Type: application/ld+json can be serialized as JSON-LD, http://inbox.scta.info/notifications/122?resourceid=http://scta.info/resource/lectio1: No Accept => Content-Type: application/ld+json can be serialized as JSON-LD, http://inbox.scta.info/notifications/124?resourceid=http://scta.info/resource/lectio1: Accept: */* => Content-Type: application/ld+json can be serialized as JSON-LD, http://inbox.scta.info/notifications/124?resourceid=http://scta.info/resource/lectio1: No Accept => Content-Type: application/ld+json can be serialized as JSON-LD, http://inbox.scta.info/notifications/125?resourceid=http://scta.info/resource/lectio1: Accept: */* => Content-Type: application/ld+json can be serialized as JSON-LD, http://inbox.scta.info/notifications/125?resourceid=http://scta.info/resource/lectio1: No Accept => Content-Type: application/ld+json can be serialized as JSON-LD
⌙ Fails to process notifications if implementation-specific constraints are not met. [source] automatic