- 25 Nov, 2018 6 commits
-
-
pitchum authored -
pitchum authored
-
pitchum authored
-
pitchum authored
Not sure it's a bug but still it seems that the Draft4Validator expects the "id" being replaced with "$id" althoug it should be only true with Draft6Validator according to this: https://json-schema.org/draft-06/json-schema-release-notes.html#q-what-are-the-changes-between-draft-04-and-draft-06
-
pitchum authored
-
pitchum authored
-
- 11 Aug, 2016 1 commit
-
-
sebian authored
-
- 10 Aug, 2016 1 commit
-
-
sebian authored
-
- 30 Jul, 2015 2 commits
- 19 May, 2015 4 commits
- 08 Jan, 2015 1 commit
-
-
Gu1 authored
-
- 12 Oct, 2014 1 commit
-
-
Gu1 authored
-
- 24 Jul, 2014 2 commits
- 23 Dec, 2013 1 commit
-
-
Gu1 authored
-
- 22 Dec, 2013 1 commit
-
-
Gu1 authored
It remove a lot of flexibility provided by the JSON format... In a next version of the format, we could specify a "sanctioned way" to create non-standard properties, like prefixing their names with an underscore.
-
- 20 Dec, 2013 1 commit
-
-
Gu1 authored
-
- 10 Dec, 2013 2 commits
- 19 Nov, 2013 1 commit
-
-
Gu1 authored
GeometryCollection doesn't make any sense for now, since MultiPolygon is already a collection of polygons
-
- 18 Nov, 2013 1 commit
-
-
Gu1 authored
-
- 05 Nov, 2013 1 commit
-
-
Gu1 authored
-
- 22 Oct, 2013 1 commit
-
-
Gu1 authored
-
- 15 Oct, 2013 1 commit
-
-
Gu1 authored
-
- 14 Oct, 2013 3 commits
