@apsoto @uglymunky 

Dealing with the fragment is a client-side concern; it doesn't even make it back to the server in the HTTP request.  What it would allow is linking to a sub-entity within the context of its parent entity.

Take the following URL, as an example: http://stackoverflow.com/questions/1647631/c-state-machine-design/1647679#1647679

The server has no idea that fragment was even included in the link.  However, when a response comes back to the client, the client searches for that ID and highlights the StackOverflow answer in context.

This could be helpful for UI-driven apps on top of hypermedia, though I imagine there could be an M2M use case, as well.

This is why it needs to be unique within the entirety of the response--you only get one fragment.