This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |
| dido:00-sip-ra:06-specific-requirements-on-proposals:06-2-scope-of-proposals-sought:start [2026/07/11 11:10] – ↷ Links adapted because of a move operation nick_dido | dido:00-sip-ra:06-specific-requirements-on-proposals:06-2-scope-of-proposals-sought:start [2026/07/11 11:15] (current) – ↷ Links adapted because of a move operation nick_dido |
|---|
| [[dido:00-sip-ra:06-specific-requirements-on-proposals:start|Return to Specific Requirements on Proposals]] | [[dido:00-sip-ra:06-specific-requirements-on-proposals:start|Return to Specific Requirements on Proposals]] |
| |
| The requested [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:p:platform_independent_model|Platform Independent Model (PIM)]] is limited to architectural abstraction and governance constructs governing structured information processing. | The requested [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_independent_model|Platform Independent Model (PIM)]] is limited to architectural abstraction and governance constructs governing structured information processing. |
| |
| The requested PIM does not extend to domain-specific data content, transport protocols, deployment topologies, or implementation technologies. | The requested PIM does not extend to domain-specific data content, transport protocols, deployment topologies, or implementation technologies. |
| |
| The requested [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]] operates at the structural and governance abstraction layer. It defines separation of concerns, lifecycle control, and conformance boundaries. | The requested [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]] operates at the structural and governance abstraction layer. It defines separation of concerns, lifecycle control, and conformance boundaries. |
| |
| The requested Reference Architecture complements existing OMG specifications addressing exchange, interoperability, and semantic federation. It does not duplicate or replace those specifications. | The requested Reference Architecture complements existing OMG specifications addressing exchange, interoperability, and semantic federation. It does not duplicate or replace those specifications. |