Skip to main content

Product Ontology

1. Introduction​

Within the Base Product Specification (BPS), a fundamental question arises: where does a product exist?
Is it the specification that defines it, the system that deploys it, or the interface through which it is consumed?

Traditional approaches tend to reduce a product to a single manifestation — a dataset, an API, a model, a service, or a physical artifact. While convenient, such reductions are incomplete and lead to fragmentation across domains, roles, and systems.

BPS adopts a different position.

A product does not reside in a single artifact or system.
It exists as a multi-perspective construct, expressed through coordinated representations across distinct layers of concern.

This section formalizes that position.

2. The Problem of Reduction​

Across industries and disciplines, products are often conflated with one of their representations:

  • A Book Product is treated as a digital file or printed volume
  • A Movie Product is treated as a video file or streaming asset
  • A Comic Product is treated as a sequence of images or pages
  • An AI product is treated as a trained model
  • A software product is treated as a service endpoint
  • A data product is treated as a dataset or pipeline
  • A physical product is treated as a manufactured object
  • A Business Product is treated as a service offering or transaction capability

These interpretations are not incorrect, but they are partial. Each reflects the perspective of a specific stakeholder, system, or lifecycle stage.

Without a unifying model, this leads to:

  • Misalignment between business, engineering, and governance
  • Loss of traceability between intent and realization
  • Inconsistent definitions across domains
  • Difficulty in automation, interoperability, and audit

BPS addresses this by separating product identity from its representations.

3. Core Principle​

A product within BPS is a single logical identity that manifests across multiple ontological layers, each providing a valid, role-dependent projection of that product.

These projections are not competing descriptions. They are coherent, coordinated, and necessary views of the same product.

4. Ontological Layers of a Product​

BPS recognizes five fundamental layers through which a product exists and is understood:

4.1 Intent Layer​

The Intent Layer captures why the product exists.

It includes:

  • Purpose and value proposition
  • Target consumers and stakeholders
  • Expected outcomes and usage context

This layer is business-native and independent of implementation.

4.2 Semantic Layer (PROD)​

The Semantic Layer defines what the product is.

It includes:

  • Conceptual structure and meaning
  • Domain semantics and definitions
  • Discoverability and descriptive metadata

In BPS, this layer is formalized through the Product Descriptor (PROD).

4.3 Realization Layer (PDS)​

The Realization Layer defines how the product is constructed and deployed.

It includes:

  • Architecture and infrastructure
  • Execution logic and dependencies
  • Deployment environments and configurations

In BPS, this layer is formalized through the Product Deployment Specification (PDS).

4.4 Governance Layer (Policies and DPP)​

The Governance Layer defines how the product is controlled, trusted, and regulated.

It includes:

  • Access and entitlement policies
  • Compliance, risk, and regulatory constraints
  • Lineage, observability, and audit signals

This layer is expressed through:

  • Policy definitions
  • The Digital Product Passport (DPP), which provides a verifiable trust envelope for the product

4.5 Experience Layer (Ports)​

The Experience Layer defines how the product is accessed and consumed.

It includes:

  • Interfaces such as APIs, data outputs, user interfaces, or physical interaction points
  • Contracts governing consumption
  • Output ports that expose the product to consumers

This is the layer through which value is realized.

5. Product Ontology Diagram​

The diagram below illustrates how a single product identity manifests across multiple ontological layers and stakeholder perspectives.

6. Stakeholder Projections​

Each stakeholder interacts with the product through a specific layer, forming a distinct but valid projection:

StakeholderPrimary View of the Product
Product Owner / BusinessIntent (purpose, value, outcomes)
Specification ConsumerSemantic definition (PROD)
Platform / EngineeringRealization (PDS and execution)
Governance / AuditPolicies, lineage, and trust signals
End Consumer / SystemInterfaces and output ports

These views do not conflict. They are aligned through a shared product identity and coordinated through BPS constructs.

7. Relationship to BPS Constructs​

BPS introduces formal constructs to stabilize and coordinate these layers:

  • PROD represents the semantic definition of the product
  • PDS represents the realization and deployment of the product
  • DPP provides the trust and governance envelope

It is therefore essential to distinguish:

A product is not equivalent to its PROD or its PDS.

Instead:

A product is the identity that binds PROD, PDS, policies, and experience into a coherent whole.

8. Product as a Boundary Object​

In BPS terms, a product functions as a boundary object.

A boundary object:

  • Exists across multiple domains and stakeholder groups
  • Is interpreted differently in each context
  • Maintains a stable identity that enables coordination

This property allows:

  • Business and engineering to collaborate without collapsing their perspectives
  • Governance to operate independently of implementation details
  • Consumers to interact with products without requiring internal knowledge

BPS formalizes this behavior through structured artifacts and explicit separation of concerns.

9. Implications​

Adopting this ontology has several important implications:

9.1 Separation of Concerns​

Each layer evolves independently while remaining coordinated through shared identity and lineage.

9.2 Artifact Integrity​

PROD, PDS, and DPP are distinct, versioned artifacts.
They must not be conflated or mutated in place.

9.3 Traceability​

Every realization of a product can be traced back to:

  • Its intent
  • Its semantic definition
  • Its governing policies

9.4 Multi-Form Realization​

A single product identity may manifest as multiple runtime forms (e.g., different environments, interfaces, or delivery modes) without losing coherence.

9.5 Cross-Domain Applicability​

This model applies uniformly across:

  • Data products
  • AI products
  • Software products
  • Physical products

10. Canonical Statement​

A product within the Base Product Specification is a multi-perspective construct, existing simultaneously across intent, semantic, realization, governance, and experience layers, and unified by a single, stable identity and lineage.

11. So to Recap ...​

By distinguishing a product from any single artifact or system, BPS provides a durable and extensible foundation for product definition across domains.

This ontology enables:

  • Clear communication across stakeholders
  • Strong governance and auditability
  • Automation through machine-readable specifications
  • Interoperability across diverse product ecosystems

In doing so, BPS elevates product definition from an implementation concern to a first-class architectural and conceptual discipline.