16:00:09 RRSAgent has joined #rdb2rdf 16:00:09 logging to http://www.w3.org/2010/05/11-rdb2rdf-irc 16:00:11 RRSAgent, make logs world 16:00:11 Zakim has joined #rdb2rdf 16:00:13 Zakim, this will be 7322733 16:00:13 ok, trackbot; I see SW_RDB2RDF()12:00PM scheduled to start now 16:00:14 Meeting: RDB2RDF Working Group Teleconference 16:00:14 Date: 11 May 2010 16:00:42 hhalpin has changed the topic to: RDB2RDF Meeting May 11th 16:00:46 Zakim, this is 7322733 16:00:49 seema has joined #rdb2rdf 16:00:55 ok, MacTed; that matches SW_RDB2RDF()12:00PM 16:00:58 juansequeda has joined #RDB2RDF 16:01:03 Zakim, who's here? 16:01:09 On the phone I see +043316876aaaa 16:01:15 + +1.781.273.aabb 16:01:19 On IRC I see juansequeda, seema, Zakim, RRSAgent, whalb, cygri, Ashok, hhalpin, Marcelo, MacTed, LeeF, nunolopes, mhausenblas, iv_an_ru, trackbot, ericP 16:01:24 + +1.562.249.aacc 16:01:26 zakim, aaaa is me 16:01:32 +whalb; got it 16:01:36 + +1.603.897.aadd 16:01:36 Zakim, aabb is OpenLink_Software 16:01:37 zakim, OpenLink_Software is temporarily me 16:01:42 +OpenLink_Software; got it 16:01:44 +MacTed; got it 16:01:51 +??P7 16:01:52 + +1.512.471.aaee 16:02:11 Zakim, ??P7 is hhalpin 16:02:14 +hhalpin; got it 16:02:20 +Ashok_Malhotra 16:02:40 Zakim, code? 16:02:40 the conference code is 7322733 (tel:+1.617.761.6200 tel:+33.4.89.06.34.99 tel:+44.117.370.6152), mhausenblas 16:02:43 zakim, aadd is me 16:02:43 +seema; got it 16:03:05 + +3539149aaff 16:03:16 Zakim, aaff is me 16:03:16 +mhausenblas; got it 16:03:23 Zakim, cygri is with me 16:03:23 +cygri; got it 16:03:28 Zakim, who's here? 16:03:28 On the phone I see whalb, MacTed, +1.562.249.aacc, seema, hhalpin, +1.512.471.aaee, Ashok_Malhotra, mhausenblas 16:03:30 mhausenblas has mhausenblas, cygri 16:03:31 On IRC I see juansequeda, seema, Zakim, RRSAgent, whalb, cygri, Ashok, hhalpin, Marcelo, MacTed, LeeF, nunolopes, mhausenblas, iv_an_ru, trackbot, ericP 16:03:33 Chair: Michael 16:03:41 scribenick: cygri 16:04:01 Zakim, please dial ericP-office 16:04:01 ok, ericP; the call is being made 16:04:02 +EricP 16:04:27 Topic: 1. Admin 16:04:43 PROPOSAL: Accept the minutes of the 4 May 2010 telecon, 16:04:43 http://www.w3.org/2010/05/04-rdb2rdf-minutes.html 16:05:11 +1 16:05:18 RESOLVED: Accept the minutes of the 4 May 2010 telecon http://www.w3.org/2010/05/04-rdb2rdf-minutes.html 16:05:32 Topic: 2. Introduction of new members 16:05:54 I can send them a quick e-mail with telecon instructions. 16:05:55 intro email from Boris and Alexander: http://lists.w3.org/Archives/Public/public-rdb2rdf-wg/2010May/0024.html 16:06:01 Topic: 3. Use Case Document 16:06:06 perhaps they had some issues calling in. 16:06:06 Zakim, aacc is me 16:06:06 +Marcelo; got it 16:06:10 -> http://www.w3.org/2001/sw/rdb2rdf/wiki/Use_Cases_and_Requirements/Reviews 16:06:27 draft is here: http://www.w3.org/2001/sw/rdb2rdf/use-cases/ 16:06:54 well, we need to make sure the working draft is well-formed english :) 16:07:03 + +039046128aagg 16:07:13 but all of my comments are minor, and do not cause substantial changes to text. 16:08:03 angela_Unitn has joined #RDB2RDF 16:08:12 Usually "authors" are people who contributed substantial amounts of text 16:08:20 "Contributors" are people who sent in, say, comments. 16:08:29 That is more or less W3C process. 16:08:35 to my knowledge. 16:08:38 +1 marcelo 16:08:38 Marcelo: authors should be who contributed to writing of use cases, not everyone 16:08:45 +1 to marcelo's suggestion 16:08:57 mhausenblas: all members would typically listed in the acknowledgements 16:09:07 PROPOSED to list WG members in acknowldgements 16:09:17 PROPOSED to list WG members in acknowldgements and keep author list as it 16:09:21 +1 16:09:23 +1 16:09:23 +1 16:09:28 _1 16:09:29 APPROVED 16:09:39 +1 16:10:14 ericP: I addressed Ahmed's comment 16:10:15 RRSAgent, draft minutes 16:10:15 I have made the request to generate http://www.w3.org/2010/05/11-rdb2rdf-minutes.html mhausenblas 16:10:22 rrsagent, make records public 16:11:11 ericP: Juan didn't want to have SQL query in use case 16:11:49 Juan: it's enough to *say* we translate to SQL, we don't need to *show* it 16:11:55 thanks mhausenblas 16:12:17 RESOLUTION: list WG members in acknowldgements and keep author list as it 16:12:56 q+ 16:13:07 Juan: the specific SQL depends on implementer so let's not show one specific 16:13:35 ack hhalpin 16:13:36 ericP: but we should show that we can do an effective job 16:13:53 ericP added this "This query is not a normative representation of the earlier SPARQL query; it is included here only to illustrate the ability of R2RML tools to produce efficient SQL queries." 16:13:55 mhausenblas: let's focus on the document, we want to get first draft out today 16:14:02 I propose that 16:14:17 s "This query is not a normative representation of the earlier SPARQL query; it is included here only to illustrate that R2ML could produce efficient SQL queries." 16:14:39 Zakim, unmute me 16:14:39 hhalpin was not muted, hhalpin 16:14:56 Well, my proposal is just as easy to read in IRC as anywhere else. 16:15:10 current text says "This query is not a normative representation of the earlier SPARQL query; it is included here only to illustrate the ability of R2RML tools to produce efficient SQL queries. 16:15:14 " 16:15:15 Thus, we do not say that we *have* to produce efficient SQL, but implementations *could*. 16:15:19 Ashok: this sentence is too weak, it doesn't say anything 16:15:34 Ashok - that sentence is from EricP. 16:15:40 I changed ONE word. 16:15:49 mhausenblas: let's take it as editorial note for now 16:16:26 i.e. said it "could" produce SQL queries. 16:16:31 PROPOSAL: ed note: "This query is not a normative representation of the earlier SPARQL query; it is included here only to illustrate that R2ML could produce efficient SQL queries." 16:17:31 Let's do a go around on deleting or keeping that SQL query in then. 16:17:43 -hhalpin 16:18:05 q+ 16:18:23 +??P7 16:18:32 Zakim, ??P7 is hhalpin 16:18:32 +hhalpin; got it 16:18:39 q+ 16:18:42 seema: let's not put a sql query 16:19:14 q? 16:19:36 ack juansequeda 16:19:41 (ericP and MacTed talk about wether efficiency is relevant in the context of the use case) 16:21:34 PROPOSAL: separate section, independent from the use cases, that says "this sparql might be translated to this efficient sql" 16:21:56 why not just keep that text in the use-case? 16:22:02 q? 16:22:10 we have enough sections as is. 16:22:20 its actually better to have it in use-cases rather than requirements. 16:22:34 Juan: why not stick it in section on requirement "sql generation"? 16:22:50 q+ 16:22:54 hhalpin: in requirements, it sounds like we *require* efficient sql to be produced 16:23:22 Juan: but we have the "sql generation" section already 16:23:41 ack MacTed 16:24:01 I'm saying it causes minimum damage in the "use case" docuemnt 16:24:29 MacTed: everyone wants efficient sql obviously. the important thing is that every sparql query is rendered as executable sql. efficiency is not important. 16:25:18 ericP: my use case has to do with querying massive numbers of records. efficiency is key to that use case. i want to keep it there 16:25:22 So maybe add "This query is not a normative representation of the earlier SPARQL query; it is included here only to illustrate the ability of R2RML tools to produce efficient SQL queries" -> "This query is not a normative representation of the earlier SPARQL query; it is included here only to illustrate the ability of R2RML tools to possibly produce efficient SQL queries, although our mapping file will not mandate any particular transformation of SPARQL to 16:25:22 SQL." 16:25:32 just to be clear. 16:26:02 +1 a vote 16:26:15 I agree, but we need a question ... :) 16:26:20 ideally on IRC 16:26:37 Who wants to put SQL in the use case document? 16:26:43 PROPOSAL: leave the SQL there as an ed note, with 16:26:56 PROPOSAL: leave the SQL there as an ed note, with hhalpin's proposed rewording 16:27:00 +1 16:27:00 +1 16:27:07 +1 16:27:07 The requirement really sounds like to avoid a design that precludes generating efficient SQL queries 16:27:17 +1 16:27:37 +1 to having a SQL query example in UC&R 16:27:51 -1 have sql query 16:27:53 (Note that the rewording mentions a SQL query in a use-case, with the following text: This query is not a normative representation of the earlier SPARQL query; it is included here only to illustrate the ability of R2RML tools to possibly produce efficient SQL queries, although our mapping file will not mandate any particular transformation of SPARQL to SQL. 16:28:01 -! 16:28:01 ) I was hoping that text addresses Juan's concern. 16:28:04 Zakim, who's here? 16:28:04 On the phone I see whalb, MacTed, Marcelo, seema, +1.512.471.aaee, Ashok_Malhotra, mhausenblas, EricP, +039046128aagg, hhalpin 16:28:06 mhausenblas has mhausenblas, cygri 16:28:08 On IRC I see angela_Unitn, juansequeda, seema, Zakim, RRSAgent, whalb, cygri, Ashok, hhalpin, Marcelo, MacTed, LeeF, nunolopes, mhausenblas, iv_an_ru, trackbot, ericP 16:28:09 -1 16:28:09 +1 16:28:23 i would rather just have the wording..not the SQL 16:28:48 -1 16:28:50 -1 16:29:05 dan: -1 16:29:24 This is rather close... 16:29:34 perhaps we should try a "Can we live with it being removed" vote? 16:29:42 english saying "the R2RML allows for translation of arbitrary SPARQL to executable SQL. efficiency is left as an excercise for the implementor." ;-) 16:30:13 RRSAgent, draft minutes 16:30:13 I have made the request to generate http://www.w3.org/2010/05/11-rdb2rdf-minutes.html mhausenblas 16:31:32 PROPOSAL: remove sql query from the document 16:31:33 PROPOSAL: Remove SQL query and associated text from document. 16:32:03 Abstain. 16:32:11 We could do a straw poll again... 16:32:28 well the associated text doesn't make much sense without the SQL query. 16:32:36 abstain 16:32:37 We could try to add some suitable text there if we can think of some. 16:33:10 ericP - can you think of some text that can be added in that satisfies you? 16:33:15 mhausenblas: any objections? 16:34:08 RESOLUTION: Remove SQL query and associated text from document. 16:34:25 dan: i'd keep the general notion of the section's first paragraph, but without the query 16:35:43 ericP: sören suggested to move UC5 and UC6 to requirements 16:36:32 ... i moved them to the requirements, MANYTOMANY and VALUETYPE 16:36:41 I'm ok with it. 16:36:45 like " The RDF graphs defined by a mapping over a relational database need not be materialised. Indeed, queries or inference may be expressed in terms of a notional representation of relational data, but executed over the original relational store. Executing a SQL query over any data in the relational tables should give results identical to a SPARQL query over the RDF graph mapped from that relational data. While our specification will not produce a normat 16:36:45 ive SQL representation of arbitrary SPARQL query; although RDB2RDF tools could possibly produce efficient SQL queries from SPARQL queries without materialization." 16:36:49 ... anyone has issues with this? 16:37:06 There's some text based on EricP's minus any reference to an actual SQL query. 16:37:49 PROPOSE 4.1.8 MANYTOMANY and 4.1.9 VALUETYPE address Soren's and Juan's comments around UC5 and 6 16:38:00 PROPOSAL: 4.1.8 MANYTOMANY and 4.1.9 VALUETYPE address Soren's and Juan's comments around UC5 and 6 16:38:08 +1 16:38:08 +1 16:38:11 +1 16:38:23 APPROVED 16:38:34 RESOLUTION: 4.1.8 MANYTOMANY and 4.1.9 VALUETYPE address Soren's and Juan's comments around UC5 and 6 16:39:12 Juan: UC3 is the only one that has all these sections 16:39:34 ericP: are you ok with publishihng UC3 as is, and clean it up later? 16:39:38 for me you can clean them up 16:40:09 and the rest of the formatting around UC3. 16:40:13 that separates it from other use-cases. 16:40:18 +1 16:40:43 propose making UC3 like the rest of the use-cases! 16:40:44 RRSAgent, draft minutes 16:40:44 I have made the request to generate http://www.w3.org/2010/05/11-rdb2rdf-minutes.html mhausenblas 16:40:48 i.e. remove special formatting. 16:40:58 PROPOSED: public UC3 as in 1.34 16:41:10 +1 16:41:14 APPROVED 16:41:14 +1 16:41:20 PROPOSAL: publish UC3 as in 1.34 16:41:26 RESOLUTION: publish UC3 as in 1.34 16:43:47 (ericP, Juan, MacTed discuss Juan's image) 16:43:54 http://userweb.cs.utexas.edu/~jsequeda/rdb2rdf/ 16:44:27 mhausenblas: can you sort this out via email after the call? 16:44:56 +1 16:44:57 ericP: PROPOSAL: keep the Approaches section as is, except for tweaking the image 16:45:02 PROPOSAL: keep the Approaches section as is, except for tweaking the image 16:45:12 +1 16:45:16 RESOLUTION: keep the Approaches section as is, except for tweaking the image 16:45:24 It does seem a bit repetivie with Section 4, so I'll +1 once I get to e-mail in some minor textual changes. 16:45:48 alexander has joined #RDB2RDF 16:46:19 hi alexander 16:47:02 we're in the call, started 45min ago ... 16:47:31 4.1.1 Direct Mapping -- RDB Schema to Local RDF Ontology 16:47:52 4.1.2 Transformative Mapping -- RDB Schema to Domain RDF Ontology/ies 16:48:21 PROPOSAL: change titles of 4.1.1and 4.1.2 as per MacTed above 16:48:23 Hello, sorry, we though that the conference was at 7PM our time 16:48:36 4.1.2 *could* be Tranformative Mapping -- Local RDF Ontology to Domain RDF Ontology/ies 16:48:41 alexander, did you receive the invitation mail? 16:48:56 see http://lists.w3.org/Archives/Public/public-rdb2rdf-wg/2010May/0034.html alexander 16:49:10 there is a link in this mail, see http://www.timeanddate.com/worldclock/fixedtime.html?month=05&day=11&year=20 16:49:22 should be unambiguous ;) 16:49:32 alexander, this happens to everyone the first time ;-) 16:49:53 Thank you, yes we received but for some reason we got confused with the times... sorry 16:49:54 no worries, yeah, alexander - can you dail in now? 16:50:20 yes we are trying to to do that now 16:50:33 ah, ok, alexander 16:50:54 -1 proforma schema 16:51:05 we just need to "choose" terms. 16:51:21 We should choose terms preferred by database community, NOT RDF community. 16:51:23 MacTed: let's stick to local ontology and domain ontology 16:51:33 ... if we simply state what they mean, it should be fine 16:51:34 +1 MacTed 16:51:48 I mean, most database administrators will likely have little idea what OWL is. 16:51:52 +1 Tes 16:52:12 As long as we clearly define our terms and use the terms known by people in the database community. 16:52:28 ericP: can we say "... convert to an RDF graph conforming to an ontology"? 16:53:13 hhalpin: database people don't use terms like "graph conforming to an ontology" 16:53:33 ericP: but do rdf people understand "local ontolgy" etc? 16:53:37 Could someone from a database background speak-up? 16:53:56 I'm happy with EricP's rewording to make it precise. 16:54:20 "instance data" 16:54:38 +1 with Michael's terms, and add clarifying text re local and domain ontology 16:54:41 + +49.133.6.aahh 16:54:41 PROPOSAL: name 4.1.1 Direct Mapping, 4.1.2 Transformative Mapping 16:55:05 Zakim, aahh is boris 16:55:05 +boris; got it 16:55:09 +1 16:55:11 +1 16:55:20 RESOLVED 16:55:22 RESOLUTION: name 4.1.1 Direct Mapping, 4.1.2 Transformative Mapping 16:56:39 MacTed: identifiers are for machine use, labels are for human use 16:57:05 ... create a glossary? 16:57:53 PROPOSAL: add a glossary/terminology section as new Section 1.4, to clarify issues around identifier/label etc 16:58:07 identifier, label, local ontology, domain ontology ... 16:58:23 My edits are all grammatical, minor edits to formatting. 16:58:45 +1 for adding a glossary 16:59:11 RESOLUTION: add a glossary/terminology section as new Section 1.4, to clarify issues around identifier/label etc 16:59:19 Seems like glossary could also clarify the mapping between database terminology of local/domain ontology and SemWeb use of word ontology. 16:59:27 +1 for adding glossary 17:00:20 MacTed: connection information (jdbc etc) is implementation detail 17:00:48 ericP: jdbc style for expressing that information can be used without jdbc drivers 17:01:30 ericP: there can be user benefit in combining connection and map 17:02:02 MacTed: connection information is fine, but it should not show jdbc as example 17:02:20 mhausenblas: doc does not mention jdbc 17:02:23 MacTed: fine 17:03:22 http://lists.w3.org/Archives/Public/public-rdb2rdf-wg/2010May/0038.html 17:03:58 ericP: we can live without more references for first publication 17:04:45 PROPOSED: to dispatch Le Ma's comments http://lists.w3.org/Archives/Public/public-rdb2rdf-wg/2010May/0038 after first publication 17:04:48 +1 17:04:54 APPROVED 17:04:55 +1 17:04:58 RRSAgent, draft minutes 17:04:58 I have made the request to generate http://www.w3.org/2010/05/11-rdb2rdf-minutes.html cygri 17:04:59 PROPOSAL: WG decides to publish the UCR document as FPWD with the corrections as resolved as today 17:05:18 +1 17:05:19 +1 17:05:30 +1 17:05:31 +1 17:05:32 +1 17:05:32 +1 (more minor editorial/grammatical changes to be sent in today) 17:05:33 +1 17:05:37 +1 17:05:52 RESOLUTION: WG decides to publish the UCR document as FPWD with the corrections as resolved as today 17:06:25 -Ashok_Malhotra 17:06:51 hhalpin 17:07:13 ACTION: hhalpin to take fixed UCR document and publish as FPWD + TR URI 17:07:14 Created ACTION-54 - Take fixed UCR document and publish as FPWD + TR URI [on Harry Halpin - due 2010-05-18]. 17:07:40 ericP: i'll just comment out the SQL stuff 17:07:44 s/Le Ma/Li Ma 17:07:50 RRSAgent, draft minutes 17:07:50 I have made the request to generate http://www.w3.org/2010/05/11-rdb2rdf-minutes.html mhausenblas 17:08:05 - +039046128aagg 17:08:27 ericP: are we happy to just publish and link to juan's images? 17:08:57 ... don't want hosting of the images to be in the critical path towards publication 17:09:35 +1 fixing image, but NOT have it linked outside of w3 space., 17:09:43 ... is rest of WG happy to accept whatever MacTed and juan come up with for the images? 17:09:51 (no objections) 17:09:51 -whalb 17:09:51 [adjourned] 17:09:52 -seema 17:09:56 -Marcelo 17:09:59 RRSAgent, draft mintues 17:09:59 I'm logging. I don't understand 'draft mintues', mhausenblas. Try /msg RRSAgent help 17:10:02 RRSAgent, draft minutes 17:10:02 I have made the request to generate http://www.w3.org/2010/05/11-rdb2rdf-minutes.html mhausenblas 17:10:09 Zakim, list attendees 17:10:09 As of this point the attendees have been +043316876aaaa, +1.781.273.aabb, +1.562.249.aacc, whalb, +1.603.897.aadd, MacTed, +1.512.471.aaee, hhalpin, Ashok_Malhotra, seema, 17:10:12 RRSAgent, draft minutes 17:10:12 I have made the request to generate http://www.w3.org/2010/05/11-rdb2rdf-minutes.html mhausenblas 17:10:13 ... +3539149aaff, mhausenblas, cygri, EricP, Marcelo, +039046128aagg, +49.133.6.aahh, boris 17:10:42 rdb2rdf-ucr 17:13:11 Zakim, who's here? 17:13:11 On the phone I see MacTed, +1.512.471.aaee, mhausenblas, EricP, hhalpin, boris 17:13:13 mhausenblas has mhausenblas, cygri 17:13:15 On IRC I see alexander, juansequeda, seema, Zakim, RRSAgent, cygri, hhalpin, MacTed, LeeF, nunolopes, mhausenblas, iv_an_ru, trackbot, ericP 17:14:39 http://www.w3.org/XML/1998/06/xmlspec-report-v21.htm#AEN2221 17:19:53 -mhausenblas 17:19:55 -hhalpin 17:20:07 -EricP 17:20:37 Zakim, bye 17:20:37 leaving. As of this point the attendees were +043316876aaaa, +1.781.273.aabb, +1.562.249.aacc, whalb, +1.603.897.aadd, MacTed, +1.512.471.aaee, hhalpin, Ashok_Malhotra, seema, 17:20:37 Zakim has left #rdb2rdf 17:20:40 ... +3539149aaff, mhausenblas, cygri, EricP, Marcelo, +039046128aagg, +49.133.6.aahh, boris 17:20:46 RRSAgent, bye 17:20:46 I see 1 open action item saved in http://www.w3.org/2010/05/11-rdb2rdf-actions.rdf : 17:20:46 ACTION: hhalpin to take fixed UCR document and publish as FPWD + TR URI [1] 17:20:46 recorded in http://www.w3.org/2010/05/11-rdb2rdf-irc#T17-07-13