Mike Ralphson

I think the renaming of `members` to `properties` is correct here (to get a valid JSON Schema object from the aws-sdk "Shape") and the renaming of `member` to `items` is...

The AWS APIs on GitHub are updated now, it will take about 35 minutes for the CI job to finish to publish them to the APIs-Guru API.

The `xml.name` is set on the items of the array, not on the array itself, where `xml.wrapped` would be set.

How will the canonical form represent circular schemas in **a document** if all `$ref`s are to have been resolved? JSON has no mechanism to support this, and we ban the...

> Different processors could accomplish this in different ways, and Canonical Form does not guarantee that the output will always be exactly the same, regardless of which processor you use....

> Please consider supporting e.g. "some-string-prefix-${ENVVAR_NAME}-and-suffix" interpolation to make reinventing the wheel unnecessary. [RFC6570](https://www.rfc-editor.org/rfc/rfc6570.html#section-2.2) states > The expression syntax specifically excludes use of the dollar ("$") and parentheses ["(" and...

> Alright, that's a very good reason not to do it. Thanks! No, I'm saying you can do it (today) with `$(..)` not `${...}` but as you need a tool...

> But since parameters are an array, in order to edit a single description, I would have to reproduce the entire array, no? Is there a way to more precisely...

Also, a parameter `name` is not a unique identifier, the `in` value is also required.

I believe the YAML-like but path-supporting object representation I was thinking of was [HOCON](https://github.com/lightbend/config/blob/master/HOCON.md#hocon-human-optimized-config-object-notation), as mentioned in OAI/OpenAPI-Specification#1314 - as was mentioned there, there is no reason tools cannot support...