OSDM Tech working group's stance on event types, especially regarding their source

[ManuelQuemerais]

We’re interested in OSDM Tech working group's stance on event types, specifically regarding the potential distinction between the following:

• Propagated events: Events that are forwarded based on events actually received from partners or suppliers.
• Inferred events: Events created by the OSDM implementer upon detecting partner/supplier changes (e.g., via opportunistic reads, without actually receiving a partner event).
• Internal events: Events created by the OSDM implementer to indicate its own state changes (e.g., an update to the 'purchaser' record).

From what we can see, the current documentation and contract mainly cover 'propagated' and 'internal' events, but don't fully cover inferred events (e.g., for these, the event's timestamp may be fairly far from the actual change time on the partner/supplier side)

Should we want to explicitly communicate these distinctions, we see a few potential approaches:

• Adding this information to the event summary (though this would be a fairly crude approach).
• Distinguishing them by event type (e.g., using different event types for a fulfillment refund detected via a GET request versus one pushed directly by a partner).
• Introducing a dedicated attribute specifically for this purpose.
• ...