CloudEvents additional custom data

So, I am talking with cdEvents who use cloudevents as the underlying transport format, and one thing I noticed is that they have an additional field called payload in their requests.

{
    "specversion" : "1.0",
    "type" : "com.github.pull_request.opened",
    "source" : "https://github.com/cloudevents/spec/pull",
    "subject" : "123",
    "id" : "A234-1234-1234",
    "time" : "2018-04-05T17:31:00Z",
    "comexampleextension1" : "value",
    "comexampleothervalue" : 5,
    "datacontenttype" : "text/xml",
    "data" : "<much wow=\"xml\"/>" // Notice the nesting of the data
}

This unfortunately is a breaking change to anyone adhering to this standard, so instead I proposed some alternative solution in cdEvents#40. The basic idea is making data a top level parent, and introducing something like a cd-events-metadata field in the payload. So instead

<much_wow>
        <somefield>hello world!</somefield>
        <cloud_events_metadata>
                <type>com.github.pull_request.opened</type>
                <source>https://github.com/cloudevents/spec/pull</source>
                <subject>123</subject>
                <time>2018-04-05T17:31:00Z</time>
                <comexampleextension1>value</comexampleextension1>
                <comexampleothervalue>5</comexampleothervalue>
                <id>A234-1234-1234</id>
                <spec-version>1.0</spec-version>
        </cloud_events_metadata>
</much_wow>

But is this possible with cloudevents? Have you guys thought about something like this?

[afrittoli]

@duglin Do you think it would be worth adding some text to the binary mode description to further clarify its purpose?

[duglin]

See: https://github.com/cloudevents/spec/pull/1035