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

RE: ISSUE-64 (PICK): Conflict resolution strategies to be covered by PRD? [PRD ]

From: Paul Vincent <pvincent@tibco.com>
Date: Fri, 20 Jun 2008 08:58:54 -0700
Message-ID: <637B7E7B51291C48838F5AE1F2ACA1D714D119@NA-PA-VBE02.na.tibco.com>
To: "Rule Interchange Format Working Group WG" <public-rif-wg@w3.org>


[RIF cannot possibly model every possible conflict resolution strategy,
and indeed rule execution is orthogonal to rule representation and
interchange. So best leave alone, with the exception maybe of optionally
supporting rule priorities, maybe as metadata, to provide guidance to a

On the topic of sequential/procedural interpretation of rules: it would
be nice to avoid precluding such a mode, but it is not a priority /
important for PRD version 1 IMHO. 

Paul Vincent
TIBCO | Business Optimization | Business Rules & CEP

> -----Original Message-----
> From: public-rif-wg-request@w3.org
> On Behalf Of Rule Interchange Format Working Group Issue Tracker
> Sent: 20 June 2008 16:33
> To: public-rif-wg@w3.org
> Subject: ISSUE-64 (PICK): Conflict resolution strategies to be covered
> PRD? [PRD ]
> ISSUE-64 (PICK): Conflict resolution strategies to be covered by PRD?
> ]
> http://www.w3.org/2005/rules/wg/track/issues/
> Raised by: Christian de Sainte Marie
> On product: PRD
> - Some PR languages permit fairly complex conflict resolution
> what conflict resolution strategies should PRD cover?
> - What combinations?
> - Should there be a default strategy, and, if yes: which one?
> - How to notify the intended strategy or combination to the consumer?
> - OMG PRR does not identify specific conflict resolution strategies,
> two operation modes: forward chaining and sequential (but the
> of the semantics makes the forward chaining mode explicitely dependent
> a conflict resolution strategy that is not defined further). Should
> cover some form of a sequential mode and, if yes: which?
Received on Friday, 20 June 2008 15:59:36 UTC

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