Comments on: Contextual links in hypermedia content

By: admin

admin — Wed, 05 May 2010 03:33:56 +0000

@edipo It’s a live website… I cant remember the name. Try googling for online sequence diagram generator

@mike Hey Mike! It was a pleasure meeting you at www2010. I have changed my mind on the link header. I still believe its hard to provide some value in specific situations, where I really wish I could, it does the job pretty well for one-entity-one-document resources (or describing an entire collection at once).

By: edipo

edipo — Tue, 04 May 2010 21:52:34 +0000

A silly question, how you created this diagram? Any tool?

By: admin

admin — Wed, 03 Mar 2010 22:20:14 +0000

Hello Mike,

I understand your point, and it does encourages fine grain resources, on the opposite direction of Roy’s REST idea (which favor large grained ‘messages’)…
Both approaches have their advantages and disadvantages as both you and me tried to point out.

Regards

By: Mike Kelly

Mike Kelly — Wed, 03 Mar 2010 17:13:12 +0000

Whilst I agree that our web of documents presents some challenges – the web of data, however, is a different issue altogether and I think the Link header should play an important role in this; I would argue more so than serialization formats because Link provides a truly serialization agnostic, standardized form of hypermedia for HTTP. afaik, response headers like ‘Link’ are supposed to be considered as a proper and full-blown part of a given representation.

Picking a primary linking mechanism which constrains you to think in terms of ‘pure’ resource relations is, to me, a good thing – since it encourages fine grain resources, and discourages ‘sloppy’ composite resources.

By: This Week in REST – Volume 5 (Feb 22 2010 – Feb 28 2010) « This week in REST

Mon, 01 Mar 2010 12:16:32 +0000

[...] is your RESTful application? – Almost RESTful is ”not” RESTful. (by Markus Karg) Contextual links in hypermedia content – Comparing the difference between links in a representation and use of the Link header. (by [...]