{"id":26,"date":"2014-06-20T12:00:52","date_gmt":"2014-06-20T12:00:52","guid":{"rendered":"http:\/\/www.w3.org\/community\/hydra\/?p=26"},"modified":"2014-06-20T12:03:04","modified_gmt":"2014-06-20T12:03:04","slug":"hydra-welcomes-linked-data-fragments","status":"publish","type":"post","link":"https:\/\/www.w3.org\/community\/hydra\/2014\/06\/20\/hydra-welcomes-linked-data-fragments\/","title":{"rendered":"Hydra welcomes Linked Data Fragments"},"content":{"rendered":"

Hydra enables us to build better\u00a0APIs, and in particular, APIs that are accessible by generic clients. One part of this is to capture the\u00a0fundamental building blocks of APIs, such as hypermedia controls and collections. This is what the Hydra Core Vocabulary<\/a> 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<\/a> show the interest and engagement of a lot of people.<\/p>\n

Today, the Hydra\u00a0project\u00a0welcomes a second part: Linked Data Fragments<\/a>, a set of\u00a0technologies\u00a0for advanced and efficient client-side querying of APIs. The\u00a0Linked Data Fragments specification<\/a>\u00a0describes a uniform vision on all kinds of APIs that offer Linked Data representations, like\u00a0JSON-LD or Turtle. By defining specific kinds of fragments, such as Triple Pattern Fragments<\/a>, clients can efficiently execute complex queries. The Hydra Core Vocabulary is an enabler for these technologies.<\/p>\n

What do Linked Data Fragments look like?<\/strong>
\nSee a Linked Data Fragments API in action on\u00a0data.linkeddatafragments.org<\/a>, and try a Linked Data Fragments client at\u00a0client.linkeddatafragments.org<\/a>. The complete source code is available on GitHub<\/a>.<\/p>\n

What does this mean for the Hydra project?
\n<\/strong>As of today, Hydra will be the home of three specifications:<\/p>\n