Interesting. Norm Walsh is the first person I’ve seen actively convert to hash URIs to slash URIs since the httpRange-14 decision. Most people I know have been going the other way (me included).
Unable to come up with a workaround I liked, I decided it was time for a big bang: I decided to change a whole lot of URIs. Instead of using a hashed URI to identify me (and everyone and everything else), I’d use a slashed one.
Is this the start of a trend…?
theyre also the natural enemy of application-functionality extensions.eg in terrace versioning is handled by appending /version/123 to a URI . http://example.org/resource#subresource/version/123 would be looking for something at resource, which isnt even correct.. since only the local host has nonescaped URLs this is no big deal, but its just one more problematic feature of these URIsi think maybe the spec should change so that the browser sends over the stuff after the #. it seems perfectly reasonable that the web should allow requesting part of a resource..