Instance validation/Format types into main specification

[zeth]

https://groups.google.com/forum/#!searchin/json-schema/format/json-schema/WInNIGWSL4U/UtTl29b-3GIJ
https://groups.google.com/forum/#!searchin/json-schema/format/json-schema/74XLt7R4ISE/FPOnAh6rq_UJ

I agree with the comment in the first post, it is too confusing; may I suggest for draft 5 or 6, JSON Schema goes back to one specification document with instance validation and format types inside it?

[handrews]

Just to be contrary ;-) as someone who started using JSON Schema with draft 4, I don't find the three-document approach confusing, and in fact appreciate having the aspects of the system split up in that way to produce smaller, more cohesive documents.

[awwright]

I know a few people weren't too thrilled about splitting the documents up, but the way I re-arranged it I think makes a lot more sense than the three documents did before, and as far as I can tell people think this makes sense:

1. JSON Schema core defines the application/schema+json media type and the bare minimum of how to handle it
2. Additional documents define vocabularies that you can use in an application/schema+json document

So this is much more modular than it is in draft-04.

I'll hopefully publish a draft soon here, and if it still doesn't make as much sense let's investigate if merging some of the new drafts back together helps things.