Conformance & certification scheme
How members prove they meet the standard. Borrows the Open Banking pattern: technical conformance tests, annual re-certification, formal scheme owner separate from regulators.
Status
This is a stub for upcoming work. The structure below is what we plan to populate; existing artefacts in source/ that feed it are cited inline.
What already exists
- OPDA Accreditation Scheme document —
source/01-organisation/accreditation/Open Property Data Association (OPDA) Accreditation Scheme.docx - OPDA Technical Certification (7 of 13 founder firms hold it): Kotini, Groundsure, Inventory Base, PEXA, LMS, Sprift, United Trust Bank — per OPDA member firms.
- Accreditation Policy —
source/01-organisation/accreditation/Accreditation Policy - OPDA.docx - Non-Compliant Member Policy —
source/01-organisation/accreditation/Non-Compliant Member Policy - OPDA.docx
Proposed structure
- Scope — what's being conformed against (which PDTF version, which overlays, which API spec)
- Levels — minimum / extended / role-specific (issuer / verifier / holder / orchestrator)
- Test suites — schema validation, API conformance, VC issuance, DID resolution
- Self-assessment — questionnaire + evidence
- Independent audit — when required, who can perform it
- Annual re-certification — cadence, fees, evidence refresh
- Trust Registry entry — outcome: a public, machine-readable record
- Suspension & revocation — when and how
Open Banking parallel
Raidiam — the Sandbox delivery partner — operated UK Open Banking's conformance infrastructure. Worth lifting the working patterns wholesale: FAPI conformance tests, the OBL certification process, directory-based participant registry. See ToIP governance — Open Banking parallel.