Section 1 - Scope, Goals and Criteria

1.1 Scope and Goals

This specification establishes the requirements to be met when 2-dimensional graphical picture data that is vector or mixed vector and raster is used in the graphical interchange between petrotechnical applications employed in petroleum Exploration and Production (E&P) and related applications, using the format of the Computer Graphics Metafile (CGM).

This profile is known and identified in full as CGM*PIP -- PIP for short.

This profile defines:

Revision 3 of a profile of Version 1 metafiles as defined in the CGM:1992 standard, to be known in this document as PIP/I/3. PIP/I/3 cancels and replaces the PIP/I/2 specification, dated May 1993. PIP/I/3 corrects a small number of defects of PIP/I/2 (a separate maintenance document describing these changes is available).
Revision 3 of a profile of Version 3 metafiles as defined in the CGM:1992 standard, to be known in this document as PIP/II/3.

It is the scope of this profile to codify the existing use of CGM in this petrotechnical application community. The scope includes:

Derive and construct a profile of standard elements of Version 1 metafiles as defined in ISO/IEC 8632:1992, incorporating at least:
1. The element sets, parameters, and features required by this application community for effective graphical interchange of standard graphical pictures;
2. The "good practice" rules of CGM usage, which have been derived and incorporated into the profiles of other application communities, and whose core principles are being incorporated into CGM:1992 Amendment 1 (Am.1, "Rules for Profiles", ISO project in progress, currently at the processing stage of DAM, formerly being processed and referenced as Amendment 4 to CGM:1987);
Derive and construct an upwardly compatible profile of standard elements of Version 3 metafiles as defined in ISO/IEC 8632:1992.
Define, clarify, document, and give legal standard encodings to CGM extensions in common use within the community, including the extensions known as Seismic Trace Extensions.
A precise definition of conformance of metafiles to this profile.
A foundation definition of conformance of implementations to this profile, including:
1. An "Interpreter Implementation Requirements Specification", as specified and required by CGM:1992 Amendment 1 (Am.1, ISO work in progress);
2. A "Generator Implementation Requirements Specification", as specified and required by CGM Am.1;
Provide base profiles which will be extensible to solving additional problems of this application community, via possible future revisions and extensions of this profile.

The scope of this profile is limited to the inclusion of technology for which there is consensus within the application community.

1.2 Criteria

The following criteria have been considered and applied in the derivation of features and the design of this profile:

A legal PIP-conforming metafile shall be a legal standard metafile according to the rules of CGM.
Features useful to, and needed by, the application community should be provided and included.
While recognizing that the ISO work is still in development, the profile should follow the rules of CGM:1992 Amendment 1 (Am.1), including its Model Profile and its requirement for "Implementation Requirements Specifications" sections.
The profile should not deviate arbitrarily from the profiles of other application communities, in particular the profiles of CALS and ATA/AIA (as well as the Model Profile of CGM:1992 Am.1).
PIP/I should define a profile based on CGM Version 1, which will be quickly and immediately usable by the application community and its technology suppliers.
PIP/I should be defined so that in the long term it continues to provide a "low-end" and inexpensive conformance target for that subset of applications which have modest graphical requirements.
PIP/I should assure, even so, that "high-end" applications within the scope of the profile have a path or a solution to their graphical problems within the constraints of the profile, even if such a solution might not be optimal.
PIP/II should provide in the long term an effective and efficient profile aimed at high-end, more advanced applications. PIP/I shall be a proper subset of PIP/II (i.e., a legal PIP/I metafile shall be a legal PIP/II metafile).
The profile should be designed in such a manner that implementation burdens for conforming technology are distributed between conforming generators and conforming interpreters.
Evaluation of features for possible inclusion in PIP/I particularly should include practical economic considerations - the cost of implementing features and technology should be balanced against the benefit of the features to the application community.
The profile should place reasonable limits on all of its aspects, so that the technology demands and requirements of implementations are deterministic.

1.3 Present scope and future enhancements

The extensions defined by this release of PIP/I and PIP/II are limited to Seismic Trace and Continuous Rendering extensions. The PIP/III and PIP/IV specifications in Volume 2 define extensions for Basic Well Logging and Advanced Well Logging. It is within the scope of a petroleum industry profile of CGM to address requirements and extensions for the application areas of mapping and contouring. This could be done in a future upgrade to PIP, via an upwardly compatible PIP specification.

Systemization and standardization of sets of Lithology Patterns and Oilfield Symbols are also within the scope of a petroleum industry profile of CGM. This release of PIP/II has not addressed the definition and incorporation of sets of standard patterns and symbols. This could be done in a future upgrade to PIP, via either a maintenance release of PIP/II or an upwardly compatible PIP specification. In both cases standard sets must be defined, and if symbol library functionality is to be used then the associated CGM:1992 Version 3 elements must be enabled for use in PIP (they are currently disallowed).

1.4 Corrections and errors

If you find errors in this document, please report them to the POSC Help Desk (help@posc.org) so that the document may be maintained. If you are an implementor, you are encouraged to keep up with any Corrigenda that might be published. Notices will be posted at the at the POSC Web site.

1.5 Document roadmap

The first eight sections and Section 10 define all of the aspects of PIP which are concerned with CGM core content. Application extensions are defined in section 9.

Section 1 - Scope, Goals, and Criteria, provides criteria for selecting functionality.

Section 2 - Normative References, used by and needed for implementation of PIP.

Section 3 - Classification of Metafiles classification of metafiles and basis for conformance determination.

Section 4 - PIP/I and PIP/II Metafile Requirements, contains definition of content of conforming PIP metafiles, CGM core content.

Section 5 - Implementation Requirements Specifications defines requirements for conforming PIP generators and interpreters.

Section 6 - Supplemental Specifications and References provides additional normative materials, especially regarding fonts and data records.

Section 7 - Production Notes contains notes on production of this PIP profile.

Section 8 - Definitions contains definitions, glossary, acronyms, and abbreviations.

Section 9 - Petroleum Industry Extensions for CGM*PIP contains the definition of Seismic Trace and Continuous Rendering extensions of PIP.

Section 10 - Font Reference - Coding Tables and Glyph Metrics contains normative tables of character code assignments and font/glyph metrics.