Skip to content

Issues: json-schema-org/json-schema-spec

Beta
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clear current search query, filters, and sorts
74 Open 757 Closed
74 Open 757 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Assigned to nobody Loading
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

"requiredProperties" keyword core Type: Enhancement validation
#846 opened Feb 4, 2020 by awwright draft-next
@Relequestual
19
Extend treatment on Unicode and/or its security considerations core Type: Security
#215 opened Dec 29, 2016 by awwright stable-release
@awwright
8
Concise encoding for JSON Schema core
#259 opened Feb 24, 2017 by mkovatsc
17
Security issue: Depth and width of resolutions Type: Security
#315 opened May 2, 2017 by brettz9 draft-future
@awwright
1
using/defining the "schema" link relation type core
#522 opened Dec 19, 2017 by dret
28
Consider "API best practices" section core
#544 opened Feb 3, 2018 by awwright
@awwright
4
Schema negotiation with HTTP Prefer core Priority: Medium
#601 opened May 28, 2018 by handrews
Vocabulary keyword meta-data, particularly for in-place applicators core Priority: High Type: Enhancement
#602 opened Jun 6, 2018 by handrews draft-next
11
Is there a standard notion of "best" error? Type: Enhancement
#632 opened Jun 30, 2018 by Julian draft-future
7
Keyword Behaviors - assumptions of knowledge is too high clarification Items that need to be clarified in the specification core
#635 opened Jul 11, 2018 by Relequestual draft-next
@Relequestual
3
"Keyword Interactions" section seems ambiguous and inaccurate clarification Items that need to be clarified in the specification Priority: Medium
#701 opened Dec 26, 2018 by ucarion draft-next
@Relequestual
13
Survey of localization tools
#743 opened May 27, 2019 by awwright
3
Investigate CBOR compatibility core question
#6 opened Jul 31, 2015 by awwright
30
JSON Schema Core - 11.1/11.2 - link relation type "schema" not explained clarification Items that need to be clarified in the specification core
#833 opened Jan 12, 2020 by hrennau
@awwright
13
Consolidate information on loading schemas core
#849 opened Feb 5, 2020 by handrews draft-next
@Relequestual @handrews
12
"missing" or "defaultProperties" annotation keyword proposal Initial discussion of a new idea. A project will be created once a proposal document is created.
#867 opened Mar 1, 2020 by awwright
@Relequestual
21
Keyword for extending a schema core Priority: Low Type: Enhancement
#907 opened May 2, 2020 by awwright
22
An alternate approach to meta-schemas core
#911 opened May 7, 2020 by jdesrosiers draft-future
27
Declare keyword use with $schema core
#918 opened May 11, 2020 by jdesrosiers
4
Make evaluation with/against language consistent. clarification Items that need to be clarified in the specification Priority: Low
#922 opened May 15, 2020 by handrews stable-release
5
Need terminology for a set of linked or embedded schema resources core
#935 opened May 22, 2020 by handrews
Add keyword id to output unit
#1065 opened Jan 15, 2021 by jdesrosiers
27
Suggestion: String JSON Schemas as shortcut for $ref core proposal Initial discussion of a new idea. A project will be created once a proposal document is created. Type: Enhancement
#1078 opened Feb 27, 2021 by moander
13
Linter
#1079 opened Mar 16, 2021 by ksze
@Relequestual
12
enum keyword was relaxed in draft5, metaschemas not updated
#1601 opened May 2, 2025 by jeremyfiel
1
ProTip! Follow long discussions with comments:>50.