W3C home > Mailing lists > Public > www-p3p-public-comments@w3.org > October 2001

RE: customization purpose

From: Clifford Lyon <Clifford.Lyon@cnet.com>
Date: Wed, 24 Oct 2001 10:36:52 -0700
Message-ID: <F5E5CB897FCA1A4BAC3FD38CEBA1A644F9191E@zdnet08.zdz.cnwk>
To: "'Lorrie Cranor'" <lorrie@research.att.com>, www-p3p-public-comments@w3.org
Thanks Lorrie. Current does seem to be the best match.

In the case of the newly defined "current-purpose", the opt-in would not apply, since the required attr was removed - isn't that right?

-----Original Message-----
From: Lorrie Cranor [mailto:lorrie@research.att.com]
Sent: Tuesday, October 23, 2001 10:14 PM
To: Clifford Lyon; www-p3p-public-comments@w3.org
Subject: Re: customization purpose


The customization purpose is covered by other
purposes with required set to "opt-in" (not the 'other' purpose).
Depending on the type of customization, it may be
covered by current, tailoring, pseudo-decision, or
individual decision. In your case it sounds like
current would be appropriate (note the new definition
of current), but I would have to know more about
what you are doing to know for sure.

Regards,

Lorrie Cranor

----- Original Message -----
From: "Clifford Lyon" <Clifford.Lyon@cnet.com>
To: <www-p3p-public-comments@w3.org>
Sent: Tuesday, October 23, 2001 5:57 PM
Subject: customization purpose


> Hi,
>
> >>Removed the customization purpose in 3.3.4
>
> Our old policy used customization purpose to cover things like stock
watchers. Going fwd, should this be added as an `other' purpose? Or is the
thought that is need not be included at all?
>
> Thanks,
>
> Cliff Lyon
>
Received on Wednesday, 24 October 2001 13:38:12 GMT

This archive was generated by hypermail 2.2.0+W3C-0.1 : Tuesday, 21 September 2004 12:14:17 GMT