On Thu, Nov 12, 2009 at 5:47 PM, Jonathan Rochkind <rochkind_at_jhu.edu> wrote:
> Personally, I've never linked the "httpRange-14" solution of doing fancy
> stuff with fragment identifiers. It only leads to confusion in my mind. But
> I'm kind of a heretic when it comes to this stuff.
Actually it's not that heretical of a perspective. Much of the
httpRange-14 hubbub seemed to derive from people reacting to timbl's
proposal to use hash fragments to aid in identifying *things*. Which
is how the 303 status code pattern came about.
I think the use of fragments in URIs for things is a great hack
myself. But like many great hacks, it's a bit hard to explain. I
always kind of hoped it was an implementation detail that most people
wouldn't have to care about: like pointer arithmetic, utf-8, etc. The
nice thing is that there are tools like Vapour that reduce the
guesswork necessary.
If you haven't run across it before Cool URIs for the Semantic Web [2]
is really quite helpful in understanding the httpRange-14 issue, and
how it plays out practically in web applications.
//Ed
[1] http://validator.linkeddata.org/vapour
[2] http://www.w3.org/TR/cooluris/
Received on Thu Nov 12 2009 - 18:37:07 EST