W3C home > Mailing lists > Public > public-rdf-dawg-comments@w3.org > November 2004

UNSAID and OR use cases, from PRIME

From: Thomas Roessler <tlr@w3.org>
Date: Wed, 17 Nov 2004 17:34:20 +0100
To: public-rdf-dawg-comments@w3.org
Cc: Rigo Wenning <rigo@w3.org>, Giles Hogben <giles.hogben@jrc.it>
Message-ID: <20041117163420.GI6308@raktajino.does-not-exist.org>


for PRIME [1] purposes, it would be preferable to have both UNSAID
and OR clauses in SPARQL.  The project envisions translating APPEL
[2] type queries into RDF queries.  This would be difficult without
negation and both OR, and AND.  Design of the project's software
architecture is currently ongoing, and would be affected by
decisions to drop or include the UNSAID and OR clauses.

Two possible use cases are included below.

[1] http://www.prime-project.eu.org/
[2] http://www.w3.org/TR/P3P-preferences/

Use case 1, PRIME; UNSAID and OR: A mobile phone provider offers
location and contact information to third parties which, in turn,
offer location-based advertising by mobile phone short message.  An
airline operates an airport restaurant as a subsidiary, which wants
to advertise a special gourmet meal based on pork to members of the
airline's frequent flyer program who are nearby the restaurant,
unless these have indicated halal, kosher, or vegetarian meal

(Note that meal preferences give hints about religious convictions
and health conditions, and should as such not be processed by a
restaurant's advertising department.)

Use case 2, non-PRIME; UNSAID: A financial institution in Europe
wants to query an RDF database of its extremely wealthy clients to
send out an investment prospectus.  The prospectus must, however,
not be given to persons within the US or Canada, since the financial
institution wants to avoid SEC jurisdiction.  ("This prospectus is
not to be sent or given to any person within the United States or
Canada" is actually a standard clause in such documents.)

Speaking more generically, UNSAID queries enable access-controlled
queries which are based on *restrictions*, as opposed to explicit
*permissions*.  They would also enable data using parties to ask for
all attributes of a certain entity, unless these attributes are of a
certain type.

If you have any questions, feel free to contact me.

Thomas Roessler <tlr@w3.org>
Received on Wednesday, 17 November 2004 16:59:29 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:52:05 UTC