The Data Product Standard application organizes information into 30 object types, grouped by purpose into six groups. Each group’s own page documents its object types and their attributes in full.
Explore by group
- Product core — the data product itself, its domain, use cases, strategy, and KPIs.
- Ports — the output, input, and management ports that expose and consume data.
- Data contract and schema — the data contract and its schema, servers, and supporting elements.
- Quality and SLA — data quality frameworks and checks, and service level agreements.
- Commercial — pricing plans, licenses, the data holder, and payment gateways.
- People and support — teams, roles, and support channels on a data contract.
For explanations of these object types rather than their fields, see What are data products, Ports, Data contracts, Data quality and SLAs, and Pricing, licensing, and data holders.
Available object types
Every object type includes a rich-text Description. The domain and data_product object types also carry ownership: an owner and a steward, with data_product adding a custodian, a subject-matter expert, and a producer.
| Group | Object type | Purpose |
|---|---|---|
| Product core | Domain (domain) | A logical grouping of related data products. |
| Product core | Data product (data_product) | An open data product that provides well-defined, governed data. |
| Product core | Use case (use_case) | A business use case the data product supports. |
| Product core | Product strategy (product_strategy) | Business alignment and goal tracking for the product. |
| Product core | KPI (kpi) | A key performance indicator for a product strategy. |
| Product core | Application overview (app_overview) | The application landing page. |
| Ports | Output port (output_port) | Delivery endpoint — what the product provides to consumers. |
| Ports | Input port (input_port) | Consumption endpoint — what the product takes from upstream sources. |
| Ports | Management port (management_port) | Operational endpoint for monitoring, health checks, and logging. |
| Data contract and schema | Data contract (data_contract) | Contract specification, governance terms, and access control. |
| Data contract and schema | Schema object (schema_object) | A dataset or table defined within a data contract schema. |
| Data contract and schema | Schema property (schema_property) | A column or field within a schema object. |
| Data contract and schema | Server (server) | Physical location and connection details for a data contract. |
| Data contract and schema | Schema relationship (schema_relationship) | A foreign-key style link between schema elements. |
| Data contract and schema | Authoritative definition (authoritative_definition) | A link to an authoritative external source. |
| Data contract and schema | Custom property (custom_property) | A custom key/value pair extending a standard element. |
| Quality and SLA | Data quality (data_quality) | A data quality measurement framework. |
| Quality and SLA | Quality dimension (data_quality_dimension) | A quality metric within a data quality definition. |
| Quality and SLA | Quality check (quality_check) | A single data quality check definition. |
| Quality and SLA | SLA (sla) | A service level agreement definition. |
| Quality and SLA | SLA dimension (sla_dimension) | A performance metric within an SLA. |
| Quality and SLA | SLA property (sla_property) | A service level property on a data contract. |
| Commercial | Pricing plan (pricing_plan) | A monetization model and cost structure. |
| Commercial | License (license) | Legal usage rights and restrictions. |
| Commercial | Data holder (data_holder) | The organization providing the data product. |
| Commercial | Payment gateway (payment_gateway) | A payment processing system. |
| People and support | Team (team) | A team defined on a data contract. |
| People and support | Team member (team_member) | A member of a team. |
| People and support | Role (role) | An access control role for a data contract. |
| People and support | Support channel (support_channel) | A dedicated support channel for a data contract. |
How the object types connect
The application arranges objects in a containment hierarchy, shown as the navigation tree in the left panel. The diagram below shows how each object type nests under a parent type.
The same hierarchy in outline form:
- Domain
- Nested domains
- Data contracts
- Data products
- Use cases
- Input ports, output ports, and management ports
- Data contracts
- Schema objects → schema properties
- Servers
- Roles
- Support channels
- Quality checks
- Teams → team members
- SLA properties
- SLAs → SLA dimensions
- Data qualities → quality dimensions
- Pricing plans
- Licenses
- Data holders
- Payment gateways
- Product strategy → KPIs
Authoritative definitions and custom properties attach to data contracts and their schema elements to add external references and extra key/value fields.
Lineage runs separately, through the ports: an output port is the data source of an input port (output_port → input_port), and Dawiso uses these links to draw lineage between data products.