Verified claims

How PDTF transactions are wrapped as W3C Verifiable Credentials so the producer signs their fragment and the consumer can verify provenance without trusting any intermediary. The detailed pattern lives in the verifiedClaims sub-schema; this page is a stub pending deeper documentation.

The shape

A PDTF Verified Claims document is a W3C VC 2.0 envelope whose credentialSubject targets a JSON Pointer path inside a PDTF transaction. Multiple claims can exist in one document — different producers signing different fragments of the same transaction.

Source material

• schemas/src/schemas/verifiedClaims/README.md — README of the verified-claims sub-schema
• schemas/src/schemas/verifiedClaims/ — schema files
• source/03-standards/trust-framework/ — Mintlify-published spec
• External: W3C VC Data Model 2.0, W3C DID 1.0

Validating a claim

Use validateVerifiedClaims from the schemas package — see Validation → validateVerifiedClaims().

What needs writing

• End-to-end signing example with did:key
• The PDTF-specific credentialSubject path conventions
• Multi-party signing patterns (estate agent + conveyancer co-signing a property pack)
• Revocation and update semantics