W3C

- DRAFT -

RDB2RDF

26 Jul 2011

See also: IRC log

Attendees

Present
Ashok_Malhotra, +3539149aaaa, EricP, mhausenblas, +1.781.273.aabb, MacTed, nunolopes, +1.562.249.aacc, boris, +575737aadd, juansequeda, Marcelo, cygri, +1.603.897.aaee, Souri, +1.603.897.aaff, Seema, Ashok, Eric, Boris, Juan, Michael, Nuno, Ted, Richard
Regrets
Ivan
Chair
Ashok
Scribe
Ashok

Contents


<mhausenblas> nunolopes is with me

<mhausenblas> rrs

<mhausenblas> Chair: Michael

<mhausenblas> scribenick: Ashok

<scribe> scribe: Ashok

<MacTed> :-)

Approve minutes of July 19 meeting: http://www.w3.org/2011/07/19-rdb2rdf-minutes.html

RESOLUTION: Minutes for July 19 are approved

Issue of the day ISSUE-7

<mhausenblas> ISSUE-7?

<trackbot> ISSUE-7 -- Linked Data aspects for mapping RDB2RDF -- open

<trackbot> http://www.w3.org/2001/sw/rdb2rdf/track/issues/7

<cygri> http://lists.w3.org/Archives/Public/public-rdb2rdf-wg/2011Jul/0118.html

<cygri> PROPOSAL: The WG is of the opinion that the charter's requirement to support the linked data principles is adequately addressed by the Direct Mapping and R2RML, with the caveat that ISSUE-43 is not yet resolved. No further action is required beyond resolving ISSUE-43. This closes ISSUE-7.

<mhausenblas> juansequeda, problems?

<ericP> second

<cygri> +1 to closing ISSUE-7

<cygri> +2 to closing ISSUE-7

<Souri> +1

<boris> +1

<Seema> +1

RESOLUTION: ISSUE-7 is resolved as R2RML provides facilities to create URIs for database entities

<mhausenblas> PROPOSAL: The WG is of the opinion that the charter's requirement to support the linked data principles is adequately addressed by the Direct Mapping and R2RML, with the caveat that ISSUE-43 is not yet resolved. No further action is required beyond resolving ISSUE-43. This closes ISSUE-7.

<MacTed> Direct Mapping *also* allows for URI creation.

<cygri> ISSUE-43?

<trackbot> ISSUE-43 -- Re-using public entity identifiers -- open

<trackbot> http://www.w3.org/2001/sw/rdb2rdf/track/issues/43

<juansequeda> +q to say that the way URIs are created in R2RML and DM satisfy the Linked Data issue

<MacTed> PROPOSAL: The WG is of the opinion that the charter's requirement to support the linked data principles is adequately addressed by the Direct Mapping and R2RML, as each allow for creation of URIs for database entities, with the caveat that ISSUE-43 is not yet resolved. No further action is required beyond resolving ISSUE-43. This closes ISSUE-7.

<cygri> +1 to MacTed

<juansequeda> +1 to MacTed

<Souri> +1 to MacTed's proposal

RESOLUTION: The WG is of the opinion that the charter's requirement to support the linked data principles is adequately addressed by the Direct Mapping and R2RML, as each allow for creation of URIs for database entities, with the caveat that ISSUE-43 is not yet resolved. No further action is required beyond resolving ISSUE-43. This closes ISSUE-7.
... ISSUE-7 is resolved with the proposal: The WG is of the opinion that the charter's requirement to support the linked data principles is adequately addressed by the Direct Mapping and R2RML, as each allow for creation of URIs for database entities, with the caveat that ISSUE-43 is not yet resolved. No further action is required beyond resolving ISSUE-43. This closes ISSUE-7.

<MacTed> issue-43?

<trackbot> Sorry... I don't know anything about this channel

<mhausenblas> ISSUE-43?

<trackbot> ISSUE-43 -- Re-using public entity identifiers -- open

<trackbot> http://www.w3.org/2001/sw/rdb2rdf/track/issues/43

<mhausenblas> http://www.w3.org/2001/sw/rdb2rdf/wiki/Identifier_re-use

<ericP> i'd say we need 3 things to do an adequate job of supporting LD: algorithmic construction of graph shapes, algorithmic construction of entity identifiers, entity construction through lookup table

Richard: Two cases: use lookup table or use function

Michael: Asks about details of implementation

<mhausenblas> Michael: How long would it take

Ted: charter says "will encourage" ...
... make it possible or easy to use well-known identifiers

