RE: RDB2RDF Usecase

Hello Ashok,

Sure.  Do you have a template for use case? and also how long, i.e., is it 1-2 pages or more?

BTW. Wanted to wish you all happy holidays and best new year.
I am disappearing starting this Monday to new years eve (out of town) going to East coast in undisclosed location and disconnected from the rest of the world.  I will work on the use case but will not be available online.
Best Regards,

Ahmed


-----Original Message-----
From: ashok malhotra [mailto:ashok.malhotra@oracle.com]
Sent: Friday, December 19, 2008 14:38
To: Ezzat, Ahmed
Cc: public-xg-rdb2rdf@w3.org
Subject: Re: RDB2RDF Usecase

Hi Ahmed:
I agree that data integration, what you call the silo pain, is a key
usecase for RDB2RDF.
If we could add a data integration usecase to the Recommendation, that
would be great.

Can you write up the usecase more formally? Perhaps something from your
experience.

All the best, Ashok


Ezzat, Ahmed wrote:
> Hello,
> One observation I have is we need to be clearer on Rdb2Rdf for solving
> the silo pain. Rdb2Rdf is a must but not sufficient technology to
> integrate silos. As you need ot reconcile the results from each data
> source together before the data is useful enough to apply SPARQL as an
> example; which is outside the Rdb2Rdf framework.
> Regarding user scenario, I see a lot of value in the Enterprise
> Information Management (EIM) area where you integrate data warehouse
> with content in the enterprise (i.e., not using current technology of
> NLP + converting to XML then shredding elements in the data warehouse
> database columns) to be able to return more actionable information.
> For example, a query to a datawarehouse today can be" "tell me all
> companies that bought $1M equipments last month" ß easy one. Now with
> integration of structured and unstructured data in the enterprise you
> can ask " tell me all companies that bought $1M equipments and had
> complaints?" The point here is customer complaints typically is in
> email content and the list of companies who bough is in the data
> warehouse. By being able to integrate the results of search and SQL at
> high-level as RDF sub-graphs, etc, you can answer the 2^nd question
> transparently w/o manual work.
> In summary, I suggest to position Rdb2Rdf as a core technology that
> would help in solving higher level problems like some of the examples
> in this email thread.
> Regards,
> Ahmed
> /*Ahmed K. Ezzat, Ph.D.*//*
> */*HP Fellow*, *Business Intelligence Software Division
> **Hewlett-Packard Corporation
> *11000 Wolf Road, Bldg 42 Upper, MS 4502, Cupertino, CA 95014-0691*
> **Office*: *Email*: _Ahmed.Ezzat@hp.com_ <mailto:Ahmed.Ezzat@hp.com>
> *Off*: 408-447-6380 *Fax*: 1408796-5427 *Cell*: 408-504-2603
> *Personal*: *Email*: _AhmedEzzat@aol.com_ <mailto:AhmedEzzat@aol.com>
> *Tel*: 408-253-5062 *Fax*: 408-253-6271
>
> ------------------------------------------------------------------------
>

Received on Saturday, 20 December 2008 00:21:47 UTC