Description
REMReM Generate should accept both a CONTEXT and CAUSE links in the same event.
Motivation
We need clear semantics in the way pipeline activities should be linked together in a non-event-driven scenario
Exemplification
A pipeline driven by e.g. Argo. How should the events be linked to each other? One way is to let the ActT of a pipeline step link to the previous ActF (or ActT?) by a CAUSE link, but maybe we should instead create a new link type for such a link?
Benefits
Clear semantics in an event graph describing the order of activities in a non-event-driven scenario, enabling clear visualizations and metrics.
raja-maragani
commented
4 years ago
Description REMReM Generate should accept both a CONTEXT and CAUSE links in the same event.
Motivation We need clear semantics in the way pipeline activities should be linked together in a non-event-driven scenario
Exemplification A pipeline driven by e.g. Argo. How should the events be linked to each other? One way is to let the ActT of a pipeline step link to the previous ActF (or ActT?) by a CAUSE link, but maybe we should instead create a new link type for such a link?
Benefits Clear semantics in an event graph describing the order of activities in a non-event-driven scenario, enabling clear visualizations and metrics.
Possible Drawbacks None