What question did this study set out to answer?

The aim is to establish a governance framework for persistent data artifacts within the SDIA ecosystem.

April 26, 2026Open Access

Data Domain-Centric Pattern ( DDCP ) - The Semantic Domain Data Layer of the SDIA Ecosystem v1.0 - FINAL

Key Points

The aim is to establish a governance framework for persistent data artifacts within the SDIA ecosystem.
Defined the architecture and governance principles for the Data Domain-Centric Pattern Layer 5 within SDIA.
Outlined the roles of various data types and their governance, including databases, schemas, and datasets.
Established validation rules and security policies for domain-scoped data management.
Implemented a governance model that enhances ownership and traceability of data artifacts.
Defined structural components of data organization, creating seamless integration across data layers.
Ensured domain authority plays a critical role in lifecycle governance and security policies.

Abstract

DDCP — Data Domain-Centric Pattern Layer 5 of the SDIA Ecosystem — v1. 0 Zenodo: 10. 5281/zenodo. 19730519🔗 https: //zenodo. org/record/19730519 DDCP is the semantic topology governance layer for persistent data fabrics within the SDIA ecosystem (Semantic Domain Integration Architecture). Its role is not to define query logic, storage tuning, or data-processing pipelines, but to govern how persistent data artifacts — databases, schemas, tables, collections, buckets, cache namespaces, datasets, and snapshots — are named, segmented, owned, and audited. In DDCP, the domain becomes the primary key of all persistent data topology. The same domain token that appears at the gateway (GDCR), routing (DDCR), orchestration (ODCP), and event (EDCP) layers continues unchanged into the data layer. The artifact is not immutable. Governance, ownership, and traceability are the goals. What DDCP covers: ↳ Databases and catalogs↳ Schemas and namespaces↳ Tables and collections↳ Object storage buckets and prefixes↳ Cache namespaces and cache keys↳ Analytical datasets and views↳ Snapshots and exports Canonical vs Derived Data: Canonical data — owned by the producer domain. Example: salesₒrdersₒrderₕeader Derived data — created for analytics, reporting, exports. Example: finance. invoicing. order. reporting ABNF grammar (RFC 5234) for persistent data artifacts. PVRL Level 5 validation rules. Domain Authority ownership and lifecycle governance. Domain-scoped security policies (sales_%, sales: *, sales/orders/*). This is the initial publication of DDCP. Further updates may follow as the pattern matures in real-world data landscapes. Author: Ricardo Luz Holanda Viana · ORCID: 0009-0009-9549-5862Repository: github. com/rhviana/deipDEIP Ecosystem DOI: 10. 5281/zenodo. 19004802License: CC BY 4. 0 Citation: Viana, R. L. H. (2026). Data Domain-Centric Pattern (DDCP) — Version 1. 0. Zenodo. https: //doi. org/10. 5281/zenodo. 19730519 The domain is the map. The storage engine is the territory. A map that matches the territory never lies. 👁️

Read Full Paperexternally

Mark Helpful

Bookmark

Relay

View Full Paper