Henry Andrews

We're struggling a bit with this in JSON Hyper-Schema as well. Currently, our `links` is an array of objects (which may use URI Templates), so multiple objects in the array...

> It seems to me that the most sensible solution would be to support referencing in the AsyncAPI document according to the JSON Pointer guidelines, and in the case of...

TL;DR: * AsyncAPI can define the usage of a reference in terms of the result of applying the reference target (regardless of what kind of schema it is) rather than...

@magicmatatjahu > is there any implementation (in any language, at least one) that supports 100% all referencing cases (in dereferencing phase) in the new OpenAPI 3.1? Yes, I believe @karenetheridge's...

Since variations have been brought up by many people in many threads, I'm going to make this plea at the top level: ### Please, please, ***please*** do not make up...

> Agreed, but didn't JSON Schema do the same? They're all JSON Schema Org specs (including JSON Reference which, like all of the early JSON Schema specs, was edited/authored or...

Thanks, @whitlockjc . > a $ref and not knowing if it's the draft spec to follow or the JSON Schema specific version seems like a valid concern. Not to re-litigate...

@webron is this sort of thing a spec clarification candidate or would it better live in tutorial per OAI/Outreach#34?

@wohnemus if you want a fully dynamic HATEOAS-driven REST API, I encourage you to come over to the JSON Schema project and help us out with JSON Hyper-Schema, which explicitly...

@wohnemus and anyone else interested in hypermedia description: we're in the final review phase for publishing Draft 06 for the next (probably) 2 weeks or so, but after that I...