VDR http binding cannot use fragment to locate the resource

**Describe the bug**

After creating a resource, we'll get the URL that look like this `http://my-agent/vdr/entries/?drf=memory&drid=memory&drv=0.1.0&m=0#2012d37f-eb19-45da-b4af-6a4ec9eb9542`.

URI fragment is typically used in client side dereferencing. It indicates a part of a resource rather than a separate resource. So it is not part of the URI resource resolution. For example, a curl command will not send `my-resource-id` to the server if we call `curl -v http://localhost:8000/my-resource-collection#my-resource-id`.

This limits the VDR http binding to pass a full URI to some endpoint rather than client directly dereferencing from the VDR URI. For example, the client must send a full URI to an endpoint like this

`http://my-agent/vdr/entries?url=`

and not

`http://my-agent/vdr/entries/my-path?drf=...&drid=...#`

I want to open this to see if this is the restriction we want to remove in the future.