Open ashleysommer opened 6 years ago
But do bear in mind that reg:RegisterItem
is the registration record (submitter, date, status etc) and is not the item description (species, name, fur length etc). The latter is independent of the registration record, which is register-specific, since the same description might be submitted to more than one register. You use reg:definition
to link from the RegisterItem to a blank node which has a property reg:entity
that points to the registered thing.
Download examples from LDR with metadata to see the full pattern. The RegisterItem and registered thing each have their own URI - the default pattern in the LDR as implemented is for the RI URI to prepend a "_" to the last field of the item URI.
Turns out I went in the wrong direction with this Issue.
The item type should actually be what is captured in self.contained_item_classes
, not self.uri
.
Created a new issue here: https://github.com/CSIRO-enviro-informatics/pyldapi/issues/12
Moving forward with reg:RegisterItem
, I believe we can use the new Accept-Profile mechanism to negotiate rendering a RI view, rather than the actual instances view.
In this cats registry example generated by pyldapi:
It shows each cat ("Jonny", "Sally", and "Spud") as
a <http://127.0.0.1:8081/cats> ;
I believe this to be incorrect, because it uses that same string as register:reg:register <http://127.0.0.1:8081/cats>
for each entry.I believe it should be:
See http://epimorphics.com/public/vocabulary/Registry.html