Table of Contents

SIP-024 — Domain-Specific Content Exclusion

Go to Annex C: Requirements

Statement

The proposed Reference Architecture SHALL NOT define Domain-specific Data content or operational Data Models.

Rationale

SIP-RA provides architectural abstractions for structured information processing across multiple Domains. Defining the operational Data content of a particular Domain would narrow the Reference Architecture and could conflict with existing Domain standards, authorities, and information Models.

Domain communities retain responsibility for their operational Data Models, field definitions, permitted values, and information content. SIP-RA defines how to represent, govern, exchange, map, and interpret such content without standardizing the content itself.

Evaluation Criteria

The Submission satisfies this requirement when the proposed Reference Architecture:

  1. Avoids defining normative Domain-specific fields, records, messages, values, or operational Data sets
  2. Avoids defining an operational Data Model for a particular mission or industry
  3. Represents Domain-specific Data Models as governed inputs, specializations, or external Artifacts
  4. Permits different Domains to use their own authoritative Data content and Models
  5. Distinguishes nonnormative Domain examples from the normative Reference Architecture
  6. Avoids making conformance dependent on the use of a particular Domain Data Model

Referenced By

Notes for Editors

This exclusion does not prevent the Reference Architecture from defining abstract constructs for Data, Structure, Data Models, mappings, or information exchange.

A Submission may include Domain-specific examples to demonstrate the architecture, provided that the examples remain nonnormative and do not constrain other Domains.


© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.