W3C home > Mailing lists > Public > www-p3p-policy@w3.org > April 2003

question about dynamic.cookies and dynamic.miscdata

From: Humphrey, Jack <JHumphrey@coremetrics.com>
Date: Wed, 2 Apr 2003 17:34:41 -0600
Message-ID: <1059641497.IAA22192@phantom.w3.org>
To: "'www-p3p-policy@w3.org'" <www-p3p-policy@w3.org>

For full policies, are the categories associated with the #dynamic.cookies
data element supposed to represent the type of data stored in the cookie, or
any data linked by the cookie?

If the latter (any data linked by the cookie), does that data need to be
reclared in the same data group, e.g. using #dynamic.miscdata?

For example, if you store a unique id in the cookie, and collect navigation
and interactive user information that is tied to the user via the unique id
in the cookie, does the data group need to look like this?
<data ref="#dynamic.cookies">
 <categories>
  <uniqueid>
  <navigation>
  <interactive>
 </categories>
</data>
<data ref="#dynamic.miscdata">
 <categories>
  <uniqueid>
 </categories>
</data>
<data ref="#dynamic.miscdata">
 <categories>
  <navigation>
 </categories>
</data>
<data ref="#dynamic.miscdata">
 <categories>
  <interactive>
 </categories>
</data>

...or can the <navigation> and <interactive> elements be removed from the
cookies data element? Or perhaps the miscdata elements are redundant and not
necessary?

If you write a policy like the one above, Internet Explorer will duplicate
information in the human-readable interpretation. It will look something
like this:

What kind of information does this Web site collect?
	Unique identifiers issued by a Web site or service...
	
	Information generated by browsing the Web site...

	Information generated from or reflectig explicit interations...

	Unique identifiers issued by a Web site or service...
	
	Information generated by browsing the Web site...

	Information generated from or reflectig explicit interations...

It would be nice to be able to avoid this redundancy in IE's interpretation,
but if the policy as written above is correct, then it's really an IE issue.

Appreciate any guidance.

Jack Humphrey
 
Received on Wednesday, 2 April 2003 18:34:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 17 January 2012 12:13:10 GMT