5.1.5 Changes to Existing Specifications
A Submission may identify changes or extensions to existing OMG specifications that would be required for its adoption. GPR-008 governs how to identify, justify, and specify those changes or extensions.
Requirement
| Requirement | Level | Statement |
|---|---|---|
| GPR-008 — Required Changes and Extensions to Existing OMG Specifications | Mandatory when applicable |
A Submission that requires a change or extension to an existing OMG specification for its adoption SHALL identify, justify, and fully specify each required change or extension. |
OMG favors Submissions that are upwardly compatible with existing standards and that minimize changes and extensions to existing specifications.
Notes for Editors
The requirement identifier and short title link to the authoritative requirement record in Annex C.
The Statement displayed in this section is transcluded from its Annex C requirement page and is not an independently maintained copy.
Make changes to the Statement or its Requirement Level on its Annex C requirement page.
GPR-008 is mandatory when adoption of the Submission depends on changing or extending an existing OMG specification.
The OMG preference for upward compatibility and minimal change is an evaluation consideration rather than a separate normative requirement because it does not use SHALL or SHOULD.
SIP-026 — Preservation of Existing OMG Specifications prohibits the Submission from replacing, superseding, or modifying existing OMG specifications. Consequently, a proposed change governed by GPR-008 must also comply with SIP-026.
A proposed extension must remain consistent with the scope restrictions of this RFP and must not redefine or duplicate capabilities governed by:
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.