- From: McBennett, Pat <McBennettP@DNB.com>
- Date: Mon, 9 Jun 2014 05:04:02 -0500
- To: Markus Lanthaler <markus.lanthaler@gmx.net>, "public-hydra@w3.org" <public-hydra@w3.org>
> -----Original Message----- > From: Markus Lanthaler [mailto:markus.lanthaler@gmx.net] > Sent: Friday, June 06, 2014 4:53 PM > To: public-hydra@w3.org > Subject: RE: Hydra @context > > 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. > Markus, I think you mean 'http://www.w3.org/ns/hydra/core', right...? > > > 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 Monday, 9 June 2014 10:04:33 UTC