Re: Question about P3P

--nextPart4045722.eqMI18RakD
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Dear Sudhakar,=20

Am Monday 26 September 2005 01:36, sprach Nischal:
>
> My name is Sudhakar Jalli. I am a web developer for a
> mortgage company here in California. I got your email
> address at www.w3.org
>
> I am very new to P3P. I am just going over the
> specification since couple of days. I have a question
> about the data collection on our web site.
>
> Our web site users are usually mortgage brokers who
> use our application to fill in their client critical
> information into our system. We do not store any of
> these mortgage brokers information but we do store
> their clients very crictical information.
>
> I was wondering if P3P is going to cover this scope of
> privacy too. If yes, do you know how I can achieve
> this.

I think P3P is able to accommodate this. P3P does not distinguish=20
between roles, but you can have multiple statements in a policy. So one=20
statement would cover all data that is collected concerning the client=20
information and the other would cover the information collection from=20
broker. You can indicate the role in question in a description in a=20
<consequence> - Element.=20

Be sure to indicate the retention of the data elements, especially for=20
the broker information as this information is not retained. But it is=20
collected at some point in time, so the collection has to be declared,=20
but the retentions is short or absent.=20

In your case it might even make sense to go down to the single=20
data-items of the base data schema and not use categories at all. This=20
way you have a sharp distinction. In fact, the statement clusters some=20
vocabulary with some data items.=20

Best,=20

Rigo

--nextPart4045722.eqMI18RakD
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQBDN/PACRlGO2Cxp/0RAvfnAJ9Gv7A66CiSnA6wx9B7LdF4/QME7wCcDVrP
2mffo/Ae4WfPSzjVibSyojA=
=dRwg
-----END PGP SIGNATURE-----

--nextPart4045722.eqMI18RakD--