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-7-independence: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-7-independence:start [2026/09/15 12:19] (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 use or depend on other specifications only when necessary.
+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.
-  * Proposals SHOULD reuse existing specifications to avoid duplication.
-  * Proposals SHOULD avoid gratuitous reuse.
+===== Requirements =====
+^ Requirement ^ Level ^ Statement ^
+| [[public:00-sip-ra:99-annexes:annex-c-requirements:gpr-011-necessary-normative-dependencies|GPR-011 — Necessary Normative Dependencies]] | Mandatory | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:gpr-011-necessary-normative-dependencies#Statement&noheader&nofooter&noeditbtn}} |
+| [[public:00-sip-ra:99-annexes:annex-c-requirements:gpr-012-avoidance-of-gratuitous-reuse|GPR-012 — Avoidance of Gratuitous Reuse]] | Recommended | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:gpr-012-avoidance-of-gratuitous-reuse#Statement&noheader&nofooter&noeditbtn}} |
+===== Related Requirement =====
+The original recommendation to reuse existing specifications to avoid duplication is governed by:
+^ Requirement ^ Level ^ Statement ^
+| [[public:00-sip-ra:99-annexes:annex-c-requirements:gpr-007-reuse-of-existing-standards|GPR-007 — Reuse of Existing Standards]] | Mandatory | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:gpr-007-reuse-of-existing-standards#Statement&noheader&nofooter&noeditbtn}} |
+===== 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.
 ----
@@ Line 12: / Line 41: @@
 © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 </WRAP>