I really like his articles on HTTP APIs. I learned quite a lot from them. What he writes makes a lot of sense, except for the "HATEOAS" part. What he consisten

I really like his articles on HTTP APIs. I learned quite a lot from them. What he writes makes a lot of sense, except for the "HATEOAS" part. What he consistently doesn't tell us is why it's necessary and how exactly we're supposed to implement HATEOAS—wouldn't HEAS be a much better acronym?—in our APIs. I'm guessing the reason why is so API wrappers would be trivial to write. A single library could simply consume a "standards-compliant" API. What that means I do not know. That's where the how comes in. It seems from the XML example that these links have to in the body of the response. That would mean every single response format has to be dealt with separately. That's not very practical. I also have no idea how something like it would look in JSON for example, let alone how it should be parsed in a meaningful way.