OPDA Knowledge base

Logical tier

Typed entity-relationship view — attributes, cardinalities, relationships, and SKOS enumerations.

Audience: Data engineers, system architects

OPDA Logical Model

This tier shows the entity-relationship structure of OPDA’s ontology in platform-independent form. Audience: data engineers, solution architects, integration architects, technical product managers. The reader is expected to be comfortable with entity-relationship modelling but should not need to read RDF, SHACL, or SKOS Turtle.

OPDA’s Logical-tier inventory: 41 entities (including three short-name aliases under owl:equivalentClass) across seven modules + 23 enumeration schemes.

See also: Modelling section

The Data dictionary page in the Modelling section is the complementary schema-level register: 1,538 PDTF schema-derived data elements (broad, schema-level, with suggested RDF URIs) sourced from the 16 canonical overlays and OPDA Glossary spreadsheets. This tier is the refined ontology reference (41 entities, deep, generator-emitted); the data dictionary is the raw schema material it grew from.

Reading order

  1. This tier overview — module catalogue, entity index, master ER diagram (below)
  2. The seven module directories (in IC-dependency order):
    • foundation/ — six foundation classes (UFO meta-classes, ValidationContext, generator provenance)
    • property/ — Property + Address + LegalEstate + RegisteredTitle + LeaseTerm + lifecycle events
    • agent/ — Person + Organisation + Roles + Relators
    • transaction/ — Transaction Relator + Milestone + TransactionChain
    • claim/ — Claim + Evidence subtypes + VerificationActivity
    • governance/ — DPV mapping records + special-category data
    • descriptive/ — Survey + Valuation + EPC + Search + Comparable
  3. Per-module enumerations/ subdirectories — typed value sets (SKOS schemes) bound by each module’s attributes.

What’s in each entity file

Every entity follows the same nine-section shape:

  1. Summary — one paragraph; UFO meta-category in brackets; back-link to Concept tier
  2. Attributes — typed table with cardinality + identity-bearing flags
  3. Relationships — typed table with cardinality + inverse predicate
  4. Identity key — typed shape of the Identity Criterion
  5. Constraints — non-cardinality business rules with SHACL severity tier
  6. Derived attributes — attributes computed from SHACL-AF rules
  7. ER diagram — Mermaid erDiagram of the entity + direct neighbours
  8. Source ODR + ADR — link targets only (no quoted text)

Module catalogue

ModuleEntitiesSchemes usedDescription
foundation6—UFO meta-classes (Role, RoleMixin, Relator); ValidationContext; generator provenance (GeneratorRun); diagnostic exemplars
property715Physical Property + Address + LegalEstate + RegisteredTitle + LeaseTerm + lifecycle events
agent74Person + Organisation as substances; Buyer/Seller/Proprietor as Roles; Proprietorship Relator
transaction32Transaction Relator; lifecycle Milestones; TransactionChain aggregate
claim112Verifiable Claims + Evidence subtypes + VerificationActivity + AssuranceLevel + TrustFramework
governance2—DPV mapping records (PII baseline + variants); special-category data scheme
descriptive5—Class-promoted descriptive Kinds: Survey, Valuation, EPC, Search, Comparable

Entity index (alphabetical)

