GPR-014 — Combined Use of Complementary Specifications [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== GPR-014 — Combined Use of Complementary Specifications ======

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

===== Statement =====

The proposed specification SHOULD support combined use with separate specifications that provide distinct, complementary functionality when such combined use is applicable.

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

Recommended

===== Rationale =====

Separate specifications often address different architectural layers, responsibilities, Domains, or implementation concerns. Supporting their combined use allows each specification to retain its distinct scope while participating in a broader solution.

This approach promotes modularity and reuse without merging unrelated specifications or duplicating their capabilities.

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

A Submission addressing this recommendation demonstrates that:

  - Specifications providing applicable complementary functionality are identified
  - The distinct scope and responsibility of each specification are described
  - Relevant integration points are identified
  - Shared concepts and information exchanges are defined or mapped
  - Combined use does not duplicate the functionality of either specification
  - Normative responsibilities remain attributable to the specification that defines them
  - Conformance to each specification can be assessed independently
  - Conflicts among applicable requirements are identified
  - Dependencies introduced by combined use are documented
  - Limitations on combined use are described
  - A departure from this recommendation includes an explanation

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

{{backlinks>public:00-sip-ra:99-annexes:annex-c-requirements:gpr-014-combined-use-of-complementary-specifications}}

===== 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 limitations.

Combined use does not require consolidation of the participating specifications. Each specification retains its own scope, normative requirements, lifecycle, and conformance model.

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-014-combined-use-of-complementary-specifications#Statement&noheader&nofooter&noeditbtn}}
</code>

----

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