Take the 2-minute tour ×  I have read a lot of discussions here
on SO, watched Jon Moore's presentation (which explained a lot,
btw) and read over Roy Fielding's blog post on HATEOAS but I
still feel a little in the dark when it comes to client design.
API Question  For now, I'm simply returning xhtml with
forms/anchors and definition lists to represent the resources.
The following snippet details how I lay out forms/anchors/lists.
# anchors <li class='docs_url/#resourcename'>   <a rel='self'
href='resource location'></a>  # forms <form action='action_url'
method='whatever_method' class='???'></form>  # lists <dl
class='docs_url/#resourcename'>  My question is mainly for
forms. In Jon's talk he documents form types such as
(add_location_form) etc. and the required inputs for them. I
don't have a lot of resources but I was thinking of abstract
form types (add , delete, update, etc) and just note in the
documentation that for (add, update) that you must send a valid
representation of the target resource and w