EntityModuleUFO meta-category
AddresspropertySubstance Kind
AssuranceLevelclaimQuale-in-Region
BuyeragentRoleMixin
ClaimclaimInformation particular
ComparabledescriptiveSubstance Kind (informational)
DiagnosticExemplarfoundationSubstance Kind (informational)
DocumentclaimSubstance Kind (informational; alias)
DocumentEvidenceclaimSubstance Kind (informational)
DPVMappingRecordgovernanceInformation particular
ElectronicRecordclaimSubstance Kind (informational; alias)
ElectronicRecordEvidenceclaimSubstance Kind (informational)
EPCCertificatedescriptiveSubstance Kind (informational)
EvidenceclaimSubstance Kind (informational)
GeneratorRunfoundationInformation particular
LeaseExtensionEventpropertyEvent particular
LeaseTermpropertyInformation particular
LegalEstatepropertySubstance Kind
MilestonetransactionEvent particular
NameChangeEventagentEvent particular
OrganisationagentSubstance Kind
PersonagentSubstance Kind
PropertypropertySubstance Kind
ProprietoragentRole
ProprietorshipagentRelator
RegisteredTitlepropertySubstance Kind (informational)
RelatorfoundationMeta-class (UFO Relator)
RolefoundationMeta-class (UFO Role)
RoleMixinfoundationMeta-class (UFO RoleMixin)
SearchdescriptiveSubstance Kind (informational)
SelleragentRoleMixin
SpecialCategorySchemegovernanceInformation particular (declaration only)
SurveydescriptiveSubstance Kind (informational)
TransactiontransactionRelator
TransactionChaintransactionAggregate
TrustFrameworkclaimInformation particular
UPRNSuccessionEventpropertyEvent particular
ValuationdescriptiveSubstance Kind (informational)
ValidationContextfoundationSubstance Kind (informational)
VerificationActivityclaimEvent particular
VouchclaimSubstance Kind (informational; alias)
VouchEvidenceclaimSubstance Kind (informational)

Master ER diagram

The diagram below shows the cross-module relationships at a glance. Per-module ER diagrams (showing within-module detail) live in the module READMEs and in diagrams/.

%%{init: {"theme": "base", "themeVariables": {"primaryColor": "#E1BEE7", "primaryTextColor": "#4A148C", "primaryBorderColor": "#6A1B9A", "lineColor": "#37474F", "secondaryColor": "#B3E5FC", "tertiaryColor": "#FFF8E1"}}}%% erDiagram accTitle: OPDA Logical Model — Master Entity-Relationship Diagram accDescr: Cross-module ER diagram showing all 41 entities across 7 modules (foundation, property, agent, transaction, claim, governance, descriptive) and their inter-module relationships. Property ||--o{ Address : "hasAddress" RegisteredTitle ||--|| LegalEstate : "recordsEstate" RegisteredTitle }o--|| Property : "identifiesSameProperty" LegalEstate }o--|| Property : "identifiesSameProperty" LegalEstate ||--o| LeaseTerm : "leaseTerm" LeaseExtensionEvent }o--|| LegalEstate : "extends" UPRNSuccessionEvent }o--|| Property : "succeeds" Transaction }o--o{ LegalEstate : "concerns" Transaction ||--o{ Seller : "founds" Transaction ||--o{ Buyer : "founds" Transaction ||--o{ Milestone : "hasMilestone" Transaction }o--o| TransactionChain : "hasChainPosition" Seller }o--|| Person : "borneBy" Seller }o--|| Organisation : "borneBy" Buyer }o--|| Person : "borneBy" Buyer }o--|| Organisation : "borneBy" Proprietorship }o--|| RegisteredTitle : "bindsTitle" Proprietorship ||--o{ Proprietor : "founds" Proprietor }o--|| Person : "borneBy" NameChangeEvent }o--|| Person : "associatedWith" Seller ||--o{ Claim : "hasEvidencedAuthority" Claim }o--o{ Evidence : "supportedBy" Evidence ||--o| DocumentEvidence : "subtype" Evidence ||--o| ElectronicRecordEvidence : "subtype" Evidence ||--o| VouchEvidence : "subtype" VerificationActivity }o--|| Claim : "produces" VerificationActivity }o--o| TrustFramework : "conformsTo" Claim }o--o{ AssuranceLevel : "assuranceLevel" VouchEvidence }o--|| Person : "attestedBy" DPVMappingRecord }o--|| Person : "targetsKind" DPVMappingRecord }o--|| Organisation : "targetsKind" DPVMappingRecord }o--|| Claim : "targetsKind" Survey }o--|| Property : "concerns" Valuation }o--|| Property : "concerns" EPCCertificate }o--|| Property : "concerns" Search }o--|| Property : "concerns" Comparable }o--|| Valuation : "supports"

Source file: diagrams/master-er.mmd.

Module dependency diagram

Module dependencies in IC-dependency order. Edges indicate that the source module declares entities or predicates whose domain or range resolves to an entity in the target module.

