<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Sourcemeta Blog on The JSON Schema Registry | Sourcemeta One</title>
    <link>https://www.sourcemeta.com/blog/index.xml</link>
    <description>Recent content in Sourcemeta Blog on The JSON Schema Registry | Sourcemeta One</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 28 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.sourcemeta.com/blog/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>In 76% of modern OpenAPI specs, JSON Schema dominates the specification</title>
      <link>https://www.sourcemeta.com/blog/json-schema-dominates-openapi/</link>
      <pubDate>Tue, 28 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://www.sourcemeta.com/blog/json-schema-dominates-openapi/</guid>
      <description>TL;DR: We analysed thousands of real-world OpenAPI specifications and found that in 76% of modern OpenAPI 3.x specs with a typed data model, JSON Schema is the majority of the file. In the best-known APIs, it routinely exceeds 80%. The schema layer is the substance of every API contract, yet almost no tool is positioned accordingly.&#xA;OpenAPI is, by every reasonable measure, the dominant standard for describing HTTP APIs. It is a Linux Foundation project whose founding members include Google, Microsoft, IBM, Capital One, and PayPal.</description>
    </item>
  </channel>
</rss>
