The June 2025 UNTP meetings focused on roadmap alignment, specification maintenance, interoperability with adjacent standards, and increasing clarity around conformity credentials and verification methods.

Here’s the snapshot:

Roadmap and Coordination

An updated development roadmap was discussed, including timeframes for aligning the draft 0.6 release with documentation, test coverage, and community review. The community reaffirmed that 0.6 will include:

• Updated schemas and naming conventions for improved consistency.
• A cleaner, more stable Playground to support newcomers and formal implementers.
• Snapshot validation and testing automation established in May will continue as the mechanism for managing release readiness.

New working groups were formalised to support Adoption, Conformity Credentials, and Testing Frameworks.

Interoperability and Specification Maintenance

The group discussed how to improve clarity between UNTP and other initiatives, particularly the UNECE “UDP” (United Nations Digital Passport) and the Global Battery Alliance’s digital product passport.

• The UNTP specification is structured to be compatible with other open frameworks while remaining transport-focused and verifiable by design.
• Maintenance efforts will avoid locking in assumptions about external protocols while maintaining support for structured, linkable credentials.

Conformity Credentials and Trust Layers

The group explored a three-tier model for understanding and testing verifiable credentials within UNTP:

• Tier 1: Credential syntax and signature validity.
• Tier 2: Credential contents, including schema compliance and logic constraints.
• Tier 3: Inter-credential relationships, e.g. whether a claim is backed by a third-party conformity credential.

There was broad agreement on the importance of Tier 3 testing and its value in enabling policy alignment, incentive structures, and responsible data redaction. The framework allows implementers to communicate trustworthiness without exposing sensitive commercial data.

🔍 Key Clarifications

• A conformity credential does not necessarily mean audit or inspection by a third party. It can reflect internal conformity, machine-based checks, or delegated assurance models.
• Data minimisation remains a core principle. Redacted or summarised information is valid within the spec, provided the credential is structurally sound and verifiable.
• “Traceability” in UNTP is about data continuity, not full chain-of-custody by default. The Playground and documentation will continue to reinforce this distinction.

Interested in contributing?

If you have relevant expertise or would like to participate in pilots, working groups, or sector extensions, you’re welcome to join the conversation on UNTP Slack or GitHub. Contributions—whether technical, operational, or business-focused—are useful as the project scales up. More on the UNTP site.

Join the Pyx Community of Trust Architects!

• 📢 Chat on Pyx Zulip – Join real-time conversations with the community
• 💬 Join the Pyx Forums – Engage in discussions about the UNTP and related topics