Copyright is held by the author/owner(s).
WWW 2006, May 23.26, 2006, Edinburgh, Scotland.
This paper provides a novel approach to use URI fragment identifiers to enable HTTP clients to address and process content, independent of its original representation.
H.4.3 [Internet], I.7.1 [WEB], I.7.2 [HTML, XML, XHTML],
ACM proceedings, HTTP, HTML, URL, browsers, fragment identifier, web content, web addressing
A 'Live URL' would look like:
where the co-ordinates specify which section is to be prominently displayed. This scheme also gives the flexibility of how we want to process and display the specified content.
We refer to the new URLs as 'Live URLs' as they bring dynamism to otherwise static content.
Another use case would be a situation, where the server would want to offload some of the processing to the client. For example, when the server wants to highlight certain content on a web page, instead of generating the highlighted content on the server, it could redirect the client to a 'Live URL', which has necessary inputs for the client to perform the highlighting.
 T Berners-Lee, R Fielding, and L Masinter, Uniform resource identifiers (uri): Generic syntax, http://www.ietf.org/rfc/rfc2396.txt
 W3C, Fragment ID of an URI, http://www.w3.org/Addressing/URL/4_2_Fragments.html
 W3C, Annotea Project, http://www.w3.org/2001/Annotea
 Brian Donovan, Everything can be a link with mozilla's window.getselection(), http://dev.lophty.com/ahoy/index.htm
 W3C, XPointer Framework, http://www.w3.org/TR/xptr-framework/
 R Fielding, J Gettys, J Mogul, H Frystyk, L Masinter, P Leach, and T Berners-Lee, Hypertext transfer protocol - HTTP/1.1, http://www.ietf.org/rfc/rfc2616.txt
 Asynchronous HTML and HTTP, http://microformats.org/wiki/rest/ahah
 Natarajan Kannan and Toufeeq Hussain, LiveURLs, http://liveurls.mozdev.org
 Mozilla, Firefox, http://www.mozilla.com/firefox/