Hydra enables us to build better APIs, and in particular, APIs that are accessible by generic clients. One part of this is to capture the fundamental building blocks of APIs, such as hypermedia controls and collections. This is what the Hydra Core Vocabulary does. So far, the effort of the Hydra Community Group has focused on the development of this vocabulary, and with great success: the many discussions on the Hydra mailing list show the interest and engagement of a lot of people.
Today, the Hydra project welcomes a second part: Linked Data Fragments, a set of technologies for advanced and efficient client-side querying of APIs. The Linked Data Fragments specification describes a uniform vision on all kinds of APIs that offer Linked Data representations, like JSON-LD or Turtle. By defining specific kinds of fragments, such as Triple Pattern Fragments, clients can efficiently execute complex queries. The Hydra Core Vocabulary is an enabler for these technologies.
What do Linked Data Fragments look like?
See a Linked Data Fragments API in action on data.linkeddatafragments.org, and try a Linked Data Fragments client at client.linkeddatafragments.org. The complete source code is available on GitHub.
What does this mean for the Hydra project?
As of today, Hydra will be the home of three specifications:
We look forward to your feedback!