====== GPR-012 — Avoidance of Gratuitous Reuse ======

[[public:00-sip-ra:99-annexes:annex-c-requirements:start|Go to Annex C: Requirements]]

===== Statement =====

The Submission SHOULD avoid reusing a specification when that reuse introduces unnecessary functionality, constraints, or dependencies.

===== Requirement Level =====

Recommended

===== Rationale =====

Reuse can reduce duplication and improve interoperability, but reuse is not beneficial when a specification introduces capabilities, constraints, implementation assumptions, or dependencies unrelated to the architectural need.

Avoiding gratuitous reuse keeps the proposed specification focused, reduces implementation and conformance complexity, and prevents unrelated external requirements from becoming implicit obligations.

===== Evaluation Criteria =====

A Submission addressing this recommendation demonstrates that:

  - Each reused specification supports an identified requirement or required capability
  - Functionality introduced through reuse is relevant to the proposed specification
  - Constraints introduced through reuse are necessary or justified
  - Normative and transitive dependencies are identified
  - Alternatives with fewer unnecessary dependencies are considered
  - Reuse does not introduce unrelated implementation technologies
  - Reuse does not expand the conformance scope without an identified need
  - Deviations from this recommendation include a documented reason
  - Effects of any unnecessary functionality or constraints are described

===== Referenced By =====

{{backlinks>public:00-sip-ra:99-annexes:annex-c-requirements:gpr-012-avoidance-of-gratuitous-reuse}}

===== Notes for Editors =====

This is a recommended requirement. A Submitter may depart from a `SHOULD` provision when a valid reason exists, but the Submission should document that reason and describe the resulting effects.

GPR-007 encourages reuse by requiring applicable existing standards to be used instead of defining equivalent new models. GPR-012 prevents that principle from being interpreted as a reason to reuse specifications that introduce unnecessary functionality, constraints, or dependencies.

Use the following syntax to include the authoritative Statement on another wiki page:

<code dokuwiki>
{{section>public:00-sip-ra:99-annexes:annex-c-requirements:gpr-012-avoidance-of-gratuitous-reuse#Statement&noheader&nofooter&noeditbtn}}
</code>

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>