The SEDRIS Data Representation Model
APPENDIX C - Types
SE_Feature_Topology_Level
/*
 * REGISTERABLE ENUM: SE_Feature_Topology_Level
 *
 *   This data type is used to indicate, for the given
 *   <Feature Topology Hierarchy> instance, the level of
 *   feature topology that is present.
 */
typedef SE_Short_Integer SE_Feature_Topology_Level;
Enumerant Definition Value
SE_FEAT_TOPO_LVL_ZERO
 Topology level 0.

 The following SEDRIS objects, and relationships among those
 SEDRIS objects, are required to exist:

 SEDRIS Objects:
     <Feature Node> - one or more instances.

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

  Relationships:
      <Feature Node> <-> <Feature Edge> association -
      -  required for each <Feature Edge> instance that is connected
         to a given <Feature Node> instance

      - required 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 objects and relationships MAY
  exist at level 0, but are not required.

  The requirements of level 1 must NOT be met (that is, there must be
  at least one pair of collocated <Feature Node> instances).
1
SE_FEAT_TOPO_LVL_ONE
 Topology level 1.

  Objects and Relationships:

  No additional types of SEDRIS objects or relationships are required.

  Constraints:
      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 2 must NOT be met; that is, at least
  one pair of intersecting <Feature Edge> instances must exist.
2
SE_FEAT_TOPO_LVL_TWO
 Topology level 2.

  Objects and Relationships:

  No additional types of SEDRIS objects or relationships are required.

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

  The requirements of level 3 must NOT be met.
3
SE_FEAT_TOPO_LVL_THREE
 Topology level 3.

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

  Objects:
      <Feature Face> - one or more instances

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

  Relationships:
      <Feature Node> <-> <Feature Face> association - required for
       each <Feature Node> instance located in the interior of a
       <Feature Face> instance

      <Feature Edge> -> <Feature Face> association - required for
       each of the <Feature Face> instances each <Feature Edge>
       instance bounds

      <Feature Face Ring> -> <Feature Edge> association - required for
       each of the <Feature Edge> instances that each <Feature Face>
       instance is bounded by

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

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

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

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

  Objects and Relationships:
      No additional types of objects or relationships are required.

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

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

      At least one <Feature Edge> instance must bound more than two
       <Feature Face> instances.
5
SE_FEAT_TOPO_LVL_FIVE
 Topology level 5.

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

  Objects:
      <Feature Volume> - one or more instances

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

  Relationships:
      <Feature Node> <-> <Feature Volume> association - required
       for each <Feature Node> instance located in the interior
       of a <Feature Volume> instance

      <Feature Edge> <-> <Feature Volume> association - required
       for each <Feature Edge> instance completely located in the
       interior of a <Feature Volume> instance

      <Feature Face> -> <Feature Volume> association - required for
       each of the two <Feature Volume> instances that each
       <Feature Face> instance bounds

      <Feature Volume Shell> -> <Feature Face> association - required
       for each of the <Feature Face> instances that each
       <Feature Volume> instance is bounded by

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

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

      Exactly one <Feature Volume> instance within the parent
       <Union Of Feature Topology> shall have its universal field
       set to SE_TRUE.  All other <Feature Volume> instances within
       the parent <Union Of Feature Topology> shall have their
       universal fields set to SE_FALSE.  All <Feature Face> instances
       within the parent <Union Of Feature Topology> 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

Last updated: July 16, 2004 Copyright © 2004 SEDRIS