Internal server error caused when using web-UI to view register with multiple "reserved" entries about ukl-registry-poc HOT 5 CLOSED

Yes, just noticed that. The UI and indeed some of the internals are complaining about bNodes in the entity definition.

Will take a look (not till tomorrow).

This whole reservation business has been the most problematic part of the whole design :(

from ukl-registry-poc.

For info, I can see each of the reserved entries using the web-UI; e.g.

http://ukgovld-registry.dnsalias.net/codes/bufr4/codeflag/0-20-086/_14

Also, note that I specified these "reserved" entities with reg:status "submitted" (sub-type of "not-valid") so that they did not "pollute" the normal behaviour of GETting a set of valid entries when one queries the register.

from ukl-registry-poc.

Oops, accidentally closed the issue.

from ukl-registry-poc.

Fixed (I hope).

Fundamentally storing entity bNodes is a bad idea. I could make it work in the current implementation but if a future version shifted to separating the triple store from the registry itself then bNode round tripping would break again.

Solution is to rewrite entities which are bNodes to be "skolem" URIs at Registration.

For now I've left those skolem URIs in the responses which has the benefit of fixing some fragile UI links for reserved entities. The could be rewritten on output back to bNodes, though I prefer not to.

from ukl-registry-poc.

It seems reasonable to leave them as "skolem" URIs; don't rewrite. I am pleased to have learned something new today: http://www.w3.org/2011/rdf-wg/wiki/Skolemisation

from ukl-registry-poc.