This is an archive of an inactive wiki and cannot be modified.


The list of requirements reflects the status of the use cases on Friday, February 10, 2006.

List of requirements

(from Situation Assessment and Adaptation)

(from RIF RuleML FOAF)

(from Operationally Equivalent Translations)

(from Enterprise Information Integration)

(from Automated Trust Establishment for eCommerce, Automated Trust Establishment for Accessing Medical Records)

(from Automated Trust Establishment for eCommerce, Automated Trust Establishment for Accessing Medical Records, Organizing a Vacation with Friends, Rule-Based Intelligent Guiding, Rule-Based Email Manipulation, Rule-Based Reactive Organizer)

(from Rule-Based Email Manipulation)

(from Rule-Based Reactive Organizer)

(from Fuzzy Reasoning with Brain Anatomical Structures)

(from Ontology Mapping with OWL and Rules)

(from Distributed e-Learning)

(from Scoped negation, Encapsulation)

(from Frame-based representation, Inheritance of defaults, Reification)

(from Message Transformation)

(from Publication of semantics (e.g. SKOS, RDFS))

(from Refund Policies in E-Commerce)

(from Credit Card Transaction Authorization)

(from Supply Chain Ordering Lead Time)

(from Price Discounting)

(from Policy - Preference Computing)

(from Filling the holes of OWL)

In conclusion, many biomedical ontologies are represented in OWL DL, so a Web rule language should be compatible with OWL DL.

(from SW rules for Health Care and Life Sciences)

(from Internet search: combining query language, rule languages and scoped negation)

(from Rule-Based Combined Access to XML and RDF Data)

An instantiation of this use case was implemented with POSL rules as NBBizKB and tested in OO jDREW. The need to construct such integration rules through iterative refinement with human experts implies the requirement of a human-readable syntax.

In this use case, the identity criterion for businesses across the Web sources is a problem if no URI is provided or URI normalization cannot be done: normalized phone numbers needed to be used in NBBizKB. This implies the requirement to 'webize' the language with URIs and interface it to the newest official URI normalization algorithm.

Given that the same business can be identified in both sources, and assuming it is correctly classified w.r.t. their respective taxonomies, an alignment between the two taxonomic classes can be hypothetically established, which becomes the stronger the more such business-occurrence pairs can be found in both sources. This implies the requirement to combine rules with taxonomies and to permit uncertainty handling, as explored in Fuzzy RuleML.

(from Information Integration with Rules and Taxonomies)

(from Interpretation and Interchange of Regulations)

SLA systems such as the one we implemented for this scenario require not only various types of rules but also rules that can be either static or dynamic.

(from Rule-based Service Level Agreements (SLA) and Web Services)

(from Transfer of rules between different vendor products)

To be effective in handling contracts, RIF must

(from Real-time contract exchange)

(from Managing incomplete information)

(from Classification of Rules w.r.t. their role)

(from Decision making in Health Care)

(from Labeling Brain Anatomical Structures in Digital Images)

(from Automatically generated rules)

(from Rule Based Service Level Management and SLAs for Service Oriented Computing)

(from Rule Interchange Through Test-Driven Verification and Validation)

(from Representing some levels of fuzzy rules with the help of datatype built-ins)

(from Supporting the Reuse of Rules)