Required attribute of <current> is dropped

While considering the change in the definition of <current> and
having input from P3P implementers, the Working Group found, that
the "required" - attribute of current adds more confusion and
doesn't provide any valid semantics. 

In fact, there is no reason to opt-in or opt-out of a
<current>-purpose. If the user proceeds with the transaction
despite the indication of a stated current purpose, the service
want's to complete the request. The completion of this request
requires always certain data. This data is always required. 

All additional demands for further data, not necessary for the
transaction, don't fall into <current> and have to choose a
different purpose, which allows to specify opt-in, opt-out or
always required...

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

Received on Friday, 27 July 2001 09:24:44 UTC