Schema Page 35 Generated 2026-05-17 DAMA · Data Modeling & Design · Reference & Master Data
Transaction & participants 40 leaves100.0% Declaration 0.0% Evidence 0.0% Derivation 5 in overlays 2 with worked example
A PDTF transaction starts with who's involved . Participants are people and organisations attached to a transaction with a role (seller, buyer, estate agent, conveyancer, surveyor, lender), an identity, a contact surface, and — for sellers — a capacity explaining their authority to convey (legal owner, personal representative, attorney, mortgagee in possession).
Mentioned but not owned here. This page references but does not own address (canonical home page 37 for property address; this page owns participant address).
The claim
Every claim, every signature, every milestone in the transaction is anchored to a participant — this page maps the anchor.
Why this aggregate exists
Every other Schema page hangs off this one. A claim about the property has no meaning without an asserter; an evidence document has no force without an issuer; a milestone has no actor without a participant. The aggregate cohesion test holds because all of these leaves share a single lifecycle (created at instruction, updated through the transaction, closed at completion) and a single root authority (the PDTF-compliant software platform that owns the user account).
Entity relationships
---
config:
layout: elk
elk:
direction: DOWN
nodePlacementStrategy: BRANDES_KOEPF
mergeEdges: false
---
erDiagram
Transaction ||--o{ Participant : "participants"
Participant ||--o| Name : "name"
Participant ||--o| Address : "address"
Participant ||--o| Verification : "verification"
Participant ||--o| SellersCapacity : "sellersCapacity"
Verification ||--o| Identity : "identity"
Verification ||--o| AntiMoneyLaundering : "antiMoneyLaundering"
AntiMoneyLaundering ||--o{ Report : "reports"
Identity ||--o{ Report : "reports"
Transaction {
object externalIds "externalIds"
string status "status"
string transactionId "UUID for the transaction"
}
Participant {
string dateOfBirth "Date of birth"
string email "Email address"
object externalIds "externalIds"
string organisation "Organisation"
string organisationReference "Reference"
string participantStatus "participantStatus"
string phone "Phone number"
string role "role"
}
Address {
string buildingName "Building name"
string buildingNumber "Building number"
string countryCode "Country code"
string homeNation "Home nation"
string line_3 "Address 3"
string line1 "Address 1"
string line2 "Address 2"
string postcode "Postcode"
string street "Street"
string subBuilding "Sub building name"
string town "Town"
}
Name {
string firstName "First name"
string lastName "lastName"
string maidenName "Middle name(s)"
string middleName "Middle name(s)"
string preferredName "Preferred name / known as"
string title "Title or honorific"
}
SellersCapacity {
string attachments "Attachments"
string capacity "capacity"
string sellersCapacityDetails "Please provide details if applicable"
}
Verification {
}
AntiMoneyLaundering {
string result "result"
}
Report {
string details "details"
string reportName "reportName"
string result "result"
}
Identity {
string result "result"
}
Physical model — every JSON object owned by this page is a node, every scalar field a row. 10 objects, 40 scalar fields. Generated from the schema walk; click any node to jump to its table. Transaction Title Description Type Kind Field Required Overlays Affordance externalIds Data group capturing external id information. objectDeclaration externalIds — — — status Enumeration: active, For sale, Under offer, Sold subject to contract…. stringDeclaration status — — example UUID for the transaction — stringDeclaration transactionId — — example
Participants Title Description Type Kind Field Required Overlays Affordance Date of birth — stringDeclaration dateOfBirth — — — Email address Company Email address stringDeclaration email — — — externalIds — objectDeclaration externalIds — — — Organisation — stringDeclaration organisation — — — Reference — stringDeclaration organisationReference — — — participantStatus Enumeration: Proposed, Invited, Active, Removed. stringDeclaration participantStatus — — — Phone number — stringDeclaration phone — — — role A role is a collection of permissions that determines what a user can do within a system. stringDeclaration role — Buyers & Sellers Property Information v5 (BASPI5)
Property Information Questionnaire (PIQ)
— role A role is a collection of permissions that determines what a user can do within a system. stringDeclaration role — Buyers & Sellers Property Information v5 (BASPI5)
Property Information Questionnaire (PIQ)
—
Title Description Type Kind Field Required Overlays Affordance Building name — stringDeclaration buildingName — — — Building number — stringDeclaration buildingNumber — — — Country code — stringDeclaration countryCode — — — Home nation — stringDeclaration homeNation — — — Address 3 — stringDeclaration line 3 — — — Address 1 — stringDeclaration line1 — — — Address 2 — stringDeclaration line2 — — — Postcode — stringDeclaration postcode — — — Street — stringDeclaration street — — — Sub building name — stringDeclaration subBuilding — — — Town — stringDeclaration town — — —
Title Description Type Kind Field Required Overlays Affordance First name — stringDeclaration firstName — — — lastName — stringDeclaration lastName — — — Middle name(s) — stringDeclaration maidenName — — — Middle name(s) — stringDeclaration middleName — — — Preferred name / known as Preferred name / known as stringDeclaration preferredName — — — Title or honorific Enumeration: Mr, Mrs, Miss, Ms…. stringDeclaration title — — —
Title Description Type Kind Field Required Overlays Affordance Attachments Please attach evidence in support of the above stringDeclaration attachments — Buyers & Sellers Property Information v5 (BASPI5)
— capacity Please tick as applicable below, to confirm the capacity in which the answer are given. stringDeclaration capacity — Buyers & Sellers Property Information v5 (BASPI5)
Property Information Questionnaire (PIQ)
Residential Disclosure Standard (RDS)
— Please provide details if applicable (for example if the seller name do not match the legal owner on the title deed due to change of name on marriage). Please provide detail if applicable stringDeclaration sellersCapacityDetails — Buyers & Sellers Property Information v5 (BASPI5)
Residential Disclosure Standard (RDS)
—
No scalar fields on this object — pure container.
Title Description Type Kind Field Required Overlays Affordance result — stringDeclaration result — — —
Title Description Type Kind Field Required Overlays Affordance result Enumeration: pass, fail, consider. stringDeclaration result — — —
Title Description Type Kind Field Required Overlays Affordance details — stringDeclaration details — — — reportName — stringDeclaration reportName — — — result — stringDeclaration result — — —
Title Description Type Kind Field Required Overlays Affordance details — stringDeclaration details — — — reportName — stringDeclaration reportName — — — result — stringDeclaration result — — —
Gap notes
Capacity is a string enum, not a graph of authorities. An executor's grant of probate, an attorney's power of attorney, a mortgagee's repossession order — all collapse to a single sellersCapacity value, with attachments. A future revision should split asserted-capacity from evidenced-authority.
Comments