15:46:03 RRSAgent has joined #RDB2RDF 15:46:03 logging to http://www.w3.org/2012/05/01-RDB2RDF-irc 15:46:05 RRSAgent, make logs world 15:46:05 Zakim has joined #RDB2RDF 15:46:07 Zakim, this will be 7322733 15:46:07 ok, trackbot; I see SW_RDB2RDF()12:00PM scheduled to start in 14 minutes 15:46:08 Meeting: RDB2RDF Working Group Teleconference 15:46:08 Date: 01 May 2012 15:46:22 Agenda: http://lists.w3.org/Archives/Public/public-rdb2rdf-wg/2012May/0001.html 15:46:59 Chair: Michael 15:47:08 regrets+ Joerg 15:47:14 present+ Michael 15:47:22 RRSAgent, draft minutes 15:47:22 I have made the request to generate http://www.w3.org/2012/05/01-RDB2RDF-minutes.html mhausenblas 15:47:33 RRSAgent, make logs public 15:55:44 Ashok has joined #rdb2rdf 15:57:58 Sure! 15:58:07 Thanks! 15:58:13 scribenick: Ashok 15:59:05 zakim, code? 15:59:05 the conference code is 7322733 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), Ashok 15:59:18 SW_RDB2RDF()12:00PM has now started 15:59:25 +Ashok_Malhotra 15:59:29 +mhausenblas 15:59:41 present+ Ashok 16:00:27 ivan has joined #rdb2rdf 16:00:49 +OpenLink_Software 16:00:54 zakim, i'm with mhausenblas 16:00:54 +cygri; got it 16:00:58 present+ Ted 16:01:01 Zakim, OpenLink_Software is temporarily me 16:01:01 +MacTed; got it 16:01:02 dmcneil has joined #RDB2RDF 16:01:05 Zakim, mute me 16:01:05 MacTed should now be muted 16:01:06 present+ Richard 16:01:29 RRSAgent, draft minutes 16:01:29 I have made the request to generate http://www.w3.org/2012/05/01-RDB2RDF-minutes.html mhausenblas 16:01:29 +dmcneil 16:01:38 present+ David 16:01:52 zakim, dial ivan-voip 16:01:52 ok, ivan; the call is being made 16:01:54 +Ivan 16:02:02 zakim, nuno is with mhausenblas 16:02:02 +nuno; got it 16:02:10 -Ivan 16:02:19 present+ Nuno 16:02:23 nunolopes has joined #rdb2rdf 16:02:31 zakim, nunolopes is with mhausenblas 16:02:31 +nunolopes; got it 16:02:53 Souri has joined #rdb2rdf 16:03:23 +Souri 16:03:32 present+ Souri 16:03:46 juansequeda has joined #rdb2rdf 16:03:54 Seema has joined #rdb2rdf 16:04:22 +juansequeda 16:04:28 present+ Juan 16:05:29 Topic: Minutes of Last Meeting 16:05:32 ROPOSAL: Accept the minutes of last meeting http://www.w3.org/2012/04/24-RDB2RDF-minutes.html 16:05:50 s/ROPOSAL/PROPOSAL 16:05:53 +1 16:06:13 Minutes acceptes without objection 16:06:21 Topic: Fixing an omission in R2RML: syntax of blank node labels 16:06:51 RRSAgent, draft minutes 16:06:51 I have made the request to generate http://www.w3.org/2012/05/01-RDB2RDF-minutes.html mhausenblas 16:06:59 zakim, dial ivan-home 16:06:59 ok, ivan; the call is being made 16:07:01 +Ivan 16:07:57 +seema 16:08:05 present+ Seema 16:08:11 PROPOSAL: Change Section 11.2 of R2RML http://www.w3.org/TR/2012/CR-r2rml-20120223/#generated-rdf-term) from: 16:08:12 [[ 16:08:13 If the term type is rr:BlankNode: Return a blank node whose blank node identifier is the natural RDF lexical form corresponding to value. 16:08:15 ]] 16:08:16 to: 16:08:18 [[ 16:08:19 If the term type is rr:BlankNode: Return a blank node that is unique to the natural RDF lexical form corresponding to value. 16:08:20 NOTE: RDF syntaxes and RDF APIs generally represent blank nodes with blank node identifiers. But the characters allowed in blank node identifiers differ between syntaxes, and not all characters occurring in value may be allowed, so a bijective mapping function from values to valid blank node identifiers may be required. The details of this mapping function are implementation-dependent, and an R2RML processors may have to use different functions for 16:08:23 different output syntaxes or access interfaces. Strings matching the regular expression [a-zA-Z_][a-zA-Z_0-9-]* are valid blank node identifiers in all W3C-recommended RDF syntaxes. 16:08:26 ]] 16:08:42 +q 16:08:52 ack dmcneil 16:08:59 q+ 16:09:03 q? 16:09:25 Topic: Fixing an omission in R2RML: syntax of blank node labels 16:10:37 present+ Ivan 16:12:30 ack Ashok 16:14:55 q? 16:14:56 +1 16:14:58 RESOLUTION: Proposal accepted without change 16:15:01 1 16:15:18 Topic: Using non-existing column in mapping 16:15:33 Topic: Using non-existing column in mapping http://lists.w3.org/Archives/Public/public-rdb2rdf-wg/2012Apr/0018.html 16:15:36 Section 6 of the R2RML spec (http://www.w3.org/TR/2012/CR-r2rml-20120223/#triples-map) states: 16:15:36 [[ 16:15:38 The referenced columns of all term maps of a triples map (subject map, predicate maps, object maps, graph maps) MUST be column names that exist in the term map's logical table. 16:15:39 ]] 16:15:41 PROPOSAL: Any referenced columns (that is, the columns mentioned in rr:column, rr:template, etc.) that don't exist in the rr:sqlQuery or table are treated simply as being NULL, rather than being considered an error. Perhaps the case could still be treated as a warning: 16:15:42 [[ 16:15:43 Processors MAY warn mapping authors if a referenced column does not exist in the logical table. 16:15:44 ]] 16:16:57 I'd prefer SHOULD to MAY 16:17:27 +1 to MacTed's comment 16:17:38 -1 (prefer error over warning -- returning wrong value from a query could be disastrous) 16:18:15 SHOULD warn, MAY error? 16:19:11 PROPOSAL: Any referenced columns (that is, the columns mentioned in rr:column, rr:template, etc.) that don't exist in the rr:sqlQuery or table are treated simply as being NULL, rather than being considered a warning. Processors SHOULD warn mapping authors if a referenced column does not exist in the logical table. 16:20:12 Zakim, unmute me 16:20:12 MacTed should no longer be muted 16:21:04 PROPOSAL: Any referenced columns (that is, the columns mentioned in rr:column, rr:template, etc.) that don't exist in the rr:sqlQuery or table are treated simply as being NULL, rather than being considered a warning. Processors SHOULD error, MAY warn mapping authors if a referenced column does not exist in the logical table. 16:23:15 q? 16:23:37 +q 16:24:41 PROPOSAL: Processors SHOULD error if any referenced columns (that is, the columns mentioned in rr:column, rr:template, etc.) don't exist in the rr:sqlQuery or table. Processors MAY treat such as NULL but if so, SHOULD return a warning to mapping authors. 16:25:17 q? 16:25:33 ack dmcneil 16:26:11 +EricP 16:26:21 +1 to David's comment 16:26:22 present+ Eric 16:26:42 s/such/such columns/ 16:29:53 Ashok++ 16:30:32 What exactly was the earlier statement about it? 16:30:45 Can't we just choose one? 16:31:16 PROPOSAL: Processors MUST error if any referenced columns (that is, the columns mentioned in rr:column, rr:template, etc.) don't exist in the rr:sqlQuery or table. 16:31:29 +0 from me (as long as earlier statement said "error" is the norm) 16:31:59 WG decided not to change the spec in this regard 16:32:27 RESOLUTION: WG decided not to change the spec in this regard 16:32:36 Topic: Unnamed columns in rr:sqlQuery 16:32:43 Section 5.2 of the R2RML spec (http://www.w3.org/TR/2012/CR-r2rml-20120223/#r2rml-views) states: 16:32:44 [[ 16:32:45 Any columns in the SELECT list derived by projecting an expression MUST be named. 16:32:47 ]] 16:32:48 PROPOSAL: Above to be replaced with an informative note: 16:32:50 [[ 16:32:51 Note: Any columns in the SELECT list derived by projecting an expression should be explicitly named because otherwise they cannot be referenced in the rest of the mapping. 16:32:51 ]] 16:33:09 Topic: Unnamed columns in rr:sqlQuery http://lists.w3.org/Archives/Public/public-rdb2rdf-wg/2012Apr/0017.html 16:33:12 +1 16:33:26 +1 16:33:42 do we need to add "unique" ? 16:36:09 Any columns in the SELECT list derived by projecting an expression MUS be explicitly named for those column names to be referenced in the rest of the mapping. 16:36:23 s/ MUS / MUST / 16:36:24 PROPOSAL: Any columns in the SELECT list derived by projecting an expression SHOULD be named. 16:36:37 q+ 16:36:39 what if you define the behavior in terms of a referenceable view? 16:36:44 q? 16:36:47 (SQL:referenceable view) 16:36:47 ack Souri 16:37:07 that way the SQL spec defines it for you 16:38:04 +1 16:38:05 q? 16:38:55 RESOLUTION: Last proposal accepted by WG 16:39:49 Topic: XSD mapping for binary columns (xsd:hexBinary vs. xsd:base64Binary) 16:40:04 PROPOSAL: Binary datatypes like BLOB and VARBINARY should be mapped to xsd:hexBinary instead of xsd:base64Binary. 16:40:12 +1 16:40:16 Topic: XSD mapping for binary columns (xsd:hexBinary vs. xsd:base64Binary) http://lists.w3.org/Archives/Public/public-rdb2rdf-wg/2012Apr/0020.html 16:41:54 +1 16:42:09 ±0 16:42:26 Topic: Implementability for tables w/o primary key 16:42:38 RESOLUTION: Proposal accepted 16:42:44 PROPOSAL: In the DM spec, replace the following text: 16:42:45 [[ 16:42:46 If the table has no primary key, the row node is a fresh blank node that is unique to this row. 16:42:48 ]] 16:42:49 with this: 16:42:51 [[ 16:42:52 If the table has no primary key, the row node is a blank node. Distinct blank nodes MUST be generated for rows with distinct column values. For duplicate rows with identical values, implementations SHOULD generate a fresh blank for each duplicate row (resulting in a non-lean RDF graph [RDF Semantics]). However, if the underlying database system does not provide any means to reliably differentiate among the rows, then implementations MAY re-use the sa 16:42:53 blank node for multiple duplicate rows (resulting in a lean RDF graph). Implementations SHOULD document and advertise their chosen behavior. 16:42:55 ]] 16:43:28 PROPOSAL: Binary datatypes like BLOB and VARBINARY should be mapped to xsd:hexBinary instead of xsd:base64Binary. 16:43:44 i think very few people are aware of lean graphs 16:43:47 s/PROPOSAL/RESOLVED/ 16:43:51 especially SPARQL users 16:43:51 w+1 to Eric 16:43:58 +1 to Eric 16:44:14 I think it would just frighten people 16:44:26 +1 as written 16:46:05 Remove: (resulting in a lean RDF graph) 16:46:38 PROPOSAL: If the table has no primary key, the row node is a blank node. Distinct blank nodes MUST be generated for rows with distinct column values. For duplicate rows with identical values, implementations SHOULD generate a fresh blank for each duplicate row. However, if the underlying database system does not provide any means to reliably differentiate among the rows, then implementations MAY re-use the same blank node for multiple duplicate rows. 16:46:39 Implementations SHOULD document and advertise their chosen behavior. 16:48:21 ericP: http://lists.w3.org/Archives/Public/public-rdb2rdf-wg/2012Apr/0036.html 16:50:59 possible informative note -- "The result of reusing the same blank node for multiple rows is a lean RDF graph [RDF Semantics]; generating fresh blank nodes for each row results in a non-lean RDF graph. One significant implication of a lean RDF graph is loss of cardinality." 16:51:57 PROPOSAL: If the table has no primary key, the row node is a blank node. Distinct blank nodes MUST be generated for rows with distinct column values. For duplicate rows with identical values, implementations SHOULD generate a fresh blank for each duplicate row. However, if the underlying database system does not provide any means to reliably differentiate among the rows, then implementations MAY re-use the same blank node for multiple duplicate rows w 16:51:57 implies loss of cardinality 16:55:08 q+ 16:55:15 q? 16:55:25 ack Ashok 16:56:30 My prediction: most probably, implementors will not support SPARQL to SQL on the direct mapping on tables with no primary keys because 1) it's complicated to implement 2) corner case 16:58:47 juansequeda++ 17:02:11 regrets+ Marcelo 17:04:07 D012-2tables2duplicates0nulls 17:05:36 q+ 17:05:40 q+ 17:05:43 q? 17:05:46 ack juansequeda 17:06:44 ack ivan 17:06:51 q+ 17:07:01 ack ivan 17:07:39 Ivan: Asks about our plans going forward 17:07:46 q+ 17:08:02 q? 17:08:12 Michael: There are 2 open issues. We need to resolve these. 17:08:40 Ivan: So it looks like we are in second last call 17:09:13 Ivan: Because of the moratorium we need to publish before next Thursday. 17:09:46 ... so we have some time pressure 17:10:23 https://lists.w3.org/Archives/Member/chairs/2012AprJun/0043.html 17:11:00 regrets+ Boris 17:11:34 q? 17:11:37 ack cygri 17:14:38 Richard: The last 2 issues make the DM and R2RML mapping incompatible 17:15:14 http://lists.w3.org/Archives/Public/public-rdb2rdf-wg/2012Apr/0070.html 17:19:15 Topic: DM cannot be implemented as an R2RML mapping (period encoding) http://lists.w3.org/Archives/Public/public-rdb2rdf-wg/2012Apr/0021.html 17:19:29 RESOLUTION: re DM cannot be implemented as an R2RML mapping (period encoding) the WG agrees to go with http://lists.w3.org/Archives/Public/public-rdb2rdf-wg/2012Apr/0070.html 17:20:32 RRSAgent, draft minutes 17:20:32 I have made the request to generate http://www.w3.org/2012/05/01-RDB2RDF-minutes.html mhausenblas 17:20:56 rrsagent, make logs public 17:22:58 ericP, how about tomorrow after the rdf-wg call? 17:23:18 Request Eric and Richard discuss over email or on the phone. 17:23:51 We will resolve this issue on the My 8 call, one way or another. 17:23:52 bye guys 17:23:55 have fun:-) 17:24:03 -Ivan 17:24:04 ADJOURNED 17:24:23 -MacTed 17:25:59 nunolopes has joined #rdb2rdf 17:26:08 -seema 17:26:24 nunolopes has joined #rdb2rdf 17:30:10 -Souri 17:32:00 SELECT * { ?I ?fname ; ?amount . ?L ?fname ; ?city } 17:32:11 │ _:a │ _:d │ 3.0E1 │ "London" │ "Bob" │ 17:32:11 │ _:a │ _:f │ 3.0E1 │ "London" │ "Bob" │ 17:32:11 │ _:c │ _:d │ 3.0E1 │ "London" │ "Bob" │ 17:32:11 │ _:c │ _:f │ 3.0E1 │ "London" │ "Bob" │ 17:32:11 │ _:b │ _:e │ 2.0E1 │ "Madrid" │ "Sue" │ 17:32:13 -dmcneil 17:32:34 SELECT * FROM IOUs INNER JOIN Lives ON IOUs.fname=Lives.fname; 17:32:42 | Bob | Smith | 30 | Bob | Smith | London | 17:32:42 | Bob | Smith | 30 | Bob | Smith | London | 17:32:42 | Sue | Jones | 20 | Sue | Jones | Madrid | 17:32:42 | Bob | Smith | 30 | Bob | Smith | London | 17:32:42 | Bob | Smith | 30 | Bob | Smith | London | 17:35:09 trackbot, end telecon 17:35:09 Zakim, list attendees 17:35:09 As of this point the attendees have been Ashok_Malhotra, mhausenblas, cygri, MacTed, dmcneil, Ivan, nuno, nunolopes, Souri, juansequeda, seema, EricP 17:35:17 RRSAgent, please draft minutes 17:35:17 I have made the request to generate http://www.w3.org/2012/05/01-RDB2RDF-minutes.html trackbot 17:35:18 RRSAgent, bye 17:35:18 I see no action items