RE: RIF: Fitting PR and RR into logical rules --> data sources

Sandro: good qu. I have been assuming that a DOM could also represent
something like a Java Object Model in many cases. However, in the use
cases, I'd assumed the XML-based object model (eg DOM). 

{Of course, the "object model" could also be mapped into (and out of)
some RDF representation, if required. }

A larger data interchange model (ie how to map different data sources
onto a single model) is, I suggest, outside of the scope of RIF,
although I recall there was at least 1 suggestion for this at the
Washington meeting.

[FYI: typically a PR engine, implemented say in Java, would expect to
deal with Java objects, or objects from non-Java sources that are mapped
into Java. In Blaze Advisor for example, there is the concept of a
Business Object Model Adapter that maps an IT model (Java JAR file, XML
XSD file, CORBA IDL file, DB schema) onto classes, objects, properties,
collections, enumerations etc. The idea is that I can write rules
against such objects, then if necessary substitute one data source for
an "equivalent" different data source, without changing the rules. This
sort of feature is useful in the commercial world where I may use a DB
data source for testing, but a Java data source for production. Also
observe this is a very IT centric view].

Paul Vincent
for Fair Isaac Blaze Advisor  -- Business Rule Management System
@ OMG and W3C standards for rules

> -----Original Message-----
> From: Sandro Hawke [mailto:sandro@w3.org]
...
> 
> (Your message touches a lot on the "Program Data" issue [1],
interfacing
> with Java.  Is that something you're concerned about for phase 1?)
> 
>      -- Sandro
> 
> [1] http://www.w3.org/2005/rules/wg/charter#data-sources0
> 
<snip>
> > [PV>] In a rule engine (ECA/PR), the object model (terms) are
typically
> > predefined, and usually defined externally to the rules (eg in a
Java
> > object model or a XML schema). There is assumed to be some other
> > business process that utilizes the fact that some goods are now
defined
> > as rejected in some subsequent process.
> > >=20
<snip>
This email and any files transmitted with it are confidential, proprietary
and intended solely for the individual or entity to whom they are addressed.
If you have received this email in error please delete it immediately.

Received on Tuesday, 6 June 2006 13:15:31 UTC