Legacy Issue Number: 6618
Source: Oracle ( John Poole)
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.
Relax the conformance statement accordingly.
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.
Incorporated the above revised text into proposed Available Specfication.
Reported: MIPS 1.0b1 — Wed, 19 Nov 2003 05:00 GMT
Disposition: Resolved — MIPS 1.0
Updated: Fri, 6 Mar 2015 20:58 GMT