Errata of the P3P1.0 Specification

This version:
$Revision: 1.4 $ on $Date: 2010/07/30 10:53:20 $ GMT by $Author: massimo $

About this document

This document lists the known errata to the Platform for Privacy Preferences 1.0 (P3P1.0) Specification.

Each reported entry has the following information:

Please report errors in this document to public-p3p-spec@w3.org (publicly archived).


Identifier E1
Date 27 Jan 2003
Category Clarification
Description The P3P Specification is ambiguous about whether a Policy Reference File (PRF) can be considered valid if located through mechanism other than the three ones described in the Specification (Section 2.2)
Resolution When a user agent locates a valid policy reference file referenced using the HTTP header, HTML link tag, or XHTML link tag mechanisms, it may discover policy references for URIs other than the URI from which it was referenced. Unless conflicting references are found in a policy reference file at the well-known location, the user agent MAY cache these references for as long as they are valid and apply them to the specified URIs. The relative URIs and URI patterns specified by INCLUDE and EXCLUDE elements in policy references MUST be interpreted relative to the root of any DNS host that declared the policy reference file.

Identifier E2
Date 27 Jan 2003
Category Clarification
Description The P3P Specification is ambiguous about whether an EXPIRY element in a Policy Reference File (PRF) applies to a policy embedded in that file or not (section
Resolution An EXPIRY element in a POLICY-REFERENCES element applies only to the lifetime of the policy references, and not to the lifetime of any policies that may be embedded in POLICIES element in the same file.

Identifier E3
Date 27 Jan 2003
Category Editorial
Description The customization element (previously removed from older drafts of the P3P specification) is still listed in the DTD (Appendix 5: XML DTD Definition, and in http://www.w3.org/2002/01/P3Pv1.dtd ). 
Resolution This is a typo: the customization element does not exist (any more) in P3P. Hence, its definition should be omitted from the DTD.
Note for implementers: using the current DTD is still safe (just, presence of an extra element named customization will not be signaled as an error by DTD validation tools, so it would have to be checked with other means). The P3P XML Schema does not have this typo, so XML-Schema validation tools based on the P3P XML Schema DTD will be able to catch the eventual presence of such an extra element.

Identifier E4
Date 10 Jul 2010
Category Editorial
Description In Example 3.2 (http://www.w3.org/TR/P3P/#encoding), the DATA element on line 94 (<DATA ref="#user.login.password"/>) is self-closing, but it also contains CATEGORIES elements. Thus, the file is not valid XML.
Resolution This is a typo: it should read <DATA ref="#user.login.password"> without the closing slash. This is confirmed by the fact that there is a closing </DATA> element present.

Created by Massimo (massimo@w3.org).
Last modified: $Revision: 1.4 $ on $Date: 2010/07/30 10:53:20 $ GMT by $Author: rigo $