Skip to content

Commit f098342

Browse files
committed
add section for format registry; add requirements to support those formats as well
1 parent b272d13 commit f098342

File tree

1 file changed

+11
-5
lines changed

1 file changed

+11
-5
lines changed

specs/jsonschema-validation.md

Lines changed: 11 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -334,10 +334,10 @@ an annotation.
334334

335335
Implementations:
336336

337-
- SHOULD provide validation for each format attribute defined in this
338-
document;
339-
- MAY support format values not defined in this document, but such support MUST
340-
be configurable and disabled by default;
337+
- SHOULD provide validation for each format attribute defined in this document
338+
and listed in the {{format-registry}};
339+
- MAY support format values not defined in this document or listed in the
340+
registry, but such support MUST be configurable and disabled by default;
341341
- SHOULD use a common parsing library or a well-known regular expression for
342342
each format;
343343
- SHOULD clearly document how and to what degree each format attribute is
@@ -348,7 +348,13 @@ syntactic checking; implementations SHOULD NOT attempt to send an email, connect
348348
to a URL, or otherwise check the existence of an entity identified by a format
349349
instance.
350350

351-
#### Custom format values
351+
#### Format Registry {#format-registry}
352+
353+
In addition to the formats defined by this document, JSON Schema also maintains a registry of formats defined by other specifications and organizations. As of the publication of this document, the format registry can be found at https://github.com/json-schema-org/json-schema-spec/blob/main/specs/format-registry.json.
354+
355+
Implementations SHOULD support the formats listed in this registry as if they were defined by this document.
356+
357+
#### Custom `format` Values
352358

353359
Implementations MAY support custom format values. Save for agreement between
354360
parties, schema authors SHALL NOT expect a peer implementation to support such

0 commit comments

Comments
 (0)