- From: Hugh Glaser <hg@ecs.soton.ac.uk>
- Date: Tue, 23 Apr 2013 19:39:15 +0000
- To: Mark Baker <distobj@acm.org>
- CC: "public-lod@w3.org <public-lod@w3.org" <public-lod@w3.org>, Phillip Lord <phillip.lord@newcastle.ac.uk>
Ah of course - thanks Mark, silly me.
So I look at the Link: header for something like
curl -L -i http://dbpedia.org/resource/Luton
Which gives me the information I want.
Anyone got any offers for how I would use Linked Data to get this into my RDF store?
So then I can do things something like:
SELECT ?type ?source FROM { <http://dbpedia.org/resource/Luton> ?foo ?file . ?file ?type ?source . }
(I think).
I suppose it would need to actually be returned from a URI at the site - I can't get a header as URI resolution - right?
And I would need an ontology?
Cheers.
On 23 Apr 2013, at 19:49, Mark Baker <distobj@acm.org>
wrote:
> On Tue, Apr 23, 2013 at 1:42 PM, Hugh Glaser <hg@ecs.soton.ac.uk> wrote:
>>
>> On 22 Apr 2013, at 12:18, Phillip Lord <phillip.lord@newcastle.ac.uk> wrote:
>> <snip>
>>> We need to check for content negotiation; I'm not clear, though, how we
>>> are supposed to know what forms of content are available. Is there
>>> anyway we can tell from your website that content negotiation is
>>> possible?
>> Ah, and interesting question.
>> I don't know of any, but maybe someone else does?
>
> Client-side conneg, look for Link rel=alternate headers in response
>
> Server-side conneg, look for "Vary: Content-Type" in response
>
> Mark.
Received on Tuesday, 23 April 2013 19:40:25 UTC