- From: Said Tabet <stabet@comcast.net>
- Date: Tue, 24 Jan 2006 10:39:14 -0500
- To: <public-rif-wg@w3.org>
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:36:34 UTC