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

[RIF][UCR] Action Follow up from last week's telecon --> + text rules

From: Vincent, Paul D <PaulVincent@fairisaac.com>
Date: Tue, 24 Jan 2006 07:56:19 -0800
Message-ID: <B3636F07C8359844A9A2370C5EA08CCBC1AA9A@SRFMSGMB00.corp.fairisaac.com>
To: "Said Tabet" <stabet@comcast.net>, <public-rif-wg@w3.org>

Said - although I would be grateful if [UCR] was to "look after" "non-computation" rules, I suspect that in fact they represent an entirely different categorization, covering also things like "contract exchange without automation" and "request for proposal" tasks, as well as regulatory compliance definitions.

The main "problem" with such rules in RIF is that their use (formal textual descriptions of business rules) is still in its infancy. The OMG SBVR standard covers this, which (AFAIK) had input from techniques such as BR Solutions Rulespeak and ORM.   

I suspect SBVR/non-computation type rules deserve their own use case category and special class of RIF, probably as a concrete implementation of SBVR to W3C standards, and probably as a longer term objective. I will leave the "need" and "format" discussions to Donald, John and their partners and customers!

[This email represents opinion only].

Paul Vincent
Fair Isaac Blaze Advisor --- Business Rule Management
OMG Standards for Business Rules, PRR & BPMI
mobile: +44 (0)781 493 7229 ... office: +44 (0)20 7871 7229 

-----Original Message-----
From: public-rif-wg-request@w3.org [mailto:public-rif-wg-request@w3.org] On Behalf Of Said Tabet
Sent: Tuesday, January 24, 2006 3:39 PM
To: public-rif-wg@w3.org
Subject: [RIF][UCR] Action Follow up from last week's telecon


Dear All,

As discussed in last week's telecon, this email is a follow up to the
discussion on the generalized category of use cases dealing with compliance
and regulations.

Since last week's telecon, we had a proposal for a new abstract usecase
called "Interchange of Human Oriented Business Rules" [see email posted
yesterday January 23rd 2006 by John Hall].

It is my recommendation that the regulatory compliance use case
http://www.w3.org/2005/rules/wg/wiki/Interpretation_and_Interchange_of_Regul
ations becomes naturally an instance of this new abstract usecase. This kind
of support for regulatory compliance has a lot in common with other kinds of
human oriented business rules interchange including contracts and
operations.

This area of application of rules is today a major topic in all companies
especially with laws and regulatory programs such as Sarbanes Oxley, Basel2,
HIPAA, and other Privacy rules. Regulators, Auditors, IT managers,
Developers, Business Analysts, and company principals are all involved in
the lifecycle of the implementation these regulations. There is an
overwhelming need for interchange of compliance rules between new systems,
legacy applications, and between various divisions of large multinational
enterprises. The lifecycle of such rules requires the interchange of rules
at various levels (business level, technical and deployment level, system
level).

Regulatory compliance usecases include scenarios from various vertical
industries such as finance, life sciences, healthcare, energy, and many
others. To the use cases presented with John Hall and Donald Chapin, we can
add scenarios from Insurance where each state (in the USA) has its own rules
and such rules change every single year, and require updates to various IT
systems for enforcement.

      -- Said
Received on Tuesday, 24 January 2006 15:56:28 GMT

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