Overview
AP203 was the first APs, and used conventions that changed in newer APs. AP203 assignments use a "cc_design_" prefix, while AP214 and others use "applied_". AP203 also uses context subtypes while newer APs just use the base context types. The second edition of AP203 deprecates the "cc_design" definitions in favor of "applied" versions (See AP203e2 annex H).
The merged library only contains the "applied_" definitions. When reading or writing an AP203 file, we automatically read the "cc_design" definitions as instances of the "applied" C++ classes, and write the "applied" definitions using the appropriate "cc_design" name.
The table below shows these and other changes. When reading AP203, an entity in the left column will appear in memory as an instance of the type on the right. When writing a file as AP203, an instance of a type on the right will be written as the type on the left.
| AP203 Definition | Merged Library Definition |
|---|---|
Deprecated AP203 assignments and contexts, automatically remapped on read and write | |
| cc_design_approval | applied_approval_assignment |
| cc_design_certification | applied_certification_assignment |
| cc_design_contract | applied_contract_assignment |
| cc_design_date_and_time_assignment | applied_date_and_time_assignment |
| cc_design_person_and_organization_assignment | applied_person_and_organization_assignment |
| cc_design_security_classification | applied_security_classification_assignment |
| cc_design_specification_reference | applied_document_reference |
| design_context | product_definition_context |
| mechanical_context | product_context |
Deprecated AP203, automatically remapped on read only. | |
| advanced_brep_representation | An old definition, which was used in AP203 files before the 1994 publication of AP203 and AIC 514. Read as an instance of advanced_brep_shape_representation. It has no name field, so we initialize that to the empty string. |
Deprecated, but still present in the schema. | |
| change | unchanged, AP203 design activity model deprecated |
| change_request | unchanged, AP203 design activity model deprecated |
| change_request_item | unchanged, AP203 design activity model deprecated |
| design_make_from_relationship | unchanged, AP203 design activity model deprecated |
| document_with_class | unchanged, deleted in AP203e2 |
| ordinal_date | unchanged |
| product_definition_formation_with_specified_source | unchanged, previously required by AP203 CC1 |
| start_request | unchanged, AP203 design activity model deprecated |
| start_request_item | unchanged, AP203 design activity model deprecated |
| start_work | unchanged, AP203 design activity model deprecated |
| supplied_part_relationship | unchanged, AP203 design activity model deprecated |
| week_of_year_and_day_date | unchanged |
| work_item | unchanged, but AP203 design activity model deprecated |
Retired/Merged SELECT types Do not appear in Part 21 files, but the names might be used in older C++ code written for AP203. The "cc_" prefix definitions are legacy things that were renamed in AP203e2 and AP242 | |
| approved_item | approval_item |
| certified_item | certification_item |
| classified_item | When updating AP203 code, change to security_classification_item. Later APs used this name for group assignments (applied_classification_assignment) |
| cc_classified_item | security_classification_item |
| contracted_item | contract_item |
| date_time_item | date_and_time_item |
| person_organization_item | person_and_organization_item |
| cc_person_organization_item | person_and_organization_item |
| specified_item | document_reference_item |
| cc_specified_item | document_reference_item |