Presentation on theme: "Requirements. UC&R: Phase 1 4.1.1. Compliance model –RIF must define a compliance model that will identify required/optional features. 4.1.2. Default."— Presentation transcript:
UC&R: Phase Compliance model –RIF must define a compliance model that will identify required/optional features Default behavior –RIF must specify at the appropriate level of detail the default behavior that is expected from a RIF compliant application that does not have the capability to process all or part of the rules described in a RIF document, or it must provide a way to specify such default behavior Different intended semantics –RIF must cover rule languages having different intended semantics Embedded comments –RIF must be able to pass comments Embedded metadata –RIF must support metadata such as author and rule name Implementability –RIF must be implementable using well understood techniques Limited number of dialects –RIF must have a limited number of standard dialects and/or a common core OWL data –RIF must cover OWL knowledge bases as data where compatible with Phase 1 semantics RDF data –RIF must cover RDF triples as data where compatible with Phase 1 semantics Rule language coverage –RIF must cover the set of languages identified in the Rulesystem Arrangement Framework. See the Coverage section.Coverage Semantic precision –RIF must have a clear and precise (unambiguous) semantics to reduce the potential for error in the exchange of rules Semantic tagging –RIF must have a standard way to specify the intended semantics (or semantics style) of the interchanged rule set in a RIF document Standard components –RIF implementations must be able to use standard support technologies such as XML parsers and other parser generators Translators –RIF must not require rule systems to be changed; it must be implementable via translators XML syntax –RIF must have an XML syntax as its primary normative syntax XML types –RIF must support an appropriate set of scalar datatypes and associated operations as defined in XML Schema part 2 and associated specifications. See the charter on Datatype support.Datatype support
UC&R: Phase XML data –RIF must be able to accept XML elements as data.
Charter Mission –The Working Group is to specify a format for rules, so they can be used across diverse systems. This format (or language) will function as an interlingua into which established and new rule languages can be mapped, allowing rules written for one application to be published, shared, and re-used in other applications and other rule engines. (req 1.3?, 1.11) Compatibility –Interoperability with the most widely deployed technologies –(MUST) XML data (phase 2) (req 2.1) –(MUST) RDF semantics as a starting point where RIF overlaps with RDF (req 1.9?) –(SHOULD) compatibility with use of SPARQL to query datasets and SPARQL protocol to fetch new datasets –(SHOULD aim at) compatibility with SPARQL use of XML datatypes, functions and operations –(IMPORTANT) compatibility with OWL allowing knowledge expressed in OWL to be used together with rules (req 1.8)
Charter Extensibility Conformance (req 1.1)Conformance –default behaviour (req 1.2) Load and Query –Semantics specified in terms of the result of evaluating the rules –Merging rulesets XML syntax (req 1.15)XML syntax –Translators (req 1.16) –(MUST) syntax must support named arguments (sloted), allowing n-ary facts, rules or queries to be provided via property-value interface Phase 1 semantics will be essentially Horn logicHorn logic –Default behaviour (req 1.2) –(MUST) include a way to express facts as well as rules –(MUST) include meta-data (req 1.4, 1.5) –(SHOULD) consider RDF for meta-data –(MAY) support rulesets Datatype support –(MUST) datatype support including syntax for litterals and a set of common functions and operators, cf XML Schema and XML Query (req 1.16) –(MUST) Phase 1: litterals and some functions and operations for xsd:string, xsd:int, xsd:decimal, xsd:boolean and list structures (req 1.16)