Re: Help me!!!!

--nextPart3080298.OPSDcYhDpc
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Am Wednesday 19 April 2006 12:09, sprach Nguyen Viet Ha:
> Is there any chance that P3P compact policy headers could be added to
> the site as part of this work? It basically involves adding a single
> HTTP header to each page as it is served out which says something like:
>
> P3P: CP=3D"BUS CUR CONo FIN IVDo ONL OUR PHY SAMo TELo"

As I said in my previous email. This is only the compact header. It can't=20
stand alone and there MUST be a full policy for conformance with the P3P=20
Specification. This can be done using the well-known location=20
($DOCUMENTROOT/w3c/p3p.xml) or by adding the location of the Policy Referen=
ce=20
=46ile to the P3P Header:

P3P: policyref=3D"http://www.w3.org/2001/05/P3P/p3p.xml" CP=3D"...."

> I attempt to verify whether a simple line of code in a header would
> solve cookie issues.

It is dangerous to do "make IE happy" policies as this might engage your=20
liability. In fact, if the real data handling practices differ from the=20
policy announced, this might be considered lying and can trigger liability.=
=20
>
> Can a compact policy statement code in a header stand alone as the
> privacy policy in an application, or it will need the other XML and text
> policies to reference to?

It needs the other info to display the policy correctly to the user. AND th=
e=20
server MUST have the XML policy to claim conformance to P3P.=20

Best,=20

=2D-=20
Rigo Wenning            W3C/ERCIM
Staff Counsel           Privacy Activity Lead
mail:[email protected]        2004, Routes des Lucioles
http://www.w3.org/      F-06902 Sophia Antipolis


--nextPart3080298.OPSDcYhDpc
Content-Type: application/pgp-signature

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

iD8DBQBERhcXCRlGO2Cxp/0RAvYFAJ4xyDu1pvPLNj4ubb7i3g9hPmVhqACdGKjW
zbOE+pxDeI/klilrpwEmHFU=
=cLLf
-----END PGP SIGNATURE-----

--nextPart3080298.OPSDcYhDpc--