Alexander Tkachev

Maybe we can create an extension attribute called `ceschema` which is a uri that describes the schema of all the attributes of an event. given they are serialized into a...

We talked on the call about that idea of creating such `ceschema` attributes and it seems it does not actually solve a particular problem. Because if a consumer receives an...

@gregsdennis each intermediary MAY add or remove optional attributes because nothing prohibits it to do so. For example I as an intermediary decide that each event passing through me will...

@gregsdennis So you are saying the the schema MAY validate only some of the attributes, correct? And I as an intermediary MAY add new attributes to the event as long...

@deissnerk We talked about the implementation in the call two weeks ago. The way we are headed right now is defining an `attrschema` URI attribute which points to a schema...

@deissnerk @devinbost Here is my current proposal for the attrschema extension https://github.com/cloudevents/spec/pull/1106

@duglin I don't think my SVG suggestion will work for now. Maybe in the future I will try to solve it's issues, but for now seems that it is not...

Maybe we can add an extension for the case that the data is encrypted. `cryptdatacontenttype` will specify the data content type of the decrypted/signed data `datacontenttype` will specify the data...

@devinbost I took upon myself for defining such extension. But probably this will happen only at the meeting next week

@alexec I don't understand why putting the serialized JWE inside the data is not efficient. Either way you need to copy the content of the JWE metadata somehow inside the...