W3C home > Mailing lists > Public > public-hydra@w3.org > June 2014

Re: Hydra @context

From: Tomasz Pluskiewicz <tomasz@t-code.pl>
Date: Sun, 8 Jun 2014 14:55:37 +0200
Message-ID: <CAAFOhSdp5XdpsPBRgBM6zV9osWGqe=RWAg417DxwKxFgbfHsNg@mail.gmail.com>
To: Markus Lanthaler <markus.lanthaler@gmx.net>
Cc: public-hydra@w3.org
On Fri, Jun 6, 2014 at 5:53 PM, Markus Lanthaler
<markus.lanthaler@gmx.net> wrote:
> Ho Tomasz,
>
> On Friday, June 06, 2014 8:20 AM, Tomasz Pluskiewicz wrote:
>> I'm lookins at the examples on the specification page and many of them
>> reference the Hydra context http://www.w3.org/ns/hydra/context.jsonld.
>> I was very much surprised to find out that in fact it's a owl
>> ontology.
>
> Yeah, that's a "trick" to reduce the number of HTTP round-trips if you also need to access information about the vocabulary itself.
> In fact, the context URL redirects to the vocabulary, so perhaps the examples should be updated to use http://www.w3.org/ns/hydra directly.
>

Thanks. I don't think that's necessary. It is clear enough and I just
wanted to make sure that I understand what the JSON-LD processor does.

>
>> Do I understand correctly that JSON-LD processor understands it simply
>> becuase the ontology itself contains a @context, and the rest of it is
>> actually ignored?
>
> Exactly. Remote JSON-LD contexts are nothing else than a JSON-LD document with an @context. A processor will ignore the rest of the document.
>
>
> --
> Markus Lanthaler
> @markuslanthaler
>
>
>
Received on Sunday, 8 June 2014 12:56:52 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 15:53:59 UTC