Issue 6618: Conformance Requirements                                                                                                                                                                                (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 entire 
CWM MIP model as a specification conformance point. Rather, implementations should 
be capable of interchanging pattern definitions independently of their capability 
to interchange any metadata that might be described by those patterns. This would 
be an acceptable level of conformance for classes of tools that are focused on 
pattern design activities only.
Resolution:
Relax the conformance statement accordingly.
Revised text:
2.5 Conformance Points
An implementation of CWM MIP must minimally provide the InterchangePattern class
of Figure 2-1, and the following classes of Figure 2-2: PatternConstraint, 
Restriction, BindingParameter, Projection, Semantic Context, and GraphSubset.
This means that implementations of CWM MIP are allowed to interchange pattern 
models only, without necessarily being required to also support the exchange 
of related pattern instances.
2.5.1 Optional Conformance Points
An implementation of CWM MIP may optionally provide the UnitOfInterchange 
class of Figure 2-1, and/or the ModeledSemanticContext and ModeledGraphSubset 
classes of Figure 2-2.
Action taken:
Incorporated the above revised text into proposed Available Specfication.
Resolution: see above
Revised Text: 
Actions taken:
November 19, 2003: received issue
March 8, 2004: closed issue
Discussion: 
The CWM MIP Specification should not force implementations to support the entire CWM MIP model as a specification conformance point. Rather, implementations should be capable of interchanging pattern definitions independently of their capability to interchange any metadata that might be described by those patterns. This would be an acceptable level of conformance for classes of tools that are focused on pattern design activities only.
Solution: Relax the conformance statement accordingly

End of Annotations:=====
ssue #2
Description: Conformance Requirements
Source: John Poole (john_poole@hyperion.com)
Nature: Revision
Severity: Significant
Summary:
The CWM MIP Specification should not force implementations to support the entire 
CWM MIP model as a specification conformance point. Rather, implementations should 
be capable of interchanging pattern definitions independently of their capability 
to interchange any metadata that might be described by those patterns. This would 
be an acceptable level of conformance for classes of tools that are focused on 
pattern design activities only.
Resolution:
Relax the conformance statement accordingly.
Revised text:
2.5 Conformance Points
An implementation of CWM MIP must minimally provide the InterchangePattern class
of Figure 2-1, and the following classes of Figure 2-2: PatternConstraint, 
Restriction, BindingParameter, Projection, Semantic Context, and GraphSubset.
This means that implementations of CWM MIP are allowed to interchange pattern 
models only, without necessarily being required to also support the exchange 
of related pattern instances.
2.5.1 Optional Conformance Points
An implementation of CWM MIP may optionally provide the UnitOfInterchange 
class of Figure 2-1, and/or the ModeledSemanticContext and ModeledGraphSubset 
classes of Figure 2-2.
Action taken:
Incorporated the above revised text into proposed Available Specfication.
Discussion: None