Organisation
https://opda.org.uk/pdtf/Organisation No DPV class-level PII baseline for opda:Organisation per ODR-0006 §Q6 + ODR-0018 §Rule 4. Organisations are not data subjects; the sole-trader / individual-director surface produces an opda:Person co-annotation (linked via the actor's ownership / control relationship), not an Organisation co-annotation.
Classification
DOLCE: NonPhysicalEndurant (Masolo et al. 2003 D18 §4.2). UFO: Substance Kind (Guizzardi 2005 Ch. 4 §4.2). W3C Org Ontology alignment per S006 Q6 9-1 verdict (Allemang held-as-live).
Attributes
| Attribute | Type | Cardinality | Required | Identity-bearing | Description |
|---|---|---|---|---|---|
accountName | xsd:string | 0..* | N | N | Name on the bank account of a leasehold / managed-freehold contact organisation (landlord / managing agent / management company / rentcharge owner / resident-tenants' association). ONE shared property reused across those contact blocks. Plain string datatype per ODR-0008 §Q5a; flat per §Q6a. (FLAG: bank-details domain — placed on opda:Organisation, no opda:BankAccount Kind minted.) |
accountNumber | xsd:string | 0..* | N | N | Bank-account number of a contact organisation. xsd:string (a fixed-width numeric identifier — leading zeros significant, per the opda:hasUPRN convention, NOT xsd:integer). ONE shared property; flat per §Q6a. (FLAG: bank-details domain.) |
organisationName | xsd:string | 0..* | N | N | Name of an Organisation — a legal owner's registered/trading name, or the organisation a participant is acting for / belongs to. ONE shared property: the same opda:organisationName serves both leaves (Linked-Data shared-property pattern; supersedes the former opda:organisation, renamed-by-merge per ADR-0044 to remove the case-clash with the opda:Organisation class). Plain string datatype per ODR-0008 §Q5a; flat per §Q6a. |
organisationReference | xsd:string | 0..* | N | N | Reference identifying an Organisation participant within an external system. Plain string datatype per ODR-0008 §Q5a; flat per §Q6a. |
reference | xsd:string | 0..* | N | N | Payment reference for a contact organisation's bank account. Plain string datatype per ODR-0008 §Q5a; flat per §Q6a. (FLAG: bank-details domain.) |
sortCode | xsd:string | 0..* | N | N | Bank sort code of a contact organisation. xsd:string. ONE shared property; flat per §Q6a. (FLAG: bank-details domain.) |
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
OrganisationIdentityKeyShape
sh:Violation Organisation identity-key surface: hasAssertedCapacity MUST be a single concept IRI when present. Full IC per ODR-0006 §Q6 borne by the registration-record (LEI / Companies House number); subclass relationship to org:Organization preserves cross-vocabulary identity.
Sources
harness/odr/ODR-0006/section-Q6
Comments
Loading comments…
Sign in to post a comment