---
title: "Comment by Adam Leventhal on \"JSON Schema is a constraint system\" | Hashnode"
description: "This is a very eloquent articulation of an aspect of JSON Schema I've struggled to describe, making do with \"in code we often describe what a thing is; JSON Sch"
url: "https://hashnode.com/posts/json-schema-is-a-constraint-system/636ec3c29fcbe783317b2b8d/comment/67200dfc67c5d34a50a6c76e"
---

[Discussion](https://hashnode.com/posts/json-schema-is-a-constraint-system/636ec3c29fcbe783317b2b8d)

Comment [JSON Schema is a constraint system](https://hashnode.com/posts/json-schema-is-a-constraint-system/636ec3c29fcbe783317b2b8d)

[Adam Leventhal](https://hashnode.com/@ahl)

[Oct 28, 2024](https://hashnode.com/posts/json-schema-is-a-constraint-system/636ec3c29fcbe783317b2b8d/comment/67200dfc67c5d34a50a6c76e)

This is a very eloquent articulation of an aspect of JSON Schema I've struggled to describe, making do with "in code we often describe what a thing is; JSON Schema describes what a thing isn't".

May I ask though: why? JSON Schema is--I presume--intended to serve programmatic uses. Why choose a constraint model that's at odds with a structural (or "object oriented") approach?