Virtuoso Universal Server LDN implementation report and test results

Description of a project

Project
Virtuoso Universal Server
Implementation type
receiver
Maintainer
http://kingsley.idehen.net/public_home/kidehen/profile.ttl#i

Dataset

Identifier
67d4f120-066d-11e7-9492-f96ede6a2dca
Published
Creator
http://kingsley.idehen.net/public_home/kidehen/profile.ttl#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: */*
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://ods-qa.openlinksw.com/DAV/home/demo/Public/inbox/3f38d2e0-066d-11e7-9492-f96ede6a2dca.jsonld 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 5 notifications.
Inbox has type ldp:Container. [source] automatic Found in Link header: http://www.w3.org/ns/ldp#BasicContainer
Advertises constraints with ldp:constrainedBy. [source] automatic Not found.
Returns JSON-LD on GET requests. [source] automatic
Notifications are available as JSON-LD. [source] automatic http://ods-qa.openlinksw.com/DAV/home/demo/Public/inbox/ldn: HTTP status 401, http://ods-qa.openlinksw.com/DAV/home/demo/Public/inbox/311bb950-066a-11e7-9cb7-570677dbe698.jsonld: Accept: application/ld+json => Content-Type: application/ld+json can be serialized as JSON-LD, http://ods-qa.openlinksw.com/DAV/home/demo/Public/inbox/10f838ad03d4918a: HTTP status 401, http://ods-qa.openlinksw.com/DAV/home/demo/Public/inbox/c2e2734fcd1accae: HTTP status 401, http://ods-qa.openlinksw.com/DAV/home/demo/Public/inbox/ldn2: HTTP status 401
When requested with no Accept header or */*, notifications are still returned as RDF. [source] automatic http://ods-qa.openlinksw.com/DAV/home/demo/Public/inbox/ldn: HTTP status 401, http://ods-qa.openlinksw.com/DAV/home/demo/Public/inbox/ldn: HTTP status 401, http://ods-qa.openlinksw.com/DAV/home/demo/Public/inbox/311bb950-066a-11e7-9cb7-570677dbe698.jsonld: Accept: */* => Content-Type: application/ld+json can be serialized as JSON-LD, http://ods-qa.openlinksw.com/DAV/home/demo/Public/inbox/311bb950-066a-11e7-9cb7-570677dbe698.jsonld: No Accept => Content-Type: application/ld+json can be serialized as JSON-LD, http://ods-qa.openlinksw.com/DAV/home/demo/Public/inbox/10f838ad03d4918a: HTTP status 401, http://ods-qa.openlinksw.com/DAV/home/demo/Public/inbox/10f838ad03d4918a: HTTP status 401, http://ods-qa.openlinksw.com/DAV/home/demo/Public/inbox/c2e2734fcd1accae: HTTP status 401, http://ods-qa.openlinksw.com/DAV/home/demo/Public/inbox/c2e2734fcd1accae: HTTP status 401, http://ods-qa.openlinksw.com/DAV/home/demo/Public/inbox/ldn2: HTTP status 401, http://ods-qa.openlinksw.com/DAV/home/demo/Public/inbox/ldn2: HTTP status 401