<mhausenblas> Richard: lookup table is some hours work, use function dunno (in D2R it's a Java class)

<Souri> we could use owl:sameAs (requires entailment) if the values to be mapped are all IRIs

MacTed: No proposal so close with no action

Juan: can we push to next version. My proposal is to postpone

Richard: We have to adhere to the charter

<MacTed> charter says "encourage". "encourage" means "suggest strongly" or "make easy".

<MacTed> R2RML makes mapping well-known-URI to DB-specific-URI, or well-known-URI to DB-entity, possible. is that enough?

Michael: Not a MUST requirement
... essentially postpone the use function

<mhausenblas> http://www.w3.org/TR/2010/WD-rdb2rdf-ucr-20100608/#GUIDGEN

Michael: Argues that we do not have to do anything
... Trade off between time and functionality

Richard: Look up table would be a new feature in the language

<mhausenblas> PROPOSAL: Split ISSUE-43 into two: look-up table and XXX, do first now, postpone second

Richard: other SQL features are, of course, available

<Souri> It has to be bijective (1-to-1)

<cygri> PROPOSAL: Split ISSUE-43 into two: 1. add lookup table feature to R2RML (similar to existing D2RQ feature); 2. call to external function/service. Do 1 now, postpone 2.

Michael: Look-up table is low-hanging fruit ... we could do it quickly

<cygri> (D2RQ lookup tables are described here: http://www.w3.org/2001/sw/rdb2rdf/wiki/Entity_disambiguation#Mapping_tables_in_D2RQ )

Souri: Lookup table has to be bijective with constraints on the type

Michael: Just trying to solve the issue quickly

<mhausenblas> PROPOSAL: Postpone ISSUE-43

<Souri> I would say, we will evaluate if part 1 can be done now

Ashok: I vote to postpone entire issue

<MacTed> +1 postpone ISSUE-43

<MacTed> I agree -- lookup table is harder than it looks.

<cygri> -1

<MacTed> (may easily and immediately grow well beyond "unwieldy")

<ericP> how much functionality do we get with a special lookup table than we do implementing it in the SQL view?

<cygri> PROPOSAL: Split ISSUE-43 into two: 1. add lookup table feature to R2RML (similar to existing D2RQ feature); 2. call to external function/service. Postpone 2.

<Souri> I am okay with evaluating it, but be ready to postpone it if we find it difficult

<mhausenblas> +1

<nunolopes> +1

<MacTed> +1 split and immediately postpone part 2

<Souri> +1

<boris> +1

<juansequeda> +`1

RESOLUTION: ISSUE-43 into two: 1. add lookup table feature to R2RML (similar to existing D2RQ feature); 2. call to external function/service. Postpone 2.

<juansequeda> +1

<mhausenblas> ACTION: Hausenblas to implement resolution re ISSUE-43 [recorded in http://www.w3.org/2011/07/26-rdb2rdf-minutes.html#action01]

<trackbot> Created ACTION-148 - Implement resolution re ISSUE-43 [on Michael Hausenblas - due 2011-08-02].

ISSUE-40

<mhausenblas> s/Topic: ISSUE-40/Topic: Direct Mapping

Juan: I have been working on this
... I also have to write the note on NULLs
... I will send mail

Michael: The NULLs note is not on the REC track. No rush on that.

Discussion on alternate approaches to describing DM

Marcelo: I think we should keep both

Eric: Can we test the rules?

Richard: If we have 2 normative descriptions I will object
... if we have one normative and the other is a re-phrasing, that's ok

Michael: We need to postpone this discussion ... out of time

<boris> I think editors should reach an agreement on that

<mhausenblas> [adjourned]

Summary of Action Items

[NEW] ACTION: Hausenblas to implement resolution re ISSUE-43 [recorded in http://www.w3.org/2011/07/26-rdb2rdf-minutes.html#action01]
 
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.136 (CVS log)
$Date: 2011/07/26 17:20:22 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.136  of Date: 2011/05/12 12:01:43  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/ISSUE-7 is resolved with MacTed proposal above/The WG is of the opinion that the charter's requirement to support the linked data principles is adequately addressed by the Direct Mapping and R2RML, as each allow for creation of URIs for database entities, with the caveat that ISSUE-43 is not yet resolved. No further action is required beyond resolving ISSUE-43. This closes ISSUE-7./
Succeeded: s/thet/that/
FAILED: s/Topic: ISSUE-40/Topic: Direct Mapping/
Succeeded: s/wrote/write/
Succeeded: s/rules/rules?/
Succeeded: s/posypone/postpone/
Found ScribeNick: Ashok
Found Scribe: Ashok
Inferring ScribeNick: Ashok
Default Present: Ashok_Malhotra, +3539149aaaa, EricP, mhausenblas, +1.781.273.aabb, MacTed, nunolopes, +1.562.249.aacc, boris, +575737aadd, juansequeda, Marcelo, cygri, +1.603.897.aaee, Souri, +1.603.897.aaff, Seema
Present: Ashok_Malhotra +3539149aaaa EricP mhausenblas +1.781.273.aabb MacTed nunolopes +1.562.249.aacc boris +575737aadd juansequeda Marcelo cygri +1.603.897.aaee Souri +1.603.897.aaff Seema Ashok Eric Boris Juan Michael Nuno Ted Richard
Regrets: Ivan
Got date from IRC log name: 26 Jul 2011
Guessing minutes URL: http://www.w3.org/2011/07/26-rdb2rdf-minutes.html
People with action items: hausenblas

[End of scribe.perl diagnostic output]