This page is about consolidating the work done in the WG regarding requirements and Design Goals and finalising it. It builds upon:
Preliminary work based on the requirements sections from the initial Use Cases;
The requirements listed during the brain storming sessions at F2F2;
The discussion on design goals at F2F2.
As well as the discussion of requirements at F2F3.
The current work focuses on determining Phase II requirements for RIF.
Proposed requirements for Phase II
WG participants should add requirements to the following list and/or champion existing ones.The following information should be listed for each of the proposed requirements: requirement title, requirement statement (short and precise), (optional) link to a short discussion (in case the WG has already discussed the requirement or one of the champions provides explanation or motivation for a requirement), and the list of participants supporting the requirement (i.e. champions).
Full Coverage of RDF
RIF must cover RDF.
Short discussion: ISSUE-14
- Champions:
Full Coverage of OWL
RIF must cover OWL.
Short discussion: ISSUE-15
- Champions:
External Calls
RIF should support external calls (e.g., to query processors).
Short discussion: ISSUE-16
- Champions:
Uncertain and Probabilistic Information
RIF should support uncertain and probabilistic information.
Short discussion: ISSUE-17
- Champions:
Meta-Data for Currency of Rules
RIF should support meta-data for currency of rules.
Short discussion: ISSUE-18
- Champions:
Meta-Data for Executability of Rules
RIF should support meta-data indicating the executability of rules.
Short discussion: ISSUE-18
- Champions:
UML Data
RIF should accept UML instances as data.
Short discussion: ISSUE-19
- Champions:
ORM Fact Model Populations
RIF should accept ORM Fact Model populations as data.
Short discussion: ISSUE-20
- Champions:
XML Representation
RIF representation of XML is XML.
Short discussion: ISSUE-21
- Champions:
- Note: Perhaps similar requirements for RDF and OWL are also meaningful.
Combined Access
RIF should support (rule-based) combined access to different kinds of data (such as XML and RDF data).
Short discussion: the requirement is motivated by use case Rule-Based Combined Access to XML and RDF Data
Champions: PaulaLaviniaPatranjan
Modules
RIF should support modules of rules.
Short discussion: this requirement is motivated by use case Rule Based Service Level Management and SLAs for Service Oriented Computing
Champions: PaulaLaviniaPatranjan
Procedural Attachements
RIF should support user-defined procedural attachements.
Short discussion: this requirement is motivated by use case Rule-Based Email Manipulation
Champions: PaulaLaviniaPatranjan
Priorities
RIF should support means to represent rule priorities.
Short discussion: this requirement is motivated by use case Rule-Based Email Manipulation and Rule Based Service Level Management and SLAs for Service Oriented Computing
Champions: PaulaLaviniaPatranjan
Events
RIF should support means to access data not only stored persistently, but also contained in (incoming) events.
Short discussion: this requirement is motivated by use case Rule-Based Email Manipulation and Rule-Based Reactive Organizer
Champions: PaulaLaviniaPatranjan
Composite Events
RIF should support composite events.
Short discussion: this requirement is motivated by use case Rule Based Service Level Management and SLAs for Service Oriented Computing
Champions: PaulaLaviniaPatranjan
Production Rules
RIF should support production rules.
- Short discussion: this is a high-level requirement, part of the requirement that RIF should support different kinds of rules (motivated by many initial use cases)
Champions: PaulaLaviniaPatranjan
ECA Rules
RIF should support Event-Condition-Action rules.
- Short discussion: this is a high-level requirement, part of the requirement that RIF should support different kinds of rules (motivated by many initial use cases)
Champions: PaulaLaviniaPatranjan