GPR-014 — Combined Use of Complementary Specifications

Go to Annex C: Requirements

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

Recommended

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.

A Submission addressing this recommendation demonstrates that:

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

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:

{{section>public:00-sip-ra:99-annexes:annex-c-requirements:gpr-014-combined-use-of-complementary-specifications#Statement&noheader&nofooter&noeditbtn}}