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

Re: Use case: OrderTracking-Fluidity

From: Eric Prud'hommeaux <eric@w3.org>
Date: Thu, 25 Mar 2004 20:50:10 -0500
To: Rob Shearer <Rob.Shearer@networkinference.com>
Cc: RDF Data Access Working Group <public-rdf-dawg@w3.org>
Message-ID: <20040326015010.GH13553@w3.org>

On Thu, Mar 25, 2004 at 08:25:46PM -0500, Eric Prud'hommeaux wrote:
> 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

The sales department can store additional data not currently allowed
for in the relational schema. This out-of-relation data is stored in a
generic triple store next to the normalized relations. Because this is
stored with more structure than a "notes" field, queries can be
constructed to make good use of this data (imagine if google stored
triples). This allows the organization to fluidly adapt to needs to
express different kinds of data.

This use case demonstrates joining a conventional relational store
against a generic triple store to resolve a query expressed in DAWG-QL
[1]. Another exmaple [2] demonstrates out-of-relation data being
stored in the generic triple store. The latter would count as update
but it is useful to see that the data could come from somewhere
without sales people entering triples into the database by hand.

[1] http://dev.w3.org/cvsweb/perl/modules/W3C/Rdf/test/OrderTracking8-alg.sh?rev=HEAD&content-type=text/x-cvsweb-markup
[2] http://dev.w3.org/cvsweb/perl/modules/W3C/Rdf/test/OrderTracking7-alg.sh?rev=HEAD&content-type=text/x-cvsweb-markup

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

Feel free to forward this message to any list for any purpose other than
email address distribution.
Received on Thursday, 25 March 2004 20:59:27 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:00:24 UTC