- From: Sandro Hawke <sandro@w3.org>
- Date: Fri, 08 Jul 2005 13:29:55 -0400
- To: Anthony Finkelstein <anthony@systemwire.com>
- Cc: Dan Connolly <connolly@w3.org>, public-rule-workshop-discuss@w3.org
Anthony Finkelstein writes:
> Here are some simple stories
>
> Scarlet and Bob work in a large bank. They trade in swaps and
> derivatives. They want to make sure that the swaps they create, that
> are due to settle in Hong Kong, are not set to settle on a date when
> the Hong Kong market is shut due to a national holiday.
>
> Scarlet and Bob also want to know that the party and counterparty
> information is consistent.
>
> Fred and Mary work for an online bicycle shop. They want to ensure
> that the catalogue price of a product is the same as that in their
> syndicated advertisements.
>
> Helen and Xavier are software engineers. They wish to ensure that the
> instances in their UML collaboration diagram correspond to valid
> classes in their class diagram. They also want to ensure that the
> class diagram corresponds the code base and the deployment
> information.
>
> Each of these imply constraints across the information. These
> constraints must be checked to see if they hold.
Thanks for the examples. Just to double check, what is the user
functionality here? Are we talking about constraint enforcement
(validation) or constraint solving (as in CHR [1])? It sounds like
just popping up an error window is fine, and one can just use rules
like: "if not condition then error", perhaps packaged more succinctly
as a list of named conditions. Is that right?
-- sandro
[1] http://www.cs.kuleuven.ac.be/~dtai/projects/CHR/
Received on Friday, 8 July 2005 17:30:04 UTC