--- config: layout: elk --- %%{init: {"theme": "base", "themeVariables": {"primaryColor": "#E1BEE7", "primaryTextColor": "#4A148C", "primaryBorderColor": "#6A1B9A", "lineColor": "#37474F"}}}%% flowchart LR accTitle: OPDA Module Dependency Diagram accDescr: Inter-module dependency edges across the seven Logical-tier modules in IC-dependency order — foundation is the root; descriptive and governance are the leaves. classDef foundationMod fill:#E1BEE7,stroke:#6A1B9A,stroke-width:2px,color:#4A148C classDef propertyMod fill:#B3E5FC,stroke:#0277BD,stroke-width:2px,color:#01579B classDef agentMod fill:#F3E5F5,stroke:#7B1FA2,stroke-width:2px,color:#4A148C classDef transactionMod fill:#E8F5E9,stroke:#2E7D32,stroke-width:2px,color:#1B5E20 classDef claimMod fill:#FFF8E1,stroke:#F57F17,stroke-width:2px,color:#E65100 classDef governanceMod fill:#E0F2F1,stroke:#00695C,stroke-width:2px,color:#004D40 classDef descriptiveMod fill:#ECEFF1,stroke:#455A64,stroke-width:2px,color:#263238 Foundation["foundation
Role / RoleMixin / Relator
ValidationContext / GeneratorRun"]:::foundationMod Property["property
Property / Address / LegalEstate
RegisteredTitle / LeaseTerm + events"]:::propertyMod Agent["agent
Person / Organisation
Buyer / Seller / Proprietor / Proprietorship"]:::agentMod Transaction["transaction
Transaction Relator
Milestone / TransactionChain"]:::transactionMod Claim["claim
Claim / Evidence subtypes
VerificationActivity / TrustFramework"]:::claimMod Governance["governance
DPVMappingRecord
SpecialCategoryScheme"]:::governanceMod Descriptive["descriptive
Survey / Valuation / EPC
Search / Comparable"]:::descriptiveMod Property -->|"specialises meta-classes"| Foundation Agent -->|"specialises meta-classes"| Foundation Transaction -->|"specialises Relator"| Foundation Claim -->|"PROV-O Entities"| Foundation Governance -->|"declaration patterns"| Foundation Descriptive -->|"PROV-O Entities"| Foundation Agent -->|"Proprietorship binds RegisteredTitle
(cross-module Relator)"| Property Transaction -->|"concerns LegalEstate"| Property Transaction -->|"founds Seller and Buyer"| Agent Claim -->|"Seller hasEvidencedAuthority
VouchEvidence attestedBy Person"| Agent Governance -->|"DPVMappingRecord targetsKind"| Agent Governance -->|"DPVMappingRecord targetsKind"| Claim Descriptive -->|"concerns Property"| Property

Identity-key index

Each entity is named alongside its Identity Criterion key. Use this as a navigation aid when designing payload shapes or evaluating cross-tier mappings.

