W3C

- DRAFT -

SV_MEETING_TITLE

13 Jun 2008

See also: IRC log

Attendees

Present
Andrew_Eisenberg, +1.509.771.aaaa, Ashok_Malhotra, +1.408.285.aabb, +1.857.362.aacc, +039320463aadd, [Microsoft]
Regrets
Chair
Ashok
Scribe
joebetz

Contents


 

 

<Ashok> meeting RDB2RDF

<Ashok> scribenick: joebetz

<Ashok> RESOLUTION: Telcon on July 4 is cancelled

actions:

notes from invormal meeting at ESWC:

Integration between databases using globally unique identifiers

Can we agree on common identifiers to be used across the web?

<Ashok> AShok: Are the identifiers URIs?

<Ashok> Themis: may not be

<Ashok> Jenny Green: This may be an output from the groups -- DB identifiers vs. RDF identifiers

Ashok: globally unique identifiers should be URIs since this is a w3c activity

there is a sub group of which identifiers should be associated with different domains (e.g. LSIDs)

<Ashok> Themis: OCCAM will create a facility to create global identifiers

Themis: Can distribute paper with general idea/architecture.

Catherine: Discussed importance of figuring out what we are going to standardize at ESWC.

Jenny: Do we want to limit ourselves to RDF or do we want to include OWL, etc?

Ashok: Yes, we should think about OWL.

Jenny: Might be good to start thinking about a name (i.e not RDB2RDF)

Another potential approach, company?

Ashok, what should we deliver? Background: this group will not write a standard, we can produce papers, surveys, and can recommend that W3C start a working group to standardize something.

Final report in Feb.

We should report a summary, currently this is a wiki, can we convert this?

Orri: submit this as a report
... take wiki and convert this to a paper, all members add to it
... submit this to conf, what was the name?
... Generate more interest, create more discussions if we submit.

Ashok: we should at least write the outlines of a working group charter?
... we can do this in two directions, we can start w/ schema and write RDF. We can also start with ontology that does not precisely match data.

Jenny: Might be best to start with saying what needs to be in the mapping rather than recommending a language.
... Start with requirements, and decide best approach from requirements.

Ashok: approach should both directions: RDB->RDF/OWL, OWL->Mapping, and we should work from requirements? Agreed.
... Update logs might be useful, but there is no sparql update language now. Ideas out there are Andy's Sparql/Update, there is another. Is update something we should examine?

Keeping search indexes up-to-date, for example, would benefit from update notifications.

(above is Soren)

Soren: Has idea of what updates might look like.

Update notifications are not specific to RDB or mapping.

Andrew: Should be careful to keep group focused. While update logs are useful we might recommend for different working group to stay focused.

Ashok: Topic: Translating SPARQL to SQL. If data is in database, translate SPARQ to SQL. Should we standardize?
... Standardize the algorithm that is. Concensus seems to be no.

Andrew: Groups can produce artifacts as well, we could produce an applet or open source code to demonstrate translation.
... Would be specific to mapping the group produces.

Jenny: We may not always not want to map to SQL.
... Services or other intermediate layers might be between DB and SPARQL, might not want to target SQL specifically.

Ashok: Will send out summary, request comments
... Presentation next week: RDB to ontology
... Think about how we get started? Volunteers are welcome to take on topics.

Orri: Try to prepare wiki page

Linked data planet next tues, weds, Attendees want to meet?

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.133 (CVS log)
$Date: 2008/06/13 16:01:15 $

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: joebetz
Inferring Scribes: joebetz

WARNING: No "Topic:" lines found.

Default Present: Andrew_Eisenberg, +1.509.771.aaaa, Ashok_Malhotra, +1.408.285.aabb, +1.857.362.aacc, +039320463aadd, [Microsoft]
Present: Andrew_Eisenberg +1.509.771.aaaa Ashok_Malhotra +1.408.285.aabb +1.857.362.aacc +039320463aadd [Microsoft]

WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting

Got date from IRC log name: 13 Jun 2008
Guessing minutes URL: http://www.w3.org/2008/06/13-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]