W3C home > Mailing lists > Public > public-credentials@w3.org > September 2017

Re: JSON Pointers, References and Templates

From: Henry Andrews <henry@cloudflare.com>
Date: Sun, 24 Sep 2017 22:48:22 -0700
Message-ID: <CANp5f1NvMYs55aKypi+jBQdwrGe7TrFkrB4ZZdNjEBUh83CP1A@mail.gmail.com>
To: Adam Sobieski <adamsobieski@hotmail.com>
Cc: "public-credentials@w3.org" <public-credentials@w3.org>, "public-linked-json@w3.org" <public-linked-json@w3.org>
Hi Adam,
  I think it would be fine to still use `$ref`, although it would be good
to get JSON Schema specification editor Austin Wright's opinion on that as
he's the one who introduced the restriction.

In my view (as the other, slightly later-to-the-party JSON Schema
specification editor) is that we are just imposing restrictions on how it
is used within the `application/schema+json` media type, which doesn't say
anything about other media types, including `application/json` or
`application/ld+json`.

`$ref` in the original JSON Reference sense is used in a number of places
outside of JSON Schema, and I wouldn't particularly expect those other
projects to stop.

I don't have too strong of an opinion on this, though.  My focus right now
is getting the next JSON Hyper-Schema draft out the door in a form that is
clear enough to produce real implementations and a conformance test suite.

thanks,
-henry


On Sun, Sep 24, 2017 at 8:43 PM, Adam Sobieski <adamsobieski@hotmail.com>
wrote:

> Henry,
>
> Thank you for sharing the Relative JSON Pointer hyperlink.
>
> After downloading the JSON Schema Core specification and observing the use
> of “$ref” (http://json-schema.org/latest/json-schema-core.html#
> rfc.section.8), it could be that a general-purpose “JSON include”
> solution might resemble:
>
> { "$include": "..." }
>
> What do you think?
>
>
> Best regards,
> Adam
>
> P.S.: https://www.w3.org/TR/xinclude-11/
>
> *From:* Henry Andrews <henry@cloudflare.com>
> *Sent:* ‎Sunday‎, ‎September‎ ‎24‎, ‎2017 ‎7‎:‎49‎ ‎PM
> *To:* Adam Sobieski <adamsobieski@hotmail.com>
> *Cc:* public-credentials@w3.org, public-linked-json@w3.org
>
> 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
>    -
>
>


-- 

   -

   *Henry Andrews*  |  Systems Engineer
   henry@cloudflare.com
   <https://www.cloudflare.com/>

   1 888 99 FLARE  |  www.cloudflare.com
   -
Received on Monday, 25 September 2017 05:49:06 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 11 July 2018 21:19:41 UTC