@@ -21,36 +21,12 @@ Advanced
21
21
--------
22
22
23
23
If you need to declare that your schema was written against a specific
24
- version of the JSON Schema standard, and not just the latest version,
25
- you can use one of these predefined values:
26
-
27
- - ``http://json-schema.org/schema# ``
28
-
29
- JSON Schema written against the current version of the
30
- specification.
31
-
32
- - ``http://json-schema.org/hyper-schema# ``
33
-
34
- JSON Schema hyperschema written against the current version of the
35
- specification.
24
+ version of the JSON Schema standard, you can include the draft name in the path, for example:
36
25
26
+ - ``http://json-schema.org/draft-06/schema# ``
37
27
- ``http://json-schema.org/draft-04/schema# ``
38
28
39
- JSON Schema written against this version.
40
-
41
- - ``http://json-schema.org/draft-04/hyper-schema# ``
42
-
43
- JSON Schema hyperschema written against this version.
44
-
45
- - ``http://json-schema.org/draft-03/schema# ``
46
-
47
- JSON Schema written against JSON Schema, draft v3
48
-
49
- - ``http://json-schema.org/draft-03/hyper-schema# ``
50
-
51
- JSON Schema hyperschema written against JSON Schema, draft v3
52
-
53
29
Additionally, if you have extended the JSON Schema language to include
54
30
your own custom keywords for validating values, you can use a custom
55
31
URI for ``$schema ``. It must not be one of the predefined values
56
- above.
32
+ above, and should probably include a domain name you own .
0 commit comments