The SEDRIS Data Representation Model
APPENDIX A - Classes
Property Table

Class Name: Property Table

Superclass - <Data Table>

Subclasses

This DRM class is concrete and has no subclasses.

Definition

An instance of this DRM class is a <Data Table> instance containing no location information and, therefore, has no spatial <Axis> components.

A <Property Table> instance is assumed to provide information that applies to the entire associating <Geometry Representation> instance or <Feature Representation> instance.

Primary Page in DRM Diagram:

Secondary Pages in DRM Diagram:

Example

  1. For an externally controlled table-based animation example, see the <Scale Control Link> class, first example.

  2. For a function-driven table-based animation example, see the <Property Table Reference Control Link> class, second example.

FAQs

Why is a <Property Table> instance permitted to have <Property Table> components?

This mechanism allows a <Property Table> instance's cell data element to specify an index into the set of ordered <Property Table> components, so that any <Property Table> component can be "re-used" by many data cells. See <<Index Codes within Tables>> for further details.

Why isn't a <Property Table> instance allowed to have <Property Grid> components?

A DRM object referencing a <Property Grid> instance shall specify a <Location> instance for the <Property Grid> instance's origin, and a <Property Table> instance has no location information.

Why is a <Property Table> instance permitted to have <Property Table Reference> components?

This mechanism allows a <Property Table> instance's cell data element to specify an index into the set of ordered <Property Table Reference> components, so that any <Property Table Reference> component can be "re-used" by many data cells, therefore referring to "slices" of other <Property Table> instances without replicating the information. See <<Index Codes within Tables>> for further details.

Can values from a <Property Table> instance be used to drive <Control Link> instances?

Yes; this is possible in the following way.

  1. Store the values in cells of the <Property Table> instance such that the meaning field values of its <Table Property Description> components are appropriate for the target <Control Link> instance that is to be driven.

  2. Where the values are to be referenced in the controlling <Expression> component of the target <Control Link> instance, place a <Predefined Function> instance with function = SE_PREDEFFN_TABLE_VALUE, which in turn has an appropriate <Property Table Reference> component as an argument, referencing the values in the <Property Table> instance.

The <Predefined Function> instance will thereby return the value referenced from the <Property Table> instance as the value that drives the target <Control Link> instance.

If desired, the <Property Table Reference> instance can itself be controlled using a <Property Table Reference Control Link> instance, allowing different values to be referenced from the <Property Table> instance based on a controlling <Expression> instance.

See P4V5 of the SEDRIS Documentation Set for further details, as well as the examples shown here.

Constraints

Associated by (one-way)

Composed of (two-way) (inherited)

Composed of (two-way)

Composed of (two-way metadata) (inherited)

Component of (two-way) (inherited)

Component of (two-way)

Inherited Field Elements

This class has no inherited field elements.

Notes

Associated from Notes


Property_Table_Reference

A <Property Table Reference> instance may be employed to select an (N-1)-dimensional slice from the referenced <Property Table> component of the <Data Table Library> instance.

Composed of Notes


Classification_Data

The <Classification Data> component indicates the kind of information represented by the <Data Table> instance, such as terrain elevation or water characteristics.


Property_Table_Reference

A <Property Table Reference> component provides a mechanism for the cells of the <Property Table> instance to reference a slice of another <Property Table> instance.


Prev: Property Set Table Library. Next: Property Table Reference. Up:Index.

Last updated: July 26, 2006 Copyright © 2006 SEDRIS