- From: Eric Prud'hommeaux <eric@w3.org>
- Date: Thu, 25 Mar 2004 20:25:46 -0500
- To: Rob Shearer <Rob.Shearer@networkinference.com>
- Cc: RDF Data Access Working Group <public-rdf-dawg@w3.org>
om>
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
Each day, the invoicing program queries the database for orders from
the previous day. This query is expressed in DAWG-QL (motivating use
cases for this choice will follow) and, due to the normalization of
the database, joins several tables.
This use case calls for a mechanism providing RDF access to the bulk
of the machine-processable data in use today. It bears on the question
"how can we match what people use today?" Following messages with
address "how can we improve corporation's infrastructure?" and "how
can we improve consumer experience?"
It would, of course, be nice if there were no performance sacrifice
inherent in using DAWG-QL to perform this query. OrderTracking1-alg.sh
[1] demonstrates a test case for an application that transforms this
somewhat complex graph query into a single somewhat complex SQL query.
See also, the example tables [2].
[1] http://dev.w3.org/cvsweb/perl/modules/W3C/Rdf/test/OrderTracking1-alg.sh?rev=HEAD&content-type=text/x-cvsweb-markup
[2] http://www.w3.org/2003/01/21-RDF-RDB-access/#tables
--
-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 20:25:46 UTC