Avoid rendering comments as giant headers...

...when looking at this file as markdown.

New Proposal: JSON Reference (JRef) media type

New proposal: JSON Referencing and Identification (JRI)

Update README for naming vs the build system

It needs to be able to accomodate boolean schemas, and formats
in which any value can be a refer...

Only proposals that want to use the build system should start
with "draft-".

Since it is not a direct adoption of terminology from another spec.

You can't adopt "$ref" but redefined "$id" to do something else.

The most significant change here is reworking the discussion of
falling back to object-level sem...

Set up build, add basic files

It really should be IETF, "Independent" is something else.

Really, part of it is context-related and part is more fundamental.

and why $defs is part of the spec.

...to the section focusing on context specification integration.

In addition to the "Definitions" section.

No other changes. Change Log and implementation inventory
are now stored elsewhere, which was w...

Move some things to the standalone and context-sensitive sections.

And remove referencess to obsolete communication channels.

GitHub auto-creates LICENSE.md with these contents for the
MIT license.

Co-authored-by: Ben Hutton <[email protected]>

Co-authored-by: Jason Desrosiers <[email protected]>

LICENSE is from the JSON Schema spec repo, replacing
"JSON Schema Specification Authors" with
"J...