A data domain (domain) is a defined grouping of properties to allow the users to view the data with a perspective that highlights the particular properties of the data. The data domain defines the model schema (model) and other properties for that specific focus. Common examples of data domains are customers, students, employees, parts and product orders.
...
Once a version of a domain is created and its data records (DRs) are loaded (or mapped in a federated model), it can be referenced by other data domains, adaptors and by API consumers as a source of truth. Domains have version numbers so numbers so that other domains, adaptors and applications can bind to a specific domain and version (e.g. students:v3). Data governance can designate data at specific adaptors as the master data and can control which zone has the appropriate ACLs to access and update it.
...
Domain Model Schemas
A domain model schema (model) is a JSON object describing the schema for a data domain; it defines the properties that make up the domain's schema. The root node of the model schema is the properties element. See Valid Property Names and Valid Types for ModelSchema Properties below.
...
With the domain in place, its first version can be created. The domain version defines the properties that make up the domain version's model schema. You may want to create a new version if you want to add more properties to the model, for instance. The domain version numbers are automatically generated and start with 1 and continue in ascending order. The root node of the model schema is the properties element. See Valid Property Names and Valid Types for ModelSchema Properties below.
...