This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Consider adding a STATEMENT grouping mechanism to allow user agents to display similar statements to the user together (for example all statements that have to do with buyers as opposed to sellers at an auction site). This might be implemented by adding an element that serves as a container for STATEMENTS. Alternatively this might be implemented by adding a group-name attribute to the STATEMENT element.
Jeremy submitted a proposal at http://lists.w3.org/Archives/Public/public-p3p-spec/ 2003Jul/0046.html -- this is related to Mathias' proposal at http://www.w3.org/P3P/2003/ 05-cc-changes-to-P3P.html -- These proposals will be combined
http://lists.w3.org/Archives/Public/public-p3p-spec/2003Jul/0046.html is the exact URI of the proposal http://www.w3.org/P3P/2003/05-cc-changes-to-P3P.html makes it clickable Below is the text of the proposal for convenience: Problems * Policies are not relevant to how a user interacts with the site * Users don't know what part of a P3P policy applies to them and there activities on a site * Users understand scenarios of how they interact with a site better than a series of statements related to a feature of the site * Policy authors have to make highest common denominate policies that could look more privacy impacting than they are for most users Goals * Provide a method for showing the sections of the P3P policy that apply to how a user interacts with the site/service * Allow an easy way for policy authors to describe what sections of their P3P policy apply to different user interaction with their site/service Scenarios * User browses to ebay and views the P3P policy. They are able to skip to the buyer section of the P3P policy since that is what applies to them. * User browses to amazon and views the P3P policy. The can see that since they are not logged in less information is collected about them. Design The P3P author decides the name of the statement group which is used in the display of the agent when it translates the nodes to natural language. <statement> <extention> <grouping-id>Member</grouping-id> </extention> <statement> Issues * Do agents now show conflicts per grouping?
There were no further issues related to the consent-choices draft. It should go to the specification as is. My concerns persist though