- From: Steve Harris <steve.harris@garlik.com>
- Date: Tue, 11 Aug 2009 18:48:38 +0100
- To: Jacek Kopecky <jacek.kopecky@sti2.at>
- Cc: "public-rdf-dawg@w3.org Group" <public-rdf-dawg@w3.org>
That's what we do now. It's OK, but it would be nice if the property had slightly stronger semantics. People tend to crawl on rdfs:seeAlso too, and if there's SPARQL discovery data at the far end of the endpoint URI it might be a bit antisocial to do that. Right now they got a 500 error or something if they attempt to crawl it. - Steve On 11 Aug 2009, at 17:38, Jacek Kopecky wrote: > Beside the SIOC option, would something like this work for you? > > <some-resource> rdfs:seeAlso <http://sparql.example/endpoint> . > <http://sparql.example/endpoint> a sparql:Endpoint . > > Not creating a new property, but reusing a class that surely must > already exist out there. > > Jacek > > > > On Tue, 2009-08-11 at 07:12 +0100, Steve Harris wrote: >> I'm acutely aware of the dangers of scope creep, but one thing I >> think >> we ought to be able to say is something like: >> >> <some-resource> sparql:seeEndpoint <http://sparql.example/endpoint> . >> >> ie. an equivalent of rdfs:seeSlso, but with slightly stronger >> semantics, and meaning that there's a SPARQL endpoint at the object >> URI, that has some information about the the resource in the subject. >> >> It's something we needed to be able to say when building the FAOF >> Builder (http://foafbuilder.qdos.com/), but weren't able to. In the >> end we settled for rdfs:seeAlso, which is a pretty bad fit. >> >> - Steve >> > -- Steve Harris Garlik Limited, 2 Sheen Road, Richmond, TW9 1AE, UK +44(0)20 8973 2465 http://www.garlik.com/ Registered in England and Wales 535 7233 VAT # 849 0517 11 Registered office: Thames House, Portsmouth Road, Esher, Surrey, KT10 9AD
Received on Tuesday, 11 August 2009 17:49:15 UTC