Skip to content

Commit f4bba48

Browse files
authored
Merge pull request #69 from agebhar1/feature/README
update Readme.md
2 parents c033bdd + 62c5712 commit f4bba48

File tree

1 file changed

+8
-7
lines changed

1 file changed

+8
-7
lines changed

README.md

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -12,22 +12,20 @@
1212
* [Resolution scopes](#resolution-scopes)
1313

1414

15-
This project is an implementation of the [JSON Schema Core Draft v4](http://json-schema.org/latest/json-schema-core.html) specification.
15+
This project is an implementation of the [JSON Schema Core Draft v4][draft-zyp-json-schema-04] specification.
1616
It uses the [org.json API](http://stleary.github.io/JSON-java/) (created by Douglas Crockford) for representing JSON data.
1717

1818
# When to use this library?
1919

2020
Lets assume that you already know what JSON Schema is, and you want to utilize it in a Java application to validate JSON data.
21-
But - as you may have already discovered - there is also an [other Java implementation](https://github.com/fge/json-schema-validator)
21+
But - as you may have already discovered - there is also an [other Java implementation][daveclayton/json-schema-validator]
2222
of the JSON Schema specification. So here are some advices about which one to use:
23-
* if you use Jackson to handle JSON in Java code, then fge/json-schema-validator is obviously a better choice, since it
24-
uses Jackson
23+
* if you use Jackson to handle JSON in Java code, then [daveclayton/json-schema-validator] is obviously a better choice, since it uses Jackson
2524
* if you want to use the [org.json API](http://www.json.org/java/) then this library is the better choice
2625
* if you want to use anything else for handling JSON (like GSON or javax.json), then you are in a little trouble, since
2726
currently there is no schema validation library backed by these libraries. It means that you will have to parse the JSON
2827
twice: once for the schema validator, and once for your own processing. In a case like that, this library is probably still
29-
a better choice, since it seems to be [twice faster](https://github.com/erosb/json-schema-perftest) than the Jackson-based fge
30-
library.
28+
a better choice, since it seems to be [twice faster](https://github.com/erosb/json-schema-perftest) than the Jackson-based [daveclayton][daveclayton/json-schema-validator] library.
3129

3230

3331
## Maven installation
@@ -165,7 +163,7 @@ following keys:
165163
## Format validators
166164

167165

168-
Starting from version `1.2.0` the library supports the [`"format"` keyword](http://json-schema.org/latest/json-schema-validation.html#anchor104)
166+
Starting from version `1.2.0` the library supports the [`"format"` keyword][draft-fge-json-schema-validation-00 format]
169167
(which is an optional part of the specification), so you can use the following formats in the schemas:
170168

171169
* date-time
@@ -235,3 +233,6 @@ SchemaLoader schemaLoader = SchemaLoader.builder()
235233
[ASL 2.0]: https://www.apache.org/licenses/LICENSE-2.0
236234
[Travis badge master]: https://travis-ci.org/everit-org/json-schema.svg?branch=master
237235
[Travis]: https://travis-ci.org/everit-org/json-schema
236+
[daveclayton/json-schema-validator]: https://github.com/daveclayton/json-schema-validator
237+
[draft-zyp-json-schema-04]: https://tools.ietf.org/html/draft-zyp-json-schema-04
238+
[draft-fge-json-schema-validation-00 format]: https://tools.ietf.org/html/draft-fge-json-schema-validation-00#section-7

0 commit comments

Comments
 (0)