---
title: "Comment by Charlie Jonas on \"JSON Schema is a constraint system\" | Hashnode"
description: "While I understand the point this is making, it seems that many of the popular uses of JSONSchema are for "Definitions" (API Contracts). These typical"
url: "https://hashnode.com/posts/json-schema-is-a-constraint-system/636ec3c29fcbe783317b2b8d/comment/648a347a1c2b5dbd4dc8e5d4"
---

[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)

[Charlie Jonas](https://hashnode.com/@cjonas)

[Jun 14, 2023](https://hashnode.com/posts/json-schema-is-a-constraint-system/636ec3c29fcbe783317b2b8d/comment/648a347a1c2b5dbd4dc8e5d4)

While I understand the point this is making, it seems that many of the popular uses of JSONSchema are for "Definitions" (API Contracts). These typically are then used directly for "Code Generation".

Would you say that this is outside the scope of what JSONSchema was designed for?

[Henry Andrews](https://hashnode.com/@handrews)

[Mar 12, 2024](https://hashnode.com/posts/json-schema-is-a-constraint-system/636ec3c29fcbe783317b2b8d/comment/648a347a1c2b5dbd4dc8e5d4#reply-65f0839ec5f013b3d4818c63)

Yes, and since I'm also very involved in the OpenAPI Specification, I'm very familiar with this mismatch and the problems it causes. We did try to address that in an [appendix to the modern JSON Schema drafts](https://www.ietf.org/archive/id/draft-bhutton-json-schema-01.html#name-references-and-generative-u) , to show how to bridge that gap, but it hasn't really caught on so far. (apologies for the very long delay in replying, see my "Coming Out of Hibernation" post for an explanation)