Re: About compact policy error
Rigo Wenning <[email protected]> Thu, 19 Aug 2004 17:39:48 +0200
| Newsgroups | gmane.comp.web.p3p.policy |
|---|---|
| Organization | W3C |
| Message-ID | <[email protected]> |
--Boundary-02=_InMJBLCtvdP0Dtm Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Am Thursday 19 August 2004 16:56 verlautbarte yuliang liu : > Dear all: > > I am a student doing a P3P demonstration on the site > of University of Sheffield. I have > created P3P.xml reference file and policy.p3p policy > file, and both of them can be validated through > validator successfully. however, when I put them in > the same root directory (/w3c/)and validate them, the > following error message > will appearing: This concerns the compact policy transported with the P3P header. This=20 generates the errors.=20 http://www.w3.org/TR/P3P/#compact_policies > > Step 2-1: Compact Policy Validation > > Compact Policy has syntax errors or warnings. > > Error: TIA is not valid compact policy element. This is a typo as the compact token is called TAI and stands for one=20 time tailoring. > > Error: No "compact-retention" element exists (at > least, one element required). http://www.w3.org/TR/P3P/#compact_retention A statement about the amount of time that data is retained is missing in=20 the compact header (see the URI above) > > Error: No "compact-recipient" element exists (at > least, one element required). This is the same as above, see=20 http://www.w3.org/TR/P3P/#compact_recipients You will need at least one element. All those things are not in your policy, but in the compact policy.=20 Those are the tokens (only for cookies) that are transported in the P3P=20 Header of the HTTP-answer to the GET request. If you don't use a=20 cookie, you won't need the compact format at all.=20 If you have a simple setup and no cookie, I would suggest that you use=20 the well-known location (/w3c/p3p.xml) for the Policy Reference File=20 and remove the P3P Header from the Web Server configuration. 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 --Boundary-02=_InMJBLCtvdP0Dtm Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBJMnICRlGO2Cxp/0RAuJZAJ9Fgv0SuQT1fcF7jNzl158KKKWUrQCdGAyh zA3/xAa6YmBuX65/QtLTofw= =zbh4 -----END PGP SIGNATURE----- --Boundary-02=_InMJBLCtvdP0Dtm--