index.html
107 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
<!DOCTYPE html>
<html dir="ltr" lang="en-US" class="no-js" xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta charset="UTF-8" />
<meta name="robots" content="index, nofollow" />
<meta name="viewport" content="width=device-width; initial-scale=1.0" />
<link rel="shortcut icon" href="/community/src/img/favicon.ico" type="image/x-icon" />
<title>Community and Business Groups | A W3C Community Group</title>
<link rel="profile" href="http://gmpg.org/xfn/11" />
<link rel="stylesheet" media="all" href="http://www.w3.org/community/wp-content/themes/ttfv/style.css" />
<link rel="pingback" href="http://www.w3.org/community/xmlrpc.php" />
<link rel="alternate" type="application/rss+xml" title="Community and Business Groups » Feed" href="http://www.w3.org/community/feed/" />
<link rel="alternate" type="application/rss+xml" title="Community and Business Groups » Comments Feed" href="http://www.w3.org/community/comments/feed/" />
<link rel='stylesheet' id='wp-polls-css' href='http://www.w3.org/community/wp-content/plugins/wp-polls/polls-css.css?ver=2.50' type='text/css' media='all' />
<script type='text/javascript' src='http://www.w3.org/community/wp-content/themes/ttfv/js/modernizr-1.7.min.js?ver=3.3.1'></script>
<script type='text/javascript' src='http://www.w3.org/community/wp-includes/js/jquery/jquery.js?ver=1.7.1'></script>
<script type='text/javascript' src='http://www.w3.org/community/wp-content/themes/ttfv/js/jquery.tinysort.min.js?ver=1.1.1'></script>
<script type='text/javascript' src='http://www.w3.org/community/wp-content/plugins/wordpress-faq-manager/inc/js/faq-collapse.js'></script>
<link rel="EditURI" type="application/rsd+xml" title="RSD" href="http://www.w3.org/community/xmlrpc.php?rsd" />
<link rel="wlwmanifest" type="application/wlwmanifest+xml" href="http://www.w3.org/community/wp-includes/wlwmanifest.xml" />
<meta name="generator" content="WordPress 3.3.1" />
<link rel="stylesheet" href="http://www.w3.org/community/wp-content/plugins/wp-hashtag/css/wp_hashtag.css" type="text/css" media="screen" />
<style type="text/css">
.wp-polls .pollbar {
margin: 1px;
font-size: 6px;
line-height: 8px;
height: 8px;
background-image: url('http://www.w3.org/community/wp-content/plugins/wp-polls/images/default/pollbg.gif');
border: 1px solid #c8c8c8;
}
</style>
<meta id="syntaxhighlighteranchor" name="syntaxhighlighter-version" content="3.1.3" />
</head>
<body class="home blog clearfix">
<!--[if lte IE 8 ]>
<noscript><strong>JavaScript is required for this website to be displayed correctly. Please enable JavaScript before continuing...</strong></noscript>
<![endif]-->
<header class="community_group_header">
<a class="logo w3c_logo" tabindex="2" accesskey="1" href="http://www.w3.org" title="W3C">
<img src="http://www.w3.org/community/wp-content/themes/ttfv/img/logo.png" alt="W3C Logo"/>
</a>
<h1 id="site-title" class="page_title">
<a href="/community/" class="logo community_logo">
<img src="http://www.w3.org/community/wp-content/themes/ttfv/img/community-group-logo.png" alt="Community Group Logo" />
<span>W3C Community and Business Groups</span>
</a>
</h1>
<!-- Uncomment if needed -->
<!--<h2 id="site-description">A W3C Community Group</h2>-->
<div id="search-form-container">
<form role="search" method="get" id="search-form" action="http://www.w3.org/community/">
<div>
<label class="screen-reader-text" for="s">Search for:</label>
<input placeholder="Search blogs" type="text" value="" name="s" id="s" class="search-box" />
<button type="submit" id="search-submit">
<img class="submit" src="http://www.w3.org/community/wp-content/themes/ttfv/img/search-icon.png" alt="search icon" width="17" height="17" />
</button>
</div>
</form>
</div>
<ul class="secondary_navigation secondary_navigation_links">
<li>
<a class="skip_link_border" href="http://www.w3.org/community/wp-login.php?redirect_to=http://www.w3.org/community/">Log in</a>
<a class="skip_link_border" href="http://www.w3.org/community/account/request" title="Get an Account">Get an Account</a>
</li>
<li><a class="skip_link_border" href="http://www.w3.org/Systems/db/userInfo">My Account</a></li>
<li><a class="skip_link" tabindex="1" accesskey="2" title="Skip to content (e.g., when browsing via audio)" href="#content">Skip</a></li>
</ul>
<nav id="access" role="navigation" class="top_navigation">
<ul id="menu-top-menu" class="menu"><li id="menu-item-231" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-231"><a href="http://www.w3.org/community/groups/">Current Groups</a></li>
<li id="menu-item-67" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-67"><a href="http://www.w3.org/community/reports/">Reports</a></li>
<li id="menu-item-59" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-59"><a title="About" href="http://www.w3.org/community/about/">About</a></li>
</ul> </nav><!-- #access -->
</header><!-- #header -->
<div id="main">
<div id="secondary" class="leftCol" role="complementary">
<div id="text-5" class="widget-container widget_text"> <div class="textwidget"><ul class="social_menu">
<li><a title="Find tweets tagged #w3ccommunity" href="http://search.twitter.com/search?q=%23w3ccommunity" class="twitter_icon social_links">Twitter</a></li>
<li><a href="http://www.facebook.com/thew3c" class="facebook_icon social_links" title="Facebook">Facebook</a></li>
<li><a href="http://www.w3.org/community?feed=rss" class="rss_icon social_links" title="RSS">RSS</a></li>
</ul></div>
</div><div id="text-6" class="widget-container widget_text"> <div class="textwidget"><ul class="social_menu">
<li><a title="Contact W3C Staff on a public list about Community and Business Groups" href="mailto:site-comments@w3.org" class="mail_icon">Question? Bug?</a></li>
</ul></div>
</div> </div><!-- #secondary .widget-area -->
<div id="primary" class="mainCol" role="complementary">
<div class="line">
<div class="unit size2on3">
<div id="content" role="main">
<section id="footer-widget-area" role="complementary">
<aside id="first" class="widget-area">
<div id="text-7" class="widget-container widget_text"> <div class="textwidget"><div class="intro">
<p class="lede">Interested in building community around a Web technology? W3C has created Community Groups and Business Groups so that developers, designers, and anyone passionate about the Web has a place to have discussions and publish documents.</p>
<p>A <strong><a href="about/#cg">W3C Community Group</a></strong> is an open forum, without fees, where Web developers and other stakeholders develop specifications, hold discussions, develop test suites, and connect with W3C's international community of Web experts.
</p>
<p>A <strong><a href="about/#bg">W3C Business Group</a></strong> gives innovators that want to have an impact on the development of the Web in the near-term a vendor-neutral forum for collaborating with like-minded stakeholders, including W3C Members and non-Members.</p>
<p class="tMarginLg">Learn more <a href="about">about Community and Business Groups</a>, the <a href="http://www.w3.org/community/about/agreements/">lightweight process</a> that governs them, and consult the <a href="/community/about/faq/">Frequently Asked Questions (FAQ)</a>. </p>
</div></div>
</div> <div class="line">
<section class="unit size1on2 tMargin">
<header>
<h3 class="header_article_group column"> <a href="/community/groups/" title="Current Groups" class="icon_headers header_icon_groups" >Current Groups</a> </h3>
</header>
<article class="news_article">
<header>
<h4 class="header_article"> <a href="/community/fedsocweb">Federated Social Web Community Group</a> </h4>
<p class="article_date">Launched On:
<time pubdate="pubdate">2012-01-12 </time>
</p>
</header>
<p>
This group continues the work of the W3C Federated Social Web Incubator Group (http://www.w3.org/2005/Incubator/federatedsocialweb/)
</p>
<form>
<p>
<a href="/community/wp-login.php?redirect_to=/community/fedsocweb/join" title="Join Federated Social Web Community Group" class="more-button">
<span class="small_text">JOIN THIS GROUP</span>
</a>
</p>
</form>
</article>
<article class="news_article">
<header>
<h4 class="header_article"> <a href="/community/pubsub">PubSubHubbub Community Group</a> </h4>
<p class="article_date">Launched On:
<time pubdate="pubdate">2012-01-11 </time>
</p>
</header>
<p>
The group will promote and design a Publish-Subscribe pattern and protocol for the web. The current de-facto protocol for it, PubSubHubbub is already widely used but has a couple issues that we...
<a href="/community/pubsub/"><strong>more</strong>
<span class="arrow_for_links">→</span>
</a>
</p>
<form>
<p>
<a href="/community/wp-login.php?redirect_to=/community/pubsub/join" title="Join PubSubHubbub Community Group" class="more-button">
<span class="small_text">JOIN THIS GROUP</span>
</a>
</p>
</form>
</article>
<article class="news_article">
<header>
<h4 class="header_article"> <a href="/community/ostatus">OStatus Community Group</a> </h4>
<p class="article_date">Launched On:
<time pubdate="pubdate">2012-01-11 </time>
</p>
</header>
<p>
OStatus is a suite of protocols that lets people on different social networks interact. This group will develop the next version of the protocol.
</p>
<form>
<p>
<a href="/community/wp-login.php?redirect_to=/community/ostatus/join" title="Join OStatus Community Group" class="more-button">
<span class="small_text">JOIN THIS GROUP</span>
</a>
</p>
</form>
</article>
<p><a href="/community/groups">View all 49 current groups</a><span class="arrow_for_links">→</span> </p>
</section>
<section class="unit size1on2 lastUnit tMargin">
<header>
<h3 class="header_article_group column header_article_group_proposed"> <a href="/community/groups/proposed/" title="Proposed Groups" class="icon_headers header_icon_groups_proposed" >Proposed Groups</a> </h3>
</header>
<article class="news_article">
<header>
<h4 class="header_article"><a href="/community/groups/proposed#html5spec" title="HTML5 Specifications Community Group">HTML5 Specifications Community Group</a></h4>
<p class="article_date">Proposed On:
<time pubdate="pubdate">2011-11-27</time>
</p>
</header>
<p>
A group addresses and discusses proposed ideas for HTML5 specifications.
</p>
<p><em>Proposed by Anas R.. 2 people support the group.</em></p>
<p>
<a href="/community/wp-login.php?redirect_to=http://www.w3.org/community/" class="more-button">
<span class="small_text">Log in to support creation</span></a></p>
</article>
<article class="news_article">
<header>
<h4 class="header_article"><a href="/community/groups/proposed#webprotoenergy" title="WEB Protocols and Energy Utilization Community Group">WEB Protocols and Energy Utilization Community Group</a></h4>
<p class="article_date">Proposed On:
<time pubdate="pubdate">2011-11-09</time>
</p>
</header>
<p>
Refactor the WEB Protocols in order to make them less energy utilizing for those who are concerned of that aspect. Make it possible to get immediate feedback to the end user how much each dialogue...
<a href="/community/groups/proposed/#webprotoenergy"><strong>more</strong>
<span class="arrow_for_links">→</span>
</a>
</p>
<p><em>Proposed by Willy Svenningsson. 3 people support the group.</em></p>
<p>
<a href="/community/wp-login.php?redirect_to=http://www.w3.org/community/" class="more-button">
<span class="small_text">Log in to support creation</span></a></p>
</article>
<article class="news_article">
<header>
<h4 class="header_article"><a href="/community/groups/proposed#sensorweb" title="Web of Sensors Community Group">Web of Sensors Community Group</a></h4>
<p class="article_date">Proposed On:
<time pubdate="pubdate">2011-11-03</time>
</p>
</header>
<p>
This group explores how the Web platform could interact with sensors around us. For instance, how do we hook up an Arduino and interact with it through the Web platform?
The scope is to explore...
<a href="/community/groups/proposed/#sensorweb"><strong>more</strong>
<span class="arrow_for_links">→</span>
</a>
</p>
<p><em>Proposed by Marcos Caceres. 4 people support the group.</em></p>
<p>
<a href="/community/wp-login.php?redirect_to=http://www.w3.org/community/" class="more-button">
<span class="small_text">Log in to support creation</span></a></p>
</article>
<p><a href="/community/groups/proposed">View all 6 proposed groups</a><span class="arrow_for_links">→</span> </p>
</section>
</div> </aside><!-- #first .widget-area -->
</section>
<h3 class="header_article_group"> <span class="icon_headers header_icon_news"> News </span></h3>
<p><em>The collected news from all Community and Business Groups, from the <a href="forum">W3C Forum</a> (a general discussion forum), and announcements of new groups and publications.</em></p>
<article id="post-1312" class="post-1312 post type-post status-publish format-standard hentry category-uncategorized tag-privacy">
<header class="clearfix">
<h3 class="header_article"><a href="http://www.w3.org/community/dntrack/2012/01/14/community-group-comments-on-w3c-dnt/" title="Permalink to Community Group comments on W3C DNT" rel="bookmark">Community Group comments on W3C DNT</a></h3>
<div class="article_info">
<img src="http://www.w3.org/2006/05/u/fae855c2f6eb-sm.jpg" height="50" class="avatar avatar-40 photo" style="height: 50px" /> <div class="article_date"> <p class="author vcard"><a class="url fn n" href="http://www.w3.org/community/blog/author/jsimpson2/" title="View all posts by John Simpson">John Simpson</a></p> Posted on <a href="http://www.w3.org/community/dntrack/2012/01/14/community-group-comments-on-w3c-dnt/" rel="bookmark"><time datetime="2012-01-14T23:51:23+00:00" pubdate>January 14, 2012</time></a> </div>
<p class="affiliation">Consumer Watchdog</p>
</div><!-- .article_info -->
</header>
<div class="entry-content">
<h1>Title: Community Group comments on W3C DNT</h1>
<h1>Date: Jan. 8, 2012</h1>
<h1>Editors: Lee Tien (EFF) and John M. Simpson (Consumer Watchdog)</h1>
<p> </p>
<p><em>This draft document represents the current consensus views of the following organizations: Center for Digital Democracy, Center for Media and Democracy, Consumer Federation of America, Consumers International, Consumers Union, Consumer Watchdog, Electronic Frontier Foundation, Fundacja Panoptykon, Privacy Rights Clearinghouse, and World Privacy Forum. Other consumer and privacy advocacy groups are considering the draft and are likely to join. We have reacted to the W3C Tracking Protection Working Groups First Public Working Drafts, as well as some of the issues that have been raised by the working group. As the Tracking Protection Working Group continues its process and completes its standards recommendations, we expect to have further refinements to this draft.</em></p>
<h1>Executive summary/high-level comments</h1>
<p>• The status quo is not normative; current tracking practices are anchored in business expectations of data flows that consumers generally would not like if they had full knowledge and understanding.</p>
<p>• Meeting user expectations should be the fundamental goal. We generally support Jonathan Mayer and Tom Lowenthal’s approach to first- and third-parties.</p>
<p>• We agree that usability of DNT for users is critical. In general, DNT should operate as a “set it and forget it” mechanism. It is appropriate for websites to seek site-specific exemptions, but we would be concerned if such mechanisms were too daunting for users.</p>
<p>• The DNT standard must permit user-agents to ship with the default of DNT:1. We recognize that this is up to the user-agent vendor under the standard. DNT defaults and reset mechanisms should be obvious and transparent.</p>
<p>• We recognize that this standards process is consensus-based and should accommodate business interests to a reasonable extent.</p>
<p>• We welcome exchange of views and information regarding operational use and other exceptions/exemptions. This process has just begun, so we do not have many detailed comments about such exemptions. Our general approach will be to place the burden on business to explain and justify such exemptions. First, we wish to understand the business case. Given that the consumer/privacy groups are far from well informed about commercial practices, it will be important to unpack claims relating to security, fraud, etc. Second, we wish to understand whether there are good alternatives to current or proposed practices for which exemptions are sought. Mozilla’s DNT field guide and other documents suggest that many operational uses can be accommodated under DNT with minimal cost to business. Third, if business interests cannot be so accommodated, we wish to understand why the business case should trump the user privacy interests at stake. The overall approach, we believe, will require detailed discussion about what data is actually needed for the particular purpose, how long it must be retained, and how it can be minimized while being useful.</p>
<h1>1. Introduction</h1>
<p>We appreciate the opportunity to participate as a Community Group in the W3C DNT process. We also appreciate all the work done by the W3C and working group members, especially the individual editors and drafters. This Community Group document represents the editors’ best understanding of the CG members’ views on the main issues presented to this date. We have ignored many of the more technical issues, and even for many of the policy issues our views remain unformed or unclear; when we do not address an issue, it does not mean that we agree with its current status. Nevertheless, this represents a good-faith effort to comment constructively on the WG work-product to date.</p>
<p> </p>
<p>While the commercial Internet/digital media environment provides important forums for diversity of expression, communication, and information, it has been structured to collect nearly unlimited amounts of information on each user — creating new forms of surveillance that raise crucial civil liberties and consumer protection concerns. In general, the user’s interest in not being tracked must be recognized as a right to be respected, not an obstacle to be overcome in the pursuit of data collection.</p>
<p> </p>
<p>Unfortunately, Internet tracking is invasive and pervasive. Wherever consumers go online and whatever they do is tracked usually without their knowledge and consent. What they click on, purchase, or share with others is compiled, analyzed and used to profile them. The data is often used to target advertising, but can also be used to make assumptions about people in connection with employment, housing, insurance, and financial services; for purposes of lawsuits against individuals; and for government surveillance.</p>
<p> </p>
<p>In our view, the vast majority of what users do online is quintessential expressional behavior —reading, writing, speaking, and associating with others — protected under the Universal Declaration of Human Rights, Article 19, which provides the right to “seek, receive and impart information and ideas through any media and regardless of frontiers.” In the United States, such activity enjoys significant constitutional protections against direct government interference (e.g., First Amendment law protects anonymous speech and privacy of association), but these protections can be circumvented when private actors keep records of online activity. Thus, for U.S. users, data about expressional activity is more weakly protected by law when it is stored by private actors.</p>
<p> </p>
<p>Our concern here is therefore mainly about the practices and products of tracking and the data retained or derived from tracking. We recognize that businesses may have valid economic interests in tracking, but businesses must also recognize that users have valid privacy and civil liberties interests in not being tracked and in control of the data retained or derived from tracking if users consent to such tracking. Even if businesses have clear and uncontroversial legitimate purposes for tracking, civil litigants and government entities may be able to obtain access to data retained or derived from tracking for purposes inimical to users’ interests.</p>
<p> </p>
<p>Our view is that the status quo is a product of a particular technological regime that was not designed to protect user privacy, under which much information is available to websites simply by virtue of how user-agents work. While we take that status quo as a practical given, we do not regard it as normative. For instance, users did not agree that browsers should transmit HTTP referrer information, and we would welcome user control over whether such data should be transmitted. In other words, that businesses are accustomed to receiving information about users, user-agents or user devices does not mean that businesses are entitled to receive that information.</p>
<p> </p>
<p>Given the status quo, citizens and consumers require tools, in addition to public policy, to protect their privacy. Existing tools are inadequate because they:</p>
<p>- <strong>Don’t actually work</strong>: Opt-out often means you don’t get targeted ads, but your information is still collected and your activities tracked.</p>
<p>- <strong>Are too confusing</strong>: Consumers don’t have the expertise to choose what companies to block, or where to go to block them.</p>
<p>- <strong>Require too many choices</strong>: Ad companies, Web browsers, search companies, and Websites all have different privacy tools and consumers must act to protect themselves with each.</p>
<p>- <strong>Don’t make clear whom to trust</strong>: There is no way for consumers to know if a privacy tool is a legitimate site, or if it is trying to trick them into giving up even more info (or worse yet, money!)</p>
<p> </p>
<p> </p>
<p>A “Do Not Track” mechanism is a method that allows a computer user to send a clear, unambiguous message that one’s online activities should not be tracked. There are a number of ways this could be accomplished. In fact the “Do Not Track” concept is technology neutral. It is any method that sends the message to websites a consumer visits that one’s activities should not be tracked. Simply put, “Do Not Track” is like posting a “No Trespassing” sign on your property. We leave to others the task of drawing the technical specifications for how such a message should be sent. At a minimum, however, the mechanism should be universal, easily usable, persistent, and cover all tracking technologies.</p>
<p> </p>
<h1>Tracking Preference Expression</h1>
<h2>Comments on Dec. 19 draft: http://www.w3.org/2011/tracking-protection/drafts/tracking-dnt.html</h2>
<p>We begin with some very general comments about the document.</p>
<p>First, the introduction is written from the industry standpoint; e.g. the rationale for DNT is “we don’t want to offend the user because this leads to lost revenue,” rather than “the user has certain privacy rights that we must respect.” Moreover, as noted above, users’ privacy interests are aligned against both commercial and government actors.</p>
<p> </p>
<p>Second, we are concerned about the presence of statements like “Advertising revenue is the single largest source of funding on the Web.” We do not know if this is true and we question its relevance here. The Internet includes vast non-commercial contributions of universities, government, libraries, nonprofit organizations and individual users. We expect that the W3C DNT standard will be adopted by these non-commercial entities as well.</p>
<p> </p>
<p>Third, the document frequently uses the term “cross-site tracking,” and we think it should simply refer to “tracking.”</p>
<h2>ISSUE-2: What is the meaning of DNT (Do Not Track) header?</h2>
<p>The document states:</p>
<h3>[CLOSED] “Does the presence of a DNT header field on requests always indicate an explicit choice.” The answer we agreed upon is “yes.”</h3>
<p>As noted earlier, we do not wish to prevent user-agent vendors from shipping with a default of DNT: 1, and we have some concern that the current language may do so. We believe that the current statement of ISSUE-4 permits user-agents to ship with DNT enabled. We equally believe that user-agents should not ship with a default of DNT:0.</p>
<h2>ISSUE-40: Enable Do Not Track just for a session, rather than being stored</h2>
<p>The document states:</p>
<h3>[CLOSED] Resolved in DNT Call 2011-10-26: The user agents are free to send different DNT values for different sessions. We agreed that this is a user-interface issue and out of scope on its own.</h3>
<h3>ISSUE-70: Does a past HTTP request with DNT set affect future HTTP requests? No</h3>
<p>These issues appear related. We strongly prefer that DNT settings persist across sessions until modified by the user. We do not object to the standard’s permissiveness here as a technical matter—when the DNT header is sent, servers need not “remember” previous sessions—but DNT will be significantly more valuable to users, and will better meet users’ expectations, if DNT need not reset each time users visit a website. A non-normative reference about the value of persistence may be appropriate here.</p>
<h2>Other closed issues</h2>
<p>We agree with the following:</p>
<h3>ISSUE-50: Are DNT headers sent to first parties? Yes</h3>
<h3>ISSUE-68: Should there be functionality for syncing preferences about tracking across different browsers?</h3>
<h4>[CLOSED] Resolved in DNT Call 2011-10-26: The user agents may or may not sync. However, this is out of scope for this spec.</h4>
<h3>ISSUE-42: Feedback to the user from the browser when Do Not Track is turned on: Yes, consistent with the apparent consensus on ISSUE-81.</h3>
<h2>Other major issues</h2>
<p>We understand the basic DNT configuration to have 3 possible states:</p>
<p>• DNT:1 (enabled, header sent)</p>
<p>• DNT:0 (enabled, header sent)</p>
<p>• Silence (user-agent lacks any DNT capability, or user/intermediary/user-agent did not set DNT (no header sent))</p>
<h3>ISSUE-13: What are the requirements for DNT on apps/native software in addition to browsers?</h3>
<p>We agree that W3C should use “the term <em>user agent</em> to refer to any of the various client programs capable of initiating HTTP requests, including browsers, spiders (web-based robots), command-line tools, native applications, and mobile apps.”</p>
<p> </p>
<p>One comment: the specific reference to HTTP may not be sufficiently technology-agnostic. For instance, the SPDY protocol may become more popular, and while current SPDY clients probably are “capable of initiating HTTP requests,” we do not know whether future clients might lack that capability. Nor would we want entities to end-run DNT by using protocols like ftp.</p>
<h3>ISSUE-4: What is the default for DNT in client configuration (opt-in or opt-out)?</h3>
<p>Our understanding is that the current consensus is agnostic, leaving it up to user-agent, so a browser MAY ship with DNT enabled [“We do not specify how that preference is configured: the user agent is responsible for determining the user experience by which this preference is set.]. This is acceptable for the technical standard, although we clearly prefer that DNT be set to “1” by default based on the belief that users generally prefer not to be tracked.</p>
<h3>ISSUE-95: May an institution or network provider set a tracking preference for a user?</h3>
<p>[current language] “An HTTP intermediary <em>must not</em> add, delete, or modify the DNT header field in requests forwarded through that intermediary unless that intermediary has been specifically installed or configured to do so by the user making the requests. For example, an Internet Service Provider must not inject DNT: 1 on behalf of all of their users who have not selected a choice.”</p>
<p>Our understanding is that there is no strong consensus here. We agree with the flat prohibition on intermediary modification of a user’s choice. We also prefer omitting the second paragraph about “There are some situations where an entity wishes to express a Do Not Track preference on the user’s behalf.” There is some interest in permitting intermediaries, when the user made no DNT choice, to set DNT: 1 (but not DNT: 0). This is a minority view provided for completeness’ sake.</p>
<h3>ISSUE-78: What is the difference between absence of DNT header and DNT = 0?</h3>
<p>“[PENDING REVIEW] Proposed text above defines that a “0″ may only be sent when DNT is enabled and some mechanism known to the user agent has specifically made an exception for this origin server. Note that we have not defined such a mechanism (and probably won’t do so). If DNT is disabled or not implemented, no DNT header field is sent. In the absence of regulatory, legal, or other requirements, servers are free to interpret the lack of a DNT header as they find most appropriate for the given user, particularly when considered in light of the user’s privacy expectations and cultural circumstances.”</p>
<p> </p>
<p>We agree that DNT silence is merely silence as a technical standard. In light of ISSUE-98: Consider applicable laws and regulations, such as Article 5(3) of the EU ePrivacy Directive, our understanding is that DNT silence will have concrete meaning in the EU, Canada, and any jurisdiction where the legal regime has more stringent consent rules than the United States. We discuss this further in the context of ISSUE-8, below.</p>
<h3>ISSUE-81: Do we need a response at all from servers?</h3>
<p>“[PENDING REVIEW] Yes: The users expect to be able to see whether a DNT header is accepted, rejected, or sent into the void.”</p>
<p> </p>
<p>We agree, server response is critical and lack of response should mean noncompliance with the standard.</p>
<h3>ISSUE-79: Should a server respond if a user sent DNT:0?</h3>
<p>Yes.</p>
<h3>ISSUE-51: Should 1st party have any response to DNT signal?</h3>
<p>Yes, all parties should acknowledge receipt of DNT header. No response signals noncompliance. First parties have definite DNT obligations. We emphasize again that while we generally accept the first-/third-party distinction as articulated by Mayer and Lowenthal for purposes of W3C’s DNT process, many of us would like to control first-party tracking as well (but recognize that consensus would not be likely on this point).</p>
<p> </p>
<p>Our acceptance of the Mayer-Lowenthal approach turns partly on its careful refusal to permit tracking by commonly branded affiliates under DNT: 1. Commonly branded affiliates may be in very different types of businesses and the fact that they share a corporate name is no guarantee that consumers will understand who they are or what they might do with their information.</p>
<h3>ISSUE-105: Response header without request header?</h3>
<p>If DNT=1, site MUST send response header (for compliance validation) (if no response header sent, this would mean non-compliance with spec)</p>
<p>If DNT=0, site MUST send response header (Issue-79)</p>
<p>If no DNT header at all, site MAY send response header</p>
<p> </p>
<p>We agree here.</p>
<h3>5.6 Status code for Tracking Required: An HTTP error response status code might be useful for indicating that the site refuses service unless the user either logs into a subscription account or agrees to an exception to DNT for this site and its contracted third-party sites.</h3>
<p>We agree.</p>
<h3>ISSUE-46: Enable users to do more granular blocking based on whether the site responds honoring Do Not Track</h3>
<p>We are not entirely sure what this issue means. If the site honors DNT, doesn’t that mean that it complies with the DNT header received? We support more granularity that gives the user more usable control, perhaps over tracking otherwise permitted under DNT: 1; sites that honor DNT may wish to be more privacy-protective. We have some concern that too much granularity can make DNT unwieldy and less attractive to users.</p>
<h3>ISSUE-43: Sites should be able to let the user know their options when they arrive with Do Not Track</h3>
<p>We generally agree. There is some concern that sites will simply say “if we can’t track you, you can’t use the site,” while others of us also believe that this will be unlikely. We are curious about the working group’s sense here.</p>
<h3>ISSUE-47: Should the response from the server point to a URI of a policy (or an existing protocol) rather than a single bit in the protocol?</h3>
<p>A possible danger here could be that the response points to a site privacy policy that tries to circumvent the user’s expressed DNT preference. We believe that such behavior would be non-compliant with the standard.</p>
<h3>ISSUE-87: Should there be an option for the server to respond with “I don’t know what my policy is”</h3>
<p>No. If the site represents itself as DNT-compliant, it must know its policy. If it does not know its policy, it is not DNT-compliant.</p>
<h1>Tracking Compliance and Scope</h1>
<h2>Comments on Dec. 14 draft: http://www.w3.org/2011/tracking-protection/drafts/tracking-compliance.html</h2>
<h2>ISSUE-8: user knowledge/expectations</h2>
<p> </p>
<p>Instead of the technology, we focus on websites’ compliance with a DNT request and user expectations when they opt to send the DNT message. The question of user expectations is a persistent theme in ongoing W3C discussion of DNT. We are greatly concerned that many stakeholders cannot put themselves in the ordinary web user’s place, expect users to understand more of what is happening on the web than they actually do, and accordingly impute more consent or even acquiescence of existing tracking practices than is realistic.</p>
<p> </p>
<p>Furthermore, even if users were as well informed as many stakeholders seem to think they are, users currently lack the tools to make their desires known. Indeed, the idea of DNT has become popular partly because businesses have deliberately circumvented users’ attempts to express their rejection of tracking. For example, when methods were developed to block tracking “cookies,” trackers got around that by using flash cookies.</p>
<p> </p>
<p>We also focus, where appropriate, on legal regimes that establish different user expectations as a matter of public policy. For instance, while the United States does not have a general background consumer privacy law that clearly resolves consent issues, other legal regimes do.</p>
<p> </p>
<h2>Canadian opt-out approach</h2>
<p>Under the recent Canadian guidance,</p>
<p> </p>
<p>“Any collection or use of an individual’s web browsing activity must be done with that person’s knowledge and consent. Therefore, if an individual is not able to decline the tracking and targeting using an opt-out mechanism because there is no viable possibility for them to exert control over the technology used, or if doing so renders a service unusable, then organizations should not be employing that type of technology for online behavioral advertising purposes.”</p>
<p> </p>
<p>Furthermore,</p>
<p> </p>
<p>“Opt-out consent for online behavioral advertising could be considered reasonable providing that:</p>
<p>“• Individuals are made aware of the purposes for the practice in a manner that is clear and understandable – the purposes must be made obvious and cannot be buried in a privacy policy. Organizations should be transparent about their practices and consider how to effectively inform individuals of their online behavioral advertising practices, by using a variety of communication methods, such as online banners, layered approaches, and interactive tools;</p>
<p>“• Individuals are informed of these purposes at or before the time of collection and provided with information about the various parties involved in online behavioral advertising;</p>
<p>“• Individuals are able to easily opt-out of the practice – ideally at or before the time the information is collected;</p>
<p>“• The opt-out takes effect immediately and is persistent;</p>
<p>“• The information collected and used is limited, to the extent practicable, to non-sensitive information (avoiding sensitive information such as medical or health information); and</p>
<p>“• Information collected and used is destroyed as soon as possible or effectively de-identified.”</p>
<h2>As we read this guidance, DNT silence would generally not permit tracking, and websites would need to implement other mechanisms in order to track in Canada. Conversely, it would seem that compliance with DNT would go a long way toward satisfying Canadian consent requirements, assuming that the user agent is DNT-capable in the first place.</h2>
<h2>EU/Art. 29 Working Group approach</h2>
<p>The European Union may take a stronger position on consent. As we read the recent Article 29 Working Group opinion on behavioral advertising (Opinion 16/2011), a DNT mechanism may be permissible under the e-Privacy Directive so long as “no tracking” is the default.</p>
<p> </p>
<p>Under EU principles, prior explicit opt-in consent is necessary for lawful tracking, and notice must be provided to users before data processing occurs. The Article 29 Working Group takes the position that such notice must include at least the following elements: who (which entities) collect data; what data is collected; that “profiles” (derived data, summaries, inferences, etc.) are created, and for what purpose or purposes; that the collection enables user identification across multiple websites; the duration of data or profile retention; the duration of any user informed consent.</p>
<p> </p>
<p>The Article 29 Working Group focused mainly on cookie-based tracking, but suggested that a DNT mechanism could satisfy its requirements so long as the default state was “no tracking.”</p>
<p> </p>
<p>This has implications for W3C, in that the current consensus is agnostic as to browser defaults. We have three distinct user expressions: user rejects tracking; user accepts tracking; user is silent (does not make a DNT choice). The W3C consensus appears to be that when the user is silent, websites have no compliance duties. Under the EU opt-in regime, it seems that user silence equals a user’s rejecting tracking. Under the Canadian regime, it seems that user silence could permit tracking, but only if the browser actually included a qualifying DNT mechanism or if the website had its own qualifying mechanism. If neither is present, then silence would not permit tracking (“if an individual is not able to decline the tracking and targeting using an opt-out mechanism because there is no viable possibility for them to exert control over the technology used, or if doing so renders a service unusable, then organizations should not be employing that type of technology for online behavioral advertising purposes.”).</p>
<p> </p>
<p> </p>
<h1>2. Scope and goals</h1>
<p>For purposes of these comments, we treat all of the data at issue as personal and identifiable data, because this data is at least initially associated with the user’s device, whether by IP address, a MAC address, or some other identifier (IMEI, IMSI, etc.). Even if users share devices, we believe that in a significant proportion of cases the device linkage is meaningful to the data collector (e.g., as expressing the purchasing preferences of a household as a unit), or that data collectors can disaggregate shared use (e.g., distinguishing between child and adult users in a household by destination, time of day, etc.). We will address proposals for de-personalizing data (aggregation, de-identification) as they emerge.</p>
<h1>3. Definitions</h1>
<h2>First and third parties<a title="" href="#_ftn1"><strong>[1]</strong></a></h2>
<p> </p>
<p>Various issues (10, 26, 49) are about the meaning of the first-party/third-party distinction. We generally agree with the Mayer-Lowenthal approach here, with minor points articulated below. We believe agree that the key principle underlying this distinction is consumer expectations, and not technical concerns such as domains or same-origin, as stated by Roy Fielding. Branding is relevant as a factor in consumer expectations, but not as an independent principle or test.</p>
<p> </p>
<p>When a user enters a URL and visits a specific website, that site which has its address in the user’s browser address box is considered the First Party site. By convention the user is the Second Party and all other sites are Third Parties. Because a user is directly interacting with the First Party there is an implicit understanding that data will be shared with the site. There is, however, no user expectation that data will be shared with unknown Third Party sites. The reality, as the Wall Street Journal’s “What They Know” series pointed out, is that Third Party tracking is extensive. The nation’s 50 top Websites install an average of 64 pieces of tracking technology on users’ browsers – all without your knowledge. This tracks all of your activity online, adds it to your profile, and then puts it up for instant sale in a stock market-like auction. And while the First Party/Third Party distinction is a useful analytic tool in assessing user expectations about Do Not Track obligations, it is also true that the distinctions between First and Third Parties are eroding, as the role of ad exchanges and demand side platforms, illustrate.</p>
<p> </p>
<p>Hidden webpage elements are, of course, core cases of third parties. They are deliberately concealed from users, and the average user is unaware of: web bugs or beacons; tools that can reveal them; how to prevent such elements from tracking them. Visible, conspicuous webpage elements like ads and widgets must also be treated as third parties. The average user does not realize that many ads are served by third parties rather than the first-party website they are visiting, or that information about the user is transmitted to those third parties. We believe that there is a general consensus on this point—that all of these webpage elements are third parties for DNT purposes.</p>
<p> </p>
<p>ISSUE-26: Providing data to 3rd-party widgets — does that imply consent? Our general answer is no. That said, Jonathan Mayer’s formulation — “A ‘first party’ is any party, in a specific network interaction, that can infer with high probability that the user knowingly and intentionally communicated with it. Otherwise, a party is a third party.”—may be sufficient. Our discussion below is tentative given the range of views within the Community Group.</p>
<p> </p>
<p>We also detect a weaker consensus on the general idea that a visible third party can become a first party for DNT purposes if and only if the user engages in “meaningful interaction” with the window or widget. We do not entirely agree here.</p>
<p> </p>
<p>First, stipulating for W3C purposes that users “expect” tracking by the sites they visit (in general, large well-established venues), it is not clear that users expect such recording tracking from widgets at all. Many widgets appear as an app that simply performs a specific function. In the case of a weather, stock or map widget, it may simply return a result, and the user may perceive the widget as merely an application without any memory. Indeed, we know that several years ago, many consumers thought of Google Search in this way and were surprised to learn that Google retained search histories.</p>
<p> </p>
<p>Second, even if users expect a widget to record data about them, they may not understand that a commonly branded widget is part of a hive mind. Branding and sharing data aren’t the same thing. As Jonathan Mayer stated,</p>
<p> </p>
<p>“Example 1: The user visits a site with a clearly-branded Accuweather.com weather widget. The user recognizes the branding and scrolls the widget forward to see tomorrow’s weather. The user expects to simply move the forecast ahead; the user does not expect Accuweather to collect cross-site tracking data.”</p>
<p> </p>
<p>That understanding could be different for well-known social widgets, such as from Facebook, Google, Twitter, etc. Our point is that an expectation of tracking by the widget is not the same as an expectation of the data’s being sent anywhere else.</p>
<p> </p>
<p>Part of this may be the nature of the interaction. Some third parties may behave in ways that make things much clearer. Maybe if you click on the Chips Ahoy ad you go to the Nabisco site or get Nabisco content, and it could be fair to say that Nabisco has become a first party. But it cannot be said categorically that deliberately clicking on a widget or other third-party element automatically confers first-party status. Put another way, an unknown party should not be endowed with first-party status merely because the user knows that party differs from the main page yet interacts anyway.</p>
<p> </p>
<h3>ISSUE-49: Third party as first party – is a third party that collects data on behalf of the first party treated the same way as the first party?</h3>
<p>Here again, we agree with the Mayer-Lowenthal approach, which we understand to restrict third parties. An overly permissive approach to third parties acting on behalf of first parties would negate DNT’s value. In the outsourcing of analytics example, it is critical that the third-party analytics provider silo all data collected on behalf of a first party and not make it available in any way to any entity other than that first party. Indeed, such siloing should be enforced technically per the ISSUE 73 draft.</p>
<h2>ISSUE-5: What is the definition of tracking?</h2>
<h3>Current text: “Behavioral tracking is the collection and retention of transactional data about the web-based activities of a particular user, computer, or device across non-commonly branded entities in a form that allows activities across non-commonly branded entities to be attributed to a particular user, computer, or device, over time, for any purpose other than the explicitly-excepted purposes specified below.”</h3>
<p> </p>
<p>We dislike this definition for several reasons. First, issues related to party status (branding), identifiability, purposes, exceptions, etc. need not be resolved in the definition of tracking. Second, we do not see the need to limit the definition to “behavioral,” “transactional data” or “particular” users or devices etc. For instance, the current definition of “transactional data” refers to “information about the user’s interactions with various websites, services, or widgets which could be used to create a record of a user’s system information, online communications, transactions and other activities, including websites visited, pages and ads viewed, purchases made, etc.” We worry that building many restrictions into the basic definition will create unnecessary ambiguity and may inadvertently exclude relevant data.</p>
<p> </p>
<p>It seems much simpler to use a broad definition, e.g. “Tracking is the collection of data about Internet activities of a user, computer, or device (including mobile phones and devices), over time and across a Website or Websites.”</p>
<p> </p>
<p>Specific enumerated purposes, such as site maintenance and improvement, fraud prevention or legal compliance may warrant exemptions if they are well defined. [note Art. 29 point that the exemption would be limited to certain requirements e.g. prior notice and consent, without exempting from minimum necessary, revocation, spoliation etc.]</p>
<p> </p>
<p>We do not limit our understanding of tracking from a policy or rights perspective to cross-site tracking. As explained earlier, our concern about tracking stems ultimately from the retention of data about users’ online activities, and the fact that such data is maintained by first-party websites does not prevent other parties (such as the government) from obtaining that data and correlating it across multiple websites.</p>
<p> </p>
<p>We nevertheless agree that in the W3C DNT context, it may be possible, and will be valuable, to develop a consensus around the mechanisms for addressing cross-site and third-party tracking. Our point here is that we are also concerned about first-party tracking, even if W3C DNT does not address it.</p>
<p> </p>
<h3>ISSUE-16: What does it mean to collect data? (caching, logging, storage, retention, accumulation, profile etc.)</h3>
<p>We believe that ALL of these should be included within “collect data,” but accommodations can be made for specific contexts. We expect that the WG will address minimization techniques, e.g. de-identification, truncation, and real-time or near-real-time deletion (ephemeral storage),</p>
<h3>ISSUE-92: If data collection (even very specific with IP address, user agent, referrer) is time-limited, with very limited retention, is that still tracking?</h3>
<p>Yes. Given the technical status quo, passive collection of protocol information will happen, but we see no reason to define such passive collection out of the definition of tracking. The preferred approach would be to create specific, well-justified exemptions with appropriately tailored minimization or other safeguards.</p>
<h3>ISSUE-89: Does DNT mean at a high level: (a) no customization, users are seen for the first time, every time. (b) DNT is about data moving between sites.</h3>
<p>We are not sure what this issue is really about.</p>
<h3>ISSUE-97: Re-direction, shortened URLs, click analytics — what kind of tracking is this?</h3>
<p>We believe that all of these are third-party tracking. We agree with Justin Brookman’s email comment:</p>
<p> </p>
<p>“I can’t think of a single URL shortener scenario that looks like a first-party interaction. If I read this on Twitter: “Neat WSJ story on <a href='http://www.w3.org/community/blog/tag/privacy/' rel='tag' class="hashtag">#privacy</a> in the cloud: goo.gl/eT3d” and click on the link, I think the WSJ is the first party and Google is a third party. I’m clearly not trying to interact with Google – someone just used that service to get under 140 characters, and I could care less whether they used bit.ly, j.mp, t.co, c.dt or anything else.”</p>
<p> </p>
<p>We recognize that we may not understand all of the corner cases here, but in general it seems that the user does not intend to interact with the third party.</p>
<h3>ISSUE-55: What is relationship between behavioral advertising and tracking, subset, different items?</h3>
<p>Behavioral advertising uses tracking to create a profile of the user and then serve targeted ads. Many industry privacy “solutions” only stop the serving of ads — but not the tracking, which is our focus. When DNT is enabled, the site must not track (with the exception of specified exceptions).</p>
<h3>ISSUE-71: Does DNT also affect past collection or use of past collection of info?</h3>
<p>Yes.</p>
<h1>Other issues</h1>
<h2>ISSUE-36: Should DNT opt-outs distinguish between behavioral targeting and other personalization?</h2>
<p>No, but we welcome further elaboration. In general we see no need for a distinction. Our underlying focus is on the tracking, so the real issue is whether the personalization uses tracking. We agree with the draft that “when the header is set to DNT:1, then this will indicate that no personalization should occur,” and that previously collected data would not be used.</p>
<p> </p>
<p>We are uncomfortable with the exceptions in the draft specification. For instance, we disagree with the example: “An individual visiting a news site will expect to see local news and weather based on her current location regardless of DNT header setting.” Such person may expect news and weather based on her home location even when traveling abroad. The general exception for “When it is individual’s expectation that personalization will occur” seems too elastic in the face of DNT: 1.</p>
<p> </p>
<p>Also, the exceptions in the draft specification touch on several different issues that may need to be resolved first: treatment of the collection-retention distinction; geolocation data; and the interaction of DNT with other user-configured settings, including logging status.</p>
<h2>Issue-30: offline data</h2>
<p>The issue seems to be: “Should we address the association of first party data with third party data? What does this standard say about a first party associating offline data from a third party with their own data and then using that in targeting? How about the first party associating it with third party data and/or selling it to a third party?”</p>
<p>We believe that DNT: 1 means no transfer of data and no use of offline data.</p>
<p>–first parties MUST not offline transfer any data to any third parties that they could not online transfer to</p>
<p>–first parties MUST not offline transfer any data to any parties not subject to DNT (because that could easily circumvent DNT)</p>
<p>–third parties MUST not offline receive any data from any parties subject to DNT that they could not online receive</p>
<p> </p>
<p>We believe that “offline append” is included. Users don’t want to go to a first-party site and see “We saw that you bought adult diapers when you last went shopping! Want to buy some more?” At that point, it has become online data even if it didn’t start that way, and seems to be fully in scope.</p>
<h2>Issue-32: Sharing of data between entities via cookie syncing/identity brokering</h2>
<p>We do not fully understand the current draft, but we fear that it could undermine DNT. It may also be insufficiently technology-agnostic. We welcome further elaboration.</p>
<p> </p>
<h1>4. Compliance with an expressed tracking preference</h1>
<h2>First-party compliance with DNT message</h2>
<p> </p>
<p>We believe that when a First Party receives a DNT message:</p>
<p> </p>
<p>The First Party MUST NOT share users’ data with third parties. An exception would be if the Third Party is acting as an agent performing a function only for the First Party and does nothing else with the data. An example might be analytics. If the Third Party is the agent of multiple First Parties, it must silo each First Party’s data without any sharing or analysis across data silos.</p>
<p> </p>
<p>The First Party SHOULD collect only the data necessary to complete the transaction during the current session and not store the data over time, without the users’ explicit informed consent.</p>
<h3>ISSUE-17: Data use by 1st Party (overlap issue)</h3>
<p>As stated above, it would be preferable if first parties did not track if DNT: 1 (should not).</p>
<h3>ISSUE-54: Can first party provide targeting based on registration information even while sending DNT</h3>
<p>No. As we understand the issue, this is about first parties sending data to others in the face of DNT: 1.</p>
<h3>ISSUE-59: Should the first party be informed about whether the user has sent a DNT header to third parties on their site?</h3>
<p>Yes.</p>
<h3>ISSUE-91: Might want prohibitions on first parties re-selling data to get around the intent of DNT (overlap issue)</h3>
<p>Yes.</p>
<h2>Third party compliance</h2>
<p>When a Third Party receives a DNT message, it MUST NOT collect data from a user without the users’ explicit informed consent.</p>
<p> </p>
<p>When a Third Party widget is embedded in a First Party site, is clearly branded and the user has meaningful interaction with the widget, it becomes a First Party site for the transaction and it MAY collect data necessary for the transaction. It MUST NOT retain the data beyond the session.</p>
<h2>ISSUE-39: Tracking of geographic data (however it’s determined, or used)</h2>
<p>Current draft text: “This specification does not place limitations on the use of geolocation technologies by the operators of third-party domains.”</p>
<p> </p>
<p>We disagree. There has been significant public concern about geolocation in various contexts recently. DNT=1 should block all third-party geolocation, because users who express the no-tracking preference probably object to geolocation, subject to valid exemptions. ISSUE-36 touches on this issue, generally in a reasonable way, but we don’t see why IP-based reverse-lookup geolocation should be automatically permitted. In any case, we believe that users want to be able to express the preference about geolocation, and it is reasonable for DNT: 1 to be used for that purpose.</p>
<h2>Exemptions generally</h2>
<p>Our comments here are fairly abstract. As stated at the outset of this document, our general approach will be to place the burden on business to explain and justify such exemptions concretely. There are certainly important business interests here, but these must be clearly specified. At this time, we have had very little detailed discussion, and we have not reviewed all of the extant drafts.</p>
<p> </p>
<p>Transparency is especially important here, because these exemptions permit tracking even in the face of DNT: 1. The standard should require websites to inform users about their practices with respect to these exemptions.</p>
<h3>ISSUE-22: Still have “operational use” of data (auditing of where ads are shown, impression tracking, etc.)</h3>
<p>The current draft describes operational uses. We need to better understand what data is needed, for which operational uses, for how long, etc. We also need to account for the existence of ways of accommodating business interests under DNT.</p>
<h3>Issue-31: Minimization for exemptions — to what extent will minimization be required for use of a particular exemption? (conditional exemptions)</h3>
<p>Here, we believe an issue-by-issue approach is needed. For example, Mayer’s IETF DNT draft stated that “Protocol logs used solely for advertising fraud detection, and subject to a one month retention period” and “Protocol logs used solely for security purposes such as intrusion detection and forensics, and subject to a six month retention period.” We do not accept these specific minimization proposals, because we lack good data about why these retention periods were chosen, but the general approach seems reasonable.</p>
<h3>ISSUE-23: Possible exemption for analytics, ISSUE-34: Possible exemption for aggregate analytics</h3>
<p>We have not reviewed this draft yet.</p>
<h3>ISSUE-73: In order for analytics or other contracting to count as first-party: by contract, by technical silo, both silo and contract</h3>
<p>We have not reviewed this draft yet, but generally agree that both technical silo and contract should be used.</p>
<h3>ISSUE-24: Possible exemption for fraud detection and defense</h3>
<p>We recognize that fraud detection and defense is a significant interest, but there has been insufficient discussion of the details for us to comment further.</p>
<h3>ISSUE-25: Possible exemption for research purposes, ISSUE-74: Are surveys out of scope?</h3>
<p>We believe that surveys are in scope. More discussion is needed on the meaning of “research.”</p>
<h3>ISSUE-28: Exception for mandatory legal process</h3>
<p>This is unavoidable, but the standard could benefit users by increasing transparency. For instance, Google has been a pioneer in informing the public about its responses to surveillance requests. Some U.S. service providers routinely notify users/subscribers about subpoenas, when legally permitted to do so. Where the law itself is unsettled about the legal process required to compel production or collection of data, companies can be more transparent about what they insist upon — in the U.S. context, for instance, companies may have policies about whether they always require a warrant for some kinds of data.</p>
<h3>ISSUE-75: How do companies claim exemptions and is that technical or not?</h3>
<p>[transparency again? In privacy policy/TOS?]</p>
<h3>Issue-15: what special treatment for children’s data?</h3>
<p>Current draft specification: “The DNT: 1 header does not require special treatment for children because DNT:1 means no tracking regardless of whether the user is a child or not. Note that operator handling of children’s data may also be governed by local laws and regulations, such as COPPA in US.”</p>
<p> </p>
<p>We generally agree, but there is strong dissent within our group that would treat websites aimed at children differently.</p>
<p> </p>
<p><strong>5. User Interactions</strong></p>
<p> </p>
<p>We are still discussing this section.</p>
<p> </p>
<p><strong>6. Interaction with other tools</strong></p>
<p> </p>
<p>We are still discussing this section.</p>
<p>###</p>
<div></p>
<hr align="left" size="1" width="33%" />
<div>
<p> <a title="" href="#_ftnref1">[1]</a> Chris Calabrese likes the Rush HR 5777 def’n (10) THIRD PARTY-</p>
<p>(A) IN GENERAL- The term ‘third party’ means, with respect to any covered entity, a person that–</p>
<p>(i) is not related to the covered entity by common ownership or corporate control; or
(ii) is a business unit or corporate entity that holds itself out to the public as separate from the covered entity, such that an individual acting reasonably under the circumstances would not expect it to be related to the covered entity or to have access to covered information the individual provides to that covered entity.</p>
</div>
</div>
</div><!-- .entry-content -->
<footer class="entry-utility">
From <a href="/community/dntrack/">Do-Not-Track Community Group</a>
<span class="meta-sep">|</span>
No Comments |
<a rel='nofollow' class='comment-reply-link' href='http://www.w3.org/community/blog/2012/01/14/community-group-comments-on-w3c-dnt/#respond' onclick='return addComment.moveForm("post-13", "0", "respond", "13")'>Leave a Comment</a>
<span class="meta-sep">|</span>
<span class="cat-links">
<span class="entry-utility-prep entry-utility-prep-cat-links">Category</span> <a href="http://www.w3.org/community/blog/category/uncategorized/" title="View all posts in Uncategorized" rel="category tag">Uncategorized</a> </span>
<span class="tag-links">
<span class="entry-utility-prep entry-utility-prep-tag-links">Tagged</span> <a href="http://www.w3.org/community/blog/tag/privacy/" rel="tag">privacy</a> </span>
</footer><!-- .entry-utility -->
</article><!-- #post-## -->
<article id="post-1311" class="post-1311 post type-post status-publish format-standard hentry category-semantic-web category-uncategorized tag-cg">
<header class="clearfix">
<h3 class="header_article"><a href="http://www.w3.org/community/socbizcg/2012/01/13/welcome-a-few-organizational-details/" title="Permalink to Welcome – A few organizational details" rel="bookmark">Welcome – A few organizational details</a></h3>
<div class="article_info">
<img src="http://www.w3.org/2006/05/u/76f4e3597159-sm.jpg" height="50" class="avatar avatar-40 photo" style="height: 50px" /> <div class="article_date"> <p class="author vcard"><a class="url fn n" href="http://www.w3.org/community/blog/author/drobinso5/" title="View all posts by David Robinson">David Robinson</a></p> Posted on <a href="http://www.w3.org/community/socbizcg/2012/01/13/welcome-a-few-organizational-details/" rel="bookmark"><time datetime="2012-01-13T22:30:38+00:00" pubdate>January 13, 2012</time></a> </div>
<p class="affiliation">IBM Corporation</p>
</div><!-- .article_info -->
</header>
<div class="entry-content">
<p>The Social Business Group is just now forming and I’ve heard from several future members that they are going through their company’s internal processes to join.</p>
<p>If you are considering joining us, I’d like to provide a few details that might be helpful to you.</p>
<p>You can read more about the W3C Community Group process here:</p>
<p>http://www.w3.org/community/about/<a href='http://www.w3.org/community/blog/tag/cg/' rel='tag' class="hashtag">#cg</a></p>
<p>The community group process is free and does not require W3C membership.</p>
<p>To join this group, click the “Join This Group” button on the group home page and accept to the lightweight IP agreement.</p>
<p>Since this group is brand new, there are several “start up” activities to take care of. We need a charter to set the bounds of the group, define how we operate, to define how this group interacts with other community groups and other standards organizations, etc. I will propose a draft charter – perhaps at the first group meeting (more on the first group meeting a bit lower in this wiki post).</p>
<p>During group formation, it was proposed we take a look at the W3C Social Business Jam Results Document and the list of recommendations for next steps in that document. The results document can be found here:</p>
<p>http://www.w3.org/2011/socialbusiness-jam/report.html</p>
<p>It has also been proposed that this group work on common social business use cases and best practices with an eye on how this information affects any existing standards or highlights the needs for new standards in the social business space.</p>
<p>If there is an operative word for this group, it could be “liaison”. If standards already exist somewhere else, we want to work with those groups for improvement. If we find true gaps, we decide where best to move forward with new standards.</p>
<p>That is a little bit of background.</p>
<p>We want to “get going” and be productive quickly, so I am working with the group chair to schedule our first meeting (kick off meeting). Please look for the kick off meeting to appear on the upcoming events calendar for the group soon.</p>
<p>If you have a topic you would like discussed at the kick off meeting, please send the topic to me or the group chair so we can place it on the agenda. If you are interested in some sort of leadership position in the group, please let me know about that also.</p>
<p>If you are looking for additional information about the group or have questions, please feel free to contact me via the W3C.</p>
</div><!-- .entry-content -->
<footer class="entry-utility">
From <a href="/community/socbizcg/">W3C Social Business Community Group</a>
<span class="meta-sep">|</span>
No Comments |
<a rel='nofollow' class='comment-reply-link' href='http://www.w3.org/community/blog/2012/01/13/welcome-a-few-organizational-details/#respond' onclick='return addComment.moveForm("post-7", "0", "respond", "7")'>Leave a Comment</a>
<span class="meta-sep">|</span>
<span class="cat-links">
<span class="entry-utility-prep entry-utility-prep-cat-links">Category</span> <a href="http://www.w3.org/community/blog/category/semantic-web/" title="View all posts in Semantic Web" rel="category tag">Semantic Web</a>, <a href="http://www.w3.org/community/blog/category/uncategorized/" title="View all posts in Uncategorized" rel="category tag">Uncategorized</a> </span>
<span class="tag-links">
<span class="entry-utility-prep entry-utility-prep-tag-links">Tagged</span> <a href="http://www.w3.org/community/blog/tag/cg/" rel="tag">cg</a> </span>
</footer><!-- .entry-utility -->
</article><!-- #post-## -->
<article id="post-1310" class="post-1310 post type-post status-publish format-standard hentry category-uncategorized">
<header class="clearfix">
<h3 class="header_article"><a href="http://www.w3.org/community/socbizcg/2012/01/13/new-zdnet-post-consistent-standards-for-defining-social-business/" title="Permalink to New ZDNet post ‘Consistent standards for defining ‘social business’" rel="bookmark">New ZDNet post ‘Consistent standards for defining ‘social business’</a></h3>
<div class="article_info">
<img alt='' src='http://1.gravatar.com/avatar/5ffda19d2cf7d9d8fdae1d9840bd3ba0?s=50&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D50&r=G' class='avatar avatar-50 photo' height='50' width='50' /> <div class="article_date"> <p class="author vcard"><a class="url fn n" href="http://www.w3.org/community/blog/author/omarks/" title="View all posts by oliver marks">oliver marks</a></p> Posted on <a href="http://www.w3.org/community/socbizcg/2012/01/13/new-zdnet-post-consistent-standards-for-defining-social-business/" rel="bookmark"><time datetime="2012-01-13T20:48:51+00:00" pubdate>January 13, 2012</time></a> </div>
<p class="affiliation">Sovos Group</p>
</div><!-- .article_info -->
</header>
<div class="entry-content">
<p><a href="http://www.zdnet.com/blog/collaboration/consistent-standards-for-defining-social-business/2257?tag=mantle_skin;content">http://www.zdnet.com/blog/collaboration/consistent-standards-for-defining-social-business/2257?tag=mantle_skin;content</a></p>
<p>Summary: The W3C are getting more involved with defining standards around ’social business’ – this is a very good thing IMO</p>
<p><img src="http://www.vincegolangco.com/wp-content/uploads/2010/09/Airport-Crowd.jpg" alt="" width="537" height="322" /></p>
<p>We’re entering a fresh year of marketing wars around <a href="http://www.zdnet.com/blog/collaboration/everybody-in-social/1867" target="_blank">naming conventions</a>, with various vendors aligned around conceptual ideas that they hope will define and corner the market for them. The noise level is likely to be greater than ever as investments need to be recouped and projected (and possibly hoped for…) market share captured.</p>
<p>While everyone and their brother has now baked an activity stream into their software, there are large, complicated operational activities enabled by our new interconnectedness and associated technologies which are not well defined and which vary enormously in value depending on industry vertical. Interoperability with previous generations of technologies and deeply ingrained ways of working make the task of defining the opportunities for greater efficiency all the more challenging.</p>
<p>Battle lines that have been drawn for some time between vendors are likely to become more defined this year, but more importantly will the average Joe or Jane outside the tech industry have any idea what all the noise is about? As Larry Dignan commented on ZDNet <a href="http://www.zdnet.com/blog/btl/ibm-aims-to-formalize-the-social-enterprise-movement/66704?tag=mantle_skin;content" target="_blank">earlier this week</a> there’s “<em>…more chatter about the social enterprise than the tech industry can stand” </em>and in my experience some people are already exasperated and turned off by all the noise over substance. I’ve talked to various people at the<a href="http://www.w3.org/standards/" target="_blank"> W3C</a> over the last couple of weeks on several topics including standards for Social Business/ Social Enterprise/ Enterprise 2.0/Collaborative Networks …or whatever you choose to call formally deployed Web 2.0 and mobile technologies inside companies and more importantly the work patterns that can improve productivity around them.</p>
<p>A heroic precursor and enabler to the Web 2.0 movement was<a href="http://www.webstandards.org/" target="_blank"> WASP, The Web Standards Project</a>, which was formed by visual coders and designers to help drive consistency across the various flavors of web browsers, which was driving everyone nuts back then. In that era there was some frustration with the W3C not holding the various vendors feet to the fire on consistency around adherence to html and later CSS standards. That type of battle ten years ago could well be repeated in the coming months, this time about technical adherence and use models, and the W3C are thankfully involved at an earlier stage this time.</p>
<p>Most large companies already have many flavors of technologies in house – marketing has <a href="http://www.jivesoftware.com/" target="_blank">Jive</a>, engineers <a href="http://www.atlassian.com/" target="_blank">Atlassian</a>, IT <a href="http://sharepoint.microsoft.com/" target="_blank">Sharepoint</a> etc etc – and getting any kind of interoperability and information between the various username and password protected collaboration silos can be very problematic, particularly when there are fiefdoms involved.</p>
<p>The larger players are now making fresh significant moves to try to capture enterprise scale with use case frameworks. The<a href="http://www.dachisgroup.com/" target="_blank"> Dachis Group</a> did ground breaking work on the then new concept of a social business over the last three years, while Jive software renamed their Clearspace products ‘Social Business Software’ in 2009 and of course <a href="http://www.salesforce.com/" target="_blank">Salesforce</a> have evangelized their vision of the ‘Social Enterprise’ on the foundation of their <a href="http://force.com/">force.com</a> platform. <a href="http://www.ibm.com/smarterplanet/us/en/socialbusiness/overview/index.html" target="_blank">IBM</a> have been slowly ramping up their version of Social Business – I attended a free roadshow with prospects this time last year where Rob Koplowitz of analyst firm <a href="http://forrester.com/" target="_blank">Forrester</a> presented their current vision. Not much interest from the attendees I spoke to back then, who admittedly were mostly pre existing IBM clients grappling with older generations of their technology.</p>
<p>A lot has happened in the last twelve months however and many people have done great work in maturing both the products and the marketplace: Jive successfully IPO’d and funding has flowed to various software companies in anticipation of a lucrative new market space. I’m one of the people working with end users of these technologies and have the bruises that come with actually rolling up your sleeves on a Monday morning and making better collaboration work within the parameters and contexts of specific company cultures, and can attest to the marketing sizzle deprogramming often necessary before you get to the pragmatic work of driving greater efficiencies – which is what justifies the purchase of these technologies.</p>
<p>The W3C did an ‘<a href="http://www.zdnet.com/news/the-success-of-social-business-depends-on-standards/6329649" target="_blank">idea jam</a>‘ using IBM technology in November of last year, partly to discuss the value of open standards in social business – more on this in another post – and IBM and Google in particular appear to be getting behind greater consistency through the W3C stewardship, which I think is a great thing and good insurance against post irrational exuberance bubble bursts. Saba Software are currently running a <a href="https://mix.sabapeoplecloud.com/" target="_blank">Management 2.0 Hackathon</a> led by <a href="http://www.garyhamel.com/" target="_blank">Gary Hamel</a> I’m involved with which is throwing up some interesting angles, cumulatively these efforts will ideally result in a body of mature thinking that will be of more use than than the endless ‘How to’ social media lightweight handy hints that often do more harm than good. A little knowledge is a dangerous thing….</p>
<p>Aside from all the marketing driven vendors I’d be remiss if I didn’t mention <a href="http://www.atlassian.com/" target="_blank">Atlassian</a> and <a href="http://www.alfresco.com/" target="_blank">Alfresco </a>in the big picture, who are the solid bedrock for those choosing to roll their own environments, vendors such as <a href="http://www.socialtext.com/" target="_blank">Socialtext </a>and <a href="http://traction.tractionsoftware.com/" target="_blank">Traction Team Page</a> who have done so much to get the marketplace to where it is today through their deep thinking and contributions to the evolving online world – and of course the much maligned (and successful) Microsoft Sharepoint and associated cloud developments. Companies free of the baggage incumbents such as IBM have, such as <a href="http://www.moxiesoft.com/" target="_blank">Moxie software</a> or <a href="http://box.net/" target="_blank">Box.net</a> arguably have advantages in their ability to provide the opportunity for a fresh start to prospects, an idea <a href="http://www.jivesoftware.com/" target="_blank">Jive</a> have historically been very successful with in the past.</p>
<p>With HR Tech, Business Process and all manner of other vendors all jumping into the ’social’ space there has never been a more important time for standards consistency – this will be a very interesting next few months and a lot depends on the longer term triumph of standards over <a href="http://www.zdnet.com/blog/collaboration/collaborative-networks-never-mistake-a-clear-view-for-a-short-distance/2199" target="_blank">marketing hyperbole</a>.</p>
<p>~</p>
</div><!-- .entry-content -->
<footer class="entry-utility">
From <a href="/community/socbizcg/">W3C Social Business Community Group</a>
<span class="meta-sep">|</span>
No Comments |
<a rel='nofollow' class='comment-reply-link' href='http://www.w3.org/community/blog/2012/01/13/new-zdnet-post-consistent-standards-for-defining-social-business/#respond' onclick='return addComment.moveForm("post-4", "0", "respond", "4")'>Leave a Comment</a>
<span class="meta-sep">|</span>
<span class="cat-links">
<span class="entry-utility-prep entry-utility-prep-cat-links">Category</span> <a href="http://www.w3.org/community/blog/category/uncategorized/" title="View all posts in Uncategorized" rel="category tag">Uncategorized</a> </span>
</footer><!-- .entry-utility -->
</article><!-- #post-## -->
<article id="post-1309" class="post-1309 post type-post status-publish format-standard hentry category-uncategorized">
<header class="clearfix">
<h3 class="header_article"><a href="http://www.w3.org/community/ostatus/2012/01/12/migrating-content-from-ostatus-org-and-wiki-ostatus-org/" title="Permalink to Migrating content from ostatus.org and wiki.ostatus.org" rel="bookmark">Migrating content from ostatus.org and wiki.ostatus.org</a></h3>
<div class="article_info">
<img src="http://www.w3.org/2006/05/u/2e1cfc2440ac-sm.jpg" height="50" class="avatar avatar-40 photo" style="height: 50px" /> <div class="article_date"> <p class="author vcard"><a class="url fn n" href="http://www.w3.org/community/blog/author/eprodrom/" title="View all posts by Evan Prodromou">Evan Prodromou</a></p> Posted on <a href="http://www.w3.org/community/ostatus/2012/01/12/migrating-content-from-ostatus-org-and-wiki-ostatus-org/" rel="bookmark"><time datetime="2012-01-12T18:01:29+00:00" pubdate>January 12, 2012</time></a> </div>
</div><!-- .article_info -->
</header>
<div class="entry-content">
<p>I’d like to take the maintenance of <a href="http://ostatus.org/">ostatus.org</a> content out of my own incapable hands, and make it more accessible through this community group.</p>
<p><a href="http://ostatus.org/">ostatus.org</a> itself consists of a Drupal-based blog with <10 posts plus a copy of the spec. I believe it can be pretty easily transferred to the community group sites here, which run on WordPress.</p>
<p><a href="http://wiki.ostatus.org/">wiki.ostatus.org</a> is a MediaWiki wiki. I believe the content can be dumped and restored on the new community group wiki, but new user accounts will need to be created.</p>
<p>After that’s done, I’ll try to 301-redirect specific URLs in the ostatus.org domain to their new equivalents on the w3.org sites.</p>
</div><!-- .entry-content -->
<footer class="entry-utility">
From <a href="/community/ostatus/">OStatus Community Group</a>
<span class="meta-sep">|</span>
No Comments |
<a rel='nofollow' class='comment-reply-link' href='http://www.w3.org/community/blog/2012/01/13/welcome-a-few-organizational-details/#respond' onclick='return addComment.moveForm("post-7", "0", "respond", "7")'>Leave a Comment</a>
<span class="meta-sep">|</span>
<span class="cat-links">
<span class="entry-utility-prep entry-utility-prep-cat-links">Category</span> <a href="http://www.w3.org/community/blog/category/uncategorized/" title="View all posts in Uncategorized" rel="category tag">Uncategorized</a> </span>
</footer><!-- .entry-utility -->
</article><!-- #post-## -->
<article id="post-1308" class="post-1308 post type-post status-publish format-standard hentry category-uncategorized">
<header class="clearfix">
<h3 class="header_article"><a href="http://www.w3.org/community/pubsub/2012/01/12/meeting-at-or-near-fosdem-2012/" title="Permalink to Meeting at or near FOSDEM 2012" rel="bookmark">Meeting at or near FOSDEM 2012</a></h3>
<div class="article_info">
<img src="http://www.w3.org/2006/05/u/2e1cfc2440ac-sm.jpg" height="50" class="avatar avatar-40 photo" style="height: 50px" /> <div class="article_date"> <p class="author vcard"><a class="url fn n" href="http://www.w3.org/community/blog/author/eprodrom/" title="View all posts by Evan Prodromou">Evan Prodromou</a></p> Posted on <a href="http://www.w3.org/community/pubsub/2012/01/12/meeting-at-or-near-fosdem-2012/" rel="bookmark"><time datetime="2012-01-12T17:48:30+00:00" pubdate>January 12, 2012</time></a> </div>
</div><!-- .article_info -->
</header>
<div class="entry-content">
<p>Can we organize an in-person meeting of this community group at or near <a href="http://fosdem.org/2012/">FOSDEM 2012</a>? I’ve started a wiki page for a <a href="http://www.w3.org/community/pubsub/wiki/Meeting_February_2012">February 2012 meeting</a> to discuss.</p>
</div><!-- .entry-content -->
<footer class="entry-utility">
From <a href="/community/pubsub/">PubSubHubbub Community Group</a>
<span class="meta-sep">|</span>
2 Comments |
<a rel='nofollow' class='comment-reply-link' href='http://www.w3.org/community/blog/2012/01/12/meeting-at-or-near-fosdem-2012/#respond' onclick='return addComment.moveForm("post-6", "0", "respond", "6")'>Leave a Comment</a>
<span class="meta-sep">|</span>
<span class="cat-links">
<span class="entry-utility-prep entry-utility-prep-cat-links">Category</span> <a href="http://www.w3.org/community/blog/category/uncategorized/" title="View all posts in Uncategorized" rel="category tag">Uncategorized</a> </span>
</footer><!-- .entry-utility -->
</article><!-- #post-## -->
<article id="post-1307" class="post-1307 post type-post status-publish format-standard hentry category-uncategorized">
<header class="clearfix">
<h3 class="header_article"><a href="http://www.w3.org/community/ostatus/2012/01/12/new-ostatus-community-group-at-w3c/" title="Permalink to New OStatus Community Group at W3C" rel="bookmark">New OStatus Community Group at W3C</a></h3>
<div class="article_info">
<img src="http://www.w3.org/2006/05/u/2e1cfc2440ac-sm.jpg" height="50" class="avatar avatar-40 photo" style="height: 50px" /> <div class="article_date"> <p class="author vcard"><a class="url fn n" href="http://www.w3.org/community/blog/author/eprodrom/" title="View all posts by Evan Prodromou">Evan Prodromou</a></p> Posted on <a href="http://www.w3.org/community/ostatus/2012/01/12/new-ostatus-community-group-at-w3c/" rel="bookmark"><time datetime="2012-01-12T17:30:22+00:00" pubdate>January 12, 2012</time></a> </div>
</div><!-- .article_info -->
</header>
<div class="entry-content">
<p>I’m happy to see that the new community group for OStatus has started.</p>
<p>My goals for this group are to:</p>
<ul>
<li>develop future versions of the OStatus specification.</li>
<li>provide resources for implementers.</li>
</ul>
<p><span style="font-size: small"><span style="line-height: 24px"><br />
</span></span></p>
</div><!-- .entry-content -->
<footer class="entry-utility">
From <a href="/community/ostatus/">OStatus Community Group</a>
<span class="meta-sep">|</span>
No Comments |
<a rel='nofollow' class='comment-reply-link' href='http://www.w3.org/community/blog/2012/01/13/new-zdnet-post-consistent-standards-for-defining-social-business/#respond' onclick='return addComment.moveForm("post-4", "0", "respond", "4")'>Leave a Comment</a>
<span class="meta-sep">|</span>
<span class="cat-links">
<span class="entry-utility-prep entry-utility-prep-cat-links">Category</span> <a href="http://www.w3.org/community/blog/category/uncategorized/" title="View all posts in Uncategorized" rel="category tag">Uncategorized</a> </span>
</footer><!-- .entry-utility -->
</article><!-- #post-## -->
<article id="post-1306" class="post-1306 post type-post status-publish format-standard hentry category-uncategorized">
<header class="clearfix">
<h3 class="header_article"><a href="http://www.w3.org/community/pubsub/2012/01/12/congratulations/" title="Permalink to Congratulations" rel="bookmark">Congratulations</a></h3>
<div class="article_info">
<img src="http://www.w3.org/2006/05/u/ee5de5f29c14-sm.jpg" height="50" class="avatar avatar-40 photo" style="height: 50px" /> <div class="article_date"> <p class="author vcard"><a class="url fn n" href="http://www.w3.org/community/blog/author/msabadel/" title="View all posts by Markus Sabadello">Markus Sabadello</a></p> Posted on <a href="http://www.w3.org/community/pubsub/2012/01/12/congratulations/" rel="bookmark"><time datetime="2012-01-12T13:27:26+00:00" pubdate>January 12, 2012</time></a> </div>
</div><!-- .article_info -->
</header>
<div class="entry-content">
</div><!-- .entry-content -->
<footer class="entry-utility">
From <a href="/community/pubsub/">PubSubHubbub Community Group</a>
<span class="meta-sep">|</span>
1 Comment |
<a rel='nofollow' class='comment-reply-link' href='http://www.w3.org/community/blog/2012/01/13/new-zdnet-post-consistent-standards-for-defining-social-business/#respond' onclick='return addComment.moveForm("post-4", "0", "respond", "4")'>Leave a Comment</a>
<span class="meta-sep">|</span>
<span class="cat-links">
<span class="entry-utility-prep entry-utility-prep-cat-links">Category</span> <a href="http://www.w3.org/community/blog/category/uncategorized/" title="View all posts in Uncategorized" rel="category tag">Uncategorized</a> </span>
</footer><!-- .entry-utility -->
</article><!-- #post-## -->
<article id="post-1305" class="post-1305 post type-post status-publish format-standard hentry category-announcements">
<header class="clearfix">
<h3 class="header_article"><a href="http://www.w3.org/community/blog/2012/01/12/call-for-participation-in-federated-social-web-community-group/" title="Permalink to Call for Participation in Federated Social Web Community Group" rel="bookmark">Call for Participation in Federated Social Web Community Group</a></h3>
<div class="article_info">
<img alt='' src='http://0.gravatar.com/avatar/207694e1ed3d7e40761b3ba7edf7524c?s=50&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D50&r=G' class='avatar avatar-50 photo' height='50' width='50' /> <div class="article_date"> <p class="author vcard"><a class="url fn n" href="http://www.w3.org/community/blog/author/steam/" title="View all posts by Search Team">Search Team</a></p> Posted on <a href="http://www.w3.org/community/blog/2012/01/12/call-for-participation-in-federated-social-web-community-group/" rel="bookmark"><time datetime="2012-01-12T13:04:55+00:00" pubdate>January 12, 2012</time></a> </div>
</div><!-- .article_info -->
</header>
<div class="entry-content">
<p>W3C has launched the <a href="http://www.w3.org/community/fedsocweb/">Federated Social Web Community Group</a></p>
<hr />
This group continues the work of the W3C Federated Social Web Incubator Group (http://www.w3.org/2005/Incubator/federatedsocialweb/)</p>
<hr />
<p>In order to join the group, you will need a <a href="http://www.w3.org/community/account/request">W3C account</a>.</p>
<p>If you believe that there is an issue with this group that requires the attention of the W3C staff, please send us email on <a href="mailto:site-comments@w3.org">site-comments@w3.org</a></p>
<p>Thank you,<br />
W3C Community Development Team</p>
</div><!-- .entry-content -->
<footer class="entry-utility">
From Global W3C Group Blog
<span class="meta-sep">|</span>
No Comments |
<a rel='nofollow' class='comment-reply-link' href='http://www.w3.org/community/blog/2012/01/12/call-for-participation-in-federated-social-web-community-group/#respond' onclick='return addComment.moveForm("post-1305", "0", "respond", "1305")'>Leave a Comment</a>
<span class="meta-sep">|</span>
<span class="cat-links">
<span class="entry-utility-prep entry-utility-prep-cat-links">Category</span> <a href="http://www.w3.org/community/blog/category/announcements/" title="View all posts in Announcements" rel="category tag">Announcements</a> </span>
</footer><!-- .entry-utility -->
</article><!-- #post-## -->
<article id="post-1294" class="post-1294 post type-post status-publish format-standard hentry category-announcements">
<header class="clearfix">
<h3 class="header_article"><a href="http://www.w3.org/community/blog/2012/01/11/proposed-group-federated-social-web-community-group/" title="Permalink to Proposed Group: Federated Social Web Community Group" rel="bookmark">Proposed Group: Federated Social Web Community Group</a></h3>
<div class="article_info">
<img alt='' src='http://0.gravatar.com/avatar/207694e1ed3d7e40761b3ba7edf7524c?s=50&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D50&r=G' class='avatar avatar-50 photo' height='50' width='50' /> <div class="article_date"> <p class="author vcard"><a class="url fn n" href="http://www.w3.org/community/blog/author/steam/" title="View all posts by Search Team">Search Team</a></p> Posted on <a href="http://www.w3.org/community/blog/2012/01/11/proposed-group-federated-social-web-community-group/" rel="bookmark"><time datetime="2012-01-11T23:57:10+00:00" pubdate>January 11, 2012</time></a> </div>
</div><!-- .article_info -->
</header>
<div class="entry-content">
<p>The Federated Social Web Community Group has been proposed:</p>
<hr />
This group continues the work of the W3C Federated Social Web Incubator Group (http://www.w3.org/2005/Incubator/federatedsocialweb/)</p>
<hr />
<p>You are invited to <a href="http://www.w3.org/community/groups/proposed#fedsocweb">support the creation of this group</a>. Once the group has a total of five supporters, W3C launch the group and people can join to begin work.</p>
<p>In order to join the group, you will need a <a href="http://www.w3.org/community/account/request">W3C account</a>.</p>
<p>If you believe that there is an issue with this group that requires the attention of the W3C staff, please send us email on <a href="mailto:site-comments@w3.org">site-comments@w3.org</a></p>
<p>Thank you,<br />
W3C Community Development Team</p>
</div><!-- .entry-content -->
<footer class="entry-utility">
From Global W3C Group Blog
<span class="meta-sep">|</span>
No Comments |
<a rel='nofollow' class='comment-reply-link' href='http://www.w3.org/community/blog/2012/01/11/proposed-group-federated-social-web-community-group/#respond' onclick='return addComment.moveForm("post-1294", "0", "respond", "1294")'>Leave a Comment</a>
<span class="meta-sep">|</span>
<span class="cat-links">
<span class="entry-utility-prep entry-utility-prep-cat-links">Category</span> <a href="http://www.w3.org/community/blog/category/announcements/" title="View all posts in Announcements" rel="category tag">Announcements</a> </span>
</footer><!-- .entry-utility -->
</article><!-- #post-## -->
<article id="post-1288" class="post-1288 post type-post status-publish format-standard hentry category-announcements">
<header class="clearfix">
<h3 class="header_article"><a href="http://www.w3.org/community/blog/2012/01/11/call-for-participation-in-ostatus-community-group/" title="Permalink to Call for Participation in OStatus Community Group" rel="bookmark">Call for Participation in OStatus Community Group</a></h3>
<div class="article_info">
<img alt='' src='http://0.gravatar.com/avatar/207694e1ed3d7e40761b3ba7edf7524c?s=50&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D50&r=G' class='avatar avatar-50 photo' height='50' width='50' /> <div class="article_date"> <p class="author vcard"><a class="url fn n" href="http://www.w3.org/community/blog/author/steam/" title="View all posts by Search Team">Search Team</a></p> Posted on <a href="http://www.w3.org/community/blog/2012/01/11/call-for-participation-in-ostatus-community-group/" rel="bookmark"><time datetime="2012-01-11T17:29:20+00:00" pubdate>January 11, 2012</time></a> </div>
</div><!-- .article_info -->
</header>
<div class="entry-content">
<p>W3C has launched the <a href="http://www.w3.org/community/ostatus/">OStatus Community Group</a></p>
<hr />
OStatus is a suite of protocols that lets people on different social networks interact. This group will develop the next version of the protocol.</p>
<hr />
<p>In order to join the group, you will need a <a href="http://www.w3.org/community/account/request">W3C account</a>.</p>
<p>If you believe that there is an issue with this group that requires the attention of the W3C staff, please send us email on <a href="mailto:site-comments@w3.org">site-comments@w3.org</a></p>
<p>Thank you,<br />
W3C Community Development Team</p>
</div><!-- .entry-content -->
<footer class="entry-utility">
From Global W3C Group Blog
<span class="meta-sep">|</span>
No Comments |
<a rel='nofollow' class='comment-reply-link' href='http://www.w3.org/community/blog/2012/01/11/call-for-participation-in-ostatus-community-group/#respond' onclick='return addComment.moveForm("post-1288", "0", "respond", "1288")'>Leave a Comment</a>
<span class="meta-sep">|</span>
<span class="cat-links">
<span class="entry-utility-prep entry-utility-prep-cat-links">Category</span> <a href="http://www.w3.org/community/blog/category/announcements/" title="View all posts in Announcements" rel="category tag">Announcements</a> </span>
</footer><!-- .entry-utility -->
</article><!-- #post-## -->
</div><!-- #content -->
</div>
<div class="unit size1on3 lastUnit">
<div id="text-3" class="widget-container widget_text"> <div class="textwidget"><div class="join_box">
<aside>
<h3>How do I start a group?</h3>
<p>Anyone with a <a href="http://www.w3.org/community/account/request">W3C account</a> may create a group:</p>
<ol>
<li>Push one of the buttons below and provide a name and description for the group.</li>
<li>Once four other people support the group (by pushing a button), W3C creates it.</li>
<li>Join the group and start using the <a href="http://www.w3.org/community/about/tool/">tools and infrastructure</a> to build your community.</li>
</ol>
<a href="/community/groups/propose_cg" title="Start a community group" class="action_button">Start a community group</a> <a href="/community/groups/propose_bg" title="Start a business group" class="action_button second">Start a business group</a> </aside>
<aside>
<h3>Where can I share ideas?</h3>
<p>The <a href="/community/forum/">W3C Forum</a> is a general forum where you can generate support for your ideas.</p>
</aside>
</div></div>
</div><div id="text-8" class="widget-container widget_text"> <div class="textwidget"><h3 class="header_article_group"><a href="/community/about/faq">FAQ</a></h3>
<ul>
<li><a href="http://www.w3.org/community/about/faq/#how-are-community-and-business-groups-similar-different">How are Community and Business Groups different? Similar?</a></li>
<li><a href="http://www.w3.org/community/about/faq/#what-are-main-similarities-and-differences-between-ipr-policies-of-working-groups-and-communitybusiness-groups">How are IPR policies different from W3C Working Groups?</a></li>
<li><a href="http://www.w3.org/community/about/faq/">More frequently asked questions<span class="arrow_for_links">→</span></a></li>
</ul></div>
</div><div id="categories-2" class="widget-container widget_categories"><h3 class="header_article_group">All Group Posts by Category</h3> <ul>
<li class="cat-item cat-item-75"><a href="http://www.w3.org/community/blog/category/administrative/" title="Administrative">Administrative</a> (1)
</li>
<li class="cat-item cat-item-33"><a href="http://www.w3.org/community/blog/category/announcements/" title="For system-wide announcements (e.g., new groups)">Announcements</a> (94)
</li>
<li class="cat-item cat-item-36"><a href="http://www.w3.org/community/blog/category/deployments/" title="Deployments">Deployments</a> (1)
</li>
<li class="cat-item cat-item-62"><a href="http://www.w3.org/community/blog/category/discussion/" title="discussion">discussion</a> (1)
</li>
<li class="cat-item cat-item-3"><a href="http://www.w3.org/community/blog/category/events/" title="View all posts filed under Events">Events</a> (12)
</li>
<li class="cat-item cat-item-34"><a href="http://www.w3.org/community/blog/category/implementations/" title="Implementations">Implementations</a> (3)
</li>
<li class="cat-item cat-item-69"><a href="http://www.w3.org/community/blog/category/information/" title="Information">Information</a> (1)
</li>
<li class="cat-item cat-item-94"><a href="http://www.w3.org/community/blog/category/introductions/" title="Introductions">Introductions</a> (4)
</li>
<li class="cat-item cat-item-81"><a href="http://www.w3.org/community/blog/category/meeting/" title="meeting">meeting</a> (1)
</li>
<li class="cat-item cat-item-55"><a href="http://www.w3.org/community/blog/category/news/" title="News">News</a> (2)
</li>
<li class="cat-item cat-item-41"><a href="http://www.w3.org/community/blog/category/other-w3c-groups/" title="Other W3C groups">Other W3C groups</a> (1)
</li>
<li class="cat-item cat-item-29"><a href="http://www.w3.org/community/blog/category/publication/" title="Publication">Publication</a> (1)
</li>
<li class="cat-item cat-item-43"><a href="http://www.w3.org/community/blog/category/releases/" title="Releases">Releases</a> (1)
</li>
<li class="cat-item cat-item-35"><a href="http://www.w3.org/community/blog/category/specifications/" title="Specifications">Specifications</a> (1)
</li>
<li class="cat-item cat-item-44"><a href="http://www.w3.org/community/blog/category/start/" title="start">start</a> (1)
</li>
<li class="cat-item cat-item-54"><a href="http://www.w3.org/community/blog/category/tips-and-tricks/" title="Tips and tricks">Tips and tricks</a> (1)
</li>
<li class="cat-item cat-item-1"><a href="http://www.w3.org/community/blog/category/uncategorized/" title="View all posts filed under Uncategorized">Uncategorized</a> (69)
</li>
<li class="cat-item cat-item-77"><a href="http://www.w3.org/community/blog/category/use-cases/" title="Use cases">Use cases</a> (1)
</li>
<li class="cat-item cat-item-73"><a href="http://www.w3.org/community/blog/category/w3cwidgets/" title="W3C Widgets">W3C Widgets</a> (10)
</li>
<li class="cat-item cat-item-93"><a href="http://www.w3.org/community/blog/category/web-certificate-services/" title="Web Certificate Services">Web Certificate Services</a> (1)
</li>
<li class="cat-item cat-item-82"><a href="http://www.w3.org/community/blog/category/web-crypto/" title="Web Crypto">Web Crypto</a> (2)
</li>
<li class="cat-item cat-item-91"><a href="http://www.w3.org/community/blog/category/web-identity/" title="Web Identity">Web Identity</a> (2)
</li>
</ul>
</div> </div><!-- .last unit -->
</div><!-- .line -->
</div><!-- #primary -->
</div><!-- #main -->
<aside id="w3c_footer" class="unit clearfix">
<div id="w3c_footer-inner" >
<h2 class="offscreen">Footer Navigation</h2>
<div class="w3c_footer-nav">
<h3>Navigation</h3>
<ul class="footer_top_nav">
<li><a href="/">Home</a></li>
<li><a href="/standards/">Standards</a></li>
<li><a href="/participate/">Participate</a></li>
<li><a href="/Consortium/membership">Membership</a></li>
<li class="last-item"><a href="/Consortium/">About W3C</a></li>
</ul>
</div>
<div class="w3c_footer-nav">
<h3>Contact W3C</h3>
<ul class="footer_bottom_nav">
<li><a href="/Consortium/contact">Contact</a></li>
<li><a accesskey="0" href="/Help/">Help and FAQ</a></li>
<li><a href="/Consortium/sponsor/">Sponsor / Donate</a></li>
<li><a href="/Consortium/siteindex">Site Map</a></li>
<li>
<address id="w3c_signature">
<a href="mailto:site-comments@w3.org">Feedback</a> (<a href="http://lists.w3.org/Archives/Public/site-comments/">archive</a>)
</address>
</li>
</ul>
</div>
<div class="w3c_footer-nav">
<h3>W3C Updates</h3>
<ul class="footer_follow_nav">
<li><a href="http://twitter.com/W3C" title="Follow W3C on Twitter"><img src="/community/src/img/twitter-bird.png" alt="Twitter" class="social-icon" width="78" height="83" /></a> <a href="http://identi.ca/w3c" title="See W3C on Identica"><img src="/community/src/img/identica-logo.png" alt="Identica" class="social-icon" width="91" height="83" /></a></li>
</ul>
</div>
<!-- #footer address / page signature -->
<footer class="copyright">Copyright © 2011 W3C <sup>®</sup> (<a href="http://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>, <a href="http://www.ercim.eu/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>, <a href="http://www.keio.ac.jp/">Keio</a>) <a href="/Consortium/Legal/ipr-notice">Usage policies apply</a>.</footer>
</div><!-- #w3c_footer-inner -->
</aside><!-- #w3c_footer -->
<script type="text/javascript" src="/community/src/js/functions.js"></script>
<script type='text/javascript'>
/* <![CDATA[ */
var pollsL10n = {"ajax_url":"http:\/\/www.w3.org\/community\/wp-content\/plugins\/wp-polls\/wp-polls.php","text_wait":"Your last request is still being processed. Please wait a while ...","text_valid":"Please choose a valid poll answer.","text_multiple":"Maximum number of choices allowed: ","show_loading":"1","show_fading":"1"};
/* ]]> */
</script>
<script type='text/javascript' src='http://www.w3.org/community/wp-content/plugins/wp-polls/polls-js.js?ver=2.50'></script>
</body>
</html>