The SEDRIS Data Representation Model
APPENDIX C - Types
SE_Feature_Topology_Level
/*
 * REGISTERABLE ENUM: SE_Feature_Topology_Level
 *
 *   This data type specifies the level of feature topology
 *   that is present in a <Feature Topology Hierarchy> instance.
 */
typedef SE_Short_Integer SE_Feature_Topology_Level;
Enumerant Definition Value
SE_FTL_ZERO
 Topology level ZERO.

 The following DRM objects and relationships shall exist:

 DRM objects:
 a. <Feature Node> - one or more instances.

 b. <Feature Edge> - required if any <Feature Face> instances
                     exist

  Relationships:
  a. A two-way association between <Feature Node> instances and
     <Feature Edge> instances:
     1. shall exist for each <Feature Edge> instance that is
        connected to a given <Feature Node> instance; and

     2. shall exist for each of the two <Feature Node> instances
        (starting node and ending node) that bound each
        <Feature Edge> instance.

  Constraints:
      No additional constraints are required.

  Other types of feature topology DRM objects and relationships
  may exist at level SE_FTL_ZERO, but are not required. The
  requirements of level SE_FTL_ONE shall not be met. Thus,
  there shall be at least one pair of collocated <Feature Node>
  instances.
1
SE_FTL_ONE
 Topology level ONE.

  No additional types of DRM objects or relationships are required.

  Constraints:
  a.  Each <Feature Node> instance shall have a <Location> instance
      with unique coordinates. That is, no two <Feature Node>
      instances may be collocated.

  The requirements of level TWO shall not be met. That is, at least
  one pair of intersecting <Feature Edge> instances must exist.
2
SE_FTL_TWO
 Topology level TWO.

  No additional types of DRM objects or relationships are required.

  Constraints:
  a.  <Feature Edge> instances may not intersect or overlap one
      another, except where they meet at a common <Feature Node>
      instance.

  The requirements of level THREE shall not be met.
3
SE_FTL_THREE
 Topology level THREE.

  The following DRM objects and relationships are required to exist,
  in addition to the requirements of topology level TWO.

  DRM objects:
  a.  <Feature Face> - one or more instances, and

  b.  <Feature Face Ring> - one or more instances for each
      <Feature Face> instance

  Relationships:
  a.  A two-way association between <Feature Node> instances and
      <Feature Face> instances shall exist for each <Feature Node>
      instance located in the interior of a <Feature Face> instance.

  b.  A one-way association from <Feature Edge> instances to
      <Feature Face> instances shall exist for each of the
      <Feature Face> instances that each <Feature Edge> instance
      bounds.

  c.  A one-way association from <Feature Face Ring> instances to
      <Feature Edge> instances shall exist for each of the
      <Feature Edge> instances that bound a <Feature Face> instance.

  Constraints:
  a.  <Feature Face> instances may not intersect or overlap one
      another, except where they meet at a common <Feature Edge>
      instance.

  b.  The set of <Feature Face> instances shall be exclusive and
      exhaustive, forming a complete topological surface.

  c.  Each <Feature Edge> instance shall bound exactly two
      <Feature Face> instances.

  d.  Exactly one <Feature Face> instance within the parent
      <Union Of Feature Topology> instance shall have its
      universal field set to SE_TRUE.  All other <Feature Face>
      instances within the parent <Union Of Feature Topology>
      instance shall have their universal fields set to SE_FALSE.
4
SE_FTL_FOUR
 Topology level FOUR.

  No additional types of DRM objects or relationships are required.

  Constraints:
  a.  <Location 3D> instances are required for all coordinates.

  b.  Each <Feature Edge> instance may bound zero or more
      <Feature Face> instances. (This overrides the level THREE
      constraint.)

  c.  At least one <Feature Edge> instance shall bound more than
      two <Feature Face> instances.
5
SE_FTL_FIVE
 Topology level FIVE.

  The following DRM objects and relationships are required to exist,
  in addition to the requirements of topology level FOUR:

  DRM objects:
  a.  <Feature Volume> - one or more instances, and

  b.  <Feature Volume Shell> - one or more instances for each
      <Feature Volume> instance

  Relationships:
  a. A two-way association between <Feature Node> instances and
     <Feature Volume> instances shall exist for each <Feature Node>
     instance located in the interior of a <Feature Volume> instance.

  b. A two-way association between <Feature Edge> instances and
     <Feature Volume> instances shall exist for each <Feature Edge>
     instance completely located in the interior of a
     <Feature Volume> instance.

  c. A one-way association from <Feature Face> instances to
     <Feature Volume> instances shall exist for each of the two
     <Feature Volume> instances that each <Feature Face> instance
     bounds.

  d. A one-way association from <Feature Volume Shell> instances
     to <Feature Face> instances shall exist for each of the
     <Feature Face> instances that bound a <Feature Volume> instance.

  Constraints:
  a.  <Feature Volume> instances may not intersect or overlap
      one another, except where they meet at a common <Feature Face>
      instance.

  b.  The set of <Feature Volume> instances shall be exclusive and
      exhaustive, forming a complete topological space.

  c.  Exactly one <Feature Volume> instance within the parent
      <Union Of Feature Topology> instance shall have its
      universal field set to SE_TRUE.  All other <Feature Volume>
      instances within the parent <Union Of Feature Topology>
      instance shall have their universal fields set to SE_FALSE.
      All <Feature Face> instances within the parent
      <Union Of Feature Topology> instance shall have their
      universal fields set to SE_FALSE.
6



Prev: SE_Enumerant_Structure. Next: SE_Field_Modifier.


Return to: Top of this Page, Type Index