Logical tier transaction

Milestone

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

Transaction lifecycle milestone. UFO Event particular; PROV-O Activity. Hybrid PROV-O typing per S007 Q2: instant milestones (instruction, offerAccepted, exchange) carry prov:atTime; interval milestones (completion-process, registration-process) carry prov:startedAtTime + prov:endedAtTime per Moreau W3C-grade discipline. Each Milestone Activity may pair with a prov:Plan carrying opda:plannedAtTime for expected-vs-actual variance (S007 Q6 Plan-vs-Activity reification).

Classification

UFO: Event particular (Guizzardi 2005 Ch. 4 §4.7). DOLCE: Achievement (instant) or Accomplishment (interval) per Masolo et al. 2003 D18 §4.4. PROV-O: Activity (W3C PROV-O REC §3.2).

Relationships

Predicate	Target	Cardinality	Inverse	Description
`partOfTransaction`	`Transaction`	0..*	—	Milestone → Transaction join: the perdurant milestone is a part of the Transaction-event (event-mereology; Guizzardi ER 2013 §4). GATED 7–0 by Council session-051 (ODR-0034 §R1) — declared to govern the predicate the diagnostic exemplars already use (ADR-0048 §As-built "left as-is"). Single-domain edge, no never-reasoned commitment: rdfs:domain opda:Milestone + rdfs:range opda:Transaction both asserted as documentary AI-signal, NEVER entailed (ADR-0035). PROV-O carries no part-of-activity relation (PROV-DM §5.3), so this is a bespoke partonomic predicate, not a prov: reuse.

Constraints

MilestoneIdentityKeyShape sh:Violation

Milestone plannedAtTime MUST be a single xsd:dateTime value when present. The variance against occurredAtTime is tracked by the MilestoneVarianceRule SHACL-AF rule below.

Sources

harness/odr/ODR-0007/section-Q2