14:27:10 RRSAgent has joined #dawg 14:27:10 logging to http://www.w3.org/2006/09/19-dawg-irc 14:27:48 zakim, agenda+ convene 14:27:48 agendum 1 added 14:27:55 zakim, agenda+ action items 14:27:55 agendum 2 added 14:28:01 zakim, agenda+ contradictoryKB 14:28:01 agendum 3 added 14:28:08 zakim, agenda+ formsOfDistinct 14:28:08 agendum 4 added 14:28:11 SW_DAWG()10:30AM has now started 14:28:16 zakim, agenda+ unbound variables in FILTER 14:28:16 agendum 5 added 14:28:18 +??P4 14:28:31 zakim, agenda+ open world and other value tests 14:28:31 agendum 6 added 14:28:47 zakim, agenda+ rq24 wording about underlying issues 14:28:47 agendum 7 added 14:28:52 +??P5 14:28:53 zakim, ??P4 is me 14:28:54 +SimonR; got it 14:28:55 zakim, ??P5 is me 14:28:55 +AndyS; got it 14:29:19 EliasT has joined #dawg 14:29:38 +Kendall_Clark 14:29:43 FredZ has joined #dawg 14:30:41 zakim, who's on the call? 14:30:41 On the phone I see SimonR, AndyS, Kendall_Clark 14:30:47 zakim, phone number? 14:30:47 I am sorry, LeeF; I do not know a number for number? 14:30:50 zakim, passcode? 14:30:50 the conference code is 7333 (tel:+1.617.761.6200), LeeF 14:30:53 thanks, Zakim 14:31:00 +Elias_Torres 14:31:08 Zakim, Elias_Torres is me 14:31:08 +EliasT; got it 14:31:13 +Fred_Zemke 14:31:15 +[IBMCambridge] 14:31:23 Zakim, IBMCambridge is me 14:31:25 +LeeF; got it 14:31:28 zakim, who's on the call? 14:31:31 On the phone I see SimonR, AndyS, Kendall_Clark, EliasT, Fred_Zemke, LeeF 14:32:18 Scribe: EliasT 14:32:22 -LeeF 14:32:29 Meeting: DAWG Weekly Meeting 14:32:31 zakim, take up next agendum 14:32:31 agendum 1. "convene" taken up [from kendallclark] 14:32:35 Chair: kendallclark 14:32:44 Zakim, Kendall_Clark is kendallclark 14:32:44 +kendallclark; got it 14:32:45 +[IBMCambridge] 14:32:46 http://lists.w3.org/Archives/Public/public-rdf-dawg/2006JulSep/0236.html 14:32:51 Zakim, IBMCambridge is me 14:32:51 +LeeF; got it 14:33:14 Regrets: none 14:33:33 http://lists.w3.org/Archives/Public/public-rdf-dawg/2006JulSep/0241.html 14:33:34 Present: LeeF, FredZ, kendallclark, LeeF, SteveH, SimonR, bijan, AndyS 14:34:36 zakim, pick a scribe 14:34:36 Not knowing who is chairing or who scribed recently, I propose LeeF 14:34:43 regrets for next time (26 Sept) 14:35:02 I might be unable to attend next week; I'll be at a conference. 14:35:22 I'll be talking about SPARQL to W3C in the UK :-) 14:35:33 +[IPcaller] 14:35:37 zakim, ipcaller is me 14:35:37 +bijan; got it 14:35:41 zakim, mute me 14:35:41 bijan should now be muted 14:36:43 Proposed to skip next week and have the next meeting on Oct 3rd, with AndyS as scribe. 14:37:58 RESOLVED to meet again on Oct 3rd, with AndyS as scribe 14:38:10 zakim, take up next agendum 14:38:10 agendum 2. "action items" taken up [from kendallclark] 14:38:32 http://lists.w3.org/Archives/Public/public-rdf-dawg/2006JulSep/0238.html 14:39:24 zakim, please dial ericP-617 14:39:24 ok, ericP; the call is being made 14:39:25 +EricP 14:39:42 zakim, unmute me 14:39:42 bijan should no longer be muted 14:39:53 zakim, mute me 14:39:53 bijan should now be muted 14:39:57 Elias's action was withdrawn immediately after issued last week 14:41:08 A 14:41:46 http://lists.w3.org/Archives/Public/public-rdf-dawg/2006JulSep/0248.html 14:42:10 Minutes: http://lists.w3.org/Archives/Public/public-rdf-dawg/2006JulSep/0241.html 14:42:33 ACTION: ericP to send mail describing how [VTV] and [BTV] (posted [PST]) illustrate basic graph matching conflicts between LC1 and LC2 semantics [CONTINUES] 14:42:43 ACTION: BijanP to to propose some editorial clarification text around DATATYPE [CONTINUES] 14:42:51 zakim, take up next agendum 14:42:51 agendum 3. "contradictoryKB" taken up [from kendallclark] 14:43:00 ACTION: ericP effect: DATATYE (RDF term) => IRI | "" => xsd:string, ""@foo => error, ""^^X => X, blank node => error, IRI => error [DONE] 14:43:11 ACTION: EliasT to follow up w/ Andy on "the idiom" for plain literals/string literals [DONE] 14:43:20 ACTION: bijan to write some text on the D-entailment issue [CONTINUES] 14:43:23 zakim, unmute me 14:43:23 bijan should no longer be muted 14:44:14 RRSAgent, what are the action items? 14:44:14 I see 5 open action items saved in http://www.w3.org/2006/09/19-dawg-actions.rdf : 14:44:14 ACTION: ericP to send mail describing how [VTV] and [BTV] (posted [PST]) illustrate basic graph matching conflicts between LC1 and LC2 semantics [CONTINUES] [1] 14:44:14 recorded in http://www.w3.org/2006/09/19-dawg-irc#T14-42-33 14:44:14 ACTION: BijanP to to propose some editorial clarification text around DATATYPE [CONTINUES] [2] 14:44:14 recorded in http://www.w3.org/2006/09/19-dawg-irc#T14-42-43 14:44:14 ACTION: ericP effect: DATATYE (RDF term) => IRI | "" => xsd:string, ""@foo => error, ""^^X => X, blank node => error, IRI => error [DONE] [3] 14:44:14 recorded in http://www.w3.org/2006/09/19-dawg-irc#T14-43-00 14:44:14 ACTION: EliasT to follow up w/ Andy on "the idiom" for plain literals/string literals [DONE] [4] 14:44:14 recorded in http://www.w3.org/2006/09/19-dawg-irc#T14-43-11 14:44:14 ACTION: bijan to write some text on the D-entailment issue [CONTINUES] [5] 14:44:14 recorded in http://www.w3.org/2006/09/19-dawg-irc#T14-43-20 14:45:24 DONE: ericP effect: DATATYE (RDF term) => IRI | "" => xsd:string, ""@foo => error, ""^^X => X, blank node => error, IRI => error [DONE] 14:45:24 zakim, mute me 14:45:24 bijan should now be muted 14:45:34 zakim, unmute me 14:45:34 bijan should no longer be muted 14:45:36 DONE: EliasT to follow up w/ Andy on "the idiom" for plain literals/string literals 14:46:27 a p ">"^^rdf:XMLLiteral 14:46:39 a p ">". 14:46:53 p range rdf:XMLLiteral 14:47:48 in SGML, and perhaps XML, '>' is allowed, so '<' may be a better choice 14:48:07 bijan: The only contradiction cases come with data types in RDF. 14:48:18 kendallclark: So if we don't use data types, we have no contradictions. 14:48:33 bijan: data types are built-in to RDF. 14:48:37 hmm, not what I said, but -shrug- 14:48:57 s/data types/entailment/ 14:49:12 kendallclark: If we don't support RDFS then we don't have a contradictory KB issue. 14:49:27 elias? I didn't say that either! 14:49:28 :) 14:49:44 :-) 14:49:49 :) 14:49:51 kendallclark: loves mochi 14:49:54 heh 14:50:22 Straw poll: 14:50:31 1. say nothing about contradictory KBs at all 14:50:51 2. say explicitly that how contradictory KBs are handled is implementation-defined 14:51:27 3. say explicitly what implementatons must do when querying contradictory KBs 14:52:45 FROM FROM A and B get RDF Merged 14:53:00 FredZ: what if two graphs are consistent independently but not merged in the case of FROM FROM 14:54:15 bijan: in RDF Semantics all ill-formed literals are mapped to another resource not of that type to avoid the contradiction. 14:54:59 FredZ: could we throw an error if we find an inconsistency? 14:55:42 SimonR: We would have to use a specific logic to resolve consistencies but that will not happen. 14:56:36 bijan: as I read the SPARQL document, it said that we support D-entailment then we need to say something about contradictions. 14:56:58 patH has joined #dawg 14:57:10 4.8 has been removed. 14:57:27 I de-D-entailed rq24. 14:57:32 :) 14:58:10 +PatH 14:58:19 Present: PatH 14:58:37 sorry im late. 14:58:48 How about: "say explicitly what implementatons MAY do when querying contradictory KBs"? 14:58:50 Present, but late: PatH 14:59:37 audio bad :) 15:00:05 zakim, mute me 15:00:05 bijan should now be muted 15:00:27 bijan, the sound just got better 15:00:49 q+ 15:00:51 zakim, unmute me 15:00:51 bijan should no longer be muted 15:01:04 ack bijan 15:01:31 zakim, mute me 15:01:33 bijan should now be muted 15:02:36 zakim, unmute me 15:02:36 bijan should no longer be muted 15:02:38 sorry, can anyone point out the 1/2/3 options? URI? 15:02:46 zakim, mute me 15:02:49 bijan should now be muted 15:02:53 10kendallclark: 01Straw poll: 15:02:53 10kendallclark: 011. say nothing about contradictory KBs at all 15:02:53 10kendallclark: 012. say explicitly that how contradictory KBs are handled is implementation-defined 15:02:53 10kendallclark: 013. say explicitly what implementatons must do when querying contradictory KBs 15:02:55 RRSAgent, where am I? 15:02:55 See http://www.w3.org/2006/09/19-dawg-irc#T15-02-55 15:02:59 10kendallclark: 011. say nothing about contradictory KBs at all 15:02:59 10[15:50] kendallclark: 012. say explicitly that how contradictory KBs are handled is implementation-defined 15:02:59 10[15:51] kendallclark: 013. say explicitly what implementatons must do when querying contradictory KBs 15:02:59 See that uri 15:03:21 zakim, unmute me 15:03:21 bijan should no longer be muted 15:03:25 That URI is forbidden 15:03:32 zakim, mute me 15:03:32 bijan should now be muted 15:03:39 zakim, who's on the call? 15:03:39 On the phone I see SimonR, AndyS, kendallclark, EliasT, Fred_Zemke, LeeF, bijan (muted), EricP, PatH 15:03:51 patH, on it... 15:04:53 SimonR: 1 would lead to confusion, 3 is too hard right now, so 2 is the closest to what's acceptable. 15:05:27 patH, fixed 15:05:36 Ta. 15:05:40 AndyS: prefers (2) explicitly saying that it's app/imple-defined 15:06:10 Elias: prefer (2) 15:06:29 against 3, OK with 1 and 2 15:07:20 FredZ: (2) only reasonable choice 15:07:37 We'd almost want release the current document as specifying what happens in the case of simple entailment, and perhaps a later extension defining how we deal with stronger entailment regimes, including the issues of inconsistency which then arise. 15:07:50 zakim, unmute me 15:07:50 bijan should no longer be muted 15:08:06 zakim, mute me 15:08:06 bijan should now be muted 15:08:25 bijan: I like 3, but 2 is good since it mentions at least. 15:08:43 ericP: I'm happy with 1 and 2. 15:09:19 looks like 2s have it 15:09:21 patH: 1 dishonest, 3 ambitious and 2 is fine. 15:10:00 I'll take an action to write up a 2 15:10:14 Take a vote then 15:10:45 I'd like to write it into the pub version in section 5 (which can be wordsmithed later like anything else) 15:11:19 sorry, someone at the door 15:11:32 PROPOSED: @@someplace near semantic or implication@@ [[Logical entailment may result in inconsistent RDF graphs. Theresult of queries on an inconsistent graph is implementation-defined.]] 15:11:49 zakim, unmute me 15:11:49 bijan should no longer be muted 15:12:07 "result of queries on contradictory KBs are implementation-defined" Discuss contradictory. Mention possible outcomes as error, nothing, some results. 15:12:12 zakim, mute me 15:12:12 bijan should now be muted 15:12:13 Yep 15:12:17 That's what I had in mind 15:12:23 Bit about RDFS/D-Entailment 15:12:26 also not necessarily the same each time. 15:12:55 Maybe a bit about how future specs might constrain this 15:12:55 PROPOSED: [[Logical entailment may result in inconsistent RDF graphs. Theresult of queries on an inconsistent graph is implementation-defined.]] 15:13:36 I like this because it gives the community a heads up on that it is an issue and implemetners and users some thoughts about what they might do 15:14:11 Do we provide any facility (error code, etc) for the implementation to signal the condition, should it choose? 15:14:21 Can we wordsmith later? 15:14:24 Only error 500 15:14:24 I don't like that 15:14:31 zakim, unmute me 15:14:31 bijan should no longer be muted 15:15:16 zakim, mute me 15:15:16 bijan should now be muted 15:16:06 zakim, unmute me 15:16:06 bijan should no longer be muted 15:17:47 error => "outside the QL spec" 15:18:02 that's been what we've done before. 15:18:36 The only errors mentioned are in the protocol document (and in FILTER evaluations, but that's neither here nor there for this issue), AFAIK. 15:18:43 That's 3 15:19:10 PROPOSED: [[Logical entailment may result in inconsistent RDF graphs. For example, "-1"^^xsd:positiveInteger is inconsistent with respect to D-entailment [INFORMATIVE]. The result of queries on an inconsistent graph is implementation-defined.]] 15:20:13 zakim, mute me 15:20:13 bijan should now be muted 15:21:13 Can we say that it is an error? 15:21:15 (not returns) 15:22:04 Yep 15:22:06 I yeild 15:22:53 As long as we can bulk up the first sentences with some specific mention of RDF and RDFS and pointers to RDFS 15:23:16 zakim, unmute me 15:23:16 bijan should no longer be muted 15:23:23 s/is implementation-defined/is outside the scope of this document/g 15:23:31 What is Eric's example not covering? 15:23:43 bijan: what's the mechanism for returning errors? 15:23:54 ericP: we don't have any mechanisms in the QL for returning errors 15:24:05 ericP: the mechanism is in the protocol. 15:24:20 zakim, mute me 15:24:20 bijan should now be muted 15:25:35 PROPOSED: [[Logical entailment may result in inconsistent RDF graphs. For example, "-1"^^xsd:positiveInteger is inconsistent with respect to D-entailment [INFORMATIVE]. The result of queries on an inconsistent graph is outside this specification.]] 15:27:25 With the proviso that this ought not be intepreted as precluding the possibility of returning errors 15:28:04 "The outcome of a query on a incon..." 15:28:14 The effect of a query 15:28:18 ? 15:28:27 "it might even blow up THE SUN!" 15:28:29 RESOLVED 15:28:48 The results of logical entailment may be outside this specification -- that seems to accurately reflect the situation. 15:29:01 ACTION KendallC: close contradictoryKB issue 15:29:21 zakim, take up next agendum 15:29:21 agendum 4. "formsOfDistinct" taken up [from kendallclark] 15:29:22 I have problems with the phrase 'results of logical entailment', will fix in email. 15:30:12 zakim, unmute me 15:30:12 bijan should no longer be muted 15:30:24 http://lists.w3.org/Archives/Public/public-rdf-dawg/2006JulSep/0200.html 15:30:24 http://www.w3.org/2001/sw/DataAccess/issues#formsOfDistinct 15:30:31 "logical entailment may'//"The use of richer/stronger/other entailment regimes may" (?) 15:31:01 Can we make sure we cover publishing process today? Just to make sure there are no blocks in the next 2 weeks. 15:31:26 Zakim, mute me 15:31:26 EliasT should now be muted 15:32:11 Andy: yes 15:32:21 Ta 15:32:43 http://www.w3.org/TR/2005/WD-rdf-sparql-query-20050721/#modDistinct 15:33:10 zakim, mute me 15:33:10 bijan should now be muted 15:33:40 zakim, unmute me 15:33:40 bijan should no longer be muted 15:33:47 That is also the text in rq24 (I restored an HTML error as I noted). Not sure when it happened. 15:34:23 zakim, mute me 15:34:23 bijan should now be muted 15:34:41 zakim, unmute me 15:34:41 bijan should no longer be muted 15:34:52 zakim, mute me 15:34:52 bijan should now be muted 15:35:14 First choice: 15:35:17 zakim, unmute me 15:35:17 bijan should no longer be muted 15:35:46 zakim, mute me 15:35:46 bijan should now be muted 15:36:07 First 15:36:11 1) one form of distinct 15:36:13 2) more than one 15:36:23 Second if 1) which: 15:36:28 A) term distinct 15:36:32 b) answer distinct 15:36:51 c) source distinct 15:37:02 zakim, unmute me 15:37:02 bijan should no longer be muted 15:40:58 zakim, mute me 15:40:58 bijan should now be muted 15:41:53 zakim, who's on the phone? 15:41:53 On the phone I see SimonR, AndyS, kendallclark, EliasT (muted), Fred_Zemke, LeeF, bijan (muted), EricP, PatH 15:42:14 Which form(s) of distinct do you prefer: 15:42:23 Path: prefer (a), no strong view, will go w/ flow 15:42:31 Eric: (a) 15:42:44 zakim, unmute me 15:42:44 bijan should no longer be muted 15:42:48 Zakim, unmute me 15:42:48 EliasT should no longer be muted 15:43:04 bijan: (a) and (b) 15:43:10 zakim, mute me 15:43:10 bijan should now be muted 15:43:33 Leef: (a) suffices, but sees appeal to (b) and (c) 15:44:18 zakim, unmute me 15:44:18 bijan should no longer be muted 15:44:35 FredZ: ^(c) 15:44:36 zakim, mute me 15:44:36 bijan should now be muted 15:45:09 Ooo, nice point 15:45:14 hadn't thought of that 15:45:17 Elias: (a) 15:45:20 indeed. 15:45:40 Andy: (a) only 15:45:40 that's the danger of wearing the geek hat all the time 15:45:50 Simon: no opinion 15:45:53 (Some examples of B and C: http://www.cs.man.ac.uk/~bparsia/2006/row-tutorial/#slide35 ) 15:45:59 kendall: (a) 15:46:04 zakim, unmute me 15:46:04 bijan should no longer be muted 15:46:09 zakim, mute me 15:46:09 bijan should now be muted 15:46:23 q+ 15:46:31 zakim, unmute me 15:46:31 bijan should no longer be muted 15:47:34 bijan: if we are going to do A, I'd like to have some text that explain it a bit more. 15:48:13 +1 15:48:21 +2 15:48:29 -- 15:48:31 =3 15:48:38 zakim, mute me 15:48:38 bijan should now be muted 15:49:57 suggest it is worth spoending some informative time in spec to get this clear, as its one of the new topics that folk will be having new kinds of trouble with. 15:50:23 yes 15:50:26 Actually, as an artsy fartsy postmodernist, i resist hemogenistic attempst to "limit" the inscription of reality 15:50:35 That's waht I would suggest 15:50:44 zakim, unmute me 15:50:44 bijan should no longer be muted 15:50:50 Ah, I knew I could smell derrida somewhere. 15:50:52 zakim, mute me 15:50:52 bijan should now be muted 15:51:51 http://www.w3.org/2001/sw/DataAccess/rq23/rq24.html#modDistinct is the current text. It uses set= : the = will tie to sameTerm for the RDF tem part of bindings in a set. 15:51:52 zakim, mute me 15:51:52 bijan was already muted, bijan 15:51:55 There's a certain parallel here to our earlier discussions about literals, compared by either syntactic form or by value. 15:52:01 PROPOSAL: To close formsOfDistinct by defining distinctness in terms of term equality, and for BP to provide informative text to guide reader's expectations 15:52:13 "01"^^xsd:integer "1"^^xsd:integer 15:52:14 (i.e. we're debated which sense of equality to use.) 15:52:17 zakim, unmute me 15:52:17 bijan should no longer be muted 15:52:22 q+ 15:52:31 (for the record: our earlier decision re: contradictoryKB also closes that issue) 15:53:02 Ack to the closing thereof. 15:53:08 PROPOSE: to extend meeting 10 minutes 15:53:17 Seconded 15:53:19 thx 15:55:02 For datatyped literals, a binding is equal either if 15:55:12 1) they are term-equal 15:55:26 2) they are = according to the datatype equality defined in value testing 15:56:13 { :x :p 1 } 15:56:19 +3 to that symmetry 15:56:24 if i grok it 15:56:46 3) they are - according to filter equality 15:56:50 "filter equality" 15:57:27 -EliasT 15:58:10 + a zillion 15:58:22 1) they are term-equal 15:58:27 2) they are equal by some other measure 15:58:44 zakim, who's on the phone? 15:58:44 On the phone I see SimonR, AndyS, kendallclark, Fred_Zemke, LeeF, bijan, EricP, PatH 15:58:46 3) both 15:59:55 zakim, mute me 15:59:55 bijan should now be muted 16:00:33 Term-distinct wrt bnodes 16:01:25 zakim, unmute me 16:01:25 bijan should no longer be muted 16:01:29 chnage it to "term/literal value (to be refined)" 16:01:30 PROPOSED: to support some form of term-distinction 16:01:53 PROPOSED: to support term distinctness w/r/t URIs and bnodes 16:02:36 +1 to fred 16:02:47 One of my objections to source distinct 16:02:58 Conceptual 16:03:02 No that wasn't the problem :0 16:03:06 zakim, mute me 16:03:06 bijan should now be muted 16:03:15 PROPOSED: to support term distinctness w/r/t URIs and bnodes, with literals to be decided 16:03:40 RESOLVED 16:03:46 Sorry 16:03:50 I abstain 16:03:51 tyes 16:04:03 RESOLVED, with BP abstaining 16:04:16 ACTION KendallC: to update formsOfDistinct issue to show progress 16:04:44 kendallclark, could you type "RRSAgent, please draft minutes\nRRSAgent, make logs world-access" after you adjourn? i have to run 16:05:14 I am also supposed to "Quick skim" review 16:05:57 possibly? literals are not distinct if the datatype recognizes a normal form and they are the same when normalized (?) Weak but handles Fred-style cases. 16:06:22 Hmm 16:06:44 That seems to work, though I regret that I shall have to spelunk into XML Schema to find out what has normal forms 16:07:07 What else can be done, though? Its really seems to be up to the DT to make this decision. 16:07:14 sure 16:07:16 Eg consider date formats. 16:07:23 I would meet next week jus tto publish 16:07:38 I have removed the DISTINCT issue from the document 16:07:39 me! 16:08:18 I'll need a day to review 16:08:31 OR an hour 16:08:33 or something :) 16:08:41 minute? 16:08:42 I'd like to be there if its a review. 16:08:54 -EricP 16:09:13 It's just supposed to be a sanity check, so I was going to send email message 16:09:20 right 16:09:22 -bijan 16:09:45 RRSAgent, please draft minutes 16:09:45 I have made the request to generate http://www.w3.org/2006/09/19-dawg-minutes.html kendallclark 16:09:51 -LeeF 16:09:55 RRSAgent, make logs world-access 16:09:59 bye 16:09:59 -SimonR 16:10:01 -PatH 16:10:05 -Fred_Zemke 16:10:05 god, i hate a bot you have to say "please" to... that's absurd :) 16:10:06 -AndyS 16:10:19 AndyS has left #dawg 16:10:32 -kendallclark 16:10:33 SW_DAWG()10:30AM has ended 16:10:34 Attendees were SimonR, AndyS, EliasT, Fred_Zemke, LeeF, kendallclark, bijan, EricP, PatH