HTTP 500 Internal Server Error when trying to "put" a new entity definition; accidentially used HTTP POST! about ukl-registry-poc HOT 4 CLOSED

Bear in mind the the deployed instance has not been updated, the current code base does map more "Internal Errors" to "Bad Requests", including I think that one.

I'm currently working on ISSUE-33 to fix the problems with reserving via blank nodes, nearly there and will update that issue.

from ukl-registry-poc.

Thanks for heads up. Jeremy

from ukl-registry-poc.

PS. the idea that I tried out here (e.g. creating a concrete "reserved" concept in the target location and then updating that concept later when the identifier is allocated) works OK; albeit that I don't really like changing the semantics of the concrete concept (e.g. from "reserved" to the semantics of the allocated concept).

I can live with this approach ... but it feels like a better solution to assert the reserved concept as a blank node which is referenced by a register item with the appropriate notation plus label & description indicating "reserved [...]". I guess the challenge is getting these reserved nodes to appear as members of the register (or some-such).

However, just to make it clear, I can live with the blunt approach described above.

from ukl-registry-poc.

Verified that current code rejects a POST to a non-register with 400 ("Can only register items in a register") instead of 500.

Given that and resolution to #33 (pending review) closing this issue.

from ukl-registry-poc.