Mike Ralphson

Closing due to inactivity - but please feel free to reopen the issue if necessary.

@cmheazel hopefully the security proposal section of the TSC meeting will be recorded.

Could you show an example of what you'd like to be able to do to clarify your question?

The YAML specification is referenced within the OAS specification, and so we defer the quoting rules to that spec. E.g. a `$ref` value containing a `#` character requires quoting so...

Examples can be PR'd against the master branch if they're external to the spec, otherwise the `v3.0.3-dev` branch and `3.0.3.md` file.

So by "where" you mean...?

@ioggstream sorry to come back to this after so long. I don't think this recommendation should be in the spec itself, as people should be free to quote (and indent...

Belated thanks for bringing this up. A PR with candidate wording would be gratefully received.

Only the top-level schema object name must conform to the components key regex. Is it possible you could do something like ```yaml components: schemas: container: type: object properties: namespace.generic(type): type:...

@cmheazel an empty security requirement object doesn't have any names, so none of the names violate this constraint. It looks like this ```yaml security: [ {}, ... ] ``` not...