15:46:21 RRSAgent has joined #rdb2rdf 15:46:21 logging to http://www.w3.org/2011/08/16-rdb2rdf-irc 15:46:23 RRSAgent, make logs world 15:46:23 Zakim has joined #rdb2rdf 15:46:25 Zakim, this will be 7322733 15:46:25 ok, trackbot; I see SW_RDB2RDF()12:00PM scheduled to start in 14 minutes 15:46:26 Meeting: RDB2RDF Working Group Teleconference 15:46:26 Date: 16 August 2011 15:46:32 Agenda: http://lists.w3.org/Archives/Public/public-rdb2rdf-wg/2011Aug/0114.html 15:46:37 Chair: Michael 15:46:44 scribenick: mhausenblas 15:46:52 RRSAgent, draft minutes 15:46:52 I have made the request to generate http://www.w3.org/2011/08/16-rdb2rdf-minutes.html mhausenblas 15:46:58 RRSAgent, make logs public 15:47:40 present+ Michael 15:48:36 RRSAgent, draft minutes 15:48:37 I have made the request to generate http://www.w3.org/2011/08/16-rdb2rdf-minutes.html mhausenblas 15:54:57 SW_RDB2RDF()12:00PM has now started 15:55:05 + +3539149aaaa 15:55:10 Zakim, aaaa is me 15:55:10 +mhausenblas; got it 15:56:16 privera has joined #RDB2RDF 15:58:50 dmcneil has joined #RDB2RDF 15:59:05 Ashok has joined #rdb2rdf 15:59:19 +dmcneil 15:59:32 present+ David 16:00:33 juansequeda has joined #RDB2RDF 16:00:35 boris has joined #rdb2rdf 16:00:56 present+ Boris 16:01:04 soeren has joined #RDB2RDF 16:01:14 Zakim, boris is with me 16:01:14 +boris; got it 16:01:25 +Ashok_Malhotra 16:01:31 present+ Ashok 16:01:34 cygri_ has joined #rdb2rdf 16:01:42 +ericP 16:01:43 Zakim, cygri is with me 16:01:43 +cygri; got it 16:02:00 present+ Richard 16:02:19 +juansequeda 16:02:31 present+ Juan 16:02:34 +??P5 16:02:48 +OpenLink_Software 16:02:48 nunolopes has joined #RDB2RDF 16:02:49 zakim, ??P5 is soeren 16:02:49 +soeren; got it 16:02:51 zakim, everyone is with mhausenblas 16:02:51 +everyone; got it 16:02:56 Zakim, OpenLink_Software is temporarily me 16:02:56 +MacTed; got it 16:02:58 does anyone else hear the echo? 16:02:58 Zakim, mute me 16:02:58 MacTed should now be muted 16:03:07 present+ Soeren 16:03:09 Zakim, nunolopes is with mhausenblas 16:03:09 +nunolopes; got it 16:03:12 present+ Ted 16:03:16 present+ Nuno 16:03:17 zakim, i'm with mhausenblas 16:03:17 +cygri_; got it 16:03:41 RRSAgent, draft minutes 16:03:41 I have made the request to generate http://www.w3.org/2011/08/16-rdb2rdf-minutes.html mhausenblas 16:04:10 Marcelo has joined #rdb2rdf 16:04:31 Zakim, Marcelo is with me 16:04:31 +Marcelo; got it 16:04:36 present+ Marcelo 16:04:40 Seema has joined #rdb2rdf 16:04:54 present+ Eric 16:06:02 Souri has joined #rdb2rdf 16:06:18 y 16:06:22 +Souri 16:06:28 Zakim, who's noisy? 16:06:35 present+ Souri 16:06:39 MacTed, listening for 10 seconds I heard sound from the following: mhausenblas (84%), ericP (9%) 16:06:46 +Seema 16:06:52 present+ Seema 16:07:28 Topic: Admin 16:07:36 PROPOSAL: Accept the minutes of last meeting http://www.w3.org/2011/08/09-rdb2rdf-minutes.html 16:07:49 +1 16:07:49 +1 16:07:57 RESOLUTION: Accept the minutes of last meeting http://www.w3.org/2011/08/09-rdb2rdf-minutes.html 16:08:10 Topic: Current actions and issue review 16:08:52 ACTION-140? 16:08:52 ACTION-140 -- Boris Villazón-Terrazas to produce an RDF Schema representation of the R2RML vocabulary terms. -- due 2011-08-16 -- OPEN 16:08:52 http://www.w3.org/2001/sw/rdb2rdf/track/actions/140 16:09:02 http://mccarthy.dia.fi.upm.es/rdb2rdf/r2rmlvocab.owl 16:09:25 ACTION-147? 16:09:25 ACTION-147 -- Richard Cyganiak to implement ISSUE-29 resolution by stating that conversion to string is done implicitly in any context where a string value is required, and is done according to the rules for SQL's CAST expression. Columns whose type cannot be CAST to string MUST NOT be used in a context that requires a string; and mark the issue as pending review -- due 2011-08-16 -- OPEN 16:09:25 http://www.w3.org/2001/sw/rdb2rdf/track/actions/147 16:10:03 no clue 16:10:08 ACTION-152? 16:10:08 ACTION-152 -- Juan Sequeda to figure out and solution with Souri to address ISSUE-64 -- due 2011-08-16 -- OPEN 16:10:08 http://www.w3.org/2001/sw/rdb2rdf/track/actions/152 16:10:35 ACTION-153? 16:10:35 ACTION-153 -- Marcelo Arenas to draft a solution for ISSUE-65 and send out to WG -- due 2011-08-16 -- OPEN 16:10:35 http://www.w3.org/2001/sw/rdb2rdf/track/actions/153 16:10:54 privera_ has joined #RDB2RDF 16:11:19 Michael: there was a proposal to close both ISSUES-64 and ISSUE-65? 16:12:24 Juan: Let's close the two actions and discuss the issues later 16:12:30 close ACTION-152 16:12:32 ACTION-152 Figure out and solution with Souri to address ISSUE-64 closed 16:12:32 close ACTION-153 16:12:33 ACTION-153 Draft a solution for ISSUE-65 and send out to WG closed 16:13:00 Topic: ISSUE-64 and ISSUE-65 16:13:16 ISSUE-64? 16:13:16 ISSUE-64 -- Predicate IRI design for foreign key does not handle common cases where same column sequence may be used for multiple foreign key constraints -- open 16:13:16 http://www.w3.org/2001/sw/rdb2rdf/track/issues/64 16:13:17 Zakim, who's noisy? 16:13:18 michael - maybe you could try muting your phone when others are speaking? 16:13:20 ISSUE-65? 16:13:20 ISSUE-65 -- For uniformity and performance, "literal" triples must be always generated for each child table column in a foreign key -- open 16:13:20 http://www.w3.org/2001/sw/rdb2rdf/track/issues/65 16:13:35 MacTed, listening for 11 seconds I heard sound from the following: mhausenblas (26%), ericP (100%) 16:13:37 no that is not better 16:13:52 try muting through Zakim? 16:14:09 PROPOSE to close ISSUE-64 noting that the current DM definition generates triples for all foreign keys even if they are on the same columns 16:14:33 s/PROPOSE/PROPOSAL: 16:14:49 Zakim, mute mhausenblas 16:14:49 mhausenblas should now be muted 16:15:08 the echo stopped 16:15:38 (Eric explains the background on the proposal) 16:16:27 example: Family , Employee , Soccer 16:16:33 Eric: cost re ISSUE-64 are to high and use case is not clear 16:17:02 Juan: agreed 16:17:08 q? 16:17:11 two different properties need to have two different ranges 16:17:40 RRSAgent, draft minutes 16:17:40 I have made the request to generate http://www.w3.org/2011/08/16-rdb2rdf-minutes.html mhausenblas 16:17:40 q+ 16:18:01 q+ to say that that ISSUE-64 is a very minor issue because it's such a small corner case 16:18:13 ack Souri 16:18:35 Souri: fine with me, I thought it's needed for completness 16:18:37 q? 16:18:48 Souri: see my example above 16:19:21 Zakim, unmute me 16:19:21 mhausenblas should no longer be muted 16:19:41 ack cygri 16:19:41 cygri, you wanted to say that that ISSUE-64 is a very minor issue because it's such a small corner case 16:19:48 +q 16:20:13 Richard: would also be possible to say that the 'ugly' but complete URI only generated in case of clash 16:20:41 ack Marcelo 16:20:52 Marcelo: also related with ISSUE-65 16:21:04 ... problem there is in case of FK with one attribute 16:21:19 ... to avoid this we need a different URI 16:21:30 +1 to Marcelo regarding issue with literal property and constraint property 16:21:51 q+ 16:21:54 q+ 16:22:09 q? 16:22:15 ack juansequeda 16:22:37 Juan: should we note the incompleteness in the spec? 16:22:41 q+ 16:22:46 Zakim, unmute me 16:22:46 MacTed should no longer be muted 16:22:49 q? 16:22:50 +1 to cygri's propsal 16:22:55 ack Souri 16:23:08 Zakim, mute mhausenblas 16:23:08 mhausenblas should now be muted 16:23:12 Souri: re ISSUE-65 ... as Marcelo says 16:23:17 q? 16:23:31 zakim, mute mhausenblas 16:23:31 mhausenblas was already muted, cygri 16:23:43 zakim, who is noisy? 16:23:53 cygri, listening for 10 seconds I heard sound from the following: MacTed (49%) 16:24:06 Zakim, unmute me 16:24:06 mhausenblas should no longer be muted 16:24:09 q+ to say that the current spec only generates a reference triple for what would be the ambiguous cases 16:24:43 q? 16:24:49 PROPOSAL: close ISSUE-64 by adding a note to the spec stating, "if multiple FKs are defined on the same sequence of columns, then the same property IRI will be used" 16:25:25 ack MacTed 16:25:34 Zakim, mute mhausenblas 16:25:34 mhausenblas should now be muted 16:25:49 -1 to ISSUE-64 proposal because it causes confusion for ISSUE-65 16:26:10 Michael: Noted, Souri, but this doesn't help me ... 16:26:42 scribe confused, doesn't understand what Ted is talking about 16:26:52 Zakim, unmute me 16:26:52 mhausenblas should no longer be muted 16:26:56 q? 16:26:58 q+ 16:27:09 ack ericP 16:27:09 ericP, you wanted to say that the current spec only generates a reference triple for what would be the ambiguous cases 16:27:17 Zakim, mute mhausenblas 16:27:17 mhausenblas should now be muted 16:27:58 Michael: I think Richard has a point, let's try 65 first 16:28:08 q? 16:28:09 +1 to address 65 first 16:28:26 Zakim, unmute me 16:28:26 mhausenblas should no longer be muted 16:28:55 Topic: ISSUE-65 16:28:56 the whole idea of having different approach for single-col fkey and multi-col fkey seems confusing 16:29:08 q+ 16:29:11 q? 16:29:14 ack Souri 16:29:36 ack cygri 16:30:06 Richard: Agree with Souri re current design is a bit confusing 16:30:35 q? 16:30:41 RRSAgent, draft minutes 16:30:41 I have made the request to generate http://www.w3.org/2011/08/16-rdb2rdf-minutes.html mhausenblas 16:30:50 ISSUE-65? 16:30:50 ISSUE-65 -- For uniformity and performance, "literal" triples must be always generated for each child table column in a foreign key -- open 16:30:50 http://www.w3.org/2001/sw/rdb2rdf/track/issues/65 16:31:34 Richard: if we had a way to distinguish FK from literal this would be easier 16:31:44 q? 16:31:54 privera has joined #RDB2RDF 16:31:55 +1 to Richard's non-concrete proposal: put a prefix say "fkey" 16:32:21 q+ 16:32:28 ack Souri 16:32:36 Souri: Agree with Richard 16:32:37 q? 16:32:45 Zakim, mute me 16:32:45 mhausenblas should now be muted 16:32:48 Zakim, mute me 16:32:48 MacTed should now be muted 16:33:10 Souri: as long as we can distinguish the two cases 16:33:25 Juan: So, what you want is XXX 16:33:43 fkey/f,n 16:33:55 Zakim, unmute me 16:33:55 mhausenblas should no longer be muted 16:34:08 Juan: So, what you want to know through the IRI if it represents a literal or foreign key 16:34:11 Souri: yes 16:35:03 absolutely agree with Richard: we need to distinguish between literal (data) property and fkey (object) property 16:36:58 i think anything we come up with would look like: 16:36:59 7 . 16:36:59 "Bob" . 16:36:59 18 . 16:36:59 . 16:37:07 note the L or R 16:37:22 cygri_ has joined #rdb2rdf 16:37:47 i also think these will be worse warts than is the unary foreign key exception 16:37:47 +mhausenblas.a 16:37:52 ericP: that works... but it's kind of a hack 16:37:55 zakim, mhausenblas.a is me 16:37:55 +cygri; got it 16:38:04 Michael: DM Editors propose solution for ISSUE-64 and ISSUE-65 after the call today and send to list (Richard to comment on) 16:38:27 Topic: ISSUE-48 16:38:33 ISSUE-48? 16:38:33 ISSUE-48 -- Mapping SQL datatypes to RDF -- open 16:38:33 http://www.w3.org/2001/sw/rdb2rdf/track/issues/48 16:38:34 juansequeda, agreed. but i think there's no avoiding it if we want to keep the namespaces (for e.g. the People properties) sane 16:38:49 Michael: Got everything you need? 16:38:51 Richard: yes 16:39:16 "Bob" . 16:39:17 . 16:39:17 rdf:type owl:DatatypeProperty 16:39:17 rdf:type owl:ObjectProperty 16:39:17 where anything that is an owl:DatatypeProperty is for literals and anything that is owl:ObjectProperty is for foreign keys 16:39:19 eric what would be the syntax for 2-col key: ? 16:39:54 Richard: will send out proposal in the next couple of days 16:40:05 Topic: ISSUE-57 16:40:09 ISSUE-57? 16:40:09 ISSUE-57 -- R2RML doesn't allow R2RML documents in RDF/XML syntax -- open 16:40:09 http://www.w3.org/2001/sw/rdb2rdf/track/issues/57 16:40:28 q+ 16:40:32 ack Souri 16:40:39 zakim, mute mhausenblas 16:40:39 mhausenblas should now be muted 16:40:52 Souri: We will not object now 16:40:56 q+ 16:41:02 ack cygri 16:41:26 Richard: two ways how to look at it 16:41:52 ... either not discuss it now and have a second LC or resolve it now 16:42:18 Richard: Would be good to resolve it before LC 16:42:37 ... what I don't understand is why the objection is here in the first place 16:42:46 q+ 16:43:08 ack Souri 16:44:21 Souri: It's more about document structure 16:44:36 scribe unsure if this is capture correctly 16:44:57 Souri: better would be two split this 16:45:08 ... into vocab and serialisation 16:45:09 q+ 16:45:16 Zakim, unmute me 16:45:16 mhausenblas should no longer be muted 16:45:21 q? 16:45:34 mhausenblas, please mute yourself and come over here 16:45:39 your phone is broken 16:45:44 Souri: people should have an option 16:45:49 Zakim, mute me 16:45:49 mhausenblas should now be muted 16:46:14 Zakim, unmute me 16:46:14 mhausenblas should no longer be muted 16:46:17 q? 16:46:25 zakim, mute mhausenblas 16:46:25 mhausenblas should now be muted 16:46:31 mhausenblas, your phone is broken 16:46:36 Zakim, unmute me 16:46:36 mhausenblas should no longer be muted 16:46:36 come over here 16:47:09 q+ 16:47:17 ack Souri 16:47:42 Michael: we can do this but then 1 Sep is not an option 16:47:46 ack Souri 16:47:49 ack me 16:48:44 q+ 16:48:48 q? 16:49:07 ack cygri 16:49:15 Zakim, mute me 16:49:15 mhausenblas should now be muted 16:49:40 Richard: I understand this (re modularity) but we have two competing design goals 16:49:49 ... interop vs. flexibility 16:50:01 Souri: it's just an option 16:50:22 q+ 16:50:53 Michael: For the record - I'd rather step down as a co-chair than loosing the most important aspect of a standard: interoperability 16:50:53 q+ 16:50:57 q? 16:51:09 ack juansequeda 16:51:39 Richard: not very compelling to me 16:52:24 Juan: IIUC then you can reuse existing ontology editors 16:52:28 q? 16:52:32 q+ 16:52:49 Souri: vocab is the important part 16:53:11 Juan: so R2RML is just a vocab? 16:53:15 ack Ashok 16:54:03 Juan: quite late in the game, this issue, isn't it? 16:54:18 Souri: it's not too late, it's simple to write 16:54:20 q? 16:54:43 Zakim, unmute me 16:54:43 mhausenblas should no longer be muted 16:54:54 Zakim, mute me 16:54:54 mhausenblas should now be muted 16:55:17 Ashok: are people open for a compromise - replace the MUST with a SHOULD? 16:55:25 Richard: 16:55:48 Richard: It depends ... the spec defines several conformance criteria 16:55:56 ... processor, doc, graph 16:56:12 q? 16:56:42 Richard: I'm happy to say nothing at all for the processor 16:56:53 ... but doc MUST be Turtle 16:56:58 Michael: I agree 16:57:03 q- 16:57:05 q? 16:57:24 right now, an R2RML doesn't need an XML processor 16:57:32 Document conforming to R2RML vocab vs. Document conforming to R2RML vocab using Turtle syntax 16:58:11 q+ 16:58:24 Zakim, unmute me 16:58:24 mhausenblas should no longer be muted 16:58:33 +1 to cygry's terminology separation 16:58:51 MUST accept R2RML graph, SHOULD accept Turtle, MAY accept other serializations... ? 16:58:51 Two-level Recommedations: 1) Vocab only 2) Vocab + Turtle 16:59:07 Souri, don't we alrady have that? 16:59:25 s/Recommedations/Recommendations/ 16:59:27 (with Richard's wording?) 16:59:32 ericP, not quite. a processor currently MUST support turtle 16:59:56 Michael: I want to ensure interoperability 17:00:13 q+ 17:00:15 ahh, R2RML is an a mapping graph expressed in Turtle? 17:00:28 ericP, what do you mean by "R2RML"? 17:00:32 ack cygri 17:00:40 Zakim, mute me 17:00:40 mhausenblas should now be muted 17:01:04 Richard: Seems there is no consensus ATM 17:01:17 ... will likely not be resolved in the next two weeks 17:01:32 ... that means more feedback from WG-external 17:01:39 RFC-standard "SHOULD accept Turtle" means "do it unless there's a damn good reason not to" ... which it seems to me assures interop 17:01:44 q+ 17:01:47 Michael: Then we need to go for a 2nd LC 17:01:54 I still do not see anything wrong with Two-level Recommedations: 1) Vocab only 2) Vocab + Turtle. If most implementers and mapping writers want Turtle, they will go with the 2nd. 17:01:57 ack ericP 17:02:25 Eric explains options 17:02:47 seems that we can offer two options and resolve post-LC 17:03:01 Michael: can you render a proposal for this now 17:03:16 +1 agree with Eric: breaking up a Rec into two Recs is not a big deal 17:03:23 Michael: sounds good to me 17:03:52 Michael: can anyone create a proposal PLEASE 17:04:33 PROPOSAL: close ISSUE-57 with rendering the options in R2RML 17:04:39 Zakim, unmute me 17:04:39 mhausenblas should no longer be muted 17:04:40 q+ 17:04:49 q- 17:05:31 We have to decide: SHOULD ... Turtle vs. MUST ... Turtle 17:05:38 as Ashok said 17:06:19 -Souri 17:06:20 -dmcneil 17:06:22 -Seema 17:06:25 -cygri 17:06:25 Mark Issue 57 in the document as requiring community feedback 17:06:27 -soeren 17:06:38 ,]... and enumerate the options 17:06:55 s/.]// 17:07:06 [adjourned] 17:07:16 -Ashok_Malhotra 17:07:21 -mhausenblas 17:07:35 RRSAgent, draft minutes 17:07:35 I have made the request to generate http://www.w3.org/2011/08/16-rdb2rdf-minutes.html mhausenblas 17:07:42 cygri_ has joined #rdb2rdf 17:07:53 +cygri 17:08:08 zakim, cygri is Marcelo 17:08:08 +Marcelo; got it 17:09:25 nunolopes has joined #RDB2RDF 17:09:44 trackbot, end telecon 17:09:44 Zakim, list attendees 17:09:44 As of this point the attendees have been +3539149aaaa, mhausenblas, dmcneil, boris, Ashok_Malhotra, ericP, juansequeda, soeren, everyone, MacTed, nunolopes, cygri_, Marcelo, Souri, 17:09:45 RRSAgent, please draft minutes 17:09:45 I have made the request to generate http://www.w3.org/2011/08/16-rdb2rdf-minutes.html trackbot 17:09:46 RRSAgent, bye 17:09:46 I see no action items 17:09:47 ... Seema