Re: JSON-LD / Hydra Console - Entry Point seems not to be correct

Hello Markus,
thanks again for your reply.

Am 17.05.2015 um 20:48 schrieb Markus Lanthaler:
> Cool. Yeah, the media type is unfortunately not very intuitively. But
we decided to stick to the
> standards instead of having a simpler one like application/json-ld.
Thats fine - my bad.

Coming back to the description again: I thought (but I am not sure
anymore after reading your reply), that the documentation displayed
(e.g. for EntryPoint) would be loaded in this way:
1) http://www.markus-lanthaler.com/hydra/api-demo/ is loaded and parsed
2)
http://www.markus-lanthaler.com/hydra/api-demo/contexts/EntryPoint.jsonld is
loaded and parsed in order to dereference EntryPoint and other types
3) As the EntryPoint is specified as vocab:entryPoint in
EntryPoint.jsonld, we need to load the vocab as well...
4) http://www.markus-lanthaler.com/hydra/api-demo/vocab# is loaded
5) Now we can dereference the EntryPoint from 1) and display the
documentation for this type.

> The HydraConsole doesn't load the vocab (anymore). It relies on the
data (hydra:title,
> hydra:description) in the Hydra ApiDocumentation.

Now what you are telling me is that the documentation actually comes
from http://www.w3.org/ns/hydra/core# - but how? The EntryPoint is
always specified as vocab:EntryPoint, never as hydra:entrypoint, so how
can the Console take the description from hydra? This is the reason why
I thought the vocab needs to be loaded.

Thanks and best regards,
Tobias

Received on Monday, 18 May 2015 06:45:43 UTC