← Catalogue
World Models · legacy example

Occurrence / Event

This meta-model is the generic backbone for recording that something happened in the world: what occurred, when, where, who took part, on what evidence, and how one happening relates causally to another. It is its own model so that every timeline in the catalogue shares one shape: specialized event models such as incidents (X3) and interactions (X5) extend it rather than reinventing time, place, participation and causality.

AI YAMLAGENTS.mdSource
IDworld.x1-occurrence-event
Version history0.2.0-legacy
CategoryReference example
IndustryCross-industry
Domainevents-phenomena
Tagsoccurrence, event
Data structure

Bundles and layers

Bundle

happening

The occurrence itself in time and space

Layers

occurrenceCore`: kind, summary, certainty and recording basis · `temporality`: instants, intervals and fuzzy periods · `spatiality`: where it happened, at any granularity

Bundle

involvement

Who or what took part

Layers

participants`: parties and objects involved · `roles`: the capacity in which each participant acted

Bundle

explanation

How happenings connect and compose

Layers

causality`: asserted cause and contribution links · `aggregation`: episodes grouping related occurrences

Findings

Catalogue-native findings must describe the information grouped by each layer. This legacy version does not declare them separately.

Questions & artifacts

Questions, artifact requirements and serial naming rules are required by Vercy vNext; they remain unassigned in this reference version.

Service layers

How this specification operates

Dimension & namespace

  • EXTEND (as base): `world.incidentEmergency` (X3) and `world.encounterInteraction` (X5) EXTEND this model with response and mutuality semantics respectively
  • REFERENCE `world.observedPhenomenon` (X2): recurring patterns are instantiated by individual occurrences recorded here
  • REFERENCE `world.situationCondition` (X4): occurrences open, advance and close situations
  • REFERENCE `world.addressLocationReferencing` (U7): place specifications resolve to addresses, geocodes and POIs
  • REFERENCE `world.person` (H1): human participants in participation records
  • REFERENCE `world.organization` (O1): organizational participants
  • REFERENCE `world.auditTrail` (S4): record-keeping actions over occurrences are audited there
  • imports: mu-event (ALIGN: interoperable event vocabulary)
  • imports: owl-time (COMPOSE: temporal instant and interval value types)
  • imports: schema-org (ALIGN: Event typing for public chronicles)

Canon, patches & standards

  • EXTEND (as base): `world.incidentEmergency` (X3) and `world.encounterInteraction` (X5) EXTEND this model with response and mutuality semantics respectively
  • REFERENCE `world.observedPhenomenon` (X2): recurring patterns are instantiated by individual occurrences recorded here
  • REFERENCE `world.situationCondition` (X4): occurrences open, advance and close situations
  • REFERENCE `world.addressLocationReferencing` (U7): place specifications resolve to addresses, geocodes and POIs
  • REFERENCE `world.person` (H1): human participants in participation records
  • REFERENCE `world.organization` (O1): organizational participants
  • REFERENCE `world.auditTrail` (S4): record-keeping actions over occurrences are audited there
  • imports: mu-event (ALIGN: interoperable event vocabulary)
  • imports: owl-time (COMPOSE: temporal instant and interval value types)
  • imports: schema-org (ALIGN: Event typing for public chronicles)

Artifact formats & serial data

Format-independent core. Concrete artifact formats and naming prefixes are not declared in this legacy version.

Policies & accepted processes

  • `timelineAccessGrant`: a participant grants access to occurrences they took part in, per S2
  • `corroborationExchange`: registrars exchange source records to raise or resolve certainty
  • `openChronicleLicense`: public occurrences released as an open chronicle

Read / add / edit / delete

CRUD procedures and interface bindings are not declared in this legacy version.

Ownership, roles & access

The owner archetype is the primary actor of the occurrence, or the observing registrar when no actor records it. Each participant controls disclosure of their own participation through S2 grants, and the steward's record-keeping is itself auditable via S4.

Existing assembly

Objects, relationships, events and projections

Objects

  • `occurrence`: a discrete thing that happened; key attributes: occurrenceKind, summary, certainty, recordedAt
  • `participation`: one party's involvement in an occurrence; key attributes: partyRef, role, presence
  • `timeSpecification`: when it happened, as an instant, interval or fuzzy period; key attributes: begin, end, precision
  • `placeSpecification`: where it happened, as an address, geocode, feature or region reference; key attributes: placeRef, granularity
  • `causalLink`: an asserted cause or contribution between occurrences; key attributes: linkKind, confidence, assertedBy
  • `episode`: a composite occurrence grouping related occurrences into a narrative unit; key attributes: episodeKind, memberCount, span
  • `sourceRecord`: the account or evidence from which the occurrence was recorded; key attributes: sourceKind, reportedAt, reliability

Relationships

  • `occurrence` -> involved -> `participation` (1:n): the set of parties and objects taking part
  • `occurrence` -> happenedAt -> `timeSpecification` (1:1): every occurrence carries exactly one temporal statement
  • `occurrence` -> happenedIn -> `placeSpecification` (n:1): places resolve through U7 references at the stated granularity
  • `causalLink` -> relates -> `occurrence` (n:m): cause and contribution assertions form a graph over occurrences
  • `episode` -> comprises -> `occurrence` (1:n): composite narrative units aggregate member occurrences
  • `occurrence` -> reportedBy -> `sourceRecord` (n:m): multiple independent sources can report the same happening

Events

  • `occurrenceRecorded`: a happening was entered into the record from a source
  • `occurrenceCorroborated`: an additional independent source confirmed the happening and certainty rose
  • `occurrenceAmended`: the recorded facts of a happening were corrected
  • `occurrenceDisputed`: a party formally contested the recorded account
  • `occurrenceLinked`: a causal or episodic link between occurrences was asserted

Projections

  • `personalTimelineProjection`: one party's occurrences in time order; omits other participants' private details
  • `publicChronicleProjection`: public occurrences only; omits non-consenting participants entirely
  • `causalGraphProjection`: occurrences and their causal links; omits participation detail