<!DOCTYPE html>
<html lang="en" class="Internet-Draft">
<head>
<meta charset="utf-8">
<meta content="Common,Latin" name="scripts">
<meta content="initial-scale=1.0" name="viewport">
<title>JSON Schema Validation: A Vocabulary for Structural Validation of JSON</title>
<meta content="Austin Wright" name="author">
<meta content="Henry Andrews" name="author">
<meta content="Ben Hutton" name="author">
<meta content="
JSON Schema (application/schema+json) has several purposes, one of which is JSON
instance validation.
This document specifies a vocabulary for JSON Schema to describe the meaning of JSON
documents, provide hints for user interfaces working with JSON data, and to make
assertions about what a valid document must look like.
" name="description">
<meta content="xml2rfc 3.12.2" name="generator">
<meta content="JSON" name="keyword">
<meta content="Schema" name="keyword">
<meta content="validation" name="keyword">
<meta content="draft-bhutton-json-schema-validation-01" name="ietf.draft">
<!-- Generator version information:
xml2rfc 3.12.2
Python 3.9.4
appdirs 1.4.4
ConfigArgParse 1.5.3
google-i18n-address 2.5.0
html5lib 1.1
intervaltree 3.1.0
Jinja2 2.11.3
kitchen 1.2.6
lxml 4.8.0
pycountry 22.1.10
pyflakes 2.4.0
PyYAML 6.0
requests 2.25.1
setuptools 49.2.1
six 1.15.0
-->
<link href="jsonschema-validation.xml" rel="alternate" type="application/rfc+xml">
<link href="#copyright" rel="license">
<style type="text/css">/*
NOTE: Changes at the bottom of this file overrides some earlier settings.
Once the style has stabilized and has been adopted as an official RFC style,
this can be consolidated so that style settings occur only in one place, but
for now the contents of this file consists first of the initial CSS work as
provided to the RFC Formatter (xml2rfc) work, followed by itemized and
commented changes found necssary during the development of the v3
formatters.
*/
/* fonts */
@import url('https://fonts.googleapis.com/css?family=Noto+Sans'); /* Sans-serif */
@import url('https://fonts.googleapis.com/css?family=Noto+Serif'); /* Serif (print) */
@import url('https://fonts.googleapis.com/css?family=Roboto+Mono'); /* Monospace */
@viewport {
zoom: 1.0;
width: extend-to-zoom;
}
@-ms-viewport {
width: extend-to-zoom;
zoom: 1.0;
}
/* general and mobile first */
html {
}
body {
max-width: 90%;
margin: 1.5em auto;
color: #222;
background-color: #fff;
font-size: 14px;
font-family: 'Noto Sans', Arial, Helvetica, sans-serif;
line-height: 1.6;
scroll-behavior: smooth;
}
.ears {
display: none;
}
/* headings */
#title, h1, h2, h3, h4, h5, h6 {
margin: 1em 0 0.5em;
font-weight: bold;
line-height: 1.3;
}
#title {
clear: both;
border-bottom: 1px solid #ddd;
margin: 0 0 0.5em 0;
padding: 1em 0 0.5em;
}
.author {
padding-bottom: 4px;
}
h1 {
font-size: 26px;
margin: 1em 0;
}
h2 {
font-size: 22px;
margin-top: -20px; /* provide offset for in-page anchors */
padding-top: 33px;
}
h3 {
font-size: 18px;
margin-top: -36px; /* provide offset for in-page anchors */
padding-top: 42px;
}
h4 {
font-size: 16px;
margin-top: -36px; /* provide offset for in-page anchors */
padding-top: 42px;
}
h5, h6 {
font-size: 14px;
}
#n-copyright-notice {
border-bottom: 1px solid #ddd;
padding-bottom: 1em;
margin-bottom: 1em;
}
/* general structure */
p {
padding: 0;
margin: 0 0 1em 0;
text-align: left;
}
div, span {
position: relative;
}
div {
margin: 0;
}
.alignRight.art-text {
background-color: #f9f9f9;
border: 1px solid #eee;
border-radius: 3px;
padding: 1em 1em 0;
margin-bottom: 1.5em;
}
.alignRight.art-text pre {
padding: 0;
}
.alignRight {
margin: 1em 0;
}
.alignRight > *:first-child {
border: none;
margin: 0;
float: right;
clear: both;
}
.alignRight > *:nth-child(2) {
clear: both;
display: block;
border: none;
}
svg {
display: block;
}
.alignCenter.art-text {
background-color: #f9f9f9;
border: 1px solid #eee;
border-radius: 3px;
padding: 1em 1em 0;
margin-bottom: 1.5em;
}
.alignCenter.art-text pre {
padding: 0;
}
.alignCenter {
margin: 1em 0;
}
.alignCenter > *:first-child {
border: none;
/* this isn't optimal, but it's an existence proof. PrinceXML doesn't
support flexbox yet.
*/
display: table;
margin: 0 auto;
}
/* lists */
ol, ul {
padding: 0;
margin: 0 0 1em 2em;
}
ol ol, ul ul, ol ul, ul ol {
margin-left: 1em;
}
li {
margin: 0 0 0.25em 0;
}
.ulCompact li {
margin: 0;
}
ul.empty, .ulEmpty {
list-style-type: none;
}
ul.empty li, .ulEmpty li {
margin-top: 0.5em;
}
ul.ulBare, li.ulBare {
margin-left: 0em !important;
}
ul.compact, .ulCompact,
ol.compact, .olCompact {
line-height: 100%;
margin: 0 0 0 2em;
}
/* definition lists */
dl {
}
dl > dt {
float: left;
margin-right: 1em;
}
/*
dl.nohang > dt {
float: none;
}
*/
dl > dd {
margin-bottom: .8em;
min-height: 1.3em;
}
dl.compact > dd, .dlCompact > dd {
margin-bottom: 0em;
}
dl > dd > dl {
margin-top: 0.5em;
margin-bottom: 0em;
}
/* links */
a {
text-decoration: none;
}
a[href] {
color: #22e; /* Arlen: WCAG 2019 */
}
a[href]:hover {
background-color: #f2f2f2;
}
figcaption a[href],
a[href].selfRef {
color: #222;
}
/* XXX probably not this:
a.selfRef:hover {
background-color: transparent;
cursor: default;
} */
/* Figures */
tt, code, pre, code {
background-color: #f9f9f9;
font-family: 'Roboto Mono', monospace;
}
pre {
border: 1px solid #eee;
margin: 0;
padding: 1em;
}
img {
max-width: 100%;
}
figure {
margin: 0;
}
figure blockquote {
margin: 0.8em 0.4em 0.4em;
}
figcaption {
font-style: italic;
margin: 0 0 1em 0;
}
@media screen {
pre {
overflow-x: auto;
max-width: 100%;
max-width: calc(100% - 22px);
}
}
/* aside, blockquote */
aside, blockquote {
margin-left: 0;
padding: 1.2em 2em;
}
blockquote {
background-color: #f9f9f9;
color: #111; /* Arlen: WCAG 2019 */
border: 1px solid #ddd;
border-radius: 3px;
margin: 1em 0;
}
cite {
display: block;
text-align: right;
font-style: italic;
}
/* tables */
table {
width: 100%;
margin: 0 0 1em;
border-collapse: collapse;
border: 1px solid #eee;
}
th, td {
text-align: left;
vertical-align: top;
padding: 0.5em 0.75em;
}
th {
text-align: left;
background-color: #e9e9e9;
}
tr:nth-child(2n+1) > td {
background-color: #f5f5f5;
}
table caption {
font-style: italic;
margin: 0;
padding: 0;
text-align: left;
}
table p {
/* XXX to avoid bottom margin on table row signifiers. If paragraphs should
be allowed within tables more generally, it would be far better to select on a class. */
margin: 0;
}
/* pilcrow */
a.pilcrow {
color: #666; /* Arlen: AHDJ 2019 */
text-decoration: none;
visibility: hidden;
user-select: none;
-ms-user-select: none;
-o-user-select:none;
-moz-user-select: none;
-khtml-user-select: none;
-webkit-user-select: none;
-webkit-touch-callout: none;
}
@media screen {
aside:hover > a.pilcrow,
p:hover > a.pilcrow,
blockquote:hover > a.pilcrow,
div:hover > a.pilcrow,
li:hover > a.pilcrow,
pre:hover > a.pilcrow {
visibility: visible;
}
a.pilcrow:hover {
background-color: transparent;
}
}
/* misc */
hr {
border: 0;
border-top: 1px solid #eee;
}
.bcp14 {
font-variant: small-caps;
}
.role {
font-variant: all-small-caps;
}
/* info block */
#identifiers {
margin: 0;
font-size: 0.9em;
}
#identifiers dt {
width: 3em;
clear: left;
}
#identifiers dd {
float: left;
margin-bottom: 0;
}
/* Fix PDF info block run off issue */
@media print {
#identifiers dd {
float: none;
}
}
#identifiers .authors .author {
display: inline-block;
margin-right: 1.5em;
}
#identifiers .authors .org {
font-style: italic;
}
/* The prepared/rendered info at the very bottom of the page */
.docInfo {
color: #666; /* Arlen: WCAG 2019 */
font-size: 0.9em;
font-style: italic;
margin-top: 2em;
}
.docInfo .prepared {
float: left;
}
.docInfo .prepared {
float: right;
}
/* table of contents */
#toc {
padding: 0.75em 0 2em 0;
margin-bottom: 1em;
}
nav.toc ul {
margin: 0 0.5em 0 0;
padding: 0;
list-style: none;
}
nav.toc li {
line-height: 1.3em;
margin: 0.75em 0;
padding-left: 1.2em;
text-indent: -1.2em;
}
/* references */
.references dt {
text-align: right;
font-weight: bold;
min-width: 7em;
}
.references dd {
margin-left: 8em;
overflow: auto;
}
.refInstance {
margin-bottom: 1.25em;
}
.references .ascii {
margin-bottom: 0.25em;
}
/* index */
.index ul {
margin: 0 0 0 1em;
padding: 0;
list-style: none;
}
.index ul ul {
margin: 0;
}
.index li {
margin: 0;
text-indent: -2em;
padding-left: 2em;
padding-bottom: 5px;
}
.indexIndex {
margin: 0.5em 0 1em;
}
.index a {
font-weight: 700;
}
/* make the index two-column on all but the smallest screens */
@media (min-width: 600px) {
.index ul {
-moz-column-count: 2;
-moz-column-gap: 20px;
}
.index ul ul {
-moz-column-count: 1;
-moz-column-gap: 0;
}
}
/* authors */
address.vcard {
font-style: normal;
margin: 1em 0;
}
address.vcard .nameRole {
font-weight: 700;
margin-left: 0;
}
address.vcard .label {
font-family: "Noto Sans",Arial,Helvetica,sans-serif;
margin: 0.5em 0;
}
address.vcard .type {
display: none;
}
.alternative-contact {
margin: 1.5em 0 1em;
}
hr.addr {
border-top: 1px dashed;
margin: 0;
color: #ddd;
max-width: calc(100% - 16px);
}
/* temporary notes */
.rfcEditorRemove::before {
position: absolute;
top: 0.2em;
right: 0.2em;
padding: 0.2em;
content: "The RFC Editor will remove this note";
color: #9e2a00; /* Arlen: WCAG 2019 */
background-color: #ffd; /* Arlen: WCAG 2019 */
}
.rfcEditorRemove {
position: relative;
padding-top: 1.8em;
background-color: #ffd; /* Arlen: WCAG 2019 */
border-radius: 3px;
}
.cref {
background-color: #ffd; /* Arlen: WCAG 2019 */
padding: 2px 4px;
}
.crefSource {
font-style: italic;
}
/* alternative layout for smaller screens */
@media screen and (max-width: 1023px) {
body {
padding-top: 2em;
}
#title {
padding: 1em 0;
}
h1 {
font-size: 24px;
}
h2 {
font-size: 20px;
margin-top: -18px; /* provide offset for in-page anchors */
padding-top: 38px;
}
#identifiers dd {
max-width: 60%;
}
#toc {
position: fixed;
z-index: 2;
top: 0;
right: 0;
padding: 0;
margin: 0;
background-color: inherit;
border-bottom: 1px solid #ccc;
}
#toc h2 {
margin: -1px 0 0 0;
padding: 4px 0 4px 6px;
padding-right: 1em;
min-width: 190px;
font-size: 1.1em;
text-align: right;
background-color: #444;
color: white;
cursor: pointer;
}
#toc h2::before { /* css hamburger */
float: right;
position: relative;
width: 1em;
height: 1px;
left: -164px;
margin: 6px 0 0 0;
background: white none repeat scroll 0 0;
box-shadow: 0 4px 0 0 white, 0 8px 0 0 white;
content: "";
}
#toc nav {
display: none;
padding: 0.5em 1em 1em;
overflow: auto;
height: calc(100vh - 48px);
border-left: 1px solid #ddd;
}
}
/* alternative layout for wide screens */
@media screen and (min-width: 1024px) {
body {
max-width: 724px;
margin: 42px auto;
padding-left: 1.5em;
padding-right: 29em;
}
#toc {
position: fixed;
top: 42px;
right: 42px;
width: 25%;
margin: 0;
padding: 0 1em;
z-index: 1;
}
#toc h2 {
border-top: none;
border-bottom: 1px solid #ddd;
font-size: 1em;
font-weight: normal;
margin: 0;
padding: 0.25em 1em 1em 0;
}
#toc nav {
display: block;
height: calc(90vh - 84px);
bottom: 0;
padding: 0.5em 0 0;
overflow: auto;
}
img { /* future proofing */
max-width: 100%;
height: auto;
}
}
/* pagination */
@media print {
body {
width: 100%;
}
p {
orphans: 3;
widows: 3;
}
#n-copyright-notice {
border-bottom: none;
}
#toc, #n-introduction {
page-break-before: always;
}
#toc {
border-top: none;
padding-top: 0;
}
figure, pre {
page-break-inside: avoid;
}
figure {
overflow: scroll;
}
h1, h2, h3, h4, h5, h6 {
page-break-after: avoid;
}
h2+*, h3+*, h4+*, h5+*, h6+* {
page-break-before: avoid;
}
pre {
white-space: pre-wrap;
word-wrap: break-word;
font-size: 10pt;
}
table {
border: 1px solid #ddd;
}
td {
border-top: 1px solid #ddd;
}
}
/* This is commented out here, as the string-set: doesn't
pass W3C validation currently */
/*
.ears thead .left {
string-set: ears-top-left content();
}
.ears thead .center {
string-set: ears-top-center content();
}
.ears thead .right {
string-set: ears-top-right content();
}
.ears tfoot .left {
string-set: ears-bottom-left content();
}
.ears tfoot .center {
string-set: ears-bottom-center content();
}
.ears tfoot .right {
string-set: ears-bottom-right content();
}
*/
@page :first {
padding-top: 0;
@top-left {
content: normal;
border: none;
}
@top-center {
content: normal;
border: none;
}
@top-right {
content: normal;
border: none;
}
}
@page {
size: A4;
margin-bottom: 45mm;
padding-top: 20px;
/* The follwing is commented out here, but set appropriately by in code, as
the content depends on the document */
/*
@top-left {
content: 'Internet-Draft';
vertical-align: bottom;
border-bottom: solid 1px #ccc;
}
@top-left {
content: string(ears-top-left);
vertical-align: bottom;
border-bottom: solid 1px #ccc;
}
@top-center {
content: string(ears-top-center);
vertical-align: bottom;
border-bottom: solid 1px #ccc;
}
@top-right {
content: string(ears-top-right);
vertical-align: bottom;
border-bottom: solid 1px #ccc;
}
@bottom-left {
content: string(ears-bottom-left);
vertical-align: top;
border-top: solid 1px #ccc;
}
@bottom-center {
content: string(ears-bottom-center);
vertical-align: top;
border-top: solid 1px #ccc;
}
@bottom-right {
content: '[Page ' counter(page) ']';
vertical-align: top;
border-top: solid 1px #ccc;
}
*/
}
/* Changes introduced to fix issues found during implementation */
/* Make sure links are clickable even if overlapped by following H* */
a {
z-index: 2;
}
/* Separate body from document info even without intervening H1 */
section {
clear: both;
}
/* Top align author divs, to avoid names without organization dropping level with org names */
.author {
vertical-align: top;
}
/* Leave room in document info to show Internet-Draft on one line */
#identifiers dt {
width: 8em;
}
/* Don't waste quite as much whitespace between label and value in doc info */
#identifiers dd {
margin-left: 1em;
}
/* Give floating toc a background color (needed when it's a div inside section */
#toc {
background-color: white;
}
/* Make the collapsed ToC header render white on gray also when it's a link */
@media screen and (max-width: 1023px) {
#toc h2 a,
#toc h2 a:link,
#toc h2 a:focus,
#toc h2 a:hover,
#toc a.toplink,
#toc a.toplink:hover {
color: white;
background-color: #444;
text-decoration: none;
}
}
/* Give the bottom of the ToC some whitespace */
@media screen and (min-width: 1024px) {
#toc {
padding: 0 0 1em 1em;
}
}
/* Style section numbers with more space between number and title */
.section-number {
padding-right: 0.5em;
}
/* prevent monospace from becoming overly large */
tt, code, pre, code {
font-size: 95%;
}
/* Fix the height/width aspect for ascii art*/
pre.sourcecode,
.art-text pre {
line-height: 1.12;
}
/* Add styling for a link in the ToC that points to the top of the document */
a.toplink {
float: right;
margin-right: 0.5em;
}
/* Fix the dl styling to match the RFC 7992 attributes */
dl > dt,
dl.dlParallel > dt {
float: left;
margin-right: 1em;
}
dl.dlNewline > dt {
float: none;
}
/* Provide styling for table cell text alignment */
table td.text-left,
table th.text-left {
text-align: left;
}
table td.text-center,
table th.text-center {
text-align: center;
}
table td.text-right,
table th.text-right {
text-align: right;
}
/* Make the alternative author contact informatio look less like just another
author, and group it closer with the primary author contact information */
.alternative-contact {
margin: 0.5em 0 0.25em 0;
}
address .non-ascii {
margin: 0 0 0 2em;
}
/* With it being possible to set tables with alignment
left, center, and right, { width: 100%; } does not make sense */
table {
width: auto;
}
/* Avoid reference text that sits in a block with very wide left margin,
because of a long floating dt label.*/
.references dd {
overflow: visible;
}
/* Control caption placement */
caption {
caption-side: bottom;
}
/* Limit the width of the author address vcard, so names in right-to-left
script don't end up on the other side of the page. */
address.vcard {
max-width: 30em;
margin-right: auto;
}
/* For address alignment dependent on LTR or RTL scripts */
address div.left {
text-align: left;
}
address div.right {
text-align: right;
}
/* Provide table alignment support. We can't use the alignX classes above
since they do unwanted things with caption and other styling. */
table.right {
margin-left: auto;
margin-right: 0;
}
table.center {
margin-left: auto;
margin-right: auto;
}
table.left {
margin-left: 0;
margin-right: auto;
}
/* Give the table caption label the same styling as the figcaption */
caption a[href] {
color: #222;
}
@media print {
.toplink {
display: none;
}
/* avoid overwriting the top border line with the ToC header */
#toc {
padding-top: 1px;
}
/* Avoid page breaks inside dl and author address entries */
.vcard {
page-break-inside: avoid;
}
}
/* Tweak the bcp14 keyword presentation */
.bcp14 {
font-variant: small-caps;
font-weight: bold;
font-size: 0.9em;
}
/* Tweak the invisible space above H* in order not to overlay links in text above */
h2 {
margin-top: -18px; /* provide offset for in-page anchors */
padding-top: 31px;
}
h3 {
margin-top: -18px; /* provide offset for in-page anchors */
padding-top: 24px;
}
h4 {
margin-top: -18px; /* provide offset for in-page anchors */
padding-top: 24px;
}
/* Float artwork pilcrow to the right */
@media screen {
.artwork a.pilcrow {
display: block;
line-height: 0.7;
margin-top: 0.15em;
}
}
/* Make pilcrows on dd visible */
@media screen {
dd:hover > a.pilcrow {
visibility: visible;
}
}
/* Make the placement of figcaption match that of a table's caption
by removing the figure's added bottom margin */
.alignLeft.art-text,
.alignCenter.art-text,
.alignRight.art-text {
margin-bottom: 0;
}
.alignLeft,
.alignCenter,
.alignRight {
margin: 1em 0 0 0;
}
/* In print, the pilcrow won't show on hover, so prevent it from taking up space,
possibly even requiring a new line */
@media print {
a.pilcrow {
display: none;
}
}
/* Styling for the external metadata */
div#external-metadata {
background-color: #eee;
padding: 0.5em;
margin-bottom: 0.5em;
display: none;
}
div#internal-metadata {
padding: 0.5em; /* to match the external-metadata padding */
}
/* Styling for title RFC Number */
h1#rfcnum {
clear: both;
margin: 0 0 -1em;
padding: 1em 0 0 0;
}
/* Make .olPercent look the same as <ol><li> */
dl.olPercent > dd {
margin-bottom: 0.25em;
min-height: initial;
}
/* Give aside some styling to set it apart */
aside {
border-left: 1px solid #ddd;
margin: 1em 0 1em 2em;
padding: 0.2em 2em;
}
aside > dl,
aside > ol,
aside > ul,
aside > table,
aside > p {
margin-bottom: 0.5em;
}
/* Additional page break settings */
@media print {
figcaption, table caption {
page-break-before: avoid;
}
}
/* Font size adjustments for print */
@media print {
body { font-size: 10pt; line-height: normal; max-width: 96%; }
h1 { font-size: 1.72em; padding-top: 1.5em; } /* 1*1.2*1.2*1.2 */
h2 { font-size: 1.44em; padding-top: 1.5em; } /* 1*1.2*1.2 */
h3 { font-size: 1.2em; padding-top: 1.5em; } /* 1*1.2 */
h4 { font-size: 1em; padding-top: 1.5em; }
h5, h6 { font-size: 1em; margin: initial; padding: 0.5em 0 0.3em; }
}
/* Sourcecode margin in print, when there's no pilcrow */
@media print {
.artwork,
.sourcecode {
margin-bottom: 1em;
}
}
/* Avoid narrow tables forcing too narrow table captions, which may render badly */
table {
min-width: 20em;
}
/* ol type a */
ol.type-a { list-style-type: lower-alpha; }
ol.type-A { list-style-type: upper-alpha; }
ol.type-i { list-style-type: lower-roman; }
ol.type-I { list-style-type: lower-roman; }
/* Apply the print table and row borders in general, on request from the RPC,
and increase the contrast between border and odd row background sligthtly */
table {
border: 1px solid #ddd;
}
td {
border-top: 1px solid #ddd;
}
tr:nth-child(2n+1) > td {
background-color: #f8f8f8;
}
/* Use style rules to govern display of the TOC. */
@media screen and (max-width: 1023px) {
#toc nav { display: none; }
#toc.active nav { display: block; }
}
/* Add support for keepWithNext */
.keepWithNext {
break-after: avoid-page;
break-after: avoid-page;
}
/* Add support for keepWithPrevious */
.keepWithPrevious {
break-before: avoid-page;
}
/* Change the approach to avoiding breaks inside artwork etc. */
figure, pre, table, .artwork, .sourcecode {
break-before: auto;
break-after: auto;
}
/* Avoid breaks between <dt> and <dd> */
dl {
break-before: auto;
break-inside: auto;
}
dt {
break-before: auto;
break-after: avoid-page;
}
dd {
break-before: avoid-page;
break-after: auto;
orphans: 3;
widows: 3
}
span.break, dd.break {
margin-bottom: 0;
min-height: 0;
break-before: auto;
break-inside: auto;
break-after: auto;
}
/* Undo break-before ToC */
@media print {
#toc {
break-before: auto;
}
}
/* Text in compact lists should not get extra bottim margin space,
since that would makes the list not compact */
ul.compact p, .ulCompact p,
ol.compact p, .olCompact p {
margin: 0;
}
/* But the list as a whole needs the extra space at the end */
section ul.compact,
section .ulCompact,
section ol.compact,
section .olCompact {
margin-bottom: 1em; /* same as p not within ul.compact etc. */
}
/* The tt and code background above interferes with for instance table cell
backgrounds. Changed to something a bit more selective. */
tt, code {
background-color: transparent;
}
p tt, p code, li tt, li code {
background-color: #f8f8f8;
}
/* Tweak the pre margin -- 0px doesn't come out well */
pre {
margin-top: 0.5px;
}
/* Tweak the comact list text */
ul.compact, .ulCompact,
ol.compact, .olCompact,
dl.compact, .dlCompact {
line-height: normal;
}
/* Don't add top margin for nested lists */
li > ul, li > ol, li > dl,
dd > ul, dd > ol, dd > dl,
dl > dd > dl {
margin-top: initial;
}
/* Elements that should not be rendered on the same line as a <dt> */
/* This should match the element list in writer.text.TextWriter.render_dl() */
dd > div.artwork:first-child,
dd > aside:first-child,
dd > figure:first-child,
dd > ol:first-child,
dd > div:first-child > pre.sourcecode,
dd > table:first-child,
dd > ul:first-child {
clear: left;
}
/* fix for weird browser behaviour when <dd/> is empty */
dt+dd:empty::before{
content: "\00a0";
}
/* Make paragraph spacing inside <li> smaller than in body text, to fit better within the list */
li > p {
margin-bottom: 0.5em
}
/* Don't let p margin spill out from inside list items */
li > p:last-of-type {
margin-bottom: 0;
}
</style>
<link href="rfc-local.css" rel="stylesheet" type="text/css">
<script type="application/javascript">async function addMetadata(){try{const e=document.styleSheets[0].cssRules;for(let t=0;t<e.length;t++)if(/#identifiers/.exec(e[t].selectorText)){const a=e[t].cssText.replace("#identifiers","#external-updates");document.styleSheets[0].insertRule(a,document.styleSheets[0].cssRules.length)}}catch(e){console.log(e)}const e=document.getElementById("external-metadata");if(e)try{var t,a="",o=function(e){const t=document.getElementsByTagName("meta");for(let a=0;a<t.length;a++)if(t[a].getAttribute("name")===e)return t[a].getAttribute("content");return""}("rfc.number");if(o){t="https://www.rfc-editor.org/rfc/rfc"+o+".json";try{const e=await fetch(t);a=await e.json()}catch(e){t=document.URL.indexOf("html")>=0?document.URL.replace(/html$/,"json"):document.URL+".json";const o=await fetch(t);a=await o.json()}}if(!a)return;e.style.display="block";const s="",d="https://datatracker.ietf.org/doc",n="https://datatracker.ietf.org/ipr/search",c="https://www.rfc-editor.org/info",l=a.doc_id.toLowerCase(),i=a.doc_id.slice(0,3).toLowerCase(),f=a.doc_id.slice(3).replace(/^0+/,""),u={status:"Status",obsoletes:"Obsoletes",obsoleted_by:"Obsoleted By",updates:"Updates",updated_by:"Updated By",see_also:"See Also",errata_url:"Errata"};let h="<dl style='overflow:hidden' id='external-updates'>";["status","obsoletes","obsoleted_by","updates","updated_by","see_also","errata_url"].forEach(e=>{if("status"==e){a[e]=a[e].toLowerCase();var t=a[e].split(" "),o=t.length,w="",p=1;for(let e=0;e<o;e++)p<o?w=w+r(t[e])+" ":w+=r(t[e]),p++;a[e]=w}else if("obsoletes"==e||"obsoleted_by"==e||"updates"==e||"updated_by"==e){var g,m="",b=1;g=a[e].length;for(let t=0;t<g;t++)a[e][t]&&(a[e][t]=String(a[e][t]).toLowerCase(),m=b<g?m+"<a href='"+s+"/rfc/".concat(a[e][t])+"'>"+a[e][t].slice(3)+"</a>, ":m+"<a href='"+s+"/rfc/".concat(a[e][t])+"'>"+a[e][t].slice(3)+"</a>",b++);a[e]=m}else if("see_also"==e){var y,L="",C=1;y=a[e].length;for(let t=0;t<y;t++)if(a[e][t]){a[e][t]=String(a[e][t]);var _=a[e][t].slice(0,3),v=a[e][t].slice(3).replace(/^0+/,"");L=C<y?"RFC"!=_?L+"<a href='"+s+"/info/"+_.toLowerCase().concat(v.toLowerCase())+"'>"+_+" "+v+"</a>, ":L+"<a href='"+s+"/info/"+_.toLowerCase().concat(v.toLowerCase())+"'>"+v+"</a>, ":"RFC"!=_?L+"<a href='"+s+"/info/"+_.toLowerCase().concat(v.toLowerCase())+"'>"+_+" "+v+"</a>":L+"<a href='"+s+"/info/"+_.toLowerCase().concat(v.toLowerCase())+"'>"+v+"</a>",C++}a[e]=L}else if("errata_url"==e){var R="";R=a[e]?R+"<a href='"+a[e]+"'>Errata exist</a> | <a href='"+d+"/"+l+"'>Datatracker</a>| <a href='"+n+"/?"+i+"="+f+"&submit="+i+"'>IPR</a> | <a href='"+c+"/"+l+"'>Info page</a>":"<a href='"+d+"/"+l+"'>Datatracker</a> | <a href='"+n+"/?"+i+"="+f+"&submit="+i+"'>IPR</a> | <a href='"+c+"/"+l+"'>Info page</a>",a[e]=R}""!=a[e]?"Errata"==u[e]?h+=`<dt>More info:</dt><dd>${a[e]}</dd>`:h+=`<dt>${u[e]}:</dt><dd>${a[e]}</dd>`:"Errata"==u[e]&&(h+=`<dt>More info:</dt><dd>${a[e]}</dd>`)}),h+="</dl>",e.innerHTML=h}catch(e){console.log(e)}else console.log("Could not locate metadata <div> element");function r(e){return e.charAt(0).toUpperCase()+e.slice(1)}}window.removeEventListener("load",addMetadata),window.addEventListener("load",addMetadata);</script>
</head>
<body>
<script src="metadata.min.js"></script>
<table class="ears">
<thead><tr>
<td class="left">Internet-Draft</td>
<td class="center">JSON Schema Validation</td>
<td class="right">June 2022</td>
</tr></thead>
<tfoot><tr>
<td class="left">Wright, et al.</td>
<td class="center">Expires 18 December 2022</td>
<td class="right">[Page]</td>
</tr></tfoot>
</table>
<div id="external-metadata" class="document-information"></div>
<div id="internal-metadata" class="document-information">
<dl id="identifiers">
<dt class="label-workgroup">Workgroup:</dt>
<dd class="workgroup">Internet Engineering Task Force</dd>
<dt class="label-internet-draft">Internet-Draft:</dt>
<dd class="internet-draft">draft-bhutton-json-schema-validation-01</dd>
<dt class="label-published">Published:</dt>
<dd class="published">
<time datetime="2022-06-16" class="published">16 June 2022</time>
</dd>
<dt class="label-intended-status">Intended Status:</dt>
<dd class="intended-status">Informational</dd>
<dt class="label-expires">Expires:</dt>
<dd class="expires"><time datetime="2022-12-18">18 December 2022</time></dd>
<dt class="label-authors">Authors:</dt>
<dd class="authors">
<div class="author">
<div class="author-name">A. Wright, <span class="editor">Ed.</span>
</div>
</div>
<div class="author">
<div class="author-name">H. Andrews, <span class="editor">Ed.</span>
</div>
</div>
<div class="author">
<div class="author-name">B. Hutton, <span class="editor">Ed.</span>
</div>
<div class="org">Postman</div>
</div>
</dd>
</dl>
</div>
<h1 id="title">JSON Schema Validation: A Vocabulary for Structural Validation of JSON</h1>
<section id="section-abstract">
<h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2>
<p id="section-abstract-1">
JSON Schema (application/schema+json) has several purposes, one of which is JSON
instance validation.
This document specifies a vocabulary for JSON Schema to describe the meaning of JSON
documents, provide hints for user interfaces working with JSON data, and to make
assertions about what a valid document must look like.<a href="#section-abstract-1" class="pilcrow">¶</a></p>
</section>
<section class="note" id="section-note.1">
<h2 id="name-note-to-readers">
<a href="#name-note-to-readers" class="section-name selfRef">Note to Readers</a>
</h2>
<p id="section-note.1-1">
The issues list for this draft can be found at
<span><a href="https://github.com/json-schema-org/json-schema-spec/issues">https://github.com/json-schema-org/json-schema-spec/issues</a></span>.<a href="#section-note.1-1" class="pilcrow">¶</a></p>
<p id="section-note.1-2">
For additional information, see <span><a href="https://json-schema.org/">https://json-schema.org/</a></span>.<a href="#section-note.1-2" class="pilcrow">¶</a></p>
<p id="section-note.1-3">
To provide feedback, use this issue tracker, the communication methods listed on the
homepage, or email the document editors.<a href="#section-note.1-3" class="pilcrow">¶</a></p>
</section>
<div id="status-of-memo">
<section id="section-boilerplate.1">
<h2 id="name-status-of-this-memo">
<a href="#name-status-of-this-memo" class="section-name selfRef">Status of This Memo</a>
</h2>
<p id="section-boilerplate.1-1">
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.<a href="#section-boilerplate.1-1" class="pilcrow">¶</a></p>
<p id="section-boilerplate.1-2">
Internet-Drafts are working documents of the Internet Engineering Task
Force (IETF). Note that other groups may also distribute working
documents as Internet-Drafts. The list of current Internet-Drafts is
at <span><a href="https://datatracker.ietf.org/drafts/current/">https://datatracker.ietf.org/drafts/current/</a></span>.<a href="#section-boilerplate.1-2" class="pilcrow">¶</a></p>
<p id="section-boilerplate.1-3">
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p>
<p id="section-boilerplate.1-4">
This Internet-Draft will expire on 18 December 2022.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
</section>
</div>
<div id="copyright">
<section id="section-boilerplate.2">
<h2 id="name-copyright-notice">
<a href="#name-copyright-notice" class="section-name selfRef">Copyright Notice</a>
</h2>
<p id="section-boilerplate.2-1">
Copyright (c) 2022 IETF Trust and the persons identified as the
document authors. All rights reserved.<a href="#section-boilerplate.2-1" class="pilcrow">¶</a></p>
<p id="section-boilerplate.2-2">
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<span><a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a></span>) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this
document must include Revised BSD License text as described in
Section 4.e of the Trust Legal Provisions and are provided without
warranty as described in the Revised BSD License.<a href="#section-boilerplate.2-2" class="pilcrow">¶</a></p>
</section>
</div>
<div id="toc">
<section id="section-toc.1">
<a href="#" onclick="scroll(0,0)" class="toplink">▲</a><h2 id="name-table-of-contents">
<a href="#name-table-of-contents" class="section-name selfRef">Table of Contents</a>
</h2>
<nav class="toc"><ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.1">
<p id="section-toc.1-1.1.1" class="keepWithNext"><a href="#section-1" class="xref">1</a>. <a href="#name-introduction" class="xref">Introduction</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2">
<p id="section-toc.1-1.2.1" class="keepWithNext"><a href="#section-2" class="xref">2</a>. <a href="#name-conventions-and-terminology" class="xref">Conventions and Terminology</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3">
<p id="section-toc.1-1.3.1" class="keepWithNext"><a href="#section-3" class="xref">3</a>. <a href="#name-overview" class="xref">Overview</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4">
<p id="section-toc.1-1.4.1"><a href="#section-4" class="xref">4</a>. <a href="#name-interoperability-considerat" class="xref">Interoperability Considerations</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.1">
<p id="section-toc.1-1.4.2.1.1"><a href="#section-4.1" class="xref">4.1</a>. <a href="#name-validation-of-string-instan" class="xref">Validation of String Instances</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.2">
<p id="section-toc.1-1.4.2.2.1"><a href="#section-4.2" class="xref">4.2</a>. <a href="#name-validation-of-numeric-insta" class="xref">Validation of Numeric Instances</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.3">
<p id="section-toc.1-1.4.2.3.1"><a href="#section-4.3" class="xref">4.3</a>. <a href="#name-regular-expressions" class="xref">Regular Expressions</a></p>
</li>
</ul>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5">
<p id="section-toc.1-1.5.1"><a href="#section-5" class="xref">5</a>. <a href="#name-meta-schema" class="xref">Meta-Schema</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6">
<p id="section-toc.1-1.6.1"><a href="#section-6" class="xref">6</a>. <a href="#name-a-vocabulary-for-structural" class="xref">A Vocabulary for Structural Validation</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.1">
<p id="section-toc.1-1.6.2.1.1"><a href="#section-6.1" class="xref">6.1</a>. <a href="#name-validation-keywords-for-any" class="xref">Validation Keywords for Any Instance Type</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.1.2.1">
<p id="section-toc.1-1.6.2.1.2.1.1"><a href="#section-6.1.1" class="xref">6.1.1</a>. <a href="#name-type" class="xref">type</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.1.2.2">
<p id="section-toc.1-1.6.2.1.2.2.1"><a href="#section-6.1.2" class="xref">6.1.2</a>. <a href="#name-enum" class="xref">enum</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.1.2.3">
<p id="section-toc.1-1.6.2.1.2.3.1"><a href="#section-6.1.3" class="xref">6.1.3</a>. <a href="#name-const" class="xref">const</a></p>
</li>
</ul>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.2">
<p id="section-toc.1-1.6.2.2.1"><a href="#section-6.2" class="xref">6.2</a>. <a href="#name-validation-keywords-for-num" class="xref">Validation Keywords for Numeric Instances (number and integer)</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.2.2.1">
<p id="section-toc.1-1.6.2.2.2.1.1"><a href="#section-6.2.1" class="xref">6.2.1</a>. <a href="#name-multipleof" class="xref">multipleOf</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.2.2.2">
<p id="section-toc.1-1.6.2.2.2.2.1"><a href="#section-6.2.2" class="xref">6.2.2</a>. <a href="#name-maximum" class="xref">maximum</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.2.2.3">
<p id="section-toc.1-1.6.2.2.2.3.1"><a href="#section-6.2.3" class="xref">6.2.3</a>. <a href="#name-exclusivemaximum" class="xref">exclusiveMaximum</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.2.2.4">
<p id="section-toc.1-1.6.2.2.2.4.1"><a href="#section-6.2.4" class="xref">6.2.4</a>. <a href="#name-minimum" class="xref">minimum</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.2.2.5">
<p id="section-toc.1-1.6.2.2.2.5.1"><a href="#section-6.2.5" class="xref">6.2.5</a>. <a href="#name-exclusiveminimum" class="xref">exclusiveMinimum</a></p>
</li>
</ul>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.3">
<p id="section-toc.1-1.6.2.3.1"><a href="#section-6.3" class="xref">6.3</a>. <a href="#name-validation-keywords-for-str" class="xref">Validation Keywords for Strings</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.3.2.1">
<p id="section-toc.1-1.6.2.3.2.1.1"><a href="#section-6.3.1" class="xref">6.3.1</a>. <a href="#name-maxlength" class="xref">maxLength</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.3.2.2">
<p id="section-toc.1-1.6.2.3.2.2.1"><a href="#section-6.3.2" class="xref">6.3.2</a>. <a href="#name-minlength" class="xref">minLength</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.3.2.3">
<p id="section-toc.1-1.6.2.3.2.3.1"><a href="#section-6.3.3" class="xref">6.3.3</a>. <a href="#name-pattern" class="xref">pattern</a></p>
</li>
</ul>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.4">
<p id="section-toc.1-1.6.2.4.1"><a href="#section-6.4" class="xref">6.4</a>. <a href="#name-validation-keywords-for-arr" class="xref">Validation Keywords for Arrays</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.4.2.1">
<p id="section-toc.1-1.6.2.4.2.1.1"><a href="#section-6.4.1" class="xref">6.4.1</a>. <a href="#name-maxitems" class="xref">maxItems</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.4.2.2">
<p id="section-toc.1-1.6.2.4.2.2.1"><a href="#section-6.4.2" class="xref">6.4.2</a>. <a href="#name-minitems" class="xref">minItems</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.4.2.3">
<p id="section-toc.1-1.6.2.4.2.3.1"><a href="#section-6.4.3" class="xref">6.4.3</a>. <a href="#name-uniqueitems" class="xref">uniqueItems</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.4.2.4">
<p id="section-toc.1-1.6.2.4.2.4.1"><a href="#section-6.4.4" class="xref">6.4.4</a>. <a href="#name-maxcontains" class="xref">maxContains</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.4.2.5">
<p id="section-toc.1-1.6.2.4.2.5.1"><a href="#section-6.4.5" class="xref">6.4.5</a>. <a href="#name-mincontains" class="xref">minContains</a></p>
</li>
</ul>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.5">
<p id="section-toc.1-1.6.2.5.1"><a href="#section-6.5" class="xref">6.5</a>. <a href="#name-validation-keywords-for-obj" class="xref">Validation Keywords for Objects</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.5.2.1">
<p id="section-toc.1-1.6.2.5.2.1.1"><a href="#section-6.5.1" class="xref">6.5.1</a>. <a href="#name-maxproperties" class="xref">maxProperties</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.5.2.2">
<p id="section-toc.1-1.6.2.5.2.2.1"><a href="#section-6.5.2" class="xref">6.5.2</a>. <a href="#name-minproperties" class="xref">minProperties</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.5.2.3">
<p id="section-toc.1-1.6.2.5.2.3.1"><a href="#section-6.5.3" class="xref">6.5.3</a>. <a href="#name-required" class="xref">required</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.5.2.4">
<p id="section-toc.1-1.6.2.5.2.4.1"><a href="#section-6.5.4" class="xref">6.5.4</a>. <a href="#name-dependentrequired" class="xref">dependentRequired</a></p>
</li>
</ul>
</li>
</ul>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7">
<p id="section-toc.1-1.7.1"><a href="#section-7" class="xref">7</a>. <a href="#name-vocabularies-for-semantic-c" class="xref">Vocabularies for Semantic Content With "format"</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.1">
<p id="section-toc.1-1.7.2.1.1"><a href="#section-7.1" class="xref">7.1</a>. <a href="#name-foreword" class="xref">Foreword</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.2">
<p id="section-toc.1-1.7.2.2.1"><a href="#section-7.2" class="xref">7.2</a>. <a href="#name-implementation-requirements" class="xref">Implementation Requirements</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.2.2.1">
<p id="section-toc.1-1.7.2.2.2.1.1"><a href="#section-7.2.1" class="xref">7.2.1</a>. <a href="#name-format-annotation-vocabular" class="xref">Format-Annotation Vocabulary</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.2.2.2">
<p id="section-toc.1-1.7.2.2.2.2.1"><a href="#section-7.2.2" class="xref">7.2.2</a>. <a href="#name-format-assertion-vocabulary" class="xref">Format-Assertion Vocabulary</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.2.2.3">
<p id="section-toc.1-1.7.2.2.2.3.1"><a href="#section-7.2.3" class="xref">7.2.3</a>. <a href="#name-custom-format-attributes" class="xref">Custom format attributes</a></p>
</li>
</ul>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.3">
<p id="section-toc.1-1.7.2.3.1"><a href="#section-7.3" class="xref">7.3</a>. <a href="#name-defined-formats" class="xref">Defined Formats</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.3.2.1">
<p id="section-toc.1-1.7.2.3.2.1.1"><a href="#section-7.3.1" class="xref">7.3.1</a>. <a href="#name-dates-times-and-duration" class="xref">Dates, Times, and Duration</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.3.2.2">
<p id="section-toc.1-1.7.2.3.2.2.1"><a href="#section-7.3.2" class="xref">7.3.2</a>. <a href="#name-email-addresses" class="xref">Email Addresses</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.3.2.3">
<p id="section-toc.1-1.7.2.3.2.3.1"><a href="#section-7.3.3" class="xref">7.3.3</a>. <a href="#name-hostnames" class="xref">Hostnames</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.3.2.4">
<p id="section-toc.1-1.7.2.3.2.4.1"><a href="#section-7.3.4" class="xref">7.3.4</a>. <a href="#name-ip-addresses" class="xref">IP Addresses</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.3.2.5">
<p id="section-toc.1-1.7.2.3.2.5.1"><a href="#section-7.3.5" class="xref">7.3.5</a>. <a href="#name-resource-identifiers" class="xref">Resource Identifiers</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.3.2.6">
<p id="section-toc.1-1.7.2.3.2.6.1"><a href="#section-7.3.6" class="xref">7.3.6</a>. <a href="#name-uri-template" class="xref">uri-template</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.3.2.7">
<p id="section-toc.1-1.7.2.3.2.7.1"><a href="#section-7.3.7" class="xref">7.3.7</a>. <a href="#name-json-pointers" class="xref">JSON Pointers</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.3.2.8">
<p id="section-toc.1-1.7.2.3.2.8.1"><a href="#section-7.3.8" class="xref">7.3.8</a>. <a href="#name-regex" class="xref">regex</a></p>
</li>
</ul>
</li>
</ul>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8">
<p id="section-toc.1-1.8.1"><a href="#section-8" class="xref">8</a>. <a href="#name-a-vocabulary-for-the-conten" class="xref">A Vocabulary for the Contents of String-Encoded Data</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.1">
<p id="section-toc.1-1.8.2.1.1"><a href="#section-8.1" class="xref">8.1</a>. <a href="#name-foreword-2" class="xref">Foreword</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.2">
<p id="section-toc.1-1.8.2.2.1"><a href="#section-8.2" class="xref">8.2</a>. <a href="#name-implementation-requirements-2" class="xref">Implementation Requirements</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.3">
<p id="section-toc.1-1.8.2.3.1"><a href="#section-8.3" class="xref">8.3</a>. <a href="#name-contentencoding" class="xref">contentEncoding</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.4">
<p id="section-toc.1-1.8.2.4.1"><a href="#section-8.4" class="xref">8.4</a>. <a href="#name-contentmediatype" class="xref">contentMediaType</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.5">
<p id="section-toc.1-1.8.2.5.1"><a href="#section-8.5" class="xref">8.5</a>. <a href="#name-contentschema" class="xref">contentSchema</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.6">
<p id="section-toc.1-1.8.2.6.1"><a href="#section-8.6" class="xref">8.6</a>. <a href="#name-example" class="xref">Example</a></p>
</li>
</ul>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.9">
<p id="section-toc.1-1.9.1"><a href="#section-9" class="xref">9</a>. <a href="#name-a-vocabulary-for-basic-meta" class="xref">A Vocabulary for Basic Meta-Data Annotations</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.9.2.1">
<p id="section-toc.1-1.9.2.1.1"><a href="#section-9.1" class="xref">9.1</a>. <a href="#name-title-and-description" class="xref">"title" and "description"</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.9.2.2">
<p id="section-toc.1-1.9.2.2.1"><a href="#section-9.2" class="xref">9.2</a>. <a href="#name-default" class="xref">"default"</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.9.2.3">
<p id="section-toc.1-1.9.2.3.1"><a href="#section-9.3" class="xref">9.3</a>. <a href="#name-deprecated" class="xref">"deprecated"</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.9.2.4">
<p id="section-toc.1-1.9.2.4.1"><a href="#section-9.4" class="xref">9.4</a>. <a href="#name-readonly-and-writeonly" class="xref">"readOnly" and "writeOnly"</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.9.2.5">
<p id="section-toc.1-1.9.2.5.1"><a href="#section-9.5" class="xref">9.5</a>. <a href="#name-examples" class="xref">"examples"</a></p>
</li>
</ul>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.10">
<p id="section-toc.1-1.10.1"><a href="#section-10" class="xref">10</a>. <a href="#name-security-considerations" class="xref">Security Considerations</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.11">
<p id="section-toc.1-1.11.1"><a href="#section-11" class="xref">11</a>. <a href="#name-references" class="xref">References</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.11.2.1">
<p id="section-toc.1-1.11.2.1.1"><a href="#section-11.1" class="xref">11.1</a>. <a href="#name-normative-references" class="xref">Normative References</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.11.2.2">
<p id="section-toc.1-1.11.2.2.1"><a href="#section-11.2" class="xref">11.2</a>. <a href="#name-informative-references" class="xref">Informative References</a></p>
</li>
</ul>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.12">
<p id="section-toc.1-1.12.1"><a href="#appendix-A" class="xref">Appendix A</a>. <a href="#name-keywords-moved-from-validat" class="xref">Keywords Moved from Validation to Core</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.13">
<p id="section-toc.1-1.13.1"><a href="#appendix-B" class="xref">Appendix B</a>. <a href="#name-acknowledgments" class="xref">Acknowledgments</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.14">
<p id="section-toc.1-1.14.1"><a href="#appendix-C" class="xref">Appendix C</a>. <a href="#name-changelog" class="xref">ChangeLog</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.15">
<p id="section-toc.1-1.15.1"><a href="#appendix-D" class="xref"></a><a href="#name-authors-addresses" class="xref">Authors' Addresses</a></p>
</li>
</ul>
</nav>
</section>
</div>
<section id="section-1">
<h2 id="name-introduction">
<a href="#section-1" class="section-number selfRef">1. </a><a href="#name-introduction" class="section-name selfRef">Introduction</a>
</h2>
<p id="section-1-1">
JSON Schema can be used to require that a given JSON document (an instance)
satisfies a certain number of criteria. These criteria are asserted by using
keywords described in this specification. In addition, a set of keywords
is also defined to assist in interactive user interface instance generation.<a href="#section-1-1" class="pilcrow">¶</a></p>
<p id="section-1-2">
This specification will use the concepts, syntax, and terminology defined
by the <span><a href="#json-schema" class="xref">JSON Schema core</a> [<a href="#json-schema" class="xref">json-schema</a>]</span> specification.<a href="#section-1-2" class="pilcrow">¶</a></p>
</section>
<section id="section-2">
<h2 id="name-conventions-and-terminology">
<a href="#section-2" class="section-number selfRef">2. </a><a href="#name-conventions-and-terminology" class="section-name selfRef">Conventions and Terminology</a>
</h2>
<p id="section-2-1">
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
"SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be
interpreted as described in <span><a href="#RFC2119" class="xref">RFC 2119</a> [<a href="#RFC2119" class="xref">RFC2119</a>]</span>.<a href="#section-2-1" class="pilcrow">¶</a></p>
<p id="section-2-2">
This specification uses the term "container instance" to refer to both array and
object instances. It uses the term "children instances" to refer to array elements
or object member values.<a href="#section-2-2" class="pilcrow">¶</a></p>
<p id="section-2-3">
Elements in an array value are said to be unique if no two elements of this array
are <span><a href="#json-schema" class="xref">equal</a> [<a href="#json-schema" class="xref">json-schema</a>]</span>.<a href="#section-2-3" class="pilcrow">¶</a></p>
</section>
<section id="section-3">
<h2 id="name-overview">
<a href="#section-3" class="section-number selfRef">3. </a><a href="#name-overview" class="section-name selfRef">Overview</a>
</h2>
<p id="section-3-1">
JSON Schema validation asserts constraints on the structure of instance data.
An instance location that satisfies all asserted constraints is then
annotated with any keywords that contain non-assertion information,
such as descriptive metadata and usage hints. If all locations within
the instance satisfy all asserted constraints, then the instance is
said to be valid against the schema.<a href="#section-3-1" class="pilcrow">¶</a></p>
<p id="section-3-2">
Each schema object is independently evaluated against each instance location
to which it applies. This greatly simplifies the implementation requirements
for validators by ensuring that they do not need to maintain state across
the document-wide validation process.<a href="#section-3-2" class="pilcrow">¶</a></p>
<p id="section-3-3">
This specification defines a set of assertion keywords, as well as a small vocabulary
of metadata keywords that can be used to annotate the JSON instance with
useful information. The <a href="#format" class="xref">Section 7</a> keyword is intended primarily
as an annotation, but can optionally be used as an assertion. The
<a href="#content" class="xref">Section 8</a> keywords are annotations for working with documents
embedded as JSON strings.<a href="#section-3-3" class="pilcrow">¶</a></p>
</section>
<section id="section-4">
<h2 id="name-interoperability-considerat">
<a href="#section-4" class="section-number selfRef">4. </a><a href="#name-interoperability-considerat" class="section-name selfRef">Interoperability Considerations</a>
</h2>
<section id="section-4.1">
<h3 id="name-validation-of-string-instan">
<a href="#section-4.1" class="section-number selfRef">4.1. </a><a href="#name-validation-of-string-instan" class="section-name selfRef">Validation of String Instances</a>
</h3>
<p id="section-4.1-1">
It should be noted that the nul character (\u0000) is valid in a JSON string. An
instance to validate may contain a string value with this character, regardless
of the ability of the underlying programming language to deal with such data.<a href="#section-4.1-1" class="pilcrow">¶</a></p>
</section>
<section id="section-4.2">
<h3 id="name-validation-of-numeric-insta">
<a href="#section-4.2" class="section-number selfRef">4.2. </a><a href="#name-validation-of-numeric-insta" class="section-name selfRef">Validation of Numeric Instances</a>
</h3>
<p id="section-4.2-1">
The JSON specification allows numbers with arbitrary precision, and JSON Schema
does not add any such bounds.
This means that numeric instances processed by JSON Schema can be arbitrarily large and/or
have an arbitrarily long decimal part, regardless of the ability of the
underlying programming language to deal with such data.<a href="#section-4.2-1" class="pilcrow">¶</a></p>
</section>
<div id="regexInterop">
<section id="section-4.3">
<h3 id="name-regular-expressions">
<a href="#section-4.3" class="section-number selfRef">4.3. </a><a href="#name-regular-expressions" class="section-name selfRef">Regular Expressions</a>
</h3>
<p id="section-4.3-1">
Keywords that use regular expressions, or constrain the instance value
to be a regular expression, are subject to the interoperability
considerations for regular expressions in the
<span><a href="#json-schema" class="xref">JSON Schema Core</a> [<a href="#json-schema" class="xref">json-schema</a>]</span> specification.<a href="#section-4.3-1" class="pilcrow">¶</a></p>
</section>
</div>
</section>
<div id="meta-schema">
<section id="section-5">
<h2 id="name-meta-schema">
<a href="#section-5" class="section-number selfRef">5. </a><a href="#name-meta-schema" class="section-name selfRef">Meta-Schema</a>
</h2>
<p id="section-5-1">
The current URI for the default JSON Schema dialect meta-schema is
<span><a href="https://json-schema.org/draft/2020-12/schema">https://json-schema.org/draft/2020-12/schema</a></span>.
For schema author convenience, this meta-schema describes a dialect
consisting of all vocabularies
defined in this specification and the JSON Schema Core specification,
as well as two former keywords which are reserved for a transitional period.
Individual vocabulary and vocabulary meta-schema URIs are given for
each section below. Certain vocabularies are optional to support, which
is explained in detail in the relevant sections.<a href="#section-5-1" class="pilcrow">¶</a></p>
<p id="section-5-2">
Updated vocabulary and meta-schema URIs MAY be published between
specification drafts in order to correct errors. Implementations
SHOULD consider URIs dated after this specification draft and
before the next to indicate the same syntax and semantics
as those listed here.<a href="#section-5-2" class="pilcrow">¶</a></p>
</section>
</div>
<section id="section-6">
<h2 id="name-a-vocabulary-for-structural">
<a href="#section-6" class="section-number selfRef">6. </a><a href="#name-a-vocabulary-for-structural" class="section-name selfRef">A Vocabulary for Structural Validation</a>
</h2>
<p id="section-6-1">
Validation keywords in a schema impose requirements for successful validation of an
instance. These keywords are all assertions without any annotation behavior.<a href="#section-6-1" class="pilcrow">¶</a></p>
<p id="section-6-2">
Meta-schemas that do not use "$vocabulary" SHOULD be considered to
require this vocabulary as if its URI were present with a value of true.<a href="#section-6-2" class="pilcrow">¶</a></p>
<p id="section-6-3">
The current URI for this vocabulary, known as the Validation vocabulary, is:
<https://json-schema.org/draft/2020-12/vocab/validation>.<a href="#section-6-3" class="pilcrow">¶</a></p>
<p id="section-6-4">
The current URI for the corresponding meta-schema is:
<span><a href="https://json-schema.org/draft/2020-12/meta/validation">https://json-schema.org/draft/2020-12/meta/validation</a></span>.<a href="#section-6-4" class="pilcrow">¶</a></p>
<div id="general">
<section id="section-6.1">
<h3 id="name-validation-keywords-for-any">
<a href="#section-6.1" class="section-number selfRef">6.1. </a><a href="#name-validation-keywords-for-any" class="section-name selfRef">Validation Keywords for Any Instance Type</a>
</h3>
<section id="section-6.1.1">
<h4 id="name-type">
<a href="#section-6.1.1" class="section-number selfRef">6.1.1. </a><a href="#name-type" class="section-name selfRef">type</a>
</h4>
<p id="section-6.1.1-1">
The value of this keyword MUST be either a string or an array. If it is
an array, elements of the array MUST be strings and MUST be unique.<a href="#section-6.1.1-1" class="pilcrow">¶</a></p>
<p id="section-6.1.1-2">
String values MUST be one of the six primitive types
("null", "boolean", "object", "array", "number", or "string"),
or "integer" which matches any number with a zero fractional part.<a href="#section-6.1.1-2" class="pilcrow">¶</a></p>
<p id="section-6.1.1-3">
If the value of "type" is a string, then an instance validates successfully if
its type matches the type represented by the value of the string.
If the value of "type" is an array, then an instance validates successfully if
its type matches any of the types indicated by the strings in the array.<a href="#section-6.1.1-3" class="pilcrow">¶</a></p>
</section>
<div id="enum">
<section id="section-6.1.2">
<h4 id="name-enum">
<a href="#section-6.1.2" class="section-number selfRef">6.1.2. </a><a href="#name-enum" class="section-name selfRef">enum</a>
</h4>
<p id="section-6.1.2-1">
The value of this keyword MUST be an array. This array SHOULD have at
least one element. Elements in the array SHOULD be unique.<a href="#section-6.1.2-1" class="pilcrow">¶</a></p>
<p id="section-6.1.2-2">
An instance validates successfully against this keyword if its value is
equal to one of the elements in this keyword's array value.<a href="#section-6.1.2-2" class="pilcrow">¶</a></p>
<p id="section-6.1.2-3">
Elements in the array might be of any type, including null.<a href="#section-6.1.2-3" class="pilcrow">¶</a></p>
</section>
</div>
<section id="section-6.1.3">
<h4 id="name-const">
<a href="#section-6.1.3" class="section-number selfRef">6.1.3. </a><a href="#name-const" class="section-name selfRef">const</a>
</h4>
<p id="section-6.1.3-1">
The value of this keyword MAY be of any type, including null.<a href="#section-6.1.3-1" class="pilcrow">¶</a></p>
<p id="section-6.1.3-2">
Use of this keyword is functionally equivalent to an
<span><a href="#enum" class="xref">"enum"</a> (<a href="#enum" class="xref">Section 6.1.2</a>)</span> with a single value.<a href="#section-6.1.3-2" class="pilcrow">¶</a></p>
<p id="section-6.1.3-3">
An instance validates successfully against this keyword if its value is
equal to the value of the keyword.<a href="#section-6.1.3-3" class="pilcrow">¶</a></p>
</section>
</section>
</div>
<div id="numeric">
<section id="section-6.2">
<h3 id="name-validation-keywords-for-num">
<a href="#section-6.2" class="section-number selfRef">6.2. </a><a href="#name-validation-keywords-for-num" class="section-name selfRef">Validation Keywords for Numeric Instances (number and integer)</a>
</h3>
<section id="section-6.2.1">
<h4 id="name-multipleof">
<a href="#section-6.2.1" class="section-number selfRef">6.2.1. </a><a href="#name-multipleof" class="section-name selfRef">multipleOf</a>
</h4>
<p id="section-6.2.1-1">
The value of "multipleOf" MUST be a number, strictly greater than 0.<a href="#section-6.2.1-1" class="pilcrow">¶</a></p>
<p id="section-6.2.1-2">
A numeric instance is valid only if division by this keyword's value results in
an integer.<a href="#section-6.2.1-2" class="pilcrow">¶</a></p>
</section>
<section id="section-6.2.2">
<h4 id="name-maximum">
<a href="#section-6.2.2" class="section-number selfRef">6.2.2. </a><a href="#name-maximum" class="section-name selfRef">maximum</a>
</h4>
<p id="section-6.2.2-1">
The value of "maximum" MUST be a number, representing an inclusive upper limit
for a numeric instance.<a href="#section-6.2.2-1" class="pilcrow">¶</a></p>
<p id="section-6.2.2-2">
If the instance is a number, then this keyword validates only if the instance is
less than or exactly equal to "maximum".<a href="#section-6.2.2-2" class="pilcrow">¶</a></p>
</section>
<section id="section-6.2.3">
<h4 id="name-exclusivemaximum">
<a href="#section-6.2.3" class="section-number selfRef">6.2.3. </a><a href="#name-exclusivemaximum" class="section-name selfRef">exclusiveMaximum</a>
</h4>
<p id="section-6.2.3-1">
The value of "exclusiveMaximum" MUST be a number, representing an exclusive upper
limit for a numeric instance.<a href="#section-6.2.3-1" class="pilcrow">¶</a></p>
<p id="section-6.2.3-2">
If the instance is a number, then the instance is valid only if it has a value
strictly less than (not equal to) "exclusiveMaximum".<a href="#section-6.2.3-2" class="pilcrow">¶</a></p>
</section>
<section id="section-6.2.4">
<h4 id="name-minimum">
<a href="#section-6.2.4" class="section-number selfRef">6.2.4. </a><a href="#name-minimum" class="section-name selfRef">minimum</a>
</h4>
<p id="section-6.2.4-1">
The value of "minimum" MUST be a number, representing an inclusive lower limit
for a numeric instance.<a href="#section-6.2.4-1" class="pilcrow">¶</a></p>
<p id="section-6.2.4-2">
If the instance is a number, then this keyword validates only if the instance is
greater than or exactly equal to "minimum".<a href="#section-6.2.4-2" class="pilcrow">¶</a></p>
</section>
<section id="section-6.2.5">
<h4 id="name-exclusiveminimum">
<a href="#section-6.2.5" class="section-number selfRef">6.2.5. </a><a href="#name-exclusiveminimum" class="section-name selfRef">exclusiveMinimum</a>
</h4>
<p id="section-6.2.5-1">
The value of "exclusiveMinimum" MUST be a number, representing an exclusive lower
limit for a numeric instance.<a href="#section-6.2.5-1" class="pilcrow">¶</a></p>
<p id="section-6.2.5-2">
If the instance is a number, then the instance is valid only if it has a value
strictly greater than (not equal to) "exclusiveMinimum".<a href="#section-6.2.5-2" class="pilcrow">¶</a></p>
</section>
</section>
</div>
<div id="string">
<section id="section-6.3">
<h3 id="name-validation-keywords-for-str">
<a href="#section-6.3" class="section-number selfRef">6.3. </a><a href="#name-validation-keywords-for-str" class="section-name selfRef">Validation Keywords for Strings</a>
</h3>
<section id="section-6.3.1">
<h4 id="name-maxlength">
<a href="#section-6.3.1" class="section-number selfRef">6.3.1. </a><a href="#name-maxlength" class="section-name selfRef">maxLength</a>
</h4>
<p id="section-6.3.1-1">
The value of this keyword MUST be a non-negative integer.<a href="#section-6.3.1-1" class="pilcrow">¶</a></p>
<p id="section-6.3.1-2">
A string instance is valid against this keyword if its
length is less than, or equal to, the value of this keyword.<a href="#section-6.3.1-2" class="pilcrow">¶</a></p>
<p id="section-6.3.1-3">
The length of a string instance is defined as the number of its
characters as defined by <span><a href="#RFC8259" class="xref">RFC 8259</a> [<a href="#RFC8259" class="xref">RFC8259</a>]</span>.<a href="#section-6.3.1-3" class="pilcrow">¶</a></p>
</section>
<section id="section-6.3.2">
<h4 id="name-minlength">
<a href="#section-6.3.2" class="section-number selfRef">6.3.2. </a><a href="#name-minlength" class="section-name selfRef">minLength</a>
</h4>
<p id="section-6.3.2-1">
The value of this keyword MUST be a non-negative integer.<a href="#section-6.3.2-1" class="pilcrow">¶</a></p>
<p id="section-6.3.2-2">
A string instance is valid against this keyword if its
length is greater than, or equal to, the value of this keyword.<a href="#section-6.3.2-2" class="pilcrow">¶</a></p>
<p id="section-6.3.2-3">
The length of a string instance is defined as the number of its
characters as defined by <span><a href="#RFC8259" class="xref">RFC 8259</a> [<a href="#RFC8259" class="xref">RFC8259</a>]</span>.<a href="#section-6.3.2-3" class="pilcrow">¶</a></p>
<p id="section-6.3.2-4">
Omitting this keyword has the same behavior as a value of 0.<a href="#section-6.3.2-4" class="pilcrow">¶</a></p>
</section>
<div id="pattern">
<section id="section-6.3.3">
<h4 id="name-pattern">
<a href="#section-6.3.3" class="section-number selfRef">6.3.3. </a><a href="#name-pattern" class="section-name selfRef">pattern</a>
</h4>
<p id="section-6.3.3-1">
The value of this keyword MUST be a string. This string SHOULD be a
valid regular expression, according to the ECMA-262 regular expression
dialect.<a href="#section-6.3.3-1" class="pilcrow">¶</a></p>
<p id="section-6.3.3-2">
A string instance is considered valid if the regular
expression matches the instance successfully. Recall: regular
expressions are not implicitly anchored.<a href="#section-6.3.3-2" class="pilcrow">¶</a></p>
</section>
</div>
</section>
</div>
<section id="section-6.4">
<h3 id="name-validation-keywords-for-arr">
<a href="#section-6.4" class="section-number selfRef">6.4. </a><a href="#name-validation-keywords-for-arr" class="section-name selfRef">Validation Keywords for Arrays</a>
</h3>
<section id="section-6.4.1">
<h4 id="name-maxitems">
<a href="#section-6.4.1" class="section-number selfRef">6.4.1. </a><a href="#name-maxitems" class="section-name selfRef">maxItems</a>
</h4>
<p id="section-6.4.1-1">
The value of this keyword MUST be a non-negative integer.<a href="#section-6.4.1-1" class="pilcrow">¶</a></p>
<p id="section-6.4.1-2">
An array instance is valid against "maxItems" if its size is
less than, or equal to, the value of this keyword.<a href="#section-6.4.1-2" class="pilcrow">¶</a></p>
</section>
<section id="section-6.4.2">
<h4 id="name-minitems">
<a href="#section-6.4.2" class="section-number selfRef">6.4.2. </a><a href="#name-minitems" class="section-name selfRef">minItems</a>
</h4>
<p id="section-6.4.2-1">
The value of this keyword MUST be a non-negative integer.<a href="#section-6.4.2-1" class="pilcrow">¶</a></p>
<p id="section-6.4.2-2">
An array instance is valid against "minItems" if its size is
greater than, or equal to, the value of this keyword.<a href="#section-6.4.2-2" class="pilcrow">¶</a></p>
<p id="section-6.4.2-3">
Omitting this keyword has the same behavior as a value of 0.<a href="#section-6.4.2-3" class="pilcrow">¶</a></p>
</section>
<section id="section-6.4.3">
<h4 id="name-uniqueitems">
<a href="#section-6.4.3" class="section-number selfRef">6.4.3. </a><a href="#name-uniqueitems" class="section-name selfRef">uniqueItems</a>
</h4>
<p id="section-6.4.3-1">
The value of this keyword MUST be a boolean.<a href="#section-6.4.3-1" class="pilcrow">¶</a></p>
<p id="section-6.4.3-2">
If this keyword has boolean value false, the instance validates
successfully. If it has boolean value true, the instance validates
successfully if all of its elements are unique.<a href="#section-6.4.3-2" class="pilcrow">¶</a></p>
<p id="section-6.4.3-3">
Omitting this keyword has the same behavior as a value of false.<a href="#section-6.4.3-3" class="pilcrow">¶</a></p>
</section>
<section id="section-6.4.4">
<h4 id="name-maxcontains">
<a href="#section-6.4.4" class="section-number selfRef">6.4.4. </a><a href="#name-maxcontains" class="section-name selfRef">maxContains</a>
</h4>
<p id="section-6.4.4-1">
The value of this keyword MUST be a non-negative integer.<a href="#section-6.4.4-1" class="pilcrow">¶</a></p>
<p id="section-6.4.4-2">
If "contains" is not present within the same schema object,
then this keyword has no effect.<a href="#section-6.4.4-2" class="pilcrow">¶</a></p>
<p id="section-6.4.4-3">
An instance array is valid against "maxContains" in two ways, depending on
the form of the annotation result of an adjacent
<span><a href="#json-schema" class="xref">"contains"</a> [<a href="#json-schema" class="xref">json-schema</a>]</span> keyword. The first way is if
the annotation result is an array and the length of that array is less than
or equal to the "maxContains" value. The second way is if the annotation
result is a boolean "true" and the instance array length is less than or
equal to the "maxContains" value.<a href="#section-6.4.4-3" class="pilcrow">¶</a></p>
</section>
<section id="section-6.4.5">
<h4 id="name-mincontains">
<a href="#section-6.4.5" class="section-number selfRef">6.4.5. </a><a href="#name-mincontains" class="section-name selfRef">minContains</a>
</h4>
<p id="section-6.4.5-1">
The value of this keyword MUST be a non-negative integer.<a href="#section-6.4.5-1" class="pilcrow">¶</a></p>
<p id="section-6.4.5-2">
If "contains" is not present within the same schema object,
then this keyword has no effect.<a href="#section-6.4.5-2" class="pilcrow">¶</a></p>
<p id="section-6.4.5-3">
An instance array is valid against "minContains" in two ways, depending on
the form of the annotation result of an adjacent
<span><a href="#json-schema" class="xref">"contains"</a> [<a href="#json-schema" class="xref">json-schema</a>]</span> keyword. The first way is if
the annotation result is an array and the length of that array is greater
than or equal to the "minContains" value. The second way is if the
annotation result is a boolean "true" and the instance array length is
greater than or equal to the "minContains" value.<a href="#section-6.4.5-3" class="pilcrow">¶</a></p>
<p id="section-6.4.5-4">
A value of 0 is allowed, but is only useful for setting a range
of occurrences from 0 to the value of "maxContains". A value of
0 causes "minContains" and "contains" to always pass validation
(but validation can still fail against a "maxContains" keyword).<a href="#section-6.4.5-4" class="pilcrow">¶</a></p>
<p id="section-6.4.5-5">
Omitting this keyword has the same behavior as a value of 1.<a href="#section-6.4.5-5" class="pilcrow">¶</a></p>
</section>
</section>
<section id="section-6.5">
<h3 id="name-validation-keywords-for-obj">
<a href="#section-6.5" class="section-number selfRef">6.5. </a><a href="#name-validation-keywords-for-obj" class="section-name selfRef">Validation Keywords for Objects</a>
</h3>
<section id="section-6.5.1">
<h4 id="name-maxproperties">
<a href="#section-6.5.1" class="section-number selfRef">6.5.1. </a><a href="#name-maxproperties" class="section-name selfRef">maxProperties</a>
</h4>
<p id="section-6.5.1-1">
The value of this keyword MUST be a non-negative integer.<a href="#section-6.5.1-1" class="pilcrow">¶</a></p>
<p id="section-6.5.1-2">
An object instance is valid against "maxProperties" if its
number of properties is less than, or equal to, the value of this
keyword.<a href="#section-6.5.1-2" class="pilcrow">¶</a></p>
</section>
<section id="section-6.5.2">
<h4 id="name-minproperties">
<a href="#section-6.5.2" class="section-number selfRef">6.5.2. </a><a href="#name-minproperties" class="section-name selfRef">minProperties</a>
</h4>
<p id="section-6.5.2-1">
The value of this keyword MUST be a non-negative integer.<a href="#section-6.5.2-1" class="pilcrow">¶</a></p>
<p id="section-6.5.2-2">
An object instance is valid against "minProperties" if its
number of properties is greater than, or equal to, the value of this
keyword.<a href="#section-6.5.2-2" class="pilcrow">¶</a></p>
<p id="section-6.5.2-3">
Omitting this keyword has the same behavior as a value of 0.<a href="#section-6.5.2-3" class="pilcrow">¶</a></p>
</section>
<section id="section-6.5.3">
<h4 id="name-required">
<a href="#section-6.5.3" class="section-number selfRef">6.5.3. </a><a href="#name-required" class="section-name selfRef">required</a>
</h4>
<p id="section-6.5.3-1">
The value of this keyword MUST be an array.
Elements of this array, if any, MUST be strings, and MUST be unique.<a href="#section-6.5.3-1" class="pilcrow">¶</a></p>
<p id="section-6.5.3-2">
An object instance is valid against this keyword if every item in the array is
the name of a property in the instance.<a href="#section-6.5.3-2" class="pilcrow">¶</a></p>
<p id="section-6.5.3-3">
Omitting this keyword has the same behavior as an empty array.<a href="#section-6.5.3-3" class="pilcrow">¶</a></p>
</section>
<section id="section-6.5.4">
<h4 id="name-dependentrequired">
<a href="#section-6.5.4" class="section-number selfRef">6.5.4. </a><a href="#name-dependentrequired" class="section-name selfRef">dependentRequired</a>
</h4>
<p id="section-6.5.4-1">
The value of this keyword MUST be an object. Properties in
this object, if any, MUST be arrays. Elements in each array,
if any, MUST be strings, and MUST be unique.<a href="#section-6.5.4-1" class="pilcrow">¶</a></p>
<p id="section-6.5.4-2">
This keyword specifies properties that are required if a specific
other property is present. Their requirement is dependent on the
presence of the other property.<a href="#section-6.5.4-2" class="pilcrow">¶</a></p>
<p id="section-6.5.4-3">
Validation succeeds if, for each name that appears in both
the instance and as a name within this keyword's value, every
item in the corresponding array is also the name of a property
in the instance.<a href="#section-6.5.4-3" class="pilcrow">¶</a></p>
<p id="section-6.5.4-4">
Omitting this keyword has the same behavior as an empty object.<a href="#section-6.5.4-4" class="pilcrow">¶</a></p>
</section>
</section>
</section>
<div id="format">
<section id="section-7">
<h2 id="name-vocabularies-for-semantic-c">
<a href="#section-7" class="section-number selfRef">7. </a><a href="#name-vocabularies-for-semantic-c" class="section-name selfRef">Vocabularies for Semantic Content With "format"</a>
</h2>
<section id="section-7.1">
<h3 id="name-foreword">
<a href="#section-7.1" class="section-number selfRef">7.1. </a><a href="#name-foreword" class="section-name selfRef">Foreword</a>
</h3>
<p id="section-7.1-1">
Structural validation alone may be insufficient to allow an application to correctly
utilize certain values. The "format" annotation keyword is defined to allow schema
authors to convey semantic information for a fixed subset of values which are
accurately described by authoritative resources, be they RFCs or other external
specifications.<a href="#section-7.1-1" class="pilcrow">¶</a></p>
<p id="section-7.1-2">
The value of this keyword is called a format attribute. It MUST be a string. A
format attribute can generally only validate a given set of instance types. If
the type of the instance to validate is not in this set, validation for this
format attribute and instance SHOULD succeed. All format attributes defined
in this section apply to strings, but a format attribute can be specified
to apply to any instance types defined in the data model defined in the
<span><a href="#json-schema" class="xref">core JSON Schema.</a> [<a href="#json-schema" class="xref">json-schema</a>]</span>
<span class="cref">
Note that the "type" keyword in this specification defines an "integer" type
which is not part of the data model. Therefore a format attribute can be
limited to numbers, but not specifically to integers. However, a numeric
format can be used alongside the "type" keyword with a value of "integer",
or could be explicitly defined to always pass if the number is not an integer,
which produces essentially the same behavior as only applying to integers.
</span><a href="#section-7.1-2" class="pilcrow">¶</a></p>
<p id="section-7.1-3">
The current URI for this vocabulary, known as the Format-Annotation vocabulary, is:
<https://json-schema.org/draft/2020-12/vocab/format-annotation>. The current
URI for the corresponding meta-schema is:
<span><a href="https://json-schema.org/draft/2020-12/meta/format-annotation">https://json-schema.org/draft/2020-12/meta/format-annotation</a></span>.
Implementing support for this vocabulary is REQUIRED.<a href="#section-7.1-3" class="pilcrow">¶</a></p>
<p id="section-7.1-4">
In addition to the Format-Annotation vocabulary, a secondary vocabulary is available
for custom meta-schemas that defines "format" as an assertion. The URI for the
Format-Assertion vocabulary, is:
<https://json-schema.org/draft/2020-12/vocab/format-assertion>. The current
URI for the corresponding meta-schema is:
<span><a href="https://json-schema.org/draft/2020-12/meta/format-assertion">https://json-schema.org/draft/2020-12/meta/format-assertion</a></span>.
Implementing support for the Format-Assertion vocabulary is OPTIONAL.<a href="#section-7.1-4" class="pilcrow">¶</a></p>
<p id="section-7.1-5">
Specifying both the Format-Annotation and the Format-Assertion vocabularies is functionally
equivalent to specifying only the Format-Assertion vocabulary since its requirements
are a superset of the Format-Annotation vocabulary.<a href="#section-7.1-5" class="pilcrow">¶</a></p>
</section>
<section id="section-7.2">
<h3 id="name-implementation-requirements">
<a href="#section-7.2" class="section-number selfRef">7.2. </a><a href="#name-implementation-requirements" class="section-name selfRef">Implementation Requirements</a>
</h3>
<p id="section-7.2-1">
The "format" keyword functions as defined by the vocabulary which is referenced.<a href="#section-7.2-1" class="pilcrow">¶</a></p>
<section id="section-7.2.1">
<h4 id="name-format-annotation-vocabular">
<a href="#section-7.2.1" class="section-number selfRef">7.2.1. </a><a href="#name-format-annotation-vocabular" class="section-name selfRef">Format-Annotation Vocabulary</a>
</h4>
<p id="section-7.2.1-1">
The value of format MUST be collected as an annotation, if the implementation
supports annotation collection. This enables application-level validation when
schema validation is unavailable or inadequate.<a href="#section-7.2.1-1" class="pilcrow">¶</a></p>
<p id="section-7.2.1-2">
Implementations MAY still treat "format" as an assertion in addition to an
annotation and attempt to validate the value's conformance to the specified
semantics. The implementation MUST provide options to enable and disable such
evaluation and MUST be disabled by default. Implementations SHOULD document
their level of support for such validation.
<span class="cref">
Specifying the Format-Annotation vocabulary and enabling validation in an
implementation should not be viewed as being equivalent to specifying
the Format-Assertion vocabulary since implementations are not required to
provide full validation support when the Format-Assertion vocabulary
is not specified.
</span><a href="#section-7.2.1-2" class="pilcrow">¶</a></p>
<p id="section-7.2.1-3">
When the implementation is configured for assertion behavior, it:<a href="#section-7.2.1-3" class="pilcrow">¶</a></p>
<ul class="normal ulEmpty">
<li class="normal ulEmpty" id="section-7.2.1-4.1">
SHOULD provide an implementation-specific best effort validation
for each format attribute defined below;<a href="#section-7.2.1-4.1" class="pilcrow">¶</a>
</li>
<li class="normal ulEmpty" id="section-7.2.1-4.2">
MAY choose to implement validation of any or all format attributes
as a no-op by always producing a validation result of true;<a href="#section-7.2.1-4.2" class="pilcrow">¶</a>
</li>
</ul>
<p id="section-7.2.1-5">
<span class="cref">
This matches the current reality of implementations, which provide
widely varying levels of validation, including no validation at all,
for some or all format attributes. It is also designed to encourage
relying only on the annotation behavior and performing semantic
validation in the application, which is the recommended best practice.
</span><a href="#section-7.2.1-5" class="pilcrow">¶</a></p>
</section>
<section id="section-7.2.2">
<h4 id="name-format-assertion-vocabulary">
<a href="#section-7.2.2" class="section-number selfRef">7.2.2. </a><a href="#name-format-assertion-vocabulary" class="section-name selfRef">Format-Assertion Vocabulary</a>
</h4>
<p id="section-7.2.2-1">
When the Format-Assertion vocabulary is declared with a value of true,
implementations MUST provide full validation support for all of the formats
defined by this specificaion. Implementations that cannot provide full
validation support MUST refuse to process the schema.<a href="#section-7.2.2-1" class="pilcrow">¶</a></p>
<p id="section-7.2.2-2">
An implementation that supports the Format-Assertion vocabulary:<a href="#section-7.2.2-2" class="pilcrow">¶</a></p>
<ul class="normal ulEmpty">
<li class="normal ulEmpty" id="section-7.2.2-3.1">
MUST still collect "format" as an annotation if the implementation
supports annotation collection;<a href="#section-7.2.2-3.1" class="pilcrow">¶</a>
</li>
<li class="normal ulEmpty" id="section-7.2.2-3.2">
MUST evaluate "format" as an assertion;<a href="#section-7.2.2-3.2" class="pilcrow">¶</a>
</li>
<li class="normal ulEmpty" id="section-7.2.2-3.3">
MUST implement syntactic validation for all format attributes defined
in this specification, and for any additional format attributes that
it recognizes, such that there exist possible instance values
of the correct type that will fail validation.<a href="#section-7.2.2-3.3" class="pilcrow">¶</a>
</li>
</ul>
<p id="section-7.2.2-4">
The requirement for minimal validation of format attributes is intentionally
vague and permissive, due to the complexity involved in many of the attributes.
Note in particular that the requirement is limited to syntactic checking; it is
not to be expected that an implementation would send an email, attempt to connect
to a URL, or otherwise check the existence of an entity identified by a format
instance.
<span class="cref">
The expectation is that for simple formats such as date-time, syntactic
validation will be thorough. For a complex format such as email addresses,
which are the amalgamation of various standards and numerous adjustments
over time, with obscure and/or obsolete rules that may or may not be
restricted by other applications making use of the value, a minimal validation
is sufficient. For example, an instance string that does not contain
an "@" is clearly not a valid email address, and an "email" or "hostname"
containing characters outside of 7-bit ASCII is likewise clearly invalid.
</span><a href="#section-7.2.2-4" class="pilcrow">¶</a></p>
<p id="section-7.2.2-5">
It is RECOMMENDED that implementations use a common parsing library for each format,
or a well-known regular expression. Implementations SHOULD clearly document
how and to what degree each format attribute is validated.<a href="#section-7.2.2-5" class="pilcrow">¶</a></p>
<p id="section-7.2.2-6">
The <span><a href="#meta-schema" class="xref">standard core and validation meta-schema</a> (<a href="#meta-schema" class="xref">Section 5</a>)</span>
includes this vocabulary in its "$vocabulary" keyword with a value of false,
since by default implementations are not required to support this keyword
as an assertion. Supporting the format vocabulary with a value of true is
understood to greatly increase code size and in some cases execution time,
and will not be appropriate for all implementations.<a href="#section-7.2.2-6" class="pilcrow">¶</a></p>
</section>
<section id="section-7.2.3">
<h4 id="name-custom-format-attributes">
<a href="#section-7.2.3" class="section-number selfRef">7.2.3. </a><a href="#name-custom-format-attributes" class="section-name selfRef">Custom format attributes</a>
</h4>
<p id="section-7.2.3-1">
Implementations MAY support custom format attributes. Save for agreement between
parties, schema authors SHALL NOT expect a peer implementation to support such
custom format attributes. An implementation MUST NOT fail to collect unknown formats
as annotations. When the Format-Assertion vocabulary is specified, implementations
MUST fail upon encountering unknown formats.<a href="#section-7.2.3-1" class="pilcrow">¶</a></p>
<p id="section-7.2.3-2">
Vocabularies do not support specifically declaring different value sets for keywords.
Due to this limitation, and the historically uneven implementation of this keyword,
it is RECOMMENDED to define additional keywords in a custom vocabulary rather than
additional format attributes if interoperability is desired.<a href="#section-7.2.3-2" class="pilcrow">¶</a></p>
</section>
</section>
<section id="section-7.3">
<h3 id="name-defined-formats">
<a href="#section-7.3" class="section-number selfRef">7.3. </a><a href="#name-defined-formats" class="section-name selfRef">Defined Formats</a>
</h3>
<section id="section-7.3.1">
<h4 id="name-dates-times-and-duration">
<a href="#section-7.3.1" class="section-number selfRef">7.3.1. </a><a href="#name-dates-times-and-duration" class="section-name selfRef">Dates, Times, and Duration</a>
</h4>
<p id="section-7.3.1-1">
These attributes apply to string instances.<a href="#section-7.3.1-1" class="pilcrow">¶</a></p>
<p id="section-7.3.1-2">
Date and time format names are derived from
<span><a href="#RFC3339" class="xref">RFC 3339, section 5.6</a> [<a href="#RFC3339" class="xref">RFC3339</a>]</span>.
The duration format is from the ISO 8601 ABNF as given
in Appendix A of RFC 3339.<a href="#section-7.3.1-2" class="pilcrow">¶</a></p>
<p id="section-7.3.1-3">
Implementations supporting formats SHOULD implement support for
the following attributes:<a href="#section-7.3.1-3" class="pilcrow">¶</a></p>
<span class="break"></span><dl class="dlParallel" id="section-7.3.1-4">
<dt id="section-7.3.1-4.1">date-time:</dt>
<dd style="margin-left: 1.5em" id="section-7.3.1-4.2">
A string instance is valid against this attribute if it is
a valid representation according to the "date-time' ABNF rule
(referenced above)<a href="#section-7.3.1-4.2" class="pilcrow">¶</a>
</dd>
<dd class="break"></dd>
<dt id="section-7.3.1-4.3">date:</dt>
<dd style="margin-left: 1.5em" id="section-7.3.1-4.4">
A string instance is valid against this attribute if it is
a valid representation according to the "full-date" ABNF rule
(referenced above)<a href="#section-7.3.1-4.4" class="pilcrow">¶</a>
</dd>
<dd class="break"></dd>
<dt id="section-7.3.1-4.5">time:</dt>
<dd style="margin-left: 1.5em" id="section-7.3.1-4.6">
A string instance is valid against this attribute if it is
a valid representation according to the "full-time" ABNF rule
(referenced above)<a href="#section-7.3.1-4.6" class="pilcrow">¶</a>
</dd>
<dd class="break"></dd>
<dt id="section-7.3.1-4.7">duration:</dt>
<dd style="margin-left: 1.5em" id="section-7.3.1-4.8">
A string instance is valid against this attribute if it is
a valid representation according to the "duration" ABNF rule
(referenced above)<a href="#section-7.3.1-4.8" class="pilcrow">¶</a>
</dd>
<dd class="break"></dd>
</dl>
<p id="section-7.3.1-5">
Implementations MAY support additional attributes using the other
format names defined anywhere in that RFC. If "full-date" or "full-time"
are implemented, the corresponding short form ("date" or "time"
respectively) MUST be implemented, and MUST behave identically.
Implementations SHOULD NOT define extension attributes
with any name matching an RFC 3339 format unless it validates
according to the rules of that format.
<span class="cref">
There is not currently consensus on the need for supporting
all RFC 3339 formats, so this approach of reserving the
namespace will encourage experimentation without committing
to the entire set. Either the format implementation requirements
will become more flexible in general, or these will likely
either be promoted to fully specified attributes or dropped.
</span><a href="#section-7.3.1-5" class="pilcrow">¶</a></p>
</section>
<section id="section-7.3.2">
<h4 id="name-email-addresses">
<a href="#section-7.3.2" class="section-number selfRef">7.3.2. </a><a href="#name-email-addresses" class="section-name selfRef">Email Addresses</a>
</h4>
<p id="section-7.3.2-1">
These attributes apply to string instances.<a href="#section-7.3.2-1" class="pilcrow">¶</a></p>
<p id="section-7.3.2-2">
A string instance is valid against these attributes if it is a valid
Internet email address as follows:<a href="#section-7.3.2-2" class="pilcrow">¶</a></p>
<span class="break"></span><dl class="dlParallel" id="section-7.3.2-3">
<dt id="section-7.3.2-3.1">email:</dt>
<dd style="margin-left: 1.5em" id="section-7.3.2-3.2">
As defined by the "Mailbox" ABNF rule in
<span><a href="#RFC5321" class="xref">RFC 5321, section 4.1.2</a> [<a href="#RFC5321" class="xref">RFC5321</a>]</span>.<a href="#section-7.3.2-3.2" class="pilcrow">¶</a>
</dd>
<dd class="break"></dd>
<dt id="section-7.3.2-3.3">idn-email:</dt>
<dd style="margin-left: 1.5em" id="section-7.3.2-3.4">
As defined by the extended "Mailbox" ABNF rule in
<span><a href="#RFC6531" class="xref">RFC 6531, section 3.3</a> [<a href="#RFC6531" class="xref">RFC6531</a>]</span>.<a href="#section-7.3.2-3.4" class="pilcrow">¶</a>
</dd>
<dd class="break"></dd>
</dl>
<p id="section-7.3.2-4">
Note that all strings valid against the "email" attribute are also
valid against the "idn-email" attribute.<a href="#section-7.3.2-4" class="pilcrow">¶</a></p>
</section>
<section id="section-7.3.3">
<h4 id="name-hostnames">
<a href="#section-7.3.3" class="section-number selfRef">7.3.3. </a><a href="#name-hostnames" class="section-name selfRef">Hostnames</a>
</h4>
<p id="section-7.3.3-1">
These attributes apply to string instances.<a href="#section-7.3.3-1" class="pilcrow">¶</a></p>
<p id="section-7.3.3-2">
A string instance is valid against these attributes if it is a valid
representation for an Internet hostname as follows:<a href="#section-7.3.3-2" class="pilcrow">¶</a></p>
<span class="break"></span><dl class="dlParallel" id="section-7.3.3-3">
<dt id="section-7.3.3-3.1">hostname:</dt>
<dd style="margin-left: 1.5em" id="section-7.3.3-3.2">
As defined by <span><a href="#RFC1123" class="xref">RFC 1123, section 2.1</a> [<a href="#RFC1123" class="xref">RFC1123</a>]</span>,
including host names produced using the Punycode algorithm
specified in <span><a href="#RFC5891" class="xref">RFC 5891, section 4.4</a> [<a href="#RFC5891" class="xref">RFC5891</a>]</span>.<a href="#section-7.3.3-3.2" class="pilcrow">¶</a>
</dd>
<dd class="break"></dd>
<dt id="section-7.3.3-3.3">idn-hostname:</dt>
<dd style="margin-left: 1.5em" id="section-7.3.3-3.4">
As defined by either RFC 1123 as for hostname, or an
internationalized hostname as defined by
<span><a href="#RFC5890" class="xref">RFC 5890, section 2.3.2.3</a> [<a href="#RFC5890" class="xref">RFC5890</a>]</span>.<a href="#section-7.3.3-3.4" class="pilcrow">¶</a>
</dd>
<dd class="break"></dd>
</dl>
<p id="section-7.3.3-4">
Note that all strings valid against the "hostname" attribute are also
valid against the "idn-hostname" attribute.<a href="#section-7.3.3-4" class="pilcrow">¶</a></p>
</section>
<section id="section-7.3.4">
<h4 id="name-ip-addresses">
<a href="#section-7.3.4" class="section-number selfRef">7.3.4. </a><a href="#name-ip-addresses" class="section-name selfRef">IP Addresses</a>
</h4>
<p id="section-7.3.4-1">
These attributes apply to string instances.<a href="#section-7.3.4-1" class="pilcrow">¶</a></p>
<p id="section-7.3.4-2">
A string instance is valid against these attributes if it is a valid
representation of an IP address as follows:<a href="#section-7.3.4-2" class="pilcrow">¶</a></p>
<span class="break"></span><dl class="dlParallel" id="section-7.3.4-3">
<dt id="section-7.3.4-3.1">ipv4:</dt>
<dd style="margin-left: 1.5em" id="section-7.3.4-3.2">
An IPv4 address according to the "dotted-quad" ABNF
syntax as defined in
<span><a href="#RFC2673" class="xref">RFC 2673, section 3.2</a> [<a href="#RFC2673" class="xref">RFC2673</a>]</span>.<a href="#section-7.3.4-3.2" class="pilcrow">¶</a>
</dd>
<dd class="break"></dd>
<dt id="section-7.3.4-3.3">ipv6:</dt>
<dd style="margin-left: 1.5em" id="section-7.3.4-3.4">
An IPv6 address as defined in
<span><a href="#RFC4291" class="xref">RFC 4291, section 2.2</a> [<a href="#RFC4291" class="xref">RFC4291</a>]</span>.<a href="#section-7.3.4-3.4" class="pilcrow">¶</a>
</dd>
<dd class="break"></dd>
</dl>
</section>
<section id="section-7.3.5">
<h4 id="name-resource-identifiers">
<a href="#section-7.3.5" class="section-number selfRef">7.3.5. </a><a href="#name-resource-identifiers" class="section-name selfRef">Resource Identifiers</a>
</h4>
<p id="section-7.3.5-1">
These attributes apply to string instances.<a href="#section-7.3.5-1" class="pilcrow">¶</a></p>
<span class="break"></span><dl class="dlParallel" id="section-7.3.5-2">
<dt id="section-7.3.5-2.1">uri:</dt>
<dd style="margin-left: 1.5em" id="section-7.3.5-2.2">
A string instance is valid against this attribute if it is
a valid URI, according to <span>[<a href="#RFC3986" class="xref">RFC3986</a>]</span>.<a href="#section-7.3.5-2.2" class="pilcrow">¶</a>
</dd>
<dd class="break"></dd>
<dt id="section-7.3.5-2.3">uri-reference:</dt>
<dd style="margin-left: 1.5em" id="section-7.3.5-2.4">
A string instance is valid against this attribute if it is a valid URI
Reference (either a URI or a relative-reference),
according to <span>[<a href="#RFC3986" class="xref">RFC3986</a>]</span>.<a href="#section-7.3.5-2.4" class="pilcrow">¶</a>
</dd>
<dd class="break"></dd>
<dt id="section-7.3.5-2.5">iri:</dt>
<dd style="margin-left: 1.5em" id="section-7.3.5-2.6">
A string instance is valid against this attribute if it is
a valid IRI, according to <span>[<a href="#RFC3987" class="xref">RFC3987</a>]</span>.<a href="#section-7.3.5-2.6" class="pilcrow">¶</a>
</dd>
<dd class="break"></dd>
<dt id="section-7.3.5-2.7">iri-reference:</dt>
<dd style="margin-left: 1.5em" id="section-7.3.5-2.8">
A string instance is valid against this attribute if it is a valid IRI
Reference (either an IRI or a relative-reference),
according to <span>[<a href="#RFC3987" class="xref">RFC3987</a>]</span>.<a href="#section-7.3.5-2.8" class="pilcrow">¶</a>
</dd>
<dd class="break"></dd>
<dt id="section-7.3.5-2.9">uuid:</dt>
<dd style="margin-left: 1.5em" id="section-7.3.5-2.10">
A string instance is valid against this attribute if it is a valid
string representation of a UUID, according to <span>[<a href="#RFC4122" class="xref">RFC4122</a>]</span>.<a href="#section-7.3.5-2.10" class="pilcrow">¶</a>
</dd>
<dd class="break"></dd>
</dl>
<p id="section-7.3.5-3">
Note that all valid URIs are valid IRIs, and all valid URI References are
also valid IRI References.<a href="#section-7.3.5-3" class="pilcrow">¶</a></p>
<p id="section-7.3.5-4">
Note also that the "uuid" format is for plain UUIDs, not UUIDs in URNs. An example
is "f81d4fae-7dec-11d0-a765-00a0c91e6bf6". For UUIDs as URNs, use the "uri" format,
with a "pattern" regular expression of "^urn:uuid:" to indicate the URI scheme and
URN namespace.<a href="#section-7.3.5-4" class="pilcrow">¶</a></p>
</section>
<section id="section-7.3.6">
<h4 id="name-uri-template">
<a href="#section-7.3.6" class="section-number selfRef">7.3.6. </a><a href="#name-uri-template" class="section-name selfRef">uri-template</a>
</h4>
<p id="section-7.3.6-1">
This attribute applies to string instances.<a href="#section-7.3.6-1" class="pilcrow">¶</a></p>
<p id="section-7.3.6-2">
A string instance is valid against this attribute if it is a valid URI Template
(of any level), according to <span>[<a href="#RFC6570" class="xref">RFC6570</a>]</span>.<a href="#section-7.3.6-2" class="pilcrow">¶</a></p>
<p id="section-7.3.6-3">
Note that URI Templates may be used for IRIs; there is no separate
IRI Template specification.<a href="#section-7.3.6-3" class="pilcrow">¶</a></p>
</section>
<section id="section-7.3.7">
<h4 id="name-json-pointers">
<a href="#section-7.3.7" class="section-number selfRef">7.3.7. </a><a href="#name-json-pointers" class="section-name selfRef">JSON Pointers</a>
</h4>
<p id="section-7.3.7-1">
These attributes apply to string instances.<a href="#section-7.3.7-1" class="pilcrow">¶</a></p>
<span class="break"></span><dl class="dlParallel" id="section-7.3.7-2">
<dt id="section-7.3.7-2.1">json-pointer:</dt>
<dd style="margin-left: 1.5em" id="section-7.3.7-2.2">
A string instance is valid against this attribute if it
is a valid JSON string representation of a JSON Pointer,
according to <span><a href="#RFC6901" class="xref">RFC 6901, section 5</a> [<a href="#RFC6901" class="xref">RFC6901</a>]</span>.<a href="#section-7.3.7-2.2" class="pilcrow">¶</a>
</dd>
<dd class="break"></dd>
<dt id="section-7.3.7-2.3">relative-json-pointer:</dt>
<dd style="margin-left: 1.5em" id="section-7.3.7-2.4">
A string instance is valid against this attribute if it is a valid
<span><a href="#relative-json-pointer" class="xref">Relative JSON Pointer</a> [<a href="#relative-json-pointer" class="xref">relative-json-pointer</a>]</span>.<a href="#section-7.3.7-2.4" class="pilcrow">¶</a>
</dd>
<dd class="break"></dd>
</dl>
<p id="section-7.3.7-3">
To allow for both absolute and relative JSON Pointers, use "anyOf" or
"oneOf" to indicate support for either format.<a href="#section-7.3.7-3" class="pilcrow">¶</a></p>
</section>
<section id="section-7.3.8">
<h4 id="name-regex">
<a href="#section-7.3.8" class="section-number selfRef">7.3.8. </a><a href="#name-regex" class="section-name selfRef">regex</a>
</h4>
<p id="section-7.3.8-1">
This attribute applies to string instances.<a href="#section-7.3.8-1" class="pilcrow">¶</a></p>
<p id="section-7.3.8-2">
A regular expression, which SHOULD be valid according to the
<span><a href="#ecma262" class="xref">ECMA-262</a> [<a href="#ecma262" class="xref">ecma262</a>]</span> regular expression dialect.<a href="#section-7.3.8-2" class="pilcrow">¶</a></p>
<p id="section-7.3.8-3">
Implementations that validate formats MUST accept at least the subset of
ECMA-262 defined in the <span><a href="#regexInterop" class="xref">Regular Expressions</a> (<a href="#regexInterop" class="xref">Section 4.3</a>)</span>
section of this specification, and SHOULD accept all valid ECMA-262 expressions.<a href="#section-7.3.8-3" class="pilcrow">¶</a></p>
</section>
</section>
</section>
</div>
<div id="content">
<section id="section-8">
<h2 id="name-a-vocabulary-for-the-conten">
<a href="#section-8" class="section-number selfRef">8. </a><a href="#name-a-vocabulary-for-the-conten" class="section-name selfRef">A Vocabulary for the Contents of String-Encoded Data</a>
</h2>
<section id="section-8.1">
<h3 id="name-foreword-2">
<a href="#section-8.1" class="section-number selfRef">8.1. </a><a href="#name-foreword-2" class="section-name selfRef">Foreword</a>
</h3>
<p id="section-8.1-1">
Annotations defined in this section indicate that an instance contains
non-JSON data encoded in a JSON string.<a href="#section-8.1-1" class="pilcrow">¶</a></p>
<p id="section-8.1-2">
These properties provide additional information required to interpret JSON data
as rich multimedia documents. They describe the type of content, how it is encoded,
and/or how it may be validated. They do not function as validation assertions;
a malformed string-encoded document MUST NOT cause the containing instance
to be considered invalid.<a href="#section-8.1-2" class="pilcrow">¶</a></p>
<p id="section-8.1-3">
Meta-schemas that do not use "$vocabulary" SHOULD be considered to
require this vocabulary as if its URI were present with a value of true.<a href="#section-8.1-3" class="pilcrow">¶</a></p>
<p id="section-8.1-4">
The current URI for this vocabulary, known as the Content vocabulary, is:
<https://json-schema.org/draft/2020-12/vocab/content>.<a href="#section-8.1-4" class="pilcrow">¶</a></p>
<p id="section-8.1-5">
The current URI for the corresponding meta-schema is:
<span><a href="https://json-schema.org/draft/2020-12/meta/content">https://json-schema.org/draft/2020-12/meta/content</a></span>.<a href="#section-8.1-5" class="pilcrow">¶</a></p>
</section>
<section id="section-8.2">
<h3 id="name-implementation-requirements-2">
<a href="#section-8.2" class="section-number selfRef">8.2. </a><a href="#name-implementation-requirements-2" class="section-name selfRef">Implementation Requirements</a>
</h3>
<p id="section-8.2-1">
Due to security and performance concerns, as well as the open-ended nature of
possible content types, implementations MUST NOT automatically decode, parse,
and/or validate the string contents by default. This additionally supports
the use case of embedded documents intended for processing by a different
consumer than that which processed the containing document.<a href="#section-8.2-1" class="pilcrow">¶</a></p>
<p id="section-8.2-2">
All keywords in this section apply only to strings, and have no
effect on other data types.<a href="#section-8.2-2" class="pilcrow">¶</a></p>
<p id="section-8.2-3">
Implementations MAY offer the ability to decode, parse, and/or validate
the string contents automatically. However, it MUST NOT perform these
operations by default, and MUST provide the validation result of each
string-encoded document separately from the enclosing document. This
process SHOULD be equivalent to fully evaluating the instance against
the original schema, followed by using the annotations to decode, parse,
and/or validate each string-encoded document.
<span class="cref">
For now, the exact mechanism of performing and returning parsed
data and/or validation results from such an automatic decoding, parsing,
and validating feature is left unspecified. Should such a feature
prove popular, it may be specified more thoroughly in a future draft.
</span><a href="#section-8.2-3" class="pilcrow">¶</a></p>
<p id="section-8.2-4">
See also the <span><a href="#security" class="xref">Security Considerations</a> (<a href="#security" class="xref">Section 10</a>)</span>
sections for possible vulnerabilities introduced by automatically
processing the instance string according to these keywords.<a href="#section-8.2-4" class="pilcrow">¶</a></p>
</section>
<section id="section-8.3">
<h3 id="name-contentencoding">
<a href="#section-8.3" class="section-number selfRef">8.3. </a><a href="#name-contentencoding" class="section-name selfRef">contentEncoding</a>
</h3>
<p id="section-8.3-1">
If the instance value is a string, this property defines that the string
SHOULD be interpreted as encoded binary data and decoded using the encoding
named by this property.<a href="#section-8.3-1" class="pilcrow">¶</a></p>
<p id="section-8.3-2">
Possible values indicating base 16, 32, and 64 encodings with several
variations are listed in <span><a href="#RFC4648" class="xref">RFC 4648</a> [<a href="#RFC4648" class="xref">RFC4648</a>]</span>. Additionally,
sections 6.7 and 6.8 of <span><a href="#RFC2045" class="xref">RFC 2045</a> [<a href="#RFC2045" class="xref">RFC2045</a>]</span> provide
encodings used in MIME. This keyword is derived from MIME's
Content-Transfer-Encoding header, which was designed to map binary data
into ASCII characters. It is not related to HTTP's Content-Encoding header,
which is used to encode (e.g. compress or encrypt)
the content of HTTP request and responses.<a href="#section-8.3-2" class="pilcrow">¶</a></p>
<p id="section-8.3-3">
As "base64" is defined in both RFCs, the definition
from RFC 4648 SHOULD be assumed unless the string is specifically intended
for use in a MIME context. Note that all of these encodings result in
strings consisting only of 7-bit ASCII characters. Therefore, this keyword
has no meaning for strings containing characters outside of that range.<a href="#section-8.3-3" class="pilcrow">¶</a></p>
<p id="section-8.3-4">
If this keyword is absent, but "contentMediaType" is present, this
indicates that the encoding is the identity encoding, meaning that
no transformation was needed in order to represent the content in
a UTF-8 string.<a href="#section-8.3-4" class="pilcrow">¶</a></p>
<p id="section-8.3-5">
The value of this property MUST be a string.<a href="#section-8.3-5" class="pilcrow">¶</a></p>
</section>
<section id="section-8.4">
<h3 id="name-contentmediatype">
<a href="#section-8.4" class="section-number selfRef">8.4. </a><a href="#name-contentmediatype" class="section-name selfRef">contentMediaType</a>
</h3>
<p id="section-8.4-1">
If the instance is a string, this property indicates the media type
of the contents of the string. If "contentEncoding" is present,
this property describes the decoded string.<a href="#section-8.4-1" class="pilcrow">¶</a></p>
<p id="section-8.4-2">
The value of this property MUST be a string, which MUST be a media type,
as defined by <span><a href="#RFC2046" class="xref">RFC 2046</a> [<a href="#RFC2046" class="xref">RFC2046</a>]</span>.<a href="#section-8.4-2" class="pilcrow">¶</a></p>
</section>
<section id="section-8.5">
<h3 id="name-contentschema">
<a href="#section-8.5" class="section-number selfRef">8.5. </a><a href="#name-contentschema" class="section-name selfRef">contentSchema</a>
</h3>
<p id="section-8.5-1">
If the instance is a string, and if "contentMediaType" is present, this
property contains a schema which describes the structure of the string.<a href="#section-8.5-1" class="pilcrow">¶</a></p>
<p id="section-8.5-2">
This keyword MAY be used with any media type that can be mapped into
JSON Schema's data model.<a href="#section-8.5-2" class="pilcrow">¶</a></p>
<p id="section-8.5-3">
The value of this property MUST be a valid JSON schema. It SHOULD be ignored if
"contentMediaType" is not present.<a href="#section-8.5-3" class="pilcrow">¶</a></p>
</section>
<section id="section-8.6">
<h3 id="name-example">
<a href="#section-8.6" class="section-number selfRef">8.6. </a><a href="#name-example" class="section-name selfRef">Example</a>
</h3>
<p id="section-8.6-1" class="keepWithNext">
Here is an example schema, illustrating the use of "contentEncoding" and
"contentMediaType":<a href="#section-8.6-1" class="pilcrow">¶</a></p>
<div class="alignLeft art-text artwork" id="section-8.6-2">
<pre>
{
"type": "string",
"contentEncoding": "base64",
"contentMediaType": "image/png"
}
</pre><a href="#section-8.6-2" class="pilcrow">¶</a>
</div>
<p id="section-8.6-3" class="keepWithPrevious">
Instances described by this schema are expected to be strings,
and their values should be interpretable as base64-encoded PNG images.<a href="#section-8.6-3" class="pilcrow">¶</a></p>
<p id="section-8.6-4" class="keepWithNext">
Another example:<a href="#section-8.6-4" class="pilcrow">¶</a></p>
<div class="alignLeft art-text artwork" id="section-8.6-5">
<pre>
{
"type": "string",
"contentMediaType": "text/html"
}
</pre><a href="#section-8.6-5" class="pilcrow">¶</a>
</div>
<p id="section-8.6-6" class="keepWithPrevious">
Instances described by this schema are expected to be strings containing HTML,
using whatever character set the JSON string was decoded into.
Per section 8.1 of
<span><a href="#RFC8259" class="xref">RFC 8259</a> [<a href="#RFC8259" class="xref">RFC8259</a>]</span>, outside of an entirely closed
system, this MUST be UTF-8.<a href="#section-8.6-6" class="pilcrow">¶</a></p>
<p id="section-8.6-7" class="keepWithNext">
This example describes a JWT that is MACed using the HMAC SHA-256
algorithm, and requires the "iss" and "exp" fields in its claim set.<a href="#section-8.6-7" class="pilcrow">¶</a></p>
<div class="alignLeft art-text artwork" id="section-8.6-8">
<pre>
{
"type": "string",
"contentMediaType": "application/jwt",
"contentSchema": {
"type": "array",
"minItems": 2,
"prefixItems": [
{
"const": {
"typ": "JWT",
"alg": "HS256"
}
},
{
"type": "object",
"required": ["iss", "exp"],
"properties": {
"iss": {"type": "string"},
"exp": {"type": "integer"}
}
}
]
}
}
</pre><a href="#section-8.6-8" class="pilcrow">¶</a>
</div>
<p id="section-8.6-9" class="keepWithPrevious">
Note that "contentEncoding" does not appear. While the "application/jwt"
media type makes use of base64url encoding, that is defined by the media
type, which determines how the JWT string is decoded into a list of two
JSON data structures: first the header, and then the payload. Since the
JWT media type ensures that the JWT can be represented in a JSON string,
there is no need for further encoding or decoding.<a href="#section-8.6-9" class="pilcrow">¶</a></p>
</section>
</section>
</div>
<section id="section-9">
<h2 id="name-a-vocabulary-for-basic-meta">
<a href="#section-9" class="section-number selfRef">9. </a><a href="#name-a-vocabulary-for-basic-meta" class="section-name selfRef">A Vocabulary for Basic Meta-Data Annotations</a>
</h2>
<p id="section-9-1">
These general-purpose annotation keywords provide commonly used information
for documentation and user interface display purposes. They are not intended
to form a comprehensive set of features. Rather, additional vocabularies
can be defined for more complex annotation-based applications.<a href="#section-9-1" class="pilcrow">¶</a></p>
<p id="section-9-2">
Meta-schemas that do not use "$vocabulary" SHOULD be considered to
require this vocabulary as if its URI were present with a value of true.<a href="#section-9-2" class="pilcrow">¶</a></p>
<p id="section-9-3">
The current URI for this vocabulary, known as the Meta-Data vocabulary, is:
<https://json-schema.org/draft/2020-12/vocab/meta-data>.<a href="#section-9-3" class="pilcrow">¶</a></p>
<p id="section-9-4">
The current URI for the corresponding meta-schema is:
<span><a href="https://json-schema.org/draft/2020-12/meta/meta-data">https://json-schema.org/draft/2020-12/meta/meta-data</a></span>.<a href="#section-9-4" class="pilcrow">¶</a></p>
<section id="section-9.1">
<h3 id="name-title-and-description">
<a href="#section-9.1" class="section-number selfRef">9.1. </a><a href="#name-title-and-description" class="section-name selfRef">"title" and "description"</a>
</h3>
<p id="section-9.1-1">
The value of both of these keywords MUST be a string.<a href="#section-9.1-1" class="pilcrow">¶</a></p>
<p id="section-9.1-2">
Both of these keywords can be used to decorate a user interface with
information about the data produced by this user interface. A title will
preferably be short, whereas a description will provide explanation about
the purpose of the instance described by this schema.<a href="#section-9.1-2" class="pilcrow">¶</a></p>
</section>
<section id="section-9.2">
<h3 id="name-default">
<a href="#section-9.2" class="section-number selfRef">9.2. </a><a href="#name-default" class="section-name selfRef">"default"</a>
</h3>
<p id="section-9.2-1">
There are no restrictions placed on the value of this keyword. When
multiple occurrences of this keyword are applicable to a single
sub-instance, implementations SHOULD remove duplicates.<a href="#section-9.2-1" class="pilcrow">¶</a></p>
<p id="section-9.2-2">
This keyword can be used to supply a default JSON value associated with a
particular schema. It is RECOMMENDED that a default value be valid against
the associated schema.<a href="#section-9.2-2" class="pilcrow">¶</a></p>
</section>
<section id="section-9.3">
<h3 id="name-deprecated">
<a href="#section-9.3" class="section-number selfRef">9.3. </a><a href="#name-deprecated" class="section-name selfRef">"deprecated"</a>
</h3>
<p id="section-9.3-1">
The value of this keyword MUST be a boolean. When multiple occurrences
of this keyword are applicable to a single sub-instance, applications
SHOULD consider the instance location to be deprecated if any occurrence
specifies a true value.<a href="#section-9.3-1" class="pilcrow">¶</a></p>
<p id="section-9.3-2">
If "deprecated" has a value of boolean true, it indicates that applications
SHOULD refrain from usage of the declared property. It MAY mean the property
is going to be removed in the future.<a href="#section-9.3-2" class="pilcrow">¶</a></p>
<p id="section-9.3-3">
A root schema containing "deprecated" with a value of true indicates that
the entire resource being described MAY be removed in the future.<a href="#section-9.3-3" class="pilcrow">¶</a></p>
<p id="section-9.3-4">
The "deprecated" keyword applies to each instance location to which the
schema object containing the keyword successfully applies. This can
result in scenarios where every array item or object property
is deprecated even though the containing array or object is not.<a href="#section-9.3-4" class="pilcrow">¶</a></p>
<p id="section-9.3-5">
Omitting this keyword has the same behavior as a value of false.<a href="#section-9.3-5" class="pilcrow">¶</a></p>
</section>
<section id="section-9.4">
<h3 id="name-readonly-and-writeonly">
<a href="#section-9.4" class="section-number selfRef">9.4. </a><a href="#name-readonly-and-writeonly" class="section-name selfRef">"readOnly" and "writeOnly"</a>
</h3>
<p id="section-9.4-1">
The value of these keywords MUST be a boolean. When multiple occurrences
of these keywords are applicable to a single sub-instance, the resulting
behavior SHOULD be as for a true value if any occurrence specifies a true value,
and SHOULD be as for a false value otherwise.<a href="#section-9.4-1" class="pilcrow">¶</a></p>
<p id="section-9.4-2">
If "readOnly" has a value of boolean true, it indicates that the value
of the instance is managed exclusively by the owning authority, and
attempts by an application to modify the value of this property are
expected to be ignored or rejected by that owning authority.<a href="#section-9.4-2" class="pilcrow">¶</a></p>
<p id="section-9.4-3">
An instance document that is marked as "readOnly" for the entire document
MAY be ignored if sent to the owning authority, or MAY result in an
error, at the authority's discretion.<a href="#section-9.4-3" class="pilcrow">¶</a></p>
<p id="section-9.4-4">
If "writeOnly" has a value of boolean true, it indicates that the value
is never present when the instance is retrieved from the owning authority.
It can be present when sent to the owning authority to update or create
the document (or the resource it represents), but it will not be included
in any updated or newly created version of the instance.<a href="#section-9.4-4" class="pilcrow">¶</a></p>
<p id="section-9.4-5">
An instance document that is marked as "writeOnly" for the entire document
MAY be returned as a blank document of some sort, or MAY produce an error
upon retrieval, or have the retrieval request ignored, at the authority's
discretion.<a href="#section-9.4-5" class="pilcrow">¶</a></p>
<p id="section-9.4-6">
For example, "readOnly" would be used to mark a database-generated serial
number as read-only, while "writeOnly" would be used to mark a password
input field.<a href="#section-9.4-6" class="pilcrow">¶</a></p>
<p id="section-9.4-7">
These keywords can be used to assist in user interface instance generation.
In particular, an application MAY choose to use a widget that hides
input values as they are typed for write-only fields.<a href="#section-9.4-7" class="pilcrow">¶</a></p>
<p id="section-9.4-8">
Omitting these keywords has the same behavior as values of false.<a href="#section-9.4-8" class="pilcrow">¶</a></p>
</section>
<section id="section-9.5">
<h3 id="name-examples">
<a href="#section-9.5" class="section-number selfRef">9.5. </a><a href="#name-examples" class="section-name selfRef">"examples"</a>
</h3>
<p id="section-9.5-1">
The value of this keyword MUST be an array.
There are no restrictions placed on the values within the array.
When multiple occurrences of this keyword are applicable to a single
sub-instance, implementations MUST provide a flat array of all
values rather than an array of arrays.<a href="#section-9.5-1" class="pilcrow">¶</a></p>
<p id="section-9.5-2">
This keyword can be used to provide sample JSON values associated with a
particular schema, for the purpose of illustrating usage. It is
RECOMMENDED that these values be valid against the associated schema.<a href="#section-9.5-2" class="pilcrow">¶</a></p>
<p id="section-9.5-3">
Implementations MAY use the value(s) of "default", if present, as
an additional example. If "examples" is absent, "default"
MAY still be used in this manner.<a href="#section-9.5-3" class="pilcrow">¶</a></p>
</section>
</section>
<div id="security">
<section id="section-10">
<h2 id="name-security-considerations">
<a href="#section-10" class="section-number selfRef">10. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a>
</h2>
<p id="section-10-1">
JSON Schema validation defines a vocabulary for JSON Schema core and concerns all
the security considerations listed there.<a href="#section-10-1" class="pilcrow">¶</a></p>
<p id="section-10-2">
JSON Schema validation allows the use of Regular Expressions, which have numerous
different (often incompatible) implementations.
Some implementations allow the embedding of arbitrary code, which is outside the
scope of JSON Schema and MUST NOT be permitted.
Regular expressions can often also be crafted to be extremely expensive to compute
(with so-called "catastrophic backtracking"), resulting in a denial-of-service
attack.<a href="#section-10-2" class="pilcrow">¶</a></p>
<p id="section-10-3">
Implementations that support validating or otherwise evaluating instance
string data based on "contentEncoding" and/or "contentMediaType" are at
risk of evaluating data in an unsafe way based on misleading information.
Applications can mitigate this risk by only performing such processing
when a relationship between the schema and instance is established
(e.g., they share the same authority).<a href="#section-10-3" class="pilcrow">¶</a></p>
<p id="section-10-4">
Processing a media type or encoding is subject to the security considerations
of that media type or encoding. For example, the security considerations
of <span><a href="#RFC4329" class="xref">RFC 4329 Scripting Media Types</a> [<a href="#RFC4329" class="xref">RFC4329</a>]</span> apply when
processing JavaScript or ECMAScript encoded within a JSON string.<a href="#section-10-4" class="pilcrow">¶</a></p>
</section>
</div>
<section id="section-11">
<h2 id="name-references">
<a href="#section-11" class="section-number selfRef">11. </a><a href="#name-references" class="section-name selfRef">References</a>
</h2>
<section id="section-11.1">
<h3 id="name-normative-references">
<a href="#section-11.1" class="section-number selfRef">11.1. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a>
</h3>
<dl class="references">
<dt id="RFC2119">[RFC2119]</dt>
<dd>
<span class="refAuthor">Bradner, S.</span>, <span class="refTitle">"Key words for use in RFCs to Indicate Requirement Levels"</span>, <span class="seriesInfo">BCP 14</span>, <span class="seriesInfo">RFC 2119</span>, <span class="seriesInfo">DOI 10.17487/RFC2119</span>, <time datetime="1997-03" class="refDate">March 1997</time>, <span><<a href="https://www.rfc-editor.org/info/rfc2119">https://www.rfc-editor.org/info/rfc2119</a>></span>. </dd>
<dd class="break"></dd>
<dt id="RFC1123">[RFC1123]</dt>
<dd>
<span class="refAuthor">Braden, R., Ed.</span>, <span class="refTitle">"Requirements for Internet Hosts - Application and Support"</span>, <span class="seriesInfo">STD 3</span>, <span class="seriesInfo">RFC 1123</span>, <span class="seriesInfo">DOI 10.17487/RFC1123</span>, <time datetime="1989-10" class="refDate">October 1989</time>, <span><<a href="https://www.rfc-editor.org/info/rfc1123">https://www.rfc-editor.org/info/rfc1123</a>></span>. </dd>
<dd class="break"></dd>
<dt id="RFC2045">[RFC2045]</dt>
<dd>
<span class="refAuthor">Freed, N.</span> and <span class="refAuthor">N. Borenstein</span>, <span class="refTitle">"Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies"</span>, <span class="seriesInfo">RFC 2045</span>, <span class="seriesInfo">DOI 10.17487/RFC2045</span>, <time datetime="1996-11" class="refDate">November 1996</time>, <span><<a href="https://www.rfc-editor.org/info/rfc2045">https://www.rfc-editor.org/info/rfc2045</a>></span>. </dd>
<dd class="break"></dd>
<dt id="RFC2046">[RFC2046]</dt>
<dd>
<span class="refAuthor">Freed, N.</span> and <span class="refAuthor">N. Borenstein</span>, <span class="refTitle">"Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types"</span>, <span class="seriesInfo">RFC 2046</span>, <span class="seriesInfo">DOI 10.17487/RFC2046</span>, <time datetime="1996-11" class="refDate">November 1996</time>, <span><<a href="https://www.rfc-editor.org/info/rfc2046">https://www.rfc-editor.org/info/rfc2046</a>></span>. </dd>
<dd class="break"></dd>
<dt id="RFC2673">[RFC2673]</dt>
<dd>
<span class="refAuthor">Crawford, M.</span>, <span class="refTitle">"Binary Labels in the Domain Name System"</span>, <span class="seriesInfo">RFC 2673</span>, <span class="seriesInfo">DOI 10.17487/RFC2673</span>, <time datetime="1999-08" class="refDate">August 1999</time>, <span><<a href="https://www.rfc-editor.org/info/rfc2673">https://www.rfc-editor.org/info/rfc2673</a>></span>. </dd>
<dd class="break"></dd>
<dt id="RFC3339">[RFC3339]</dt>
<dd>
<span class="refAuthor">Klyne, G.</span> and <span class="refAuthor">C. Newman</span>, <span class="refTitle">"Date and Time on the Internet: Timestamps"</span>, <span class="seriesInfo">RFC 3339</span>, <span class="seriesInfo">DOI 10.17487/RFC3339</span>, <time datetime="2002-07" class="refDate">July 2002</time>, <span><<a href="https://www.rfc-editor.org/info/rfc3339">https://www.rfc-editor.org/info/rfc3339</a>></span>. </dd>
<dd class="break"></dd>
<dt id="RFC3986">[RFC3986]</dt>
<dd>
<span class="refAuthor">Berners-Lee, T.</span>, <span class="refAuthor">Fielding, R.</span>, and <span class="refAuthor">L. Masinter</span>, <span class="refTitle">"Uniform Resource Identifier (URI): Generic Syntax"</span>, <span class="seriesInfo">STD 66</span>, <span class="seriesInfo">RFC 3986</span>, <span class="seriesInfo">DOI 10.17487/RFC3986</span>, <time datetime="2005-01" class="refDate">January 2005</time>, <span><<a href="https://www.rfc-editor.org/info/rfc3986">https://www.rfc-editor.org/info/rfc3986</a>></span>. </dd>
<dd class="break"></dd>
<dt id="RFC3987">[RFC3987]</dt>
<dd>
<span class="refAuthor">Duerst, M.</span> and <span class="refAuthor">M. Suignard</span>, <span class="refTitle">"Internationalized Resource Identifiers (IRIs)"</span>, <span class="seriesInfo">RFC 3987</span>, <span class="seriesInfo">DOI 10.17487/RFC3987</span>, <time datetime="2005-01" class="refDate">January 2005</time>, <span><<a href="https://www.rfc-editor.org/info/rfc3987">https://www.rfc-editor.org/info/rfc3987</a>></span>. </dd>
<dd class="break"></dd>
<dt id="RFC4122">[RFC4122]</dt>
<dd>
<span class="refAuthor">Leach, P.</span>, <span class="refAuthor">Mealling, M.</span>, and <span class="refAuthor">R. Salz</span>, <span class="refTitle">"A Universally Unique IDentifier (UUID) URN Namespace"</span>, <span class="seriesInfo">RFC 4122</span>, <span class="seriesInfo">DOI 10.17487/RFC4122</span>, <time datetime="2005-07" class="refDate">July 2005</time>, <span><<a href="https://www.rfc-editor.org/info/rfc4122">https://www.rfc-editor.org/info/rfc4122</a>></span>. </dd>
<dd class="break"></dd>
<dt id="RFC4291">[RFC4291]</dt>
<dd>
<span class="refAuthor">Hinden, R.</span> and <span class="refAuthor">S. Deering</span>, <span class="refTitle">"IP Version 6 Addressing Architecture"</span>, <span class="seriesInfo">RFC 4291</span>, <span class="seriesInfo">DOI 10.17487/RFC4291</span>, <time datetime="2006-02" class="refDate">February 2006</time>, <span><<a href="https://www.rfc-editor.org/info/rfc4291">https://www.rfc-editor.org/info/rfc4291</a>></span>. </dd>
<dd class="break"></dd>
<dt id="RFC4648">[RFC4648]</dt>
<dd>
<span class="refAuthor">Josefsson, S.</span>, <span class="refTitle">"The Base16, Base32, and Base64 Data Encodings"</span>, <span class="seriesInfo">RFC 4648</span>, <span class="seriesInfo">DOI 10.17487/RFC4648</span>, <time datetime="2006-10" class="refDate">October 2006</time>, <span><<a href="https://www.rfc-editor.org/info/rfc4648">https://www.rfc-editor.org/info/rfc4648</a>></span>. </dd>
<dd class="break"></dd>
<dt id="RFC5321">[RFC5321]</dt>
<dd>
<span class="refAuthor">Klensin, J.</span>, <span class="refTitle">"Simple Mail Transfer Protocol"</span>, <span class="seriesInfo">RFC 5321</span>, <span class="seriesInfo">DOI 10.17487/RFC5321</span>, <time datetime="2008-10" class="refDate">October 2008</time>, <span><<a href="https://www.rfc-editor.org/info/rfc5321">https://www.rfc-editor.org/info/rfc5321</a>></span>. </dd>
<dd class="break"></dd>
<dt id="RFC5890">[RFC5890]</dt>
<dd>
<span class="refAuthor">Klensin, J.</span>, <span class="refTitle">"Internationalized Domain Names for Applications (IDNA): Definitions and Document Framework"</span>, <span class="seriesInfo">RFC 5890</span>, <span class="seriesInfo">DOI 10.17487/RFC5890</span>, <time datetime="2010-08" class="refDate">August 2010</time>, <span><<a href="https://www.rfc-editor.org/info/rfc5890">https://www.rfc-editor.org/info/rfc5890</a>></span>. </dd>
<dd class="break"></dd>
<dt id="RFC5891">[RFC5891]</dt>
<dd>
<span class="refAuthor">Klensin, J.</span>, <span class="refTitle">"Internationalized Domain Names in Applications (IDNA): Protocol"</span>, <span class="seriesInfo">RFC 5891</span>, <span class="seriesInfo">DOI 10.17487/RFC5891</span>, <time datetime="2010-08" class="refDate">August 2010</time>, <span><<a href="https://www.rfc-editor.org/info/rfc5891">https://www.rfc-editor.org/info/rfc5891</a>></span>. </dd>
<dd class="break"></dd>
<dt id="RFC6570">[RFC6570]</dt>
<dd>
<span class="refAuthor">Gregorio, J.</span>, <span class="refAuthor">Fielding, R.</span>, <span class="refAuthor">Hadley, M.</span>, <span class="refAuthor">Nottingham, M.</span>, and <span class="refAuthor">D. Orchard</span>, <span class="refTitle">"URI Template"</span>, <span class="seriesInfo">RFC 6570</span>, <span class="seriesInfo">DOI 10.17487/RFC6570</span>, <time datetime="2012-03" class="refDate">March 2012</time>, <span><<a href="https://www.rfc-editor.org/info/rfc6570">https://www.rfc-editor.org/info/rfc6570</a>></span>. </dd>
<dd class="break"></dd>
<dt id="RFC6531">[RFC6531]</dt>
<dd>
<span class="refAuthor">Yao, J.</span> and <span class="refAuthor">W. Mao</span>, <span class="refTitle">"SMTP Extension for Internationalized Email"</span>, <span class="seriesInfo">RFC 6531</span>, <span class="seriesInfo">DOI 10.17487/RFC6531</span>, <time datetime="2012-02" class="refDate">February 2012</time>, <span><<a href="https://www.rfc-editor.org/info/rfc6531">https://www.rfc-editor.org/info/rfc6531</a>></span>. </dd>
<dd class="break"></dd>
<dt id="RFC6901">[RFC6901]</dt>
<dd>
<span class="refAuthor">Bryan, P., Ed.</span>, <span class="refAuthor">Zyp, K.</span>, and <span class="refAuthor">M. Nottingham, Ed.</span>, <span class="refTitle">"JavaScript Object Notation (JSON) Pointer"</span>, <span class="seriesInfo">RFC 6901</span>, <span class="seriesInfo">DOI 10.17487/RFC6901</span>, <time datetime="2013-04" class="refDate">April 2013</time>, <span><<a href="https://www.rfc-editor.org/info/rfc6901">https://www.rfc-editor.org/info/rfc6901</a>></span>. </dd>
<dd class="break"></dd>
<dt id="RFC8259">[RFC8259]</dt>
<dd>
<span class="refAuthor">Bray, T., Ed.</span>, <span class="refTitle">"The JavaScript Object Notation (JSON) Data Interchange Format"</span>, <span class="seriesInfo">STD 90</span>, <span class="seriesInfo">RFC 8259</span>, <span class="seriesInfo">DOI 10.17487/RFC8259</span>, <time datetime="2017-12" class="refDate">December 2017</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8259">https://www.rfc-editor.org/info/rfc8259</a>></span>. </dd>
<dd class="break"></dd>
<dt id="ecma262">[ecma262]</dt>
<dd>
<span class="refTitle">"ECMA-262, 11th edition specification"</span>, <time datetime="2020-06" class="refDate">June 2020</time>, <span><<a href="https://www.ecma-international.org/ecma-262/11.0">https://www.ecma-international.org/ecma-262/11.0</a>></span>. </dd>
<dd class="break"></dd>
<dt id="relative-json-pointer">[relative-json-pointer]</dt>
<dd>
<span class="refAuthor">Luff, G.</span>, <span class="refAuthor">Andrews, H.</span>, and <span class="refAuthor">B. Hutton, Ed.</span>, <span class="refTitle">"Relative JSON Pointers"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-handrews-relative-json-pointer-01</span>, <time datetime="2020-12" class="refDate">December 2020</time>, <span><<a href="https://datatracker.ietf.org/doc/html/draft-handrews-relative-json-pointer-01">https://datatracker.ietf.org/doc/html/draft-handrews-relative-json-pointer-01</a>></span>. </dd>
<dd class="break"></dd>
<dt id="json-schema">[json-schema]</dt>
<dd>
<span class="refAuthor">Wright, A.</span>, <span class="refAuthor">Andrews, H.</span>, <span class="refAuthor">Hutton, B.</span>, and <span class="refAuthor">G. Dennis</span>, <span class="refTitle">"JSON Schema: A Media Type for Describing JSON Documents"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-bhutton-json-schema-01</span>, <time datetime="2022-06" class="refDate">June 2022</time>, <span><<a href="https://datatracker.ietf.org/doc/html/draft-bhutton-json-schema-01">https://datatracker.ietf.org/doc/html/draft-bhutton-json-schema-01</a>></span>. </dd>
<dd class="break"></dd>
</dl>
</section>
<section id="section-11.2">
<h3 id="name-informative-references">
<a href="#section-11.2" class="section-number selfRef">11.2. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a>
</h3>
<dl class="references">
<dt id="RFC4329">[RFC4329]</dt>
<dd>
<span class="refAuthor">Hoehrmann, B.</span>, <span class="refTitle">"Scripting Media Types"</span>, <span class="seriesInfo">RFC 4329</span>, <span class="seriesInfo">DOI 10.17487/RFC4329</span>, <time datetime="2006-04" class="refDate">April 2006</time>, <span><<a href="https://www.rfc-editor.org/info/rfc4329">https://www.rfc-editor.org/info/rfc4329</a>></span>. </dd>
<dd class="break"></dd>
</dl>
</section>
</section>
<section id="appendix-A">
<h2 id="name-keywords-moved-from-validat">
<a href="#appendix-A" class="section-number selfRef">Appendix A. </a><a href="#name-keywords-moved-from-validat" class="section-name selfRef">Keywords Moved from Validation to Core</a>
</h2>
<p id="appendix-A-1">
Several keywords have been moved from this document into the
<span><a href="#json-schema" class="xref">Core Specification</a> [<a href="#json-schema" class="xref">json-schema</a>]</span> as of this draft, in some
cases with re-naming or other changes. This affects the following former
validation keywords:<a href="#appendix-A-1" class="pilcrow">¶</a></p>
<span class="break"></span><dl class="dlParallel" id="appendix-A-2">
<dt id="appendix-A-2.1">"definitions"</dt>
<dd style="margin-left: 1.5em" id="appendix-A-2.2">
Renamed to "$defs" to match "$ref" and be shorter to type.
Schema vocabulary authors SHOULD NOT define a "definitions" keyword
with different behavior in order to avoid invalidating schemas that
still use the older name. While "definitions" is absent in the
single-vocabulary meta-schemas referenced by this document, it
remains present in the default meta-schema, and implementations
SHOULD assume that "$defs" and "definitions" have the same
behavior when that meta-schema is used.<a href="#appendix-A-2.2" class="pilcrow">¶</a>
</dd>
<dd class="break"></dd>
<dt id="appendix-A-2.3">"allOf", "anyOf", "oneOf", "not", "if", "then", "else", "items", "additionalItems", "contains", "propertyNames", "properties", "patternProperties", "additionalProperties"</dt>
<dd style="margin-left: 1.5em" id="appendix-A-2.4">
All of these keywords apply subschemas to the instance and combine
their results, without asserting any conditions of their own.
Without assertion keywords, these applicators can only cause assertion
failures by using the false boolean schema, or by inverting the result
of the true boolean schema (or equivalent schema objects).
For this reason, they are better defined as a generic mechanism on which
validation, hyper-schema, and extension vocabularies can all be based.<a href="#appendix-A-2.4" class="pilcrow">¶</a>
</dd>
<dd class="break"></dd>
<dt id="appendix-A-2.5">"dependencies"</dt>
<dd style="margin-left: 1.5em" id="appendix-A-2.6">
This keyword had two different modes of behavior, which made it
relatively challenging to implement and reason about.
The schema form has been moved to Core and renamed to
"dependentSchemas", as part of the applicator vocabulary.
It is analogous to "properties", except that instead of applying
its subschema to the property value, it applies it to the object
containing the property.
The property name array form is retained here and renamed to
"dependentRequired", as it is an assertion which is a shortcut
for the conditional use of the "required" assertion keyword.<a href="#appendix-A-2.6" class="pilcrow">¶</a>
</dd>
<dd class="break"></dd>
</dl>
</section>
<section id="appendix-B">
<h2 id="name-acknowledgments">
<a href="#appendix-B" class="section-number selfRef">Appendix B. </a><a href="#name-acknowledgments" class="section-name selfRef">Acknowledgments</a>
</h2>
<p id="appendix-B-1">
Thanks to
Gary Court,
Francis Galiegue,
Kris Zyp,
and Geraint Luff
for their work on the initial drafts of JSON Schema.<a href="#appendix-B-1" class="pilcrow">¶</a></p>
<p id="appendix-B-2">
Thanks to
Jason Desrosiers,
Daniel Perrett,
Erik Wilde,
Evgeny Poberezkin,
Brad Bowman,
Gowry Sankar,
Donald Pipowitch,
Dave Finlay,
Denis Laxalde,
Phil Sturgeon,
Shawn Silverman,
and Karen Etheridge
for their submissions and patches to the document.<a href="#appendix-B-2" class="pilcrow">¶</a></p>
</section>
<section id="appendix-C">
<h2 id="name-changelog">
<a href="#appendix-C" class="section-number selfRef">Appendix C. </a><a href="#name-changelog" class="section-name selfRef">ChangeLog</a>
</h2>
<p id="appendix-C-1">
<span class="cref">This section to be removed before leaving Internet-Draft status.</span><a href="#appendix-C-1" class="pilcrow">¶</a></p>
<span class="break"></span><dl class="dlParallel" id="appendix-C-2">
<dt id="appendix-C-2.1">draft-bhutton-json-schema-validation-01</dt>
<dd style="margin-left: 1.5em" id="appendix-C-2.2">
<ul class="normal">
<li class="normal" id="appendix-C-2.2.1.1">Improve and clarify the "minContains" keyword explanation<a href="#appendix-C-2.2.1.1" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.2.1.2">Remove the use of "production" in favour of "ABNF rule"<a href="#appendix-C-2.2.1.2" class="pilcrow">¶</a>
</li>
</ul>
</dd>
<dd class="break"></dd>
<dt id="appendix-C-2.3">draft-bhutton-json-schema-validation-00</dt>
<dd style="margin-left: 1.5em" id="appendix-C-2.4">
<ul class="normal">
<li class="normal" id="appendix-C-2.4.1.1">Correct email format RFC reference to 5321 instead of 5322<a href="#appendix-C-2.4.1.1" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.4.1.2">Clarified the set and meaning of "contentEncoding" values<a href="#appendix-C-2.4.1.2" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.4.1.3">Reference ECMA-262, 11th edition for regular expression support<a href="#appendix-C-2.4.1.3" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.4.1.4">Split "format" into an annotation only vocabulary and an assertion vocabulary<a href="#appendix-C-2.4.1.4" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.4.1.5">Clarify "deprecated" when applicable to arrays<a href="#appendix-C-2.4.1.5" class="pilcrow">¶</a>
</li>
</ul>
</dd>
<dd class="break"></dd>
<dt id="appendix-C-2.5">draft-handrews-json-schema-validation-02</dt>
<dd style="margin-left: 1.5em" id="appendix-C-2.6">
<ul class="normal">
<li class="normal" id="appendix-C-2.6.1.1">Grouped keywords into formal vocabularies<a href="#appendix-C-2.6.1.1" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.6.1.2">Update "format" implementation requirements in terms of vocabularies<a href="#appendix-C-2.6.1.2" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.6.1.3">By default, "format" MUST NOT be validated, although validation can be enabled<a href="#appendix-C-2.6.1.3" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.6.1.4">A vocabulary declaration can be used to require "format" validation<a href="#appendix-C-2.6.1.4" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.6.1.5">Moved "definitions" to the core spec as "$defs"<a href="#appendix-C-2.6.1.5" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.6.1.6">Moved applicator keywords to the core spec<a href="#appendix-C-2.6.1.6" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.6.1.7">Renamed the array form of "dependencies" to "dependentRequired", moved the schema form to the core spec<a href="#appendix-C-2.6.1.7" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.6.1.8">Specified all "content*" keywords as annotations, not assertions<a href="#appendix-C-2.6.1.8" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.6.1.9">Added "contentSchema" to allow applying a schema to a string-encoded document<a href="#appendix-C-2.6.1.9" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.6.1.10">Also allow RFC 4648 encodings in "contentEncoding"<a href="#appendix-C-2.6.1.10" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.6.1.11">Added "minContains" and "maxContains"<a href="#appendix-C-2.6.1.11" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.6.1.12">Update RFC reference for "hostname" and "idn-hostname"<a href="#appendix-C-2.6.1.12" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.6.1.13">Add "uuid" and "duration" formats<a href="#appendix-C-2.6.1.13" class="pilcrow">¶</a>
</li>
</ul>
</dd>
<dd class="break"></dd>
<dt id="appendix-C-2.7">draft-handrews-json-schema-validation-01</dt>
<dd style="margin-left: 1.5em" id="appendix-C-2.8">
<ul class="normal">
<li class="normal" id="appendix-C-2.8.1.1">This draft is purely a clarification with no functional changes<a href="#appendix-C-2.8.1.1" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.8.1.2">Provided the general principle behind ignoring annotations under "not" and similar cases<a href="#appendix-C-2.8.1.2" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.8.1.3">Clarified "if"/"then"/"else" validation interactions<a href="#appendix-C-2.8.1.3" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.8.1.4">Clarified "if"/"then"/"else" behavior for annotation<a href="#appendix-C-2.8.1.4" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.8.1.5">Minor formatting and cross-referencing improvements<a href="#appendix-C-2.8.1.5" class="pilcrow">¶</a>
</li>
</ul>
</dd>
<dd class="break"></dd>
<dt id="appendix-C-2.9">draft-handrews-json-schema-validation-00</dt>
<dd style="margin-left: 1.5em" id="appendix-C-2.10">
<ul class="normal">
<li class="normal" id="appendix-C-2.10.1.1">Added "if"/"then"/"else"<a href="#appendix-C-2.10.1.1" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.10.1.2">Classify keywords as assertions or annotations per the core spec<a href="#appendix-C-2.10.1.2" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.10.1.3">Warn of possibly removing "dependencies" in the future<a href="#appendix-C-2.10.1.3" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.10.1.4">Grouped validation keywords into sub-sections for readability<a href="#appendix-C-2.10.1.4" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.10.1.5">Moved "readOnly" from hyper-schema to validation meta-data<a href="#appendix-C-2.10.1.5" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.10.1.6">Added "writeOnly"<a href="#appendix-C-2.10.1.6" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.10.1.7">Added string-encoded media section, with former hyper-schema "media" keywords<a href="#appendix-C-2.10.1.7" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.10.1.8">Restored "regex" format (removal was unintentional)<a href="#appendix-C-2.10.1.8" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.10.1.9">Added "date" and "time" formats, and reserved additional RFC 3339 format names<a href="#appendix-C-2.10.1.9" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.10.1.10">I18N formats: "iri", "iri-reference", "idn-hostname", "idn-email"<a href="#appendix-C-2.10.1.10" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.10.1.11">Clarify that "json-pointer" format means string encoding, not URI fragment<a href="#appendix-C-2.10.1.11" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.10.1.12">Fixed typo that inverted the meaning of "minimum" and "exclusiveMinimum"<a href="#appendix-C-2.10.1.12" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.10.1.13">Move format syntax references into Normative References<a href="#appendix-C-2.10.1.13" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.10.1.14">JSON is a normative requirement<a href="#appendix-C-2.10.1.14" class="pilcrow">¶</a>
</li>
</ul>
</dd>
<dd class="break"></dd>
<dt id="appendix-C-2.11">draft-wright-json-schema-validation-01</dt>
<dd style="margin-left: 1.5em" id="appendix-C-2.12">
<ul class="normal">
<li class="normal" id="appendix-C-2.12.1.1">Standardized on hyphenated format names with full words ("uriref" becomes "uri-reference")<a href="#appendix-C-2.12.1.1" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.12.1.2">Add the formats "uri-template" and "json-pointer"<a href="#appendix-C-2.12.1.2" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.12.1.3">Changed "exclusiveMaximum"/"exclusiveMinimum" from boolean modifiers of "maximum"/"minimum" to independent numeric fields.<a href="#appendix-C-2.12.1.3" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.12.1.4">Split the additionalItems/items into two sections<a href="#appendix-C-2.12.1.4" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.12.1.5">Reworked properties/patternProperties/additionalProperties definition<a href="#appendix-C-2.12.1.5" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.12.1.6">Added "examples" keyword<a href="#appendix-C-2.12.1.6" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.12.1.7">Added "contains" keyword<a href="#appendix-C-2.12.1.7" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.12.1.8">Allow empty "required" and "dependencies" arrays<a href="#appendix-C-2.12.1.8" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.12.1.9">Fixed "type" reference to primitive types<a href="#appendix-C-2.12.1.9" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.12.1.10">Added "const" keyword<a href="#appendix-C-2.12.1.10" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.12.1.11">Added "propertyNames" keyword<a href="#appendix-C-2.12.1.11" class="pilcrow">¶</a>
</li>
</ul>
</dd>
<dd class="break"></dd>
<dt id="appendix-C-2.13">draft-wright-json-schema-validation-00</dt>
<dd style="margin-left: 1.5em" id="appendix-C-2.14">
<ul class="normal">
<li class="normal" id="appendix-C-2.14.1.1">Added additional security considerations<a href="#appendix-C-2.14.1.1" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.14.1.2">Removed reference to "latest version" meta-schema, use numbered version instead<a href="#appendix-C-2.14.1.2" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.14.1.3">Rephrased many keyword definitions for brevity<a href="#appendix-C-2.14.1.3" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.14.1.4">Added "uriref" format that also allows relative URI references<a href="#appendix-C-2.14.1.4" class="pilcrow">¶</a>
</li>
</ul>
</dd>
<dd class="break"></dd>
<dt id="appendix-C-2.15">draft-fge-json-schema-validation-00</dt>
<dd style="margin-left: 1.5em" id="appendix-C-2.16">
<ul class="normal">
<li class="normal" id="appendix-C-2.16.1.1">Initial draft.<a href="#appendix-C-2.16.1.1" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.16.1.2">Salvaged from draft v3.<a href="#appendix-C-2.16.1.2" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.16.1.3">Redefine the "required" keyword.<a href="#appendix-C-2.16.1.3" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.16.1.4">Remove "extends", "disallow"<a href="#appendix-C-2.16.1.4" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.16.1.5">Add "anyOf", "allOf", "oneOf", "not", "definitions", "minProperties",
"maxProperties".<a href="#appendix-C-2.16.1.5" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.16.1.6">"dependencies" member values can no longer be single strings; at
least one element is required in a property dependency array.<a href="#appendix-C-2.16.1.6" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.16.1.7">Rename "divisibleBy" to "multipleOf".<a href="#appendix-C-2.16.1.7" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.16.1.8">"type" arrays can no longer have schemas; remove "any" as a possible
value.<a href="#appendix-C-2.16.1.8" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.16.1.9">Rework the "format" section; make support optional.<a href="#appendix-C-2.16.1.9" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.16.1.10">"format": remove attributes "phone", "style", "color"; rename
"ip-address" to "ipv4"; add references for all attributes.<a href="#appendix-C-2.16.1.10" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.16.1.11">Provide algorithms to calculate schema(s) for array/object
instances.<a href="#appendix-C-2.16.1.11" class="pilcrow">¶</a>
</li>
<li class="normal" id="appendix-C-2.16.1.12">Add interoperability considerations.<a href="#appendix-C-2.16.1.12" class="pilcrow">¶</a>
</li>
</ul>
</dd>
<dd class="break"></dd>
</dl>
</section>
<div id="authors-addresses">
<section id="appendix-D">
<h2 id="name-authors-addresses">
<a href="#name-authors-addresses" class="section-name selfRef">Authors' Addresses</a>
</h2>
<address class="vcard">
<div dir="auto" class="left"><span class="fn nameRole">Austin Wright (<span class="role">editor</span>)</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:aaa@bzfx.net" class="email">aaa@bzfx.net</a>
</div>
</address>
<address class="vcard">
<div dir="auto" class="left"><span class="fn nameRole">Henry Andrews (<span class="role">editor</span>)</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:andrews_henry@yahoo.com" class="email">andrews_henry@yahoo.com</a>
</div>
</address>
<address class="vcard">
<div dir="auto" class="left"><span class="fn nameRole">Ben Hutton (<span class="role">editor</span>)</span></div>
<div dir="auto" class="left"><span class="org">Postman</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:ben@jsonschema.dev" class="email">ben@jsonschema.dev</a>
</div>
<div class="url">
<span>URI:</span>
<a href="https://jsonschema.dev" class="url">https://jsonschema.dev</a>
</div>
</address>
</section>
</div>
<script>const toc = document.getElementById("toc");
toc.querySelector("h2").addEventListener("click", e => {
toc.classList.toggle("active");
});
toc.querySelector("nav").addEventListener("click", e => {
toc.classList.remove("active");
});
</script>
</body>
</html>