W3C home > Mailing lists > Public > www-p3p-dev@w3.org > March 2004

Re: Implementing P3P policy for on-line surveys.

From: Lorrie Cranor <lorrie@cs.cmu.edu>
Date: Tue, 30 Mar 2004 22:21:00 -0500
Message-Id: <6EC95670-82C2-11D8-8624-000A95DA3F5A@cs.cmu.edu>
Cc: www-p3p-dev@w3.org
To: Olga Veksler <Olga.Veksler@foreseeresults.com>

You can have a single policy reference file that includes multiple 
POLICY-REF elements. Each POLICY-REF element associates a specific URL 
(or sets of URLs) with a policy. So, assuming your surveys each have a 
unique URL, you should be able to apply a separate policy to each one.


On Mar 22, 2004, at 4:14 PM, Olga Veksler wrote:

> Hello,
> Our company is conducting surveys for different web sites.  Our 
> surveys are usually presented on our clients' web sites as pop-up 
> windows.   Surveys are dynamically generated and are not stored as 
> files.  We are trying to make the surveys p3p compliant.  We think 
> that we can implement p3p policy by placing an embedded link tag on 
> our surveys.  The problem is that we collect different types of 
> information depending on the customer.  So for different customers we 
> would like to implement different policies.  I understand that we can 
> create as many policies as we want, but should there be only one 
> reference file?  In the embedded link we are supposed to reference our 
> policy reference file then how would I specify which policy to use.
> Please advise on how to implement p3p for our on-line surveys.
> Thank you,
> Olga Veksler
> _______________
> Olga Veksler
> Developer
> ForeSee Results
> 2929 Plymouth Rd. Suite 220
> Ann Arbor, MI  48105
> Olga.Veksler@ForeSeeResults.com
> www.ForeSeeResults.com
> phone:   734-205-2578
> fax:       734-205-2601
Lorrie Faith Cranor <http://lorrie.cranor.org/>
(Note, as of Dec 2003 I'm at Carnegie Mellon University)
P3P Specification Working Group Chair <http://www.w3.org/p3p/>
Book: Web Privacy with P3P <http://p3pbook.com/>
Received on Tuesday, 30 March 2004 22:24:10 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:49:16 UTC