Open Property Data Association
Smart Property Data Trust Framework
Become a member Join a working group
    Concept tier foundation

    Role Mixin

    https://opda.org.uk/pdtf/RoleMixin

    UFO RoleMixin — anti-rigid, cross-sortal role pattern. An instance of a RoleMixin is borne by a bearer drawn from more than one substantial Kind (e.g. Seller may be borne by Person OR Organisation). Distinguished from `opda:Role` (which is sortal — borne by a single Kind). Per ODR-0006 §Q2 Role layer.

    Classification

    UFO: RoleMixin (Guizzardi 2005 Ch. 4 §4.4 — anti-rigid, externally founded, cross-sortal). DOLCE: Role qua Universal without sortal commitment (Masolo et al. 2003 D18 §4.5).

    Relationships

    Predicate Target Cardinality Inverse Description
    playedBy Organisation 0..* plays Role → bearer navigable edge: the Person or Organisation that plays this Role qua-individual. Documentary "any-of" domain/range (ODR-0032 §R2 session-050 amendment; schema.org domainIncludes idiom): rdfs:domain opda:Role , opda:RoleMixin (the subject is an opda:Role — Proprietor — OR an opda:RoleMixin — Seller/Buyer — sibling role meta-classes) and rdfs:range opda:Person , opda:Organisation (the bearer), 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 range does NOT entail every bearer is a Person). The authoritative disjunctions live in SHACL sh:or (subject: opda:RolePlaySubjectShape; bearer: opda:RolePlayShape / opda:SellerShape / opda:BuyerShape), NOT owl:unionOf (excluded construct). OPTIONAL / distinct-node-only per Council session-047 Q4: emitted only where the role qua-individual is a node distinct from its bearer; never a self-edge. Coexists with role co-typing (ODR-0006 §Q2) — the typed encoding is the canonical IC, this is the navigable link for the distinct-node case (a qua-individual, prov:Agent-attested participant). Inverse: opda:plays.
    roleNotation Concept 0..* — Notation value naming the transactional role borne by a Seller / Buyer / Proprietor / Conveyancer / etc. Constrained by per-overlay profile shapes via SHACL `sh:in` over the SKOS RoleScheme members. Per ODR-0006 §Q2 the role-bearing pattern is encoded by `opda:Seller` / `opda:Buyer` / `opda:Proprietor` sub-classes of `opda:RoleMixin`; this predicate exposes the notation for DASH editor ergonomics and SPARQL convenience. Renamed from opda:role (ADR-0044) to avoid the case-clash with the opda:Role class.

    Sources

    • harness/odr/ODR-0006/section-Q2

    Comments

    Loading comments…