Class Name: Property Table

Superclass - Data Table

Definition

Primary Page in DRM Diagram:

• 6

Secondary Pages in DRM Diagram:

• 3
• 5
• 8
• 18
• 19

Example

1. Externally Controlled Table-Based Animation

   A Scale Control Link is to be driven using values from a Property Table. The table value that is to be used is to be specified from outside the transmittal. The Scale Control Link would contain the Predefined Function SE_FUNC_TABLE_VALUE. This would contain a Property Table Reference with an association to the Property Table that contains the scale values. The Property Table would be of table_type EDCS_CC_CONTROL_VALUES and have a Table_Property_Description specified by EDCS_AC_CONTROL_VALUE_SCALE_AMOUNT. Which value is referenced from the Property Table would be controlled by a Property Table Reference Control Link that is contained in the Property Table Reference. This in turn would be driven by a Variable. To provide the hook for this Variable to be set from outside, the Variable would be associated with an Interface Template.

   An instance diagram is given below:

   
2. Cyclic Table-Based Animation

   A Translation Control Link is to be driven using values from a Property Table. The table values that are to be used are to be cycled through 8 times with each cycle taking 10 seconds. This sequence of cycles is to be triggered from outside the transmittal. The Translation Control Link would contain the Predefined Function SE_FUNC_TABLE_VALUE. This would contain a Property Table Reference with an association to the Property Table that contains the translation values. The Property Table would be of table_type EDCS_CC_CONTROL_VALUES and have a Table_Property_Description specified by EDCS_AC_CONTROL_VALUE_TRANSLATION_AMOUNT. Which value is referenced from the Property Table would be controlled by a Property Table Reference Control Link that is contained in the Property Table Reference. This in turn would be driven by the SE_FUNC_CYCLE_TIME Predefined Function. The cycle length (10 seconds) and the number of cycles (8) are specified by arguments to the function. The function is triggered by a Variable. To provide the hook for this Variable to be set from outside, the Variable would be associated with an Interface Template.
   An instance diagram is given below:

   

3. Function-Driven Table-Based Animation

   A Rotation Control Link is to be driven using values from a Property Table. The table value that is to be used is to be specified by the simulation's wind speed in order to rotate a wind sock to the appropriate elevation. The Rotation Control Link would contain the Predefined Function SE_FUNC_TABLE_VALUE. This would contain a Property Table Reference with an association to the Property Table that contains the rotation values. The Property Table would be of table_type EDCS_CC_CONTROL_VALUES and have a Table_Property_Description specified by EDCS_AC_CONTROL_VALUE_ROTATION_ANGLE. Which value is referenced from the Property Table would be controlled by a Property Table Reference Control Link that is contained in the Property Table Reference. This in turn would be driven by the SE_FUNC_WIND_SPEED Predefined Function.

   An instance diagram is given below:

   

FAQs

How does a Property Table differ from a Data Table?

It is distinguished in the data model in that a Property Table can aggregate other Property Tables but not Data Tables, while Property Grids can aggregate Data Tables (i.e.: Property Grids can aggregate both Property Grids and Property Tables).

Why would you want a Property Table to aggregate another Property Table?

In this way a Property Table cell data element can be "Property Table valued" in that it can give the component number of a Property Table component in the ordered aggregate list. This mechanism allows some component Data Table to be "re-used" by many data cells. Similarly, Property Grid cells can reference aggregated Property Tables or Property Grids.

Why isn't a Property Table allowed to aggregate Property Grids?

An object that references a Property Grid must supply a location for the Property Grid origin. Property Grid cells have location, but Property Table cells do not.

Constraints

• Non Cyclic Aggregations

Associated by (one-way)

• optionally, some Property Table References

Composed of (one-way)(inherited)

• optionally, some {ordered} Image Mapping Functions

Composed of (one-way)

• one or more {ordered} Axis
• one or more {ordered} Table Property Descriptions
• optionally, some {ordered} Property Tables

Composed of (one-way metadata)(inherited)

• optionally, an Access
• optionally, some Browse Graphics
• optionally, a Citation
• optionally, some Cross References
• optionally, a Data Quality
• optionally, a Description
• optionally, a Keywords
• optionally, a Point of Contact
• optionally, a Time Constraints Data

Component of (one-way)(inherited)

• optionally, some Property Grids

Component of (one-way)

• optionally, some Attribute Sets
• optionally, some Features
• optionally, some Geometries
• optionally, some Property Tables

Component of (two-way)(inherited)

• optionally, a Data Table Library

Inherited Field Elements

Notes

Fields Notes

data_table_type

 identifies the type of the table
 (e.g.: elevation grid (EDCS_CC_TERRAIN_ELEVATION),
        bathymetry (EDCS_CC_OCEAN_FLOOR_BATHYMETRY),
        underwater sound speed
        (EDCS_CC_OCEAN_WATER_CHARACTERISTICS_SOUND_SPEED), etc.)