Draft 6 publication checklist

[handrews]

This tracks all of the stuff around getting Draft 6 out the door other than actually submitting it to the IETF as a new personal draft. It's mostly to help me remember what to review during the final review period. Plus some stuff that's really obvious but felt like it should be on the list :-) I don't expect anyone else to take action on this issue, but please comment if you know of something that does not make sense as an issue/PR against the spec that should get tracked.

• Test cases for Draft 6 (and Draft 5 as needed)
• Final review: Verify that the meta-schema and specification match
• Final review: Overall spelling, grammar, and wording consistency check
• Final review: Verify that all examples make sense and match current specs
• Final review: Verify that all notable changes are in the changelog section
• Submit drafts to IETF
• Update the web site
• Announce to mailing list

[awwright]

@handrews The process I'll follow is listed on the wiki page, take a look at that and let me know if you think that's missing anything from here.

[handrews]

@awwright the main point here is the final review stuff. That is not in your process, and wikis don't track anything anyway. You don't need to do anything for this issue, so if you don't find it useful please just ignore it.

[Relequestual]

I agree with this list of requirements before rubber stamping the draft.

[Relequestual]

@handrews Can any of these checks be checked? =]

[Relequestual]

@epoberezkin How are the updates to the tests coming along?

[epoberezkin]

@Relequestual They are coming ok, not too much left to do: json-schema-org/JSON-Schema-Test-Suite#153

[handrews]

@epoberezkin can you verify that the schema.json and hyper-schema.json currently on master validate themselves? And the hyper-schema.json validates links.json? If so we can copy them over to the web site repo and update the URIs in preparation for release.

[epoberezkin]

@handrews there are the following problems:

• schema.json (meta-schema)
  • $id should be version specific, we have agreed not to use unversioned URIs I think
• hyperschema
  • $id should be version specific
  • unless I am missing something, inside /definitions/schemaArray should be anyOf and each subschema inside anyOf should be similar to schemaArray definition in meta-schema
  • $ref to schema inside /definitions/schemaArray is wrong: it is unversioned and it is different from the current $id in schema (URI segment "drafts" in $ref vs "draft" in $id).

That's the failing code, once these issues are fixed we can try again: https://runkit.com/esp/58b87f8dc8e4bd0015b7a0f6