In 76% of modern OpenAPI specs, JSON Schema dominates the specification

In 76% of modern OpenAPI specs, JSON Schema dominates the specification(sourcemeta.com)

4 points by jviotti 19 days ago | 3 comments

benoau 19 days ago |

I really like OpenAPI in conjunction with openapi-fetch to create a typed interface for frontends/tests/etc to leverage. I especially like deleting the manual types that get strewn around frontends with inaccuracies, bespoke class names and unnecessary property names/types transformations.

I wouldn't work without these tools anymore!

aeberhart 19 days ago |

Interesting analysis! Do you also have insights into which JSON Schema constructs are used most often in that dataset?

jviotti 18 days ago | |

I don't but seems like an interesting follow up for us.

There have been research in that area (i.e. https://link.springer.com/chapter/10.1007/978-3-030-34146-6_...) but usually the input set is too small or biased.

As a JSON Schema TSC member, I consulted with various organisations on large scale JSON Schema use, which is where things get truly interesting (>8000 complex interconnected schema data models) though all of them are sadly closed-source.