Architectural Principles Extensibility and Subsetting
Extensibility and subsetting refers to the ability of an individual data model user to customize the model to meet their individual member business needs. In some cases, extensions are needed to manage proprietary or application specific information.
Contents |
Objective
To assist in the implementation of extensions or subsets so that changes to the model are easily identified to external users of the model (i.e. application vendors).
Guidelines
- Additional tables and columns may be added but the Primary Keys and Foreign Keys of PPDM tables must remain intact.
- Tables and columns may be subsetted but the Primary Keys and Foreign Keys of remaining PPDM tables must remain intact. This means that you may not drop a parent table if you are including the child table in your implementation.
Naming Extensions
Tables
A total of 6 characters are available for naming private table name extensions. These characters should be added as a prefix to the usual table naming structure.
Example:
- ABC OIL COMPANY wants to extend the model by adding a table containing special core analysis information. They would name the table AB_CORE_ANALYSIS where AB_ identifies this as a private extension.
Columns
A total of 3 characters are available for naming private column name extensions. These characters should be added as a prefix to the usual column naming structure.
Example:
- ABC OIL COMPANY wants to extend the model by adding a column containing proprietary Seismic line information. They would name the column AB_PROPRIETARY_FIELD where AB_ identifies this a private extension.
