| POSC Specifications Version 2.2 |
Epicentre Logical Data Model |
The specification of a document, including references to such E and P data that comprise the content of a document. A specification may serve as a graphical and/or textual template, populated with the actual text, figures, and tables of the document.
- identifier (M: ndt_name)
- The label by which a document specification is identified, such as a title.
- description (O: ndt_comment)
- A textual description of the document specification.
- be_positioned_by (V: SET[0:?] document_specification_placement(placement_of))
- A document specification may be inserted into other document specifications. Each document_specification may be positioned by one or more document_specification_placement.
- be_used_by (V: SET[0:?] data_collection(document_specification))
- Defines the data collections whose contents were defined from a document created according to this specification. Each document_specification may used by one or more data_collection.
- compose_document_specification (O: compose_document_specification(document_specification))
- Specifies the activity which produced this specification. Each document_specification may be the result of one compose_document_specification.
- data_collection (I, V: SET[0:?] data_collection(collection_content))
- Indicates the data collections that include this instance of E and P data. Each document_specification may be a member of one or more data_collection. Inherited from e_and_p_data.
- datum_for_ranking (I, V: SET[0:?] object_ranking(base_object))
- Indicates that an object is being used as a basis for comparison with another object. Each document_specification may datum for ranking one or more object_ranking. Inherited from object_of_interest.
- derived_interest (I, V: SET[0:?] derived_interest_makeup(interest_for))
- These are the ownership fractions for business associates of this business object. Each document_specification may be owned according to one or more derived_interest_makeup. Inherited from business_object.
- document (V: SET[0:?] document(document_specification))
- The specification may be rendered as physical documents, such as books, maps, or electronic files. Each document_specification may be represented by one or more document.
- document_specification_classification (V: SET[0:?] document_specification_classification(document_specification)) (1181)
- Gives the classifications that have been made of the document specification. Each document_specification may be classified by one or more document_specification_classification.
- graphical_composition (V: SET[0:?] graphical_element(document_specification))
- Indicates the graphical elements which make up this document specification. Each document_specification may contain one or more graphical_element.
- graphical_element (I, V: SET[0:?] graphical_element(depicted_object))
- Specifies one or more graphical elements which are depicting this data item. Each document_specification may be depicted by one or more graphical_element. Inherited from e_and_p_data.
- guideline_or_privilege (I, V: SET[0:?] guideline_or_privilege(business_object))
- These are the guidelines, limitations, regulations or privileges that are specifically defined for this business object. Other general guidelines, etc., that apply to this business object are defined via the typical and class relationships (if any) defined for this business object. Each document_specification may be the subject of one or more guideline_or_privilege. Inherited from business_object.
- guideline_or_privilege_compliance (I, V: SET[0:?] guideline_or_privilege_compliance(business_object))
- These are the designations of compliance with guidelines, limitations, regulations and privileges that are made for this business object. Each compliance statement describes the state of compliance for a specified guideline, limitation, regulation or privilege for a period of time. Each document_specification may be the subject of one or more guideline_or_privilege_compliance. Inherited from business_object.
- information_content (O: data_collection(specify_contents_of))
- Defines the data collection which points to instances that are referenced by this specification. This describes the contents of the document specification. Each document_specification may reference the contents of one data_collection.
- object_of_ranking (I, V: SET[0:?] object_ranking(ranked_object))
- Indicates that an object is being classified in a rank order based on its characteristics. Each document_specification may object of ranking one or more object_ranking. Inherited from object_of_interest.
- placement_of (V: SET[0:?] document_specification_placement(place_within))
- Reference to placement parameters for inserting another document specification. Each document_specification may include one or more document_specification_placement.
- render_document (V: SET[0:?] render_document(document_specification))
- Specifies various rendering activities which utilized this specification. Each document_specification may be utilized by one or more render_document.
- satisfy_obligation (I, V: SET[0:?] contractual_obligation(contractual_obligation_object))
- These are the contractual obligations that this business object is designated as fulfilling, either completely or partially. Each document_specification may satisfy one or more contractual_obligation. Inherited from business_object.
- subject_of_contract (O, I: SET[0:?] contract(contract_business_object))
- These are the contracts that specify information about the business object, and the business object is subject to the terms of these contracts. Each document_specification may be a subject of one or more contract. Inherited from business_object.
- subject_of_contract_designation (I, V: SET[0:?] contract_designation(contract_designation_object))
- This defines the contract designations that are made for this business object. For example, this may be the contract designations that define the specific interest ownership fractions of the business object as it is bought and sold. Each document_specification may be subject to one or more contract_designation. Inherited from business_object.
- typical_document_specification (O: typical_document_specification(document_specification))
- This defines the typical document specification that gives the generic description of the design or content of this document specification. Each document_specification may use one typical_document_specification.
Local rules:
- Abstract supertype:
- Each DOCUMENT_SPECIFICATION must be instantiated as one of its subtypes. These subtypes are: application_for_permit, contract_clause_set, diagram_specification, guideline_set, limitation_set, map, notification, other_document_specification, permit_specification, photographic_image, recorded_document_specification, regulation_set, report_specification, seismic_display, well_log
- Supertype path(s):
-
e_and_p_data >
object_of_interest >
business_object >
document_specification.
Referenced in Diagrams:
Generated on Mon Dec 1 10:00:10 1997
© Copyright 1997 POSC. All rights reserved.