Henry Andrews

Results 182 issues of Henry Andrews

These fields have usually been interpreted by us as requiring serialized values, but this is called into question on an (at least) annual basis ([2022](https://github.com/OAI/OpenAPI-Specification/issues/3041#issuecomment-1449051507), [2023](https://github.com/handrews) ([mostly on Slack](https://open-api.slack.com/archives/C1137F8HF/p1675197255857239)), [2024](https://github.com/OAI/OpenAPI-Specification/pull/3893),...

example obj/keywords

Many long-requested features for OAS can now be better handled by using the Overlay and/or Arazzo specifications. I think Arazzo mostly overlaps with the Link Object, but I might be...

clarification

@karenetheridge and @notEthan raised various points about confusion and usage of the Server Object and its `url` field in PR #4389. From @karenetheridge > We can also offer caution that...

deployment

PR #3234 proposes a `url-template` format, and is currently in discussion regarding the scope and naming of the format. PR #3235 applied the format to the current schema, resulting in...

Schema
format-registry

From @karenetheridge in PR #4389 > Perhaps we can simplify this by simply strongly recommending that `$self` is an absolute URI (i.e. fully resolved; resolving it against another base URI...

re-use: ref/id resolution

From @notEthan in PR #4389: > I think this goes somewhat into the weeds of circumstances when an implementation might need to be told the retrieval URI. But it seems...

re-use: ref/id resolution
deployment

We don't want schema URIs with `latest` in place of the date because schema contents should not change unexpectedly. However, we need some way for folks to access the latest...

Schema
website

GitHub Pages has several very problematic limitations for a project focused on HTTP standards: * It does not allow setting `Content-Type` except via file extension, which is not how our...

Housekeeping

See discussion #4233 and issue #4147. Requiring the patch version is creating tremendous amounts of confusion. While we cannot seem to reach consensus on forbidding it, there has long been...

metadata

I expected it would (e.g. `contentType: text/css, text/javascript, image/*`) by analogy with the `Accept` header, while @ralfhandl read it more literally and expects only `contentType: text/css,text/javascript,image/*` would be allowed. I...

clarification
media and encoding