You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+10-3Lines changed: 10 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -109,7 +109,7 @@ To test a specific version:
109
109
110
110
* For 2019-09 and later published drafts, implementations that are able to detect the draft of each schema via `$schema` SHOULD be configured to do so
111
111
* For draft-07 and earlier, draft-next, and implementations unable to detect via `$schema`, implementations MUST be configured to expect the draft matching the test directory name
112
-
* Load any remote references [described below](additional-assumptions) and configure your implementation to retrieve them via their URIs
112
+
* Load any remote references [described below](#additional-assumptions) and configure your implementation to retrieve them via their URIs
113
113
* Walk the filesystem tree for that version's subdirectory and for each `.json` file found:
114
114
115
115
* if the file is located in the root of the version directory:
@@ -159,7 +159,7 @@ If your implementation supports multiple versions, run the above procedure for e
159
159
```
160
160
161
161
2. Test cases found within [special subdirectories](#subdirectories-within-each-draft) may require additional configuration to run.
162
-
In particular, tests within the `optional/format` subdirectory may require implementations to change the way they treat the `"format"`keyword (particularly on older drafts which did not have a notion of vocabularies).
162
+
In particular, when running tests within the `optional/format` subdirectory, test runners should configure implementations to enable format validation, where the implementation supports it.
163
163
164
164
### Invariants & Guarantees
165
165
@@ -254,12 +254,14 @@ This suite is being used by:
254
254
255
255
### Java
256
256
257
+
*[json-schema-validation-comparison](https://www.creekservice.org/json-schema-validation-comparison/functional) (Comparison site for JVM-based validator implementations)
*[json-schema-validation-comparison](https://www.creekservice.org/json-schema-validation-comparison/functional) (Comparison site for JVM-based validator implementations)
287
+
282
288
### Node.js
283
289
284
290
For node.js developers, the suite is also available as an [npm](https://www.npmjs.com/package/@json-schema-org/tests) package.
@@ -313,7 +319,7 @@ Node-specific support is maintained in a [separate repository](https://github.co
@@ -327,6 +333,7 @@ Node-specific support is maintained in a [separate repository](https://github.co
327
333
328
334
### Scala
329
335
336
+
*[json-schema-validation-comparison](https://www.creekservice.org/json-schema-validation-comparison/functional) (Comparison site for JVM-based validator implementations)
0 commit comments