POSC Specifications: Epicentre Version 3.0 | Relational Implementation |
Describes the consequence of a relationship between two geologic features, primary and secondary. The relationship is asymmetric if the consequence applies only to the primary feature. If the consequence could apply equally well to either the primary or the secondary feature, the relationship is symmetrical and either feature may be arbitrarily assigned the consequence. Examples include; "a horizon is the top of a sand layer" (asymmetrical), or "a sand layer is interbedded with a shale layer" (symmetrical).
- instance_s (PK, M: CHAR VARYING(19))
- Surrogate key of the table.
- instance_create_date (O: TIMESTAMP)
- e_and_p_data.instance_create_date
This is the date that this instance was created. This date is defined by the source if imported, or is the date the instance is created if a new instance.
- last_updated (O: TIMESTAMP)
- e_and_p_data.last_updated
This is the date that this instance was last updated. This value should be updated when any part of this instance is altered (except for inverse relationships).
- consequence (FNK, M: CHAR VARYING(80))
- geologic_feature_association.consequence
This describes the consequence of the interaction between two geologic feature, primary and secondary. It describes, in geologic terms, the primary feature relative to the secondary feature.
Defines a foreign key to table r_geologic_feature_assoc.
- primary_geologic_feature_s (FSK, M: CHAR VARYING(19))
- geologic_feature_association.primary_geologic_feature
Indicates a geologic feature in the role of primary agent. The primary feature is defined by a consequence relative to the secondary object. Consequences are asymmetrical or symmetrical. For asymmetric interactions, the consequence, such as "top", can only apply to the primary feature. For example, "a horizon (primary feature) is the top (consequence) of a sand layer (secondary feature)". Here only the horizon can be a "top". If the relationship between the two features is symmetrical both features can be described equally well by the consequence, and either could be chosen as the primary agent with the other chosen as the secondary agent. An example of a symmetrical relationship is "a sand layer (primary feature) is interbedded (consequence) with a shale layer(secondary feature)".
Defines a foreign key to table geologic_feature.
- secondary_geologic_feature_s (FSK, M: CHAR VARYING(19))
- geologic_feature_association.secondary_geologic_feature
Indicates a geologic feature in the role of secondary agent. The secondary feature relates the primary feature to a consequence. The consequence does not apply to the secondary feature but tells where it is derived from. For example in, "a horizon (primary feature) is the top (consequence) of a sand layer (secondary feature)" the secondary feature shows where the consequence is coming from. If the relationship between the two features is symmetrical both can be described equally well by the consequence, and either could be chosen as the primary agent with the other chosen as the secondary agent. An example of a symmetrical relationship is "a sand layer (primary feature) is interbedded (consequence) with a shale layer(secondary feature)".
Defines a foreign key to table geologic_feature.
- description (O: CHAR VARYING(2000))
- e_and_p_data.description
A remark or comment about the instance.
- duration (O: FLOAT)
duration_u (FNK, O: CHAR VARYING(15))
- transient_association.duration
Defines the duration of the association expressed in any valid units of time.
duration_u: Defines the unit of measure. Defines a foreign key to table r_unit_of_measure.
- end_time (O: TIMESTAMP)
end_time_cd (O: CHAR(1))
end_time_yr (O: FLOAT)
end_time_yp (O: INTEGER)
end_time_dy (O: INTEGER)
end_time_hr (O: INTEGER)
end_time_mt (O: INTEGER)
end_time_st (O: FLOAT)
end_time_of (O: FLOAT)
- transient_association.end_time
End time of the association.
- instance_creator (O: CHAR VARYING(80))
- e_and_p_data.instance_creator
This is the person, company or application that created this instance. This identifies the party responsible for loading this instance.
- is_current (O: CHAR(1))
- transient_association.is_current
When TRUE, this flag indicates that this instance is designated as a current instance. This flag can be used in place of time based attributes or can be used in conjunction with them; however, it should not conflict with them.
- last_updated_by (O: CHAR VARYING(80))
- e_and_p_data.last_updated_by
This records the person or application making the update to this instance.
- source (O: CHAR VARYING(80))
- e_and_p_data.source
The provider of this instance, which is usually a data provider for imported/purchased data. If this instance is provided by POSC, then this attribute must be "POSC".
- start_time (O: TIMESTAMP)
start_time_cd (O: CHAR(1))
start_time_yr (O: FLOAT)
start_time_yp (O: INTEGER)
start_time_dy (O: INTEGER)
start_time_hr (O: INTEGER)
start_time_mt (O: INTEGER)
start_time_st (O: FLOAT)
start_time_of (O: FLOAT)
- transient_association.start_time
Start time of the association.
- caused_by_s (FSK, O: CHAR VARYING(19))
- transient_association.caused_by
Specifies the activity which establishes this association.
Defines a foreign key to table activity.
- r_transient_period (FNK, O: CHAR VARYING(80))
- transient_association.ref_transient_period
The type of period over which the property applies, such as day, month, quarter, cumulative, etc.
Defines a foreign key to table r_transient_period.
- terminated_by_s (FSK, O: CHAR VARYING(19))
- transient_association.terminated_by
Specifies the activity which established the termination of a transient association between two objects.
Defines a foreign key to table activity.
Table is related to: data_collection_content, document_specification_part, @graphical_element
Primary Key Constraint on: INSTANCE_S
Fully implemented Unique Constraint on: PRIMARY_GEOLOGIC_FEATURE_S, SECONDARY_GEOLOGIC_FEATURE_S, CONSEQUENCE
Generated on Tue Jul 10 16:29:34 2001
© Copyright 2001 POSC. All rights reserved.