Closed jnehring closed 8 years ago
makes sense, will consider this.
resolvable URIs have been already configured. Example: http://data.freme-project.eu/resource/page/cordis/people/AdamMorawiecECSI
We have resolvable URIs for the CORDIS FP7: http://data.freme-project.eu/resource/page/cordis/people/AdamMorawiecECSI GRID: http://data.freme-project.eu/resource/page/grid/institutes/grid.414148.c and Global Airports: http://data.freme-project.eu/resource/page/airports/1
Very cool, thanks! I saw at http://data.freme-project.eu/resource/page/cordis/people/AdamMorawiecECSI that some generated triples hae URIs which not resolve, like http://data.freme-project.eu/resource/page/cordis/organizations/EUROPEAN+ELECTRONIC+CHIPS+%26+SYSTEMS+DESIGN+INITIATIVE Is this a technical issue or is the triple just with the wrong URI as object?
it looks like technical issue due to the encodings in the URI. Let me investigate this.
The three URIs
CORDIS FP7: http://data.freme-project.eu/resource/page/cordis/people/AdamMorawiecECSI GRID: http://data.freme-project.eu/resource/page/grid/institutes/grid.414148.c and Global Airports: http://data.freme-project.eu/resource/page/airports/1
lead to
Service Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
I think the resolvable URIs are broken.
fixed
When we convert datasets to linked data then we should take care that the URIs are resolvable. This involves two tasks:
We can schedule this feature for FREME 0.5