On Wed, 21 Jan 1998, Tim Showalter wrote:
So the action limitations need to be spelled out in the draft, right?
Advice would be useful. I'm not sure they have to be requirements.
In the case where there's a conflict, what happens? Three possibilities:
* require implementations to reject any script they can't guarantee will
have problems (this is pretty hard)
* take the first/last action specified, and just get on with life
* run-time error, do a keep, then mail the user explaining what happened
I'd say do the actions in order and skip those actions which are illegal
by policy -- generating an email error report to the user for skipped
actions. That seems like the simplist way to do it.
- Chris