pub:projects:samurai
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
pub:projects:samurai [2013/01/03 21:54] – wta | pub:projects:samurai [2013/01/10 19:19] (current) – removed kkr | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ~~NOTOC~~ | ||
- | ====== SaMURaI ====== | ||
- | // | ||
- | |||
- | |||
- | <WRAP center round info 60%> | ||
- | {{ : | ||
- | * Preludium 2 NCN Grant no. UMO-2011/ | ||
- | * **Project Manager:** [[pub: | ||
- | * **Scientific Supervisor: | ||
- | * **Start time:** 05.09.2012 | ||
- | * **Duration: | ||
- | * **Budget:** 67 600 PLN | ||
- | </ | ||
- | ===== Motivation ===== | ||
- | The main objective of this project is to propose a new knowledge interoperability formalism for business rules. | ||
- | The motivation for this project involves the fact that existing technologies and languages for rule interchange (e.g. RIF, RuleML, R2ML, KIF) suffer from their general nature and complexity. | ||
- | Hence, their practical support is very difficult. | ||
- | What is more, existing Rule-Based System shells (e.g. CLIPS, Jess, Drools, OpenRules) provide different rule languages, which are merely only a programming solution. | ||
- | Even though the syntax of these languages is precisely defined, they rarely provide any underlying logical interpretation. | ||
- | This research aims at developing a unified business rule representation model which will play a key role in formulation of formalized methods for rule interoperability supported by tools. | ||
- | |||
- | ===== Intended results ===== | ||
- | The most important results of this research include development of the formalized methods for rule interoperability. | ||
- | In this project the following rule languages are considered: CLIPS, Jess, Drools, OpenRules. | ||
- | Nevertheless, | ||
- | From the practical point of view, the project outcome will constitute a semantically coherent knowledge interoperability method for rules, which brings the following advantages: | ||
- | - Unified logical interpretation of the common rule languages. | ||
- | - Unequivocal knowledge exchange between rule language formats. | ||
- | - Improved rule base maintenance methods. | ||
- | |||
- | |||
- | {{tag> | ||
- | |||
- | Go back to -> [[start|projects]] |