title: Hateoas links in Header or in Entity
body: <p>I've seen two primary ways to add JSON REST Hateoas and I'm not sure which is more standard or the pros and cons of each approach.</p>
  
  <p>The typical approach I see (Atom Links) is that the returned entity is appended to with a field named either <code>links</code> or <code>_links</code>. This field is an array of <code>rel=&lt;rel&gt;</code> and <code>href=&lt;href&gt;</code> pairs.</p>
  
  <p>But I've also seen (Link Headers) links put into the header value named "Link". The Link is a collection with the format <code>&lt;hef&gt;; rel=&lt;rel&gt;</code>.</p>
  
  <p>Also, I noticed that in JAX-RS there doesn't seem to add Atom Links with fully qualified hrefs, only paths. By fully qualified I mean scheme and authority included. Is it looked on as bad practice to have a complete URI for the href when using Atom Links for HATEOAS?</p>