- From: Noah Mendelsohn <nrm@arcanedomain.com>
- Date: Wed, 21 Dec 2011 18:26:10 -0500
- To: www-tag@w3.org, public-tag-announce@w3.org
- CC: Ashok Malhotra <ashok.malhotra@oracle.com>, "chairs@w3.org" <chairs@w3.org>, W3C Members <w3c-ac-forum@w3.org>, Jeff Jaffe <jeff@w3.org>, "T.V Raman" <raman@google.com>
I am pleased to announce the publication of a new TAG Finding "Identifying Application State" [1,2]. URIs were originally used primarily to identify documents on the Web, or with the use of fragment identifiers, portions of those documents. As Web content has evolved to include Javascript and similar applications that have extensive client-side logic, a need has arisen to use URIs to identify states of such applications, to provide for bookmarking and linking those states, etc. This finding sets out some of the challenges of using URIs to identify application states, and recommends some best practices. A more formal introduction to the Finding and its scope can be found in its abstract [3]. I would like to thank to Ashok Malhotra, who did much of the analysis and editing for this work, and also former TAG member T.V. Raman, who first brought this issue to the TAG's attention, and who wrote earlier drafts on which this finding is based. Noah Mendelsohn Chair: W3C Technical Architecture Group [1] http://www.w3.org/2001/tag/doc/IdentifyingApplicationState [2] http://www.w3.org/2001/tag/doc/IdentifyingApplicationState-20111201 [3] http://www.w3.org/2001/tag/doc/IdentifyingApplicationState#abstract P.S. Tracker: this fulfills TAG ACTION-634
Received on Wednesday, 21 December 2011 23:26:33 UTC