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

Re: Discovering service descriptions

From: Chimezie Ogbuji <ogbujic@ccf.org>
Date: Tue, 11 Aug 2009 09:45:32 -0400
To: "Seaborne, Andy" <andy.seaborne@hp.com>, "Lee Feigenbaum" <lee@thefigtrees.net>, "SPARQL Working Group" <public-rdf-dawg@w3.org>
Message-ID: <C6A6EE3C.BCAB%ogbujic@ccf.org>
Comments below

>> Of the remaining options, 1 - HTTP Header and 7 - Conneg both are
>> "protocol-level" operations. They each seem to be somewhat specific to
>> HTTP, though I'm guessing there'd be a moral equivalent for things like
>> SOAP. They definitely lend themselves easily enough to equivalents via
>> an API (myEngine.getServiceDescription() ? :-) ).
>> The other options, DESCRIBE <endpoint> and DESCRIBE_ENDPOINT, are
>> "query-level" operations. Some people have expressed concerns that
>> DESCRIBE <endpoint> (or its cousin, DESCRIBE <>) constrains what
>> information the store can actually contain, and it also seems to me that
>> it requires that the endpoint actually have a URI in the first place,

Isn't this a reasonable assumption.

>> and that the caller know that URI (not necessarily the case in an API
>> environment, though there are non-standard ways to get at service
>> descriptions in those cases, as above, I guess).

I think allocating a URI to the endpoint and using it for things such as
discovery (even within a query) is a good practice even in an API
environment.  It also *feels* very intuitive

-- Chimezie


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

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:46:42 UTC

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