RE: [Jersey] What HATEOAS actually means

From: Markus Karg <>
Date: Mon, 15 Feb 2010 22:44:08 +0100

In fact I need to disagree. If a browser receives a HTML docuemtn containing
<A> and <FORM> actions, it is possible to view and trigger all of them. So
it cannot be that complex. If a client receives a XML document, it can
easily select all XLinks. If a client receives a PDF it obviously is able to
understand PDF so it can select links from it. An API could be provided that
does "receivedEntity.getLinks():Map<String role, URI link>". The
implementation can be done with a simple plugin mechanism. Whether it was
<A> or <FORM> is of no interest for the API. I don't see the problem.


From: Santiago.Pericasgeertsen_at_Sun.COM
Sent: Montag, 15. Februar 2010 21:42
Subject: Re: [Jersey] What HATEOAS actually means



On Feb 15, 2010, at 2:48 PM, Jan Algermissen wrote:

I am not sure a generic approach is feasible because hypermedia can take
many forms

- links
- link templates
- forms
- exotic (as in )


 The general case may be very difficult to tackle indeed. I agree with your


-- Santiago