| Both sides previous revision Previous revision Next revision | Previous revision |
| public:00-sip-ra:05-general-requirements-on-proposals:05-1-requirements:05-1-2-pims-and-psms:start [2026/09/12 18:34] – ↷ Links adapted because of a move operation nick_dido | public:00-sip-ra:05-general-requirements-on-proposals:05-1-requirements:05-1-2-pims-and-psms:start [2026/09/15 10:31] (current) – nick_dido |
|---|
| [[public:00-sip-ra:06-specific-requirements-on-proposals:start|Section 6 Specific Requirements on Proposals]] specifies whether [[public:99_annexes:annex-b-terms-and-definitions:p:platform_independent_model|Platform Independent Models (PIMs)]], [[public:99_annexes:annex-b-terms-and-definitions:p:platform_specific_model|Platform Specific Models (PSMs)]], or both are solicited. | [[public:00-sip-ra:06-specific-requirements-on-proposals:start|Section 6 Specific Requirements on Proposals]] specifies whether [[public:99_annexes:annex-b-terms-and-definitions:p:platform_independent_model|Platform Independent Models (PIMs)]], [[public:99_annexes:annex-b-terms-and-definitions:p:platform_specific_model|Platform Specific Models (PSMs)]], or both are solicited. |
| |
| If proposals specify a PIM and corresponding PSMs, then the rules defining the mappings between the PIM and PSMs SHALL either be referenced in a standard mapping or specified in the proposal. | The following requirements apply when a Submission includes a PIM and one or more corresponding PSMs. |
| |
| To allow possible inconsistencies in a proposal to be resolved later, proposals SHALL identify whether the mapping technique or the resulting PSMs are normative. | ===== Requirements ===== |
| | |
| | ^ Requirement ^ Level ^ Statement ^ |
| | | [[public:00-sip-ra:99-annexes:annex-c-requirements:gpr-003-pim-to-psm-mapping-definition|GPR-003 — PIM-to-PSM Mapping Definition]] | Mandatory when applicable | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:gpr-003-pim-to-psm-mapping-definition#Statement&noheader&nofooter&noeditbtn}} | |
| | | [[public:00-sip-ra:99-annexes:annex-c-requirements:gpr-004-pim-to-psm-normative-authority|GPR-004 — PIM-to-PSM Normative Authority]] | Mandatory when applicable | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:gpr-004-pim-to-psm-normative-authority#Statement&noheader&nofooter&noeditbtn}} | |
| | |
| | ===== Notes for Editors ===== |
| | |
| | The requirement identifiers and short titles link to the authoritative requirement records in Annex C. |
| | |
| | The Statements displayed in this section are transcluded from their corresponding Annex C requirement pages and are not independently maintained copies. |
| | |
| | Make changes to a Statement or its Requirement Level on its Annex C requirement page. |
| | |
| | GPR-003 and GPR-004 are mandatory when a Submission specifies a PIM and one or more corresponding PSMs. |
| | |
| | GPR-003 requires either a reference to an applicable standard mapping or a specification of the mapping rules used by the Submission. |
| | |
| | GPR-004 requires the Submission to identify which representation has normative Authority when the mapping rules and resulting PSMs are inconsistent. Assigning independent normative Authority to both without defining precedence does not provide an unambiguous means of resolving an inconsistency. |
| |
| ---- | ---- |
| © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. |
| </WRAP> | </WRAP> |
| |