Skip to main content

DPP Consumer Guide

Purpose​

This guide explains how consumers of products — including buyers, regulators, auditors, and business partners — should interpret and interact with Digital Product Passports (DPPs).
The goal is to help consumers make informed, trust-aware decisions before onboarding and during usage of a product.

Consumer Personas​

1. Buyers & End-Users​

  • Need to quickly check who owns the product, what it contains, and whether it is trustworthy.
  • Typically access the Lite DPP via a QR code or marketplace interface.
  • Expect a simple UI with clear trust signals.

2. Regulators​

  • Require verifiable trust evidence during audits.
  • Interact with Full DPPs, including Inline data and ByRef artifacts.
  • May validate provenance logs, policy compliance, and lineage graphs.

3. Auditors​

  • Independent third parties verifying product claims and compliance.
  • Use ByRef artifacts from the DPP for integrity checks (via hashes) and replay of provenance.
  • May query PROD knowledge graphs for cross-product reasoning.

4. Business Partners​

  • External enterprises consuming products as part of a joint venture or B2B arrangement.
  • Use DPPs to assess quality, SLAs, and interoperability before onboarding.
  • Often need access to both Lite (for quick checks) and Full (for operational contracts).

Lite vs Full DPP Consumption​

Lite DPP​

  • Inline data only.
  • Designed for quick inspection, such as:
    • Ownership & issuer
    • High-level schema snapshot
    • Simplified lineage (source → process → view)
    • Recent quality aggregates
    • Basic policy outcomes
  • Available via marketplace UI or QR code scan.
  • No additional API calls required.

When to use Lite DPP:

  • Buyers comparing multiple products.
  • Marketplace discovery.
  • Basic compliance verification.

Full DPP​

  • Inline + ByRef sections.
  • Includes:
    • Content-addressed schema files
    • Full lineage graphs
    • Provenance logs (ETL runs, code versions)
    • Complete data quality time series
    • Detailed policy evaluation reports
    • Knowledge graph snapshots
  • Supports integrity verification using hash fields.
  • May require pulling larger artifacts (e.g., Parquet logs, Turtle graphs).

When to use Full DPP:

  • Regulators during audits.
  • Auditors validating compliance.
  • Business partners negotiating interoperability.
  • Internal governance teams for deeper risk analysis.

Consumer Workflow​

Step 1. Discovery​

  • Scan QR code on product or select product from marketplace.
  • Retrieve Lite DPP payload.
  • View flattened trust signals in UI.

Step 2. Verification​

  • If required, pull the Full DPP from API.
  • Validate hashes of ByRef artifacts.
  • Cross-check provenance, lineage, and policies against organizational/regulatory requirements.

Step 3. Knowledge Graph Reasoning​

  • If onboarded, query the product’s PROD knowledge graph for semantic exploration.
  • Example: “Which downstream products depend on CBPaymentDataProduct?”

Step 4. Ongoing Monitoring​

  • Subscribe to product updates via marketplace or governance plane.
  • Track changes in DPP status (Valid, Revoked, Superseded).
  • Use Full DPP for audit trails when required.

Example: Buyer’s Lite View​

{
  "type": "dpp:Passport",
  "subject": "urn:ant:cb:prod:payment:v1.3.0",
  "issuer": "did:ant:cb:govl:platform",
  "issuedAt": "2025-10-04T10:00:00Z",
  "status": "Valid",

  "schemaInline": {
    "entities": [
      { "name": "Payment", "fields": [
        {"name":"payment_id","type":"string","key":true},
        {"name":"amount","type":"decimal"},
        {"name":"currency","type":"string(3)"}
      ]}
    ]
  },
  "qualityInline": { "window":"P30D", "aggregates": { "availabilityPct": 99.9 } },
  "policyInline": [{ "policyName":"DataResidency-EU", "result":"Pass" }]
}

Example​


{
  "type": "dpp:Passport",
  "subject": "urn:ant:cb:prod:payment:v1.3.0",
  "issuer": "did:ant:cb:govl:platform",
  "issuedAt": "2025-10-04T10:00:00Z",
  "status": "Valid",

  "schemaByRef": {
    "uri": "/schema/payment/1.3.0.json",
    "hash": "sha256-AAA",
    "mediaType": "application/json",
    "size": 48231
  },
  "lineageByRef": {
    "uri": "/lineage/cbpayment/2025-10-01.graph.json",
    "hash": "sha256-BBB",
    "mediaType": "application/json",
    "size": 220154,
    "capturedAt": "2025-10-01T23:59:59Z"
  },
  "provenanceByRef": {
    "uri": "/prov/cbpayment/2025Q4.log.parquet",
    "hash": "sha256-CCC",
    "mediaType": "application/parquet",
    "size": 1203301
  }
}

Consumer Recommendations​

  • Verify integrity: Always validate ByRef hash fields before trusting external artifacts.
  • Use Lite first: Quick checks and comparisons are best done via Lite DPP.
  • Pull Full when needed: Only regulators, auditors, and contractual partners need ByRef payloads.
  • Rely on PROD for reasoning: Use DPP for trust signals, PROD for semantics and graph traversal.
  • Check lifecycle: Ensure DPP status is Valid — avoid superseded or revoked products.

Summary​

  • This DPP Consumer Guide ensures that every stakeholder persona — from buyers to regulators — can interact with DPPs appropriately.
  • Lite DPPs = fast trust signals for discovery.
  • Full DPPs = deep evidence for verification and audits.
  • Together, they make product consumption more transparent, secure, and efficient.