Henry Andrews

@bassmanitram great! Please feel free to introduce yourself on our quiet but still functional [mailing list](https://groups.google.com/forum/#!forum/json-schemal) or grab my email address out of the the [current drafts on master](https://github.com/json-schema-org/json-schema-spec) and...

FYI, for value / title or description pairs the official JSON Schema recommendation (using draft-06 syntax, replace `const` with single-element `enum` for draft-04) is: ```YAML oneOf: - const: foo title:...

@adamjones1 I would use an `anyOf` since the `const` values ensure that it behaves mostly like a `oneOf`. At that point, you just need to figure out if the instance...

@thejeff77 this sounds more like a problem with the code generation tool not understand the schema than a problem with the schema.

@dpashkevich this is more a JSON Schema thing than an OpenAPI thing, so such a keyword could be implemented as an extension vocabulary (OpenAPI itself implements a few additional keywords...

@dpashkevich my point is that people can take action now, and in doing so can demonstrate the usefulness and suitability of a proposal. We don't have to just debate it...

@thejeff77 someone needs to write up the spec for the keyword(s) involved, assign a URI to the vocabulary, publish it (somewhere, anywhere) so that people who want to use it...

@rmunix regarding URL max length problems, I was very happy to see the HTTP SEARCH method draft RFC revived last month: https://tools.ietf.org/html/draft-snell-search-method-01

I believe the only difference is that `/`, `?`, and ';' are no longer reserved within the query string in RFC 3986, correct? (And I agree, it should reference RFC...

@galvo formal extension vocabularies will be a thing in OAS 3.1 (with JSON Schema draft 2019-09 or later). So there aren't any yet but there is a lot of interest....