Jon Skeet

> We could create a set of common types for the above types, but right now they wouldn't have any effect. And that's what I'm suggesting should change. Inlining "external"...

We shouldn't close it. It should be part of our discussions about the DevX for events. (Those discussions are ongoing, they've just been a bit behind-the-scenes.) I'm happy to keep...

I'd like to know more about what's being proposed. I would expect the `dataschema` attribute to at least potentially refer to a JSON schema for the payload. But is this...

@devinbost: We have some guidance on that in https://github.com/cloudevents/spec/blob/main/cloudevents/primer.md#versioning-of-cloudevents EDIT: Whoops - just seen that's the note you referred to.

@devinbost: I think it's really up to providers, to be honest. I'm not entirely sure what the request/proposal is here - and I may well not be the best person...

I believe we *used* to do this, a very long time ago... and there was some reason why it was really bad. I can't remember what the reason was, offhand...

(In an ideal world, the descriptor would be a binary file included as a resource in the assembly, but that would be quite painful to get working, I suspect.)

It's possible that both VS and the compiler itself are okay with the huge concatenation now. I'll try it when I get a chance, but like the default string literal...

Just a drive-by comment while looking at `RepeatedField`: doesn't this really depend on being able to return the array to the `ArrayPool` when we're done with it? That's fine when...

Assigned myself as I'm working on having a consistent set of libraries and a consistent set of documentation for field masks.