Quote Kin

Signed-off-by: Juan Cruz Viotti <jv@jviotti.com>

Author: jviotti

content/blog/g7-runs-on-json-schema/index.markdown

@@ -171,6 +171,14 @@ As Charlie Holland puts it, [*JSON Schema has become "the interface definition
 language for AI tools"*](https://www.chiply.dev/post-schema-languages).
 **A government MCP server is, on closer reading, a JSON Schema deployment.**
 
+We are not the only ones making this observation. When Kin Lane inventoried
+the API specifications stewarded by the [Linux
+Foundation](https://www.linuxfoundation.org), he concluded that [JSON Schema
+is the connective tissue across the whole
+catalogue](https://apievangelist.com/2026/06/30/the-linux-foundation-is-the-home-of-our-api-specifications/):
+OpenAPI, AsyncAPI, CloudEvents, and others all build on it, and *"JSON Schema
+is the substrate the other specifications are built on top of"*.
+
 Taken together, public-sector use of OpenAPI and MCP rank among the largest
 JSON Schema deployments in the world.
 

content/blog/json-schema-dominates-openapi/index.markdown

@@ -73,6 +73,18 @@ paths:
                     minLength: 1
 ```
 
+This layering is not an OpenAPI quirk. When [Kin
+Lane](https://apievangelist.com) inventoried every API specification stewarded
+by the Linux Foundation, he found that [JSON Schema is the connective tissue
+of the entire
+catalogue](https://apievangelist.com/2026/06/30/the-linux-foundation-is-the-home-of-our-api-specifications/):
+
+> The deeper I looked, the more one thread kept showing up underneath
+> everything else: JSON Schema. OpenAPI uses it. Arazzo and Overlay use it.
+> AsyncAPI uses it. CloudEvents ships a JSON Schema. OSV and SPDX lean on it.
+> The OpenAPI metaschema is JSON Schema. [...] JSON Schema is the substrate
+> the other specifications are built on top of.
+
 ## Let's measure how big the engine is
 
 We analysed 4,127 real-world API specifications from the
@@ -196,5 +208,11 @@ API-first registry, a governance model, a discovery mechanism, and tooling
 that understands them as semantic objects rather than as opaque sections
 within a YAML file.
 
+Kin Lane [arrives at the same
+conclusion](https://apievangelist.com/2026/06/30/the-linux-foundation-is-the-home-of-our-api-specifications/)
+from the standards side: *"there is no reason a CloudEvent's schema, an
+AsyncAPI message, and an OpenAPI body could not lean on the same JSON Schema
+tooling and the same registry patterns"*.
+
 The data says the schema layer is already most of your API. The question is
 whether you treat it that way.