Mike Ralphson

> it is still a good idea to disallow API keys in query strings It would leave the OAS unable to describe a large number of current APIs - best...

This also raises the question: what is a "root schema"? The term is not defined elsewhere in the spec. Given this fragment: ```yaml components: schemas: container: type: object properties: value:...

`/services.{format}` should work fine with whatever tools you're using, as long as you define a matching `format` parameter which is `in: path`.

See also #567 Much as `links` in OAS 3.0 don't serve to replace or mandate existing HTTP/hypermedia standards, but merely document how information can be used from responses, I'm tempted...

RAML 1.0 defines the properties necessary for oAuth1 authentication [as follows](https://github.com/raml-org/raml-spec/blob/master/versions/raml-10/raml-10.md#oauth-10)

See [issue 556](https://github.com/OAI/OpenAPI-Specification/issues/556) for (much) more on combining $ref and other properties.

> I thought descriptions supported GFM syntax? Because that could do hyperlinks at least. Maybe less powerful than you intended here, but it's something. @tycho01 `description` properties support commonMark syntax...

@gnxx - It looks like your API definition did not fully validate. Please mention (@) MikeRalphson to discuss. Here is the log output:

> [email protected] check > node --no-warnings --insecure-http-parser ./node_modules/@Mermade/api-registry/registry.js check https://api.zenark.com/v1/apidocs/openapi-v1.0.yaml https://api.zenark.com/v1/apidocs/openapi-v1.0.yaml FRV expected 'intger' to be equals one of Array [ 'integer', 'number', 'string', 'boolean', 'object', 'array' ] #/components/schemas/BeaconItem/properties/offset ✗...

@calebhearth - It looks like your API definition did not fully validate. Please mention (@) MikeRalphson to discuss. Here is the log output: