W3C home > Mailing lists > Public > public-rdf-dawg@w3.org > July to September 2009

Re: Service description schema

From: Jacek Kopecky <jacek.kopecky@sti2.at>
Date: Tue, 11 Aug 2009 18:38:09 +0200
To: Steve Harris <steve.harris@garlik.com>
Cc: "public-rdf-dawg@w3.org Group" <public-rdf-dawg@w3.org>
Message-Id: <1250008689.5410.66.camel@Kalb>
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.


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
Received on Tuesday, 11 August 2009 16:38:46 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:00:57 UTC