CloudEvents clarity

[olitomlinson]

What content needs to be created or modified?

Things that are missing

• What is the relationship between using Cloud Events and how de-dupe is enabled? It is not clear. Dapr suggests that CloudEvents are required to enable "deduplication by messageId" but doesn't state how this is actually achieved? Many brokers have their own native deduplication feature. Does dapr provide its own de-dupe capability, or does dapr rely on the underlying broker? or both?
• It is not clear that if a developer publishes a manually crafted Cloud Event envelope (dapr does not create the envelope) then Dapr will actually augment that envelope with any missing properties. More detail about this behaviour is needed.

---

Also, the below screenshot is ambiguous, for the following reasons

• This sentence doesn't make sense - "Dapr implements the following CloudEvents fields when creating a message topic."
• "The following example demonstrates an orders topic message sent by Dapr" - what is mean't by sent by dapr? Whats the scenario here?
• the data object in the json should be correctly indented.

Where should the new material be placed?

[olitomlinson]

cc @berndverst

[olitomlinson]

Opened this docs issue forever ago, and its still tripping up my Teams to this day.

Really need docs to be specific on what the actual behaviours are.