technical content. 7/7/2015 5.0 Major Updated for new product version. 11/2/2015 5.0 None No changes to the meaning, language, or formatting of the technical content. 3/22/2016 5.0 None No changes to the meaning, language, or formatting of the technical content. 11/2/2016 5.0 None No changes to the meaning, language, or formatting of the technical content. 3/14/2017 5.0 None No changes to the meaning, language, or formatting of the technical content. 10/3/2017 5.0 None No changes to the meaning, language, or formatting of the technical content. 2/22/2018 5.0 None No changes to the meaning, language,
circumstance. All Document (All Versions) Action URIs are not checked. Collecting data elements is not performed. [W3C-P3P1.0] Section 2.4.1, Non-ambiguity The specification states: If an HTML (resp. XHTML) file includes HTML (resp. XHTML) link tag references to more than one policy reference file, P3P user agents MUST ignore all references after the first one. All Document Modes (All Versions) When more than one policy reference file is included, the last policy reference file is used. [W3C-P3P1.0] Section 3.2.1, The POLICIES element V0012: The specification states: policies = `<POLICIES xmlns="http://www.w3.org/2002/01/P3Pv1"` [xml-lang] `>` [expiry] [dataschema] *policy "</POLICIES>" All Document Modes (All Versions) When multiple policies are specified, all their statements are merged into a single policy that is then presented to the user. [W3C-P3P1.0] Section 3.2.4, The ENTITY element V0013: The specification states: entity = "<ENTITY>" *extension entitydescription *extension "</ENTITY>" entitydescription = "<DATA-GROUP>" `<DATA ref="#business.name"/>` PCDATA "</DATA>" *(`<DATA ref="#business.` string `"/>` PCDATA "</DATA>") "</DATA-GROUP>" All Document Modes (All Versions)
[W3C-P3P1.0] Section 3.3.2, The CONSEQUENCE element V0018: The specification states: <CONSEQUENCE> Consequences that can be shown to a human user to explain why the suggested practice may be valuable in a particular instance even if the user would not normally allow the practice. consequence = "<CONSEQUENCE>" PCDATA "</CONSEQUENCE>" All Document (All Versions) The CONSEQUENCE element is not supported. [W3C-P3P1.0] Section 3.3.3, The NON-IDENTIFIABLE element V0019: The specification states: If the NON-IDENTIFIABLE element is present in any STATEMENT elements in a policy, then a human readable explanation of how the data is anonymized MUST be included or linked to at the discURI. All Document Modes (All Versions) The NON-IDENTIFIABLE element is not supported. [W3C-P3P1.0] Section 3.3.4, The PURPOSE element V0020: The specification states: Each STATEMENT element that does not include a NON-IDENTIFIABLE element MUST contain a PURPOSE element that contains one or more purposes of data collection or uses of data. All Document Modes (All Versions) If the NON-IDENTIFIABLE element is missing, STATEMENT elements are not required to contain PURPOSE elements. V0021: The specification states: <PURPOSE> purposes for data processing relevant to the Web. The PURPOSE element MUST contain one or more sub-elements.
Index A 21 B 18 C 17 25 18 E Elements 12 17 14 10 10 16 24 24 16 12 11 9 18 9 9 12 8 14 11 21 8 14 15 13 15 9 18 F Forms and Related Mechanisms ( 10, 20) G 5 I 5 5 L 19 M 21 N Non-ambiguity ( 11, 20) 5 R References 5 5 22 20 T 12 14 10 24 16 12 11 9 9 8 14 11 21 14 15 13 15 19 25 U 18 22 W Wildcards in policy reference files ( 8, 19)