The Internet Draft does supercede the prior draft that is at
http://json-schema.org/ (actually I should copy the I-D to
http://json-schema.org/), but the intention is that conventions from the
prior draft at
http://json-schema.org/ should now become normative with
the JSON schema link definitions in combination with the normative
meta-schema definition at
http://json-schema.org/hyper-schema, which
extends
http://json-schema.org/json-ref, which contains the link
definitions that are used by schemas. This probably should be spelled
out more clearly in the Internet Draft, so one does not need to actually
follow all these links to understand how in-place links are used in schemas.
Also, I know there has frequently been confusion that "extends" and
"schema" are not URI-valued properties, instead use JSON referencing:
{"extends": {"$ref":"
http://somesite.com/some-schema"}}
JSON schema does have the ability to self-describe this property as a
URI link it self, so it would be pretty easy to update meta-schema so
you could write:
{"extends": "
http://somesite.com/some-schema"}
Would that be preferable?
Kris