Doug Davis

thanks - on the agenda for today

Approved on the 8/11 call

I believe this was done to allow for new filter expressions to be defined. But as you noted #1038 perhaps we need to define it differently since it matches everything.

Can't people just put an xs:any at the end of their schema for the current list of CE elements? https://www.w3schools.com/xml/schema_complex_any.asp

thanks for the reminder... been way too long since I've played with XML :-) @JemDay thoughts?

They're just sibling attributes to the CE defined ones. We tried to have them be treated just like the optional CE defined attributes.

Since you said to ignore xml, here's the json version from the spec: ``` { "specversion" : "1.0", "type" : "com.github.pull_request.opened", "source" : "https://github.com/cloudevents/spec/pull", "subject" : "123", "id" : "A234-1234-1234",...

Since, like CE, we're not trying to manifest these fields in all sorts of interesting places (like http headers where case doesn't matter), this seems like a reasonable thing to...

All - we discussed this on today's call but there wasn't a significant preference on a direction. So, we're going to vote on this during next week's call. We decided...

camel (subscriptionDialects): cathy, clemens, jem, klaus, lance, manuel, scott, camel, tommy, doug snake (subscription_dialects): all-lower (subscriptiondialects): erik, ad