14:58:13 RRSAgent has joined #rif 14:58:14 logging to http://www.w3.org/2008/09/22-rif-irc 14:58:24 AxelPolleres has joined #rif 14:58:36 Hi Axel! 14:58:37 Hi! 14:58:47 do we have the Core conf call now? 14:58:59 dial-in number as usual? 14:59:03 Can u try to join with the EU phone number? 14:59:16 the normal code? 14:59:18 Yes, try it. 15:00:09 zakim, who is here? 15:00:09 sorry, Harold, I don't know what conference this is 15:00:10 On IRC I see AxelPolleres, RRSAgent, Zakim, Harold, MoZ, trackbot 15:00:19 DaveReynolds has joined #rif 15:00:47 this is RIF-CORE 15:01:06 zakim, this is RIF-CORE 15:01:06 sorry, Harold, I do not see a conference named 'RIF-CORE' in progress or scheduled at this time 15:01:16 zakim, this is RIF CORE 15:01:16 sorry, Harold, I do not see a conference named 'RIF CORE' in progress or scheduled at this time 15:02:33 maybe one word? 15:02:37 anyway... 15:02:41 zakim, this is RIFCORE 15:02:41 sorry, Harold, I do not see a conference named 'RIFCORE' in progress or scheduled at this time 15:02:55 zakim, who is on the phone? 15:03:03 sorry, Harold, I don't know what conference this is 15:03:04 in the worst case, we can just save and send around the IRClog manually 15:03:15 On IRC I see DaveReynolds, AxelPolleres, RRSAgent, Zakim, Harold, MoZ, trackbot 15:03:55 Zakim, who is on the phone? 15:03:55 sorry, AxelPolleres, I don't know what conference this is 15:03:56 On IRC I see DaveReynolds, AxelPolleres, RRSAgent, Zakim, Harold, MoZ, trackbot 15:04:16 GaryHallmark has joined #rif 15:04:46 Zakim, this is RIF 15:04:46 ok, AxelPolleres; that matches SW_RIF(CORE)11:00AM 15:04:49 zakim, this is RIF 15:04:49 Harold, this was already SW_RIF(CORE)11:00AM 15:04:50 ok, Harold; that matches SW_RIF(CORE)11:00AM 15:05:00 Zakim, who is on the phone? 15:05:00 On the phone I see [NRCC], ??P9, ??P10 15:05:20 +Dave_Reynolds (was ??P10) 15:05:26 Zakim, ??P9 is me 15:05:26 +AxelPolleres; got it 15:05:41 Zakim, who is on the phone? 15:05:41 On the phone I see [NRCC], AxelPolleres, Dave_Reynolds 15:05:47 perfect 15:06:03 + +1.503.533.aaaa 15:07:59 MichaelKifer has joined #rif 15:08:02 scribe: AxelPolleres 15:08:13 scribenick: Axel Polleres 15:08:52 http://www.w3.org/2005/rules/wiki/Core 15:09:06 issues are summarized at: ??? 15:09:21 harold: let's go through the issues. 15:09:36 ... first one: keep membership "#" in core. 15:09:49 + +1.631.833.aabb 15:10:01 Dave: trying to keep it as small as possible. 15:10:05 zakim, who is on the phone? 15:10:05 On the phone I see [NRCC], AxelPolleres, Dave_Reynolds, +1.503.533.aaaa, +1.631.833.aabb 15:10:06 zakim, mite aabb 15:10:08 I don't understand 'mite aabb', GaryHallmark 15:10:13 zakim, mute aabb 15:10:13 +1.631.833.aabb should now be muted 15:10:19 - +1.631.833.aabb 15:10:24 Michael, thanks 15:10:36 it was again a high-pitch noice. 15:10:39 Dave: syntactic suger should rather not be included. 15:10:58 ... similar to but not quite the same as rdf:type. 15:11:12 + +1.631.833.aacc 15:11:22 zakim, mute aacc 15:11:22 +1.631.833.aacc should now be muted 15:11:24 ... preferences for avoiding confusion. 15:11:32 We are discussing Agenda items 15:11:45 Michael, maybe u have to type here. 15:11:56 zakim, aacc is me 15:11:56 +MichaelKifer; got it 15:12:00 Open Core issues [2] and initial PROPOSED resolutions 15:12:06 Can we summarize the diffs between # and rdf:type again? 15:13:18 Michael, re "PROPOSED: Keep membership/subclass in Core", what is the benefit of "(maybe limiting these constructs to rule bodies)"? 15:13:31 Axel: type is ok, only subclass is discussed. 15:15:10 Is it this? When we allow membership/subclass only in rule bodies, # and ## cannot be reDEFINEd. 15:15:12 Gary: main issue is that they are both (subclass/##, membership/#) should not be allowedi n the conclusions 15:15:28 s/edi n/ed in/ 15:15:59 Michael, can u type in something here??? 15:16:34 Gary: datamodels translated into RIF might have memership/subclass (e.g. Java Beans) 15:16:38 I think the benefit is that in PRD the ##/# things cannot be augmented/redefined by rules. 15:17:49 ... datamodel could be translated rather with OWL or an ontology language rather than RIF 15:18:19 Dave: you want membership test in Core? 15:18:35 Thanks, Michael! 15:18:40 ... in a PR setting, you say you can't change membership, yes? 15:18:59 Dave, would you be even less object with such a restriction? 15:19:04 Gary: it is the same status as equal foe me, just as equal. 15:19:21 Dave, would you even less object with such a "(maybe limiting these constructs to rule bodies)" restriction? 15:19:43 Dave: seems reasonable, #/## only in rule bodies. 15:22:01 Axel: BUT rdf:type is the same as #, so we can't allow one and disallow the other in Core. 15:22:41 Dave response to Axel: the use of # is a syntactic restriction only, RDF users could still have rdf:type in conclusion 15:22:46 Dave: Even with the restriction, #/## could still be possibly confused with the similar RDF constructs. 15:22:53 Gary: Not everyone has to implement RDF as their datamodel 15:24:45 Axel: Either #/## in both body and head or nowehere, all other is unclear, if the rdf versions are allowd (rdf:type, rdfs:subClassOf) 15:24:52 Gary: subclass is so rarely used don't require its inclusion in Core 15:25:29 All: Since we are scribing in a distributed manner, "PersonName: ..." (colon) should be restricted to taking notes about what PersonName said. "PersonName, ..." (comma) should be used for addressing PersonName. 15:26:21 "PROPOSED: Keep membership/subclass in Core" 15:26:25 was the original 15:26:30 PROPOSED: RIF Core will not include subclass (##) 15:27:38 PROPOSED: RIF Core will include member (#) but syntactically restricted to use in rule bodies. Note that in RIF-RDF the equivalent property rdf:type would still be permitted in rule heads. 15:27:49 s/to use/its use/ 15:28:30 rationale: PRD rules almost always start with "if p is a person and p.age > 16 and ... then ... 15:29:03 also, almost no PRD system allows ... then p is a person 15:29:36 Dave: In XML syntax we have "member" for # but also rdf:type is allowed. 15:29:42 but ok ... then p.type = "person" 15:29:49 ... so the compromise might work. 15:30:38 Axel: would prefer both allowed, without restrictions. 15:30:48 Gary: would object if they are allowed in conclusions. 15:32:09 Axel: Dave's proposals are fine for me 15:32:20 > > http://www.w3.org/2005/rules/wg/track/issues/71 15:32:20 > > PROPOSED: Core should keep unrestricted equality and external function 15:32:20 > > calls in rule bodies and keep external functions calls in rule heads. 15:32:21 next one issue 71 15:33:43 PROPOSED: Core should keep unrestricted equality and external function and predicate calls in rule bodies and keep external functions calls in rule heads. 15:34:05 Objections? 15:34:11 Seems fine. 15:34:27 (The above PROPOSED for issue 48 was accepted by us here.) 15:34:36 agreed by all. 15:34:53 next one: 15:34:53 > > http://www.w3.org/2005/rules/wg/track/issues/74 15:34:53 > > PROPOSED: Core should keep both frames/objects and 15:34:53 > > (positional-argument) predicates/relations. 15:36:01 Dave: we don't have predicates in RDF, we have to simulate that, but should work. Just frames would be better for us. 15:36:13 ... but I won't gonna object. 15:36:29 Just frames is better for us, too 15:36:47 Harold: Also better for you Gary? 15:37:01 are all these PROPOSED things the ones to be proposed to the WG? 15:37:49 Michael, yes, that's the idea. 15:37:51 ... Is there a standard relation between datalog rules and frames-only? 15:38:08 Gary: I think that's ok. 15:38:16 Gary: should be ok. 15:38:26 Axel: Emulate by introducing new IDs? 15:38:35 Gary: Using Java beans. 15:39:01 Gary: right, new id/object per tuple. 15:39:48 Harold: Should translator be part of the spec? 15:39:50 We could have a 'standard' translation of this kind. 15:40:03 ...(from tuples to object) 15:40:06 "Two-level Core". 15:41:01 Axel: Cannot be part of spec, since eg in RDF u would use BNodes, in Flogic somthing else... 15:41:25 But maybe some Rel-to-Obj mapping. 15:41:30 Gary: A Note, as opposed to a concrete guidance, seems suficient here. 15:41:53 (Like there is a more or less standard Obj-to-Rel mapping.) 15:43:38 PROPOSED: Core should keep both frames/objects and (positional-argument) predicates/relations. 15:43:44 > > http://www.w3.org/2005/rules/wg/track/issues/75 15:43:44 > > PROPOSED: Core should keep disjunction in rule bodies (cf. Gary's UC). 15:46:06 Gary, you would allow then a(X) :- Or( b(X) c(Y) ). ? 15:47:39 axel, no I don't need that case 15:48:49 e.g. if p is a person and p.age < 14 or p.age > 33 or p.smoker = "yes" then ... 15:48:59 Dave: if it is only a syntactic transformation, then fine. 15:49:43 note p is bound outside of the Or (i.e. by a membership 15:50:52 Axel: the issue is safety again, see above rule example, if C(Y) is true then X can be unbound 15:51:01 Strict SafeNESS 15:52:09 Axel: Or in thbodies is strongly related to safeness. 15:52:46 ... I can formulate the various safeness definitions by the F2F, probably, but won't have time before to write it down :-( 15:53:22 PROPOSED: Core should keep disjunction in rule bodies, only if this is permitted by the solution to issue-70. 15:53:30 :-) 15:53:38 -MichaelKifer 15:53:43 > > http://www.w3.org/2005/rules/wg/track/issues/76 15:53:43 > > PROPOSED: Core should keep unrestricted equality in rule bodies (cf. 15:53:43 > > ISSUE-71). 15:53:43 > 15:53:43 > Agreed. 15:54:14 fine... we don't need that anymore. 15:54:29 > > http://www.w3.org/2005/rules/wg/track/issues/70 15:54:29 > > PROPOSED: Parameterize the conformance clauses of Core with 15:54:29 > > safeness requirements "strict", "weak", and "none" (default: "none"). 15:54:53 My clarification: 15:54:53 I meant "strictly-safe" (a), "weakly-safe" (b), and "unsafe" (d) 15:54:53 conformance levels similarly as defined/linked in/from issue 70. 15:54:53 Perhaps a version of Dave's (c) could become another level. 15:56:33 http://www.w3.org/2005/rules/wg/track/issues/70 15:58:07 Harold: to see safeness have to do data flow analysis, which may not always be possible so have to default back to unsafe 15:58:44 I think strict safeness is ok for PRD 15:58:45 Axel: unless binding patterns are declared can't find anything more out. What would be an example? 15:59:05 Harold: if you know the query, the constants in the query would propagate. 15:59:27 Axel: but that is safe *use* of ruleset, not that the ruleset itself is safe 16:00:27 Axel: how would you define weakly safe core without binding patterns? 16:03:23 ACTION: Axel to write down the definitions of strict and weak safety of a ruleset. 16:03:23 Created ACTION-577 - Write down the definitions of strict and weak safety of a ruleset. [on Axel Polleres - due 2008-09-29]. 16:06:03 +MichaelKifer 16:06:37 Michael, can u say something? 16:06:53 Michael, can you type instead? 16:07:02 I only hear the high-pitch noice. 16:07:05 ... on IRC? 16:07:23 BTW: I have not much time left (5-10min) 16:09:28 I am afraid they kick me out of the room in some minutes. 16:10:14 It's called SafeNESS. 16:10:19 Dave: In jena we have both LP style and PR style 16:11:17 probably the stricter the better (but don't forbid disjunction completely) is best for PRD 16:11:42 Michael: binding patterns depend on execution strategy 16:11:54 ... strict safety is ok. 16:12:21 The 'Safeness' discussion seems to move us towards procedural semantics ... 16:14:11 PROPOSED: Core will have a strict safeness restriction. 16:14:46 Dave: would object. 16:15:45 PROPOSED: Parameterize the conformance clauses of Core with safeness requirements "strict" and "none" (default: "none"). 16:17:11 ok, seems we have all, I need to leave! 16:17:24 (modulo nice word for "none") 16:17:31 All agree. 16:17:36 bye! 16:17:48 zakim, make minutes 16:17:49 I don't understand 'make minutes', Harold 16:17:51 -AxelPolleres 16:18:01 RRSAgent, make minutes 16:18:01 I have made the request to generate http://www.w3.org/2008/09/22-rif-minutes.html DaveReynolds 16:19:23 RRSAgent, make public 16:19:23 I'm logging. I don't understand 'make public', DaveReynolds. Try /msg RRSAgent help 16:20:00 RRSAgent, make logs public 16:20:16 RRSAgent, make minutes 16:20:16 I have made the request to generate http://www.w3.org/2008/09/22-rif-minutes.html DaveReynolds 16:20:47 - +1.503.533.aaaa 16:20:58 -[NRCC] 16:20:59 -Dave_Reynolds 16:21:01 -MichaelKifer 16:21:01 SW_RIF(CORE)11:00AM has ended 16:21:03 Attendees were [NRCC], Dave_Reynolds, AxelPolleres, +1.503.533.aaaa, +1.631.833.aabb, +1.631.833.aacc, MichaelKifer 18:27:49 Zakim has left #rif