W3C home > Mailing lists > Public > public-rif-wg@w3.org > April 2006

RE: [UCR] Design constraints: early example goal/csf hierarchy --> PR / PRR

From: Vincent, Paul D <PaulVincent@fairisaac.com>
Date: Sun, 23 Apr 2006 11:25:05 -0700
Message-ID: <B3636F07C8359844A9A2370C5EA08CCBDEA7A9@SRFMSGMB00.corp.fairisaac.com>
To: "Gerd Wagner" <wagnerg@tu-cottbus.de>, "Bijan Parsia" <bparsia@isr.umd.edu>
Cc: "RIF WG" <public-rif-wg@w3.org>

Gerd - I don't think comparing the state of standardization in current PR systems with HTML is very useful. The latter was defined as a "standard" from the start, for distributed (+ public) internet access. A better analogy would be to complain that the semantics of Java/Java byte code and .NET/CLR are different (and we don't want to open that can of worms).

The reason for PRR and PR in RIF is to share rules across different systems. In time, if the standard is successful, then it may take on some role of leading the semantic definitions for PR engines / use. But there is a long way to go yet! 

PS: I would expect all PR vendors to have well defined semantics for their rule engines. I would not expect RIF to take on the challenge of deciding which particular PR semantic was "correct" - what may be a quirk to one person may be an essential productivity saver to another! 

Paul Vincent
Fair Isaac Blaze Advisor --- Business Rule Management
OMG Standards for Business Rules, PRR & BPMI
ON VACATION TO 24th APRIL
-----Original Message-----
From: Gerd Wagner [mailto:wagnerg@tu-cottbus.de] 
Sent: Thursday, April 20, 2006 10:12 AM
To: 'Bijan Parsia'; Vincent, Paul D
Cc: 'RIF WG'
Subject: RE: [UCR] Design constraints: early example goal/csf hierarchy --> PR / PRR

> So it's worth considering affordances toward homoginization 
> (instead of being completely bound by quirk support).
 
I think this is a very important point, in particular
for production rule systems, which, like HTML, because
of a lack of precise semantics, have developed all kinds
of proprietary quirks. 

Notice that in the case of HTML, the subsequent clean-up 
through the XHTML standard has led the browser vendors to 
support two processing modes: their old quirks mode and
additionally a standards mode that is XHTML compliant
(they recognize the required mode by checking if the
HTML document conatains a corresponding document type
declaration or not).

I think a similar development is desirable for production 
rule systems.

-Gerd

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 Sunday, 23 April 2006 18:25:33 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:33:28 GMT