New `connects` impact on track/trace
Stefano from Dyne wisely asked about this for their Digital Product Passport work:
"my question is where does the 'correcting" event shows up when tracing back, as it is temporally (possibly much) later but logically next to the 'corrected' event? This has implications for the Digital Product Passport (which you might say it is an application outside the standard, but then the question becomes does VF support DPP applications or not?)"
Initial thoughts, discussion welcome:
- A correcting event won't fit into any other structure (like input or output on a process), although I suppose it could be added where the original event is, if there is a reason to do that. I wasn't thinking that would be done. So if not, the
corrects
relationship is the only way to get the event into a flow explicitly. - A UI could display them separately, or could combine them into one "corrected" event.
- For track/trace, I don't think timing matters, it all attempts to be causally ordered. But of course a UI could group things when it matters.
- I think it would work in the track/trace if the logic explicitly looked for the
corrects
relationship as part of that logic. It would look like a separate (short) branch in the graph if not combined to make a corrected record. But I will try out some examples, and add to the yaml examples in the doc and the suggested trace pseudocode.