Move JSON Schema parser/stuff into own package

[davidanthoff]

I'm not really sure this makes sense, but if the JSON schema stuff is generic enough that it is not vega-lite specific, it might make use to move it into a JSONSchema.jl package, so that other packages can also use it?

[fredo-dedup]

I have been thinking about this too. I'll give it a try.

[fredo-dedup]

I finished the JSONSchema package handling the JSON validation function. It is in the process of being registered.
I'd like to start the adaptation of VegaLite but I am not sure where to start. Ideally this should be on a branch compliant with julia 0.7 and 1.0.
Should I start a new branch off the current master or should I wait ? What is your advice ?

[davidanthoff]

So what I did in the meantime is that master is julia 0.7/1.0 only. But there are still a few kinks to iron out before we can tag a version for 0.7/1.0. Maybe the best thing right now would be to wait a little, until we have tagged a version for 0.7/1.0, and then start off master?

I should also say that I currently disabled all schema checking because it had some false negatives. I think it would be good to get schema checking back in, though!

[davidanthoff]

Alright, I think we could do this now. master is julia 0.7/1.0 only, we have tagged a release, so now might be a good time to sort this out?

[fredo-dedup]

Thanks David. I'll start as soon as I can.