-
-
Notifications
You must be signed in to change notification settings - Fork 213
Update the web site with the new draft. #42
Conversation
These were copied from the draft-wright-json-schema-00 tag in the json-schema-org/json-schema-spec repository. Addresses issue json-schema-org#38. Also remove "links" as it was part of older drafts and is no longer a separate meta-schema.
Fixes #38 |
@awwright Should this result in a minor point release? |
If there are no objections or queries over the weekend, I'll merge early next week (although may need a prompt!) |
The meta-schema did not change with the new draft, the URI is the same We should be updating the website's links to the latest draft though, but I I've been working on a use cases document, I'll publish that sometime too. On Nov 4, 2016 04:47, "Ben Hutton" notifications@github.com wrote:
|
Actually, now I'm even more confused. @awwright The meta-schemas should have been changed, particularly the meta-hyper-schema. You took out Should we perhaps rush out another draft so that we can have usable meta-schemas? The ones at the tagged point in the spec repo do not match the current draft at all. |
@awwright has made it clear that this isn't going to work. I'll re-submit a new pull request with the meta-schema update removed. |
Tried to acknowledge that this is the fifth draft while preserving the proper IETF draft author+numbering scheme. Also needed to change the URIs compared to what's in json-schema-spec as they were never changed from "04" before things were tagged. Otherwise these are copied directly over.