14:26:23 RRSAgent has joined #dawg 14:26:24 logging to http://www.w3.org/2007/03/20-dawg-irc 14:26:47 zakim, this will be dawg 14:26:47 ok, LeeF; I see SW_DAWG()9:30AM scheduled to start in 4 minutes 14:27:00 Meeting: RDF Data Access Weekly 14:27:04 Chair: LeeF 14:27:06 Scribe: LeeF 14:27:50 SW_DAWG()9:30AM has now started 14:27:57 +MIT531 14:28:47 patH has joined #dawg 14:28:53 Zakim, MIT531 has LeeF, ericP 14:28:53 +LeeF, ericP; got it 14:29:21 Zakim, who is here? 14:29:21 On the phone I see MIT531 14:29:22 MIT531 has LeeF, ericP 14:29:23 On IRC I see patH, RRSAgent, Zakim, LeeF, AndyS, SteveH, afs, ericP, iv_an_ru 14:29:37 be there in a second 14:29:46 Agenda: http://lists.w3.org/Archives/Public/public-rdf-dawg/2007JanMar/0162.html 14:30:00 agenda + convene 14:30:02 agenda + action items 14:30:25 +??P2 14:30:27 zakim, ??P2 is me 14:30:27 +AndyS; got it 14:30:28 +PatH 14:30:37 agenda + Duplicate solution cardinality 14:30:45 agenda + issue entailmentFramework 14:30:49 +??P4 14:30:52 jeen has joined #dawg 14:30:54 agenda + last call 14:30:56 Zakim, ??P4 is SteveH 14:30:56 +SteveH; got it 14:31:01 Zakim, mute me 14:31:01 SteveH should now be muted 14:31:05 hi 14:31:06 sdas2 has joined #dawg 14:31:07 agenda + Test suite 14:32:25 LeeF has changed the topic to: RDF Data Access Working Group weekly telecon. agenda http://lists.w3.org/Archives/Public/public-rdf-dawg/2007JanMar/0162.html 14:32:31 SimonR has joined #dawg 14:32:48 + +1.603.897.aaaa 14:33:13 zakim, aaaa is sdas2 14:33:13 +sdas2; got it 14:33:48 zakim, sdas2 is souri 14:33:48 +souri; got it 14:34:02 +[IPcaller] 14:34:07 zakim, [IPcaller] is me 14:34:07 +jeen; got it 14:34:57 minutes from last week -> http://www.w3.org/2007/03/13-dawg-minutes 14:36:17 SimonR has joined #dawg 14:36:36 +[IBMCambridge] 14:36:37 +??P28 14:36:50 Zakim, ??P28 is me 14:36:50 +SimonR; got it 14:37:04 approved minutes http://www.w3.org/2007/03/13-dawg-minutes 14:37:29 next meeting 27th of march, scribe: ericP 14:37:57 agenda + active graph 14:38:03 zakim, take up agendum 2 14:38:03 agendum 2. "action items" taken up [from LeeF] 14:38:05 EliasT has joined #dawg 14:38:14 Zakim, IBM is me 14:38:14 sorry, EliasT, I do not recognize a party named 'IBM' 14:38:18 Zakim, IBMCambridge is me 14:38:18 +EliasT; got it 14:38:23 ACTION: ericP to draft text about a LOOSE keyword and run it by w3 folks 14:38:23 to see if we're abusing the "at risk" mechanism [DONE] 14:38:31 ACTION: LeeF to seek guidance about at-risk features from the CG [DONE] 14:38:38 Zakim, pointer? 14:38:38 I don't understand your question, EliasT. 14:38:41 ACTION: ericP to mark sections 2 and 3 informative, Appendices A, B and D 14:38:41 normative in the text and table of contents and 1.1 document outline [DONE] 14:38:47 ACTION: LeeF to close bnodeRef issue [DONE] 14:38:52 ACTION: LeeF to close nested optionals issue [DONE] 14:39:00 ACTION: LeeF to close openWorldValueTesting issue [DONE] 14:39:19 ACTION: PatH to investigate closing the entailment issue [DONE] 14:39:28 ACTION: EricP to run the yacker tool over and annotate the existing tests [CONTINUES] 14:39:36 ACTION: LeeF or EliasT to reply to Bjoern regarding (not) POSTing application/sparql-query documents [CONTINUES] 14:39:44 ACTION: LeeF to remember that the wee, lost filter tests should be put [CONTINUES] 14:39:50 zakim, close agendum 14:39:50 I don't understand 'close agendum', LeeF 14:39:55 zakim, close this agendum 14:39:55 agendum 2 closed 14:39:57 I see 6 items remaining on the agenda; the next one is 14:39:58 1. convene [from LeeF] 14:40:00 zakim, take up agendum 3 14:40:00 agendum 3. "Duplicate solution cardinality" taken up [from LeeF] 14:43:18 LeeF: I spoke to Ivan and Ralph and they agreed that we can make use of the at risk feature in our publication and mark LOOSE at risk. 14:43:24 Scribe: EliasT 14:44:03 ... we can also make use of an informative section for LOOSE but that might not neccessarily fit this situation. 14:44:35 ericP: LOOSE keyword shouldn't affect implementations too much since they only need to know how to parse it. They don't have to do any extra work when encountering it. 14:45:34 patH: I'll keep my mute button on for this discussion. 14:45:45 PROPOSE: SPARQL SELECT queries with no keyword following SELECT must 14:45:45 return the precise cardinality of duplicate solutions specified by the 14:45:45 algebra; SPARQL contains a @@ LOOSE keyword that allows duplicate 14:45:45 solutions to be returned with cardinality of at least 1 and no greater 14:45:45 than that specified by the algebra. The @@ LOOSE keyword will be marked as 14:45:46 an at-risk feature of SPARQL. 14:46:18 i nominate "LAX" as the keyword 14:46:48 DISTINCT PLUS 14:47:03 zakim, sdas2 is Souri 14:47:03 sorry, sdas2, I do not recognize a party named 'sdas2' 14:47:04 AndyS: We should discuss the keyword because that will dictate the semantics 14:47:11 LOOSE 14:47:12 LAX 14:47:14 INDISTINCT 14:47:17 DISTINCT PLUS 14:47:23 how about VOMIT 14:47:56 "SOME" ? 14:47:56 Thanks Jeen 14:48:17 'indistinct' sounds like you can't tell the difference betwen the answers. 14:48:28 -1 to LAX : 0 to LOOSE 14:48:55 LAX is an airport code, which might be a problem? 14:49:20 AT-LEAST-ONE-OF-EACH 14:49:27 WHATEVER? 14:49:36 REDUCED? 14:49:42 SILLY? 14:49:51 +q 14:50:03 ack Souri 14:50:45 MORE (seriously) 14:51:04 what about LOOSE DISTINCT 14:51:20 It's a little bit disturbing that there's no english word for this concept.... 14:51:38 BAG 14:52:29 PARTIAL ? (same problem as SOME) 14:52:39 from www.wordsmyth.net: 14:52:39 lax[1]: not rigorous, strict, or careful; loose; lenient. 14:52:39 loose[1]: not restrained or confined; free. 14:52:39 reduce[1]:to make less in amount or size. 14:53:00 I like REDUCE best I think 14:53:02 how about FREE? 14:53:07 DUPLICATED 14:53:25 REDUCED DUPLICATES ? 14:53:49 LeeF: AndyS and Souri have a good comment that PARTIAL and SOME might imply that you are getting less than at least one for each unique answer. 14:54:21 ericP: (answering to Lee's what about REDUCED) +0 14:54:36 REDUCE or REDUCED 14:54:44 REDUCTIBLE 14:54:55 RUSTED 14:55:06 +q 14:55:08 ericP: +1 REDUCED 14:55:09 +1 for REDUCED 14:55:14 PROPOSE: SPARQL SELECT queries with no keyword following SELECT must 14:55:14 return the precise cardinality of duplicate solutions specified by the 14:55:14 algebra; SPARQL contains a REDUCED keyword that allows duplicate 14:55:14 solutions to be returned with cardinality of at least 1 and no greater 14:55:14 than that specified by the algebra. The REDUCED keyword will be marked as 14:55:16 an at-risk feature of SPARQL. 14:55:26 ack Souri 14:55:49 REDUCE works better with DISTINCT, surely? 14:55:55 otherwise it would be DISTINCTED 14:57:29 DISTINGUISHED 14:57:43 AndyS: Will the text highlight that this could affect future counting? 14:57:47 ericP: I don't think it does. 14:58:08 AndyS: If you do SELECT REDUCE DISTINCT COUNT is meaningless 14:58:27 LeeF: I'm inclined to say no because we don't know what COUNT looks like 14:58:31 SELECT REDUCE COUNT(*) 14:58:47 SimonR: This is specifically for the case when you don't want to count things 14:59:16 second 14:59:18 second 14:59:34 Abstaining. 14:59:39 AndyS: Abstain 14:59:48 RESOLVED 15:00:02 RESOLVED, AndyS and SimonR abstaining 15:00:21 ACTION: Eric to incorporate text for REDUCED into rq25, including text noting that REDUCED does not play nicely with counting 15:00:36 zakim, close this agendum 15:00:39 agendum 3 closed 15:00:40 I see 5 items remaining on the agenda; the next one is 15:00:40 zakim, take up agendum 4 15:00:41 1. convene [from LeeF] 15:00:44 agendum 4. "issue entailmentFramework" taken up [from LeeF] 15:00:49 -> http://www.w3.org/2001/sw/DataAccess/issues#entailmentFramework 15:01:42 LeeF: patH do you think we have address the entailment framework issue in the document? 15:01:47 patH: yes 15:02:14 PROPOSED: that version 1.59 of rq25 addresses and closes http://www.w3.org/2001/sw/DataAccess/issues#entailmentFramework 15:02:23 second 15:02:35 RESOLVED 15:02:44 ACTION: LeeF to close #entailmentFramework issue 15:03:00 zakim, close this agendum 15:03:01 Zakim, close agendum 1 15:03:03 agendum 4 closed 15:03:04 I see 4 items remaining on the agenda; the next one is 15:03:06 1. convene [from LeeF] 15:03:07 agendum 1, convene, closed 15:03:09 I see 3 items remaining on the agenda; the next one is 15:03:11 5. last call [from LeeF] 15:03:20 zakim, take up agendum 7 15:03:21 agendum 7. "active graph" taken up [from LeeF] 15:03:58 http://lists.w3.org/Archives/Public/public-rdf-dawg/2007JanMar/0163.html 15:04:38 -> http://lists.w3.org/Archives/Public/public-rdf-dawg/2007JanMar/0163 PatH's mail, Subject: comments on section 12 (and a little more) 15:06:13 q+ 15:06:22 ACTION: AndyS to incorporate and explain the notion of active graph in section 8 and/or wherever else appropriate 15:06:28 ack SimonR 15:07:30 zakim, close this agendum 15:07:30 agendum 7 closed 15:07:31 I see 2 items remaining on the agenda; the next one is 15:07:33 5. last call [from LeeF] 15:09:50 LeeF: Anybody who does not think it's a good idea to move to Last Call? 15:10:11 LeeF: Is anybody uncomfortable the way we are moving towards last call? 15:10:56 LeeF: Nobody raised any issues or concerns with my two questions. Fantastic. 15:11:34 PROPOSED: To publish as a Last Call working draft rq25 v1.59 plus text added for relevant action items (REDUCED and active graph) 15:12:12 PROPOSED: To publish as a Last Call working draft rq25 v1.59 plus text added for relevant action items (REDUCED and active graph) and text for remainder of PatH's Section 12 review 15:13:37 PROPOSED: To publish as a Last Call working draft rq25 v1.59 plus text added for relevant action items (REDUCED and active graph) and text for remainder of PatH's Section 12 review plus query results for example query at beginning of section 11 15:14:32 AndyS: I think it's OK 15:14:34 second 15:14:41 ericP: second, much later after Elias 15:15:22 LeeF: Good job everybody. I appreciate all of your hard work. 15:15:30 ... but you are not off the hook just yet 15:17:03 last bytes editorial call at 15:00 UTC on Friday 15:17:03 What's corr EDT? 15:17:14 11:00AM EDT 15:17:15 DAWG telecon +30mins 15:18:38 LeeF: Over the next few weeks we are going to be focusing on answering comments and the test suite. 15:18:50 ... If everything goes well, we'll be working on the implementation report. 15:18:57 ADJOURNED 15:19:02 -souri 15:19:03 RRSAgent, please generate minutes 15:19:03 I have made the request to generate http://www.w3.org/2007/03/20-dawg-minutes.html EliasT 15:19:05 bye 15:19:07 -PatH 15:19:08 -SteveH 15:19:09 15:20Z 15:19:18 -SimonR 15:19:24 ACTION: ericP schedule teleconf for Friday 15:19:27 RRSAgent, please generate minutes 15:19:27 I have made the request to generate http://www.w3.org/2007/03/20-dawg-minutes.html EliasT 15:22:58 -jeen 15:24:20 -EliasT 15:27:07 RRSAgent, please draft minutes 15:27:07 I have made the request to generate http://www.w3.org/2007/03/20-dawg-minutes.html ericP 15:27:29 RRSAgent, please make logs world-visible 15:27:47 zakim, please leave 15:27:47 leaving. As of this point the attendees were LeeF, ericP, AndyS, PatH, SteveH, +1.603.897.aaaa, souri, jeen, SimonR, EliasT 15:27:47 Zakim has left #dawg 15:28:12 rrsagent, please leave 15:28:12 I see 14 open action items saved in http://www.w3.org/2007/03/20-dawg-actions.rdf : 15:28:12 ACTION: ericP to draft text about a LOOSE keyword and run it by w3 folks [1] 15:28:12 recorded in http://www.w3.org/2007/03/20-dawg-irc#T14-38-23 15:28:12 ACTION: LeeF to seek guidance about at-risk features from the CG [DONE] [2] 15:28:12 recorded in http://www.w3.org/2007/03/20-dawg-irc#T14-38-31 15:28:12 ACTION: ericP to mark sections 2 and 3 informative, Appendices A, B and D [3] 15:28:12 recorded in http://www.w3.org/2007/03/20-dawg-irc#T14-38-41 15:28:12 ACTION: LeeF to close bnodeRef issue [DONE] [4] 15:28:12 recorded in http://www.w3.org/2007/03/20-dawg-irc#T14-38-47 15:28:12 ACTION: LeeF to close nested optionals issue [DONE] [5] 15:28:12 recorded in http://www.w3.org/2007/03/20-dawg-irc#T14-38-52 15:28:12 ACTION: LeeF to close openWorldValueTesting issue [DONE] [6] 15:28:12 recorded in http://www.w3.org/2007/03/20-dawg-irc#T14-39-00 15:28:12 ACTION: PatH to investigate closing the entailment issue [DONE] [7] 15:28:12 recorded in http://www.w3.org/2007/03/20-dawg-irc#T14-39-19 15:28:12 ACTION: EricP to run the yacker tool over and annotate the existing tests [CONTINUES] [8] 15:28:12 recorded in http://www.w3.org/2007/03/20-dawg-irc#T14-39-28 15:28:12 ACTION: LeeF or EliasT to reply to Bjoern regarding (not) POSTing application/sparql-query documents [CONTINUES] [9] 15:28:12 recorded in http://www.w3.org/2007/03/20-dawg-irc#T14-39-36 15:28:12 ACTION: LeeF to remember that the wee, lost filter tests should be put [CONTINUES] [10] 15:28:12 recorded in http://www.w3.org/2007/03/20-dawg-irc#T14-39-44 15:28:12 ACTION: Eric to incorporate text for REDUCED into rq25, including text noting that REDUCED does not play nicely with counting [11] 15:28:12 recorded in http://www.w3.org/2007/03/20-dawg-irc#T15-00-21 15:28:12 ACTION: LeeF to close #entailmentFramework issue [12] 15:28:12 recorded in http://www.w3.org/2007/03/20-dawg-irc#T15-02-44 15:28:12 ACTION: AndyS to incorporate and explain the notion of active graph in section 8 and/or wherever else appropriate [13] 15:28:12 recorded in http://www.w3.org/2007/03/20-dawg-irc#T15-06-22 15:28:12 ACTION: ericP schedule teleconf for Friday [14] 15:28:12 recorded in http://www.w3.org/2007/03/20-dawg-irc#T15-19-24