Dear all,
beforehand, the Specification contained "affirmative"
customization. The definition was:
<customization/>
Affirmative Customization: Information may be used to tailor or
modify the content or design of the site only to specifications
affirmatively selected by the particular individual during a
single visit or multiple visits to the site. For example, a
financial site that lets users select several stocks whose
current prices are displayed whenever the user visits.
During the discussion around the "required" attribute we found,
that "affirmative" customization had only the option of "opt-in"
as it was "affirmative", means the user had to select and
complete an action. Yuichi Koike suggested, that we drop this
purpose, as the semantics could be covered with <pseudo-decision
required="opt-in" /> or <individual-decision required="opt-in"/>
The Working Group followed his arguments and decided to drop the
"affirmative" <customization/> - purpose.
The updates-page[1] was updated accordingly
Best,
Rigo Wenning W3C/INRIA
Policy Analyst Privacy Activity Lead
mail:rigo@w3.org 2004, Routes des Lucioles
+33 (0)6 73 84 87 31 F-06902 Sophia Antipolis
http://www.w3.org/
1. http://www.w3.org/P3P/updates.html