David Biesack

Also note that although these source files use Markdown source with YAML frontmatter, the site does _not_ convert Markdown within that frontmatter to HTML -- see http://api.specificationtoolbox.com/extensions/ for example and...

Added to _extensions via PRs #47 #53

@philsturgeon Re "the default behavior for `additionalProperties` has changed in OAS 3.1 to make it more permissive." Can you provide a citation for that? https://spec.openapis.org/oas/v3.1.0 does not specify any behavior...

@philsturgeon That 3.0.3 vs. 3.1.0 language is not talking about the JSON schema `additionalProperties` keyword (i.e. whether a JSON value can have properties not listed in the schema `properties`) but...

See also https://github.com/api-specification-toolbox/tools/issues/11

I very much like [RAML's use of traits](http://raml.org/developers/raml-200-tutorial#traits) for this. Let's look there for design inspiration.

Is there a JSON equivalent of this YAML

"_additional data can be added to extend the specification at certain points_" does **not** mean (to me) "_only add additional data_". It means exactly what it says, "_extend the specification_"...

@casualjim I agree wrt YAML/JSON. I'm bilexical myself, though not fluent in YAML. But we need to be careful about using constructs such as

Another option is to add a `json-pointer` or similar property to each item in the output when using `--format json`. I don't know which other output formats are extensible -...