AsyncAPI vs. OpenAPI: Answers to Your Burning Questions

Re:AsyncAPI vs. OpenAPI: Answers to Your Burning Questions by no_wizard on Thursday September 09, 2021 @10:43AM (#28470232)

I couldn’t find anything about it being on hiatus, though it hasn’t had any updates on the spec from the looks of it, assuming I have it right[0]. Though for a spec I don’t feel like that means it’s in hiatus, they tend to move slowly

Would you mind elaborating if you know more?

[0]: https://json-schema.org/draft/2019-09/json-schema-hypermedia...

[ Parent | on HN ]

Re:AsyncAPI vs. OpenAPI: Answers to Your Burning Questions by hardwaresofton on Thursday September 09, 2021 @08:03PM (#28476208)

Another thing was that Hyperschema never really had its own proper page and documentation. You had to go to The jsonschema page[0] to find it. It says:

> JSON Hyper-Schema is on hiatus / not currently maintained as of 2021.

> This allows the team to focus the little time they do donate on JSON Schema core and validation.

> We may revisit JSON Hyper-Schema at a later date.

[0]: http://json-schema.org/

[ Parent | on HN ]

Re:AsyncAPI vs. OpenAPI: Answers to Your Burning Questions by relequestual on Friday September 10, 2021 @05:47AM (#28479453)

We really just wanted to signal that people shouldn't expect any attention on issues or PRs raised against Hyperschema till we can make time for it. Spec work is hard ya'll

[ Parent | on HN ]

Re:AsyncAPI vs. OpenAPI: Answers to Your Burning Questions by hardwaresofton on Friday September 10, 2021 @07:19AM (#28479962)

Reading through the hyperschema spec it instantly seemed like the best option with really good formalisms around discovery and of course the usual specification concerns.

Thank you for that hard work! Hyperschema is a great accomplishment already and I think (as I did before) that what will bring people to it is more tooling around it more than anything else.

[ Parent | on HN ]