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

Re: Service description schema

From: Chimezie Ogbuji <ogbujic@ccf.org>
Date: Tue, 11 Aug 2009 09:55:11 -0400
To: "Steve Harris" <steve.harris@garlik.com>, "public-rdf-dawg@w3.org Group" <public-rdf-dawg@w3.org>
Message-ID: <C6A6F07F.BCAF%ogbujic@ccf.org>
I agree that something like this would be really useful.  I'm a big fan of
follow-your-nose via explicit RDF vocabulary (rather than network sniffing).
But did you mean for this sparql:seeEndpoint predicate to be explicitly
asserted or entailed (or the equivalent)?

-- Chimezie

On 8/11/09 2:12 AM, "Steve Harris" <steve.harris@garlik.com> 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


===================================

P Please consider the environment before printing this e-mail

Cleveland Clinic is ranked one of the top hospitals
in America by U.S. News & World Report (2008).  
Visit us online at http://www.clevelandclinic.org for
a complete listing of our services, staff and
locations.


Confidentiality Note:  This message is intended for use
only by the individual or entity to which it is addressed
and may contain information that is privileged,
confidential, and exempt from disclosure under applicable
law.  If the reader of this message is not the intended
recipient or the employee or agent responsible for
delivering the message to the intended recipient, you are
hereby notified that any dissemination, distribution or
copying of this communication is strictly prohibited.  If
you have received this communication in error,  please
contact the sender immediately and destroy the material in
its entirety, whether electronic or hard copy.  Thank you.
Received on Tuesday, 11 August 2009 13:56:16 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 16:15:39 GMT