--- layout: post title: 'Getting To Know Markus Lanthaler For The API Craft 2014 Detroit Hypermedia Panel ' image: http://kinlane-productions2.s3.amazonaws.com/api-evangelist-site/blog/markus-lanthaler.jpg author: name: kinlane tags: - Hypermedia - '4' --- I'm preparing for my hypermedia panel with Mike Amundsen ([@mamund](https://twitter.com/mamund)), Mike Kelly ([@mikekelly85](https://twitter.com/mikekelly85)), Steve Klabnik ([@steveklabnik](https://twitter.com/steveklabnik)), Kevin Swiber ([@kevinswiber](https://twitter.com/kevinswiber)), Jørn Wildt ([@JornWildt](https://twitter.com/JornWildt)), and Markus Lanthaler ([@MarkusLanthaler](https://twitter.com/MarkusLanthaler)), at [API Craft Detroit](http://api-craft.org/) next week. I wanted to go into the panel with a snapshot, and at least a minimal understanding of each of the panelists. This is kind of an all-star panel of hypermedia experts, so I need to at least bump up my understanding of what they are contributing to the API space, and who they are, beyond what I know from my own interactions with these API leaders. As I do with all of my research, I wanted to share my work with you, my reader. Next up is Markus Lanthaler. I knew of JSON-LD from work I was doing in the federal government, around making government services available, before I knew Markus. I had the pleasure of meeting him when he spoke at [API Strategy & Practice](http://apistrategyconference.com/) in Amsterdam, as well as share the stage with him in Germany at [API Days](http://apidays.io).  Here is the outline of my research into Markus's work: **Markus Lanthaler** Using JSON-LD, Hydra, and Schema.org to build awesome Web APIs **Title:** Developer, Consultant, W3C Invited Expert **Mission:** Working on JSON-LD and Hydra to make Web APIs more fun **Links:**  * Website - [http://www.markus-lanthaler.com/](http://www.markus-lanthaler.com/) * Twitter - [https://twitter.com/markuslanthaler](https://twitter.com/markuslanthaler) * Github - [https://github.com/lanthaler](https://github.com/lanthaler) * * * **JSON-LD** JSON-LD is a lightweight Linked Data format. It is easy for humans to read and write. **Links:** * Definition - [http://json-ld.org/](http://json-ld.org/) * Playground - [http://json-ld.org/playground/index.html](http://json-ld.org/playground/index.html) * Wikipedia - [http://en.wikipedia.org/wiki/JSON-LD](http://en.wikipedia.org/wiki/JSON-LD) **Conversation:** * W3C Community and Business Groups - [http://www.w3.org/community/json-ld/](http://www.w3.org/community/json-ld/) **Videos:** * [What is Linked Data?](http://www.youtube.com/watch?v=4x_xzT5eF5Q) Short video introduction to Linked Data by Manu Sporny. * [What is JSON-LD](http://www.youtube.com/watch?v=vioCbTo3C-4)? Short video introduction to JSON-LD by Manu Sporny. **Stories:** * [Creating 3rd Generation Web APIs with JSON-LD and Hydra](http://m.lanthi.com/www2013-paper) * [Model Your Application Domain, Not Your JSON Structures](http://m.lanthi.com/wsrest2013-paper) * [Hydra: A Vocabulary for Hypermedia-Driven Web APIs](http://m.lanthi.com/ldow2013-paper) * [On Using JSON-LD to Create Evolvable RESTful Services](http://m.lanthi.com/jsonld4rest-paper) * [JSON-LD and Why I Hate the Semantic Web](http://manu.sporny.org/2014/json-ld-origins-2/) * [Schema.org and JSON-LD](http://blog.schema.org/2013/06/schemaorg-and-json-ld.html) * [JSON-LD is an official Web Standard](http://semanticweb.com/j-son-ld-official-web-standard_b41441) **Presentations:** * [JSON-LD: JSON for the Social Web](http://www.slideshare.net/gkellogg1/jsonld-json-for-the-social-web) * [Building Next-Generation Web APIs with JSON-LD and Hydra](http://slidesha.re/sl-portland2013) * [Model Your Application Domain, Not Your JSON Structures](http://slidesha.re/wsrest2013-preso) * [Hydra: A Vocabulary for Hypermedia-Driven Web APIs](http://slidesha.re/ldow2013-preso) * [JSON-LD: JSON for Linked Data](http://www.slideshare.net/gkellogg1/json-for-linked-data) * [JSON-LD for RESTful Services](http://slidesha.re/jsonld4rest) * [JSON-LD and MongoDB](http://www.slideshare.net/gkellogg1/jsonld-and-mongodb) **Supporting JSON-LD:** * Gmail - [https://developers.google.com/gmail/actions/reference/formats/json-ld](https://developers.google.com/gmail/actions/reference/formats/json-ld) * Drupal - [https://www.drupal.org/project/jsonld](https://www.drupal.org/project/jsonld) **Tooling:** * JSON-LD NPM Package - A JSON-LD Processor and API implementation in JavaScript. * * * **Hydra** Hydra is an effort to simplify the development of interoperable, hypermedia-driven Web APIs. The two fundamental building blocks of Hydra are JSON‑LD and the Hydra Core Vocabulary. **Links:** * Definition - [http://www.markus-lanthaler.com/hydra/](http://www.markus-lanthaler.com/hydra/) * Playground - [http://www.markus-lanthaler.com/hydra/console/?url=http://www.markus-lanthaler.com/hydra/api-demo/](http://www.markus-lanthaler.com/hydra/console/?url=http://www.markus-lanthaler.com/hydra/api-demo/) **Code:** * [HydraBundle](http://m.lanthi.com/HydraBundleGH) - a bundle for Symfony2 to create Web APIs based on Hydra * [HydraConsole](http://m.lanthi.com/HydraConsoleGH) - a generic API console for Hydra-powered Web APIs * [HydraClient](http://m.lanthi.com/HydraClientGH) - a PHP client library to access Hydra-powered Web APIs * [JsonLD](http://m.lanthi.com/json-ld) - a JSON-LD processor implemented in PHP **Video:** * API Strategy & Practice Conference - [http://m.lanthi.com/1hZucSQ](http://m.lanthi.com/1hZucSQ) * Building Next-Generation Web APIs with JSON-LD and Hydra - [http://m.lanthi.com/sl-portland2013](http://m.lanthi.com/sl-portland2013) **Stories:** * [REST: Advanced Research Topics and Practical Applications](http://m.lanthi.com/springer2014-rest-book-toc) * [RESTful Web APIs](http://amzn.to/1d7RHqy) * [Hydra: A Vocabulary for Hypermedia-Driven Web APIs](http://m.lanthi.com/ldow2013-paper) * [Creating 3rd Generation Web APIs with Hydra](http://m.lanthi.com/www2013-paper) * [Model Your Application Domain, Not Your JSON Structures](http://m.lanthi.com/wsrest2013-paper) **Conversation:** * W3C Community and Business Groups - [http://www.w3.org/community/hydra/](http://www.w3.org/community/hydra/) * * * **Talks:** * Website - [http://www.markus-lanthaler.com/talks](http://www.markus-lanthaler.com/talks) **Papers:** * [Third Generation Web APIs—Bridging the Gap between REST and Linked Data](http://m.lanthi.com/3gen-web-apis) * [Leveraging Linked Data to Build Hypermedia-Driven Web APIs](http://m.lanthi.com/springer2014-rest-book-toc) * [Creating 3rd Generation Web APIs with Hydra](http://m.lanthi.com/www2013-paper) * [Model Your Application Domain, Not Your JSON Structures](http://m.lanthi.com/wsrest2013-paper)  * [Hydra: A Vocabulary for Hypermedia-Driven Web APIs](http://m.lanthi.com/ldow2013-paper) * [On Using JSON-LD to Create Evolvable RESTful Services](http://m.lanthi.com/jsonld4rest-paper) * [A Web of Things to Reduce Energy Wastage](http://m.lanthi.com/indin2012-paper) * [Seamless Integration of RESTful Services into the Web of Data](http://m.lanthi.com/1azILrQ) * [Aligning Web Services with the Semantic Web to Create a Global Read-Write Graph of Data](http://m.lanthi.com/sparql2rest) * [A Semantic Description Language for RESTful Data Services to Combat Semaphobia](http://m.lanthi.com/seredasj) * [SAPS: Semantic AtomPub-based Services](http://m.lanthi.com/saps-paper) * [Semantic Web Services: State of the Art](http://m.lanthi.com/its2010-paper) * [Towards a RESTful Service Ecosystem - Perspectives and Challeng](http://m.lanthi.com/dest2010-paper)es I'm not posting all of this information just so I can share my research, it is also because Markus has an important vision of where we should take API design, and how we should be linking our most valuable data. While I learned a lot through this process, I will also use it as a reference for my panel at API Craft, and for other stories I write in the future. I've already added [Hydra](http://www.markus-lanthaler.com/hydra/) and [JSON-LD](http://json-ld.org/) as a tools in my [hypermedia API research](http://hypermedia.apievangelist.com). I could spend days going through this research, but I also have 2 ther hypermedia API experts to profile, so I'm going to move on to the others, and come back to my profile of Markus in the future to continue my own hypermedia education.