event trajectory
- CURIE:
gmeow:eventTrajectory - IRI: https://blackcatinformatics.ca/gmeow/eventTrajectory
- Category: property
- Defined by:
gmeow:slices/events - Box roles: RBox role (What is this?)
The trajectory of a moving event — a parade, march, migration, or procession — describing its continuous space-time path. Reuses the gmeow:Trajectory facility from the locations module (trajectory design). Non-functional: competing trajectory claims from different sources coexist (Principle 9).
Structure
Property shape: object property; gmeow:Event -> gmeow:Trajectory
Practical Pattern
Use gmeow:eventTrajectory from gmeow:Event to gmeow:Trajectory when the relationship itself belongs in the native GMEOW graph.
Common Companion Terms
External Equivalences
Equivalent or closely aligned targets: crm
Linkages
Generated from the canonical mapping DSL. SSSOM files are the generated public interchange form for term equivalences.
Term Equivalences
| Source | Kind | Profile | Predicate/Relation | Target | Evidence |
|---|---|---|---|---|---|
gmeow:eventTrajectory |
equivalence | - |
skos:relatedMatch | crm:E92_Spacetime_Volume | gmeow-events.sssom.tsv; gmeow:eqEvents128; confidence 0.6 |
Usage Advice
Use when
- Use for the continuous space-time path of a moving event — a parade, march, migration, or procession — when the route itself, not just its endpoints, must be modelled.
Avoid when
- Avoid it when two discrete endpoints suffice (use
gmeow:eventFromLocation/eventToLocation) and avoid collapsing competing routes — keep it non-functional so standpoint-indexed trajectories coexist.
How to use
- Point the
gmeow:Eventat agmeow:Trajectoryfrom the locations module rather than minting a parallel path class; carry source-specific routes as coexisting claims.
Examples
- ex:parade
gmeow:eventTrajectoryex:downtownRoute.