<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Rest on Pasi Dev</title><link>https://dev.pasi.pl/tags/rest/</link><description>Recent content in Rest on Pasi Dev</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 13 Jun 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://dev.pasi.pl/tags/rest/index.xml" rel="self" type="application/rss+xml"/><item><title>Introducing the 3.1 Maturity Level of REST API Design: JSON Schema-Aware Hypermedia</title><link>https://dev.pasi.pl/introducing-the-3-1-maturity-level-of-rest-api-design-json-schema-aware-hypermedia/</link><pubDate>Fri, 13 Jun 2025 00:00:00 +0000</pubDate><guid>https://dev.pasi.pl/introducing-the-3-1-maturity-level-of-rest-api-design-json-schema-aware-hypermedia/</guid><description>&lt;p&gt;REST API maturity is often evaluated using the Richardson Maturity Model (RMM), which defines four levels:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Level 0&lt;/strong&gt; – Single URI, typically using POST for everything&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Level 1&lt;/strong&gt; – Resources identified by URIs&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Level 2&lt;/strong&gt; – Use of HTTP methods to define behavior (GET, POST, PUT, DELETE)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Level 3&lt;/strong&gt; – Hypermedia controls (HATEOAS)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;However, traditional REST maturity models often overlook an important aspect: schema awareness. That&amp;rsquo;s why I would like to propose a new, unofficial but pragmatic step after Level 3:&lt;/p&gt;</description></item></channel></rss>