Update meta-schemas for draft-wright-00

[handrews]

Addresses issue #122 and (sort of) json-schema-org/json-schema-org.github.io#38

I went ahead and made this a pull request so that we can talk about something concrete.
This is a branch from the draft-wright-json-schema-00 to avoid pulling in other work. We'd presumably also merge this into master.

[awwright]

I suppose one name is as arbitrary as any other, at least to a computer; but for us humans I've been thinking the next meta-schema will be named http://json-schema.org/draft-06/schema#

As seen here, I don't see any problem with skipping numbers if it represents an I-D release that didn't change the meta-schema. If there's a good argument we could just call it draft-05, but that was already used to refer to the latest release.

[handrews]

Totally on board with draft-06.

Do we want to release this as a new draft of just a meta-schema update, or should I drop this and open a new pull request rebased out to the current master and also include the seem-likely-to-be-approved "contains", "examples", and required-can-be-empty changes? I think all of that together is quite useful.

That would be a new draft with matching meta-schema and a bit of updated content.

[handrews]

It's clear that this pull request is not doing anything allowable, so I'm closing it. I will re-submit the relevant changes on top of the current master using a draft-06 number.