5.1.7 Independence
Independence limits unnecessary dependencies while allowing reuse when an existing specification provides an applicable capability. A Submission balances these concerns by reusing relevant standards without introducing dependencies that do not help meet the RFP requirements.
Requirements
| Requirement | Level | Statement |
|---|---|---|
| GPR-011 — Necessary Normative Dependencies | Mandatory |
The Submission SHALL introduce a normative dependency on another specification only when that dependency is necessary to satisfy an applicable requirement or provide a required capability. |
| GPR-012 — Avoidance of Gratuitous Reuse | Recommended |
The Submission SHOULD avoid reusing a specification when that reuse introduces unnecessary functionality, constraints, or dependencies. |
Related Requirement
The original recommendation to reuse existing specifications to avoid duplication is governed by:
| Requirement | Level | Statement |
|---|---|---|
| GPR-007 — Reuse of Existing Standards | Mandatory |
The Submission SHALL reuse applicable existing OMG and other recognized standards rather than define new models that provide equivalent capabilities. |
Notes for Editors
The requirement identifiers and short titles link to the authoritative requirement records in Annex C.
The Statements displayed in this section are transcluded from their corresponding Annex C requirement pages and are not independently maintained copies.
Make changes to a Statement or its Requirement Level on its Annex C requirement page.
GPR-011 is mandatory because it uses SHALL.
GPR-012 is recommended because it uses SHOULD.
GPR-007 already establishes a mandatory obligation to reuse applicable existing standards. Creating another requirement from the original recommendation to reuse existing specifications would duplicate that obligation.
GPR-011 limits normative dependencies to those needed to satisfy an applicable requirement or provide a required capability. Informative references that do not create a normative dependency are outside its scope.
GPR-012 balances GPR-007 by discouraging reuse that introduces unrelated functionality, unnecessary constraints, or avoidable dependencies.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.