maytkso LDN implementation report and test results

Description of a project

Project
maytkso
Implementation type
receiver
Maintainer
http://csarven.ca/#i

Dataset

Identifier
74ff0110-f82b-11e6-a642-0dd857219753
Published
Creator
http://csarven.ca/#i

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/html, application/xhtml+xml, 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://linkedresearch.org/ldn/tests/inbox/ef401cd0-f82a-11e6-8458-353b08e96f93.jsonld 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 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.
✔ Lists notification URIs with ldp:contains. [source] automatic Found 2 notifications.
✔ Notifications are available as JSON-LD. [source] automatic https://linkedresearch.org/ldn/tests/inbox/b3a27500-f81c-11e6-9bf2-55c9148911ff.jsonld: Accept: application/ld+json => Content-Type: application/ld+json; charset=utf-8 can be serialized as JSON-LD, https://linkedresearch.org/ldn/tests/inbox/d36da1a0-f823-11e6-a560-93b44cc1d87e.jsonld: Accept: application/ld+json => Content-Type: application/ld+json; charset=utf-8 can be serialized as JSON-LD
✔ When requested with no Accept header or */*, notifications are still returned as RDF. [source] automatic https://linkedresearch.org/ldn/tests/inbox/b3a27500-f81c-11e6-9bf2-55c9148911ff.jsonld: Accept: */* => Content-Type: application/ld+json; charset=utf-8 can be serialized as JSON-LD, https://linkedresearch.org/ldn/tests/inbox/b3a27500-f81c-11e6-9bf2-55c9148911ff.jsonld: No Accept => Content-Type: application/ld+json; charset=utf-8 can be serialized as JSON-LD, https://linkedresearch.org/ldn/tests/inbox/d36da1a0-f823-11e6-a560-93b44cc1d87e.jsonld: Accept: */* => Content-Type: application/ld+json; charset=utf-8 can be serialized as JSON-LD, https://linkedresearch.org/ldn/tests/inbox/d36da1a0-f823-11e6-a560-93b44cc1d87e.jsonld: No Accept => Content-Type: application/ld+json; charset=utf-8 can be serialized as JSON-LD
⌙ Fails to process notifications if implementation-specific constraints are not met. [source] automatic