15:41:35 RRSAgent has joined #rif 15:41:35 logging to http://www.w3.org/2009/03/03-rif-irc 15:41:43 zakim, this will be rif 15:41:43 ok, csma; I see SW_RIF()11:00AM scheduled to start in 19 minutes 15:41:53 rrsagent, make log public 15:42:00 rrsagent, make minutes 15:42:00 I have made the request to generate http://www.w3.org/2009/03/03-rif-minutes.html csma 15:42:25 Meeting: RIF telecon 3 March 2009 15:42:33 Chair: Christian de Sainte Marie 15:43:01 Agenda: http://lists.w3.org/Archives/Public/public-rif-wg/2009Mar/0005.html 15:43:35 csma has changed the topic to: 3 March RIF telecon; Agenda http://lists.w3.org/Archives/Public/public-rif-wg/2009Mar/0005.html 15:44:37 Regrets: DaveReynolds LeoraMorgenstern AdrianPaschke 15:45:20 Michael, will you scribe today? 15:46:43 Michael, are you here? 15:58:37 ChrisW has joined #rif 15:58:55 zakim, list agenda 15:58:55 I see 4 items remaining on the agenda: 15:58:57 8. Safeness/Termination [from ChrisW] 15:58:57 9. Lists... [from ChrisW] 15:58:59 10. Test Cases [from ChrisW] 15:58:59 11. AOB [from ChrisW] 15:59:14 AdrianP has joined #rif 15:59:23 zakim, clear agenda 15:59:23 agenda cleared 15:59:30 item+ Admin 15:59:41 agendum+ Admin 15:59:50 agendum+ Liaisons 15:59:51 SW_RIF()11:00AM has now started 15:59:58 +[NRCC] 15:59:59 agendum+ F2F13 16:00:00 rrsagent, make minutes 16:00:00 I have made the request to generate http://www.w3.org/2009/03/03-rif-minutes.html ChrisW 16:00:05 agendum+ Actions 16:00:06 rrsagent, make logs public 16:00:16 agendum+ safeness 16:00:23 agendum+ List data type 16:00:30 agendum+ issue 80 16:00:37 agendum+ issue 92 16:00:38 zakim, [NRCC] is me 16:00:40 +Harold; got it 16:00:42 agendum+ PS 16:00:45 +Sandro 16:00:48 agendum+ AOB 16:01:15 ChrisWelty has joined #rif 16:01:21 +??P3 16:01:35 zakim, who is on the phone? 16:01:35 On the phone I see Harold, Sandro, ??P3 16:01:45 zakim, ??P3 is me 16:01:45 +csma; got it 16:01:54 +[IBM] 16:02:01 zakim, ibm is temporarily me 16:02:01 +ChrisWelty; got it 16:02:22 +Michael_Kifer 16:02:33 scribenick: Michael_Kifer 16:02:39 Scribe: Michael_Kifer 16:02:57 josb has joined #rif 16:05:30 +??P8 16:05:46 Zakim, ??P8 is me 16:05:46 +AdrianP; got it 16:07:02 zakim, who is on the phone? 16:07:02 On the phone I see Harold, Sandro, csma, ChrisWelty, Michael_Kifer, AdrianP 16:07:29 Zakim, mute me 16:07:29 AdrianP should now be muted 16:07:34 next item 16:07:49 + +43.158.801.1aaaa 16:07:50 http://lists.w3.org/Archives/Public/public-rif-wg/2009Feb/att-0122/20090224-rif-minutes.html 16:08:14 PROPOSED: to accept the minutes of Febraury 24 16:08:38 minutes of Feb 24 accepted 16:08:47 RESOLVED; to accept the minutes of Feb 24 telecon 16:10:17 AxelPolleres has joined #rif 16:10:37 next item 16:10:50 +??P11 16:11:16 Gary_Hallmark has joined #rif 16:11:58 +Gary 16:12:16 zakim, who is on the phone? 16:12:16 On the phone I see Harold, Sandro, csma, ChrisWelty, Michael_Kifer, AdrianP (muted), josb, AxelPolleres, Gary 16:12:28 next item 16:14:44 action-709: complete 16:14:44 ACTION-709 Put merged PS on agenda for Mar 3 notes added 16:17:31 action-592: completed 16:17:31 ACTION-592 Open issue based on the White Board line: "What about methods -- Ignore" notes added 16:19:23 next item 16:20:00 http://www.w3.org/2005/rules/wiki/Core#Safeness 16:20:14 Zakim, mute me 16:20:14 AdrianP was already muted, AdrianP 16:20:48 http://lists.w3.org/Archives/Public/public-rif-wg/2009Feb/0065.html 16:23:18 question is whether to take josb's definition or axel's, which is stricter 16:23:45 axel: would prefer to have finiteness as well as safeness 16:24:28 csma: should safety be about termination or about implementability in dialects like PRD? 16:25:21 q+ 16:25:40 axel: worried about systems like DLV (stable models), which do grounding. Therefore, safeness should guarantee that grounding is finite. 16:25:49 q- 16:26:48 axel: might go for 2 definitions: one general, like we have now, and another very strict one 16:27:11 daver probably has an opinion about this 16:32:00 q+ 16:33:36 ack Chris 16:35:59 q+ 16:36:00 the discussion is still about whether we want safeness for core that inplies FININTE models or not. 16:36:08 jos, do you have an idea what DaveR's opinion is (more or less)? 16:36:20 he does not want finiteness 16:36:28 s/FININTE/finite minimal/ 16:36:43 q+ to say I would call it a different dialect 16:36:58 q- 16:37:09 ack sandro 16:37:09 sandro, you wanted to say I would call it a different dialect 16:37:15 i'd be happy to leave safeness where it is, and not make it more strict 16:37:29 axel: strict condition is the common denominator 16:37:47 me too, but I don't have a strong opinion either way 16:38:38 sandro: we want just one safeness cond in core so that all engines will be able to interoperate through Core. 16:39:59 q+ 16:41:09 ack josb 16:44:35 Straw Poll: (+1) go with stricter safeness requiring finiteness, (0) don't care, (-1) stick with current safeness 16:45:30 csma: is there a constituency for less strict (termination)? 16:45:46 All I say is: If we do not restrict finiteness in Core, we are on the safe side for ALL systems. 16:45:53 (-0.1) 16:45:54 not more, not less. 16:46:01 Straw Poll: (+1) go with stricter safeness requiring finiteness, (0) don't care, (-1) stick with current safeness 16:46:09 several: developers of interested systems (eg, DLV) should make an effort to become compliant. 16:46:10 +1 16:46:18 +0 I care, but don't know 16:46:20 0 (don't know yet) 16:46:33 -1 16:46:34 +0.75 16:47:02 chris: -1 allows infinit, +1 disallow infinite 16:47:06 -0.5 16:47:11 -0.5 (without finiteness) 16:47:20 0 Icare but I do not know 16:48:31 possible path forward: add section on finiteness to CORE safety, but label it "AT RISK" 16:48:46 sandro: use the currens (lenient) definition; add axel's restrictions and make them at risk 16:49:43 +1 to add at risk! 16:52:54 PROPOSAL: The issue of finiteness will be At Risk through CR, as we get implementor feedback. We need to know who wants and/or doesn't want this limitation in Core. 16:53:42 PROPOSAL: The issue of finiteness will be At Risk through CR, as we get implementor feedback. We need to know who wants / doesn't want this limitation in Core. (Safeness as defined by Jos not being in question.) 16:53:56 next item 16:56:23 q+ 16:56:57 q+ 16:57:03 ack axel 16:57:34 http://www.w3.org/TR/xpath-functions/#sequence-functions 16:57:38 These lists would not be (potentially non-ground) terms but (always ground) built-in data. 16:57:47 csma: the lists in question are not Prolog-like lists, but a datatype, like xsd lists. 16:58:19 I don't see datatypes as fitting with our current definition of "datatype" 16:58:38 s/see datatypes/lists/ 16:58:52 it would be very useful to retrieve the multivalues of a frame slot as a list 16:59:20 OWL used to have lists more general than built-in data; what about OWL 2? 17:00:16 They are! 17:00:50 q? 17:00:53 q- 17:01:45 xml schema doesn't support lists of lists, I think 17:02:33 (often such flat lists are called sequences) 17:02:36 Can we use rdf:List?s 17:03:16 Yes, I'm very much in favor if (1) we can make it work (2) it wont slow us down too long. 17:03:24 What are the implications for DTB? 17:03:35 I'm looking at: http://www.w3.org/TR/xpath-functions/#sequence-functions 17:03:37 http://www.w3.org/TR/xmlschema11-2/#list-datatypes 17:04:24 why not go back to the earlier effort and introduce list terms (after fixing)? 17:05:27 sandro: I think for Core/PRD we need to disallow variables from lists.... 17:05:27 I think that terms with s dedicated/reserved list constructor function symbol would be the way to go. 17:05:36 I would imagine the only problem is if there are non-ground lists in the head 17:05:49 (unbound variables, of course) 17:06:54 I think the list methods are builtins (externals) and should inherit the same safeness as the other externals 17:06:58 For lists as terms we had http://www.w3.org/2005/rules/wg/wiki/Core/List_Constructor and http://www.w3.org/2005/rules/wg/wiki/Core/List_Constructor-alt 17:08:00 does anyone see how to bind a list to *all* the values of a multivalued frame slot? 17:08:34 Gary, I think this would be a kind of aggregate. 17:08:48 josb_ has joined #rif 17:09:04 proposed: ACTION: Michael draft a proposal for lists that will work in Core (and other dialects) 17:09:46 (In Prolog bagof, listof have been used to collect all elements from a query, which could retrieve all the values of a multivalued frame slot.) 17:09:53 proposed: ACTION: kifer draft a proposal for lists that will (hopefull) work in Core (and other dialects) 17:10:03 ACTION: kifer draft a proposal for lists that will (hopefully) work in Core (and other dialects) 17:10:04 Created ACTION-711 - Draft a proposal for lists that will (hopefully) work in Core (and other dialects) [on Michael Kifer - due 2009-03-10]. 17:10:25 How about: no non-ground lists in the head 17:11:17 works for me, Jos. 17:11:26 next item 17:11:34 issue-80? 17:11:34 ISSUE-80 -- Shoudl we extend DTB to include more general builtins -- OPEN 17:11:34 http://www.w3.org/2005/rules/wg/track/issues/80 17:12:31 q+ 17:13:11 I agree to have literal-no-equal should be symmetric. 17:13:53 q+ 17:13:55 csma: what is special about pred:LiteralEqual? Why don't we have the same problems with pred:LiteralNotEqual 17:14:54 jos: pred:LiteralEqual and pred:LiteralNotEqual should be complimentary. We just haven't defined them 17:15:46 need to go, sorry, bye all! will read the notes on the outcomes of this and follow up per mail if I have additional opinions. 17:15:55 ack josb 17:16:02 q- 17:16:03 http://lists.w3.org/Archives/Public/public-rif-wg/2009Mar/0022.html 17:16:14 -AxelPolleres 17:17:24 josb: XSD distinguishes betw identity and equality (eg, DateTime items can be equal because of different time zones, but they would not be identical) 17:17:49 http://lists.w3.org/Archives/Public/public-rif-wg/2009Feb/0128.html 17:17:56 1) Drop pred:literal-equal 17:17:56 2) Leave pred:literal-equal as is (redundant with RIF =) 17:17:56 3) Redefine pred:literal-equal to perform all the datatype specific equality tests including numeric, and remove those datatype specific tests from DTB. 17:18:39 I strongly prefer option 1) 17:18:58 I would object to 2) unless someone can make a very strong case 17:19:18 option 1 17:19:55 1 or 3 but not 2 17:24:23 1^^int = 1^^float is inconsistent, right? value spaces are disjoint 17:24:32 datetime-equal 17:25:28 +1 option1 17:26:07 which option do you support most? 1, 2 or 3 17:26:10 right Gary 17:26:13 1 17:26:14 1 17:26:24 1 17:26:29 .9 17:26:38 1 i guess maybe maybe 17:27:03 mild pref for 3 17:27:28 object to option 1? 17:27:35 none 17:27:41 object to option 3? 17:27:44 option 3 is complicated 17:27:44 none 17:28:08 and also drop literal-not-equal 17:28:20 PROPOSED: drop pred:literal-equal 17:29:56 my understanding was that we would KEEP not-equal 17:30:06 that wasn't part of the options 1-3 17:31:22 I don't understand why we would keep not-equal, but drop equal. Seems very awkward. 17:32:13 I agree with Jos. Keep both equal and not-equal, or neither 17:32:13 zakim, list attendees 17:32:13 As of this point the attendees have been Harold, Sandro, csma, ChrisWelty, Michael_Kifer, AdrianP, +43.158.801.1aaaa, josb, AxelPolleres, Gary 17:32:16 -josb 17:32:18 -Harold 17:32:20 bye 17:32:23 -AdrianP 17:32:26 -Gary 17:32:30 rrsagent, make minutes 17:32:30 I have made the request to generate http://www.w3.org/2009/03/03-rif-minutes.html ChrisWelty 17:32:31 zakim, list attendees 17:32:31 As of this point the attendees have been Harold, Sandro, csma, ChrisWelty, Michael_Kifer, AdrianP, +43.158.801.1aaaa, josb, AxelPolleres, Gary 17:32:40 rrsagent, make minutes 17:32:40 I have made the request to generate http://www.w3.org/2009/03/03-rif-minutes.html csma 17:32:56 zakim, who is on the phone? 17:32:56 On the phone I see Sandro, csma, ChrisWelty, Michael_Kifer 17:34:51 -Michael_Kifer 17:38:13 -ChrisWelty 17:38:14 -Sandro 17:38:15 -csma 17:38:16 SW_RIF()11:00AM has ended 17:38:17 Attendees were Harold, Sandro, csma, ChrisWelty, Michael_Kifer, AdrianP, +43.158.801.1aaaa, josb, AxelPolleres, Gary 17:43:41 csma has left #rif 18:02:31 Gary_Hallmark has joined #rif