RE: fragment identifiers

> It solved the problem by distinguishing between resources, messages,
> and the results of method invocations.  The spec doesn't say
> "representations" because the editors couldn't agree on whether
> to call them representations or instances.  Dan did a great job of

This is a bit misleading.  The "resource" that HTTP talks about is
purely imaginary.  

HTTP only ever deals with representations, messages, the results of
method invocations.  It is fine to say that HTTP distinguishes between
those various things that it actually deals with.  But HTTP ignores the
resources, and it's a bit of a stretch to say that HTTP has any advice
to offer in this regards.

HTTP never "solved" this problem.  It simply ignored it.