Confirmed users
152
edits
Line 123: | Line 123: | ||
|} | |} | ||
While we went back and forth internally over how to rate each dimension, and others will undoubtedly weigh things differently, we hope this analysis points out that codes of conduct are not going to be a one-size-fits all approach to online privacy. | While we went back and forth internally over how to rate each dimension, and others will undoubtedly weigh things differently, we hope this analysis points out that codes of conduct are not going to be a one-size-fits all approach to online privacy. Nor will codes be easy to develop and promulgate without, in many cases, seeing changes across multiple stakeholders to gear up to tackle any one online privacy and security consideration. | ||
From our analysis, we would end up | From our analysis, we would end up ranking privacy considerations for online services directed at teenagers as an ideal area for a code, given the maturity and number of accountable industry and public interest groups already working on kids privacy as a result of the Children's Online Privacy Protection Act. Likewise, looking to codes in the area of collecting personal data via multiple technologies (e.g., cookies, LSOs and cache) is another area where we see technology standards groups being well positioned and public interest groups having substantial experience working together with business and consumers to be a potentially good area for a code of conduct. | ||
Overall, from our perspective, the important thing for the Administration to recognize is when conditions are ideal to convene a multistakeholder process to develop a code of conduct for online privacy. | |||
===III. Mozilla's Experience: Considerations for Implementing Multi Stakeholder Processes=== | ===III. Mozilla's Experience: Considerations for Implementing Multi Stakeholder Processes=== |