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

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

From: Adrian Paschke <Adrian.Paschke@gmx.de>
Date: Tue, 24 Jun 2008 18:12:37 +0200
Message-ID: <20080624161237.37520@gmx.net>
To: public-rif-wg@w3.org

We could list the common ones (Gary already listed some in his eMail and there a many other proposal for conflict resolution, e.g. based defeasible , argumentation etc.  ). 

But shall we really define a default one??? That might be easily misunderstood as being normative, i.e. a RIF PRD compliant production rule system must at least support the default semantics for conflict resolution. 

That is certainly not what we want, or?

We could simply say there is a function which resolve certain conflicts in our operational semantics without being specific about it (i.e. refer to the different strategies which are possible).


From: Rule Interchange Format Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Fri, 20 Jun 2008 15:32:43 +0000 (GMT)
To: public-rif-wg@w3.org
Message-Id: <20080620153243.84A5D6B62A@kent.w3.org>

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


Raised by: Christian de Sainte Marie
On product: PRD 

- Some PR languages permit fairly complex conflict resolution strategies: 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, but two operation modes: forward chaining and sequential (but the description of the semantics makes the forward chaining mode explicitely dependent on a conflict resolution strategy that is not defined further). Should PRD cover some form of a sequential mode and, if yes: which?

Psssst! Schon vom neuen GMX MultiMessenger gehört?
Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger
Received on Tuesday, 24 June 2008 16:13:17 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:47:51 UTC