ISSUE-60: Web Application State Management

webApplicationState-60

Web Application State Management

State:

OPEN

Product:

Web Application Architecture

Raised by:

T.V. Raman

Opened on:

2007-12-14

Description:

Current work is: Repurposing the Hash Sign for the New Web.

http://www.w3.org/2001/tag/2011/02/HashInURI-20110228.html

See also:
Usage Patterns For Client-Side URI parameters
W3C Working Draft 15 April 2009
http://www.w3.org/TR/hash-in-uri/

(hmm... there's probably an editor's draft around too.)

The TAG has openned a new issues, webApplicationState-60, around which to organise discussion of application state management techniques, partitioning of application state between origin servers and web clients, particularly rich web clients.

An earlier draft finding "State in Web application design" http://www.w3.org/2001/tag/doc/state.html is relevant to this issue.

In addition, recent threads on www-tag and related blog entries have discussed the use of URI fragId and user agent history stacks as a mechanism for managing client side state and for passing parameters from servers to rich web clients.

http://lists.w3.org/Archives/Public/www-tag/2007Jul/0148
http://xml-applications.blogspot.com/2007/11/toward-url-equality-for-web-clients-and.html

Regards

Stuart Williams
for W3C TAG

Related Actions Items:

• ACTION-50 on Rhys Lewis to Investigate two AJAX libraries and see how well they support exposing URIs for intermediate results. - due 2007-11-28, closed
• ACTION-91 on T.V. Raman to Write a finding about the current state of application state management on the web. - due 2008-02-18, closed
• ACTION-105 on T.V. Raman to Send email about growth of context dependence in URI interpretation - due 2008-03-04, closed
• ACTION-118 on T.V. Raman to Call for review of "Usage Patterns For Client-Side URL parameters" draft finding after collecting any input for a week - due 2008-03-06, closed
• ACTION-120 on Dan Connolly to Review of "Usage Patterns For Client-Side URL parameters" , preferably this week - due 2008-03-20, closed
• ACTION-119 on Henry Thompson to Henry review of "Usage Patterns For Client-Side URL parameters" , preferably this week - due 2008-03-27, closed
• ACTION-142 on Norman Walsh to Review Raman's draft of webApplicationState-60 - due 2008-11-28, closed
• ACTION-193 on Dan Connolly to Try to draft a blog posting adapted from http://www.w3.org/2001/tag/doc/hash-in-url, with help from TVR - due 2009-02-25, closed
• ACTION-143 on Stuart Williams to Review Raman's draft of webApplicationState-60 - due 2009-03-03, closed
• ACTION-144 on Noah Mendelsohn to Attempt to articulate some of the higher level questions for inclusion in the draft. - due 2009-03-03, closed
• ACTION-234 on John Kemp to Review the current draft of Usage Patterns For Client-Side URL parameters for possible publication - due 2009-03-11, closed
• ACTION-235 on Ashok Malhotra to Review the current draft of Usage Patterns For Client-Side URL parameters for possible publication - due 2009-03-11, closed
• ACTION-247 on to Noah to schedule followup on Raman proposal: publish issue 60 draft - due 2009-03-24, closed
• ACTION-248 on T.V. Raman to Prepare a new draft of http://www.w3.org/2001/tag/doc/hash-in-url-20080320.html for review by the group - due 2009-04-02, closed
• ACTION-236 on Noah Mendelsohn to Schedule discussion of the stress on media types imposed by client-side synthesised content - due 2009-05-05, closed
• ACTION-266 on Noah Mendelsohn to Send a note to www-tag pointing out that discussion is open on the WD for ISSUE-60 - due 2009-05-14, closed
• ACTION-353 on Noah Mendelsohn to Do just a bit of work framing some issues around identification for Ajax apps (remembering the merged maps use case) - due 2010-03-08, closed
• ACTION-432 on Noah Mendelsohn to Review client state finding update w.r.t. maps case - due 2010-05-18, closed
• ACTION-422 on T.V. Raman to Examine the current text of his client state finding and update appropriately with Noah's email from ACTION-353 - due 2010-05-31, closed
• ACTION-533 on Noah Mendelsohn to Schedule TAG discussion of #! (check with Yves) [self-assigne] - due 2011-04-05, closed
• ACTION-475 on Ashok Malhotra to Write finding on client-side storage, DanA to review - due 2011-08-24, closed
• ACTION-481 on Ashok Malhotra to Update client-side state document with help from Raman - due 2011-09-10, closed
• ACTION-536 on Noah Mendelsohn to Work with HST to identify a way forward wrt interaction - due 2011-10-11, closed
• ACTION-646 on Ashok Malhotra to With help from Noah, update product page and product index to reflect publication of Client-Side state finding - due 2012-01-03, closed

