Implementation — overview
This section is the engineer's view of PDTF. The Modelling section explains the vocabulary; this section is about building software that produces, validates, transmits and verifies PDTF transactions.
The five-piece stack
flowchart TB
classDef pkg fill:#eef4f8,stroke:#1a4d80,color:#0b2545,stroke-width:2px;
classDef spec fill:#fef3c7,stroke:#b45309,color:#7c2d12;
classDef proc fill:#dbeafe,stroke:#1e40af,color:#1e3a8a;
S1["@pdtf/schemas
npm · v3.4.0"]:::pkg S2["@pdtf/api
OpenAPI spec"]:::spec S3["trust-framework
spec repo"]:::spec S4["@pdtf/accreditation
conformance test suite"]:::pkg S5["W3C VC / DID
verified claims wrapper"]:::pkg P[Your product]:::proc S1 -.consumed by.-> P S2 -.consumed by.-> P S3 -.bound by.-> P P --> S4 P --> S5
npm · v3.4.0"]:::pkg S2["@pdtf/api
OpenAPI spec"]:::spec S3["trust-framework
spec repo"]:::spec S4["@pdtf/accreditation
conformance test suite"]:::pkg S5["W3C VC / DID
verified claims wrapper"]:::pkg P[Your product]:::proc S1 -.consumed by.-> P S2 -.consumed by.-> P S3 -.bound by.-> P P --> S4 P --> S5
Most integrations consume Schemas + API spec; serious ones also satisfy
the trust framework's accreditation criteria and emit Verifiable Credentials.
The pieces
| Component | Where it lives | What it gives you |
|---|---|---|
| Schemas package | npm: @pdtf/schemas · source: source/03-standards/schemas/ |
The base PDTF transaction schema + 18 main overlays + 16 extension overlays. Functions to merge them, validate, walk paths. See Schema composition. |
| OpenAPI spec | Source: source/03-standards/api/ |
v1.2 of the HTTP API. Defines the endpoints for transaction exchange. Implement on your side; or consume someone else's. |
| Trust framework spec | Source: source/03-standards/trust-framework/ |
The rules of the road — governance, security, audit, accreditation criteria. Published as a Mintlify docs site. |
| Accreditation | Conformance test suite (to be released) | Mechanically check whether your implementation meets the criteria for OPDA-accredited intermediary or certified data source. |
| Verified claims | W3C VC Data Model 2.0 + DID 1.0 | Wrapping PDTF transaction fragments as signed Verifiable Credentials for cross-party trust. See Verified claims. |
Common integration paths
| Use case | Likely overlays | Stack needed |
|---|---|---|
| Estate-agent product showing material-info-compliant listings | baspi5, nts2, ntsl2 |
Schemas package + minimal API client |
| Conveyancer firm consuming a property pack | ta6, ta7, ta10, lpe1 |
Schemas + API consumer |
| Lender taking a mortgage application | fme1 |
Schemas + verified-claims verifier (need to trust the data) |
| Search-product provider | con29R, con29DW, llc1, oc1, rds |
Full stack — you're a certified data source |
| Property tech orchestrator | Many overlays composed at runtime | Full stack incl. accreditation as intermediary |
Sub-pages
- Quickstart — install + first validation in ~3 minutes
- Schema composition — overlay merge mechanics
- Validation — Ajv, getValidator, validateVerifiedClaims
- Verified claims — VC/DID integration (stub)