POSC Specifications: Epicentre Version 3.0 | Logical Data Model |
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).
- primary_geologic_feature (M, K: geologic_feature(primary_feature_association)) (C007)
- 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)". Each geologic_feature_association must primarily involve one geologic_feature.
- secondary_geologic_feature (M, K: geologic_feature(secondary_feature_association)) (C007)
- 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)". Each geologic_feature_association must secondarily involve one geologic_feature.
- consequence (M, K: ref_geologic_feature_assoc(geologic_feature_association)) (C007)
- 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. Each geologic_feature_association must have a consequence of one ref_geologic_feature_assoc.
- description (O, I: ndt_comment) (C117)
- A remark or comment about the instance. Inherited from e_and_p_data.
- duration (O, I: ndt_time)
- Defines the duration of the association expressed in any valid units of time. Inherited from transient_association.
- end_time (O, I: ndt_date_tod)
- End time of the association. Inherited from transient_association.
- instance_create_date (O, I: ndt_date_tod) (C126)
- 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. Inherited from e_and_p_data.
- instance_creator (O, I: ndt_identifier) (C126)
- This is the person, company or application that created this instance. This identifies the party responsible for loading this instance. Inherited from e_and_p_data.
- is_current (O, I: ndt_boolean) (C137)
- 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. Inherited from transient_association.
- last_updated (O, I: ndt_date_tod) (C126)
- 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). Inherited from e_and_p_data.
- last_updated_by (O, I: ndt_identifier) (C126)
- This records the person or application making the update to this instance. Inherited from e_and_p_data.
- source (O, I: ndt_identifier) (C126)
- 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". Inherited from e_and_p_data.
- start_time (O, I: ndt_date_tod)
- Start time of the association. Inherited from transient_association.
- caused_by (O, I: activity(cause_association))
- Specifies the activity which establishes this association. Each geologic_feature_association may be caused by one activity. Inherited from transient_association.
- data_collection (I, V: SET[0:?] data_collection_content(collection_part)) (C020)
- Indicates the data collections that include this instance of E and P data. Each geologic_feature_association may be a member of one or more data_collection_content. Inherited from e_and_p_data.
- document_information_content (I, V: SET[0:?] document_information_content(e_and_p_data)) (C136)
- These are the document specification parts that include this data value and define its meaning within a document specification. Each use may define a different meaning, and many uses are allowed. Each geologic_feature_association may be included in one or more document_information_content. Inherited from e_and_p_data.
- graphical_element (I, V: SET[0:?] graphical_element(depicted_object))
- Specifies one or more graphical elements which are depicting this data item. Each geologic_feature_association may be depicted by one or more graphical_element. Inherited from e_and_p_data.
- ref_transient_period (O, I: ref_transient_period(transient_association)) (C138)
- The type of period over which the property applies, such as day, month, quarter, cumulative, etc. Each geologic_feature_association may represent a period of one ref_transient_period. Inherited from transient_association.
- terminated_by (O, I: activity(terminate_association))
- Specifies the activity which established the termination of a transient association between two objects. Each geologic_feature_association may be terminated by one activity. Inherited from transient_association.
Local rules:
- Uniqueness Constraint
- primary_geologic_feature, secondary_geologic_feature, consequence
- [I: transient_association] Instance Value Constraint (C050)
-
If REF_TRANSIENT_PERIOD is either YEAR TO DATE, MONTH TO DATE or CUMULATIVE, then END_TIME must be instantiated.
- [I: transient_association] Instance Value Constraint (C050)
-
If REF_TRANSIENT_PERIOD is ANNUAL, SEMIANNUAL, QUARTER, MONTHLY, DAILY, or HOURLY, then either both START_TIME and END_TIME are blank or both must be instantiated.
- [I: transient_association] Instance Value Constraint (C050)
-
If REF_TRANSIENT_PERIOD is EVENT, then both START_TIME and END_TIME must either be blank or be identical.
Supertype path(s):
Referenced in Diagrams:
Generated on Tue Jul 10 15:42:48 2001
© Copyright 2001 POSC. All rights reserved.