Henry Andrews

@dret I'm trying to understand how this would fit in the top-level or info objects. Would this be for links that are expected to be present on every response? What...

@dret I was going to ask how that differs from the existing OAS 3.0 Link Objects, but then I looked and sure enough there is no place for RFC 8288...

@dret to be fair to OpenAPI, they have repeatedly been clear that they are not attempting to support actual (meaning runtime) hypermedia. Agree that the naming of Link Objects vs...

Note that while I definitely have an opinion on this, if there's a clear majority in favor of giving `contentSchema` location behavior then I'll go with that. I filed this...

@notEthan thanks for replying and copying over that text. > However, lacking an `$id` has the problem @handrews noted that its retrieval URI is the same as its parent's, if...

This issue doesn't mean that we have to keep `$schema` and `$vocabulary` exactly as they are, just that whatever we end up with in the next release needs normative language...

@awwright prominent members of the JSON working group told us (in email I can no longer find b/c their email software is such a mess) that they would likely throw...

> One of the benefits of an RFC is other standards can normatively reference it, and use JSON Schema to define their JSON-based syntaxes. Independently publishing a specification does not...

@admin-cimug thanks so much for this comment, it's tremendously helpful. I'd like to understand how a couple of possible scenarios might impact you. Currently, @jdesrosiers (from our core team) and...

@admin-cimug a few more questions: * how do specifications like OpenAPI ([charter](https://www.openapis.org/participate/how-to-contribute/governance)) or AsyncAPI ([charter](https://github.com/asyncapi/community/blob/master/CHARTER.md)) which have their own governance processes and are affiliated with the Linux Foundation, fit into...