- From: ashok malhotra <ashok.malhotra@oracle.com>
- Date: Wed, 27 Apr 2011 08:57:08 -0700
- To: www-tag@w3.org
Re. HashInURI, the revised document has a significantly changed message. OLD MESSAGE If an application wants to identify public, reproducible states it should use fragment identifiers because frag-ids can be changed without causing a page reload. ADDITIONAL NEW MESSAGE But using frag-ids has disadvantages: JavaScript is required on the client, states cannot be tracked by Search Engines and WebCrawlers ... HTML5 now provides history.pushState and history.replaceState operations that allow the URI to be changed without causing a page reload. Using these operations new URIs can be minted to identify states using new query parameters or paths. This provides advantages in that JavaScript is not required, states can be tracked by search engines and the full URI is sent to server and it can decide on the best way to respond given the capabilities of the client ... The new HTML5 operations are, however, not universally supported yet. All the best, Ashok On 4/27/2011 7:54 AM, Noah Mendelsohn wrote: > I apologize for being somewhat behind on finalizing the agenda for tomorrow's TAG call. I'm part way through preparing it, and you can see what's done so far at [1]. Note that, although Ashok will be at the Privacy workshop, he will dial in to the TAG call, and we will be discussing his edits to [2], especially changes to sections 2.3, 3, 4 & 5. > > I have to go out for a few hours, so the final agenda may not be out until this evening. I still have to work through pending actions, the minutes of 14 April, etc., but if you happen to see something that should be discussed, please let me know ASAP. Keep in mind that Larry has sent regrets, so a couple of items we would otherwise discuss are being delayed pending his return. Thank you. > > Noah > > [1] http://www.w3.org/2001/tag/tag-weekly > [2] http://www.w3.org/2001/tag/2011/03/HashInURI-20110331.html >
Received on Wednesday, 27 April 2011 15:58:25 UTC