Note that since the JSON Schema / JSON Hyper-Schema project re-launched and
began producing drafts roughly every six months again, we have include JSON
Reference in the JSON Schema Core specification rather than continuing with
it as an outside concept. That is why the last JSON Reference draft is so
old.
This doesn't mean that someone else couldn't pick up JSON Reference as a
stand-alone specification. It was just more useful for us to put some
limits on how it is used in the context of JSON Schema, which meant it was
specified enough for our purposes within the JSON Schema Core spec.
Somewhat related: we may be reviving the Relative JSON Pointer proposal,
btw (whether separately or as part of one of our specs is not entirely
clear yet). https://tools.ietf.org/html/draft-luff-relative-json-pointer-00
thanks,
-henry
On Sun, Sep 24, 2017 at 4:04 PM, Adam Sobieski <adamsobieski@hotmail.com>
wrote:
> JSON and JSON-LD enthusiasts,
>
> JSON Pointers
> https://tools.ietf.org/html/rfc6901
>
> JSON References
> https://tools.ietf.org/html/draft-pbryan-zyp-json-ref-03
>
> JSON Templates
> https://w3c-ccg.github.io/verifiable-news/sketchpad.html#templates
>
>
> Best regards,
> Adam Sobieski
> http://www.phoster.com/contents/
>
>
--
-
*Henry Andrews* | Systems Engineer
henry@cloudflare.com
<https://www.cloudflare.com/>
1 888 99 FLARE | www.cloudflare.com
-