Update for new meta-schemas.

[handrews]

I've asked @epoberezkin to verify that these validate themselves (see #206 (comment) )

Once we are certain of that, we can copy them over to the web site repo and merge this change, as discussed in issue #165

This PR directly addresses #208

[handrews]

Note that @epoberezkin validated the meta-schemas with Ajv, leading to fixes merged in PR #266.
PR json-schema-org/json-schema-org.github.io#82 puts the appropriate files in place in order for these URIs to work.

[epoberezkin]

@awwright @handrews @Relequestual why is it not merged/approved? pre-release document still points to draft-04 schema:

https://github.com/json-schema-org/json-schema-spec/blob/20170309/jsonschema-validation.xml#L230

etc.

[awwright]

Oh I'm sorry, I didn't see see this in between the prolific activity on the test suite... Yeah, this is good, the intention is to update this at the same time as we copy it into archives/ (Feel free to update the PR with that, I'll make the change before publishing if not.)

…

On Mar 12, 2017 04:58, "Evgeny Poberezkin" ***@***.***> wrote: @awwright <https://github.com/awwright> @handrews <https://github.com/handrews> @Relequestual <https://github.com/Relequestual> why is it not merged/approved? pre-release document still points to draft-04 schema: https://github.com/json-schema-org/json-schema-spec/ blob/20170309/jsonschema-validation.xml#L230 etc. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#265 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAatDazeExM99eaHQsJ6CnN4iUY6y7QAks5rk934gaJpZM4MRawG> .