This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 169 - statement grouping mechanism
Summary: statement grouping mechanism
Alias: None
Product: P3P
Classification: Unclassified
Component: Vocabulary extensions (show other bugs)
Version: unspecified
Hardware: Other other
: P2 normal
Target Milestone: P3P1.1
Assignee: Lorrie Cranor
QA Contact:
Depends on:
Blocks: 217
  Show dependency treegraph
Reported: 2003-03-10 21:35 UTC by Lorrie Cranor
Modified: 2008-12-02 22:41 UTC (History)
0 users

See Also:


Description Lorrie Cranor 2003-03-10 21:35:17 UTC
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.
Comment 1 Lorrie Cranor 2003-07-30 13:31:45 UTC
Jeremy submitted a proposal at
2003Jul/0046.html -- this is related to Mathias' proposal at
05-cc-changes-to-P3P.html -- These proposals will be combined
Comment 2 Rigo Wenning 2003-08-27 10:15:25 UTC
is the exact URI of the proposal
makes it clickable

Below is the text of the proposal for convenience:


* 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

* 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
* 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
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
* Do agents now show conflicts per grouping?
Comment 3 Rigo Wenning 2004-01-19 14:47:12 UTC
There were no further issues related to the consent-choices draft. It should go 
to the specification as is. My concerns persist though