W3C home > Mailing lists > Public > public-rdf-dawg@w3.org > January to March 2004

Re: Use case: OrderTracking-ConsumerAccess

From: Eric Prud'hommeaux <eric@w3.org>
Date: Thu, 25 Mar 2004 21:03:42 -0500
To: Rob Shearer <Rob.Shearer@networkinference.com>
Cc: RDF Data Access Working Group <public-rdf-dawg@w3.org>
Message-ID: <20040326020342.GI13553@w3.org>

On Thu, Mar 25, 2004 at 08:25:46PM -0500, Eric Prud'hommeaux wrote:
> FredCo sells a variety of products to consumers and maintains an order
> tracking database to track customer orders. The database is a
> conventional relational database with a schema normalized for their
> application

A consumer, Chip Thompson, wants to check on the status of his
order. His money-minding application, QuickWeb, supports a widely
adopted schema to track pending orders. It communicates a query to
http://fredco.example.org/RDF using DAWG-QL.

The endpoint trivially translates this query into a query that maps to
its internal structure (either a graph that corresponds to the actual
schema of their database, or a layer on top that is used to insulate
the enterprise programs from the implementation details). The endpoint
executes the query, re-maps the results to the outside schema before
giving them back to QuickWeb.

Chip plans to attend a party to show off the item which has just been
shippedq.

Sorry, no specific implementation on this one.
-- 
-eric

office: +81.466.49.1170 W3C, Keio Research Institute at SFC,
                        Shonan Fujisawa Campus, Keio University,
                        5322 Endo, Fujisawa, Kanagawa 252-8520
                        JAPAN
        +1.617.258.5741 NE43-344, MIT, Cambridge, MA 02144 USA
cell:   +1.857.222.5741 (does not work in Asia)

(eric@w3.org)
Feel free to forward this message to any list for any purpose other than
email address distribution.
Received on Thursday, 25 March 2004 21:03:42 GMT

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