File tree Expand file tree Collapse file tree 1 file changed +8
-5
lines changed
Expand file tree Collapse file tree 1 file changed +8
-5
lines changed Original file line number Diff line number Diff line change @@ -21,10 +21,6 @@ definitions to remain lightweight and easy to understand.
2121
2222## 1. Introduction
2323
24- JSON Schema has been in development since ca. 2009 and has gone through several
25- iterations. The industry has largely standardized on "Draft 7" of JSON Schema,
26- with subsequent releases seeing comparatively weak adoption.
27-
2824There are rapidly growing needs for a standardized (IETF RFC) schema language
2925that can describe data types and structures and whose definitions map cleanly to
3026programming language types and database constructs as well as into the popular
@@ -33,7 +29,14 @@ applications and it must allow rich annotations with semantic information that
3329can be evaluated and understood by developers and by large language models
3430(LLMs).
3531
36- JSON Structure aims to address these different use cases and priorities while
32+ JSON Schema has been in development since ca. 2009 and has gone through several
33+ iterations. The industry has largely settled on "Draft 7" of JSON Schema, with
34+ subsequent releases seeing comparatively weak adoption. There's substantial
35+ frustration that many developers have with JSON Schema because they try to use
36+ it for scenarios that it was not designed for. JSON Schema is a powerful
37+ document validation tool, but it is not a data definition language.
38+
39+ _ JSON Structure_ aims to address these different use cases and priorities while
3740maintaining familiarity with JSON Schema's syntax. While JSON Schema focuses on
3841and excels at document validation, JSON Structure focuses on being a strong data
3942definition language.
You can’t perform that action at this time.
0 commit comments