--- config: layout: elk --- %%{init: {"theme": "base", "themeVariables": {"primaryColor": "#E1BEE7", "primaryTextColor": "#4A148C", "primaryBorderColor": "#6A1B9A", "lineColor": "#37474F"}}}%% flowchart LR accTitle: OPDA Identity-Key Index accDescr: Flowchart grouping every OPDA Logical-tier entity by its Identity Criterion key surface — spatial-material, identifier-bundle, PROV-O tuple, digest, or parasitic role-identity. classDef icKey fill:#F8BBD9,stroke:#AD1457,stroke-width:2px,color:#880E4F classDef entity fill:#B3E5FC,stroke:#0277BD,stroke-width:2px,color:#01579B classDef parasitic fill:#FFF8E1,stroke:#F57F17,stroke-width:2px,color:#E65100 classDef metaEntity fill:#E1BEE7,stroke:#6A1B9A,stroke-width:2px,color:#4A148C SpatialMaterial[Spatial-material
continuity]:::icKey AuthorityRecord[Authority-record
variant + record-id]:::icKey RightsBundle[Rights-bundle
persistence]:::icKey TitleLineage[Title-number lineage
+ registry-event history]:::icKey OWLTime[OWL-Time interval
+ LegalEstate]:::icKey ProvTuple[PROV-O tuple
entity + timestamp]:::icKey IdentifierBundle[Identifier bundle
FIBO multi-id]:::icKey Tuple[Relator tuple
bearers + founding event]:::icKey Digest[Cryptographic digest
content-addressable]:::icKey SchemeMember[Scheme-member
notation]:::icKey URI[Dereferenceable URI]:::icKey ProvActivity[Provenance Activity
prov:wasGeneratedBy]:::icKey TargetTuple[targetsKind
+ baselineCategory]:::icKey GenRun[generatorVersion
+ sourceCommit]:::icKey Parasitic["Parasitic on bearer
+ Relator (no IC)"]:::icKey Property[Property]:::entity --> SpatialMaterial Address[Address]:::entity --> AuthorityRecord LegalEstate[LegalEstate]:::entity --> RightsBundle RegisteredTitle[RegisteredTitle]:::entity --> TitleLineage LeaseTerm[LeaseTerm]:::entity --> OWLTime LeaseExtensionEvent[LeaseExtensionEvent]:::entity --> ProvTuple UPRNSuccessionEvent[UPRNSuccessionEvent]:::entity --> ProvTuple NameChangeEvent[NameChangeEvent]:::entity --> ProvTuple Person[Person]:::entity --> IdentifierBundle Organisation[Organisation]:::entity --> IdentifierBundle Proprietorship[Proprietorship]:::entity --> Tuple Transaction[Transaction]:::entity --> Tuple Milestone[Milestone]:::entity --> Tuple TransactionChain[TransactionChain]:::entity --> Tuple Seller[Seller]:::parasitic --> Parasitic Buyer[Buyer]:::parasitic --> Parasitic Proprietor[Proprietor]:::parasitic --> Parasitic Role[Role]:::metaEntity --> Parasitic RoleMixin[RoleMixin]:::metaEntity --> Parasitic Relator[Relator]:::metaEntity --> Tuple Claim[Claim]:::entity --> Digest Evidence[Evidence]:::entity --> Digest DocumentEvidence[DocumentEvidence]:::entity --> Digest ElectronicRecordEvidence[ElectronicRecordEvidence]:::entity --> Digest VouchEvidence[VouchEvidence]:::entity --> Digest Document[Document]:::entity --> Digest ElectronicRecord[ElectronicRecord]:::entity --> Digest Vouch[Vouch]:::entity --> Digest VerificationActivity[VerificationActivity]:::entity --> ProvTuple AssuranceLevel[AssuranceLevel]:::entity --> SchemeMember TrustFramework[TrustFramework]:::entity --> URI ValidationContext[ValidationContext]:::entity --> URI DPVMappingRecord[DPVMappingRecord]:::entity --> TargetTuple GeneratorRun[GeneratorRun]:::entity --> GenRun Survey[Survey]:::entity --> ProvActivity Valuation[Valuation]:::entity --> ProvActivity EPCCertificate[EPCCertificate]:::entity --> ProvActivity Search[Search]:::entity --> ProvActivity Comparable[Comparable]:::entity --> ProvActivity

UFO category index

Each entity grouped by its UFO meta-category bracket (pulled from the entity’s ## Summary UFO bracket per the IA spec).

--- config: layout: elk --- %%{init: {"theme": "base", "themeVariables": {"primaryColor": "#E1BEE7", "primaryTextColor": "#4A148C", "primaryBorderColor": "#6A1B9A", "lineColor": "#37474F"}}}%% flowchart LR accTitle: OPDA UFO Category Index accDescr: Flowchart grouping the 41 OPDA Logical-tier entities by their UFO meta-category — Substance Kind, Role, RoleMixin, Relator, Event particular, Information particular, Quale-in-Region, Aggregate, Meta-class. classDef ufoCat fill:#E1BEE7,stroke:#6A1B9A,stroke-width:2px,color:#4A148C classDef entity fill:#B3E5FC,stroke:#0277BD,stroke-width:2px,color:#01579B SubKind[Substance Kind]:::ufoCat RoleCat[Role]:::ufoCat RoleMixinCat[RoleMixin]:::ufoCat RelatorCat[Relator]:::ufoCat EventP[Event particular]:::ufoCat InfoP[Information particular]:::ufoCat QualeR[Quale-in-Region]:::ufoCat AggregateCat[Aggregate]:::ufoCat MetaCls[Meta-class]:::ufoCat PropertyE[Property]:::entity --> SubKind AddressE[Address]:::entity --> SubKind LegalEstateE[LegalEstate]:::entity --> SubKind RegisteredTitleE["RegisteredTitle
(informational)"]:::entity --> SubKind PersonE[Person]:::entity --> SubKind OrganisationE[Organisation]:::entity --> SubKind ValidationContextE["ValidationContext
(informational)"]:::entity --> SubKind DiagnosticExemplarE["DiagnosticExemplar
(informational)"]:::entity --> SubKind EvidenceE["Evidence
(informational)"]:::entity --> SubKind DocumentEvidenceE[DocumentEvidence]:::entity --> SubKind ElectronicRecordEvidenceE[ElectronicRecordEvidence]:::entity --> SubKind VouchEvidenceE[VouchEvidence]:::entity --> SubKind DocumentE["Document (alias)"]:::entity --> SubKind ElectronicRecordE["ElectronicRecord (alias)"]:::entity --> SubKind VouchE["Vouch (alias)"]:::entity --> SubKind SurveyE[Survey]:::entity --> SubKind ValuationE[Valuation]:::entity --> SubKind EPCCertificateE[EPCCertificate]:::entity --> SubKind SearchE[Search]:::entity --> SubKind ComparableE[Comparable]:::entity --> SubKind ProprietorE[Proprietor]:::entity --> RoleCat SellerE[Seller]:::entity --> RoleMixinCat BuyerE[Buyer]:::entity --> RoleMixinCat ProprietorshipE[Proprietorship]:::entity --> RelatorCat TransactionE[Transaction]:::entity --> RelatorCat NameChangeEventE[NameChangeEvent]:::entity --> EventP LeaseExtensionEventE[LeaseExtensionEvent]:::entity --> EventP UPRNSuccessionEventE[UPRNSuccessionEvent]:::entity --> EventP MilestoneE[Milestone]:::entity --> EventP VerificationActivityE[VerificationActivity]:::entity --> EventP LeaseTermE[LeaseTerm]:::entity --> InfoP ClaimE[Claim]:::entity --> InfoP TrustFrameworkE[TrustFramework]:::entity --> InfoP GeneratorRunE[GeneratorRun]:::entity --> InfoP DPVMappingRecordE[DPVMappingRecord]:::entity --> InfoP SpecialCategorySchemeE["SpecialCategoryScheme
(declaration only)"]:::entity --> InfoP AssuranceLevelE[AssuranceLevel]:::entity --> QualeR TransactionChainE[TransactionChain]:::entity --> AggregateCat RoleE[Role]:::entity --> MetaCls RoleMixinE[RoleMixin]:::entity --> MetaCls RelatorE[Relator]:::entity --> MetaCls

Cross-tier traceability

Every Logical-tier entity maps 1:1 to:

  • the Concept-tier file at ../concept/<module>/<entity>.md (business-language narrative)
  • one owl:Class URI in the Physical-Ontology tier (TBox specifics)
  • one or more named graphs in the Physical-Database tier (deployment specifics)

The same <module>/<entity>.md path shape is used across all four tiers.

Out of scope at this tier

  • Business prose, hard cases, anti-pattern rationale → Concept tier
  • Named-graph layout, derived profiles, BASPI5 overlay composition → Physical-Database tier
  • OWL / SHACL / SKOS / Turtle syntax → Physical-Ontology tier

Provenance

Generated from the 24 emitted TTLs at source/03-standards/ontology/ per the IA spec at ../../information-architecture/logical-model-ia.md. The ODR corpus is the modelling-decision audit trail and is referenced as link targets only.

Comments

Loading comments…
← DescriptiveFoundation →