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

Re: Signalling entailment in queries

From: Alexandre Passant <alexandre.passant@deri.org>
Date: Wed, 21 Jul 2010 11:11:30 +0100
Cc: "Gregory Williams" <greg@evilfunhouse.com>, "Sandro Hawke" <sandro@w3.org>, "Birte Glimm" <birte.glimm@comlab.ox.ac.uk>, "SPARQL Working Group" <public-rdf-dawg@w3.org>
Message-Id: <D484D1C6-C178-4718-9505-4C98176591D7@deri.org>
To: Chimezie Ogbuji <ogbujic@ccf.org>

On 21 Jul 2010, at 02:44, Chimezie Ogbuji wrote:

> Comments inline below
> On 7/20/10 5:13 PM, "Gregory Williams" <greg@evilfunhouse.com> wrote:
>> I've always considered it a feature that an endpoint could use entailment on
>> the underlying data and the user would use the same query syntax. I'd be very
>> hesitant about a syntax that requires the user to specify an entailment regime
>> to use, especially if the system only supports one entailment regime and will
>> throw an error if you request others.
> I don't think the user has to specify an entailment regime, but they should
> be able to and there should be some order of precedence that determines
> which is used (in the same way we do with datasets).  It seems okay for the
> server to throw an error if an unsupported entailment regime is requested.

We currently have sd:supportedEntailment in the SD vocabulary - so sd:defaultEntailment would probably make sense.
-> User retrieves the endpoint's SD so can check if he's happy with the default one, or wants to apply another regime to the query.

Yet, there is still a need to figure out how this can be specified.
[1] seems indeed to be out of scope, but there was complex use-cases in there (RULESET, ontologies, etc.).
What about a limited set of available RULESET patterns ? (RDFS, etc.)


[1] http://www.w3.org/2009/sparql/wiki/Feature:ParameterizedInference

>> I don't want to be in the position of
>> trying to submit a query by hand and having to guess the supported entailment
>> repeatedly or having to download the service description and pick through it
>> to figure out what entailment regime the endpoint supports.
> See above.
> -- Chime
> ===================================
> 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 (2009).  
> 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.

Dr. Alexandre Passant
Digital Enterprise Research Institute
National University of Ireland, Galway
:me owl:sameAs <http://apassant.net/alex> .
Received on Wednesday, 21 July 2010 10:12:06 UTC

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