Issue 6617: OCL Constraints                                                                                                                                                                                         (cwmmip-ftf)
Source: Oracle (Mr. John Poole, john.d.poole@oracle.com)
Nature: Revision
Severity: Significant
Summary: The CWM MIP Specification should not force 
implementations to support the Object Constraint Language (OCL).
Resolution:
Replace OCLExpression with a new class called PatternConstraint
that supports a string-based representation of a constraint with no specific 
language requirement. PatternConstraint should include an attribute that
names the constraint language.
Revised text:
PatternConstraint is used to define constraints against the metamodel 
Projection (described below). There is no requirement to use any 
particular constraint language. However, if OCL is used, the OCL 
expression contained by PatternConstraint must be a valid OCL expression 
relative to the modeling context of the Projection.
Action taken:
Corrected in model and in proposed Available Specfication text
Resolution: see above
Revised Text: 
Actions taken:
November 19, 2003: received issue
November 19, 2003: received issue
March 8, 2004: closed issue
Discussion: 
The CWM MIP Specification should not force implementations to support the Object Constraint Language (OCL).
Solution: Change OCLExpression to some other class that supports a string-based representation of a constraint with no specific language requirement.

End of Annotations:=====
WM Metadata Interchange Patterns: Adopted Specification

Issue #1 
Description: OCL Constraints
Source: John Poole (john_poole@hyperion.com)
Nature: Revision
Severity: Significant
Summary:
The CWM MIP Specification should not force 
implementations to support the Object Constraint Language (OCL).
Resolution:
Replace OCLExpression with a new class called PatternConstraint
that supports a string-based representation of a constraint with no specific 
language requirement. PatternConstraint should include an attribute that
names the constraint language.
Revised text:
PatternConstraint is used to define constraints against the metamodel 
Projection (described below). There is no requirement to use any 
particular constraint language. However, if OCL is used, the OCL 
expression contained by PatternConstraint must be a valid OCL expression 
relative to the modeling context of the Projection.
Action taken:
Corrected in model and in proposed Available Specfication text
Discussion: None