GPR-017 — Minimal Interoperability Constraints [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-017 — Minimal Interoperability Constraints ======

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

===== Statement =====

The proposed specification SHALL NOT constrain implementations beyond what is necessary to support required [[public:99_annexes:annex-b-terms-and-definitions:i:interoperability|Interoperability]].

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

Mandatory

===== Rationale =====

Interoperability may require normative constraints on externally observable behavior, information structures, interfaces, interaction rules, or conformance conditions. Constraints unrelated to an identified Interoperability requirement unnecessarily restrict implementation choice, inhibit innovation, and may create avoidable dependencies on particular technologies or products.

Each implementation constraint should therefore be limited to what is necessary to satisfy a defined Interoperability need.

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

A conforming Submission demonstrates that:

* Each normative implementation constraint is traceable to an identified Interoperability requirement
* The necessity of each such constraint is stated or can be objectively established
* Internal design choices remain open when they do not affect required Interoperability
* The proposed specification does not impose unrelated product, platform, vendor, language, framework, or deployment restrictions
* Alternative implementation approaches are permitted when they provide equivalent conformance and Interoperability
* Conformance criteria assess required outcomes without unnecessarily prescribing implementation methods

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

{{backlinks>public:00-sip-ra:99-annexes:annex-c-requirements:gpr-017-minimal-interoperability-constraints}}

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

This requirement does not prohibit normative constraints. It limits them to constraints necessary to support an identified Interoperability requirement.

Security, safety, compatibility, or other constraints imposed by separate applicable requirements should be governed and justified by those requirements rather than characterized as Interoperability constraints.

To transclude the authoritative Statement into another page, use:

<code dokuwiki>
{{section>public:00-sip-ra:99-annexes:annex-c-requirements:gpr-017-minimal-interoperability-constraints#Statement&noheader&nofooter&noeditbtn}}
</code>

---

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