SIP-001 — Platform-Independent Reference Architecture [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== SIP-001 — Platform-Independent Reference Architecture ======

[[public:00-sip-ra:99-annexes:annex-c-requirements:start|Go to Annex C: Requirements]]

===== Statement =====

The proposed [[public:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]] SHALL be platform independent.

===== Rationale =====

Platform independence allows the Reference Architecture to define architectural concepts, responsibilities, relationships, and interactions without requiring a particular operating system, runtime environment, middleware product, programming language, data-storage technology, deployment environment, or vendor implementation.

This separation permits the same Reference Architecture to support multiple platform-specific realizations. It also promotes portability, interoperability, reuse, technology evolution, and competition among conforming implementations.

===== Evaluation Criteria =====

The Submission satisfies this requirement when:

  - The Reference Architecture is specified without requiring a particular implementation platform or product
  - Its architectural elements, roles, relationships, and interactions are expressed independently of platform-specific technologies
  - Platform-specific examples or mappings are clearly distinguished from the platform-independent architecture
  - The architecture permits realization on more than one implementation platform
  - Conformance to the Reference Architecture can be evaluated without requiring a particular vendor technology

===== Referenced By =====

{{backlinks>public:00-sip-ra:99-annexes:annex-c-requirements:sip-001-platform-independent-reference-architecture}}

===== Notes for Editors =====

SIP-001 establishes platform independence as a property of the proposed Reference Architecture.

[[public:00-sip-ra:99-annexes:annex-c-requirements:sip-002-formal-platform-independent-model|SIP-002 — Formal Platform Independent Model]] separately requires the Submission to provide a formal Platform Independent Model of that architecture.

Platform independence does not prohibit platform-specific implementations, mappings, examples, or profiles. Such material must remain distinguishable from the platform-independent architectural definition.

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>