Jon Skeet
Jon Skeet
I tried several times to think of a better title, but failed. I realize it's slightly hyperbolic at the moment. Versioning worries me a lot, and the point of this...
This is an initial drafty proposal for how we might handle minor versions. It's intended for discussion as a pull request, although we could potentially end up with it in...
This is a somewhat experimental way of gathering opinions on this issue, but hopefully it'll be clear enough. Each of my comments below contains: - A description of what it's...
The Discovery spec uses the "epoch" attribute as a form of version, and I don't currently understand the choice of term. I'd normally expect an epoch to be a sort...
Currently we have three XML types for data: - Text - Binary (base64) - "XML" The XML form is required to have a single child element and no peer non-whitespace...
For example, assuming appropriate namespaces, should we automatically preserve leading and trailing whitespace on context attributes? ```xml middle middle ``` How does this apply to text and base64 data elements?...
While working on introducing the term *core attributes* within the specification and primer, it looks like we also have another area of ambiguity, this time with extension attributes. Any given...
As promised, this is the result of trawling through the JSON format spec, and seeing which aspects should possibly be specified elsewhere, or generally clarified. There was actually less scope...
The Discovery spec uses JSON with all-lower-case property keys (e.g. "subscriptiondialects" and "subscriptionurl") which are quite tricky to read. I'd expect more idiomatic JSON keys to be "subscriptionDialects" and "subscriptionUrl"...
From https://github.com/cloudevents/spec/blob/v1.0.1/http-protocol-binding.md#33-batched-content-mode: > All batched CloudEvents MUST have the same specversion attribute Shouldn't this be up to the event format to decide? (It would be reasonable for a batch event...