Rule Name: Distinct Link Objects

Definition

Under any single Aggregate Feature, the link objects must have non-identical discriminators.

Under any single Topology Hierarchy, the link objects must have non-identical discriminators.

Under any single Aggregate Geometry, other than Separating Plane Related Geometry, the link objects must have non-identical discriminators.

Under any single Feature Model Instance, the Feature Instance Template Indices must be distinct.

Under any single Geometry Model Instance, the Geometry Instance Template Indices must be distinct.

Rationale

Discriminators must be distinct in order to allow the user to discriminate between the branches they represent.

However, this does not apply to link objects that exist only to specify sides of a Separating Plane.

For model instances, the indices into the Interface Template must be distinct because no Variable can be set to more than one value at a time.

Example

  1. For a <Level of Detail Related> aggregation, no 2 Level of Detail Data may be identical.
  2. For a <Time Related> aggregation, 2 Base Time Constraints Data may overlap, but not be identical.

FAQs

--FAQs needed here --
Prev: Consistent Table Type. Next: Elaboration of Classification Data. Up:Index.