Comments on: JSON Schema: first Java implementation available!

By: joe

joe — Tue, 30 Aug 2011 11:51:25 +0000

Jeff, you might be interesting in watching this new project:
https://github.com/fge/json-schema-validator

This new project was originally based on Nico’s validator but has been developed further and supports (most of) the latest draft.

By: Jeff

Jeff — Wed, 30 Mar 2011 20:58:16 +0000

I see the same thing with card.json test. It appears, however, that the latest version of the Core Schema Definition has changed fairly dramatically. From the most recent changes log of draft-zyp-json-schema-03:

* Replaced “optional” attribute with “required” attribute.
* Replaced “maximumCanEqual” attribute with “exclusiveMaximum”
attribute.
* Replaced “minimumCanEqual” attribute with “exclusiveMinimum”
attribute.
* Replaced “requires” attribute with “dependencies” attribute.

…among others. Is anyone working on updates?

By: Alex

Alex — Sat, 19 Mar 2011 22:33:13 +0000

Hey Nico,

i tried the schema validator, there some bugs in there as it doesn´t validate description anymore… Any chance you are still workin on it?

Greetz,
Alex

By: ken

ken — Sun, 20 Feb 2011 04:18:08 +0000

Thx for implementing JSON schema in Java!

I have built your library. The car.json test (JSONSchemaTest) fails. I suspect the car schema has changed since you ran your test. The test asserts there should be 4 errors but there are 9:
$.adr.description: is missing and it is not optional
$.adr.properties: is missing and it is not optional
$.adr.type: is missing and it is not optional
$.geo.description: is missing and it is not optional
$.geo.properties: is missing and it is not optional
$.geo.type: is missing and it is not optional
$.email: string found, object expected
$.email.value: is missing and it is not optional
$.email.type: is missing and it is not optional

A few other suggestions:
* The test shouldn’t depend on the order of errors in errors[].
* validate() should return a Map of errors so they can be bound to form fields.
* Include a snapshot of the car schema in your resources.
* It would be nice to have a suite which runs all of the tests.
* The format attribute should be implemented so dates/times can validate.
* The API should be standardized w/ the IETF so a programmer can switch impls.
* public JacksonSchemaProvider(ObjectMapper mapper) — Don’t require the mapper argument.

Do you need some help?

By: jane

jane — Tue, 04 Jan 2011 01:05:39 +0000

Nico,
I have a lot of interest I took a look at your current implementation. It seems that it doesn’t provide a facility for me to plug in validators for custom types. json-schema.org says “If the property is not defined or is not in this list, then any type of value is acceptable. Other type values MAY be used for custom purposes …”
In JacksonSchema.java, line 136 – ” Class clazz = (Class) Class.forName(“eu.vahlas.json.schema.impl.validators.” + className);
“, is it possible to be enhanced to make it pluggable? Your code could have default type and validator mapping, and we can overwrite the map through some APIs.
How does it sound to you?

Thanks,
Jane

By: Joe

Joe — Mon, 20 Dec 2010 17:01:41 +0000

Nico, do you have any plans to add your project to the maven central repo? If you need help with this I would be more than happy to give you a hand (I’ve just gone through the process myself).

I’d like to use your validator in my own project but at the moment my only sensible option seems to be to import your source. My project is ASL 2.0 too so I’m not concerned about licensing.

By: Joe

Joe — Mon, 01 Nov 2010 20:20:01 +0000

s/write/right/ ;D

By: Joe

Joe — Mon, 01 Nov 2010 20:19:29 +0000

Nico (sorry, I’ll get your name write from now on ) – one simple solution for issue tracking might be to migrate from gitorious to github. Github has a built in issue tracker and wiki.

By: nico

nico — Mon, 01 Nov 2010 19:21:58 +0000

Hi,

sorry again for the delay … it is taking me far more time to move to Paris than I expected … and I am not done yet!

Anyway, here are my plans for the JSON Schema implementation:

1) Review the 3rd revision of the JSON Schema specification and implement the changes
2) Implement the reference mechanism : this is by far the most urgent thing to do
3) Enrich the javadoc
4) Release a first version of the implementation
5) Enrich the Project page and the wiki page on gitorious

I do not plan to open a google code project, as I already have the gitorious project. But I agree that the issue tracker is a need … I don’t kown if there is something out there compatible with gitorious and free of charges I’ll have to take a look and see what can be done.

Any help is, of course, welcome on any of these tasks or any other that you can see.

Nicolas

By: Joe

Joe — Mon, 01 Nov 2010 10:50:09 +0000

Hi Nick,
Any chance you could maybe spin-up a google code project for this? Seems like a good time to start a project page (and an issue tracker).

I’d like to contribute to the project if I can. What do you need?