Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| public:00-sip-ra:06-specific-requirements-on-proposals:06-3-relationship-to-other-omg-specifications:06-3-3-modeling-neutrality:start [2026/09/12 18:33] – removed - external edit (Unknown date) 127.0.0.1 | public:00-sip-ra:06-specific-requirements-on-proposals:06-3-relationship-to-other-omg-specifications:06-3-3-modeling-neutrality:start [2026/09/14 18:06] (current) – nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== 6.3.3 Modeling Neutrality ====== | ||
| + | [[public: | ||
| + | |||
| + | The proposed [[public: | ||
| + | |||
| + | Modeling neutrality applies to implementations claiming conformance to the Reference Architecture. It does not prevent the adopted specification from using an OMG modeling language, notation, or interchange format to express and distribute its normative [[public: | ||
| + | |||
| + | ===== Requirements ===== | ||
| + | |||
| + | ^ Requirement ^ Statement ^ | ||
| + | | [[public: | ||
| + | | [[public: | ||
| + | | [[public: | ||
| + | |||
| + | ===== 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 the corresponding Annex C requirement pages and are not independently maintained copies. | ||
| + | |||
| + | Make changes to a Statement on its Annex C requirement page. | ||
| + | |||
| + | SIP-001 establishes the general platform independence of the proposed Reference Architecture. SIP-039 applies that principle specifically to its architectural modeling. | ||
| + | |||
| + | SIP-030 establishes general tool and technology neutrality. SIP-041 applies that principle specifically to modeling languages, model-interchange formats, and modeling tools used by conforming implementations. | ||
| + | |||
| + | SIP-002 requires the Submission to include a formal PIM. The adopted specification may select an OMG modeling language and a standardized interchange format to express and distribute that normative model. Such specification-authoring choices do not become required implementation technologies or tools. | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||