Issue 2181:  Specify the semantics of Constraint verification (mof-rtf)
Source:  (, )
Nature:  Revision
Severity:  Significant
Summary: Summary: We need a thorough specification of the semantics of Constraint 
 verification. This should cover the following:
   1) What happens; e.g. is the verification allowed to give up on the 
      first error? 
   2) When evaluation of deferrable Contraints can occur; i.e. where could 
      the ConstraintError exceptions be raised?
   3) How evaluation of deferred Constraints is triggered. 
 
 

Resolution: 
Revised Text: 
Actions taken:
November 6, 1998: received issue
July 23, 1999: deferred to new RFP
Discussion: 
The specification should cover:
1. What happens; e.g. is the verification allowed to give up on the first error?
2. When evaluation of deferrable Contraints can occur; i.e. where can the Constrain-tError
exceptions be raised?
3. How evaluation of deferred Constraints is triggered. One possibility is to tie this to
one or more Operations in a meta-model. If so, how do we meta-model this?
It is assumed that we want verification semantics that work for Constraints on all meta-models,
not just for Constraints on MOF Model.
Cross reference Issue 1082
Status: Beyond RTF scope - except for specific clarifications. Deferred to MOF 2.0; Desir-able
feature..
Implementation: A description of what is not currently specified is in Section , “Con-sistency
Checking Mechanisms,” on page 2-18. Also mentioned in
Section 4.6, “Extents,” on page 4-9. Done. [SC] The specification should cover: 

What happens; e.g. is the verification allowed to give up on the first error? 
When evaluation of deferrable Contraints can occur; i.e. where can the Constrain-tError exceptions be raised? 
How evaluation of deferred Constraints is triggered. One possibility is to tie this to one or more Operations in a meta-model. If so, how do we meta-model this? 
It is assumed that we want verification semantics that work for Constraints on all meta-models, not just for Constraints on MOF Model. See also Issue 1082
End of Annotations:=====
Return-Path: <crawley@dstc.edu.au>
X-Exmh-Isig-CompType: unknown
X-Exmh-Isig-Folder: inbox
To: mof-rtf@omg.org, issues@omg.org
Errors-to: request@omg.org
Subject: Specify the semantics of Constraint verification
Date: Fri, 06 Nov 1998 15:49:37 +1000
From: Stephen Crawley <crawley@dstc.edu.au>


["new issue 12" from Seattle RTF doc.]

Source: DSTC (Dr. Stephen Crawley, crawley@dstc.edu.au)
Nature: Revision
Severity: Significant
Summary: We need a thorough specification of the semantics of
Constraint 
verification. This should cover the following:
  1) What happens; e.g. is the verification allowed to give up on the 
     first error? 
  2) When evaluation of deferrable Contraints can occur; i.e. where
could 
     the ConstraintError exceptions be raised?
  3) How evaluation of deferred Constraints is triggered. 

Additional text:

One possibility for triggering deferred Constraint evaluation is to
tie this function to one or more Operations in a meta-model. If so,
how do we meta-model this?

It is implicit that we want verification semantics that work for
Constraints on >>all<< meta-models, not just for Constraints on MOF
Model.