Hydra: similarities and differences

Dear all,

The previous post asked to introduce ourselves:
I'm Ruben, semantic hypermedia researcher at Ghent University – iMinds.
My interest goes out to the development of intelligent clients,
and the APIs that enable those clients.

I've just become aware of this group and immediately joined,
but I'm not entirely sure about its context.

In particular, could you shed some light on how it relates to:
- the Hydra Core Vocabulary [1], which introduces hypermedia controls?
- Linked Data Fragments [2,3], which defines APIs that allow flexible querying?
Both initiatives are discussed in the Hydra Community Group [4].

As far as I understand, your goals seem similar,
but the ideas are executed differently.
For instance, similar to Linked Data Platform,
you seem to rely on pre-determined rules [5]
rather than in-band information in representations.
But I might be misinterpreting, so this is why I ask.

The similarities with the Hydra Core Vocabulary seem
that you also have similar concepts (resources, collections).
The similarities with Linked Data Fragments seem
that you also incorporate existing interfaces, such as SPARQL endpoints.

Thanks for telling us about this and best of luck with this group!

Ruben

[1] http://www.hydra-cg.com/spec/latest/core/
[2] http://www.hydra-cg.com/spec/latest/linked-data-fragments/
[3] http://www.hydra-cg.com/spec/latest/triple-pattern-fragments/
[4] http://www.w3.org/community/hydra/
[5] https://github.com/Graphity/graphity-browser/wiki/Linked-Data-Processor-specification

Received on Friday, 20 June 2014 14:14:08 UTC