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

    Class claim context

    Evidence

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

    A role a bearer plays when a verification activity draws on it to support a claim, whose acquisition kind (Document, Electronic-Record or Vouch) is stated by a coded evidence-type value rather than by subclassing.

    Evidence supporting a Claim. UFO RoleMixin (anti-rigid, cross-categorial — a bearer is evidence only qua a VerificationActivity using it; ODR-0006 Seller/Buyer pattern); PROV-O Entity. Evidence KIND is a coded isMemberOf classification — opda:evidenceType over opda:EvidenceMethodScheme (the OIDC4IDA evidence.type value-space: Document / Electronic-Record / Vouch) — NOT a subclass tree (ODR-0027 §R6; the former …Evidence subclasses are retired, since 'evidence is a role a document plays' and a Role is never rdfs:subClassOf a Kind). The three kinds are NOT collapsed (S009 R5): they remain distinct scheme concepts. Kind-specific attributes (opda:attestedBy for vouches; document/record specifics) are facets borne by the role; per-kind obligations are validated VALUE-KEYED by opda:EvidenceFacetShape (sh:targetSubjectsOf opda:evidenceType + sh:or material implication; ADR-0012).

    Classification

    Classified under UFO meta-category RoleMixin — a design-time classification (UFO-informed, not UFO-grounded), not an entailed type

    PROV-O: Entity (W3C PROV-O REC §3.2). The three evidence kinds (Document / Electronic-Record / Vouch) are OIDC4IDA / eIDAS evidence.type concepts in opda:EvidenceMethodScheme (S009 Rule 5), carried as the coded opda:evidenceType value (ODR-0027 §R6).

    Outgoing connections · 2

    PredicateTargetInverse
    attestedBy Agent —
    evidenceType Concept —

    Incoming connections · 1

    Object properties whose range is this class — what points at it.

    PredicateFrom (domain)Inverse
    supportedBy Claim —

    Governing SHACL shapes · 1

    SKOS schemes used · 1

    Used in the RML mapping · 6

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

    Provenance · dct:source

    • harness/odr/ODR-0009/section-Q1