Object property property context

    has address

    https://opda.org.uk/pdtf/hasAddressTurtle ↓

    Relates an address-bearing entity (a Property, Person, or Organisation) to an Address that locates it, uniformly across address variants so that one bearer may hold several Addresses differing on their variant.

    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).

    Domain & range

    Subjects (domain)
    Organisation, Person, Property
    Objects (range)
    Address

    Used in the RML mapping · 2

    TriplesMap(s) that populate this property (ADR-0060 — the RML mapping's own bidirectional trace to the PDTF JSON Schema).

    Provenance · dct:source

    • harness/odr/ODR-0015/section-3a