Digital Electronic Goods Passport
The RBTP Knowledge Base is evolving weekly as part of our pilot programs with RBA members. We’d love your input — submit feedback or help shape the protocol in real time by joining a pilot.
Digital Electronic Goods Passport (DEGP): Implementation Guide
If you're looking for an Overview, go to Digital Electronic Goods Passport Overview
The Digital Electronic Goods Passport (DEGP) is a commodity-specific extension of the UNTP Digital Product Passport (DPP). It is designed to meet the unique traceability, compliance, and circularity needs of electrical and electronic goods.
Before implementing a DEGP, implementers should become familiar with the core UNTP DPP Specification, which defines the base structure, vocabulary, and requirements shared by all passport types in the RBTP ecosystem.
📦 DEGP Profile Information
| Name | Current Version | Status | Release Date | UNTP dependency |
|---|---|---|---|---|
| Digital Electrical Goods Passport (DEGP) | 0.1.0 | Draft | 10-04-2025 | UNTP DPP v0.5.0 |
🔧 What Makes the DEGP Unique?
While a DEGP reuses the full UNTP DPP model, it introduces an additional specification layer with structures and rules tailored to electronics. These include:
- A new
ElectricalGoodsSpecificationsextension block (for firmware, embedded components, voltage ratings, etc.) - Stricter field requirements for product IDs, classification schemes, and traceability references
- Controlled vocabularies for circularity, repairability, and compliance topics
- Encouragement to use linked passports (e.g., DBP for batteries) wherever applicable
The DEGP is modular—not every electronic product requires every field—but validators and CABs may enforce stricter conformance depending on your pilot or compliance target..
📐 Logical Model
A visual overview of the DEGP profile and extensions is available here:
Logical Model: Digital Electrical Goods Passport.
Core structure: identical to the UNTP DPP with these additions:
electricalGoodsSpecifications(new object block)
📏 Profile Rules
Note: This section outlines constraints and required patterns that make a valid DEGP.
TBD
Note: This section defines strict dependencies and requirements for product information. For instance, the ID field may be required to originate from a designated register, product.productCategory must conform to recognized international coding schemes, Claim.assessmentCriteria must be selected from predefined controlled vocabularies, etc.
| Field | Requirements |
|---|---|
id | Must be a globally resolvable URI (preferably did:web or GS1 identifier) |
product.productCategory | Must conform to a recognized product classification system (e.g., UN CPC, HS, or industry standard) |
conformityClaim.assessmentCriteria | Must reference RBTP-approved controlled vocabularies |
traceabilityInformation.traceabilityEvent[].linkType | Must be drawn from the UNTP vocabulary |
electricalGoodsSpecifications | Required for all products with firmware, embedded batteries, or voltage/amperage ratings |
producedAtFacility | Should reference a resolvable and verifiable identifier (e.g., GS1 GLN, cadastral boundary ID) |
A JSON Schema validator will be made available in a future stable release.
🛠 Technical Artifacts
These artifacts are in development. Once published, they will include:
- JSON-LD
@contextfor DEGP extension fields - JSON Schema validator for DEGP conformance
- Controlled vocabularies and code lists (repairability, safety topics, classification)
- Sample DEGP instances (e.g., laptop, e-scooter, refurbished phone)
📝 Status: Draft format available internally via Notion; will be moved to RBTP GitHub once stable.
📄 Working Sample
| Clickable Link | Scan the QR | Comments |
|---|---|---|
| Electrical Goods Passport |  | This is a sample DEGP, work in progress. At the moment, it is still using the UNTP DPP schema as the base. Click on the JSON tab to see the underlying RBTP data. Download the signed credential to test verification in your own system |