Sebastien Rosset

Thank you for the clarification. > Metric attributes are defined in the scope of a given metric (in OpenTelemetry) and there is no possible conflict of 2 attributes with identical...

After reading this issue, I'm still confused about the direction. There seems to be two variants of the specs. Does that man library developers will have to decide which version...

Related to this, it would be useful to have a standardized way to document the checks in a standard format, maybe with a name, tag (or category) and description. Ideally,...

> Though I don't see how this relates to golangci-lint specifically, which uses `go/analysis` and can access this information directly from Go. Emitting this information in JSON would be interesting...

> [golangci/golangci-lint#1685](https://github.com/golangci/golangci-lint/issues/1685) can be implemented right now, via go/analysis.Analyzer.Name and go/analysis.Diagnostic.Category. [golangci/golangci-lint#1767](https://github.com/golangci/golangci-lint/issues/1767) might indeed need some additional work, as there is nothing to encode "tags". Of course coming up with...

@tedepstein, in #2141 two of your sentences caught my attention: ```yaml # Require type==obj1, so a standard JSON schema validator can discriminate. # This duplicates the discriminator logic, so should...

> @sebastien-rosset , > > > 1. You are stating the `discriminator` keyword can always be replaced with a JSON schema _functional_ equivalent. > > Yes, functionally equivalent for validation...

> After OAS 3.1 catches up to the most recent JSON Schema, which supports modular extension vocabularies, we expect additional work on one or more code generation vocabularies, which will...

> @sebastien-rosset I suspect what I proposed two years ago would also still work. There's another approach in [Appendix E](https://json-schema.org/draft/2019-09/json-schema-core.html#rfc.appendix.E) of draft 2019-09. > > The reason I brought up...

Now that 3.1 RC-0 has been released, I see 3.1 RC-0 has the following text which is incorrectly referring to the 3.0 release: > The discriminator object is legal only...