The list below contains the set of changes that the group had identified as potential candidates for a v2 of the CloudEvents specification. There no guarantee as to when, or if, a v2 might happen, or that any of these will be adopted. Rather this list is just a reminder to consider them so that we can reduce the number of open issues and PRs on our backlog.
- Do we want a new optional "mustunderstand" core attribute
- Why does the HTTP binding for batch require the same spec version for all events in the batch?
- handling of datacontenttype is inconsistent
- fix(protobuf)!: Expose CloudEvent structure with explicit fields
- The case for minor version
- How should we handle text_data in proto
- Discussion on CloudEvent data and transcoding
- For discussion: SDK conformance tests
- Discussion of the meaning of optional
- JSON format spec review (for scope creep, ambiguity etc)