dido:00-sip-ra:06-specific-requirements-on-proposals:06-2-scope-of-proposals-sought:06-2-2-out-of-scope:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
dido:00-sip-ra:06-specific-requirements-on-proposals:06-2-scope-of-proposals-sought:06-2-2-out-of-scope:start [2026/07/11 11:10] – ↷ Links adapted because of a move operation nick_didodido:00-sip-ra:06-specific-requirements-on-proposals:06-2-scope-of-proposals-sought:06-2-2-out-of-scope:start [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 3: Line 3:
 [[dido:00-sip-ra:06-specific-requirements-on-proposals:06-2-scope-of-proposals-sought:start|Return to Scope of Proposals Sought]] [[dido:00-sip-ra:06-specific-requirements-on-proposals:06-2-scope-of-proposals-sought:start|Return to Scope of Proposals Sought]]
  
-The requested [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]] is limited to architectural abstraction and governance constructs.+The requested [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]] is limited to architectural abstraction and governance constructs.
  
 The following exclusions clarify the boundaries of the requested Reference Architecture and prevent overlap with existing OMG specifications, domain standards, and implementation technologies. The following exclusions clarify the boundaries of the requested Reference Architecture and prevent overlap with existing OMG specifications, domain standards, and implementation technologies.
Line 10: Line 10:
   - Proposals SHALL NOT define transport protocols, message exchange frameworks, or runtime communication mechanisms.   - Proposals SHALL NOT define transport protocols, message exchange frameworks, or runtime communication mechanisms.
   - Proposals SHALL NOT replace, supersede, or modify existing OMG specifications addressing exchange, interoperability, or semantic federation.   - Proposals SHALL NOT replace, supersede, or modify existing OMG specifications addressing exchange, interoperability, or semantic federation.
-  - Proposals SHALL NOT standardise any specific ontology, vocabulary, or domain taxonomy.+  - Proposals SHALL NOT standardize any specific ontology, vocabulary, or domain taxonomy.
   - Proposals SHALL NOT define operational doctrine, mission procedures, or domain policy rules.   - Proposals SHALL NOT define operational doctrine, mission procedures, or domain policy rules.
   - Proposals SHALL NOT prescribe specific implementation technologies, deployment topologies, or system architectures.   - Proposals SHALL NOT prescribe specific implementation technologies, deployment topologies, or system architectures.
-  - Proposals SHALL NOT require the use of any specific modelling language, transport framework, or vendor tooling environment.+  - Proposals SHALL NOT require the use of any specific modeling language, transport framework, or vendor tooling environment.
  
 ---- ----
  • dido/00-sip-ra/06-specific-requirements-on-proposals/06-2-scope-of-proposals-sought/06-2-2-out-of-scope/start.1783793456.txt.gz
  • Last modified: 2026/07/11 11:10
  • by nick_dido