You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems hard for organisations to use a consistent name and uri as publisher (and creator). This is visible in the demonstrator where you see some organisations more than once. The RCE is the most extreme example:
Other organisations which appear more than once include the Anne Frank Stichting, CREATE, Nationaal Museum van Wereldculturen, KB and Gemeente Borne.
The datasetregister just shows the contents of the datasetdescriptions the organisations publish themselves. So the responsibility for using a consistent name and URI lies with these organisations themselves.
The Dataset Register should point out to these organisations that they currently do not use a consistent name/URI.
We could help these organisation by adding owl:sameAs triples. This would mean more maintenance (collecting the data) and also a change in the demonstrator (to use these sameAs and not duplicates). Note: the current repo in GraphDB does not do inference.
The text was updated successfully, but these errors were encountered:
It seems hard for organisations to use a consistent name and uri as publisher (and creator). This is visible in the demonstrator where you see some organisations more than once. The RCE is the most extreme example:
Linked to these 4 names are 5 different URIs:
Other organisations which appear more than once include the Anne Frank Stichting, CREATE, Nationaal Museum van Wereldculturen, KB and Gemeente Borne.
The datasetregister just shows the contents of the datasetdescriptions the organisations publish themselves. So the responsibility for using a consistent name and URI lies with these organisations themselves.
The Dataset Register should point out to these organisations that they currently do not use a consistent name/URI.
We could help these organisation by adding owl:sameAs triples. This would mean more maintenance (collecting the data) and also a change in the demonstrator (to use these sameAs and not duplicates). Note: the current repo in GraphDB does not do inference.
The text was updated successfully, but these errors were encountered: