Run the LDP WG's Test Suite

[no-reply]

No description provided.

[no-reply]

Added the basic report here: https://github.com/ruby-rdf/rdf-ldp/blob/develop/report/ldp-testsuite-execution-report.html

I'm getting a bunch of Java NullPointerErrors, and a few other issues. It's hard to separate things that are problems on our end and things that relate to the test suite and/or my Java version. Giving this more attention this week.

[no-reply]

The test suite is strongly opinionated that POSTing with the same slug twice creates two resources with two different URIs. https://github.com/w3c/ldp-testsuite/blob/816e98ae3360ec6945b0db6cd9cb246045e2b654/src/main/java/org/w3/ldp/testsuite/test/CommonContainerTest.java#L907-L927

I had assumed it would be nicer to fail with 409, since we are otherwise honoring slugs precisely. I don't know of anything in HTTP/REST or LDP (other than the test suite) which suggests this is disallowed. I'll need to follow up with the list on this.

[no-reply]

We are now passing for both Basic and Direct Containers.

There are a couple of issues submitted to the test suite repository:

• Many tests fail with NullPointerError if a representation is an empty graph w3c/ldp-testsuite#224 until this is closed, we'll need to run the tests against https://github.com/ruby-rdf/rdf-ldp/tree/testsuite.
• Suite testRestrictUriReUseSlug fails if the server DOES NOT create second resource w3c/ldp-testsuite#225 this causes us to fail a SHOULD. Since we comply with the spirit, and the behavior is documented in IMPLEMENTATION.md, I'm not terribly concerned about when it gets closed.