> Link is part of the representation metadata (that's its whole reason to
> exist).
> Content-Location is representation metadata for the URI of this
> content.
> Location is a response header used as part of the redirect aspects of
> HTTP.
>
> All three are data for describing transitions from here to there, when
> used
> according to the HTTP standards, and thus are part of the hypertext as
> far
> as REST is concerned. This is necessary for the support of hypermedia
> representations in a format that does not allow embedded links or
> overlays,
> and for a lot of other reasons that I have no time to describe right
> now.
It's always enlighting to ask the master himself! So I am wrong, there are
few (exactly these) headers that may contain links -- besides the entity
itself. Great! But how shall a generic client (a) know which headers are
used to transfer the link information and (b) that it has to check a header
that is not even standardized?