Data dictionary & business glossary

Programmatically extracted from PDTF Schemas v3 (the base transaction + 18 main overlays — extension overlays not yet included) and merged with the two OPDA Glossary spreadsheets. The first deliverable of the semantic-modelling workstream.

Browse all properties

All 8,458 property-path entries from the canonical schemas. Search by name or path, filter by bounded context, source schema, or JSON type. Click any column header to sort.

Tip: try tenure, EPC or address in the search box; or pin a single overlay (e.g. ta6) with the source filter to see exactly what it adds.

Deliverables

All files generated to source/00-deliverables/semantic-models/.

Canonical schema inventory

Excluded as redundant: combined.json (derived merge), skeleton.json (template), baspi4.json (superseded by baspi5), nts.json (superseded by nts2), ntsl.json (superseded by ntsl2).

How it was built

Source citations

Every entry in data-dictionary.json carries the source field naming the schema file it was extracted from. Every entry in glossary-merged.json carries a sources array naming which of the two Glossary.xlsx files contributed.

The primary sources, with paths:

• source/03-standards/schemas/src/schemas/v3/pdtf-transaction.json (base transaction schema)
• source/03-standards/schemas/src/schemas/v3/combined.json (base + overlays merged)
• source/03-standards/schemas/src/schemas/v3/skeleton.json (skeleton for new transactions)
• source/03-standards/schemas/src/schemas/v3/overlays/*.json (BASPI v4 + v5, TA6, TA7, TA10, NTS, NTS2, NTSL, NTSL2, CON29R, CON29DW, PIQ, RDS, OC1, LLC1, LPE1, FME1, sr24)
• source/06-research/trust-framework-poc/Glossary.xlsx
• source/04-governance-bodies/working-groups/technical/Glossary.xlsx
• External: W3C VCDM 2.0, W3C DID 1.0, Trust Over IP Foundation

Schema coverage

The 21 v3 root-level + main-overlay JSON files the extractor reads, and the bounded context each one serves. (The 16 NTS2 extension overlays under overlays/extensions/ are documented separately on the PDTF overlays page and not yet processed by this generator.)

The 313 cross-context concepts

313 property names appear in three or more overlays — these are the cross-context vocabulary that needs explicit reconciliation in the ontology (same word, possibly different meanings in different contexts). Top examples (sorted by spread):

address, name, date, amount, type, description, reference, status, provider, title, property, id, required, code, category …

Full list with which overlays contain each: see the "Cross-context concepts" section of source/00-deliverables/semantic-models/business-glossary.md.

What to do with these deliverables

1. Have an editorial pass over business-glossary.md with the Technical Working Group — reconcile the OPDA Glossary terms (which are open-banking/trust-framework-flavoured) with the property-data terms extracted from the schemas. The mix today is asymmetric.
2. Define the upper ontology — pick the core classes (Transaction, Property, Participant, Claim, Document, Form, Search) and align with W3C VC. Use business-glossary.ttl as the seed.
3. Per-overlay JSON-LD contexts — for each of the 18 main overlays (and eventually the 16 extension overlays), author a @context that maps the JSON property names to ontology terms. Start with baspi5.json as the worked example.
4. Generate SHACL shapes from the JSON Schema validation rules. Most rules (required, enum, pattern, type) translate mechanically.
5. Disambiguate the 313 cross-context names — for each, decide whether they refer to the same concept (single ontology class) or to context-specific concepts (separate classes with mapping).