1.1 Use Case U1701: Detect equivalent dimensional relationships

If a dimensional relationship has only syntactic changes, these changes MUST NOT be reported (e.g.. the composition of a hypercube has changed or it is divided but the relationships between primary and dimensional elements are the same).

1.2 Use Case U1702: Change to dimensional representation of set of concepts

Change from multiple concepts to shared concept and explicit dimensional representation

FINREP example. Facts represented by primary item ConceptA become represented by ConceptX and Dimension1, Member1, facts represented by primary item ConceptB become represented by ConceptX and Dimension1, Member2, and facts represented by primary item ConceptC become represented by ConceptX and Dimension1, Member3. In this example, the primary items and hypercube dimensional relationship sets of the toDTS is also reported (as a separate relationship-sets event), although not by requirement U1702 (instead this is U1703).

EDINET Example. Facts represented by scenario element <xdt:consolidated> changed to dimension1 member consolidated, facts not represented by segment <xdt:consolidated> are changed to dimension1 member nonConsolidated. As with prior example, an event reporting addition of DRSes representing primary item relationships is provided.

1.3 Use Case U1703: Change to dimensional structure of a primary element

A dimension is introduced to concept X. For the instance aspects model, the concept has a change that it now has a dimension, and for the relationships set model, there is introduction of the primary item dimensional relationship sets.

1.4 Use Case U1704: Change to domain of a dimension

The Country dimension Czechoslovakia member has split into two members Czech Republic and Slovakia.

An aspect model information is provided to note that it is necessary to re-map facts from the prior to subsequent dimensions, but insufficient information is available for conducting such remapping automatically.

1.5 Use Case U1705: Change to typedDomainRef element

The typedDomainRef element has a change to its element complex type definition, adding an attribute, affects aspects model only.

The typedDomainRef element moved to separate file, targetNamespace changed.

Same as prior example but this variation causes namespace change of dimension affecting aspect values for instance fact mapping maintenance.

The typedDomainRef element excludes a value in the toDTS.

In the toDTS, the typedDomain element excludes a name value that was allowed in the fromDTS. (This example was written as if the CR-status xsd 1.1 as of 2009 were used, but would also pertain for an application using formula linkbase or any other approach to validating allowed values of typed domain contents.)

1.6 Use Case U1706: Change to @closed attribute

Change from open to closed

Closed attribute is changed from being absent (defaulting to value false) to closed="true". An extra dimension, NoCubeDim, and its unvalidated member, NoCubeDimMem, can no longer be reported on fact items of primary item ConceptX, so an aspects model change is required to delete this aspect, as well as the relationship-sets model event to note the changed in closedness.

1.7 Use Case U1707: Change to @contextElement attribute

The syntax of the Versioning Report MUST support documentation of any change in the @contextElement attribute value on has-hypercube networks. This change only affects the syntax of the relationship arc, but not the semantic of the aspects model. The reported change is on the relationship set.

1.8 Use Case U1708: Change to @usable attribute value

Change to the usable attribute for a domain member (to false)

A domain member in the hierarchy of domain members has become unusable. The semantic result of this syntactical attribute change is represented by the deletion of aspect for that domain member from aspects model. The syntactical attribute is not represented explicitly in the aspects model, but is recorded as a relationship sets relationship attribute change.

1.9 Use Case U1709: Change to definition of default dimension

Change to the definition of the default dimension (it is moved from Member1 to Member2).

A change in default dimension is reported by the aspect model as it is of significance to the preparer of instance documents, reflecting how the context with default dimension is to be reported, and possibly how the context reflecting the default dimension may be shared with contexts used on facts that do not report this dimension.