GPR-016 — Avoidance of Normative Implementation Descriptions

Go to Annex C: Requirements

The Submission SHOULD NOT include implementation-specific descriptions as normative specification content.

Recommended

Implementation-specific descriptions can unintentionally constrain otherwise valid implementations or cause readers to interpret an example implementation as a conformance requirement.

A Submission may include implementation examples, guidance, and explanatory material when they improve understanding. Such material should be clearly identified as nonnormative and should not restrict alternative conforming implementations.

A Submission satisfying this recommendation demonstrates that:

* Normative specification content defines required behavior, responsibilities, interfaces, constraints, and conformance conditions without prescribing implementation internals * Implementation-specific descriptions are omitted from normative clauses unless necessary to satisfy an applicable requirement * Implementation examples are clearly identified as nonnormative * No example is presented as the only permitted implementation approach * Any departure from this recommendation is identified and justified

This requirement uses SHOULD NOT and is therefore a recommendation rather than an absolute prohibition.

Informative implementation examples remain permitted when they are clearly distinguished from normative specification content.

To transclude the authoritative Statement into another page, use:

{{section>public:00-sip-ra:99-annexes:annex-c-requirements:gpr-016-avoidance-of-normative-implementation-descriptions#Statement&noheader&nofooter&noeditbtn}}

—