This is a single archived entry from Stefan Tilkov’s blog. For more up-to-date content, check out my author page at INNOQ, which has more information about me and also contains a list of published talks, podcasts, and articles. Or you can check out the full archive.

Link Relations and HTTP Header Linking

Stefan Tilkov,

I just stumbled across this RFC draft by Mark Nottingham:

This document specifies relation types for Web links, and defines a registry for them. It also defines how to send such links in HTTP headers with the Link header-field.

Interestingly, it suggests a nice balance between the need for registration of well-known types and the decentralization needs: In a rel=’xyz’ attribute, ‘xyz’ is interpreted as a URI that’s relative to http://www.iana.org/assignments/relation/; alternatively it can be an absolute URI, such as http://innoq.com/st/loves-it. I love it! Now can I please get the same thing for media types?

On January 5, 2009 9:41 PM, Subbu Allamaraju said:

Web Gods speaking …

“Nice try. No. Would like Semantic Web instead?”

On January 5, 2009 11:54 PM, Aristotle Pagaltzis said:

Atom: taking over the world, one idea at a time. :-)

On January 6, 2009 12:05 AM, Subbu Allamaraju said:

The quoted text in my comment should have been

“Nice try. No. Would you like Semantic Web instead?”

On January 6, 2009 9:09 AM, Martin Probst said:

Subbu: if anything like the semantic web is ever to succeed, this will be the path to it: small, incremental steps that create value along the way.

On January 6, 2009 12:57 PM, Erik Mogensen said:

Actually, Opera decodes the Link: headers as if they were HTML links. It provides buttons in the UI to navigate well known HTML relations, like up, next, previous, first, last, top etc. Link headers rule!