User Tools

Site Tools


api4kb_rules

====== Differences ====== This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
api4kb_rules [2012/10/22 05:13]
apaschke
api4kb_rules [2012/12/09 15:18] (current)
apaschke
Line 2: Line 2:
    * Need to identify a target set of rule languages and rule types (derivation,​ reaction (production,​ ECA, CEP)    * Need to identify a target set of rule languages and rule types (derivation,​ reaction (production,​ ECA, CEP)
    * Need to determine whether support for machine learning, planning, etc. is in scope long term    * Need to determine whether support for machine learning, planning, etc. is in scope long term
-   * Need support for a general rule language interchange (RuleML as general rule interchange language and RIF as specialized Web rule interchange format)+   * Need support for a general rule language interchange ([[http://​www.slideshare.net/​swadpasc/​reaction-ruleml-ruleml2012paschketutorial|RuleML as general rule interchange language]] and maybe RIF as specialized Web rule interchange format ​(only support for basic logic rules))
       * Translate and Load vocabularies       * Translate and Load vocabularies
-      * Execute rules (transformations from the platform-independent interchange format into the platform-specific executable rule language) +      * Execute rules (transformations from the platform-independent ​RuleML ​interchange format into the platform-specific executable rule language) 
-      * Interchange of queries and answers (at a minimum) ​+      * Interchange of queries and answers (at a minimum; supported by  [[http://​www.springerlink.com/​content/​k13040qqqv262882/​|RuleML]]
       * Interchange of rule sets / rule bases       * Interchange of rule sets / rule bases
       * Interchange of proofs       * Interchange of proofs
-      * Interchange of test cases for verification and validation+      * Interchange of test cases for verification and validation ​(see verification,​ validation and integrity testing below)
 Need to see how this connects with the work that is going on for PRR and Decision Management at %%OMG%% Need to see how this connects with the work that is going on for PRR and Decision Management at %%OMG%%
  
-    * Need support for a rule interface description for distributed rule bases (see RuleML)+    * Need support for a rule interface description for distributed rule bases (see [[http://​www.slideshare.net/​swadpasc/​reaction-ruleml-ruleml2012paschketutorial|RuleML]])
       * description of supported semantics       * description of supported semantics
       * description of public signatures which can be queried (derivation rules) or triggered (reaction rules) including ​       * description of public signatures which can be queried (derivation rules) or triggered (reaction rules) including ​
       * description of life cycle management (e.g. descriptive metadata and qualifying metadata, e.g. validity of the rules, rule management in KB etc.)       * description of life cycle management (e.g. descriptive metadata and qualifying metadata, e.g. validity of the rules, rule management in KB etc.)
-    * Need to support rule inference services (looseley-coupled or de-coupled +    * Need to support rule inference services (looseley-coupled or de-coupled
-      * wrap rule inference services into agents (see e.g. RuleResponder) +      * REST services 
-        * agent role models +      * wrap rule inference services into agents ​which communicate via messages ​(see e.g. [[http://​ruleml.org/​RuleResponder/|Rule Responder]] and [[http://​www.slideshare.net/​swadpasc/​reaction-ruleml-ruleml2012paschketutorial|Messaging in RuleML]]
-        * pragmatic primitives for coordination and negotiation (e.g. FIPA ACL primitives) +        * support for agent role models 
-      * description of non-functional properties of the rule service+        * pragmatic primitives for coordination and negotiation ​between agents ​(e.g. FIPA ACL primitives) 
 +      * description of non-functional properties of the rule service ​(see [[http://​ibis.in.tum.de/​projects/​rbsla/​|Rule Based Service Level Agreements]])
     * Need support for validation, verification and integrity (VVI) testing     * Need support for validation, verification and integrity (VVI) testing
       * Verification ensures the logical correctness of a rule base       * Verification ensures the logical correctness of a rule base
       * Validation is concerned with the correctness of a rule-based system in a certain domain or application (e.g. a derived discount of 10% and 5% might be mutual exclusive or might add up depending on the domain/​application)       * Validation is concerned with the correctness of a rule-based system in a certain domain or application (e.g. a derived discount of 10% and 5% might be mutual exclusive or might add up depending on the domain/​application)
       * Integrity (constraints) are a way to formulate consistency (or inconsistency) criteria       * Integrity (constraints) are a way to formulate consistency (or inconsistency) criteria
-      * Uses Test Cases for VVI (see RuleML test cases for VVI)+      * Uses Test Cases for VVI (see [[http://​km.aifb.kit.edu/​ws/​swese2006/​final/​paschke_full.pdf|RuleML test cases for VVI]] [[http://​www.l3s.de/​~olmedilla/​events/​2006/​SWPW06/​programme/​paper_15.pdf|Verification,​ Validation, Integrity of Rule Based Policies and Contracts in the Semantic Web]])
         * Test Cases can be used for testing at design time (test-driven development) and run time (e.g. rule translation and compliance test cases)         * Test Cases can be used for testing at design time (test-driven development) and run time (e.g. rule translation and compliance test cases)
         * Test cases can be interchanged together with rules and          * Test cases can be interchanged together with rules and 
Line 31: Line 32:
           * Test cases can be predefined by experts while rules are written or combined by “normal” practitioners. The test cases then safeguard this latter authoring process.           * Test cases can be predefined by experts while rules are written or combined by “normal” practitioners. The test cases then safeguard this latter authoring process.
           * Test cases are less abstract than the general purpose rules and therefore easier to comprehend for the end user.            * Test cases are less abstract than the general purpose rules and therefore easier to comprehend for the end user. 
- 
- 
  
 ===== Questions ===== ===== Questions =====
    * Enter questions here    * Enter questions here
api4kb_rules.1350897215.txt.gz · Last modified: 2012/10/22 05:13 by apaschke