W3C | TAG
TAG Product: Identifying Application State
Goals
The goal of this work is to document for the community good practices relating to the use of URIs for identifying
and tracking the state of Web Applications.
Success criteria
- The TAG comes to consensus on good (and bad) practices relating to the use of URIs for identifying and tracking
the state of Web applications.
The analysis will include, but not be limited, to script-driven (e.g. AJAX-style) applications that are used to
display documents (email, maps, spreadsheets, etc.)
- The TAG publishes either a full W3C Recommendation or a TAG finding that effectively communicates the issues
and good practices to the Web technical community.
Key deliverables with dates:
Per discussion on 13 Sept. 2011 at the Edinburg F2F:
- "Proposed" TAG Finding: Identifying Application State Due 30 Sept. 2011 for review until 15 November 2011, to allow for discussion at TPAC
- TAG Finding: Identifying Application State Due date: For publication at 4-6 January 2012 TAG F2F
- W3C Note with FPWD (Raman's version) indicating this work no longer
on Rec. track (to be done after reference to finding available)
Schedules:
- 25 June 2011: Draft for TAG review based on June 2011 F2F review
- 1 Sept 2011: Last-call quality draft
- 30 Sept 2011: Proposed Finding
- 6 January 2012: Published TAG Finding
TAG Members assigned:
Ashok Malhotra (confirmed)
Working documents:
TAG Issues, Actions and Tracker Product Page
- ISSUE-60: Web Application State Management
- ACTION-597: on - Ashok Malhotra - Publish a final draft for public review of the finding on Application State - Due: 2011-12-01 - OPEN
- ACTION-481: on - Ashok Malhotra - Update client-side state document with help from Raman - Due: 2011-09-10 - CLOSED
- ACTION-586: on - Ashok Malhotra - Add text covering advice equivalent to "Use of AJAX implementation technology is not a sufficient excuse for failing to provide first class URI identification for documents on the Web" - Due: 2011-08-11 - CLOSED