UCM Dimensions (source use cases / requirements):

1) Semantic Modeling Dimension (the "concept" of the component does not change and becomes more precise)
cardinality
restrictions which narrow the concept
resasons for selection and building a BIE- human rationale for building a BIE
semantic inheritance - needs discussion and definition - path information / propety extension? / etc
packaging design (of the concept)
multi-parent hierarchies
multiple "code lists for context categories"
context processing: logic (and, or) and query/selection
value domain (same and "codelists for datatypes" and identification schemes)
primitives
facets

2) Type/Representation Dimension - restictions (also does not change the concept. Does not make the concept more precise)
syntax binding rules

3) Deployment Dimension (or query result)
state of meaning across messages (UC-12)
packaging design (of the result)
late binding selection on codes (low priority)

Cross - Dimension Aspects:
versionng impacts
editing of classifications
issues similar to Major/Minor (backward compatable) and lifecycle
issues between runtime and dev time



------------------------------------------------
-Transformation (out of scope but consider duing UCM design)

-Meaning of absent elements and default value (UC-12) (out of scope)

-inadequate CCTS 2.X mechanism (CIDX)

-UMM worksheet usage

-architecture
what is at design time
what is at runtime
what is at config
late binding
when representations occur
behaviour/lifecycle