03-agenda
47.8 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
<title>TAG F2F, 3-5 March 2009</title>
<link href="http://www.w3.org/StyleSheets/base.css" rel="stylesheet"
type="text/css" />
<!-- ************************************* -->
<!-- Inline CSS -->
<!-- -->
<!-- Maybe someday move to stylesheet -->
<!-- but for now having this stand -->
<!-- on its own as a single file -->
<!-- seems better. -->
<!-- ************************************* -->
<style type="text/css">
@media print {
body {
font-size:11px;
}
dl div.frontmatter {
font-size:11px;
}
h2#issuetable {
page-break-before: always
}
}
@media screen {
div.frontmatter {
font-size:medium;
}
}
/* Used to create red warning that draft is not ready for review */
.warning { color:red; font-size:130%;
font-weight:bold; }
.bold {font-weight:bold;}
/* Front matter */
div.frontmatter {
margin-left:.35cm;
margin-right:.35cm;
font-size:medium;
font-weight:normal;
}
/* topic separators */
h2 {
background:#eeeeee;
border:solid;
border-width:1px;
margin-left:.1cm;
/* width:12cm; */
padding:.3em;
padding-left:.3cm;
margin-top:1.5em;
margin-bottom:.6em;
margin-right:.2cm;
}
div.nonlistsection {
margin-left:.35cm;
margin-right:.35cm;
font-size:medium;
font-weight:normal;
}
ol li div.nonlistsection {
margin-left:.35cm;
margin-right:.35cm;
font-size:76.9%;
font-weight:normal;
}
/* nested lists for agenda items */
ol {
font-size:140%;
font-weight:bold;
margin-right:.35cm;
}
ol li {
margin-top:1em;
}
ol li a[href] {
font-weight:normal;
}
ol li ul li {
margin-top:0em;
}
ol li ul, div.itemtext {
margin-top:.5em;
font-size:76.9%;
font-weight:normal;
}
ol li ul li ul {
margin-top:0;
font-size:90%;
}
/* Styles for right pane links to minutes here */
table ol {
font-size:100%;
font-weight:bold;
}
table ol li {
margin-top:.5em;
}
/* H3 is used for subheadings within numbered ol agenda list items */
h3 {
font-size:80%;
margin-bottom:0;
margin-left:0.25cm;
margin-top:.5em;
}
table.agendatable {
/* width:12cm; */
margin-left:1cm;
margin-right:1cm;
margin-top:1em;
}
td {padding:4px}
td.date {padding-left:.2em;
background:#bebebe;
}
td ul {
margin-top:.2em;
margin-bottom:.5em;
}
/* ******************************************** */
/* STYLES FOR ISSUE LIST TABLE */
/* ******************************************** */
table.issuetable {
margin-left:.35cm;
margin-bottom:2em;
margin-top:.5em;
margin-right:.5cm;
}
table.issuetable td, table.issuetable th {
padding:3px;
vertical-align:bottom;
text-align:left;
}
table.issuetable th {
font-weight:bold;
}
.calendarTimeHeading {font-weight:bold}
.rightalign {text-align:right;}
.centeralign {text-align:center;}
</style>
</head>
<!-- ************************************* -->
<!-- Body - Frontmatter -->
<!-- ************************************* -->
<body>
<p><a href="http://www.w3.org/">W3C</a> | <a
href="http://www.w3.org/2001/tag/">TAG</a> | Previous teleconference: <a
href="http://www.w3.org/2001/tag/2009/02/19-minutes">19 Feb
2009.</a> | Next teleconference: 12th March 2009 (tentative).</p>
<h1>TAG face-to-face meeting, 3-5 March 2009, Redwood Shores, CA, USA</h1>
<!-- ************************************* -->
<!-- Work in progress warning -->
<!-- ************************************* -->
<!--
<p class="warning">WORK IN PROGRESS DRAFT - NOT READY FOR PUBLIC REVIEW</p>
-->
<!-- ************************************* -->
<!-- Picture -->
<!-- ************************************* -->
<img style="margin-left:1cm" src="./TagWithDave.jpg" alt="Picture of the TAG" />
<p style="margin-left:1cm;">Dave Orchard (outgoing TAG member), Noah Mendelsohn, Larry Masinter, John Kemp, T.V. Raman, Hubbell, Tim Berners-Lee, Henry Thompson, Jonathan Rees, Dan Connolly, Ashok Malhotra</p>
<div class="frontmatter">
<p>Nearby: <a href="http://www.w3.org/2001/tag/group/track/issues">issues
list</a> - <a href="http://www.w3.org/2001/tag/findings">findings</a> - <a
href="http://lists.w3.org/Archives/Public/www-tag/">www-tag archive</a>
- <a href="http://lists.w3.org/Archives/Member/tag/">tag archive</a> - Actions: (<a
href="http://www.w3.org/2001/tag/group/track/actions/open">open</a>, <a
href="http://www.w3.org/2001/tag/group/track/actions/pendingreview">pending review</a>)</p>
<p><span class="bold">Regrets:</span> none (former TAG member David Orchard will join us Wed. evening and Thursday)
</p></div>
<!-- ************************************* -->
<!-- Agenda summary table -->
<!-- ************************************* -->
<h2 id="Agenda">Agenda Summary</h2>
<table class="agendatable" border="1" cellpadding="1" cellspacing="1">
<tbody>
<!-- - - - - - - - - - - - - - - - - - - -->
<!-- Tuesday -->
<!-- - - - - - - - - - - - - - - - - - - -->
<tr>
<td class="date calendarTimeHeading" align="left" valign="top" colspan="3" >Tues 3rd March</td>
</tr>
<tr>
<td colspan="2" style="text-align:center">Agenda</td>
<td style="text-align:center">Minutes</td>
</tr>
<tr>
<td align="left" valign="top">09:00-9:30</td>
<td align="left" valign="top"><a href="#convene">Convene</a>
<br />
Welcome new members
<br />
Review: F2F Goals and Agenda
<br />
</td>
<td rowspan="11">
<ol>
<li><a href="03-tagmem-minutes.html#item01">Convene</a></li>
<li><a href="03-tagmem-minutes.html#item02">Introductions</a></li>
<li><a href="03-tagmem-minutes.html#item03">HTTP Content Negotiation (maybe track under
ISSUE-57 or should we open a new one?)</a></li>
<li><a href="03-tagmem-minutes.html#item04">HTML and "TAG Soup" Integration
(ISSUE-54)</a></li>
<li><a href="03-tagmem-minutes.html#item05">URNsAndRegistries-50 ISSUE-50</a></li>
<li><a href="03-tagmem-minutes.html#item06">Review of ongoing TAG projects</a></li>
<li><a href="03-tagmem-minutes.html#item07">Issue status: whenToUseGet-7, etc.</a></li>
<li><a href="03-tagmem-minutes.html#item08">Administration: TAG Operations, Scheduling
Future Meetings</a></li>
</ol>
</td>
</tr>
<tr>
<td align="left" valign="top">9:30-10:30</td>
<td align="left" valign="top"><a href="#conneg">HTTP Content negotiation</a></td>
</tr>
<tr>
<td align="left" valign="top">10:30-10:45</td>
<td align="left" valign="top">Break (15 mins)</td>
</tr>
<tr>
<td align="left" valign="top">10:45-12:00</td>
<td align="left" valign="top"><a href="#HTML">HTML and "Tag Soup" Integration</a><br />
</td>
</tr>
<tr>
<td align="left" valign="top">12:00-13:15</td>
<td align="left" valign="top">Lunch (75 mins)</td>
</tr>
<tr>
<td align="left" valign="top">13:15-14:00</td>
<td align="left" valign="top"><a href="#URNsandRegistries">URNsAndRegistries-50</a>: URIs, URNs, "location independent" naming systems and associated registries for naming on the Web (review - Henry)
</td>
</tr>
<tr>
<td align="left" valign="top">14:00-15:00</td>
<td align="left" valign="top"><a href="#issues">Review of ongoing TAG projects</a></td>
</tr>
<tr>
<td align="left" valign="top">15:00-15:30</td>
<td align="left" valign="top">Break (30 mins)</td>
</tr>
<tr>
<td align="left" valign="top">15:30-16:00</td>
<td align="left" valign="top"><a href="#issues">Issue Prioritization</a></td>
</tr>
<tr>
<td align="left" valign="top">16:00-16:30</td>
<td align="left" valign="top"><a href="#admin">Administration</a>:
<ul>
<li>TAG Operations</li>
<li>Scheduling Future Meetings</li>
</ul>
</td>
</tr>
<tr>
<td align="left" valign="top">16:30-17:00</td>
<td align="left" valign="top">...available...</td>
</tr>
<!-- - - - - - - - - - - - - - - - - - - -->
<!-- Wednesday -->
<!-- - - - - - - - - - - - - - - - - - - -->
<tr>
<td class="date calendarTimeHeading" align="left" valign="top" colspan="3" >Weds 4th March</td>
</tr>
<tr>
<td colspan="2" style="text-align:center">Agenda</td>
<td style="text-align:center">Minutes</td>
</tr>
<tr>
<td align="left" valign="top">09:00-10:30</td>
<td align="left" valign="top"><a href="#TAGpriorities">TAG Priorities for Coming Year</a> - initial discussion
</td>
<td rowspan="8">
<ol>
<li><a href="http://www.w3.org/2001/tag/2009/03/04-minutes.html#item01">TAG priorities for the coming year</a></li>
<li><a href="http://www.w3.org/2001/tag/2009/03/04-minutes.html#item02">webApplicationState-60: Web application state management</a></li>
<li><a href="http://www.w3.org/2001/tag/2009/03/04-minutes.html#item03">httpRedirections-57: Resource description discovery and access</a></li>
<li><a href="http://www.w3.org/2001/tag/2009/03/04-minutes.html#item04">xmlFunctions-34: XML Transformation and composability -- review</a></li>
</ol>
</td>
</tr>
<tr>
<td align="left" valign="top">10:30-11:00</td>
<td align="left" valign="top">Break (30 mins)</td>
</tr>
<tr>
<td align="left" valign="top">11:00-12:00</td>
<td align="left" valign="top"><a href="#webApplicationState"> webApplicationState-60</a>: Web Application State Management (Raman?)
</td>
</tr>
<tr>
<td align="left" valign="top">12:00-13:15</td>
<td align="left" valign="top">Lunch (75 mins)</td>
</tr>
<tr>
<td align="left" valign="top">13:15-14:45</td>
<td align="left" valign="top"><a href="#httpRedirections">httpRedirections-57</a>: Resource description discovery and access
</td>
</tr>
<tr>
<td align="left" valign="top">14:45-15:15</td>
<td align="left" valign="top"><a href="#xmlFunctions">xmlFunctions-34</a>: XML Transformation and composability (review - Henry)
</td>
</tr>
<tr>
<td align="left" valign="top">15:15-15:45</td>
<td align="left" valign="top">Break (30 mins)</td>
</tr>
<tr>
<td align="left" valign="top">15:45-17:00</td>
<td align="left" valign="top">This was supposed to be <a href="#errorhandling">errorHandling-20</a>: Error handling, but we decided to use it for more of <a href="#xmlFunctions">xmlFunctions-34</a>.
</td>
</tr>
<!-- - - - - - - - - - - - - - - - - - - -->
<!-- Thursday -->
<!-- - - - - - - - - - - - - - - - - - - -->
<tr>
<td class="date calendarTimeHeading" align="left" valign="top" colspan="3" >Thurs 5th March</td>
</tr>
<tr>
<td colspan="2" style="text-align:center">Agenda</td>
<td style="text-align:center">Minutes</td>
</tr>
<tr>
<td align="left" valign="top">09:00-10:30</td>
<td align="left" valign="top"><a href="#TAGpriorities">TAG Priorities for Coming Year</a> - conclusion
</td>
<td rowspan="7">
<ol>
<li><a href="05-minutes.html#item01">TAG Priorities for 2009</a></li>
<li><a href="05-minutes.html#item02">Error Handling 20</a></li>
<li><a href="05-minutes.html#item03">Other items (mostly TAG priorities)</a></li>
</ol>
</td>
</tr>
<tr>
<td align="left" valign="top">10:30-11:00</td>
<td align="left" valign="top">Break (30 mins)</td>
</tr>
<tr>
<td align="left" valign="top">11:00-12:00</td>
<td align="left" valign="top"><a href="#errorhandling">errorHandling-20</a>: Error handling
</td>
</tr>
<tr>
<td align="left" valign="top">12:00-13:15</td>
<td align="left" valign="top">Lunch (75 mins)</td>
</tr>
<tr>
<td align="left" valign="top">13:15-15:00</td>
<td align="left" valign="top">...available...</td>
</tr>
<tr>
<td align="left" valign="top">15:00</td>
<td class="bold" align="left" valign="top">Meeting adjourns</td>
</tr>
<tr>
<td align="left" valign="top">15:00-17:00</td>
<td align="left" valign="top">...those who are not traveling until Friday may wish to stay for informal discussion...</td>
</tr>
<!-- - - - - - - - - - - - - - - - - - - -->
<!-- Unscheduled topics -->
<!-- - - - - - - - - - - - - - - - - - - -->
<tr>
<td class="date" align="left" valign="top" colspan="3" ><span class="calendarTimeHeading">Unscheduled topics</span>
<br />
There are some other topics we may decide
to discuss in the free
time slots.
Suggested discussion goals
and preparation materials
are available in the section linked
below.</td>
</tr>
<tr>
<td align="left" valign="top"></td>
<td align="left" valign="top"><a href="#unscheduled">Unscheduled topics</a>
</td>
</tr>
</tbody>
</table>
<div class="nonlistsection">
<p>Note that preparation is also encouraged for some items for which <a href="#unscheduled">fixed time slots have not been allocated</a>.
We may or may not decide to discuss some or all of these, presumably in the sessions not yet scheduled.</p>
</div>
<!-- ************************************* -->
<!-- Logistics -->
<!-- ************************************* -->
<h2 id="Logistics">Logistics</h2>
<div class="nonlistsection">
<p>(also separate <a href="03-f2f-local-arrangements.html">Logistics</a>
page)</p>
<dl>
<dt><strong>Venue</strong></dt>
<dd>Oracle Conference Center (OCC) <br />
Building 350 <br />
Oracle Parkway, <br />
Redwood Shores, <br />
CA, 94065
<br />
The campus
is located about 10 miles South of San Francisco (SFO) airport. See <a href="http://lists.w3.org/Archives/Member/tag/2009Jan/att-0032/hq_map.pdf">map</a>
for directions.
</dd>
<dt><strong>Schedule:</strong></dt>
<dd>Tue 3 March: 09:00 - 17:00<br />
Wed 4 March: 09:00 - 17:00<br />
Thurs 5 March: 09:00 - 15:00</dd>
</dl>
</div> <!-- nonlistsection -->
<h2 id="agendaDetails">Agenda Details</h2>
<!-- Individual agenda items are marked up as li within the ol -->
<!-- Nested lists can be used (though CSS for nested ol isn't in place yet -->
<!-- for nested headings on sub-lists like "goals", use h3 -->
<!-- ************************************* -->
<!-- Convene -->
<!-- ************************************* -->
<ol>
<li><a name="convene">Convene</a>
<ul>
<li>Welcome new members</li>
<li>Appoint scribes</li>
<li>Review F2F Goals
<ul>
<li>Bring new TAG members "up to speed" on continuing work</li>
<li>Make progress on high priority technical issues</li>
<li>Establish TAG priorities for coming year - ensure issues list reflects actual priorities</li>
<li>Refine TAG administrative procedures</li>
</ul>
</li>
<li>Review F2F Agenda (this document)</li>
<li>Approve <a href="http://www.w3.org/2001/tag/2009/02/19-minutes">Minutes of TAG Telcon of 19 February 2009</a></li>
</ul>
</li>
<!-- ************************************* -->
<!-- Content Negotiation -->
<!-- ************************************* -->
<li><a name="conneg">HTTP Content Negotiation</a> (maybe track under <a href="http://www.w3.org/2001/tag/group/track/issues/57">ISSUE-57</a> or should we open a new one?)
<h3>Background:</h3>
<div class="nonlistsection">
<p>
Several recent email threads have raised questions about the proper use of content negotiation on the Web. In particular, these questions have included:
</p>
</div>
<ul>
<li>When, if ever, is it appropriate to use content negotiation
to choose between representations of a resource and
descriptions of that resource?
Should redirection be used in conjunction with content negotiation for such purposes?</li>
<li>Typical AJAX applications use Javascript and HTML to
create a presentation that is derived from one or
more data sources which themselves are identified with URIs.
Sometimes the presentation is a very direct rendering
of the data, but in other cases one may wish to have separate
links for the underlying data (e.g. an email document) and
for its presentation in some particular user agent (e.g. Google gmail).
Using separate URIs for these can be inconvenient, since
in many cases both links will need to be recorded or transmitted.
The TAG has been asked (email from Martin Nally, linked below) whether
use of content negotiation might be an appropriate
compromise. </li>
<li>The treatment of content negotiation in HTTPbis is likely
to be revised, and there is some suggestion that content
negotiation should be deprecated.</li>
</ul>
<h3>Goals:</h3>
<ul>
<li>Explore technical issues relating to content negotiation</li>
<li>Decide whether TAG wants to pursue work on one or more of
the questions discussed above</li>
<li>Identify next steps</li>
</ul>
<h3>Preparation:</h3>
<ul>
<li><a href="http://lists.w3.org/Archives/Public/www-tag/2009Feb/0074.html">Email from Michael Hausenblas</a> asking for TAG guidance
on the proper use of content negotiation.
See also the thread following from that <a href="http://lists.w3.org/Archives/Public/www-tag/2009Feb/subject.html">in the email listing for February</a>, and the related thread starting with the message <a href="http://lists.w3.org/Archives/Public/www-tag/2009Feb/0183.html">Last minute input to discussion re 'on the boundaries of content negotiation in the context of the Web of Data'</a></li>
<li>
Jonathan Rees points us to three emails he has sent on this subject, with the hint that
that they get "progressively better". So, he suggests the
<a href="http://lists.w3.org/Archives/Public/www-tag/2009Feb/0080.html">first</a> and the
<a href="http://lists.w3.org/Archives/Public/www-tag/2009Feb/0170.html">second</a> as
optional reading for the F2F, and the
<a href="http://lists.w3.org/Archives/Public/www-tag/2009Feb/0172.html">third</a>
as required (Jonathan's suggestions along with a little additional background
are in <a href="http://lists.w3.org/Archives/Member/tag/2009Feb/0102.html">this email</a> - member only)
</li>
<li>Larry Masinter <a href="http://lists.w3.org/Archives/Public/www-tag/2009Feb/0211.html">email</a> indicating that
he will be updating the HTTPbis section on content negotiation. Tim Berners-Lee response email suggesting
that <a href="http://lists.w3.org/Archives/Member/tag/2009Feb/0105.html">deprecation of content negotiation would be a bad idea</a> (member only).</li>
<li><a href="http://lists.w3.org/Archives/Public/www-tag/2009Feb/0198.html">Email from Martin Nally</a> describing challenges in deciding
whether to use content negotiation to choose between the presentation and the data driving the presentation in an Ajax application</li>
</ul>
</li>
<!-- ************************************* -->
<!-- HTML -->
<!-- ************************************* -->
<li><a name="HTML">HTML and "TAG Soup" Integration</a> (<a href="http://www.w3.org/2001/tag/group/track/issues/54">ISSUE-54</a>)
<h3>Goals:</h3>
<ul>
<li>Review history, successes, and challenges with respect to TAG's efforts to assist the HTML community</li>
<li>Decide what, if anything, the TAG should set as goals for work on HTML this year. Explore ways that we can be helpful to the HTML 5 working group and to other W3C groups that provide HTML-based technologies.</li>
<li>Clarify relationship to TAG work in areas such as error handling, versioning, etc.</li>
</ul>
<h3>Preparation:</h3>
<ul>
<li>T.V. Raman's analysis prepared for agenda of the TAG's Sept. 2008 meeting in Kansas City.
It's in the agenda itself under the heading <a href="http://www.w3.org/2001/tag/2008/09/f2fkc-agenda#htmlAndWebBigPicture">tagSoupIntegration-54 - HTML and The Web</a>.</li>
<li>Update from Dan Connolly on <a href="http://lists.w3.org/Archives/Member/tag/2009Feb/0080.html">HTML/Tag Soup Progress since TPAC</a> (member-only)</li>
<li>HTML working group action 108 <a href="http://www.w3.org/html/wg/tracker/actions/108">requests that the TAG consider HTML when working on versioning</a></li>
</ul>
</li>
<!-- ************************************* -->
<!-- Error Handling -->
<!-- ************************************* -->
<li><a name="errorhandling">Error handling</a> (<a href="http://www.w3.org/2001/tag/group/track/issues/20">ISSUE-20</a>)
<h3>Goals:</h3>
<ul>
<li>Explore architectural principles relating to error recovery by software receiving incorrect data from Web interactions.
Explore tradeoffs involving silent recovery from errors, robustness of Web communications, risk of incorrect processing,
proliferation of incorrect content, vs. convenience for others and recipients of documents.</li>
<li>Decide what, if anything, the TAG should set as goals for work on error handling this year</li>
<li>Clarify relationship to TAG work in areas such as HTML/Tag soup, versioning, etc.</li>
</ul>
<h3>Action:</h3>
<ul>
<li><a href="http://www.w3.org/2001/tag/group/track/actions/199">ACTION-199</a> on Henry S. Thompson to Follow up on error handling thread (8 Oct) - due <span class="date overdue">2009-02-17</span>, pending review</li>
</ul>
<h3>Preparation:</h3>
<ul>
<li><a href="http://www.w3.org/2001/tag/2009/02/19-minutes#item03">Error handling discussion in minutes of TAG Telcon of 19 February 2009</a></li>
<li>Email thread on <a href="http://lists.w3.org/Archives/Public/www-tag/2009Feb/0040.html">HTML and XML</a></li>
</ul>
</li>
<!-- ************************************* -->
<!-- XML Functions -->
<!-- ************************************* -->
<li><a name="xmlFunctions">XML Functions</a> (<a href="http://www.w3.org/2001/tag/group/track/issues/34">ISSUE-34</a>)
<h3>Goals:</h3>
<ul>
<li>Bring new (and returning) members up to date on prior work on XML Functions.</li>
<li>Brief discussion of technical issues, if time permits.</li>
<li>Clarify goals and next steps.</li>
</ul>
<h3>Action:</h3>
<ul>
<li><a href="http://www.w3.org/2001/tag/group/track/actions/113">ACTION-113</a> on Henry S. Thompson to HT to a) revise <a href="http://www.ltg.ed.ac.uk/~ht/compositional.pdf">composition.pdf</a>[sic] to take account of suggestions from Tim & Jonathan and feedback from email and b) produce a new version of the Elaborated Infoset finding, possibly incorporating some of the PDF - due <span class="date">2009-03-27</span>, open</li>
</ul>
<h3>Preparation:</h3>
<ul>
<li><a href="http://www.w3.org/2001/tag/doc/elabInfoset-20071127/elabInfoset.html">The elaborated infoset: A proposal</a> by Henry Thompson</li>
<li><a href="http://www.ltg.ed.ac.uk/~ht/compositional.pdf">Compositionality, elaboration and XML document
semantics</a> by Henry Thompson (28 November 2007)</li>
</ul>
</li>
<!-- ************************************* -->
<!-- URNS and Registries -->
<!-- ************************************* -->
<li><a name="URNsandRegistries">URNsandRegistries-50</a>: URIs, URNs, "location independent" naming systems and associated registries for naming on the Web (<a href="http://www.w3.org/2001/tag/group/track/issues/50">ISSUE-50</a>)
<h3>Goals:</h3>
<ul>
<li>Bring new (and returning) members up to date on prior work on issue URNsAndRegistries-50.</li>
<li>Brief discussion of technical issues, if time permits.</li>
<li>Clarify goals and next steps.</li>
</ul>
<h3>Action:</h3>
<ul>
<li><a href="http://www.w3.org/2001/tag/group/track/actions/33">ACTION-33</a> on Henry S. Thompson to revise naming challenges story in response to Dec 2008 F2F discussion - due <span class="date">2009-03-27</span>, open</li>
<li><a href="http://www.w3.org/2001/tag/group/track/actions/121">ACTION-121</a> on Henry S. Thompson to HT to draft TAG input to review of draft ARK RFC - due <span class="date">2009-03-27</span>, open</li>
</ul>
<h3>Preparation:</h3>
<ul>
<li><a href="http://www.w3.org/2001/tag/doc/URNsAndRegistries-50-2006-08-17">URNs, Namespaces and Registries</a> by Henry Thompson and David Orchard (yes, sadly, the latest revision on this draft is from August, 2006)</li>
</ul>
</li>
<!-- ************************************* -->
<!-- Web Application State -->
<!-- ************************************* -->
<li><a name="webApplicationState">webApplicationState-60</a>Web Application State Management (<a href="http://www.w3.org/2001/tag/group/track/issues/60">ISSUE-60</a>)
<h3>Goals:</h3>
<ul>
<li>Bring new (and returning) members up to date on prior work on issue webApplicationState-60</li>
<li>Discuss technical issues</li>
<li>Clarify goals and next steps</li>
</ul>
<h3>Actions:</h3>
<ul>
<li><a href="http://www.w3.org/2001/tag/group/track/actions/143">ACTION-143</a> on Stuart Williams to Review Raman's draft of webApplicationState-60 - due <span class="date">2009-03-03</span>, open</li>
<li><a href="http://www.w3.org/2001/tag/group/track/actions/144">ACTION-144</a> on Noah Mendelsohn to Attempt to articulate some of the higher level questions for inclusion in the draft. - due <span class="date">2009-03-03</span>, open</li>
</ul>
<h3>Preparation:</h3>
<ul>
<li><a href="http://www.w3.org/2001/tag/doc/hash-in-url-20080211.html">Usage Patterns For Client-Side URL parameters </a> by T.V. Raman - 11 February 2008</li>
<li><a href="http://lists.w3.org/Archives/Public/www-tag/2009Feb/0198.html">Email from Martin Nally</a> describing challenges in deciding
whether to use content negotiation to choose between the presentation and the data driving the presentation in an Ajax application.
This email also relates to application state management and use of URIs to track application state.</li>
</ul>
</li>
<!-- ************************************* -->
<!-- Resource descriptions & -->
<!-- httpRedirections-57 -->
<!-- ************************************* -->
<li><a name="httpRedirections">httpRedirections-57: Resource description discovery and access</a> (<a href="http://www.w3.org/2001/tag/group/track/issues/57">ISSUE-57</a>)
<h3>Goals:</h3>
<ul>
<li>Review history and status of work in ISSUE-57 and resource description access in general</li>
<li>Decide what, if anything, the TAG wants to do in this area starting now</li>
<li>Clarify relationship to TAG work in areas such as metadata, content negotiation, site description metadata, etc.</li>
</ul>
<h3>Actions:</h3>
<ul>
<li><a href="http://www.w3.org/2001/tag/group/track/actions/116">ACTION-116</a> on Tim Berners-Lee to Align the tabulator internal vocabulary with the vocabulary in the rules http://esw.w3.org/topic/AwwswDboothsRules, getting changes to either as needed. - due <span class="date overdue">2009-02-24</span>, open</li>
<li><a href="http://www.w3.org/2001/tag/group/track/actions/178">ACTION-178</a> on Jonathan Rees to update draft of finding on uniform access to metadata. - due <span class="date overdue">2009-02-13</span>, open</li>
<li><a href="http://www.w3.org/2001/tag/group/track/actions/200">ACTION-200</a> on Jonathan Rees to Revise "Uniform Access to Metadata" (needs title change) to add XRD use case - due <span class="date overdue">2009-02-24</span>, pending review</li>
<li><a href="http://www.w3.org/2001/tag/group/track/actions/201">ACTION-201</a> on Jonathan Rees to Report on status of AWWSW discussions - due <span class="date">2009-03-30</span>, open</li>
<li><a href="http://www.w3.org/2001/tag/group/track/actions/217">ACTION-217</a> on Jonathan Rees to Raise moving the registry to w3.org with Mark Nottingham - due <span class="date overdue">2009-02-24</span>, pending review</li>
</ul>
<h3>Preparation:</h3>
<ul>
<li><a href="http://lists.w3.org/Archives/Public/www-tag/2009Feb/0235.html">Stuart Williams' email</a> summarizing the history and status of ISSUE-57</li>
<li><a href="http://www.w3.org/2001/tag/doc/uniform-access-20090205.html">Uniform Access to Metadata</a> (5 Feb 2009 draft by Phil Archer and Jonathan Rees) and assocated <a href="http://lists.w3.org/Archives/Public/www-tag/2009Feb/0034.html">email thread</a></li>
<li>Internet draft <a href="http://tools.ietf.org/html/draft-hammer-discovery-02">HTTP-based Resource Descriptor Discovery
(draft-hammer-discovery-02)</a> by E. Hammer-Lahav</li>
<li>(optional) Internet draft <a href="http://tools.ietf.org/html/draft-nottingham-http-link-header-04">Link Relations and HTTP Header Linking (draft-nottingham-http-link-header-04)</a> by Mark Nottingham</li>
<li>(optional) Internet draft <a href="http://tools.ietf.org/html/draft-nottingham-site-meta-01">Host Metadata for the Web (draft-nottingham-site-meta-01)</a> by M. Nottingham and E. Hammer-Lahav</li>
</ul>
</li>
<!-- ************************************* -->
<!-- Issues List Revision -->
<!-- ************************************* -->
<li id="issues"><a href="http://www.w3.org/2001/tag/group/track/issues/open">Review of ongoing TAG projects & Issue Prioritization </a>
<h3>Goals:</h3>
<div class="nonlistsection">
<p>
The TAG goes into this meeting with 28 open issues.
The overall goal of this session to identify a few key issues from our previous work
that we will designate as possible major focus items for the coming year, to identify other issues that should remain
active with lesser emphasis, and as appropriate to close (or open) others.
In <a href="#TAGpriorities">other F2F sessions</a>, we will consider suggestions for new focus areas and priorities, so the
final TAG
agenda for the coming year
will likely be a combination of ongoing work continued or refocused, along with new undertakings.
This particular F2F session is aimed at ensuring that we understand and are properly tracking the status of
work already underway.
When we are done, the issues list should reflect in the description field the goals, deliverables, checkpoints, and success criteria for issues that remain active.
</p>
<p>
Specific goals for this F2F session are:</p>
</div>
<ul>
<li>Review open issues and close or change status as necessary.
This is an opportunity for returning TAG members to remind themselves of the status of our long list of issues, and especially
for new members to come up to speed.
We will do this by splitting into small groups, each of which will do the following for a handful of issues:
<ul>
<li>Ensure that goals, deliverables, checkpoints and success criteria are understood, at least for high priority issues and preferably for all active issues.</li>
<li>Recommend whether the issue should remain open or be closed. If open, then whether the issue should be
one of the few key focus areas of the TAG, or should have lesser emphasis.
</li>
</ul>
</li>
<li>After the breakout reviews are done, we will discuss recommendations, especially for high priority focus areas. If time
permits, we will agree on revised status for all issues. If that proves a bad use of F2F time, then we will plan to
finish the job via email and/or telcons as appropriate.
The essential goal here is to learn enough that we can appropriately balance proposals for new TAG work
with following through on our existing activities.</li>
<li>Also, the chair would like to propose more direct ongoing (I.e. post F2F) involvement of the rest of the TAG
in tracking the status of particular TAG issues. We will discuss details at the F2F.</li>
</ul>
<h3>Preparation:</h3>
<ul>
<li>Review <a href="#issuetable">open TAG issues table</a> below. Think in advance about which ones we should be our main priorities, which ones should be closed, and which should continue as background activities.</li>
</ul>
</li>
<!-- ************************************* -->
<!-- Setting TAG Priorities -->
<!-- ************************************* -->
<li id="TAGpriorities">TAG Priorities for Coming Year
<h3>Goals:</h3>
<ul>
<li>Discuss specific proposals for new TAG directions and focus areas</li>
<li>Determine specific TAG goals and priorities for coming year.</li>
<li>For each such goal or direction, briefly identify success criteria, timeframes, the intended audience for any materials we produce, and next steps.</li>
</ul>
<h3>Preparation:</h3>
<ul>
<li>Review <a href="http://lists.w3.org/Archives/Public/www-archive/2009Feb/0105.html">Larry Masinter's suggestions for new TAG work areas</a></li>
<li>Review <a href="#issuetable">open TAG issues table</a> (below)</li>
<li>Consider whether the <a href="http://www.w3.org/TR/webarch/">Architecture of the World Wide Web</a> and the <a href="http://www.w3.org/2001/tag/findings">findings</a> that the TAG publishes
are effective in getting the attention of and educating their intended audience(s).
</li>
</ul>
<div class="nonlistsection">
<p>
We will discuss this topic at least twice. The first session will focus on briefly reviewing proposals for new directions for TAG work,
as well as proposals for which ongoing activites should be emphasized.
We will also discuss which aspects of the TAG's work have been most effective, and which have not been effective.
Note that we will in a separate session do a detailed review of all ongoing TAG activity (I.e. open issues), closing and reprioritizing as appropriate.
The results of that analysis will be used as input to the second round discussion, which will attempt to set our overall priorities for the coming year.
</p>
</div>
</li>
<!-- ************************************* -->
<!-- Administration -->
<!-- ************************************* -->
<li id="admin">Administration
<h3>Goals:</h3>
<ul>
<li>Discuss (minor) changes in TAG administrative procedures</li>
<li>Get concurrence on contents of <a href="http://www.w3.org/2001/tag/coordination/TAGGuide.html">Guide to TAG Participation</a> (W3C member-only),
making revisions as necessary</li>
<li>Make plan to ensure everyone has access to CVS & other tools needed to
assist with TAG operations, scribing, and document publication</li>
<li>Schedule upcoming F2F meeting(s) (<a href="http://lists.w3.org/Archives/Member/w3c-ac-forum/2009JanMar/0058.html">email from Steve Bratt</a> - member only)</li>
</ul>
<h3>Preparation:</h3>
<ul>
<li>Read draft of <a href="http://www.w3.org/2001/tag/coordination/TAGGuide.html">Guide to TAG Participation</a> (W3C member-only).
Either be prepared to endorse it as is, or to suggest specific changes.
</li>
</ul>
</li>
<!-- ************************************* -->
<!-- Unscheduled Items -->
<!-- ************************************* -->
<li id="unscheduled">Unscheduled items
<div class="nonlistsection">
<p>
No specific discussion time is allocated to the following, but we may choose to discuss these in some of the free time slots.
</p>
</div>
<ul>
<li>(late addition to this agenda) The TAG has, within the last week, been <a href="http://lists.w3.org/Archives/Public/www-tag/2009Feb/0295.html">asked to help resolve concerns
with the use of CURIEs in RDFa and with the HTML profile attribute</a>. See very long email thread that was instigated with an <a href="http://lists.w3.org/Archives/Public/www-tag/2009Feb/0270.html">email message from Mark Nottingham to www-tag titled "Using XMLNS in link/@rel"</a>, which in turn promoted a message to the public-html list from Julian Reschke titled <a href="http://lists.w3.org/Archives/Public/public-html/2009Feb/0753.html">@rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel</a>. The long thread starts with that; early messages in the thread were not cross-posted to www-tag, but later ones were (starting with <a href="http://lists.w3.org/Archives/Public/www-tag/2009Feb/0279.html">this one</a>).</li>
<li>contentTypeOverride-24 (<a href="http://www.w3.org/2001/tag/group/track/issues/24">ISSUE-24)</a>: Dan Connolly <a href="">suggests</a> that we discuss the draft <a href="http://ietfreport.isoc.org/idref/draft-abarth-mime-sniff/">Content-Type Processing Model</a>, by Ian Hickson and Adam Barth; the draft proposes interoperable rules for Content-type "sniffing" in browsers. Note that the draft acknowledges at one point that it is in "... willful violation of the HTTP specification. [<a href="http://www.ietf.org/rfc/rfc2616.txt">RFC2616</a>]
</li>
<li> XMLVersioning-41 (<a href="http://www.w3.org/2001/tag/group/track/issues/41">ISSUE-41</a>).
<br />
Background:
<ul>
<li>
HTML working group action 108 <a href="http://www.w3.org/html/wg/tracker/actions/108">requests that the TAG consider HTML when working on versioning</a></li>
<li>
Thread starting with <a href="http://lists.w3.org/Archives/Public/www-tag/2009Feb/0147.html">John Kemp email on updating AWWW good practice note on versioning</a>
</li>
<li><a href="http://www.w3.org/2001/tag/group/track/actions/183">ACTION-183</a> (David Orchard) Incorporate formalism into versioning compatibility strategies. Due 3 March 2009.</li>
<li><a href="http://www.w3.org/2001/tag/group/track/actions/221">ACTION-221</a> (Jonathan Rees) Work with Dave Orchard to close up the formalism facet of the versioning document, due in two weeks. Due 24 February 2009 (OVERDUE).</li>
<li><a href="http://www.w3.org/2001/tag/group/track/actions/229">ACTION-229</a> (Noah Mendelsohn) Noah to respond to John Kemp proposal of Feb 17 on versioning. Due 13 March 2009. </li>
</ul>
</li>
<li>Should TAG focus more on the mobile Web and the growing use of smartphones with the Web? (Noah is interested in this.)</li>
<li>Review of Open Action Items
<ul>
<li>Review <a href="http://www.w3.org/2001/tag/group/track/actions/open">open
action items</a>: reassign owned by those who are leaving the TAG.</li>
<li>Review and, if possible, close <a href="http://www.w3.org/2001/tag/group/track/actions/pendingreview">pending review action items</a></li>
</ul>
</li>
<li>Update on the <a href="http://lists.w3.org/Archives/Public/public-awwsw/">Architecture of the World Wide Semantic Web</a> AWWSW work.
</li>
</ul>
</li>
</ol>
<!-- ************************************* -->
<!-- ISSUE LIST TABLE -->
<!-- ************************************* -->
<h2 id="issuetable">Open W3C TAG Issues as of 24 February 2009</h2>
<div class="nonlistsection">
<p>
The following list was extracted from Tracker's list of <a href="http://www.w3.org/2001/tag/group/track/issues/open">open issues</a>.
The "F2F" column indicates issues that appear as explicit agenda items for this F2F.
We will discuss the "Proposed Priority" column at the meeting.
</p>
</div>
<table class="issuetable" border="1" cellpadding="0" style="border-collapse:
collapse;border:solid;">
<tr>
<th class="rightalign">ISSUE #</th>
<th class="centeralign">F2F</th>
<th>Old Issue Name</th>
<th>Proposed
<br />
Priority</th>
<th>Description</th>
<th class="centeralign">Raised on</th>
<th class="rightalign">
Number of
<br />
Open Actions</th>
</tr>
<tr>
<td class="rightalign"><a href="http://www.w3.org/2001/tag/group/track/issues/7">7</a></td>
<td class="centeralign"></td>
<td>whenToUseGet-7</td>
<td>Close</td>
<td>(1) GET should be encouraged, not deprecated, in XForms(2) How to handle
safe queries <span style='display:none'>(New POST-like method?GET plus a
body?)</span></td>
<td class="centeralign">23-Jan-02</td>
<td class="rightalign">0</td>
</tr>
<tr>
<td class="rightalign"><a href="http://www.w3.org/2001/tag/group/track/issues/16">16</a></td>
<td class="centeralign"></td>
<td>HTTPSubstrate-16</td>
<td>Close</td>
<td>Should HTTP be used as a substrate protocol? Does W3Cagree with RFC 3205?</td>
<td class="centeralign">24-Mar-02</td>
<td class="rightalign">0</td>
</tr>
<tr>
<td class="rightalign"><a href="http://www.w3.org/2001/tag/group/track/issues/20">20</a></td>
<td class="centeralign">X</td>
<td>errorHandling-20</td>
<td>High</td>
<td>What should specifications say about error handling?</td>
<td class="centeralign">22-May-02</td>
<td class="rightalign">0</td>
</tr>
<tr>
<td class="rightalign"><a href="http://www.w3.org/2001/tag/group/track/issues/24">24</a></td>
<td class="centeralign"></td>
<td>contentTypeOverride-24</td>
<td>Background</td>
<td>Can a specification include rules for overriding HTTPcontent type
parameters?</td>
<td class="centeralign">14-Jun-02</td>
<td class="rightalign">0</td>
</tr>
<tr>
<td class="rightalign"><a href="http://www.w3.org/2001/tag/group/track/issues/27">27</a></td>
<td class="centeralign"></td>
<td>IRIEverywhere-27</td>
<td>Background</td>
<td>Should W3C specifications start promoting IRIs?</td>
<td class="centeralign">9-Oct-02</td>
<td class="rightalign">2</td>
</tr>
<tr>
<td class="rightalign"><a href="http://www.w3.org/2001/tag/group/track/issues/28">28</a></td>
<td class="centeralign"></td>
<td>fragmentInXML-28</td>
<td>Background</td>
<td>Use of fragment identifiers in XML</td>
<td class="centeralign">31-Oct-02</td>
<td class="rightalign">0</td>
</tr>
<tr>
<td class="rightalign"><a href="http://www.w3.org/2001/tag/group/track/issues/30">30</a></td>
<td class="centeralign"></td>
<td>binaryXML-30</td>
<td>Background</td>
<td>Standardize a "binary XML" format?</td>
<td class="centeralign">9-Oct-02</td>
<td class="rightalign">1</td>
</tr>
<tr>
<td class="rightalign"><a href="http://www.w3.org/2001/tag/group/track/issues/33">33</a></td>
<td class="centeralign"></td>
<td>mixedUIXMLNamespace-33</td>
<td>??</td>
<td>Composability for user interface-oriented XML namespaces</td>
<td class="centeralign">6-Feb-03</td>
<td class="rightalign">0</td>
</tr>
<tr>
<td class="rightalign"><a href="http://www.w3.org/2001/tag/group/track/issues/34">34</a></td>
<td class="centeralign">X</td>
<td>xmlFunctions-34</td>
<td>Medium</td>
<td>XML Transformation and composability (e.g., XSLT,XInclude, Encryption)</td>
<td class="centeralign">6-Feb-03</td>
<td class="rightalign">1</td>
</tr>
<tr>
<td class="rightalign"><a href="http://www.w3.org/2001/tag/group/track/issues/36">36</a></td>
<td class="centeralign"></td>
<td>siteData-36</td>
<td>Medium</td>
<td>Web site metadata improving on robots.txt, w3c/p3p and favicon etc.</td>
<td class="centeralign">10-Feb-03</td>
<td class="rightalign">0</td>
</tr>
<tr>
<td class="rightalign"><a href="http://www.w3.org/2001/tag/group/track/issues/37">37</a></td>
<td class="centeralign"></td>
<td>abstractComponentRefs-37</td>
<td>??</td>
<td>Definition of abstract components with namespace names and frag ids</td>
<td class="centeralign">3-Feb-03</td>
<td class="rightalign">0</td>
</tr>
<tr>
<td class="rightalign"><a href="http://www.w3.org/2001/tag/group/track/issues/39">39</a></td>
<td class="centeralign"></td>
<td>rdfURIMeaning-39</td>
<td>??</td>
<td>Meaning of URIs in RDF documents</td>
<td class="centeralign">13-Jul-03</td>
<td class="rightalign">0</td>
</tr>
<tr>
<td class="rightalign"><a href="http://www.w3.org/2001/tag/group/track/issues/40">40</a></td>
<td class="centeralign"></td>
<td>URIGoodPractice-40</td>
<td>Background</td>
<td>What are good practices for URI construction?</td>
<td class="centeralign">16-Oct-03</td>
<td class="rightalign">0</td>
</tr>
<tr>
<td class="rightalign"><a href="http://www.w3.org/2001/tag/group/track/issues/41">41</a></td>
<td class="centeralign"></td>
<td>XMLVersioning-41</td>
<td>Background</td>
<td>What are good practices for designing extensible XMLlanguages and for
handling versioni<span style='display:none'>ng?</span></td>
<td class="centeralign">27-Jun-03</td>
<td class="rightalign">3</td>
</tr>
<tr>
<td class="rightalign"><a href="http://www.w3.org/2001/tag/group/track/issues/42">42</a></td>
<td class="centeralign"></td>
<td>ultimateQuestion-42</td>
<td></td>
<td>What is the answer to life, the universe, and everything.</td>
<td class="centeralign">15-Nov-03</td>
<td class="rightalign">3</td>
</tr>
<tr>
<td class="rightalign"><a href="http://www.w3.org/2001/tag/group/track/issues/43">43</a></td>
<td class="centeralign"></td>
<td>DerivedResources-43</td>
<td>??</td>
<td>How are secondary resources derived?</td>
<td class="centeralign">15-Nov-03</td>
<td class="rightalign">0</td>
</tr>
<tr>
<td class="rightalign"><a href="http://www.w3.org/2001/tag/group/track/issues/45">45</a></td>
<td class="centeralign"></td>
<td>mediaTypeManagement-45</td>
<td>Background</td>
<td>What is the appropriate level of granularity of the media type mechanism?</td>
<td class="centeralign">14-May-04</td>
<td class="rightalign">0</td>
</tr>
<tr>
<td class="rightalign"><a href="http://www.w3.org/2001/tag/group/track/issues/46">46</a></td>
<td class="centeralign"></td>
<td>xml11Names-46</td>
<td>Close</td>
<td>Impact of changes to XML 1.1 on other XML Specifications</td>
<td class="centeralign">19-May-04</td>
<td class="rightalign">0</td>
</tr>
<tr>
<td class="rightalign"><a href="http://www.w3.org/2001/tag/group/track/issues/47">47</a></td>
<td class="centeralign"></td>
<td>endPointRefs-47</td>
<td>Close</td>
<td>WS-Addressing SOAP binding & app protocols</td>
<td class="centeralign">3-Jan-05</td>
<td class="rightalign">0</td>
</tr>
<tr>
<td class="rightalign"><a href="http://www.w3.org/2001/tag/group/track/issues/49">49</a></td>
<td class="centeralign"></td>
<td>schemeProtocols-49</td>
<td>Background</td>
<td>Relationship of URI schemes to protocols and operations</td>
<td class="centeralign">7-Feb-05</td>
<td class="rightalign">0</td>
</tr>
<tr>
<td class="rightalign"><a href="http://www.w3.org/2001/tag/group/track/issues/50">50</a></td>
<td class="centeralign">X</td>
<td>URNsAndRegistries-50</td>
<td>High</td>
<td>URIs, URNs, "location independent" naming systems and
associated registries for namin<span style='display:none'>g on the Web</span></td>
<td class="centeralign">15-Mar-05</td>
<td class="rightalign">2</td>
</tr>
<tr>
<td class="rightalign"><a href="http://www.w3.org/2001/tag/group/track/issues/54">54</a></td>
<td class="centeralign">X</td>
<td>TagSoupIntegration-54</td>
<td>High</td>
<td>Tag soup integration</td>
<td class="centeralign">17-Oct-06</td>
<td class="rightalign">1</td>
</tr>
<tr>
<td class="rightalign"><a href="http://www.w3.org/2001/tag/group/track/issues/55">55</a></td>
<td class="centeralign"></td>
<td>utf7Encoding-55</td>
<td>Background</td>
<td>Security issues with incorrect metadata</td>
<td class="centeralign">14-Dec-06</td>
<td class="rightalign">0</td>
</tr>
<tr>
<td class="rightalign"><a href="http://www.w3.org/2001/tag/group/track/issues/56">56</a></td>
<td class="centeralign"></td>
<td>abbreviatedURIs-56</td>
<td>Background</td>
<td>Abbreviating URIs in Web Languages</td>
<td class="centeralign">30-Mar-07</td>
<td class="rightalign">0</td>
</tr>
<tr>
<td class="rightalign"><a href="http://www.w3.org/2001/tag/group/track/issues/57">57</a></td>
<td class="centeralign">X</td>
<td>HttpRedirections-57</td>
<td>High</td>
<td>The use of HTTP Redirection</td>
<td class="centeralign">22-Aug-07</td>
<td class="rightalign">3</td>
</tr>
<tr>
<td class="rightalign"><a href="http://www.w3.org/2001/tag/group/track/issues/58">58</a></td>
<td class="centeralign"></td>
<td>scalabilityOfURIAccess-58</td>
<td>??</td>
<td>Scalability of URI Access to Resources</td>
<td class="centeralign">22-Aug-07</td>
<td class="rightalign">1</td>
</tr>
<tr>
<td class="rightalign"><a href="http://www.w3.org/2001/tag/group/track/issues/60">60</a></td>
<td class="centeralign">X</td>
<td>webApplicationState-60</td>
<td>High</td>
<td>Web Application State Management</td>
<td class="centeralign">14-Dec-07</td>
<td class="rightalign">3</td>
</tr>
<tr>
<td class="rightalign"><a href="http://www.w3.org/2001/tag/group/track/issues/61">61</a></td>
<td class="centeralign"></td>
<td>uriBasedPackageAccess-61</td>
<td>High or Background?</td>
<td>URI Based Access to Packaged Items</td>
<td class="centeralign">8-Jul-08</td>
<td class="rightalign">0</td>
</tr>
</table>
<address>Noah Mendelsohn for TAG<br />
$Revision: 1.37 $ of $Date: 2009/05/14 21:55:34 $</address>
<p>
<a href="http://validator.w3.org/check?uri=referer"><img
src="http://www.w3.org/Icons/valid-xhtml10"
alt="Valid XHTML 1.0 Transitional" height="31" width="88" /></a>
<a href="http://jigsaw.w3.org/css-validator/check/referer">
<img style="border:0;width:88px;height:31px"
src="http://jigsaw.w3.org/css-validator/images/vcss"
alt="Valid CSS!" />
</a>
</p>
</body>
</html>