The SEDRIS Data Representation Model
APPENDIX A - Classes
State Related Features
|
|---|
Class Name: State Related Features
Subclasses
This DRM class is concrete and has no subclasses.
Definition
An instance of this DRM class specifies a mechanism for specifying
discrete states from a possibly continuous
state value. Each discrete state corresponds to a branch of the
<State Related Features> and is
identified by the <State Data> for
that branch; the state value itself is given by the
state_tag
of <State Related Features>.
Primary Page in DRM Diagram:
Secondary Pages in DRM Diagram:
This class appears on only one page of the DRM class diagram.
Example
Consider a <Feature Model> representing
a road in various states of damage - in this example, after flooding.
The road's topological connections are different in various states
of damage, due to bridges being washed away and various road segments
being blocked due to fallen trees and the like.
Consequently, the <Feature Model>
consists of a State Related Features
instance, with state_tag =
EAC_GENERAL_DAMAGE_FRACTION
and active_state
= 0.0 % (that is, initially the road is undamaged,
before flooding takes place).
The <State Data>
for each branch indicates the range of percent damage for which that
branch describes the road's feature topology.
FAQs
- Is <State Related Features>
the only way to represent multi-state objects in SEDRIS?
No. <Control Link> instances can be used to
provide a fine level of control
over state by changing fields instead of representing states
as different <Feature Representation>
instances.
Constraints
Associated to (one-way) (inherited)
Associated by (one-way) (inherited)
Composed of (two-way) (inherited)
Composed of (two-way)
Composed of (two-way metadata) (inherited)
Component of (two-way) (inherited)
Notes
Associated to Notes
An association between two <Feature Representation> instances
indicates that the environmental object(s) that they
represent have the semantic relationship indicated by
the <Base Association Data> instance on the association
relationship.
An association between a <Geometry Hierarchy> instance and
a <Feature Representation> instance indicates that the
environmental object(s) that they represent have the
semantic relationship indicated by the <Base Association Data>
instance on the association relationship.
An association between a <Property Grid> instance and a
<Feature Representation> instance indicates that the
environmental object(s) represented by the
<Feature Representation> instance and the <Property Grid> instance
(or some specific cell data within that <Property Grid> instance)
have the semantic relationship indicated by the
<Base Association Data> instance on the association relationship.
Each associated <Property Grid> instance will indicate whether the
entire <Property Grid> instance or only some specific cell data
within it is participating in the relationship in question.
Associated from Notes
An association between two <Feature Representation> instances
indicates that the environmental object(s) that they
represent have the semantic relationship indicated by
the <Base Association Data> instance on the association
relationship.
An association between a <Geometry Hierarchy> instance and
a <Feature Representation> instance indicates that the
environmental object(s) that they represent have the
semantic relationship indicated by the <Base Association Data>
instance on the association relationship.
An association between a <Property Grid> instance and a
<Feature Representation> instance indicates that the
environmental object(s) represented by the
<Feature Representation> instance and the <Property Grid> instance
(or some specific cell data within that <Property Grid> instance)
have the semantic relationship indicated by the
<Base Association Data> instance on the association relationship.
Each associated <Property Grid> instance will indicate whether the
entire <Property Grid> instance or only some specific cell data
within it is participating in the relationship in question.
Composed of Notes
This relationship exists to support *attributes for derived objects.*
That is, these components are used only to specify texture mapping
information for geometry that is to be derived from the
<Aggregate Feature> by the consumer. These <Image Mapping Function>
instances shall use <Image Anchor> components to specify the mapping.
A <Presentation Domain> component is needed for instances of
<Aggregate Feature> that are significant only for a particular domain,
such as radar.
Fields Notes
If the value of the unique_descendants field is SE_TRUE, each
descendant, that is, each <Feature Representation> instance that
exists in the component tree rooted at the given <Aggregate Feature>,
shall be unique, in the
sense that it shall appear in only one branch of this aggregation.
If unique_descendants is SE_FALSE, at least one
<Feature Representation> instance
appears in more than one branch of the aggregation.
If the value of the strict_organizing_principle field is SE_TRUE,
each branch of this aggregation
strictly complies with the organizing principle for its
particular subclass. If this value is SE_FALSE, at least
one branch does not strictly comply with the given
organizing principle. See the organizing principle constraint
for each specific subclass for details.
The state_tag field specifies the state by which the component
<Feature Hierarchy> instances are being differentiated, and
shall specify an EAC which qualifies as "state applicable".
The active_state_value field specifies the default state. If the
given <State Related Features> instance has a
<State Control Link> component, the active_state_value field is
the target of that <State Control Link> instance.
Prev: State Data.
Next: State Related Geometry.
Up:Index.
|
Last updated: July 16, 2004
|
Copyright © 2004 SEDRIS™
|
|