Add a known extension attribute to support bitemporal event data

[aucampia]

Add a known extension attribute to support bitemporal event data

[duglin]

I don't see a problem with a time representing the time the CE was created, but I'm curious about some of the scenarios you mentioned. In particular, the detection of the event showing up more than once... why wouldn't people look for a duplicate CE.ID rather than look at timestamps?

[aucampia]

In particular, the detection of the event showing up more than once... why wouldn't people look for a duplicate CE.ID rather than look at timestamps?

Well, it would not be for detecting duplicates, it would be for distinguishing duplicates, so two events with the same CE.ID could be kept as long as their createdtime attributes are different, and they would be kept so that anything that was using the old event would still be able to get it if they extract events using both the createdtime and time.

[aucampia]

I'm a bit unsure about the name, some other options:

• eventtime - given that the time attribute should be the occurrence time, this is possibly the best option, however, this is also slightly confusing to people who may not be familiar with the CloudEvents terminology.
• timerecorded - this may be less ambiguous than recordedtime.