09-swxg-minutes.html
39.4 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
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html lang="en"><head><title>Social Web XG Meeting -- 09 Sep 2009</title>
<link type="text/css" rel="STYLESHEET" href="minutes_files/base.css">
<link type="text/css" rel="STYLESHEET" href="minutes_files/public.css">
<link type="text/css" rel="STYLESHEET" href="minutes_files/minutes-style.css">
<meta content="SV_MEETING_TITLE" name="Title">
<meta content="text/html; charset=iso-8859-1" http-equiv="Content-Type"></head><body>
<p><a href="http://www.w3.org/"><img src="minutes_files/w3c_home.png" alt="W3C" border="0" height="48" width="72"></a>
</p>
<h1>Social Web XG Meetng</h1>
<h2>09 Sep 2009</h2>
<p><a href="http://www.w3.org/2005/Incubator/socialweb/weekly-agenda.html">Agenda</a></p>
<p>See also: <a href="http://www.w3.org/2009/09/02-swxg-irc">IRC log</a></p>
<h2><a name="attendees">Attendees</a></h2>
<div class="intro">
<dl>
<dt>Present</dt>
<dd>+95177aaaa, rreck, melvster, tinkster, pchampin, DKA,
+1.314.683.aabb, bblfish, caribou, AlexPassant, hhalpin, Adam, AndreaP,
+34.91.549.aacc, jsalvachua, oshani, MacTed</dd>
<dt>Regrets</dt>
<dd>Mischa, PeterF</dd>
<dt>Chair</dt>
<dd>DKA </dd>
<dt>Scribe</dt>
<dd>Toby</dd>
</dl>
</div>
<h2>Contents</h2>
<ul>
<li><a href="#agenda">Topics</a>
<ol>
<li><a href="#item01">Convene SWXG WG meeting of 2009-09-02T13:00-15:00Z</a></li>
<li><a href="#item02">General Organization and Task Forces</a></li>
<li><a href="#item03">User stories</a></li>
</ol>
</li>
<li><a href="#ActionSummary">Summary of Action Items</a></li>
</ul>
<hr>
<div class="meeting">
<h3 id="item01">Convene SWXG WG meeting of 2009-09-02T13:00-15:00Z</h3>
<p class="phone">
</p><p class="irc">
<<cite>danbri</cite>> hi folks
</p>
<p class="irc">
<<cite>danbri</cite>> i might be irc only today i'm afraid (drupalcon multitasking)
</p>
<p class="irc">
<<cite>rreck</cite>> hhalpin did you send out minutes to approve?
</p>
<p class="irc">
<<cite>DKA</cite>> <a href="http://www.w3.org/2009/07/29-swxg-minutes.html">http://www.w3.org/2009/07/29-swxg-minutes.html</a>
</p>
<p class="phone">
links to agenda, etc should be OK here - <a href="http://www.w3.org/2005/Incubator/socialweb/wiki/Telecons">http://www.w3.org/2005/Incubator/socialweb/wiki/Telecons</a>
</p>
<p class="irc">
<<cite>hhalpin</cite>> Last meeting minutes are linked from agenda
</p>
<p class="irc">
<<cite>hhalpin</cite>> <a href="http://www.w3.org/2009/07/29-swxg-minutes.html">http://www.w3.org/2009/07/29-swxg-minutes.html</a>
</p>
<p class="irc">
<<cite>rreck</cite>> you mean victim
</p>
<p class="phone">
I don't mind if nobody else wants to.
</p>
<p class="irc">
<<cite>rreck</cite>> +1 tinkster
</p>
<p class="irc">
<<cite>DKA</cite>> ScribeNick: tinkster
</p>
<p class="irc">
<<cite>DKA</cite>> Scribe: Toby
</p>
<p class="irc">
<<cite>rreck</cite>> i saw dan perform some incantation
</p>
<p class="phone">
<cite>DKA:</cite> Let's kick off. First item on our agenda is (as usual) to review last week's minutes.
</p>
<p class="irc">
<<cite>bblfish</cite>> hi
</p>
<p class="phone">
<a href="http://www.w3.org/2009/08/26-swxg-minutes.html">http://www.w3.org/2009/08/26-swxg-minutes.html</a>
</p>
<p class="irc">
<<cite>danbri</cite>> didn't we do webfinger last week?
</p>
<p class="irc">
<<cite>rreck</cite>> +1 approve minutes
</p>
<p class="irc">
<<cite>danbri</cite>> ie. <a href="http://www.w3.org/2009/08/26-swxg-minutes.html#item05">http://www.w3.org/2009/08/26-swxg-minutes.html#item05</a>
</p>
<p class="irc">
<<cite>bblfish</cite>> yes, I understood sparql webfinger right after the end of the conf
</p>
<p class="phone">
<cite>scribe:</cite> Any objections to approving last week's minutes?
</p>
<p class="irc">
<<cite>rreck</cite>> +1 meet again
</p>
<h3 id="item02">General Organization and Task Forces</h3>
<p class="phone">
<cite>scribe:</cite> Moving swiftly on: general organisations. Still not completed my action on OSLO/geolocation
</p>
<p class="irc">
<<cite>DKA</cite>> <a href="http://www.w3.org/2002/09/wbs/43434/USECASES/results">http://www.w3.org/2002/09/wbs/43434/USECASES/results</a>
</p>
<p class="phone">
<cite>scribe:</cite> Focus today on discussing use cases and results of poll. Move onto that?
</p>
<p class="phone">
<cite>Harry:</cite> that sounds fine.
</p>
<p class="irc">
<<cite>melvster</cite>> <a href="http://www.w3.org/2002/09/wbs/43434/USECASES/results">http://www.w3.org/2002/09/wbs/43434/USECASES/results</a>
</p>
<h3 id="item03">User stories</h3>
<p class="irc">
<<cite>hhalpin</cite>> <a href="http://www.w3.org/2002/09/wbs/43434/USECASES/results">http://www.w3.org/2002/09/wbs/43434/USECASES/results</a>
</p>
<p class="phone">
<cite>Harry:</cite> Most productive to continue from last meeting, walking through use cases.
</p>
<p class="irc">
<<cite>Adam</cite>> <a href="http://www.w3.org/2002/09/wbs/43434/USECASES/results?view=compact">http://www.w3.org/2002/09/wbs/43434/USECASES/results?view=compact</a>
</p>
<p class="phone">
<cite>Harry:</cite> Most use cases have a champion. Some can clearly be
dropped - bidirectional; drag and drop; etc. Some have almost unanimous
support. Some more mixed.
</p>
<p class="phone">
<cite>DKA:</cite> CRUD is on a much lower level than the others; can't really be argued against.
</p>
<p class="phone">
<cite>Harry:</cite> Last time we got up to "Adding new features to Social Networks" case.
</p>
<p class="irc">
<<cite>hhalpin</cite>> <a href="http://www.w3.org/2002/09/wbs/43434/USECASES/results#xq6">http://www.w3.org/2002/09/wbs/43434/USECASES/results#xq6</a>
</p>
<p class="irc">
<<cite>hhalpin</cite>> Developers should be able
to expose existing data in new and interesting ways. But at the same
time, people should be made aware of how their data is being used, and
updated when this changes
</p>
<p class="phone">
<cite>Harry:</cite> To me this is talking mostly about widgets.
</p>
<p class="irc">
<<cite>hhalpin</cite>> Maybe we should separate those out
</p>
<p class="phone">
<cite>DKA:</cite> There's widgets as in browser-widgets, but also those
that live on the page, and APIs, etc. This encompasses both of those
aspects.
</p>
<p class="irc">
<<cite>hhalpin</cite>> ?
</p>
<p class="phone">
<cite>Harry:</cite> should separate out?
</p>
<p class="irc">
<<cite>Yuk</cite>> ??P36 is me
</p>
<p class="phone">
<cite>DKA:</cite> Not so sure they should be separate. They seem related.
</p>
<p class="irc">
<<cite>hhalpin</cite>> The issue with this usecase is needs a champion
</p>
<p class="irc">
<<cite>rreck</cite>> i think there should be an opt in policy about newly added functionality
</p>
<p class="irc">
<<cite>rreck</cite>> beuler
</p>
<p class="irc">
<<cite>melvster</cite>> I'll champion this one if no one wants to
</p>
<p class="phone">
<cite>hhalpin:</cite> Anyone want to champion it?
</p>
<p class="phone">
<cite>DKA:</cite> yay for melvster championing.
</p>
<p class="irc">
<<cite>hhalpin</cite>> To find the original source of a meme or piece of information.
</p>
<p class="phone">
<cite>hhalpin:</cite> Tracking of sources use case. We want to find the original source of the information.
</p>
<p class="phone">
<cite>tinkster:</cite> am happy to champion this use case.
</p>
<p class="irc">
<<cite>rreck</cite>> i just disagree with christine
</p>
<p class="phone">
<cite>hhalpin:</cite> Multiple identities / anonymous identities - merge?
</p>
<p class="irc">
<<cite>hhalpin</cite>> To provide information without being the attributed source or “whistle blower”.
</p>
<p class="irc">
<<cite>hhalpin</cite>> Anonymous information usecase
</p>
<p class="irc">
<<cite>hhalpin</cite>> Provenance is effectivelzy blocked or unknown, i.e. anonymous, or anonymous identity.
</p>
<p class="phone">
<cite>hhalpin:</cite> this could also be considered to be merged with source tracking / provenance.
</p>
<p class="irc">
<<cite>rreck</cite>> yeah provenance is an anonymous node
</p>
<p class="phone">
<cite>DKA:</cite> curious to understand the argument against.
</p>
<p class="irc">
<<cite>rreck</cite>> i want to share it, just not have it attributed to me
</p>
<p class="phone">
<cite>oshani:</cite> there could be a set of people you are comfortable
with sharing information; other people not so much; so have two
identities - a real one and a pseudononymous one.
</p>
<p class="irc">
<<cite>hhalpin</cite>> anonymous could also be wikileaks-style, i.e. truly anonymous
</p>
<p class="phone">
<cite>DKA:</cite> Not sure this answers the whistleblower use case completely anonymously.
</p>
<p class="irc">
<<cite>hhalpin</cite>> this can be accomplished technically via messages sent out over mixminion for example
</p>
<p class="irc">
<<cite>rreck</cite>> yeah someone on my street put up a sign saying the water wasnt safe. im sure it made him a target
</p>
<p class="phone">
<cite>DKA:</cite> Whistleblower use case more interesting if we look at it from a gov't agency point of view.
</p>
<p class="irc">
<<cite>bblfish</cite>> what is the problem with having identifiers for people with no info linked to that id?
</p>
<p class="irc">
<<cite>bblfish</cite>> then you get id, and anonymity
</p>
<p class="irc">
<<cite>pchampin</cite>> +1 bblfish
</p>
<p class="phone">
<cite>hhalpin:</cite> if rreck wants to champion it, we should keep it around, but note its links to related use cases.
</p>
<p class="irc">
<<cite>jsalvachua</cite>> +1 bblfish
</p>
<p class="irc">
<<cite>hhalpin</cite>> I think if Ronald wants to
champion if Ronald making sure its suitable, especially if we can track
back to merging source...
</p>
<p class="phone">
<cite>oshani:</cite> From a social net point of view, what does this encompass? How does it relate to e.g. Webcams.
</p>
<p class="irc">
<<cite>rreck</cite>> i want to protect my friends from something, but i dont want it tracked to me
</p>
<p class="phone">
<cite>hhalpin:</cite> there exists technical infrastructure that can provide pretty good anonymity.
</p>
<p class="irc">
<<cite>rreck</cite>> i think its null provenance
</p>
<p class="irc">
<<cite>rreck</cite>> ill talk to oshani offline
</p>
<p class="phone">
<cite>hhalpin:</cite> should champions be rewriting use cases, cleaning up, fleshing out?
</p>
<p class="phone">
<cite>DKA:</cite> yes/
</p>
<p class="irc">
<<cite>melvster</cite>> +1
</p>
<a name="action01"></a>
<p class="irc">
<<cite>hhalpin</cite>> <strong>ACTION:</strong> rreck to flesh out anonymous usecase connecting to multiple identies and null provenance [recorded in <a href="http://www.w3.org/2009/09/02-swxg-minutes.html#action01">http://www.w3.org/2009/09/02-swxg-minutes.html#action01</a>]
</p>
<p class="irc">
<<cite>trackbot</cite>> Created ACTION-71 - Flesh
out anonymous usecase connecting to multiple identies and null
provenance [on Ronald Reck - due 2009-09-09].
</p>
<p class="irc">
<<cite>hhalpin</cite>> "Removing Data or Changing Data permission" Use-case
</p>
<p class="phone">
<cite>hhalpin:</cite> next use case is removing data / changing
permissions use case. Most people not in favour of keeping. Perhaps use
case is too abstract?
</p>
<p class="irc">
<<cite>bblfish</cite>> there really is not much text at <a href="http://www.w3.org/2005/Incubator/socialweb/wiki/UserStories#Removing_Data_or_Changing_Data_permission">http://www.w3.org/2005/Incubator/socialweb/wiki/UserStories#Removing_Data_or_Changing_Data_permission</a>
</p>
<p class="phone">
<cite>hhalpin:</cite> relates to the more concrete 10 year and takedown cases. <br>
... Merge these three use cases?
</p>
<p class="irc">
<<cite>hhalpin</cite>> Document Takedowns Propagators Use-case
</p>
<p class="irc">
<<cite>Adam</cite>> are all of them really related to the life cycle management of data?
</p>
<p class="phone">
<cite>DKA:</cite> Seems sensible to me.
</p>
<p class="irc">
<<cite>rreck</cite>> i think all this case could be solved with obligatory metadata stating time to life
</p>
<p class="phone">
<cite>hhalpin:</cite> 10 year use case had a lot of support, no champion. Would oshani like to incorporate this into document takedown?
</p>
<p class="phone">
<cite>oshani:</cite> yes, I can do that.
</p>
<p class="phone">
<cite>hhalpin:</cite> 10 years is just a time-related document takedown.
</p>
<p class="phone">
<cite>bblfish:</cite> if you do everything by reference (rather than by copying) then you only need to take down the original.
</p>
<a name="action02"></a>
<p class="irc">
<<cite>hhalpin</cite>> <strong>ACTION:</strong>
Oshani to merge document takedown with time-related takedown "forget
this in ten years" and more general concept of data removal. [recorded
in <a href="http://www.w3.org/2009/09/02-swxg-minutes.html#action02">http://www.w3.org/2009/09/02-swxg-minutes.html#action02</a>]
</p>
<p class="irc">
<<cite>trackbot</cite>> Created ACTION-72 - Merge
document takedown with time-related takedown "forget this in ten years"
and more general concept of data removal. [on Oshani Seneviratne - due
2009-09-09].
</p>
<p class="phone">
<cite>DKA:</cite> example is a photo that I've taken, which includes
bblfish's face, and bblfish annotates it. Someone else in the photo
asked DKA to take down the photo. <br>
... DKA should be able to remove photo. What happens to annotation? What is bblfish's right to the image vs DKA's right?
</p>
<p class="irc">
<<cite>rreck</cite>> DKA's example happened to me
</p>
<p class="phone">
<cite>bblfish:</cite> it's complicated - that's true.
</p>
<p class="irc">
<<cite>hhalpin</cite>> "Last Will" usecase
</p>
<p class="phone">
<cite>hhalpin:</cite> last will and testament use case.
</p>
<p class="irc">
<<cite>rreck</cite>> time to life for information
</p>
<p class="irc">
<<cite>rreck</cite>> obligatory metadata
</p>
<p class="phone">
<cite>hhalpin:</cite> very popular, but lacking a champion. <br>
... perhaps should be merged with takedowns? but it's a very special case.
</p>
<p class="irc">
<<cite>rreck</cite>> i will champion that but solve it with obligatory metadata
</p>
<p class="irc">
<<cite>MacTed</cite>> everybody's gonna... :-)
</p>
<p class="phone">
<cite>DKA:</cite> this is something we'll all end up facing!
</p>
<p class="irc">
<<cite>rreck</cite>> +q
</p>
<p class="phone">
<cite>DKA:</cite> worth keeping on its own. volunteer champion?
</p>
<p class="irc">
<<cite>hhalpin</cite>> Ron?
</p>
<p class="phone">
<cite>MacTed:</cite> this could be solved by including a time-to-live (TTL) for every piece of content.
</p>
<p class="irc">
<<cite>hhalpin</cite>> is an option on time-to-life?
</p>
<p class="irc">
<<cite>bblfish</cite>> yes, but it is weird. I think that removing information is problematic.
</p>
<p class="phone">
<cite>everyone:</cite> "if you know the exact time of your death".
</p>
<p class="phone">
<cite>MacTed:</cite> copyright is based on death date.
</p>
<p class="irc">
<<cite>Yuk</cite>> it also happens that one's parents/friends want to see his/her history
</p>
<p class="phone">
<cite>tinkster:</cite> it's based on the author's death date, but calculated *after* death. (currently)
</p>
<p class="phone">
Ah, so MacTed above is rreck. (Note to editor!)
</p>
<p class="phone">
(Or maybe not?)
</p>
<p class="irc">
<<cite>hhalpin</cite>> Hmmm...it seems like what we need to do next is move to group permissions
</p>
<p class="irc">
<<cite>Adam</cite>> is some of that regarding permissions of access versus time of life?
</p>
<p class="phone">
<cite>MacTed:</cite> TTL could be fragmented by different groups.
</p>
<p class="irc">
<<cite>rreck</cite>> that is an awesome point, its much more complicated than i had appreciated
</p>
<p class="irc">
<<cite>jsalvachua</cite>> unix like permissions?
</p>
<p class="phone">
<cite>DKA:</cite> Death use case needs a champion, even if nobody wants to be the "champion of death". <br>
... I'd be happy to take it on myself.
</p>
<p class="irc">
<<cite>rreck</cite>> one of my FB passed, and i wondered what will happen to his page
</p>
<a name="action03"></a>
<p class="irc">
<<cite>hhalpin</cite>> <strong>ACTION:</strong>
DKA to take on "Last Will and Testament Usecase", referencing it as
both a legal issue and with regards document takedown [recorded in <a href="http://www.w3.org/2009/09/02-swxg-minutes.html#action03">http://www.w3.org/2009/09/02-swxg-minutes.html#action03</a>]
</p>
<p class="irc">
<<cite>trackbot</cite>> Created ACTION-73 - Take
on "Last Will and Testament Usecase", referencing it as both a legal
issue and with regards document takedown [on Daniel Appelquist - due
2009-09-09].
</p>
<p class="phone">
<cite>DKA:</cite> What happens right now on social networks when people
die? What happens if someone is believed dead, their account deleted,
and it turns out they're alive?
</p>
<p class="irc">
<<cite>danbri</cite>> (de-lurking)
</p>
<p class="irc">
<<cite>MacTed</cite>> mostly someone finds their username/password, and assumes ownership of the account ...
</p>
<p class="phone">
<cite>tinkster:</cite> there exist facebook memorial pages (I'm told)
</p>
<p class="irc">
<<cite>danbri</cite>> i'd like to spend some time chasing up this issue, seems a useful kind of thing for w3c to investigate
</p>
<p class="irc">
<<cite>MacTed</cite>> if that doesn't happen, most accounts I've known have just sat there untouched (sometimes years) like any other inactive
</p>
<p class="phone">
<cite>hhalpin:</cite> multiple identities use case. champion bblfish?
</p>
<p class="irc">
<<cite>hhalpin</cite>> "Multiple Identities" Use-case
</p>
<p class="irc">
<<cite>Yuk</cite>> Social network for the dead Respectance crosses the ocean <a href="http://thenextweb.com/2008/10/03/social-network-for-the-death-respectance-crosses-the-ocean/">http://thenextweb.com/2008/10/03/social-network-for-the-death-respectance-crosses-the-ocean/</a>
</p>
<p class="irc">
<<cite>hhalpin</cite>> Sort of built from
multiple identities over multiple networks to metadata about the
management of data over multiple networks to access control.
</p>
<p class="phone">
<cite>hhalpin:</cite> Maybe this could be the starting point for other use cases.
</p>
<p class="irc">
<<cite>MacTed</cite>> demerits for me, I found no window to review/restructure :-(
</p>
<p class="phone">
<cite>hhalpin:</cite> e.g. identities on mutiple networks.
</p>
<p class="phone">
<cite>bblfish:</cite> Multiple identities seems like a good idea - easy to do.
</p>
<p class="irc">
<<cite>rreck</cite>> acceptable use is a problem, i dont think FB let's you do it
</p>
<p class="phone">
<cite>hhalpin:</cite> Could you maybe merge this with no-password use case?
</p>
<p class="irc">
<<cite>hhalpin</cite>> "Using a web service should not involve password or account name creation" Use-case
</p>
<p class="irc">
<<cite>hhalpin</cite>> but these seem kinda of technically separate
</p>
<p class="irc">
<<cite>hhalpin</cite>> so keep them separate?
</p>
<p class="irc">
<<cite>rreck</cite>> tons of cross talk
</p>
<p class="phone">
<cite>bblfish:</cite> the user not needing to have a password doesn't
mean they can't identify themselves. It's a question of ease-of-use. A
bit technical.
</p>
<p class="irc">
<<cite>Adam</cite>> no
</p>
<p class="irc">
<<cite>Adam</cite>> think its henrys line
</p>
<p class="phone">
<cite>bblfish:</cite> repeated setting up of accounts is unnecessary and tedious.
</p>
<p class="irc">
<<cite>hhalpin</cite>> are we losing bblfish?
</p>
<p class="phone">
<cite>bblfish:</cite> data portability problem?
</p>
<p class="phone">
<cite>hhalpin:</cite> so bblfish wants to keep multiple identities and passwordless use cases separate?
</p>
<p class="phone">
<cite>bblfish:</cite> yes. latter is about ease of use.
</p>
<p class="irc">
<<cite>MacTed</cite>> sounds like OpenID?
</p>
<p class="irc">
<<cite>jsalvachua</cite>> sorry have to leave, see you.
</p>
<p class="irc">
<<cite>rreck</cite>> tough to hear agreed
</p>
<p class="irc">
<<cite>bblfish</cite>> another use case that this
makes me think of is: Identifiers on SN should not be resold to other
people, as this would mess up the web of relations on the web. Eg:
people saying they are firends of <a href="http://facebook.org/joe#me">http://facebook.org/joe#me</a> and then this being reassinged to Joe BadGuy
</p>
<p class="phone">
<cite>DKA:</cite> problem with zakim <br>
... let's move on; for now Henry as champion for multiple identities.
</p>
<p class="irc">
<<cite>rreck</cite>> yes better
</p>
<p class="irc">
<<cite>bblfish</cite>> yes, the point is that the DataPortability group have mentioned that loggin in to every web site is a big problem
</p>
<p class="irc">
<<cite>bblfish</cite>> This is solved by OpenId, Passport, foaf+ssl
</p>
<p class="phone">
<cite>hhalpin:</cite> next use cases are all about group access control.
</p>
<p class="irc">
<<cite>bblfish</cite>> the data portability video: <a href="http://blogs.sun.com/bblfish/entry/data_portability_the_video">http://blogs.sun.com/bblfish/entry/data_portability_the_video</a>
</p>
<p class="phone">
<cite>hhalpin:</cite> first is more abstract; second is the concrete example of family-access for a resource.
</p>
<p class="irc">
<<cite>rreck</cite>> agreed kinship is cultural
</p>
<p class="phone">
<cite>hhalpin:</cite> Most comments suggest merging these.
</p>
<p class="irc">
<<cite>hhalpin</cite>> Distributed Group Access Control" Use-case
</p>
<p class="irc">
<<cite>MacTed</cite>> hm.
</p>
<p class="phone">
<cite>DKA:</cite> who would agree on what a family is? link identity to genome?
</p>
<p class="phone">
<cite>hhalpin:</cite> who will champion this/these use cases?
</p>
<a name="action04"></a>
<p class="irc">
<<cite>hhalpin</cite>> <strong>ACTION:</strong> bblfish to merge Family and Group access usecases [recorded in <a href="http://www.w3.org/2009/09/02-swxg-minutes.html#action04">http://www.w3.org/2009/09/02-swxg-minutes.html#action04</a>]
</p>
<p class="irc">
<<cite>trackbot</cite>> Created ACTION-74 - Merge Family and Group access usecases [on Henry Story - due 2009-09-09].
</p>
<p class="phone">
<cite>bblfish:</cite> yes, I'm championing this. Don't need to link in
genome (scribe notes that FOAF does have an appropriate property) -
just need to link to your family.
</p>
<p class="irc">
<<cite>hhalpin</cite>> Intransitivity of Policies Applied to Social Network Data" Use-cas
</p>
<p class="irc">
<<cite>rreck</cite>> but family markedness is cultural
</p>
<p class="phone">
<cite>hhalpin:</cite> intransitivity use case.
</p>
<p class="irc">
<<cite>rreck</cite>> some cultures mark siblings but not gender
</p>
<p class="irc">
<<cite>danbri</cite>> (tinkster - new foaf properties can be had for as little as 5 euros... send me mail :)
</p>
<p class="irc">
<<cite>hhalpin</cite>> Current social networking
platforms implement very rudimentary data usage policies. These mostly
focuses on the immediate individuals concerned and do not have much
consideration about the data transfer beyond them. Policy conflicts are
also not properly handled. If the policies applied to social networking
data are made to be transitive, we can make sure tha
</p>
<p class="phone">
<cite>hhalpin:</cite> if your data moves from one SN to another, your privacy policy can accompany it.
</p>
<p class="phone">
<cite>oshani:</cite> facebook quizzes - I'm not just giving out my own data, but my friends' data. This is a problem.
</p>
<p class="irc">
<<cite>rreck</cite>> yeah that is a problem
</p>
<p class="irc">
<<cite>danbri</cite>> (ah, i read "doesn't" :)
</p>
<p class="irc">
<<cite>danbri</cite>> (yeah, dnachecksum started as a joke, but i think a few folk would like a real one!)
</p>
<p class="irc">
<<cite>Yuk</cite>> can the friends choose not to have their data being taken from one website to another?
</p>
<p class="phone">
<cite>DKA:</cite> oshani, could you find a link to quizzes example?
</p>
<a name="action05"></a>
<p class="irc">
<<cite>hhalpin</cite>> <strong>ACTION:</strong> oshani to flesh out "Intransitivity of Policies Applied to Social Network Data" [recorded in <a href="http://www.w3.org/2009/09/02-swxg-minutes.html#action05">http://www.w3.org/2009/09/02-swxg-minutes.html#action05</a>]
</p>
<p class="irc">
<<cite>trackbot</cite>> Created ACTION-75 - Flesh
out "Intransitivity of Policies Applied to Social Network Data" [on
Oshani Seneviratne - due 2009-09-09].
</p>
<p class="phone">
<cite>hhalpin:</cite> bidirectional use case - everyone agreed to drop it. too vague?
</p>
<a name="action06"></a>
<p class="irc">
<<cite>hhalpin</cite>> <strong>ACTION:</strong> hhalpin to drop bidirectional use case [recorded in <a href="http://www.w3.org/2009/09/02-swxg-minutes.html#action06">http://www.w3.org/2009/09/02-swxg-minutes.html#action06</a>]
</p>
<p class="irc">
<<cite>trackbot</cite>> Created ACTION-76 - Drop bidirectional use case [on Harry Halpin - due 2009-09-09].
</p>
<p class="irc">
<<cite>rreck</cite>> peer pressure
</p>
<p class="phone">
<cite>hhalpin:</cite> virtual private organisation use case - create a temporary internal (or cross-organisation) network.
</p>
<p class="irc">
<<cite>hhalpin</cite>> "Virtual Private Organization" Use-case
</p>
<p class="irc">
<<cite>hhalpin</cite>> No champion
</p>
<p class="phone">
<cite>hhalpin:</cite> make sure it doesn't leak data.
</p>
<p class="irc">
<<cite>hhalpin</cite>> I thought it came from joaquin...
</p>
<p class="phone">
<cite>DKA:</cite> Isn't this the corporate SN use case?
</p>
<p class="phone">
<cite>hhalpin:</cite> related to that heavily.
</p>
<p class="irc">
<<cite>bblfish</cite>> I suppose this is also very similar to "Distributed Group Access Control"
</p>
<p class="irc">
<<cite>hhalpin</cite>> it is very similar to distributed group access contol.
</p>
<p class="phone">
<cite>Adam:</cite> I can champion this use case. Can look at this two
ways - internally, people could create their own groups, which they
could make private (even within the company) or not. <br>
... Or is this more complicated.
</p>
<p class="phone">
<cite>DKA:</cite> It's pretty bare-bones right now. It seems to point more to organically-growing networks.
</p>
<p class="irc">
<<cite>pchampin</cite>> sorry, I have to leave
</p>
<p class="irc">
<<cite>rreck</cite>> groove does what you are describing
</p>
<p class="irc">
<<cite>hhalpin</cite>> take care pchampin!
</p>
<p class="phone">
<cite>Adam:</cite> if you were to create one of these private virtual
organisations, people would need to agree to its terms. Right now, our
IT dept can create private organisations like this, and use the group
to post some specific public content too.
</p>
<p class="irc">
<<cite>hhalpin</cite>> maybe add links to Distributed Access control?
</p>
<p class="phone">
<cite>DKA:</cite> Can you add this as a sub-usecase?
</p>
<p class="phone">
<cite>tinkster:</cite> if what Adam describes could also take in people and departments at other organisations too.
</p>
<p class="phone">
<cite>bblfish:</cite> related to distributed access control, which would be an enabling technology for it.
</p>
<p class="phone">
<cite>DKA:</cite> we're at the end of our slot.
</p>
<p class="irc">
<<cite>rreck</cite>> we did pretty well getting through them
</p>
<p class="irc">
<<cite>rreck</cite>> bye DKA
</p>
<p class="phone">
<cite>hhalpin:</cite> three more use cases to go through. Should we go through them now?
</p>
<p class="irc">
<<cite>rreck</cite>> so keep geo is clear
</p>
<p class="irc">
<<cite>bblfish</cite>> +1 for talking about these now
</p>
<p class="phone">
+1
</p>
<p class="irc">
<<cite>oshani</cite>> +1
</p>
<p class="irc">
<<cite>melvster</cite>> +1
</p>
<a name="action07"></a>
<p class="irc">
<<cite>hhalpin</cite>> <strong>ACTION:</strong>
Adam to work on fleshing on "Virtual Private Organisation Use Case"
reference distributed data access control policy [recorded in <a href="http://www.w3.org/2009/09/02-swxg-minutes.html#action07">http://www.w3.org/2009/09/02-swxg-minutes.html#action07</a>]
</p>
<p class="irc">
<<cite>trackbot</cite>> Created ACTION-77 - Work
on fleshing on "Virtual Private Organisation Use Case" reference
distributed data access control policy [on Adam Boyet - due
2009-09-09].
</p>
<p class="irc">
<<cite>bblfish</cite>> did we doo the Too Many Channels?
</p>
<p class="phone">
<cite>hhalpin:</cite> geo use case. Inferences on location-based
contextual data. We should have privacy controls on this, but should be
able to share it if we want. Relates to portability and access control.
</p>
<p class="phone">
<cite>oshani:</cite> happy to champion this. can't see anything to merge with.
</p>
<p class="irc">
<<cite>hhalpin</cite>> "Too many channels" can be move across different channels
</p>
<a name="action08"></a>
<p class="irc">
<<cite>hhalpin</cite>> <strong>ACTION:</strong> hhalpin to drop "too many channels" [recorded in <a href="http://www.w3.org/2009/09/02-swxg-minutes.html#action08">http://www.w3.org/2009/09/02-swxg-minutes.html#action08</a>]
</p>
<p class="phone">
<cite>hhalpin:</cite> "too many channels" use case - allow data to move
across between different SNs. Pretty much covered by other portability
and access use cases. We should drop.
</p>
<p class="irc">
<<cite>trackbot</cite>> Created ACTION-78 - Drop "too many channels" [on Harry Halpin - due 2009-09-09].
</p>
<p class="phone">
<cite>hhalpin:</cite> Data protection use case. This is not easy.
</p>
<p class="irc">
<<cite>oshani</cite>> hhalpin, nope, I am not a champion for that
</p>
<p class="phone">
<cite>bblfish:</cite> the question is very interesting, but I don't know what the answer is.
</p>
<p class="irc">
<<cite>hhalpin</cite>> Alice is not a member of a
given walled-garden social network and Bob tags her in an image from an
event they were both at. Given that Alice finds out about this image,
through word of mouth or by whatever means, should she be able to ask
for her depiction to be removed? If she somehow manages to confirm that
indeed it was a picture of her, should she be abl
</p>
<p class="phone">
<cite>hhalpin:</cite> similar to document takedown perhaps, but also need to look at legal requirements.
</p>
<p class="irc">
<<cite>oshani</cite>> I think I am
</p>
<p class="irc">
<<cite>Adam</cite>> data protection to me infers controlled access
</p>
<p class="irc">
<<cite>hhalpin</cite>> controlled access
</p>
<p class="irc">
<<cite>hhalpin</cite>> Could be kept separate there...
</p>
<p class="irc">
<<cite>Adam</cite>> is this use case more about Alice's right to have the image removed?
</p>
<p class="irc">
<<cite>bblfish</cite>> Could be an intro to a number of use cases
</p>
<p class="phone">
<cite>oshani:</cite> this is different fron document take down in that it's initiated by an outsider.
</p>
<p class="phone">
<cite>hhalpin:</cite> perhaps it needs a bit of rephrasing.
</p>
<p class="phone">
<cite>bblfish:</cite> I'll think about that.
</p>
<a name="action09"></a>
<p class="irc">
<<cite>hhalpin</cite>> <strong>ACTION:</strong> bblfish to relabel data protection use case to be about controlled access and takedown to data "about" you [recorded in <a href="http://www.w3.org/2009/09/02-swxg-minutes.html#action09">http://www.w3.org/2009/09/02-swxg-minutes.html#action09</a>]
</p>
<p class="irc">
<<cite>trackbot</cite>> Created ACTION-79 -
Relabel data protection use case to be about controlled access and
takedown to data "about" you [on Henry Story - due 2009-09-09].
</p>
<p class="irc">
<<cite>rreck</cite>> +1 yeah
</p>
<p class="irc">
<<cite>bblfish</cite>> we have a few extra use cases that were added
</p>
<p class="phone">
<cite>hhalpin:</cite> I think we've managed to drop three use cases and merge about four.
</p>
<p class="irc">
<<cite>rreck</cite>> what about the shill one? can we keep it
</p>
<p class="phone">
<cite>hhalpin:</cite> Next week after a bit more boiling down, we can maybe freeze the use cases and start drafting a full document. <br>
... Document structure maybe: identity, metadata, access?
</p>
<p class="irc">
<<cite>hhalpin</cite>> do you know who added that one?
</p>
<p class="phone">
I think I might have added one - commercial incentives for social networks to open their data.
</p>
<p class="irc">
<<cite>bblfish</cite>> <a href="http://www.w3.org/2005/Incubator/socialweb/wiki/UserStories#Social_Web_for_Business_Intelligence">http://www.w3.org/2005/Incubator/socialweb/wiki/UserStories#Social_Web_for_Business_Intelligence</a>
</p>
<p class="irc">
<<cite>Adam</cite>> yeah, toby did and there was one other as well
</p>
<p class="irc">
<<cite>bblfish</cite>> this one perhaps?
</p>
<p class="phone">
There was bblfish's plastic toy one too.
</p>
<p class="irc">
<<cite>oshani</cite>> <a href="http://www.w3.org/2005/Incubator/socialweb/wiki/UserStories#Current_Location_as_a_Direction">http://www.w3.org/2005/Incubator/socialweb/wiki/UserStories#Current_Location_as_a_Direction</a>
</p>
<p class="irc">
<<cite>rreck</cite>> hhalpin: i added shill
</p>
<p class="irc">
<<cite>Adam</cite>> i'm happy to champion the Social Web for Business Intellegence
</p>
<p class="phone">
Not realy.
</p>
<p class="irc">
<<cite>bblfish</cite>> was this one new too <a href="http://www.w3.org/2005/Incubator/socialweb/wiki/UserStories#Shills_Posting_False_Information_to_Dilute_the_Truth">http://www.w3.org/2005/Incubator/socialweb/wiki/UserStories#Shills_Posting_False_Information_to_Dilute_the_Truth</a>
</p>
<p class="irc">
<<cite>hhalpin</cite>> OK.
</p>
<p class="irc">
<<cite>hhalpin</cite>> oshani and henry
</p>
<p class="phone">
<cite>tinkster:</cite> I don't have any special interest in the use
case I've recently posted - just wrote it up as I'd been actioned.
Someone else can champion.
</p>
<p class="irc">
<<cite>bblfish</cite>> yes, I can do that.
</p>
<p class="phone">
<cite>hhalpin:</cite> bblfish and oshani to edit full use case document?
</p>
<p class="phone">
<cite>oshani:</cite> happy to help.
</p>
<p class="phone">
<cite>bblfish:</cite> not edited a w3c doc before.
</p>
<p class="irc">
<<cite>bblfish</cite>> don't think I did edit a doc
</p>
<p class="irc">
<<cite>bblfish</cite>> apart from wiki
</p>
<p class="phone">
<cite>hhalpin:</cite> I'll show you the process next week. Draft it on Wiki; cut out HTML and put it on CVS; then edit it from there.
</p>
<p class="irc">
<<cite>bblfish</cite>> ok
</p>
<a name="action10"></a>
<p class="irc">
<<cite>hhalpin</cite>> <strong>ACTION:</strong> Explain to henry and oshani doc editing process for usecases [recorded in <a href="http://www.w3.org/2009/09/02-swxg-minutes.html#action10">http://www.w3.org/2009/09/02-swxg-minutes.html#action10</a>]
</p>
<p class="irc">
<<cite>trackbot</cite>> Sorry, couldn't find user - Explain
</p>
<a name="action11"></a>
<p class="irc">
<<cite>hhalpin</cite>> <strong>ACTION:</strong> hhalpin explain to henry and oshani doc editing process for usecases [recorded in <a href="http://www.w3.org/2009/09/02-swxg-minutes.html#action11">http://www.w3.org/2009/09/02-swxg-minutes.html#action11</a>]
</p>
<p class="irc">
<<cite>trackbot</cite>> Created ACTION-80 - Explain to henry and oshani doc editing process for usecases [on Harry Halpin - due 2009-09-09].
</p>
<p class="phone">
<cite>hhalpin:</cite> that's all folks.
</p>
<p class="irc">
<<cite>hhalpin</cite>> Meeting adjourned
</p>
<p class="irc">
<<cite>rreck</cite>> bubye
</p>
<p class="phone">
<cite>hhalpin:</cite> sorry for overrunning.
</p>
<p class="irc">
<<cite>bblfish</cite>> ok by
</p>
<p class="irc">
<<cite>rreck</cite>> i wont be here next week.
</p>
<p class="irc">
<<cite>hhalpin</cite>> trackbot, end meeting
</p>
<p class="irc">
<<cite>melvster</cite>> bye
</p>
</div>
<h2><a name="ActionSummary">Summary of Action Items</a></h2>
<!-- Action Items -->
<strong>[NEW]</strong> <strong>ACTION:</strong> Adam to work on
fleshing on "Virtual Private Organisation Use Case" reference
distributed data access control policy [recorded in <a href="http://www.w3.org/2009/09/02-swxg-minutes.html#action07">http://www.w3.org/2009/09/02-swxg-minutes.html#action07</a>] <br>
<strong>[NEW]</strong> <strong>ACTION:</strong> bblfish to merge Family and Group access usecases [recorded in <a href="http://www.w3.org/2009/09/02-swxg-minutes.html#action04">http://www.w3.org/2009/09/02-swxg-minutes.html#action04</a>] <br>
<strong>[NEW]</strong> <strong>ACTION:</strong> bblfish to relabel data protection use case to be about controlled access and takedown to data "about" you [recorded in <a href="http://www.w3.org/2009/09/02-swxg-minutes.html#action09">http://www.w3.org/2009/09/02-swxg-minutes.html#action09</a>] <br>
<strong>[NEW]</strong> <strong>ACTION:</strong> DKA to take on "Last
Will and Testament Usecase", referencing it as both a legal issue and
with regards document takedown [recorded in <a href="http://www.w3.org/2009/09/02-swxg-minutes.html#action03">http://www.w3.org/2009/09/02-swxg-minutes.html#action03</a>] <br>
<strong>[NEW]</strong> <strong>ACTION:</strong> Explain to henry and oshani doc editing process for usecases [recorded in <a href="http://www.w3.org/2009/09/02-swxg-minutes.html#action10">http://www.w3.org/2009/09/02-swxg-minutes.html#action10</a>] <br>
<strong>[NEW]</strong> <strong>ACTION:</strong> hhalpin explain to henry and oshani doc editing process for usecases [recorded in <a href="http://www.w3.org/2009/09/02-swxg-minutes.html#action11">http://www.w3.org/2009/09/02-swxg-minutes.html#action11</a>] <br>
<strong>[NEW]</strong> <strong>ACTION:</strong> hhalpin to drop "too many channels" [recorded in <a href="http://www.w3.org/2009/09/02-swxg-minutes.html#action08">http://www.w3.org/2009/09/02-swxg-minutes.html#action08</a>] <br>
<strong>[NEW]</strong> <strong>ACTION:</strong> hhalpin to drop bidirectional use case [recorded in <a href="http://www.w3.org/2009/09/02-swxg-minutes.html#action06">http://www.w3.org/2009/09/02-swxg-minutes.html#action06</a>] <br>
<strong>[NEW]</strong> <strong>ACTION:</strong> oshani to flesh out "Intransitivity of Policies Applied to Social Network Data" [recorded in <a href="http://www.w3.org/2009/09/02-swxg-minutes.html#action05">http://www.w3.org/2009/09/02-swxg-minutes.html#action05</a>] <br>
<strong>[NEW]</strong> <strong>ACTION:</strong> Oshani to merge
document takedown with time-related takedown "forget this in ten years"
and more general concept of data removal. [recorded in <a href="http://www.w3.org/2009/09/02-swxg-minutes.html#action02">http://www.w3.org/2009/09/02-swxg-minutes.html#action02</a>] <br>
<strong>[NEW]</strong> <strong>ACTION:</strong> rreck to flesh out anonymous usecase connecting to multiple identies and null provenance [recorded in <a href="http://www.w3.org/2009/09/02-swxg-minutes.html#action01">http://www.w3.org/2009/09/02-swxg-minutes.html#action01</a>] <br>
<br>
[End of minutes] <br>
<hr>
<address>
Minutes formatted by David Booth's
<a href="http://dev.w3.org/cvsweb/%7Echeckout%7E/2002/scribe/scribedoc.htm">scribe.perl</a> version 1.133 (<a href="http://dev.w3.org/cvsweb/2002/scribe/">CVS log</a>)<br>
$Date: 2009/09/18 19:25:33 $
</address>
</body></html>