W3C home > Mailing lists > Public > public-rif-wg@w3.org > June 2008

UCR Requirements Text

From: Sandro Hawke <sandro@w3.org>
Date: Tue, 03 Jun 2008 10:52:47 -0400
To: Christian de Sainte Marie <csma@ilog.fr>
Cc: RIF WG <public-rif-wg@w3.org>
Message-ID: <14019.1212504767@ubuhebe>

> *Agenda summary*
> 5. UCR [5] (40 mn)

Some quick thoughts.   Sorry for not getting them out earlier!

> 5.1.3
> It must be possible to create new dialects of RIF and extend existing
> ones upwardly compatible. 

Not very clear.   This is what I think it means:

    It must be possible to create new RIF dialects which extend existing
    dialects (providing backward compatibility) and are handled
    gracefully by systems which support existing dialects (providing
    forward compatibility). 

> 5.1.6 Rule language coverage
> RIF must cover the set of languages identified in the _Rulesystem
> Arrangement Framework_. See the _Coverage_ section.  

Both those links are broken.  How about this:

      RIF (with extensions) must cover all widely-deployed rule

> 5.2.1 Compliance model
> RIF must define a compliance model that will identify
> required/optional features. 

I think this is really a general thing.   And we're using the term
"conformance" not "compliance".  Is this what we mean?

     The RIF specifications must provide clear conformance criteria,
     defining what is or is not a conformant RIF implementation. 

> 5.2.2 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.  

I don't understand this.  I think it's subsumed by 5.1.3, to the extent
I do understand it.

> 5.2.6
> RIF must have a standard core and a limited number of standard
> dialects based upon that core. 

"limited"?   I thought we agreed on "handful".   How about:

   RIF must have a standard core and a small number of standard
   dialects based upon that core. 

> 5.2.7 OWL data
> RIF must cover OWL knowledge bases as data where compatible with Phase
> 1 semantics. 
> 5.2.8 RDF data
> RIF must cover RDF triples as data where compatible with Phase 1
> semantics. 

I don't know what to do with these.  The term "Phase 1" semantics should
go, though...

> 5.2.9 Dialect Identification
> RIF must have a standard way to specify the dialect of the
> interchanged rule set in a RIF document. 

I don't know what this means.    Some possible interpretations (that the
document must include a dialect id string) contradict extensibility and
aren't very useful.

> 5.2.12 Merge Rule Sets
> RIF should support the ability to merge rule sets. 

should => must

> 5.2.13 Identify Rule Sets
> RIF will support the identification of rule sets. (implicit in
> previous requirement)  

will => must

and the bit in parens doesn't make sense to me.

      - Sandro
Received on Tuesday, 3 June 2008 14:53:32 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:07:45 UTC