15:08:12 RRSAgent has joined #rif 15:08:12 logging to http://www.w3.org/2005/12/08-rif-irc 16:17:06 ha-k has joined #rif 16:19:09 hak has joined #rif 16:26:49 Jing has joined #rif 16:36:43 DZHirtle has joined #rif 16:40:12 DZHirtle has left #rif 16:46:50 Hirtle has joined #rif 16:55:26 Jing has joined #rif 16:55:50 ChrisW has joined #rif 16:56:22 csma has joined #rif 16:56:29 sandro has joined #rif 16:56:45 Harold has joined #rif 16:58:47 jos has joined #rif 17:02:17 zakim, who is here? 17:02:17 SW_RIF()11:00AM has not yet started, sandro 17:02:18 On IRC I see jos, Harold, sandro, csma, ChrisW, Jing, Hirtle, hak, RRSAgent, Zakim 17:03:01 Elisa has joined #rif 17:05:20 der has joined #rif 17:05:33 giorgos has joined #rif 17:07:37 jos has joined #rif 17:09:35 phitzler has joined #rif 17:09:54 Scribe: Jos de Bruijn 17:09:59 ScribeNick: jos 17:10:11 Meeting: first RIF f2f 17:10:23 Chair: Christian 17:12:02 ericP has joined #rif 17:12:10 mdean has joined #rif 17:12:56 aharth has joined #rif 17:15:30 Topic: run through of agenda 17:17:36 Christian: we need scribes! 17:17:37 pfps has joined #rif 17:18:32 SW_RIF()11:00AM has now started 17:18:39 +??P3 17:18:49 Bijan: not all inputs in the charter are presented in the background 17:19:26 Christian: all background info will be included in the topics 17:19:29 Zakim, ??P3 is JeremyC 17:19:29 +JeremyC; got it 17:20:01 + +1.650.696.aaaa 17:20:02 Topic: round of introductions 17:20:12 jeremy has joined #rif 17:20:52 Hi, just heard from hotel on Zakim 17:21:17 zakim, who is here? 17:21:17 On the phone I see JeremyC, +1.650.696.aaaa 17:21:18 On IRC I see jeremy, pfps, aharth, mdean, ericP, phitzler, jos, giorgos, der, Elisa, Harold, sandro, ChrisW, Jing, Hirtle, hak, RRSAgent, Zakim 17:22:17 jeremyC, can you hear anything> 17:22:25 hearing very well thankyou 17:23:09 + +1.604.930.aabb 17:24:30 vassilis has joined #rif 17:25:08 bijan has joined #rif 17:26:12 bparsia has joined #rif 17:28:33 On paper 17:29:42 I'm afraid that I cannot find an electronic copy of the list 17:29:55 http://www.w3.org/2005/rules/wg_f2f_1_participants.html 17:29:57 zakim, who is on the phone 17:29:57 I don't understand 'who is on the phone', ChrisW 17:30:00 zakim, who is on the phone? 17:30:00 On the phone I see JeremyC, +1.650.696.aaaa, +1.604.930.aabb 17:30:25 Well, that's a testimony to my inability to find that list 17:30:33 zakim, aabb is meeting_room 17:30:33 +meeting_room; got it 17:31:10 Christian: observers will not be at every meeting; many observers are from OMG; other observers will become 17:31:22 .. members after going through the red tape in their organization 17:31:37 -JeremyC 17:31:52 +1 617 761 6200 conf code RIFWG 17:32:22 +??P1 17:32:36 m has joined #RIF 17:33:16 markus has joined #rif 17:33:56 Topic: W3C process 101, roles and duties in a WG 17:34:23 +Giorgos_Stamou 17:34:32 m has left #RIF 17:34:59 m has joined #rif 17:35:32 Sandro: much of the content overlaps with DanC's presentation in the workshop in Washington in April 17:35:36 JeffP has joined #rif 17:35:46 zakim, loquaciate me 17:35:46 I don't understand 'loquaciate me', bijan 17:37:04 msintek has joined #rif 17:39:58 holger has joined #rif 17:42:56 Current slides: http://www.w3.org/2005/12/rif/process101.html 17:43:07 We are currently on slide 7 17:45:42 Slide 13 17:47:12 sandro's slides (again): http://www.w3.org/2005/12/rif/process101.html 17:47:49 Allen has joined #rif 17:48:11 csma has joined #rif 17:48:29 sandro's slides (again again): http://www.w3.org/2005/12/rif/process101.html 17:49:03 Deborah has joined #rif 17:55:34 Slide 14 17:55:45 I note that this is not a process based constraint on the working group 17:56:57 Even our charter doesn't strictly bound us, since we only need to publish on use case "of interest to the working group". This could be almost none. 17:57:14 Slide 16 17:57:31 Slide 18 17:58:29 slide 7 17:59:06 ChrisW: roles and responsibilities in the WG 18:00:07 .. many differences between how W3C and other standards bodies do things 18:00:22 .. role: director of W3C: TimBL 18:00:45 ... role: WG chairs: Christian and ChrisW 18:00:53 ... tale credit for all the work 18:01:01 ... role: staff contact: Sandro 18:01:22 ... coordinates technical support 18:01:39 ... role: primary and alternate participants 18:02:01 ... any number of people from each organization can join the WG 18:02:16 ... each orgnization nominated one primary member 18:02:33 ... when there is a vote, each organization has one vote 18:02:56 ... the primary is responsible for representing the position of the organization and casting the vote 18:03:29 ... role: observers 18:04:34 ... role of observers not clear to ChrisW 18:04:54 ... members are expected to participate in weekly telecons 18:05:34 ... members are expected to review the documents produced by the WG 18:06:02 Adrian has joined #rif 18:06:05 ... members are expected to contribute to the documents 18:06:16 ... role: editor 18:06:37 ... already editors required for use cases & requirements document and the issues list 18:07:13 ... issues list very important; maintaining is a time-consuming task 18:07:26 ... having a large number of editors on a draft doesn't work 18:07:41 ... there will be a limit of two editors by default 18:08:07 ... role: contributor/author 18:08:41 ... contributors have recognition of efforts w/o being an editor 18:09:02 ... drafts are maintained in the W3C CVS 18:09:30 ... thus, editors need to be willing to use CVS 18:10:02 s/tale/take 18:10:06 ... role: scribe 18:10:17 ... every telecon and f2f is scribed 18:10:47 ... everyone is expected to scribe at some point in time 18:11:00 ... role: invited expert 18:11:15 ... do not represent W3C member organizations 18:11:50 ... Jeff Pan, Ben Grosof and Michael Kifer are invited experts 18:12:11 ... role: task force 18:12:28 But Jeff and Ben are both temporary measures. 18:12:29 ... task force is small subgroup of WG 18:12:52 ... at discretion of chairs 18:12:54 (Aberdeen is joining, and MIT as a W3C host is complicated.) 18:13:15 ... liaison activities 18:13:35 ... there will be liaison positions 18:13:56 ... will be responsible for representing RIF WG in other activity 18:14:14 ... there will be coordination with other W3C WGs 18:14:57 ... for such things as document reviews, requested expertise 18:16:12 -meeting_room 18:16:52 jeremy has joined #rif 18:17:03 jp has joined #rif 18:25:30 Allen has joined #rif 18:25:34 Donald has joined #RIF 18:28:41 edbark has joined #rif 18:38:07 zakim, who is here? 18:38:07 On the phone I see +1.650.696.aaaa, jeremy (muted), Giorgos_Stamou 18:38:08 On IRC I see edbark, Donald, Allen, jeremy, Deborah, csma, holger, msintek, mkroetzsch, bijan, vassilis, pfps, aharth, mdean, ericP, phitzler, jos, giorgos, der, Elisa, Harold, 18:38:10 ... sandro, ChrisW, Jing, Hirtle, hak, RRSAgent, Zakim 18:43:13 Mala has joined #rif 18:45:52 jp has joined #rif 18:47:45 Scribe: Holger Lausen 18:48:01 ScribeNick: holger 18:48:02 zakim, who is on the phone? 18:48:02 On the phone I see +1.650.696.aaaa, jeremy (muted), Giorgos_Stamou 18:48:17 jeremy, girogos, can you hear? 18:48:20 +??P0 18:48:24 Topic: Charter Over view 18:48:26 Slides: http://www.w3.org/2005/12/rif/charter-overview.html 18:48:40 Slide 2 18:48:43 I can hear 18:48:47 zakim, aaaa is Meeting_Room 18:48:48 +Meeting_Room; got it 18:49:07 Sandro: everyone should have read the charter by now 18:49:33 zakim, who is on the phone? 18:49:33 On the phone I see Meeting_Room, jeremy (muted), Giorgos_Stamou, jeremy.a 18:49:47 jeremy? you on two lines? 18:50:20 ... deliberables should be understood by all 18:50:24 Slide 3 18:50:44 ... charter is sort of project plan 18:51:56 -jeremy 18:53:04 JeffP has joined #rif 18:53:10 ... about the history of the layercake 18:53:27 ... rules have been come more important and priminent in that layer cake 18:54:20 ... 2 years ago sandro drafted a charter for a *semantic* rule working group 18:54:38 ... but was not sucessfull, but now ILOG approached W3C for a more broad rule effort 18:57:33 w3c has joined #rif 18:57:37 slide 6 18:57:44 Slide 7 18:58:35 ... 2 phase design was result of to get good scope and fast results 19:00:09 Slide 8 19:00:15 ... phase 2 should be kept in mind but not worry us for now 19:01:37 ... phase 2 may start after candidate recommendation 19:02:26 ... about deadlines: if no results are shown w3c may shut down working group 19:02:36 ... however with good reason extension might negotiated 19:03:51 bijan: are there examples for w3c groups that come to recommendation in 10 month? 19:04:11 Sandro: I am not aware and don't follow other shedules 19:04:52 ... a problem with some working groups is that during livetime they extend feature list 19:05:09 ... should not occur to us since we have 2 phases 19:05:34 bijan: one possability but still very challenging 19:06:01 benjamin: have the same point timeline is very challenging 19:06:29 ... should use use cases for priotorizing 19:06:47 dave: should stick to 2 phase approach 19:07:12 ... and to what is defined in charter 19:07:24 Sandro: phase 1 is to set the ground 19:08:07 benjamin: however priorities of phase 2 requirements might impact phase 1 19:09:16 ChrisW: agrees with Benjamin part of phase 1 is to prioratize what is in phase 2 19:09:45 ... decission what is to be in phase 2 must be done before phase 2 starts 19:10:01 This seems to be proposing to fix the problem with the possible unrealisticness of the schedule by adding *more* and more *contentious* work in phase I. 19:10:09 ^CHrisW^csma^ 19:10:30 Adrian has joined #rif 19:10:44 ... need to agree that phase1 is not really usefull (wrt. features) but sets the ground with architecture and extension mechanism. 19:10:45 Ah, csma puts a stake in the ground against the extra work 19:10:53 THe point: part of Phase 1 is defining Phase 2 19:11:10 q+ to argue for less 19:11:26 ...this will happen along the way, not just at the end 19:11:35 Speaker: Ugo 19:12:14 ugo: w3c process might be slow due to consensus need 19:12:21 +meeting_room.a 19:12:27 ... what is the chairs approach to that? 19:12:36 Sandro: can you be more sepcific 19:13:19 ugo: are you in favour of voting mechanism or are you more in favour of the w3c consensus approach? 19:13:52 ChrisW: most of time only 2 conflicting opinions, will try to reach consensus 19:14:09 however votes are the last method to resolve conflicts 19:14:20 ... in phase 1 I do not expect this necessary 19:14:21 ^ChrisW^csma^ 19:14:55 W3C working groups have "formal votes" and they need not *resolve* issues. Members are allowed to make a formal objection which carry *great weight* against moving to, e.g., LC or CR or REc 19:15:02 sandro: in phase 2 2 solutions might be the outcome 19:16:21 zakim, meeting_room.a is hassan 19:16:21 +hassan; got it 19:16:39 zakim, queue? 19:16:39 I see jeremy on the speaker queue 19:17:20 pascal: necessary to distinct phase1 and phase2 issues. However some phase2 features might be only possible with specific decission in phase 1. 19:17:57 david: own experience with eclipse environment, extensions are driven by the people who extend 19:18:16 ... however designer of the core might not always be aware of the extension possabilities 19:18:28 zakim, ack jeremy 19:18:28 jeremy, you wanted to argue for less 19:18:30 I see no one on the speaker queue 19:18:55 jermey: most people seem to be motivated by phase 2 19:19:31 help 19:19:50 +1 to jermey 19:20:11 ... phase 2 should allow revisit phase 1 19:21:37 csma: use cases are for phase 2 19:22:05 ... phase 1 only shall provide the basis of the use cases and *not* solve them 19:22:11 Slide 9 19:22:33 The Charter: http://www.w3.org/2005/rules/wg/charter 19:22:48 sandro: glossary not mentioned in charter, but should be at least internal glossary 19:23:46 w3c has joined #rif 19:24:22 Slide 10 19:24:36 he said "this is normative, and this is ..." 19:24:37 Tech spec, OWL compat and thats it 19:24:42 OK ta 19:24:53 Use cases and Requer adn TEst cases "have flexibilty 19:25:16 ... real use case for the details 19:25:17 See: http://www.w3.org/2005/rules/wg/charter#deliverables 19:25:46 ... test cases have to prooved to be useful 19:25:57 Slide 11 19:26:04 csma: tomorrow slot about concrete role of usecase and testcases 19:26:30 correction: tomorrow we will discuss use cases 19:26:46 ...not test cases (at least as described on the agenda) 19:26:53 I would like to note that the RDF and OWL tests were *not* designed as confromance tests though the are sometimes used that way 19:26:54 Not conformance tests !!! (my opinion) 19:26:59 :) 19:27:42 sandro: personal note on testcases good to check conformance 19:27:58 ... did this with OWL test cases. 19:28:14 bijan: makes point that test suites are not conformence tests 19:28:34 sandro: yes. They can however clarify 19:29:04 csma: word conformence will be removed 19:29:36 jeremy, you must speak loudly, we can barely hear you 19:29:47 sandro: glossary are about 30 sec. answers 19:29:49 slide 13 19:31:08 slide 15 19:31:54 ... about OWL: anyone wants to discuss it now? 19:32:22 Donald has joined #rif 19:32:32 ... reads charter word by word 19:33:45 csma: stresses "do not reinvent" if something can be done in OWL it should not be dublicated 19:33:50 Slide 14 19:35:23 bijan: is it part of charter to have mapping of n-ary predicates to rdf? 19:35:38 csma: no he did not say that 19:36:46 bijan: should not close down the mapping of n-ary to triples, there are multiple ways. 19:36:59 csma: up to the WG 19:37:10 Mala_Mehrotra has joined #rif 19:37:41 jon: reads out charter section shown on slite 19:38:16 csma: "starting point" does not say too much 19:39:10 from the charter: In order to allow interoperability with RDF and object-oriented systems, the syntax must support named arguments (also called "role" or "slot" names), allowing n-ary facts, rules, and queries to be provided through property/value interfaces. 19:39:29 2.2.4 19:40:00 dieter: need to address rdf anyway 19:40:21 q+ to make process point: chair interprets charter 19:40:22 csma: the question is if the charter prescribes already a certain way of the mapping 19:40:44 ... interprets that it does not 19:41:01 ack 19:41:02 ... suggest that there is no preimposed way to do the mapping 19:43:06 jeremy: chairs are supposed to interpret the charter? 19:43:22 ChrisW: not clear to me what is discussed. 19:43:28 ... lets move on 19:44:05 sandro: compatibility with PRR 19:44:31 To address the other co-chairs puzzlement about the discussion, while no one objected to the point that we must deal with rdf and with nary predicates, the question was whether the *specific method* of encoding nary predicates in RDF was a charter derived constraint, or just one possible approach 19:44:53 Slide 16 19:45:27 slide 17 19:45:31 All done 19:46:00 csma: asks if there is more discussion on charter 19:46:50 benjamin: have a process question - what is the process on how to decide the shedule to be extended? 19:47:59 csma: we will achieve the deadline 19:48:17 ... (said in my role of project manager) 19:49:28 csma: working group is about "rule interchange format" and not "rule language for the web" 19:49:34 ... any bad fealings? 19:49:59 ... someone advertising WRL (points to dieter) 19:50:19 bijan: I do not understand the difference. 19:51:36 csma: question is: do we want a vendor neutral xml format for interchange? Or do we want a language that is directly executed by different engines? 19:51:50 q+ to ask about semantics 19:52:04 peter: I view both to be exactly the same 19:52:31 jeremy: disagrees and sees both as different things 19:53:17 I would like to point out that we should avoid the "Semantic Web" part of the analogy 19:53:28 ... just identifying the space we are working in. 19:53:44 I.e., Peter just meant, I think, that developing a Rule Interchange Language requires developing a Rule Language 19:54:08 s/Rule Interchange Language/Rule Interchange Format/ 19:54:19 ... to exchange rules in a common format and not to design a new language 19:54:43 wasn't me speaking above 19:54:58 Was it...hassan? 19:55:16 who was it? 19:55:47 not me 19:55:52 q- 19:55:54 It was me - Hassan Ait-Kaci 19:57:33 Edd: issue is weather the interpretations are well enough defined such that the interachange and the extension do not modify the interpretation 19:58:29 dieter: Should not include all features but apply the 80/20 rule to include 20% feature to achieve 80% 19:59:49 q+ to illustrate raising hand on IRC 19:59:56 q- 20:00:02 well done 20:00:38 joshua: the tricky part is not to design some particular features, but to identify overlaps and concrete interpretations and to characterize the difference between concrete rule language 20:01:08 csma: closes session 20:01:10 -hassan 20:01:37 s/Edd/Ed 20:01:44 msintek has left #rif 20:02:01 -jeremy.a 20:03:31 PaulV has joined #rif 20:07:58 quit 20:16:07 Hirtle has left #rif 20:46:47 -Giorgos_Stamou 20:47:35 der has joined #rif 20:50:18 giorgos has joined #rif 20:56:19 +Sandro 20:56:52 -Sandro 21:00:16 Jing has joined #rif 21:00:40 +??P3 21:00:54 sandro has joined #rif 21:02:38 phitzler has joined #rif 21:02:54 markus has joined #rif 21:02:56 Mala_Mehrotra has joined #rif 21:03:05 earlier could you hear hassan better than me? 21:03:17 was problem my end or yours? 21:04:43 msintek has joined #rif 21:05:44 jos has joined #rif 21:06:02 ChrisW has joined #rif 21:06:08 +hassan 21:06:12 I thought it was pretty similar 21:06:30 ahh, i could hear hassan really well 21:06:36 ugo has joined #rif 21:06:43 so problem was your end 21:06:46 bijan has joined #rif 21:08:01 Allen has joined #rif 21:08:19 Donald has joined #rif 21:08:20 aharth has joined #rif 21:08:35 hirtle has joined #rif 21:09:32 GaryH has joined #rif 21:09:37 csma has joined #rif 21:10:15 PaulV has joined #rif 21:10:35 Scribe: Dave Reynolds 21:10:45 ScribeNick: der 21:10:47 mdean has joined #rif 21:10:48 Elisa has joined #rif 21:11:00 holger has joined #rif 21:11:15 Topic: History of KR standardization, Ben Grosof 21:11:29 Slides: to be posted 21:13:16 jp has joined #rif 21:15:27 hirtle has joined #rif 21:15:34 Highlighting CLIPS syntax as a de facto rule interchange, at least in past 21:15:46 ? is there a link to this presentation? 21:16:10 Not yet, to be posted 21:16:17 as in, after the talk? 21:16:23 k tnx 21:17:15 ChrisW has left #rif 21:17:23 ChrisW has joined #rif 21:17:36 +??P25 21:20:37 I would like to point out that I find much of this presentation tendentious 21:23:35 Bijan corrects SWRL comments on implementation - there exists a non-FOL reasoner, non-LP implmentation, Kaon 21:23:47 I guess it depends on what you mean by "non-LP" 21:23:55 tendentious: Marked by a strong implicit point of view; partisan: a tendentious account of the recent elections. 21:24:16 while your at it define "inference" 21:24:22 ^Kaon^KAON2^ 21:24:38 vassilis has joined #rif 21:24:39 I mean, KAON2 works by a (somewhat complex) reduction to positive disjuctive datalog 21:24:45 giorgos has joined #rif 21:24:50 But this is very difference than, say, AL Log 21:25:06 very different 21:25:41 What I mean is that KAON2 implements a direct decision procedure for a rather expressive subset of SWRL (namely DL Safe SHIQ rules) 21:26:45 KAON2: http://kaon2.semanticweb.org/ 21:32:42 [slides on semantics and examples, inferencing, ontology, skipped over, not presented] 21:32:48 JeffP has joined #rif 21:32:58 ugo has left #rif 21:35:32 Sandro: use some of material as basis for glossary? Benjamin maintain? 21:35:41 Deborah has joined #rif 21:35:41 BG: depends 21:36:04 Topic: W3C recommendations of relevance, Sandro 21:36:36 sandros slides: http://www.w3.org/2005/12/rif/glossary_w3c.html 21:38:46 slide 7 21:39:41 Bijan: why is web arch relevant, given RIF charter is for interchange? 21:40:29 Sandro: e.g. use of URIs etc as in RDF and OWL is part of this group's charter 21:41:26 Bijan questions how formally Sandro represents tbl and DanC 21:42:37 PPS: points out that people who know XSD are likely confused by it, e.g. xsd:duration 21:42:59 s/PPS/pfps/ 21:44:51 -jeremy 21:45:09 oops 21:45:26 +??P3 21:45:36 [not as scribe: I think S in SPARQL is Simple, at least according to some members] 21:45:46 zakim, who is on the phone? 21:45:46 On the phone I see Meeting_Room, hassan, ??P25, jeremy 21:46:37 jos has joined #rif 21:47:20 [der see: http://lists.w3.org/Archives/Public/public-rdf-dawg/2005JulSep/0345.html and http://en.wikipedia.org/wiki/SPARQL 21:47:34 Harold: MathML is good for describing functions 21:47:48 zakim, ?p25 is PedramAbrari 21:47:48 sorry, ChrisW-alt, I do not recognize a party named '?p25' 21:47:57 zakim, ??p25 is PedramAbrari 21:47:57 +PedramAbrari; got it 21:48:09 .. a sub-initiative might be logical fns in MathML for user defined functions 21:49:25 Topic: Harold Boley, glossary entries 21:49:47 Anyone know the URL for the slides? 21:58:30 Slides presented by authors of each entry - MK for f-logic, Mike Dean for SWRL, Jos for WRL 22:01:04 Igor 22:01:20 ChrisW points out we treat these languages as examples of this that must interoperate, not as languages to argue over 22:01:31 s/this/things/ 22:01:48 .. just covered web rule languages in this section 22:02:22 Discussion on how to do interchange w/o defining "a language" 22:03:01 Grosof: need "X language" terminology where X can be .. 22:03:08 Execution Language 22:03:08 Authoring Language 22:03:08 RDF Encoding Syntax 22:03:08 Concrete Syntax 22:03:08 Abstraction Sytnax 22:04:04 Jos: horn logic used ambiguously - subset of FOL v. LP 22:06:59 Topic: Chris Menzel, Common Logics 22:07:50 What was especially strange is the interpretation of Harold of Datalog. All model-theoretic definitions of Datalog in the literature are based on minimal Herbrand models and *not* first-order models 22:08:20 ChrisW: introduces CL, owl & rdf embedding, not kif but descended .. 22:08:40 .. has formal semantics which we will need too 22:10:41 Harold has joined #rif 22:13:09 As I mentioned in the glossary overiew, the current entries give a top-level characterization. 22:14:26 (laughter at KIF example's english being amusingly different from KIF version) 22:14:26 Further distinctions such as FOL vs. LP semantics should be added for Datalog, Horn logic, and (indeed) for more expressive languages. 22:16:55 Slide on KIF is first order provokes discussion on whether it is really fully expressable in first order 22:17:31 cm's conclusion: KIF maybe isn't needed any more, if every tool starts working with RIF 22:21:19 I think we need a different name for the function-free subset of Horn logic (with safety condition) 22:21:46 Using "Datalog" is IMHO not clear 22:21:46 a name other than "datalog" ? 22:21:48 interesting. 22:22:20 Yes, because Datalog is based on minimal model semantics, whereas Harold also wanted to describe first-order semantics 22:22:33 In that case we should probably also avoid "Datalog" because it's ambiguoug as to semantics. Depending on whom you ask. 22:23:02 practical solution is to make it a practice to always state which semantics you mean 22:23:06 Maybe we should start using citations when talking ;) 22:24:04 Yes 22:26:48 How and when will the glossary be published? It would be helpful to have this common terminology asap. 22:28:19 My suggestion is people put it into the RIF Wiki as quick as they can. 22:28:37 URI of the RDF wiki? 22:28:56 http://www.w3.org/2005/rules/wg/wiki/ 22:32:32 Slide on CL's ability to allow syntactic restiction .. 22:32:53 .. Dieter asks for clarification how the integrity constraint works 22:33:10 .. see Pat Hayes for more details on that 22:33:11 GaryH has joined #rif 22:34:09 .. dialect is purely syntactic notion (but has semantic implications) 22:34:42 zakim, who is on the phone? 22:34:42 On the phone I see Meeting_Room, hassan, PedramAbrari, jeremy (muted) 22:35:36 How do we organize discussion around entries in the glossary? Email or in-line comments in the Wiki? 22:36:08 That's a tendentious claim! 22:36:23 (That first order roughtly means "compact") 22:36:53 \me as a non-native speaker wonders what 'tendentious' means 22:37:34 tendentious: Marked by a strong implicit point of view; partisan: a tendentious account of the recent elections. 22:37:38 from Meriam webster: marked by a tendency in favor of a particular point of view : BIASED 22:38:08 It has a strong connotation of "contentious" or "controversial" 22:38:34 It is not usually, at least in my usage, a pejorative *per se* 22:39:16 Sandro: would xcl dialect restricted to horn fit with RIF phase 1? 22:39:33 cm: yes 22:39:54 cm: I think so ... not sure what exactly you need 22:40:10 pfps: CL with equality won't be horn .. 22:40:34 "A Horrocks Sentence" 22:41:29 .. cm: use dialect restrictions to prevent the punning which the pseudo-higher order allows 22:42:43 "It depends what you mean by 'having a different meaning'" :-) 22:43:25 (CM and PFPS going on.... we beyond what most of us are following.) 22:44:50 Harold: SCL ... CL ? 22:45:11 CM: SCL was an unnecessary diversion that has been channeled back into CL 22:45:11 SCL? cm: unnecessary diversion, all channeled back into CL 22:46:20 Dieter: can you express transitive closure? 22:47:00 A Horrocks sentence is something like (forall x forall y x=y) implies (Pa implies Qb) 22:47:11 .. cm tries to clarify question ... taken off line 22:47:12 People on the phone: please get on the queue by saying "q+' on IRC 22:47:16 This is an axiom in CL but not in FOL 22:47:23 It is also an FOL sentence 22:48:24 There was a question for the CL Website. It is http://cl.tamu.edu/ 22:48:38 mk: (refering to Dieter question) can't express that one relation is a transitive conclusion of another 22:48:40 kifer: to express that one relationion is a transitive closure of another relation 22:48:56 s/conclusion/closure/ 22:49:00 Consider the following rule: x=y 22:49:30 This brings up divergences between FOL and CL 22:49:37 kifer: is not possible in FOL 22:51:05 -hassan 22:51:13 -jeremy 22:51:36 quit #rif 22:52:21 If I understand it correctly, the sentence is an axiom in CL, because x=y ensures that P and Q are actually interpreted as the same relation; is this correct? 22:55:40 ircleuser has joined #rif 22:56:29 23:06:13 JosD has joined #rif 23:18:29 + +aacc 23:18:37 ekw has joined #rif 23:20:01 +hassan 23:20:47 phitzler has joined #rif 23:23:43 in response to jos: yes 23:23:52 MarkusK has joined #rif 23:24:38 scribe: Mike Dean 23:24:39 PaulV has joined #rif 23:24:59 Topic: Christian: tomorrow's schedule 23:25:15 morning: 1 use case per person 23:25:48 pet use cases, not necessary real - why you think RIF is interested/needed 23:26:00 interests of everyone, plus useful base 23:26:10 5 minutes/person 23:26:33 maybe we'll all have the same idea and be done very fast :-) 23:26:53 in afternoon, take a few more elaborated use cases (e.g. from email list) 23:27:11 identify candidates for Use Case and Requirements document 23:27:22 what's needed, etc. 23:27:24 JosD has joined #rif 23:27:48 dissect case to see what is useful, missing 23:27:54 shopping list of what we want in use cases 23:28:35 random selection or ask for volunteers (cadavers) 23:29:24 homework for tonight: synthesize/consolidate use cases 23:29:57 call for volunteers now 23:30:33 volunteer for what, exactly? 23:30:41 the "homework"? 23:31:17 Harold Boley, Dave Reynolds, Paul, Benjamin, Vassilis, Mala, Bijan, Uli 23:31:25 I didn't volunteer 23:31:34 I volunteered uli 23:31:37 sorry 23:31:54 +Paula 23:31:57 -Paula 23:32:02 Volunteers Paula 23:33:15 morning will be more personal 23:33:31 no prescribed format initially 23:34:01 Christian removes hat to present a few PRR glossary entries 23:34:08 -jeremy 23:34:18 and OMG standards 23:34:41 Ahh - my call got dropped, but I'm flaking anyway 23:34:59 ok - g'nite then? 23:35:01 I think I'll go to bed, and not redial ... see you all tomorrow 23:35:13 5 entries: meta-model, production rule, PRR, SOA, JSR 94 23:35:30 slides presumably to be made available 23:35:48 ciao, Jeremy! 23:36:06 meta-model is the ontology for a model 23:36:09 extends UML 23:36:24 no definition of meta-model in OMG literature :-( 23:37:55 pfps skeptical of rule language ontology 23:38:32 Now *that* is contentious :) 23:39:03 OMG MOF, UML, and other standards are relevant to meta-models 23:39:56 ?: translation between rule languages if they share meta-model? 23:40:12 syntax only? 23:40:23 christian: no, semantics too 23:40:38 barkmeyer: some confusion even within OMG 23:40:43 ^?^Pascal Hitzler^ 23:40:49 thanx 23:41:14 barkmeyer: mapping between meta-models 23:41:32 christian: that's what is meant by sharing 23:41:43 grosof: sweetrules translations, e.g. jess to xsb 23:42:02 grosof: distinctions necessary to handle, e.g. negation, properly 23:42:20 back to briefing slides 23:42:28 slide: production rule 23:42:56 consequent is action or list of actions 23:43:23 couldn't find statistics - but major vendors have 1000s of active customers 23:43:38 users demanding standard rule interchange format 23:43:50 vendors willing to implement 23:45:14 slide: PRR 23:45:23 Production Rule Representation 23:45:35 under specification at OMG 23:45:51 JeffP has joined #rif 23:46:08 follow link to PRR Core UML diagram 23:47:31 provides operational semantics not logic 23:48:56 PRR support not much of a constraint 23:49:50 defining PRR OCL (constraint language) 23:50:48 translation to/from IRL and OCL via meta-models 23:51:10 Bijan: what are constraints expressed in UML diagram? 23:51:20 Evan: constraints are separate package 23:51:32 weaker than Z 23:52:01 OCL = Object Constraint Language 23:52:32 Paul: extension to OCL for rules 23:52:53 ?: difference between production rule and rule? 23:53:06 not every rule is a production rule 23:53:32 color on diagram is slightly different (hard to see) - provides for future extensions (other classes of rules) 23:53:33 q+ 23:54:14 PRR white paper in January 23:54:24 slide: SOA 23:54:29 q- 23:54:35 Service Oriented Architecture 23:54:41 end of OMG definitions 23:55:11 large class of use cases 23:55:41 RIF must be able to refer to web service as procedural attachment 23:55:51 Slide: JSR 94 23:55:58 informative, not constraining 23:56:25 RIF would be standard rule language for JSR 94 23:56:39 part of the motivation for vendors to implement RIF 23:57:08 no apparent impact on design of RIF 23:57:54 Slide: SBVR 23:58:13 who is speaking? 23:58:18 Donald Chapin 23:58:25 Where are his slides? 23:58:40 not posted yet 23:58:51 Semantics of Business Vocabulary & Business Rules 23:58:59 Business Modelling and Integration Domain Task Force 23:59:08 OMG ^^ 23:59:22 "Semantic Beaver" (SBVR)