Conversation
|
4f4ef63 to
04ee3ed
Compare
|
Nope, the tests are still failing for EasyRdf 1.14.1 and above (also tested newest EasyRdf release 1.17.0). It seems there is still a compatibility issue between EasyRdf 1.14.1+ and Fuseki. This should probably be investigated further and reported to EasyRdf. |
04ee3ed to
608effc
Compare
|
The Fuseki compatibility issues have been sorted out in EasyRdf 1.18.0, so I bumped to that version. Also rebased on current Sadly, there is another EasyRdf/Fuseki compatibility issue; the Turtle parser fails to parse empty CONSTRUCT query responses. Reported as sweetrdf/easyrdf#74 |
|
|
There was one more EasyRdf bug, in the RDF/XML parser. It is now fixed and 1.18.2 has been released with the fix. |
There was a problem hiding this comment.
Looks fine - but I did find a bug in the handling of MIME-types: we have the same supported types for both vocabularies and concepts, but in fact we only support application/marcxml+xml on vocabulary level, not on concept level. If the MIME-type is requested for concept data
http://localhost/Skosmos/rest/v1/yso/data?format=application%2Fmarcxml%2Bxml&uri=http%3A%2F%2Fwww.yso.fi%2Fonto%2Fyso%2Fp8627&lang=fi
There should be an unsupported MIME-type message - but we don't get one, and we don't get marcxml either. Instead rdf-xml data is returned. I think this should be a separate bug report and this branch can be merged after that.



Reasons for creating this PR
We should use recent versions of EasyRdf (see #1700). This PR upgrades EasyRdf from 1.13.1 to 1.18.*, fixing some mock resources in the test suite according to changes in that release and removing content negotiation tweaks that are no longer necessary with recent changes to the Accept header in EasyRdf.
Link to relevant issue(s), if any
Description of the changes in this PR
Known problems or uncertainties in this PR
none
Checklist
.sr-onlyclass, color contrast)