Using Content Negotiation to relate "data resources" to AJAX user interfaces

In this context, see the early draft of the TAG  finding I
started last year entitled "Hash in URLs".
It attempts to document the various  design patterns that one
sees on the Web whereby the fragment identifier is used to
advantage to pass in what one would otherwise call "clientData"
to code running inside a Web page.

Basically, at the outset of the Web, '?' in a URL denoted
server-side args --- '#' was interpreted in HTML  as a fragment
identifier, with the interpretation  of the '#' in general left
to client softwrae. 
I remember during the early days of byte serving that '#' was
suggested as a possible means of addressing into PDF streams
i.e. not sure if this was ever
widely deployed.

As the AJAX  world has innovated within the constraints of the
already deployed Web, the '#' suffix of the URL has been used as
an interesting hook for passing in arguments to script running
inside the page.  

This usage essentially results in URLs that are *very*
representation specific   -- see the examples enumerated in the
finding cited above at

Present usage ranges from simple tokens that get passed in as an
argument to client side code, all the way to JSON dictionaries
that record an application's interaction state ---

Best Regards,

Title:  Research Scientist      
Google: tv+raman 

Received on Monday, 2 March 2009 22:48:53 UTC