{"id":40911,"date":"2026-09-01T09:51:37","date_gmt":"2026-09-01T07:51:37","guid":{"rendered":"https:\/\/smartdatamodels.org\/?p=40911"},"modified":"2026-09-01T10:37:49","modified_gmt":"2026-09-01T08:37:49","slug":"untp-digital-product-passport-joins-smart-data-models-date-2026-09-04-categories-announcements-candidates-sustainability-supplychain-tags-untp-digitalproductpassport-verifiablecredential","status":"publish","type":"post","link":"https:\/\/smartdatamodels.org\/index.php\/untp-digital-product-passport-joins-smart-data-models-date-2026-09-04-categories-announcements-candidates-sustainability-supplychain-tags-untp-digitalproductpassport-verifiablecredential\/","title":{"rendered":"UNTP Digital Product Passport Joins Smart Data Models: Two new candidate models \u2014 DigitalProductPassport and Product"},"content":{"rendered":"

Smart Data Models’ Candidates repository<\/a> now includes a new candidate standard, untp-v0.8.0<\/code><\/strong>, translated from the UN Transparency Protocol (UNTP) Digital Product Passport<\/strong> specification \u2014 a B2B data standard, issued as a W3C Verifiable Credential, for carrying product and sustainability information through supply chains. Two entities are covered: DigitalProductPassport<\/code><\/strong> and Product<\/code><\/strong>.<\/p>\n

What’s in it<\/h2>\n\n\n\n\n\n\n
Model<\/th>\nWhat it is<\/th>\n<\/tr>\n<\/thead>\n
DigitalProductPassport<\/code><\/td>\nThe W3C Verifiable Credential (VCDM 2.0) envelope: issuer, validity period, credential status, render method, issuing software.<\/td>\n<\/tr>\n
Product<\/code><\/td>\nThe core product data model: identification, classification, material provenance, producing facility, dimensions, packaging, performance claims, and an open industry-specific characteristics<\/code> extension point.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Every model ships the full set of Candidates artifacts: a JSON Schema, an NGSI-LD @context<\/code>, and all four example serializations (NGSI-v2 and NGSI-LD, key-values and normalized) \u2014 each validated against its own schema.<\/p>\n

Two entities, one relationship \u2014 not one flattened blob<\/h2>\n

In the source, DigitalProductPassport.json<\/code>‘s credentialSubject<\/code> is literally $ref: \"#\/$defs\/Product\"<\/code> \u2014 a 1:1 inline embedding. But Product.json<\/code> is also<\/em> published standalone, with its own complete identity independent of any credential wrapper. This candidate keeps that distinction: DigitalProductPassport<\/code> carries only the envelope fields plus a product<\/code> Relationship, and Product<\/code> is its own separately-addressable entity \u2014 avoiding a ~20-property duplication and matching how the source itself chose to publish two files, not one.<\/p>\n

The VC envelope fields (issuer DID, credential status, render method, issuing software) are modeled faithfully as real typed properties rather than simplified away \u2014 even though they’re strictly artifacts of the credential-verification layer, not “product data” per se.<\/p>\n

Real context, real examples \u2014 not invented<\/h2>\n

Two things set this translation apart from working off prose docs alone:<\/p>\n