% file created by excerpting file notes-session-v1.txt by Benjamin Grosof Rules Breakout at DAML PI Meeting April 9, 2003: led by Benjamin Grosof http://www.daml.org/rules ; http://www.ebusiness.mit.edu/bgrosof Notes from the discussion, taken by Benjamin Grosof: (NB: these are not official minutes!) o SEE the OUTBRIEF SLIDES which has lots of stuff - in file rules-breakout+primer+outbrief-v7.* o Some DAML users of rules (people in room): - Massimo Paolucci at CMU working with Katia S.: RuleML rules in matchmaker, with home-grown engine - Stefan Decker: ISI Grid matchmaking: build grid ontologies, background KB eg on compatibility of Operating Systems, matchmaking rules for jobs to services; uses RDF and Triple - Rudi Studer: at U. Karlsruhe: chemical domain and cars domain: model dependencies using frame logic - Sandro Hawke: at W3C: use cwm (has some built-ins) for agenda, meetings, report/summary generation -- maybe could do same in Prolog; have simple form of NAF -- "notincludes", which is lookup-only - Chris Matthews(?name correct): at Versatile Information Systems (with Mitch Kokar): RuleML for domain theory for situation awareness for military, incl. to learn; engine: Snark via Slang - Benjamin Grosof: at MIT Sloan RuleML specification, tools for translation and inferencing, incl. to XSB, IBM CommonRules, Jess (SweetRules and SweetJess); application scenarios in e-contracting (SweetDeal), financial knowledge integration (ECOIN), security/privacy, biz policies - others who were not present during discussion, e.g., Mike Dean at BBN o Common Logic update: [by Pat Hayes] focus is on Simple (v. of) Common Logic abstract syntax, with plan to have the ff. concrete syntaxes: . textbook-y . KIF . XML . Conceptual Graphs . maybe RDF triples also plan to support a subset that corresponds to RuleML o Stefan use cases: types of rule uses include transformation, reaction, integrity constraints, as well as derivation rules Sandro, Benjamin, Stefan: most can be viewed as built upon derivation rules, may be reducible fully to LP/Horn Pat: let's keep it to stuff that gets published or exchanged on the Web o discussion on what is appropriate defn of rules Adam Pease: desire to include any implication, head disjunction we can say: "LP Rules" to be clearer o discussion on layering: Me: can view DL/OWL and FOL/CommonLogic as points in lattice/hierarchy extending RuleML's current lattice/hierarchy o onto and argument roles: problematic to view DL onto as constraints [Ian] can represent a n-ary predicate as a group of n binary predicates - worth exploring [Pat] o Situated LP ideas and issues: - SLP with NAF: does this always produce control-indep, e.g., full WFS; wrt stratified: maybe difference between top-down and bot-up [Michael Kifer] - be clearer: in what sense one can view an OPS5 system as SLP [Michael Kifer] - close relationship of side-effect-free-ness of sensor to W3C's normative principles for GET -type of visiting a webpage, for general Web [Sandro Hawke] - could even try to base RuleML Situated LP on GET and POST [Sandro Hawke] o nonmon: Implicit, vs. explicit persistently named, specification of rest of KB; explicit assumptions about use of nonmon rulebases Overall monotonicity of {KB entails p} relation