Differences

This shows you the differences between two versions of the page.

--- public:00-sip-ra:05-general-requirements-on-proposals:05-1-requirements:05-1-8-compatibility:start [2026/09/12 18:34] – ↷ Links adapted because of a move operation nick_dido
+++ public:00-sip-ra:05-general-requirements-on-proposals:05-1-requirements:05-1-8-compatibility:start [2026/09/15 12:45] (current) – nick_dido
@@ Line 3: / Line 3: @@
 [[public:00-sip-ra:05-general-requirements-on-proposals:05-1-requirements:start|Return to Requirements]]
-Proposals SHALL be compatible with and usable alongside existing OMG specifications and other standards-body specifications, as appropriate.
+Compatibility allows the proposed specification to coexist and operate with applicable OMG specifications and standards developed by other recognized standards bodies without requiring their replacement or modification.
-Separate specifications offering distinct functionality SHOULD be usable together where such combined use makes sense.
+===== Requirements =====
+^ Requirement ^ Level ^ Statement ^
+| [[public:00-sip-ra:99-annexes:annex-c-requirements:gpr-013-compatibility-with-existing-standards|GPR-013 — Compatibility with Existing Standards]] | Mandatory | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:gpr-013-compatibility-with-existing-standards#Statement&noheader&nofooter&noeditbtn}} |
+| [[public:00-sip-ra:99-annexes:annex-c-requirements:gpr-014-combined-use-of-complementary-specifications|GPR-014 — Combined Use of Complementary Specifications]] | Recommended | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:gpr-014-combined-use-of-complementary-specifications#Statement&noheader&nofooter&noeditbtn}} |
+===== Related Requirements =====
+GPR-013 and GPR-014 complement, but do not duplicate, the following requirements:
+^ Requirement ^ Level ^ Relationship ^
+| [[public:00-sip-ra:99-annexes:annex-c-requirements:gpr-007-reuse-of-existing-standards|GPR-007 — Reuse of Existing Standards]] | Mandatory | Requires reuse of applicable existing standards instead of defining new Models that provide equivalent capabilities |
+| [[public:00-sip-ra:99-annexes:annex-c-requirements:gpr-011-necessary-normative-dependencies|GPR-011 — Necessary Normative Dependencies]] | Mandatory | Limits normative dependencies to those needed to satisfy an applicable requirement or provide a required capability |
+| [[public:00-sip-ra:99-annexes:annex-c-requirements:gpr-012-avoidance-of-gratuitous-reuse|GPR-012 — Avoidance of Gratuitous Reuse]] | Recommended | Discourages reuse that introduces unnecessary functionality, constraints, or dependencies |
+===== Notes for Editors =====
+The requirement identifiers and short titles link to the authoritative requirement records in Annex C.
+The Statements displayed in the Requirements table 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-013 is mandatory because it uses ''SHALL''.
+GPR-014 is recommended because it uses ''SHOULD''.
+The term “applicable” replaces “as appropriate” to connect compatibility to an identifiable architectural or operational need.
+Compatibility does not necessarily create a normative dependency. A specification may coexist or interoperate with another specification without incorporating that specification into its own conformance requirements.
+GPR-013 governs compatibility with applicable existing standards. GPR-014 addresses the combined use of separate specifications that provide complementary functionality.
+The Related Requirements table provides nonnormative relationship summaries. The corresponding Annex C requirement records remain authoritative.
 ----
@@ Line 12: / Line 45: @@
 © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 </WRAP>