Klaus Deißner

I wonder, how changes to attributes like `authscope` and `subscriptionurl` are handled. Attributes like these may be adjusted by a DE to reflect a local eventing infrastructure. If epoch had...

@duglin I think, the important text in the section you referenced is >For any other type, the implementation MUST translate the data value into a JSON value, and use the...

There was some discussion around this in #520. In 0.3 we still had an attribute called [datacontentencoding](https://github.com/cloudevents/spec/blob/v0.3/spec.md#datacontentencoding), but we had to remove it. Instead the data_base64 field was introduced in...

@tsurdilo The `dataschema` attribute is defined as a URI. So you can of course use it to identify a schema like the one you posted, but it won't have any...

@Thoemmeli I agree to your point, but `"{\"foo\": \"bar\"}"` is a string and therefore also a JSON value. In that sense the example is valid, but the `datacontenttype` in this...

I don't see any special handling of the JSON format here, @dazuma. I think the nesting of quotes combined with the different representations of the event in Javascript (not JSON)...

@dazuma IMHO it should be: `dataEncoded : ''` @athalhammer Currently the go SDK only recognizes `application/json` and `text/json` [into account.](https://github.com/cloudevents/sdk-go/blob/43b8eca508219f50e528e86de1aa3df0f97546fa/v2/event/event_unmarshal.go#L396), but it's an interesting question. @n3wscott @slinkydeveloper What do you...

This depends on what we want to achieve with discovery. Is the discovery API only used to support UIs for browsing events? Do people have in mind to generate boiler...

Yes, I think some of the questions raised in there are still valid. I hope I can address them with the proposal I'm working on.

@erikerikson Of course what you describe regarding identities and authorizations between A and B is possible. In practice it can be quite some challenge, though. I'm not a security expert,...