R2ML Interchange Principle
F-Logic is a deductive, object oriented database language which combines the declarative semantics and expressiveness of deductive database languages with the rich data modeling capabilities supported by the object oriented data model. The bases for a logic programming language which use objects comes from the early 1986, when Maier, 1986 presents his "logic for objects", O-Logic which was then revisited in Kifer et Wu, 1989 and finalized with the J. of ACM paper of Kifer et al, 1995.
R2ML to F-Logic (Run it!)
F-Logic to R2ML
R2ML to F-LogicXML
The translator is based on the XML Schema provided in Brujin and Kifer, 2004. A white paper will be available.
F-LogicXML to R2ML(Run it!)
A white paper concerning our translation will be available.
- Jos de Bruijn, Michael Kifer, F-logic/XML - An XML Syntax for F-logic, WSMO Working Draft 24 March 2004.
- M. Kifer and J. Wu. A Logic for Object-Oriented Logic Programming (Maier's O-Logic Revisited). In Proc. of ACM SIGACT-SIGMOD-SIGART Symposium on Principles of Database Systems, March 1989, 379-383.
- M. Kifer, G. Lausen, and J. Wu. Logical foundations of object oriented and frame-based languages. Journal of the ACM, 42(4):741-843, 1995.
- D. Maier. A Logic for Objects. In: Preprints of Workshop on Foundations of Deductive Databases and Logic Programming, ed. Jack Minker, Washington DC, August 1986.
- Ontoprise GmbH, F-Logic Tutorial, July 2007.
Jess is a rule engine and scripting environment written entirely in Sun's Java language by Ernest Friedman-Hill at Sandia National Laboratories in Livermore, CA. Using Jess, you can build Java software that has the capacity to reason using knowledge you supply in the form of declarative rules. Jess is small, light, and one of the fastest rule engines available. Its powerful scripting language gives you access to all of Java's APIs.
R2ML to Jess (Run it!)
Jess to R2ML
- Jess Official Home Page, www.jessrules.com.
The RuleML Initiative, started in August 2000 during the Pacific Rim International Conference on Artificial Intelligence (PRICAI 2000). It has brought together expert teams from several countries, including leaders in Knowledge Representation and Markup Languages, from both academia and industry. The RuleML Initiative is developing an open, vendor neutral XML-based language for rule interchange.
R2ML to RuleML (Run it!)
This translator is based on RuleML version 0.9.
RuleML to R2ML (Run it!)
JenaRules includes a general purpose rule-based reasoner which is used to implement both the RDFS and OWL reasoners but is also available for general use. This reasoner supports rule-based inference over RDF graphs and provides forward chaining, backward chaining and a hybrid execution model. A rule set is simply a list of rules. The hybrid execution model allow forward chaining rules to invoke backward chaining rules. The forward rules work incrementally, including incrementally asserting or removing backward rules in response to the data changes. The hybrid execution makes available both forward chaining rules and backward chaining rules in the same session.
JBoss Rules is the supported and branded release of the Drools project. Drools is a Rules Engine implementation, ReteOO, based on Charles Forgy's Rete algorithm.
R2ML to JBoss Rules (Run it!)
JBoss Rules to R2ML
Semantic Web Rule Language (SWRL) based on a combination of the OWL DL and OWL Lite sublanguages of the OWL Web Ontology Language with the Unary/Binary Datalog RuleML sublanguages of the Rule Markup Language.
SWRL to R2ML (Run it!)
R2ML to SWRL (Run it!)
- Ian Horrocks, Peter F. Patel-Schneider,Harold Boley, Said Tabet, Benjamin Grosof,Mike Dean, SWRL: A Semantic Web Rule Language Combining OWL and RuleML.
- Milan Milanovic, Dragan Gasevic, Adrian Giurca, Gerd Wagner and Vladan Devedzic (2006). On Interchanging Between OWL/SWRL and UML/OCL, In:Proc. of 6th OCL Workshop at the UML/MoDELS Conference, OCLApps2006, October 2, 2006, Genoa, Italy.
Object Constraint Language (OCL) is a formal language used to describe expressions on UML models. These expressions typically specify invariant conditions that must hold for the system being modeled or queries over objects described in a model. Note that when the OCL expressions are evaluated, they do not have side effects (i.e., their evaluation cannot alter the state of the corresponding executing system). OCL expressions can be used to specify operations / actions that, when executed, do alter the state of the system. UML modelers can use OCL to specify application-specific constraints in their models. UML modelers can also use OCL to specify queries on the UML model, which are completely programming language independent.
OCL to R2ML (Run it!)
R2ML to OCL (Run it!)
R2ML to XMI (Run it!)
Oracle Business Rules
Copyright © 2006 Some rights reserved.
This page is maintained by Adrian Giurca. Last update March 14, 2007