W3C

- DRAFT -

RDB2RDF Telcon Minutes, Sept 19, 2008

19 Sep 2008

See also: IRC log

Attendees

Present
Soeren Auer, Andrew Eisenberg, Orri Erling, Jenny Green, Ashok Malhotra, Ivan Mikhailov, Axel Polleres, Juan Sequeda
Regrets
Davide Palmisano, Wolfgang Halb, Michael Hausenblas
Chair
Ashok
Scribe
soeren

Contents


 

 

<Ashok> scribenick: soeren

<Ashok> scribe Soeren Auer

Approval of Minutes

No objections to approving minutes from Sept 12. Minutes approved.

XG Logistics

Oct 30/31 will be f2f organized by Wolfgang

Wolfgang said he would send more information

No phone calls for next two weeks and no call 17th and 24th of Oct. Next call Oct 10.

Action Items

Jenny Green provided interesting use case scenario

Orri updated RDB2RDF requirements

<juansequeda> This is the link from Orri's updated requirement document: http://esw.w3.org/topic/Rdb2RdfXG/ReqForMappingByOErling

Discussion about Orri's requirements document

Orri gives an introduction

better definition of the scope of the requirements document

addition of usages scenarios

esp. with regard to mapping on demand

some kind of basic inferencing is required

e.g. when the same triples can be derived from different sources

properties of mapping functions (injective, bijective etc) must be known by the mapping layer

virtuoso provides some of the functionality already

question from Ashok about Simplicity

How can that be achieved?

Orri answers: maybe by two language layers.

often only few simple things are required

Soeren: why not use SQL as a mapping language?

<Ashok> Ashok: You can define a SQL query for each OWL class

Orri will collect some examples of thnigs which are not easily expressible in SQL.

<Ashok> Jenny: If you limit mapping to SQL you n only solve problems that SQL can solve

Limitation to SQL -- can only problems that SQL can solve.

Ashok: benefit of translating from RDB to RDF is integration of data, but the real value is when you can add extra semantic

Ivan: SPARQL is easier and simpler to write than large SQL queries

Jenny presents her use case:

create a demonstrator that takes spatial operations into account in RDF

5 different data sources from different companies

questionnaires and knowledge elicitation techniques employed to create the data

creation of ontologies for the datasources

now merging of the ontologies and data sources

spatial attributes hae to be considered

SQUIRREL used for linking

starting point are SPARQL queries

one big table for polygons

seven different conditions define what is a field, many different constraints on the metadata

use of Oracle spatial operations

D2RQ used for mapping

no change of underlying data

sometimes preprocessing required

Orri: interesting use-case

Ashok: Excellent use case since it speaks about data from multiple DBs and allows addition of semantics

Winding Up

One more phone call till F2F

10th of October

continuing discussion of Orri's requirements and Jenny's use case

in the next conf. call

Orri promises additions till next call

Ashok, please continue discussion by emaily

<Ashok> Adjourn

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.133 (CVS log)
$Date: 2008/09/19 15:58:16 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.133  of Date: 2008/01/18 18:48:51  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found ScribeNick: soeren
Inferring Scribes: soeren

WARNING: No "Topic:" lines found.


WARNING: No "Present: ... " found!
Possibly Present: Andre1 Ashok AxelPolleres Ivan Jenny Orri Soeren iv_an_ru_ juansequeda scribenick
You can indicate people for the Present list like this:
        <dbooth> Present: dbooth jonathan mary
        <dbooth> Present+ amy

Got date from IRC log name: 19 Sep 2008
Guessing minutes URL: http://www.w3.org/2008/09/19-RDB2RDF-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report


[End of scribe.perl diagnostic output]