Person
https://opda.org.uk/pdtf/Person Natural person. UFO Substance Kind; DOLCE Endurant. IC: FIBO-style multi-identifier persistence (date-of-birth + state-issued ID + name) over name-change, gender-recognition, and death hard cases. Anchors PII regimes (DPV co-annotation lands per ODR-0018 in opda-annotations.ttl; ADR-0012 emits).
Classification
DOLCE: Endurant / Agent (Masolo et al. 2003 D18 §4.1). UFO: Substance Kind (Guizzardi 2005 Ch. 4 §4.2 — Sortal, Rigid).
Attributes
| Attribute | Type | Cardinality | Required | Identity-bearing | Description |
|---|---|---|---|---|---|
currentName | xsd:string | 0..* | N | N | A Person's current surname, asserted alongside opda:formerName when a marriage-style name change is on record (ODR-0006 §Q1). Plain string datatype per ODR-0008 §Q5a; flat per §Q6a. |
dateOfBirth | xsd:date | 0..* | N | N | Date of birth of a Person participant. xsd:date. Flat per §Q6a. Part of the Person multi-identifier IC (ODR-0006 §Q1); PII under ODR-0018 (DPV co-annotation in opda-annotations.ttl). |
formerName | xsd:string | 0..* | N | N | A Person's surname before a marriage-style name change (ODR-0006 §Q1 name-change hard case). Plain string datatype per ODR-0008 §Q5a; flat per §Q6a. Scoped to surname, not a constructed full name (see the ambiguous-domains note above this list). |
middleNames | xsd:string | 0..* | N | N | Middle name(s) of a Person legal owner. Plain string datatype per ODR-0008 §Q5a; flat per §Q6a. |
Relationships
| Predicate | Target | Cardinality | Inverse | Description |
|---|---|---|---|---|
hasAddress | Address | 0..* | — | Canonical bearer → Address join predicate. Per ODR-0005 §6b pre-commitment and ODR-0015 §3a, opda:hasAddress is uniform across variants — one bearer may hasAddress multiple Address instances differing on opda:addressVariant (title / marketing / inspire). Per Council session-047 Q6 the predicate is bearer-extended to Person/Organisation. Documentary "any-of" domain (ODR-0032 §R2 session-050 amendment): rdfs:domain opda:Property , opda:Person , opda:Organisation — three triples read DISJUNCTIVELY per the module-header convention, NOT the RDFS §3.2 conjunction; authored as AI-signal, NEVER entailed (zero domain/range triples materialise, ADR-0035 — so the domain does NOT entail every addressed Person is a Property). The authoritative bearer disjunction lives in SHACL sh:or (opda:HasAddressBearerShape), NOT owl:unionOf. rdfs:range opda:Address kept (single co-domain); the Address class/IC stays ODR-0015-pending (Mode-vs-Resource open). |
hasAssertedCapacity | Concept | 0..* | — | Seller-side asserted capacity per opda:SellersCapacityScheme (SKOS in opda-vocabularies.ttl). Sales-context seam in the two-predicate Capacity/Authority split per S006 Q4 (Evans + Vernon load-bearing). The assertion lives on the Sales side; the evidence link lives on the Conveyancing side via opda:hasEvidencedAuthority. |
plays | RoleMixin | 0..* | playedBy | Bearer → Role inverse of opda:playedBy: the Role a Person or Organisation plays. Documentary "any-of" domain/range (the mirror of opda:playedBy; ODR-0032 §R2 session-050 amendment): rdfs:domain opda:Person , opda:Organisation (the bearer subject) and rdfs:range opda:Role , opda:RoleMixin (the role object), each MULTIPLE triples read DISJUNCTIVELY per the module-header convention, NOT the RDFS §3.2 conjunction. Authored as AI-signal, NEVER entailed (zero domain/range triples materialise, ADR-0035 — so the domain does NOT entail every bearer is a Person). The authoritative subject/object disjunctions are carried by the opda:playedBy SHACL shapes (the inverse direction shares the same closed-world constraints); owl:unionOf is NOT used. Emitted as the navigable inverse so consumers query from either end without inverse-property inference (ODR-0029/0030 — UFO layer inert at load). |
Constraints
PersonIdentityKeyShape
sh:Violation Person identity-key surface: hasAssertedCapacity MUST be a single concept IRI when present. The full Person IC per ODR-0006 §Q1 is borne by the identifier-bundle (NI number / passport / driving-licence); succession is tracked by the IdentifierSuccessionRule SHACL-AF rule below.
Sources
harness/odr/ODR-0006/section-Q1
Comments
Loading comments…
Sign in to post a comment