The assumptions of the RIF Condition Language are structured here following the Phase 1 requirements of the UCR document.
Different intended semantics
RIF must cover rule languages having different intended semantics.
- The Condition Language covers several language dialects
(A. RIF Condition Language) having different semantics for FOL, LP, and production rules (A.6 Semantics).
Implementability
RIF must be implementable using well understood techniques.
The Condition Language syntax is implementable using parser generators such as Jacc; its semantics, using techniques of query languages.
Limited number of dialects
RIF must have a limited number of standard dialects and/or a common core.
- The Condition Language is a common core for a limited number of language dialects
OWL data
RIF must cover OWL knowledge bases as data where compatible with Phase 1 semantics.
- The Condition Language will allow to retrieve OWL knowledge bases as data.
RDF data
RIF must cover RDF triples as data where compatible with Phase 1 semantics.
- The Condition Language will allow to retrieve RDF triples as data.
Semantic precision
RIF must have a clear and precise (unambiguous) semantics to reduce the potential for error in the exchange of rules.
The Condition Language uses model-theoretic semantics (A.6 Semantics).
Standard components
RIF implementations must be able to use standard support technologies such as XML parsers and other parser generators.
The Condition Language's XML serialization has been implemented via Abstract Syntax Trees with the parser generator Jacc.
Translators
RIF must not require rule systems to be changed; it must be implementable via translators.
- Translators to/fro the Condition Language are being explored in RIF Action items.
XML syntax
RIF must have an XML syntax as its primary normative syntax.
- The Condition Language has an XML syntax that can be considered primary.