Related emails:

1. Agenda for TAG F2F 4-6 January 2012 (from nrm@arcanedomain.com on 2011-12-30)
2. Agenda for TAG Teleconference of 15 December (from nrm@arcanedomain.com on 2011-12-14)
3. Agenda for TAG teleconference of 1 December 2011 (from nrm@arcanedomain.com on 2011-11-29)
4. Draft Minutes of November 17 Telcon (from ashok.malhotra@oracle.com on 2011-11-23)
5. Re: Final agenda for TAG teleconference of 17 November 2011 (from amy@w3.org on 2011-11-17)
6. Final agenda for TAG teleconference of 17 November 2011 (from nrm@arcanedomain.com on 2011-11-16)
7. Re: Agenda for today's TAG teleconference (from Frederick.Hirsch@nokia.com on 2011-10-28)
8. Agenda for today's TAG teleconference (from nrm@arcanedomain.com on 2011-10-27)
9. Re: No formal TAG call 10/20/11 (from nrm@arcanedomain.com on 2011-10-21)
10. No formal TAG call 10/20/11 (from masinter@adobe.com on 2011-10-20)
11. Agenda for TAG call 10/20/11 (from masinter@adobe.com on 2011-10-20)
12. Re: Draft Agenda for TAG call 10/20/11 (from Daniel.Appelquist@vodafone.com on 2011-10-20)
13. Draft Agenda for TAG call 10/20/11 (from LMM@acm.org on 2011-10-19)
14. RE: Draft Agenda for TAG call 10/20/11 (from masinter@adobe.com on 2011-10-19)
15. Re: Draft Agenda for TAG call 10/20/11 (from nrm@arcanedomain.com on 2011-10-19)
16. Agenda for the TAG teleconference of 13 October 2011 (from nrm@arcanedomain.com on 2011-10-12)
17. Agenda for the TAG teleconference of 6 October 2011 (from nrm@arcanedomain.com on 2011-10-04)
18. Agenda for TAG F2F meeting: 13-15 September 2011 (from nrm@arcanedomain.com on 2011-09-05)
19. Minutes for September 1 Telcon (from jeni@jenitennison.com on 2011-09-04)
20. Very preliminary agenda and required reading for 13-15 Sept. 2011 TAG F2F now available (from nrm@arcanedomain.com on 2011-08-30)
21. Draft TAG minutes 2011-04-28 (from Daniel.Appelquist@vodafone.com on 2011-05-05)
22. Agenda for the TAG teleconference of 28 April 2011 (from nrm@arcanedomain.com on 2011-04-27)
23. Agenda for TAG Teleconference of 14 April 2011 (from nrm@arcanedomain.com on 2011-04-12)
24. Agenda for TAG Teleconference of 24 March 2011 (from nrm@arcanedomain.com on 2011-03-23)
25. Draft Minutes for March 10 Telcon (from ashok.malhotra@oracle.com on 2011-03-11)
26. Re: Agenda for TAG teleconference of 10 March 2011 (from ashok.malhotra@oracle.com on 2011-03-10)
27. Agenda for TAG teleconference of 10 March 2011 (from nrm@arcanedomain.com on 2011-03-09)
28. HashInURI notes (from nathan@webr3.org on 2011-03-09)
29. Draft minutes of the 8-10 February 2011 TAG F2F Meeting are now available (from nrm@arcanedomain.com on 2011-02-21)
30. Draft minutes of the 8-10 February 2011 TAG F2F Meeting are now available (from nrm@arcanedomain.com on 2011-02-21)
31. Stable agenda for TAG F2F of 8-10 February 2011 (from nrm@arcanedomain.com on 2011-02-05)
32. Preliminary version of the Agenda for the TAG F2F Meeting of 8-10 February 2011 (from nrm@arcanedomain.com on 2011-01-30)
33. Agenda for the TAG teleconference of 20 January 2011 (from nrm@arcanedomain.com on 2011-01-19)
34. Re: Agenda for TAG teleconference of 13 January 2011 (from Daniel.Appelquist@vodafone.com on 2011-01-13)
35. Agenda for TAG teleconference of 13 January 2011 (from nrm@arcanedomain.com on 2011-01-11)
36. Agenda for TAG teleconference of 16 Dec 2010 (from nrm@arcanedomain.com on 2010-12-14)
37. ACTION-353: Client-side identification in Ajax applications (from noah_mendelsohn@us.ibm.com on 2010-03-06)
38. TAG Members: please reviews status of issues you 'shepherd' by Monday, 8 March (from noah_mendelsohn@us.ibm.com on 2010-03-03)
39. 'A proposal for making AJAX crawlable' squats in URI space, doesn't follow the principle of least power (from connolly@w3.org on 2009-12-03)
40. Agenda for TAG teleconference of 23 July 2009 (from noah_mendelsohn@us.ibm.com on 2009-07-21)
41. Agenda for TAG teleconference of 28 May 2009 (from noah_mendelsohn@us.ibm.com on 2009-05-27)
42. Draft minutes of TAG teleconference of 21 May 2009 (from noah_mendelsohn@us.ibm.com on 2009-05-26)
43. Next steps on TAG ISSUE-60 (from noah_mendelsohn@us.ibm.com on 2009-05-20)
44. Agenda for 21 May 2009 TAG Teleconference and Start of F2F Agenda Planning (from noah_mendelsohn@us.ibm.com on 2009-05-19)
45. Minutes of the 7th May TAG teleconference (from john.kemp@nokia.com on 2009-05-15)
46. Re: Who is willing to shepherd TAG ISSUE-60? (was: Re: [hash-in-uri] pushState()) (from noah_mendelsohn@us.ibm.com on 2009-05-11)
47. Who is willing to shepherd TAG ISSUE-60? (was: Re: [hash-in-uri] pushState()) (from raman@google.com on 2009-05-11)
48. Who is willing to shepherd TAG ISSUE-60? (was: Re: [hash-in-uri] pushState()) (from raman@google.com on 2009-05-11)
49. Who is willing to shepherd TAG ISSUE-60? (was: Re: [hash-in-uri] pushState()) (from noah_mendelsohn@us.ibm.com on 2009-05-11)
50. Agenda for TAG teleconference of 7 May 2009 (from noah_mendelsohn@us.ibm.com on 2009-05-05)
51. Re: ISSUE-60: Name of draft should be changed to refer to URI's not URL's (from noah_mendelsohn@us.ibm.com on 2009-04-06)
52. RE: ISSUE-60: Name of draft should be changed to refer to URI's not URL's (from masinter@adobe.com on 2009-04-03)
53. Re: ISSUE-60: Name of draft should be changed to refer to URI's not URL's (from john.kemp@nokia.com on 2009-04-03)
54. Re: incorrect link in 04-02-agenda (from noah_mendelsohn@us.ibm.com on 2009-04-02)
55. Re: ISSUE-60: Name of draft should be changed to refer to URI's not URL's (from noah_mendelsohn@us.ibm.com on 2009-04-02)
56. Approved minutes of the TAG F2F of 3-5 March 2009 (from noah_mendelsohn@us.ibm.com on 2009-04-02)
57. incorrect link in 04-02-agenda (from jar@creativecommons.org on 2009-04-02)
58. Re: ISSUE-60: Name of draft should be changed to refer to URI's not URL's (from john.kemp@nokia.com on 2009-04-02)
59. ISSUE-60: Important 2002 email from Roy Fielding on history of fragment identifiers (from noah_mendelsohn@us.ibm.com on 2009-04-01)
60. ISSUE-60: Name of draft should be changed to refer to URI's not URL's (from noah_mendelsohn@us.ibm.com on 2009-04-01)
61. Fw: Temporary publications schedule: Tuesdays and Thursdays (from noah_mendelsohn@us.ibm.com on 2009-03-31)
62. Setting TAG Priorities - Review of discussion and planning to date (from noah_mendelsohn@us.ibm.com on 2009-03-22)
63. Re: Hash In URLs: (from raman@google.com on 2009-03-16)
64. Re: Hash In URLs: (from noah_mendelsohn@us.ibm.com on 2009-03-16)
65. RE: TAG Pending Review Action Items (from noah_mendelsohn@us.ibm.com on 2009-03-13)
66. Re: TAG Pending Review Action Items (from jar@creativecommons.org on 2009-03-11)
67. RE: TAG Pending Review Action Items (from masinter@adobe.com on 2009-03-11)
68. RE: Agenda for TAG teleconference of 12 March 2009 (from masinter@adobe.com on 2009-03-11)
69. RE: Agenda for TAG teleconference of 12 March 2009 (from masinter@adobe.com on 2009-03-10)
70. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from rsayre@mozilla.com on 2009-03-10)
71. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from rubys@intertwingly.net on 2009-03-10)
72. Agenda for TAG teleconference of 12 March 2009 (from noah_mendelsohn@us.ibm.com on 2009-03-10)
73. TAG Pending Review Action Items (from noah_mendelsohn@us.ibm.com on 2009-03-10)
74. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from rsayre@mozilla.com on 2009-03-10)
75. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from simonp@opera.com on 2009-03-09)
76. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from jonas@sicking.cc on 2009-03-06)
77. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from rubys@intertwingly.net on 2009-03-06)
78. RE: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from Chris.Wilson@microsoft.com on 2009-03-06)
79. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from hsivonen@iki.fi on 2009-03-06)
80. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from lhs@malform.no on 2009-03-06)
81. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from john.kemp@nokia.com on 2009-03-05)
82. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from rubys@intertwingly.net on 2009-03-05)
83. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from rsayre@mozilla.com on 2009-03-05)
84. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from mjs@apple.com on 2009-03-05)
85. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from timbl@w3.org on 2009-03-05)
86. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from steven.pemberton@cwi.nl on 2009-03-05)
87. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from julian.reschke@gmx.de on 2009-03-05)
88. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from steven.pemberton@cwi.nl on 2009-03-05)
89. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from julian.reschke@gmx.de on 2009-03-05)
90. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from msporny@digitalbazaar.com on 2009-03-05)
91. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from julian.reschke@gmx.de on 2009-03-05)
92. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from hsivonen@iki.fi on 2009-03-05)
93. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from mnot@mnot.net on 2009-03-05)
94. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from ben@adida.net on 2009-03-04)
95. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from mjs@apple.com on 2009-03-04)
96. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from ben@adida.net on 2009-03-04)
97. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from ben@adida.net on 2009-03-04)
98. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from ben@adida.net on 2009-03-04)
99. Re: Hash In URLs: (from noah_mendelsohn@us.ibm.com on 2009-03-04)
100. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from hsivonen@iki.fi on 2009-03-02)
101. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from rsayre@mozilla.com on 2009-03-01)
102. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from danbri@danbri.org on 2009-03-01)
103. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from mjs@apple.com on 2009-03-01)
104. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from rsayre@mozilla.com on 2009-03-01)
105. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from danbri@danbri.org on 2009-03-01)
106. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from lhs@malform.no on 2009-03-01)
107. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from julian.reschke@gmx.de on 2009-03-01)
108. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from rsayre@mozilla.com on 2009-03-01)
109. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from julian.reschke@gmx.de on 2009-03-01)
110. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from danbri@danbri.org on 2009-03-01)
111. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from rsayre@mozilla.com on 2009-03-01)
112. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from karl+w3c@la-grange.net on 2009-03-01)
113. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from pjt47@cam.ac.uk on 2009-03-01)
114. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from rsayre@mozilla.com on 2009-03-01)
115. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from karl+w3c@la-grange.net on 2009-03-01)
116. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from danbri@danbri.org on 2009-03-01)
117. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from rubys@intertwingly.net on 2009-03-01)
118. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from ben@adida.net on 2009-03-01)
119. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from julian.reschke@gmx.de on 2009-03-01)
120. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from ben@adida.net on 2009-03-01)
121. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from ben@adida.net on 2009-03-01)
122. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from julian.reschke@gmx.de on 2009-03-01)
123. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from ben@adida.net on 2009-03-01)
124. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from michael.hausenblas@deri.org on 2009-03-01)
125. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from karl+w3c@la-grange.net on 2009-03-01)
126. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from hsivonen@iki.fi on 2009-03-01)
127. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from mnot@mnot.net on 2009-03-01)
128. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from rubys@intertwingly.net on 2009-03-01)
129. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from mnot@mnot.net on 2009-03-01)
130. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from rubys@intertwingly.net on 2009-03-01)
131. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from mnot@mnot.net on 2009-03-01)
132. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from fielding@gbiv.com on 2009-02-28)
133. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from ben@adida.net on 2009-02-28)
134. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from ben@adida.net on 2009-02-28)
135. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from rsayre@mozilla.com on 2009-02-28)
136. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from ben@adida.net on 2009-02-28)
137. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from rsayre@mozilla.com on 2009-02-28)
138. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from rubys@intertwingly.net on 2009-02-28)
139. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from rsayre@mozilla.com on 2009-02-28)
140. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from noah_mendelsohn@us.ibm.com on 2009-02-28)
141. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from mjs@apple.com on 2009-02-28)
142. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from rubys@intertwingly.net on 2009-02-28)
143. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from msporny@digitalbazaar.com on 2009-02-28)
144. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from karl+w3c@la-grange.net on 2009-02-28)
145. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from julian.reschke@gmx.de on 2009-02-28)
146. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from ben@adida.net on 2009-02-28)
147. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from julian.reschke@gmx.de on 2009-02-28)
148. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from julian.reschke@gmx.de on 2009-02-28)
149. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from ben@adida.net on 2009-02-28)
150. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from ben@adida.net on 2009-02-28)
151. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from julian.reschke@gmx.de on 2009-02-28)
152. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from ben@adida.net on 2009-02-28)
153. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from ben@adida.net on 2009-02-28)
154. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from julian.reschke@gmx.de on 2009-02-28)
155. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from mnot@mnot.net on 2009-02-28)
156. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from mnot@mnot.net on 2009-02-28)
157. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from fielding@gbiv.com on 2009-02-27)
158. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from rubys@intertwingly.net on 2009-02-27)
159. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from ben@adida.net on 2009-02-27)
160. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from ben@adida.net on 2009-02-27)
161. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from danbri@danbri.org on 2009-02-27)
162. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from julian.reschke@gmx.de on 2009-02-27)
163. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from ben@adida.net on 2009-02-27)
164. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from julian.reschke@gmx.de on 2009-02-27)
165. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from ben@adida.net on 2009-02-27)
166. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from rob@robburns.com on 2009-02-27)
167. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from julian.reschke@gmx.de on 2009-02-27)
168. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from ben@adida.net on 2009-02-27)
169. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from julian.reschke@gmx.de on 2009-02-27)
170. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from noah_mendelsohn@us.ibm.com on 2009-02-27)
171. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from ben@adida.net on 2009-02-27)
172. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from ben@adida.net on 2009-02-27)
173. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from hsivonen@iki.fi on 2009-02-27)
174. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from msporny@digitalbazaar.com on 2009-02-27)
175. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from julian.reschke@gmx.de on 2009-02-27)
176. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from msporny@digitalbazaar.com on 2009-02-27)
177. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from shane@aptest.com on 2009-02-27)
178. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from hsivonen@iki.fi on 2009-02-27)
179. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from karl@la-grange.net on 2009-02-27)
180. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from hsivonen@iki.fi on 2009-02-27)
181. Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel (from hsivonen@iki.fi on 2009-02-27)
182. Agenda for TAG Face-to-Face Meeting, 3-5 March 2009 (Redwood Shores, CA) (from noah_mendelsohn@us.ibm.com on 2009-02-25)
183. Re: Request for Agenda items for TAG Telcon of 18th December 2008 (from connolly@w3.org on 2008-12-15)
184. TAG Telcon agenda fro 8th May 2008: httpredirections-57; tagSoupIntegration-54; passwordsInThClear-52; webApplicationState-60 (from skw@hp.com on 2008-05-07)
185. TAG Weekly Telcon Agenda: 20th March 2008 (from skw@hp.com on 2008-03-19)
186. TAG Telcon Agenda: 13th March 2008: webApplicationState-60; tagSoupIntegration-54; UrnsAndRegistries-50; httpRedirections-57 (from skw@hp.com on 2008-03-12)
187. RE: Getting Trackers attention (was RE: webApplicationState-60 (was RE: issue-60 (webApplicationState-48): Web Application State Management) (from skw@hp.com on 2007-12-17)
188. Re: Getting Trackers attention (was RE: webApplicationState-60 (was RE: issue-60 (webApplicationState-48): Web Application State Management) (from noah_mendelsohn@us.ibm.com on 2007-12-14)
189. Re: webApplicationState-60 (was RE: ISSUE-60 (webApplicationState-48): Web Application State Management) (from noah_mendelsohn@us.ibm.com on 2007-12-14)
190. webApplicationState-60 (was RE: ISSUE-60 (webApplicationState-48): Web Application State Management) (from skw@hp.com on 2007-12-14)
191. ISSUE-60 (webApplicationState-48): Web Application State Management (from sysbot+tracker@w3.org on 2007-12-14)

Related notes:

Display change log