you're reading...
Linked Data

Linked Data for RESTafarians

So, you took the red pill? You’re a full blown RESTafarian brother? Good news for you, then. You’ll understand linked data in less then 30sec. Ok. Step by step. REST, understood as a ‘set of constraints that inform an architecture’:

  1. Resource Identification
  2. Uniform Interface
  3. Self-Describing Messages
  4. Hypermedia Driving Application State
  5. Stateless Interactions

… and now read the linked data principles with your ‘REST goggles’ on:

  1. Use URIs as names for things
  2. Use HTTP URIs so that people can look up those names.
  3. When someone looks up a URI, provide useful information, using the standards (RDF, SPARQL)
  4. Include links to other URIs. so that they can discover more things.

In the linked data, we use HTTP URIs for everything. For documents, but also for concepts or real-world entities such as people. Linked data provides a uniform (read-only) interface through HTTP GET. The messages are self-describing through RDF and RDF-based vocabularies and through the last of the linked data principles, what we have in the LOD cloud is a highly connected (or: interlinked) system.

As nicely described by Leonard Richardson and Sam Ruby in RESTful Web Services you design a RESTful (ROA) system in that you:

  • Identify and name your resources (using HTTP URIs),
  • design your representations (documents & data), and
  • link the resources to each other.

You’ll typically end up in a 3D design space such as the following (kudos to Cesare Pautasso and Erik Wilde):

The same actually happens when you publish linked data, with some simplifications: due to the read-only characteristic of linked data you only have to worry about one HTTP verb (GET) and with RDF as the unified data model (based on your preferences and needs) you pick one of the RDF serializations (preferably RDFa, as it nicely integrates with HTML and hence allows you to serve humans and programs). When you have your data in RDF (or so 😉 you’ll mainly find yourself worrying how to interlink it with other data on the Web. But this really is a huge benefit – finally enabling to use the Web as one huge database.

As an aside: I’m aware of the fact that we still need to sort out some issues along the way, both in the academia and in practice. However, I encourage people in both camps (RESTful yadayada and Linked Data rogues) to look beyond one’s own nose and eventually understand that there is only one Web and we all ‘live’ in it 😉


About woddiscovery

Web of Data researcher and practitioner


7 thoughts on “Linked Data for RESTafarians

  1. In a single post you illustrate why we are talking Web 3.0 (Web to power of 3) and not Web 2.0 (Web to the power of 2) 🙂


    Posted by Kingsley Idehen | 2009-10-09, 14:17
  2. Yes, it is one evolving Web where things like 1.0, 2.0, 3.0 simply put names/monikers to the evolution of usage dimensions etc..

    Posted by Kingsley Idehen | 2009-10-09, 14:21
  3. Thanks for that post, I’ve had a hunch that REST might benefit from semantic web technologies, but you explain that much better than I could 🙂

    Greets from Graz!

    Posted by peter sabaini | 2009-10-21, 09:32


  1. Pingback: Twitter Trackbacks for Linked Data for RESTafarians « Web of Data [webofdata.wordpress.com] on Topsy.com - 2009-10-09

  2. Pingback: Danny Ayers (danja) 's status on Friday, 09-Oct-09 11:49:56 UTC - Identi.ca - 2009-10-09

  3. Pingback: Linked Data for RESTafarians « Web of Data | Dataentry update today - 2009-10-09

  4. Pingback: REST/Linked Data « Business, Technology and Me - 2012-07-17

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s


%d bloggers like this: