Henry Andrews
Henry Andrews
* Fixes #3730 (which consolidated at least two other issues/discussions) These formats can easily be modeled as if they were JSON arrays, with fairly minimal new tooling requirements. As documented...
As noted in Slack discussions, there is no formal specification for where variables can appear in server URL templates and path templates. There does not seem to be any reason...
* Fixes #3775 Undefined means "don't use this even if it seems to work, as there are cases where it won't." Implementation-defined means "this isn't portable or interoperable, but it...
We need to figure this out, so I'm extracting the recent/relevant comments from #151 as it is so old and long that potential contributors are discouraged from figuring out where...
Docs for the `contentType` field of the Encoding Object in 3.1.0 read (***emphasis added***): > The Content-Type for encoding a specific property. Default value depends on the property type: for...
This is the next step in un-blocking OASComply. Unlike the previous OASComply-related PR, this PR ***does not*** apply to v3.0.4. What, if any, wording about document parsing needs to go...
As I write PRs, I keep finding little things that I'm not sure how to do. Some examples: * What are the rules about which headings go in the TOC...
As seen in PR #3688, `scripts/md2html` fails to use the correct revision of the MAINTAINERS.md file for the 3.0 and 3.1 specifications. Specifically, `build.sh` [uses a specific revision for the...
We already use these terms a bit in the spec, but with PRs like these: * #3732 * #3772 * #3758 we are relying more on such descriptions to define...
Resolving component names used in _referenced_ (as opposed to _entry_) documents is ambiguous, particularly in 3.1 where we advertise the ability to have a `components`-only document to use as a...