A  Data Asset  represents the abstract structure of any kind of data that can be processed and memorized by a Business Software System.

A  Data Asset is either a Data Entity or a  Data Property.

Only Data Entitys can have identity and states.  Data Propertys only handle raw data.

 Data Assets are managed in Data Catalogs.

A  Physical Data Asset  represents the physical structure of any kind of data that can be memorized by a Business Software System.

A  Physical Data Asset is either a Physical Data Entity or a Physical Data Property.

Only Physical Data Entitys can have an identity can by be referenced by Physical Relationship. Physical Data Property only handle raw data.

A  Physical Data Domain is subset of the metadata of an enterprise’s data store.

For instance, a "Sales"  Physical Data Domain contains a "Client" Table and a "Order" Table.

Each Physical Data Entity in a  Physical Data Domain has CRUD characteristics. For instance, the "Client" Table in the "Sales"  Physical Data Domain, has all CRUD characteristics.

 Physical Data Domains define functional data boundaries used both for Data Allocation to Business Systems (see Resource Agent Store) and data governance for data stewardship (see Data Catalog).

A  Physical Data Entity is a representation the physical structure of a Data Entity as it will be stored in a DBMS.

A  Physical Data Entity has an independent existence and can be uniquely identified.

A  Physical Data Entity is characterized by Physical Relationships it has with other  Physical Data Entity(ies) and by Physical Data Property(ies).

A  Physical Data Property is a Physical Data Asset that is fundamentally defined by its value. It doesn't evolve over time is thereby immutable.

It represents a data structure that is stored in any kind of data store: databases, data files.

For instance an "address" or a "customer name" are usually considered as  Physical Data Property(ies).