search

neontribe / Linked_Development

Linked Development
1 stars 1 forks source link

Item detail and dereferenced uri's #46

Closed tobybatch closed 11 years ago

tobybatch commented 11 years ago

@practicalparticipation

I was foolishly thinking I could use the dereferenced uri to build the data for the get paths but this: 

http://tetchy.neontribe.org/linked-data/get

Does not seem to contain enough data to build:

http://api.ids.ac.uk/openapi/eldis/get/documents/A65165/full

Could you check the output in the first url and check it looks good please?

I'll go back to the construct query for now.

practicalparticipation commented 11 years ago

Yes - so the construct query is fetching a graph that might extend out a number of links from the URI we're fetching, whereas the DESCRIBE be default just gives us one link out.

Whilst we can modify the DESCRIBE / dereferenced URI behaviour, it would be better for the API to get all it's data only via SPARQL, as else it becomes less portable and more reliant on the behaviour of whatever is providing the deferenced URIs, which could change over time.

practicalparticipation commented 11 years ago

I can take a look at construct queries that might help later on if useful.