The Platform for Privacy Preferences 1.0 (P3P1.0) Specification

W3C Working Draft 18 October 2000

This Version:: http://www.w3.org/TR/2000/WD-P3P-20001018
Latest Public Version:: http://www.w3.org/TR/P3P
Previous Version:: http://www.w3.org/TR/2000/WD-P3P-20000915
Editor:: Massimo Marchiori, W3C/MIT/UNIVE, (massimo@w3.org)
Authors:: Lorrie Cranor, AT&T; Marc Langheinrich, ETH Zurich; Massimo Marchiori, W3C/MIT/UNIVE; Martin Presler-Marshall, IBM; Joseph Reagle, W3C/MIT

Abstract

This is the specification of the Platform for Privacy Preferences (P3P). This document, along with its normative references, includes all the specification necessary for the implementation of interoperable P3P applications.

Status of This Document

This section describes the status of this document at the time of its publication. Other documents may supersede this document. The latest status of this document series is maintained at the W3C.

This is the 18 October 2000 Last Call Working Draft of "The Platform for Privacy Preferences 1.0 (P3P1.0) Specification", for review by W3C members and other interested parties. The last call review period ends 31 October 2000. Please send review comments before the review period ends to www-p3p-public-comments@w3.org (publicly archived).

This document has been produced by the P3P Specification Working Group as part of the P3P Activity. The Working Group has agreed [members only] to its publication as a Last Call draft. Following this Last Call period, the Working Group intends to submit this specification for publication as a Candidate Recommendation.

This document is a draft document and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use W3C Working Drafts as reference material or to cite them as other than "work in progress". A revised version of this specification is expected to advance toward W3C Recommendation status after two interoperable implementations have been demonstrated.

A change log with a summary of the modifications occurred from the previous public version is included at the end of this document for convenience.

A list of current public W3C Working Drafts can be found at http://www.w3.org/TR.

Introduction
Referencing Policies
Policy Syntax and Semantics
Data Schemas
Appendices
Appendix 1: References (Normative)
Appendix 2: References (Non-normative)
Appendix 3: The P3P Base Data Schema Definition (Normative)
Appendix 4: XML Schema Definition (Normative)
Appendix 5: XML DTD Definition (Normative)
Appendix 6: ABNF Notation (Non-normative)
Appendix 7: P3P Guiding Principles (Non-normative)
Appendix 8: Working Group Contributors (Non-normative)

1. Introduction

The Platform for Privacy Preferences Project (P3P) enables Web sites to express their privacy practices in a standard format that can be retrieved automatically and interpreted easily by user agents. P3P user agents will allow users to be informed of site practices (in both machine- and human-readable formats) and to automate decision-making based on these practices when appropriate. Thus users need not read the privacy policies at every site they visit.

Although P3P provides a technical mechanism for ensuring that users can be informed about privacy policies before they release personal information, it does not provide a technical mechanism for making sure sites act according to their policies. Products implementing this specification MAY provide some assistance in that regard, but that is up to specific implementations and outside the scope of this specification. However, P3P is complementary to laws and self-regulatory programs that can provide enforcement mechanisms. In addition, P3P does not include mechanisms for transferring data or for securing personal data in transit or storage. P3P may be built into tools designed to facilitate data transfer. These tools should include appropriate security safeguards.

1.1 The P3P1.0 Specification

The P3P1.0 specification defines the syntax and semantics of P3P privacy policies, and the mechanisms for associating policies with Web resources. P3P policies consist of statements made using the P3P vocabulary for expressing privacy practices. P3P policies also reference elements of the P3P base data schema -- a standard set of data elements that all P3P user agents should be aware of. The P3P specification includes a mechanism for defining new data elements and data sets, and a simple mechanism that allows for extensions to the P3P vocabulary.

1.1.1 Goals and Capabilities of P3P 1.0

P3P version 1.0 is a protocol designed to inform Web users of the data-collection practices of Web sites. It provides a way for a Web site to encode its data-collection and data-use practices in a machine-readable XML format known as a P3P policy. The P3P specification defines:

A standard schema for data a Web site may wish to collect, known as the "P3P base data schema"
A standard set of uses, recipients, data categories, and other privacy disclosures
An XML format for expressing a privacy policy
A means of associating privacy policies with Web pages or sites, and cookies
A mechanism for transporting P3P policies over HTTP

The goal of P3P version 1.0 is twofold. First, it allows Web sites to present their data-collection practices in a standardized, machine-readable, easy-to-locate manner. Second, it enables Web users to understand what data will be collected by sites they visit, how that data will be used, and what data/uses they may "opt-out" of or "opt-in" to.

1.1.2 Example of P3P in Use

As an introduction to P3P, let us consider one common scenario that makes use of P3P. Sheila has decided to check out a store called CatalogExample, located at http://www.catalog.example.com/. Let us assume that CatalogExample has placed P3P policies on all their pages, and that Sheila is using a Web browser with P3P built in.

Sheila types the address for CatalogExample into her Web browser. Her browser is able to automatically fetch the P3P policy for that page. The policy states that the only data the site collects on its home page is the data found in standard HTTP access logs. Now Sheila's Web browser checks this policy against the preferences Sheila has given it. Is this policy acceptable to her, or should she be notified? Let's assume that Sheila has told her browser that this is acceptable. In this case, the homepage is displayed normally, with no pop-up messages appearing. Perhaps her browser displays a small icon somewhere along the edge of its window to tell her that a privacy policy was given by the site, and that it matched her preferences.

Next, Sheila clicks on a link to the site's online catalog. The catalog section of the site has some more complex software behind it. This software uses cookies to implement a "shopping cart" feature. Since more information is being gathered in this section of the web site, the Web server provides a separate P3P policy to cover this section of the site. Again, let's assume that this policy matches Sheila's preferences, so she gets no pop-up messages. Sheila continues and selects a few items she wishes to purchase. Then she proceeds to the checkout page.

The checkout page of CatalogExample requires some additional information: Sheila's name, address, credit card number, and telephone number. Another P3P policy is available that describes the data that is collected here and states that her data will be used only for completing the current transaction, her order.

Sheila's browser examines this P3P policy. Imagine that Sheila has told her browser that she wants to be warned whenever a site asks for her telephone number. In this case, the browser will pop up a message saying that this Web site is asking for her telephone number, and explaining the contents of the P3P statement. Sheila can then decide if this is acceptable to her. If it is acceptable, she can continue with her order; otherwise she can cancel the transaction.

Alternatively, Sheila could have told her browser that she wanted to be warned only if a site is asking for her telephone number and was going to give it to third parties and/or use it for uses other than completing the current transaction. In that case, she would have received no prompts from her browser at all, and she could proceed with completing her order.

Note that this scenario describes one hypothetical implementation of P3P. Other types of user interfaces are also possible.

1.1.3 P3P Policies

P3P policies use an XML encoding of the P3P vocabulary to identify the legal entity making the representation of privacy practices in a policy, enumerate the types of data or data elements collected, and explain how the data will be used. In addition, policies identify the data recipients, and make a variety of other disclosures including information about dispute resolution, and the address of a site's human-readable privacy policy. P3P policies must cover all relevant data elements and practices (but note that legal issues regarding law enforcement demands for information are not addressed by this specification; it is possible that a site that otherwise abides by its policy of not redistributing data to others may be required to do so by force of law). P3P declarations are positive, meaning that sites state what they do, rather than what they do not do. The P3P vocabulary is designed to be descriptive of a site's practices rather than simply an indicator of compliance with a particular law or code of conduct. However, user agents may be developed that can test whether a site's practices are compliant with a law or code.

P3P policies represent the practices of the site. Intermediaries such as telecommunication providers, Internet service providers, proxies and others may be privy to the exchange of data between a site and a user, but their practices may not be governed by the site's policies.

1.1.4 P3P User Agents

P3P1.0 user agents can be built into web browsers, browser plug-ins, or proxy servers. They can also be implemented as Java applets or JavaScript; or built into electronic wallets, automatic form-fillers, or other user data management tools. P3P user agents look for references to a P3P policy at a well-known location, in P3P headers in HTTP responses, and in P3P link tags embedded in HTML content. These references indicate the location of a relevant P3P policy. User agents can fetch the policy from the indicated location, parse it, and display symbols, play sounds, or generate user prompts that reflect a site's P3P privacy practices. They can also compare P3P policies with privacy preferences set by the user and take appropriate actions. P3P can perform a sort of "gate keeper" function for data transfer mechanisms such as electronic wallets and automatic form fillers. A P3P user agent integrated into one of these mechanisms would retrieve P3P policies, compare them with user's preferences, and authorize the release of data only if a) the policy is consistent with the user's preferences and b) the requested data transfer is consistent with the policy. If one of these conditions is not met, the user might be informed of the discrepancy and given an opportunity to authorize the data release themselves.

1.1.5 Implementing P3P1.0 on Servers

Web sites can implement P3P1.0 on their servers by translating their human-readable privacy policies into P3P syntax and then publishing the resulting files along with a policy reference file that indicates the parts of the site to which the policy applies. Automated tools can assist site operators in performing this translation. P3P1.0 can be implemented on existing HTTP 1.1-compliant Web servers without requiring additional or upgraded software. Servers may publish their policy reference files at a well-known location, or they may reference their P3P policy reference files in HTML content using a link tag. Alternatively, compatible servers may be configured to insert a P3P extension header into all HTTP responses that indicates the location of a site's P3P policy reference file.

Web sites have some flexibility in how they use P3P: they can opt for one P3P policy for their entire site or they can designate different policies for different parts of their sites. A P3P policy MUST cover all data generated or exchanged as part of a site's HTTP interactions with visitors. In addition, some sites may wish to write policies that cover all data an entity collects, regardless of how the data is collected.

1.1.6 Future Versions of P3P

The P3P Specification Working Group removed significant sections from earlier drafts of the P3P1.0 specification in order to facilitate rapid implementation and deployment of a P3P first step. The group envisions the release of future versions of the P3P specification after P3P1.0 is deployed. This specification would likely include improvements based on feedback from implementation and deployment experience as well as four major components that were part of the original P3P vision but not included in P3P1.0:

a mechanism to allow sites to offer a choice of P3P policies to visitors
a mechanism to allow visitors (through their user agents) to explicitly agree to a P3P policy
mechanisms to allow for non-repudiation of agreements between visitors and web sites
a mechanism to allow user agents to transfer user data to services

1.2 About this Specification

This document, along with its normative references, includes all the specification necessary for the implementation of interoperable P3P applications.

The [ABNF] notation used in this specification is specified in RFC2234 and summarized in Appendix 7. However, note that such syntax is only a grammar representative of the XML syntax: all the syntactic flexibilities of XML are also implicitly included; e.g. whitespace rules, quoting using either single quote (') or double quote ("), character escaping, comments, case sensitivity, order of attributes. Note that while XML allows flexibility in the ordering of element attributes, it does not allow flexibility in the ordering of elements. XML elements MUST be given in the order represented by the document type definitions (DTDs).

In the sections that follow a number of XML elements are introduced. Each element is given in angle brackets ("<element>"), followed by a list of valid attributes. All listed attributes are optional, except when tagged as mandatory. Note that many XML elements are shown in the BNF with separate beginning and ending tags to allow optional elements inside them. If no elements are included, then, following standard XML rules, a self-closing element may be used instead.

The following key words are used throughout the document and should be read as interoperability requirements. This specification uses words as defined in RFC2119 [KEY] for defining the significance of each particular requirement. These words are:

MUST or MUST NOT: This word or the adjective "required" means that the item is an absolute requirement of the specification.
SHOULD or SHOULD NOT: This word or the adjective "recommended" means that there may exist valid reasons in particular circumstances to ignore this item, but the full implications should be understood and the case carefully weighed before choosing a different course.
MAY: This word or the adjective "optional" means that this item is truly optional. One vendor may choose to include the item because a particular marketplace requires it or because it enhances the product, for example; another vendor may omit the same item.

1.3 Terminology

Character: Strings consist of a sequence of zero or more characters, where a character is defined as in the XML Recommendation [XML]. A single character in P3P thus corresponds to a single Unicode abstract character with a single corresponding Unicode scalar value (see [UNICODE]).
Data Element: An individual data entity, such as last name or telephone number. For interoperability, P3P1.0 specifies a base set of data elements.
Data Category: A significant attribute of a data element or data set that may be used by a trust engine to determine what type of element is under discussion, such as physical contact information. P3P1.0 specifies a set of data categories.
Data Set: A known grouping of data elements, such as "user.home.postal". The P3P1.0 base data schema specifies a number of data sets.
Equable Practice: A practice that is very similar to another in that the purpose and recipients are the same or more constrained than the original, and the other disclosures are not substantially different. For example, two sites with otherwise similar practices that follow different -- but similar -- sets of industry guidelines.
Personally Identifiable Data: Any information relating to an identified or identifiable individual.
Policy: A collection of one or more privacy statements together with information asserting the identity, URI, assurances, and dispute resolution procedures of the service covered by the policy.
Practice: The set of disclosures regarding data usage, including purpose, recipients, and other disclosures.
Preference: A rule, or set of rules, that determines what action(s) a user agent will take. A preference might be expressed as a formally defined computable statement (e.g., the [APPEL] preference exchange language).
Purpose: The reason(s) for data collection and use.
Repository: A mechanism for storing user information under the control of the user agent.
Safe Zone: Part of a Web site where the service provider performs only minimal data collection, and any data that is collected is used only in non-identifiable ways.
Service: A program that issues policies and (possibly) data requests. By this definition, a service may be a server (site), a local application, a piece of locally active code, such as an ActiveX control or Java applet, or even another user agent.
Service Provider (Data Controller, Legal Entity): The person or legal entity which offers information, products or services from a Web site, collects information, and is responsible for the representations made in a practice statement.
Statement: A P3P statement is a set of privacy practice disclosures relevant to a collection of data elements.
URI: A Uniform Resource Identifier used to identify Web resources. For definitive information on URI syntax and semantics, see [URI]. URIs that appear within XML or HTML have to be treated as specified in [CHARMODEL], section Character Encoding in URI References. This does not apply to URIs appearing in HTTP header fields; the URIs there should always be fully escaped.
User: An individual (or group of individuals acting as a single entity) on whose behalf a service is accessed and for which personal data exists.
User Agent: A program whose purpose is to mediate interactions with services on behalf of the user under the user's preferences. A user may have more than one user agent, and agents need not reside on the user's desktop, but any agent must be controlled by and act on behalf of only the user. The trust relationship between a user and her agent may be governed by constraints outside of P3P. For instance, an agent may be trusted as a part of the user's operating system or Web client, or as a part of the terms and conditions of an ISP or privacy proxy.

2. Referencing Policies

2.1 Overview and Purpose of Policy References

Locating a P3P policy is one of the first steps in the operation of the P3P protocol. Services use policy references to state what policy applies to a specific URI or set of URIs. User agents use policy references to locate the privacy policy that applies to a page, so that they can process that policy for the benefit of their user.

Policy references are used extensively as a performance optimization. P3P policies are typically several kilobytes of data, while a URI that references a privacy policy is typically less than 100 bytes. In addition to the bandwidth savings, policy references also reduce the need for computation: policies can be uniquely associated with URIs, so that a user agent need only parse and process a policy once rather than process it with every document to which the policy applies. Furthermore, by placing the information about relevant policies in a centralized location, Web site administration is simplified.

A policy reference file is used to associate P3P policies with certain regions of URI-space. The policy reference file is used to make any or all of the following statements:

The URI where a P3P policy is found
The URIs or regions of URI-space covered by this policy
The URIs or regions of URI-space not covered by this policy
The regions of URI-space for embedded content on other servers that are covered by this policy
The cookies that are or are not covered by this policy
The access methods for which this policy is applicable
The period of time for which these claims are considered to be valid

All of these statements are made in the body of the policy reference file. The last can also be made using HTTP expiration headers on the policy reference file. See section 2.3 for examples and explanations.

2.2 Locating Policy Reference Files

This section describes the mechanisms used to indicate the location of a policy reference file. Detailed syntax is also given for the supported mechanisms.

The location of the policy reference file can be indicated using one of three mechanisms. The policy reference file may be located in a predefined "well-known" location, or a document may indicate a policy reference file through an HTML LINK tag, or through an HTTP header. The policy reference file specifies the P3P policy that applies to that document, and possibly to other URIs as well. The policy reference file is an XML (see [XML]) file that can specify the policy for a single Web document, portions of a Web site, or for an entire site. The policy reference file may refer to one or more P3P policies; this allows for a single reference file to cover an entire site, even if different P3P policies apply to different portions of the site.

Note that if user agents support retrieving HTML content over HTTP, they MUST handle all three mechanisms listed above interchangeably; none of the mechanisms overrides the other. See also the requirements for non-ambiguity.

Note that policies are applied at the level of HTTP entities. An entity, retrieved by fetching a URI, has a P3P policy associated with it. A "page" from the user's perspective may be composed of multiple HTTP entities; each entity may have its own P3P policy associated with it. As a practical note, however, placing many different P3P policies on different entities on a single page may make rendering the page and informing the user of the relevant policies difficult for user agents. Additionally, services SHOULD attempt to craft their policy reference files such that a single policy reference file covers any given "page"; this will speed up the user's browsing experience.

For a user agent to process the policy that applies to a given entity, it must locate the policy reference file for that entity, fetch the policy reference file, parse the policy reference file, fetch any required P3P policies, and then parse the P3P policy or policies.

This document does not specify how P3P policies may be associated with documents retrieved by means other than HTTP. However, it does not preclude future development of mechanisms for associating P3P policies with documents retrieved over other protocols. Furthermore, additional methods of associating P3P policies with documents retrieved using HTTP may be developed in the future.

2.2.1 Well-Known Location

Web sites using P3P SHOULD place a policy reference file in a "well-known" location. To do this, a policy reference file would be placed in the site's /w3c directory, under the name p3p.xml. Thus a user agent could request this policy reference file by using a GET request for the resource /w3c/p3p.xml.

Note that sites are not required to use this mechanism; however, by using this mechanism, sites can ensure that their P3P policy will be accessable to user agents before any other resources are requested from the site. This will reduce the need for user agents to access the site using safezone practices. Additionally, if a site chooses to use this mechanism, the policy reference file located in the well-known location is not required to cover the entire site. For example, sites where not all of the content is under the control of a single organization MAY choose not to use this mechanism, or MAY choose to post a policy reference file which covers only a limited portion of the site.

Use of the well-known location for a policy reference file does not preclude use of other mechanisms for specifying a policy reference file. Portions of the site MAY use any of the other supported mechanisms to specify a policy reference file, so long as the non-ambiguity requirements are met.

For example, imagine a shopping-mall Web site run by the MallExample company. On their Web site (mall.example.com), companies offering goods or services at the mall would get a company-specific subtree of the site, perhaps in the path /companies/company-name. The MallExample company may choose to put a policy reference file in the well-known location which covers all of their site except the /companies subtree. Then if the ShoeStoreExample company has some content in /companies/shoestoreexample, they could use one of the other mechanisms to indicate the location of a policy reference file covering their portion of the mall.example.com site.

One case where using the well-known location for policy reference files is expected to be particularly useful is in the case of a site which has divided its content across several hosts. For example, consider a site which uses a different logical host for all of its Web-based applications than for its static HTML content. The other mechanisms allowed for specifying the location of a policy reference file require that some URI on the host being accessed must be fetched to locate the policy reference file. However, the well-known location mechanism has no such requirement. Consider the example of an HTML form located on www.example.com. Imagine that the action URI on that form points to server cgi.example.com. The policy reference file that covers the form is unable to make any statements about the action URI that processes the form. However, the site administrator publishes a policy reference file at http://cgi.example.com/w3c/p3p.xml that covers the action URI, thus enabling a user agent to easily locate the P3P policy that applies to the action URI before submitting the form contents.

2.2.2 HTTP Headers

Any document retrieved by HTTP MAY point to a policy reference file through the use of a new response header, the P3P header ([P3P-HEADER]). If a site is using P3P headers, it SHOULD include this on responses for all appropriate request methods, including HEAD and OPTIONS requests.

The P3P header gives one or more comma-separated directives. The syntax follows:

[1]
p3p-header

=

`P3P: ` p3p-header-field *(`,` p3p-header-field)

[2]
p3p-header-field

=

policy-ref-field | extension-field

[3]
policy-ref-field

=

`policyref="` URI `"`

[4]
extension-field

=

token [`=` (token | quoted-string) ]

Here, URI is defined as per RFC 2396 [URI], token and quoted-string are defined by [HTTP1.1].

In keeping with the rules for other HTTP headers, the P3P portion of this header may be written in any case.

The policyref directive gives a URI which specifies the location of the policy reference file which will state the P3P policy covering the document that pointed to the reference file, and possibly others as well. Note that fetching the URI given in the policyref directive MAY result in a 300-class HTTP return code (redirection); user agents MUST interpret those redirects with normal HTTP semantics. Services should note, of course, that use of redirects will increase the time required for user agents to find and interpret their policies. The policyref URI MUST NOT be used for any other purpose beyond identifying and referencing P3P policies.

User-agents which find unrecognized directives (in the extension-fields) MUST ignore the unrecognized directives. This is to allow easier deployment of future versions of P3P.

Example 2.1:

1. Client makes a GET request.

GET /index.html HTTP/1.1
Host: catalog.example.com
Accept: */*
Accept-Language: de, en
User-Agent: WonderBrowser/5.2 (RT-11)

2. Server returns content and the P3P header pointing to the policy of the page.

HTTP/1.1 200 OK
P3P: policyref="http://catalog.example.com/P3P/PolicyReferences.xml"
Content-Type: text/html
Content-Length: 7413
Server: CC-Galaxy/1.3.18

2.2.3 The HTML `link` Tag

Servers MAY serve HTML content with embedded link tags that indicate the location of the relevant P3P policy reference file. This use of P3P does not require any change in the server behavior.

The link tag encodes the information that could be expressed using the P3P header. The link tag takes the following form:

[5]
p3p-link-tag

=

`<link rel="P3Pv1" href="` URI `">`

Here, URI is defined as per RFC 2396 [URI].

In order to illustrate with an example the use of the link tag, we consider the policy reference expressed in Example 2.1 using HTTP headers. That example can be equivalently expressed using the link tag with the following piece of HTML:

<link rel="P3Pv1"
    href="http://catalog.example.com/P3P/PolicyReferences.xml">

Finally, note that since the p3p-link-tag is embedded in an HTML document, its character encoding will be the same as that of the HTML document. In contrast to P3P policy and policy reference documents (see section 2.3 and section 3 below), the p3p-link-tag need not be encoded using [UTF-8].

2.3 Policy Reference File Syntax and Semantics

This section explains the contents of policy reference files in detail.

2.3.1 Example Policy Reference File

Consider the case of a Web site wishing to make the following statements:

P3P policy /P3P/Policy1.xml applies to the entire site, except the subtrees /catalog, /cgi-bin, and /servlet.
P3P policy /P3P/Policy2.xml applies to all documents in the /catalog directory (and its subdirectories).
P3P policy /P3P/Policy3.xml applies to all documents in the /cgi-bin and /servlet directories (and their subdirectories), except for /servlet/unknown.
No statement is made about what P3P policy applies to /servlet/unknown.
These statements are valid for 2 days.

These statements could be represented by the following piece of XML:

Example 2.2:

<META xmlns="http://www.w3.org/2000/10/18/P3Pv1">
 <POLICY-REFERENCES>
  <EXPIRY max-age="172800"/>

    <POLICY-REF about="/P3P/Policy1.xml">
      <INCLUDE>/*</INCLUDE>
      <EXCLUDE>/catalog/*</EXCLUDE>
      <EXCLUDE>/cgi-bin/*</EXCLUDE>
      <EXCLUDE>/servlet/*</EXCLUDE>
    </POLICY-REF>

    <POLICY-REF about="/P3P/Policy2.xml">
      <INCLUDE>/catalog/*</INCLUDE>
    </POLICY-REF>

    <POLICY-REF about="/P3P/Policy3.xml">
      <INCLUDE>/cgi-bin/*</INCLUDE>
      <INCLUDE>/servlet/*</INCLUDE>
      <EXCLUDE>/servlet/unknown</EXCLUDE>
    </POLICY-REF>

 </POLICY-REFERENCES>
</META>

This example includes a relative expiry time in the document. The expiry time could also be expressed through HTTP headers:

The origin server serving this page could return a Cache-Control: max-age=172800 header with this file, or
The origin server could generate an Expires header dated 2 days past the Date header in the response.

2.3.2 Policy Reference File Definition

This section defines the syntax and semantics of P3P policy reference files. All policies MUST be encoded using [UTF-8]. P3P servers MUST encode their policy references using this syntax. P3P user agents MUST be able to parse this syntax.

One significant point to make about the syntax of policy reference files is that the syntax defined here does not have an extension mechanism. The syntax for P3P policies has a powerful extension mechanism, but that mechanism is not supported for policy reference files.

2.3.2.1 Policy reference file processing

2.3.2.1.1 Significance of order

A policy reference file may contain multiple POLICY-REF elements. If it does contain more than one element, they MUST be processed by user agents in the order given in the file. When a user agent is attempting to determine what policy applies to a given URI, it MUST use the first POLICY-REF element in the policy reference file which applies to that URI.

2.3.2.1.2 Wildcards in policy reference files

Policy reference files make statements about what policy applies to a given URI. Policy reference files support a simple wildcard character to allow making statements about regions of URI-space. The character asterix ("*") is used to represent a sequence of 0 or more of any character. No other special characters (such are those found in regular expressions) are supported. Note that since the asterix is also a legal character in URIs ([URI]), some special conventions have to be followed when encoding such "extended URIs" in a policy reference file:

URIs represented in policy-ref files MUST be properly escaped, as in [URI].
P3P User-Agents MUST escape any characters which should be escaped, as according to [URI], before attempting to match a URI for a policy.
P3P User-Agents MUST un-escape any escaped sequences which resolve to URI-legal characters, according to [URI], before attempting to match a URI for a policy, EXCEPT
Literal '*'s in URIs MUST be escaped by P3P User-Agents before attempting to match a URI for a policy.
User-agents MUST ignore any URI pattern that do not conform to [URI]

The wildcard character MAY be used in the INCLUDE and EXCLUDE elements, in the EMBEDDED-INCLUDE and EMBEDDED-EXCLUDE elements, and in the COOKIE-INCLUDE and COOKIE-EXCLUDE elements.

2.3.2.2 The `META` and `POLICY-REFERENCES` elements

The META element contains a complete policy reference file. Exactly one POLICY-REFERENCES element MUST be in a policy reference file. Optionally, one POLICIES element can follow. Additionally, other XML markup MAY follow the POLICY-REFERENCES (or POLICIES, if present) element, although that markup MUST be ignored by any P3P1.0 user agent.

<POLICY-REFERENCES>: This element MAY contain one or more POLICY-REF (policy reference) elements. It MAY also contain one EXPIRY element (indicating their expiration time), and also some in-line policies.

[6]
prf

=

`<META xmlns="http://www.w3.org/2000/10/18/P3Pv1">` policyrefs [policies] PCDATA "</META>"

[7]
policyrefs

=

"<POLICY-REFERENCES>" [expiry] *policyref "</POLICY-REFERENCES>"

Here PCDATA is defined in [XML].

2.3.2.3 Policy reference file lifetimes and the `EXPIRY` element

2.3.2.3.1 Motivation and mechanism

It is desirable for servers to inform user agents how long they can use the claims made in a policy reference file. By enabling clients to cache the contents of a policy reference file, it reduces the time required to process the privacy policy associated with a Web page. This also reduces load on the network. In addition, clients that don't have a valid policy reference file for a URI will need to use "safe zone" practices for their requests. If clients have policy reference files which they know are still valid, then they can make more informed decisions on how to proceed.

The lifetime of a policy reference file tells user agents how long they can rely on the claims made in the reference file. For example, if a policy reference file has a lifetime of 3 days, then a user agent need not reload that file for 3 days, and can assume that the references made in that reference file are good for 3 days. All of the policy references made in a single policy reference file will receive the same lifetime. The only way to specify different lifetimes for P3P policies is to use separate policy reference files for each policy.

When picking a lifetime for policies and policy reference files, sites need to pick a lifetime which balances two competing concerns. One concern is that the lifetime ought to be long enough to allow user agents to receive significant benefits from caching. The other concern is that the site would like to be able to change their policy without waiting for an extremely long lifetime to expire. It is expected that lifetimes in the range of 1-7 days would be a reasonable balance between these two competing desires. Sites also need to remember the policy update requirements when updating their policies.

When a policy reference file has expired, the information in the policy reference file MUST NOT be used by a user-agent until that user-agent has successfully revalidated the policy reference file, or has fetched a new copy of the policy reference file.

As stated in section 2.3, there are two mechanisms for specifying the lifetime of policy reference files. Two different mechanisms are provided to give sites additional flexibility in deploying policy reference files. A policy reference file MAY contain an EXPIRY element, which gives the lifetime for the file. If there is no EXPIRY element in the policy reference file, then the HTTP cache control headers associated with the policy reference file give the lifetime of the policy reference file.

Note that while user agents are not obligated to refetch policy reference files or policy files that have not expired, they MAY choose to revalidate those files before their expiry period has passed, in order to reduce the need for using "safe zone" practices.

2.3.2.3.2 The `EXPIRY` element

The EXPIRY element can be used in a policy reference file and/or in a P3P policy to state how long the policy reference file (or policy) remains valid. The expiry is given as either an absolute expiry time, or a relative expiry time. An absolute expiry time is a time, given in GMT, until which the policy reference file (or policy) is valid. A relative expiry time gives a number of seconds for which the policy reference file (or policy) is valid. This expiry time is relative to the time the response was sent from the origin server (as stated by the Date: header in the response).

[8]
expiry

=

"<EXPIRY" (absdate|reldate) "/>"

[9]
absdate

=

`date="` HTTP-date `"`

[10]
reldate

=

`max-age="` delta-seconds `"`

Here, HTTP-date is defined in section 3.3.1 of [HTTP1.1], and delta-seconds is defined in section 3.3.2 of [HTTP1.1].

2.3.2.3.3 Use of HTTP headers

When a policy reference file contains no EXPIRY element, the HTTP headers served with the policy reference file determine its lifetime. However, user agents MUST NOT use heuristic expiration based on last-modified to compute a lifetime for the reference file. When using the HTTP headers to determine the lifetime of a policy reference file, user agents MUST compute that lifetime for the policy reference file based on Expires, Cache-Control, or Pragma headers served with the file if they are available. The semantics of these headers are defined by [HTTP]. If none of these headers is available, the lifetime MUST be set to 24 hours from the time the document was sent from the origin server. Origin servers SHOULD use either the EXPIRY element or one of the HTTP headers listed above to give an explicit lifetime for their policy reference files.

The possible presence of caches in the network and the heuristic expiration mechanism in HTTP considerably complicates lifetime considerations. Consider the case of policy reference files that have no explicit cache lifetime defined by the origin server (i.e., none of the headers listed above are included in the response). A network cache will, in all likelihood, compute a cache lifetime for the policy reference file based on its last-modified date; the resulting cache lifetime could be significantly longer that 24 hours. If a cache implements HTTP 1.0, then when a user agent then retrieves this policy reference file, the user agent has no way to know how long the reference file may have been in the cache. It would then be impossible for the user agent to determine if the reference file's lifetime has already expired, or when it will expire. HTTP 1.1 caches improve the situation somewhat, as the HTTP protocol states that HTTP 1.1-compliant caches MUST send an Age header when serving a request from their cache. However, even this is not sufficient; the cache could return a file with an age exceeding the 24-hour lifetime defined here, resulting in a useless policy reference file. To avoid these problems, user agents MUST insure that they load a fresh copy of the policy reference file when it is fetched. Thus, a user agent MUST include either a Pragma: no-cache or a Cache-Control: no-cache request-header when fetching a policy reference file. The former is suggested for compatibility with HTTP 1.0 caches.

Note that it is impossible for a client to accurately predict the amount of latency that may affect an HTTP request. Thus, if the policy reference file covering a request is going to expire soon, clients MAY wish to consider warning their users and/or revalidating the policy reference file before continuing with the request.

2.3.2.3.4 Error handling for policy reference file lifetimes

The following situations have their semantics specifically defined:

When a policy reference file contains an EXPIRY element, and it is served with one of the HTTP headers listed in the previous subsection 2.3.2.3.3, the EXPIRY header takes precedence for determining the lifetime of the policy reference file.
An absolute expiry date in the past renders the policy reference file stale. This covers a date in an Expires: HTTP header as well as one in an expires-date attribute of an EXPIRY element.
An invalid or malformed expiry date, whether relative or absolute, should be considered to be in the past. This would result in the policy reference file being stale.
When a policy reference file contains more than one EXPIRY element, the first one takes precedence for determining the lfetime of the policy reference file.

2.3.2.4 The `POLICY-REF` element

A policy reference file may refer to multiple P3P policies, specifying information about each. The POLICY-REF element describes attributes of a single P3P policy. Elements within the POLICY-REF element give the location of the policy and specify the areas of URI-space that each policy covers.

POLICY-REF: contains information about a single P3P policy.
about (mandatory attribute): URI of the P3P policy. If this is a relative URI, it is interpreted relative to the URI of the policy reference file. Note that this MAY be a reference to a policy included in this policy reference file. To do this, the policy URI is given by #policy-name, where policy-name is the value given on the name attribute of a policy in this policy reference file.

[11]	policy-ref	=	`<POLICY-REF about="` URI `">` include exclude cookie-include cookie-exclude embedded-include embedded-exclude *method-element `</POLICY-REF>`
Here, `URI` is defined as per RFC 2396 [URI].

2.3.2.5 The `INCLUDE` and `EXCLUDE` elements

Each INCLUDE or EXCLUDE element specifies one local URI or set of local URIs. A set of URIs is specified if the wildcard character '*' is used in the URI-pattern. These elements are used to specify the portion of the Web site that is covered by the policy referenced by the enclosing POLICY-REF element.

When INCLUDE (and optionally, EXCLUDE) elements are present in a POLICY-REF element, it means that the policy specified in the about attribute of the POLICY-REF element applies to all the URIs at the requested host corresponding to the local-URI(s) matched by any of the INCLUDEs, but not matched by an EXCLUDE element.

If a METHOD element (section 2.3.2.8) specifies one or more methods for an enclosing policy reference, it follows that all methods not mentioned are consequently not covered by this policy. In the case that this is the only policy reference for a given URI prefix, user agents MUST assume that NO policy is in effect for all methods NOT mentioned in the policy reference file.

It is legal, but pointless, to supply an EXCLUDE element without any INCLUDE elements; in that case, the EXCLUDE element MUST be ignored by user agents.

A policy reference file can only cover URIs on the same host as the reference file. Therefore, the INCLUDE and EXCLUDE elements MUST specify only local URI prefixes; they MUST NOT refer to URIs on other hosts. This requirement does NOT apply to the location of the P3P policy file (the about attribute on the POLICY-REF element).

Note that the set of URIs specified with INCLUDE and EXCLUDE does not include cookies that might be triggered when requesting one of such URIs: in order to associate policies with cookies, the COOKIE-INCLUDE and COOKIE-EXCLUDE elements are needed.

[12]
include

=

"<INCLUDE>" relativeURI "</INCLUDE>"

[13]
exclude

=

"<EXCLUDE>" relativeURI "</EXCLUDE>"

Here, relativeURI is defined as per RFC 2396 [URI], with the addition that the '*' character is to be treated as a wildcard, as defined in section 2.3.2.1.2.

2.3.2.6 The `EMBEDDED-INCLUDE` and`EMBEDDED-EXCLUDE` elements

HTML pages often contain links to other resources that are embedded directly in the page, such as images, sounds, layers or frames. Thus, in order to render the page, the user agents may need to make additional requests that might or might not be covered by the policy in effect for the page that is currently laid out. Because embedded content could be served by a third-party server (and INCLUDE and EXCLUDE MUST specify only local URI prefixes) additional elements are needed to associate a policy with that content.

Each EMBEDDED-INCLUDE or EMBEDDED-EXCLUDE element specifies a third-party absolute URI (see [URI]). These prefixes are used to specify (similarly to INCLUDE and EXCLUDE) the third-party servers who are covered by the policy specified by the about attribute when their content is embedded within the documents on the Web site where the policy reference file resides. However, to limit the scope of when an absolute URI should be considered "embedded", we make use of the HTTP Referer header:

When EMBEDDED-INCLUDE (and optionally, EMBEDDED-EXCLUDE) elements are present in a POLICY-REF element, it means that the policy specified in the about attribute of the POLICY-REF element applies to all the URI(s) matched by any EMBEDDED-INCLUDE's, and not matched by an EMBEDDED-EXCLUDE element, when those URIs are normally requested with a Referer header that contains a URI from a resource which is covered by the policy reference file containing the embedded URI.

This means that the policy will be applied to objects embedded or linked to, but not objects which are embedded in them. Proxy implementations will be able to examine the Referer header generated by the HTTP User-Agent, locate the policy applying to the Referer object, and then determine if an embedded content policy is in effect.

P3P user agents are not required to send Referer headers to web sites; indeed, depending on user preferences and safezone issues, a user agent may discard the Referer after using it to determine whether an EMBEDDED-INCLUDE policy applies.

User agents SHOULD interpret EMBEDDED-INCLUDE and EMBEDDED-EXCLUDE elements in a policy reference file to determine the policy that applies to third-party content. Such policy association SHOULD NOT be used for content that will generate a redirect.

Example 2.5 states that /P3P/Policy1.xml applies to all documents in the subtree /docs/ plus the file /other/index.html. In addition, that policy applies to embedded documents requested from the /ads/ directory -- but not the /network/ subdirectory -- on hosts in the adserver.example.com domain.

Example 2.5:

<META xmlns="http://www.w3.org/2000/10/18/P3Pv1">
 <POLICY-REFERENCES>
    <POLICY-REF about="/P3P/Policy1.xml">
      <INCLUDE>/docs/*</INCLUDE>
      <INCLUDE>/other/index.html</INCLUDE>
      <EMBEDDED-INCLUDE>http://*.adserver.example.com/ads/*</EMBEDDED-INCLUDE>
      <EMBEDDED-EXCLUDE>http://*.adserver.example.com/ads/network/*</EMBEDDED-EXCLUDE>
    </POLICY-REF>
 </POLICY-REFERENCES>
</META>

The syntax for the EMBEDDED-INCLUDE and EMBEDDED-EXCLUDE elements is:

[16]
embedded-include

=

"<EMBEDDED-INCLUDE>" absoluteURI "</EMBEDDED-INCLUDE>"

[17]
embedded-exclude

=

"<EMBEDDED-EXCLUDE>" absoluteURI "</EMBEDDED-EXCLUDE>"

Here, absoluteURI is defined as per RFC 2396 [URI], with the addition that the '*' character is to be treated as a wildcard, as defined in section 2.3.2.1.2

Note that sites MAY choose not to specify a policy for some or all of their embedded content. In those cases P3P user agents SHOULD attempt to obtain a P3P policy directly from the site hosting the embedded content.

Also note that, just like in the case of INCLUDE and EXCLUDE, the set of URIs specified with EMBEDDED-INCLUDE and EMBEDDED-EXCLUDE does not include cookies that might be triggered when requesting one of such URIs: in order to associate policies with cookies, the COOKIE-INCLUDE and COOKIE-EXCLUDE elements are needed.

2.3.2.7 The `COOKIE-INCLUDE` and `COOKIE-EXCLUDE` elements

HTML pages often contain instances of state management mechanisms, also known as cookies. Because cookies may have a scope which is distinct from the scope of the page, user agents may need to make additional requests that might or might not be covered by the policy in effect for the page that is currently laid out. The COOKIE-INCLUDE and COOKIE-EXCLUDE elements are used to attach policies to cookies.

For the purpose of this specification, state management mechanisms use either SET-COOKIE or SET-COOKIE2 headers, and cookie-namespace is defined as the value of the Name, Domain and Path attributes, specified in [COOKIES] and [STATE].

Each COOKIE-INCLUDE or COOKIE-EXCLUDE element specifies a cookie-namespace, consisting of the Name, Domain and Path attributes, any or all of which may be wildcarded. These prefixes are used to specify (similarly to INCLUDE and EXCLUDE) the cookie-namespaces which are covered by the policy specified by the about attribute when the cookies are set from the documents on the Web site where the policy reference file resides.

When COOKIE-INCLUDE (and optionally, COOKIE-EXCLUDE) elements are present in a POLICY-REF element, it means that the policy specified in the about attribute of the POLICY-REF element applies to every cookie whose cookie-namespace is matched by any COOKIE-INCLUDE's, and not matched by a COOKIE-EXCLUDE element.

A site cannot declare policies for cookies unless the cookies are on its own site, or they are set from elements that are embedded (in the sense of Section 2.3.2.6) on its own site. User agents SHOULD accordingly interpret COOKIE-INCLUDE and COOKIE-EXCLUDE elements in a policy reference file to determine the policy that applies to cookies.

The policy which applies to a cookie applies until the policy expires. If the policy associated with a cookie has expired, or if the user agent preferences are changed, then the user agent SHOULD reevaluate the cookie policy before sending the cookie.

Example 2.3 states that /P3P/Policy1.xml applies to all cookies.

Example 2.3:

<META xmlns="http://www.w3.org/2000/10/18/P3Pv1">
 <POLICY-REFERENCES>
    <POLICY-REF about="/P3P/Policy1.xml">
       <COOKIE-INCLUDE>*..*/*</COOKIE-INCLUDE>
    </POLICY-REF>
 </POLICY-REFERENCES>
</META>

Example 2.4 states that /P3P/Policy1.xml applies to all cookies, except cookies with the cookie name value of "obnoxious-cookie", a domain value of ".example.com", and a path value of "/", and that /P3P/Policy2.xml applies to all cookies with the cookie name of "obnoxious-cookie", a domain value of ".example.com", and a path value of "/".

Example 2.4:

<META xmlns="http://www.w3.org/2000/10/18/P3Pv1">
 <POLICY-REFERENCES>
    <POLICY-REF about="/P3P/Policy1.xml">
       <COOKIE-INCLUDE>*</COOKIE-INCLUDE>
       <COOKIE-EXCLUDE>obnoxious-cookie..example.com/</COOKIE-EXCLUDE>
    </POLICY-REF>
    <POLICY-REF about="/P3P/Policy2.xml">
       <COOKIE-INCLUDE>obnoxious-cookie..example.com/<COOKIE-INCLUDE>
    </POLICY-REF>
 </POLICY-REFERENCES>
</META>

[14]
cookie-include

=

"<COOKIE-INCLUDE>" NAME "." Domain Path "</COOKIE-INCLUDE>"

[15]
cookie-exclude

=

"<COOKIE-EXCLUDE>" NAME "." Domain Path "</COOKIE-EXCLUDE>"

Here, NAME, Domain and Path are defined as per RFC 2965 [STATE], with the addition that the '*' character is to be treated as a wildcard, as defined in section 2.3.2.1.2.

Note that, conforming to [STATE], if an explicitly specified Domain value does not start with a dot, the user agent MUST supply a leading dot for it. Hence, the separation between a NAME and a Domain inside a COOKIE-INCLUDE (or COOKIE-EXCLUDE) element can be easily identified by finding the rightmost occurrence of a double dot ".." in the element content. Also, since every Path begins with the "/" symbol, which cannot occur in a Domain, the separation between a Domain and a Path can be similarly identified by finding the first occurrence of "/" after the rightmost double dot.

2.3.2.8 The `METHOD` element

By default, a policy reference applies to the stated URIs regardless of the method used to access the resource. However, a Web site may wish to define different P3P policies depending on the method to be applied to a resource. For example, a site may wish to collect more data from users when they are performing PUT or DELETE methods than when performing GET methods.

The METHOD element in a policy reference file is used to state that the enclosing policy reference only applies when the specified methods are used to access the referenced resources. The METHOD element may be repeated to indicate multiple applicable methods. If the METHOD element is not present in a POLICY-REF element, then that POLICY-REF element covers the resources indicated regardless of the method used to access them.

So, to state that /P3P/Policy1.xml applies to all documents in the subtree /docs/ for GET and HEAD methods, while /P3P/Policy2.xml applies for PUT and DELETE methods, the following policy reference would be written:

Example 2.6:

<META xmlns="http://www.w3.org/2000/10/18/P3Pv1">
 <POLICY-REFERENCES>
    <POLICY-REF about="/P3P/Policy1.xml">
      <INCLUDE>/docs/*</INCLUDE>
      <METHOD>GET</METHOD>
      <METHOD>HEAD</METHOD>
    </POLICY-REF>
    <POLICY-REF about="/P3P/Policy2.xml">
      <INCLUDE>/docs/*</INCLUDE>
      <METHOD>PUT</METHOD>
      <METHOD>DELETE</METHOD>
    </POLICY-REF>
 </POLICY-REFERENCES>
</META>

Note that HTTP requires the same behavior for GET and HEAD requests, thus it is inappropriate to specify different P3P policies for these methods. The syntax for the METHOD element is:

[18]
method-element

=

`<METHOD>` Method `</METHOD>`

Here, Method is defined in the section 5.1.1 of [HTTP1.1].

2.3.3 Applying a Policy to a URI

A policy reference file specifies the policy which applies to a given URI. The meaning of this is that the indicated policy describes all effects of performing any of the methods listed in the policy reference file against the given URI.

There is a general rule which describes what it means for a P3P policy to cover a URI: the referenced policy MUST cover actions that the user's client software is expected to perform as a result of requesting that URI. Obviously, the policy must describe all data collection performed by site as a result of processing the request for the URI. Thus, if a given URI is covered for terms of GET requests, then the policy given by the policy reference file MUST describe all data collection performed by the site when that URI is fetched. Likewise, if a URI is covered for POST requests, then any data collection that occurs as a result of posting a form or other content to that URI MUST be described by the policy.

The concept of "actions that the client software is expected to perform" includes the setting of client-side cookies or other state-management mechanisms invoked by the response. If executable code is returned when a URI is requested, then the P3P policy covering that URI MUST cover certain actions which will occur when that code is executed. The covered actions are any actions which could take place without the user explicitly invoking them. If explicit user action causes data to be collected, then the P3P policy covering the URI for that action would disclose that data collection.

Some specific examples:

Fetching a URI returns an HTML page which contains a form, and the form contents are sent to a second URI when the user clicks a "Submit" button. The P3P policy covering the second URI MUST disclose all data collected by the form. The P3P policy covering the first URI (the URI the form was loaded from) MAY or MAY NOT disclose any of the data that will be collected on the form.
An HTML page includes JavaScript code which tracks how long the page is displayed and whether the user moved the mouse over a certain object on the page; when the page is unloaded, the JavaScript code sends that information to the server where the HTML page originated. The activity of the JavaScript code MUST be covered by the P3P policy of the HTML page. The reasoning is that this activity takes place without the user's knowledge or consent, and it occurs automatically as a result of loading the page.
A response is an installable image for an electronic mail program. In order to use the e-mail program, the user must run an installation program, start the e-mail program, and use its facilities. The P3P policy covering URI from where the e-mail program was downloaded is not required to make a statement about the data which could be collected by using the e-mail program. Installing and running the e-mail program is clearly outside the Web browsing experience, so it is not covered by this specification. A separate protocol could be designed to allow downloaded applications to present a P3P policy, but this is outside the scope of this specification.
An HTML page containing a form includes a reference to an executable which provides a custom client-side control. The data in the control is submitted to a site when the form is submitted. In this case, the URI for the HTML page and the URI for the custom control is not required to make a statement about the data the custom control represents. However, the URI to which the form contents are posted MUST cover the data from the custom control, just as it would cover any other data collected by processing the form. This behavior is similar to the way HTML forms are handled when they use only standard HTML controls: the control itself collects no data, and the data is collected when the form is posted. Note that this example assumes that the form is only posted when the user actively presses a "submit" or similar button. If the form were posted automatically (for example, by some JavaScript code in the page), then this example would be similar to example #2, and the data collected by the form MUST be described in the P3P policy which covers the HTML form.
Requests to a URI are redirected to a third party. If the first party embeds previously collected personal data in the query string or other part of the redirect URI, the privacy policy for the first party's URI MUST describe the types of data transmitted and include the third party as a recipient.

2.3.4 Forms and Related Mechanisms

Forms deserve special consideration, as they often link to CGI scripts or other server-side applications in their action URIs. It is often the case that those action URIs are covered by a different policy than the form itself.

If a user agent is unable to find a matching prefix for a given action URI in the policy reference file that was referenced from the page, it SHOULD assume that no policy is in effect. Under these circumstances, user agents SHOULD check the well-known location on the host of the action URI to attempt to find a policy reference file that covers the action URI. If this does not provide a P3P policy to cover the action URI, then a user agent MAY try to issue a HEAD request to an action URI before actually submitting any data in order to find the policy in effect. Services SHOULD ensure that server-side applications can properly respond to such HEAD requests and return the corresponding policy reference link in the headers. In case the underlying application does not understand the HEAD request and no policy has been predeclared for the action URI in question, user agents MUST assume that no policy is in effect and SHOULD inform the user about this or take the corresponding actions according to the user's preferences.

Note that services might want to make use of the <METHOD> element in order to declare policies for server-side applications that only cover a subset of supported methods, e.g., POST or GET. Under such circumstances, it is acceptable that the application in question only supports the methods given in the policy reference file (i.e., HEAD requests need not be supported). User agents SHOULD NOT attempt to issue a HEAD request to an action URI if the relevant methods specified in the form's method attribute have been properly predeclared in the page's policy reference file.

In some cases, different data is collected at the same action URI depending on some selection in the form. For example, a search service might offer to both search for people (by name and/or email) and (arbitrary) images. Using a set of radio buttons on the form, a single server-side application located at one and the same action URI handles both cases and collects the required information necessary for the search. If a service wants to predeclare the data collection practices of the server-side application it MAY declare all of the data collection practices in a single policy file (using a <INCLUDE> declaration matching the action URI). In this case, user agents MUST assume that all data elements are collected under every circumstance. This solution offers the convenience of a single policy but might not properly reflect the fact that only parts of the listed data elements are collected at a time. Services SHOULD make sure that a simple HEAD request to the action URI (i.e., without any arguments, especially without the value of the selected radio button) will return a policy that covers all cases.

Note that if a form is handled through use of the GET method, then the action URI reflects the choice of form elements selected by the user. In some cases, it will be possible to make use of the wildcard syntax allowed in policy reference files to specify different policies for different uses of the same form action-handler URI. Therefore, user agents MUST include the query-string portion of URIs when making comparisons with INCLUDE and EXCLUDE elements in policy reference files.

2.4 Additional Requirements

2.4.1 Non-ambiguity

A very important rule of policy references is that of non-ambiguity: For each resource at a website there MUST be at most one policy active at any given time. Thus two non-expired policy reference files on a given site MUST NOT declare two or more different policy URIs for the same resource.

If a policy reference file at the well-known location declares a non-expired policy for a given URI, this policy applies, regardless of any conflicting policy reference files referenced through HTTP headers or HTML link tags.

2.4.2 Multiple Languages

Multiple language versions (translations) of the same policy can be offered by the server using the HTTP "Content-Language" header to properly indicate that a particular language has been used for the policy. This is useful so that human-readable fields such as entity and consequence can be presented in multiple languages. The same mechanism can also be used to offer multiple language versions for data schemas.

Whenever Content-Language is used to distinguish policies at the same URI that are offered in multiple languages, the policies MUST have the same meaning in each language. Two policies (or two data schemas) are taken to be identical if

All formal (not natural language) protocol elements are semantically identical (i.e., attribute order does not matter, the presence or absence of a default value does not matter, but attribute values matter)
All natural language protocol elements correspond one-to-one, and for each correspondence, one is a careful translation of the other.

Due to the use of the Accept-Language mechanism, implementors should take note that user agents may see different language versions of a policy or policy reference file despite sending the same Accept-Language request header if a new language version of a policy or data schema has been added.

2.4.3 The "Safe Zone"

Every P3P-enabled user agent and service SHOULD ensure that all the relevant communications that take place as part of fetching a P3P policy are part of a special "safe zone" in which minimal data collection takes place and any data that is collected is used only in non-identifiable ways. In particular, requests to the well-known location for policy reference files SHOULD be covered by these "safe zone" practices.

To support this safe zone, P3P user agents SHOULD suppress the transmission of data unnecessary for the purpose of finding a site's policy until the policy has been fetched. Thus user agents SHOULD NOT send the HTTP Referer header or accept cookies while requesting a P3P policy. User agents MAY also wish to refrain from sending user agent information or cookies accepted in a previous session while requesting a P3P policy. User agent implementors need to be aware that there is a privacy trade-off with using the Accept-Language HTTP header when requesting a P3P policy. Sending the correct Accept-Language header will allow fetching the P3P policy in the user's preferred natural language (if available), but does expose a certain amount of information about the identity of the user. User agents MAY wish to allow users to decide when these headers should be sent.

Servers SHOULD NOT require the receipt of an HTTP Referer header, cookies, user agent information, or other information unnecessary for responding to the request in order to serve a policy file or policy reference file. In addition, servers SHOULD NOT use in an identifiable way any information collected while serving a policy file/policy reference file or responding to a HEAD request.

Servers MAY return a P3P header in the response headers when a P3P policy is requested. However, it is important to note that the P3P header MUST be ignored, and that the "safe zone" requirements described in this section apply instead. Returning a P3P header in such cases is permitted in consideration of the fact that administrators may find it easier to apply a P3P policy to all documents on a server, and that requiring policies to be served without a P3P header may result in extra work for site administrators.

Note that the safe zone requirements do not say that sites cannot keep identifiable information -- only that they SHOULD NOT use in an identifiable way any information collected while serving a policy file. Tracking down the source of a denial of service attack, for example, would be a legitimate reason to use this information and ignore this recommendation.

2.4.4 Non-Discrimination of Policies

Servers SHOULD make every effort to help user agents find P3P policies. In particular, servers SHOULD place a policy reference file at the well-known location whenever possible. When the P3P HTTP header is used as an alternative, servers SHOULD:

Reference a policy in response to any request:: P3P-compliant sites SHOULD include a link to a policy reference file for a web resource whenever possible.
Support HTTP HEAD requests: P3P-compliant servers SHOULD support HEAD requests for any documents that can be retrieved with GET requests. Whenever technically feasible, servers should give a valid response to a HEAD request for documents that are normally accessed by other HTTP methods as well (such as POST).

2.4.5 Security of Policy Transport

P3P policies and references to P3P policies SHOULD NOT, in themselves, contain any sensitive information. This means that there are no additional security requirements for transporting a reference to a P3P policy beyond the requirements of the document it is associated with; so, if an HTML document would normally be served over a non-encrypted session, then the P3P protocol would not require nor recommend that the document be served over an encrypted session when a reference to a P3P policy is included with that document.

2.4.6 Policy Updates

Note that when a web site changes its P3P policy, the old policy applies to data collected when it was in effect. It is the responsibility of the site to keep records of past P3P policies and policy reference files along with the dates when they were in effect, and to apply these policies appropriately.

If a site wishes to apply a new P3P policy to previously collected data, it MUST provide appropriate notice and opportunities for users to accept the new policy that are consistent with applicable laws, industry guidelines, or other privacy-related agreements the site has made.

2.5 Example Scenarios

As an aid to sites deploying P3P, several example scenarios are presented, along with descriptions of how P3P is used on those sites.

Scenario 1: Web site basic.example.com uses a variety of images, all of which it hosts. It also includes some forms, which are all submitted directly to the site. This site can declare a single P3P policy for the entire site (or if different privacy policies apply to different parts of the site, it can declare multiple P3P policies). As long as all of the images and form action URIs are in directories covered by the site's P3P policy, user agents will automatically recognize the images and forms as covered by the site's policy.

Scenario 2: Web site busy.example.com uses a content distribution network called cdn.example.com to host its images so as to reduce the load on its servers. Thus, all of the images on the site have URIs at cdn.example.com. CDN acts as an agent to Busy in this situation, and collects no data other than log data. This log data is used only for web site and system administration in support of providing the services that Busy contracted for. Busy's privacy policy applies to the images hosted by CDN, so Busy uses the EMBEDDED-INCLUDE element in its policy reference file to indicate that its P3P policy applies to embedded content served by cdn.example.com. Optionally, cdn.example.com might also have a policy reference file that declares that the busy.example.com privacy policy applies to these images.

Scenario 3: Web site busy.example.com also has a contract with an advertising company called clickads.example.com to provide banner ads on its site. The contract allows Clickads to set cookies so as to make sure each user doesn't see a given ad more than three times. Clickads collects statistics on how many users view each ad and reports them to the companies whose products are being advertised. But these reports do not reveal information about any individual users. As was the case in Scenario 2, Busy's privacy policies applies to these ads hosted by Clickads, so Busy uses the EMBEDDED-INCLUDE element in its policy reference file to indicate that its P3P policy applies to embedded content served by clickads.example.com. Optionally, clickads.example.com might also have a policy reference file that declares that the busy.example.com privacy policy applies to these ads. The companies whose products are being advertised need not be mentioned in the Busy privacy policy because the only data they are receiving is aggregate data.

Scenario 4: Web site busy.example.com also has a contract with funchat.example.com to host a chat room for its users. When users enter the chat room they are actually leaving the Busy site. However, the chat room has the Busy logo and is actually covered by the Busy privacy policy. In this instance Funchat is acting as an agent for Busy, but -- unlike the previous examples -- their content is not embedded in the Busy site. In this case, there is no way for Busy to include Funchat in its policy reference file. However, Busy should direct Funchat to place a policy reference file on its site that points to the Busy P3P policy.

Scenario 5: Web site bigsearch.example.com has a form that allows users to type in a search query and have it performed on their choice of search engines located on other sites. When a user clicks the "submit" button, the search query is actually submitted directly to these search engines -- the action URI is not on bigsearch.example.com but rather on the search engine selected by the user. Bigsearch cannot declare the privacy policies for these search engines because form actions are not embedded content. So when a user clicks the "submit" button, their user agent should go to the appropriate search engine and check its privacy policy before posting any data. In order to make this search choice mechanism work, Bigsearch might actually have a form with an action URI on its own site, which redirects to the appropriate search engine. In this case, the user agent should check the search engine privacy policy upon receiving the redirect response.

Scenario 6: Web site bigsearch.example.com also has a form that allows users to type in a search query and have it simultaneously performed on ten different search engines. Bigsearch submits the queries, gets back the results from each search engine, removes the duplicates, and presents the results to the user. In this case, the user interacts only with Bigsearch. Thus, the only P3P policy involved is the one that covers the Bigsearch web site. However, Bigsearch must disclose that it shares the users' search queries with third parties (the search web sites), unless Bigsearch has a contract with these search engines and they act as agents to Bigsearch.

Scenario 7: Web site bigsearch.example.com also has banner advertisements provided by a company called adnetwork.example.com. Adnetwork uses cookies to develop profiles of users across many different web sites so that it can provide them with ads better suited to their interests. Because the data about the sites that users are visiting is being used for purposes other than just serving ads on the Bigsearch web site, Adnetwork cannot be considered an agent in this context. Adnetwork must create its own P3P policy and use its own policy reference file to indicate what content it applies to. In addition, Bigsearch may optionally use the EMBEDDED-INCLUDE element in its policy reference file to indicate that the Adnetwork P3P policy applies to these advertisements. Bigsearch should only do this if Adnetwork has told it what P3P policy applies to these advertisements and has agreed to notify Bigsearch if the policy reference needs to be changed.

3. Policy Syntax and Semantics

P3P policies are encoded in XML. They may also be represented using the RDF data model ([RDF]); however, an RDF representation is not included in this specification. (The working group plans to make this available as a W3C Note prior to submitting P3P as a Proposed Recommendation, together with a suitable RDF encoding of the policy reference file).

Section 3.1 begins with an example of an English language privacy policy and a corresponding P3P policy. P3P policies include general assertions that apply to the entire policy as well as specific assertions -- called statements -- that apply only to the handling of particular types of data referred to by data references. Section 3.2 describes the POLICY element and policy-level assertions. Section 3.3 describes statements and data references.

3.1 Example policies

3.1.1 English language policies

The following are two examples of English-language privacy policy to be encoded as a P3P policy. Both policies are for one example company, CatalogExample, which has different policies for those browsing their site and those actually purchasing products. Example 3.1. is provided in both English and as a more formal description using P3P element and attribute names.

Example 3.1: CatalogExample's Privacy Policy for Browsers

At CatalogExample, we care about your privacy. When you come to our site to look for an item, we will only use this information to improve our site and will not store it in an identifiable way.

CatalogExample, Inc. is a licensee of the PrivacySealExample Program. The PrivacySealExample Program ensures your privacy by holding Web site licensees to high privacy standards and confirming with independent auditors that these information practices are being followed.

Questions regarding this statement should be directed to:

CatalogExample

    4000 Lincoln Ave.

    Birmingham, MI 48009 USA

    E-mail: catalog@example.com

    Telephone 248-EXAMPLE (248-392-6753)

If we have not responded to your inquiry or your inquiry has not been satisfactorily addressed, you can contact PrivacySealExample at http://www.privacyseal.example.org. CatalogExample will correct all errors or wrongful actions arising in connection with the privacy policy.

What We Collect and Why:
When you browse through our site we collect:

the basic information about your computer and connection to make sure that we can get you the proper information and for security purposes.
aggregate information on what pages consumers access or visit to improve our site.

Data retention:
We purge every two weeks the browsing information that we collect.

Here is Example 3.1 in a more formal description, using the P3P element and attribute names [with the section of the spec that was used cited in brackets for easy reference]:

Disclosure URI: http://www.catalog.example.com/PrivacyPracticeBrowsing.html
[3.2.2 Policy]
Entity: CatalogExample
4000 Lincoln Ave.
Birmingham, MI 48009
USA
catalog@example.com
+1 (248) 392-6753
[3.2.3 Entity]
Access to Identifiable Information: None
[3.2.4 Access]
Disputes:
resolution type: independent
service: http://www.privacyseal.example.org
description: PrivacySealExample
[3.2.5 Disputes]
Remedies: we'll correct any harm done wrong
[3.2.6 Remedies]
We collect:
dynamic.clickstream
dynamic.http
[4.5 Base Data Schema]
For purpose: Web site and system administration, research and development
[3.3.4 Purpose]
Recipients: Only ourselves and our agents
[3.3.5 Recipients]
Retention: As long as appropriate for the stated purposes
[3.3.6 Retention]
(Note also that the site's human-readable privacy policy MUST mention that data is purged every two weeks, or provide a link to this information.)

Example 3.2: CatalogExample's Privacy Policy for Shoppers

At CatalogExample, we care about your privacy. We will never share your credit card number or any other financial information with any third party. With your permission only, we will share information with carefully selected marketing partners that meet either the preferences that you've specifically provided or your past purchasing habits. The more we and know about your likes and dislikes, the better we can tailor offerings to your needs.

CatalogExample is a licensee of the PrivacySealExample Program. The PrivacySealExample Program ensures your privacy by holding Web site licensees to high privacy standards and confirming with independent auditors that these information practices are being followed.

Questions regarding this statement should be directed to:

CatalogExample

    4000 Lincoln Ave.

    Birmingham, MI 48009 USA

    E-mail: catalog@example.com

    Telephone +1 248-EXAMPLE (+1 248-392-6753)

If we have not responded to your inquiry or your inquiry has not been satisfactorily addressed, you can contact PrivacySealExample - http://privacyseal.example.org/privacyseal. CatalogExample will correct all errors or wrongful actions arising in connection with the privacy policy.

When you browse through our site we collect:

the basic information about your computer and connection to make sure that we can get you the proper information and for security purposes; and
aggregate information on what pages consumers access or visit to improve our site

If you choose to purchase an item we will ask you for more information including:

your name and address so that we can have your purchase delivered to you and so we can contact you in the future;
your email address and telephone number so we can contact you;
a login and password to use to update your information at any time in the future; and
financial information to complete your purchase (you may choose to store this for future use)
optionally, you can enter other demographic information so that we can tailor services to you in the future.

Also on this page we will give you the option to choose if you would like to receive email, telephone calls or written service from CatalogExample or from our carefully selected marketing partners who maintain similar privacy practices. If you would like to receive these solicitations simply check the appropriate boxes. You can choose to stop participating at any time simply by changing your preferences.

Changing and Updating personal information
Consumers can change all of their personal account information by going to the preferences section of CatalogExample at http://catalog.example.com/preferences.html. You can change your address, telephone number, e-mail address, password as well as your privacy settings.

Cookies
CatalogExample uses cookies only to see if you have been an CatalogExample customer in the past and, if so, customize services based on your past browsing habits and purchases. We do not store any personal data in the cookie nor do we share or sell the any of the information with other parties or affiliates.

Data retention
We will keep the information about you and your purchases for as long as you remain our customer. If you do not place an order from us for one year we will remove your information from our databases.

3.1.2 XML encoding of policies

The following pieces of [XML] capture the information as expressed in the above two examples. P3P policies are statements that are properly expressed as well-formed XML. The policy syntax will be explained in more detail in the sections that follow.

XML Encoding of Example 3.1:

<POLICY xmlns="http://www.w3.org/2000/10/18/P3Pv1"
    discuri="http://www.catalog.example.com/PrivacyPracticeBrowsing.html">
 <ENTITY>
  <DATA-GROUP>
   <DATA ref="#business.name">CatalogExample</DATA>
   <DATA ref="#business.contact-info.postal.street">4000 Lincoln Ave.</DATA>
   <DATA ref="#business.contact-info.postal.city">Birmingham</DATA>
   <DATA ref="#business.contact-info.postal.stateprov">MI</DATA>
   <DATA ref="#business.contact-info.postal.postalcode">48009</DATA>
   <DATA ref="#business.contact-info.postal.country">USA</DATA>
   <DATA ref="#business.contact-info.online.email">catalog@example.com</DATA>
   <DATA ref="#business.contact-info.telecom.telephone.intcode">1</DATA>
   <DATA ref="#business.contact-info.telecom.telephone.loccode">248</DATA>
   <DATA ref="#business.contact-info.telecom.telephone.number">3926753</DATA>
  </DATA-GROUP>
 </ENTITY>
 <ACCESS><nonident/></ACCESS>
 <DISPUTES-GROUP>
  <DISPUTES resolution-type="independent"
    service="http://www.PrivacySeal.example.org"
    short-description="PrivacySeal.example.org">
   <IMG src="http://www.PrivacySeal.example.org/Logo.gif" alt="PrivacySeal's logo"/>
   <REMEDIES><correct/></REMEDIES>
  </DISPUTES>
 </DISPUTES-GROUP>
 <STATEMENT>
  <PURPOSE><admin/><develop/></PURPOSE>
  <RECIPIENT><ours/></RECIPIENT>
  <RETENTION><stated-purpose/></RETENTION> <!-- Note also that the site's human-readable
                                                privacy policy MUST mention that data 
                                                is purged every two weeks, or provide a 
                                                link to this information. -->
  <DATA-GROUP>
   <DATA ref="#dynamic.clickstream"/>
   <DATA ref="#dynamic.http"/>
  </DATA-GROUP>
 </STATEMENT>
</POLICY>

XML Encoding of Example 3.2:

<POLICY xmlns="http://www.w3.org/2000/10/18/P3Pv1"
    discuri="http://www.catalog.example.com/Privacy/PrivacyPracticeShopping.html"
    opturi="http://catalog.example.com/preferences.html">
 <ENTITY>
  <DATA-GROUP>
   <DATA ref="#business.name">CatalogExample</DATA>
   <DATA ref="#business.contact-info.postal.street">4000 Lincoln Ave.</DATA>
   <DATA ref="#business.contact-info.postal.city">Birmingham</DATA>
   <DATA ref="#business.contact-info.postal.stateprov">MI</DATA>
   <DATA ref="#business.contact-info.postal.postalcode">48009</DATA>
   <DATA ref="#business.contact-info.postal.country">USA</DATA>
   <DATA ref="#business.contact-info.online.email">catalog@example.com</DATA>
   <DATA ref="#business.contact-info.telecom.telephone.intcode">1</DATA>
   <DATA ref="#business.contact-info.telecom.telephone.loccode">248</DATA>
   <DATA ref="#business.contact-info.telecom.telephone.number">3926753</DATA>
  </DATA-GROUP>
 </ENTITY>
 <ACCESS><contact_and_other/></ACCESS>
 <DISPUTES-GROUP>
  <DISPUTES resolution-type="independent"
    service="http://www.PrivacySeal.example.org"
    short-description="PrivacySeal.example.org">
   <IMG src="http://www.PrivacySeal.example.org/Logo.gif" alt="PrivacySeal's logo"/>
   <REMEDIES><correct/></REMEDIES>
  </DISPUTES>
 </DISPUTES-GROUP>
 <STATEMENT>
  <CONSEQUENCE>
    We record some information in order to serve your request 
    and to secure and improve our web site.
  </CONSEQUENCE>
  <PURPOSE><admin/><develop/></PURPOSE>
  <RECIPIENT><ours/></RECIPIENT>
  <RETENTION><stated-purpose/></RETENTION>
  <DATA-GROUP>
   <DATA ref="#dynamic.clickstream.server"/>
   <DATA ref="#dynamic.http.useragent"/>
  </DATA-GROUP>
 </STATEMENT>
 <STATEMENT>
  <CONSEQUENCE>
    We use this information when you make a purchase.
  </CONSEQUENCE>
  <PURPOSE><current/></PURPOSE>
  <RECIPIENT><ours/></RECIPIENT>
  <RETENTION><stated-purpose/></RETENTION>
  <DATA-GROUP>
   <DATA ref="#user.name"/>
   <DATA ref="#user.home-info.postal"/>
   <DATA ref="#user.home-info.telecom.telephone"/>
   <DATA ref="#user.business-info.postal"/>
   <DATA ref="#user.business-info.telecom.telephone"/>
   <DATA ref="#user.home-info.online.email"/>
   <DATA ref="#dynamic.miscdata">
    <CATEGORIES><purchase/></CATEGORIES>
   </DATA>
  </DATA-GROUP>
 </STATEMENT>
 <STATEMENT>
  <CONSEQUENCE>
    At your request, we will send you carefully selected marketing 
    solicitations that we think you will be interested in.
  </CONSEQUENCE>
  <PURPOSE>
   <contact required="opt_in"/>
   <customization required="opt_in"/>
   <tailoring required="opt_in"/>
  </PURPOSE>
  <RECIPIENT required="opt_in"><ours/><same/></RECIPIENT>
  <RETENTION><stated-purpose/></RETENTION>
  <DATA-GROUP>
   <DATA ref="#user.name" optional="yes"/>
   <DATA ref="#user.home-info.postal" optional="yes"/>
   <DATA ref="#user.home-info.telecom.telephone" optional="yes"/>
   <DATA ref="#user.business-info.postal" optional="yes"/>
   <DATA ref="#user.business-info.telecom.telephone" optional="yes"/>
   <DATA ref="#user.home-info.online.email" optional="yes"/>
  </DATA-GROUP>
 </STATEMENT>
 <STATEMENT>
  <CONSEQUENCE>
    We allow you to set a password so that you
    can access your own information.
  </CONSEQUENCE>
  <PURPOSE><customization required="opt_in"/></PURPOSE>
  <RECIPIENT><ours/></RECIPIENT>
  <RETENTION><stated-purpose/></RETENTION>
  <DATA-GROUP>
   <DATA ref="#dynamic.miscdata">
    <CATEGORIES><uniqueid/></CATEGORIES>
   </DATA>
  </DATA-GROUP>
 </STATEMENT>
 <STATEMENT>
  <CONSEQUENCE>
    At your request, we will tailor our site and 
    highlight products related to your interests.
  </CONSEQUENCE>
  <PURPOSE>
    <customization required="opt_in"/>
    <tailoring required="opt_in"/>
  </PURPOSE>
  <RECIPIENT><ours/></RECIPIENT>
  <RETENTION><stated-purpose/></RETENTION>
  <DATA-GROUP>
   <DATA ref="#user.bdate.ymd.year" optional="yes"/>
   <DATA ref="#user.gender" optional="yes"/>
  </DATA-GROUP>
 </STATEMENT>
 <STATEMENT>
  <CONSEQUENCE>
    We tailor our site based on your past visits.
  </CONSEQUENCE>
  <PURPOSE><tailoring/><develop/></PURPOSE>
  <RECIPIENT><ours/></RECIPIENT>
  <RETENTION><stated-purpose/></RETENTION>
  <DATA-GROUP>
   <DATA ref="#dynamic.cookies">
    <CATEGORIES><state/></CATEGORIES>
   </DATA>
   <DATA ref="#dynamic.miscdata">
    <CATEGORIES><preference/></CATEGORIES>
   </DATA>
  </DATA-GROUP>
 </STATEMENT>
</POLICY>

3.2 Policies

This section defines the syntax and semantics of P3P policies. All policies MUST be encoded using [UTF-8]. P3P servers MUST encode their policies using this encoding. P3P user agents MUST be able to parse this syntax.

Policies can be placed stand-alone in a single file (using the POLICY element), or gathered together using the POLICIES element.

3.2.1 The `POLICIES` element

The POLICIES element is used to gather several P3P policies together in a single file. This is provided as a performance optimization: many policies can be collected with a single request, improving network traffic and caching. Even, the POLICIES element can be placed in the well-known location, inside the META element: in this case, user agents need only fetch a single file, containing both the policy reference file and the policies.

Each policy included in a POLICIES element MUST have a name attribute which is unique in the file. This allows policy references (in POLICY-REF elements) to link to that policy.

Example 3.3:

The file in http://www.example.com/Shop/policies.xml could have the following content:

<POLICIES xmlns="http://www.w3.org/2000/10/18/P3Pv1">
   <POLICY discuri="http://www.example.com/disc1" name="policy1"> .... </POLICY>
   <POLICY discuri="http://www.example.com/disc2" name="policy2"> .... </POLICY>
   <POLICY discuri="http://www.example.com/disc3" name="policy3"> .... </POLICY>
</POLICIES>

The files in http://www.example.com/Shop/CDs/* could then be associated to the second policy ("policy2") using the following policy reference file in http://www.example.com/w3c/p3p.xml :

<META xmlns="http://www.w3.org/2000/10/18/P3Pv1">
<POLICY-REFERENCES>
    <POLICY-REF about="/Shop/policies#policy2">
      <INCLUDE>/Shops/CDs/*</INCLUDE>
    </POLICY-REF>
 </POLICY-REFERENCES>
</META>

[19]
policies

=

`<POLICIES xmlns="http://www.w3.org/2000/10/18/P3Pv1">` *policy "</POLICIES>"

3.2.2 The `POLICY` element

The POLICY element contains a complete P3P policy. Each P3P policy MUST contain exactly one POLICY element. The policy element MUST contain an ENTITY element that identifies the legal entity making the representation of the privacy practices contained in the policy. In addition, the policy element MUST contain an ACCESS element, and optionally STATEMENT elements, a DISPUTES-GROUP element, an EXPIRY element (indicating the expiration of the policy), a P3P dataschema, and one or more extensions.

<POLICY>: includes one or more statements. Each statement includes a set of disclosures as applied to a set of data elements.
discuri (mandatory attribute): URI of the natural language privacy statement
opturi: URI of instructions that users can follow to request or decline to have their data used for a particular purpose (opt-in or opt-out). This attribute is mandatory for policies that contain a purpose with required attribute set to opt_in or opt_out.
name: name of the policy, used as a fragment identifier to be able to reference the policy. This attribute is mandatory if the POLICY is included in a POLICIES element.

[20]

policy

`<POLICY xmlns="http://www.w3.org/2000/10/18/P3Pv1"
         discuri=` quoted-URI 
         [` opturi=` quoted-URI]
         [` name=` quotedstring] `>`
*extension
[expiry]
[dataschema]
entity
access
[disputes-group]
*statement-block
*extension
`</POLICY>`

[20]

quoted-URI

`"` URI `"`

Here, URI is defined as per RFC 2396 [URI].

3.2.3 The `ENTITY` element

The ENTITY element gives a precise description of the legal entity making the representation of the privacy practices.

<ENTITY>: identifies the legal entity making the representation of the privacy practices contained in the policy

The ENTITY element contains a description of the legal entity consisting of DATA elements referencing (all or some of) the fields of the business dataset: it MUST contain both the legal entity's name as well as contact information such as postal address, telephone number, email address, or other information that individuals may use to contact the entity about their privacy policy. Note that some laws and codes of conduct require entities to include a postal address or other specific information in their contact information.

[21]
entity

=

"<ENTITY>" *extension entitydescription *extension "</ENTITY>"

[21]
entitydescription

=

"<DATA-GROUP>" `<DATA ref="#business.name"/>` PCDATA "</DATA>" *(`<DATA ref="#business.` string `"/>` PCDATA "</DATA>") "</DATA-GROUP>"

Here, string is defined as a sequence of characters (with " and & escaped) among the values that are allowed by the business dataset. PCDATA is defined as in [XML].

3.2.4 The `ACCESS` element

The ACCESS element indicates whether the site provides access to various kinds of information.

<ACCESS>: the ability of the individual to view identifiable information and address questions or concerns to the service provider. Service providers MUST disclose one value for the access attribute. The method of access is not specified. Any disclosure (other than <all/>) is not meant to imply that access to all data is possible, but that some of the data may be accessible and that the user should communicate further with the service provider to determine what capabilities they have.
Note that service providers may also wish to provide capabilities to access information collected through means other than the Web at the discuri. However, the scope of P3P statements are limited to data collected through HTTP or other Web transport protocols. Also, if access is provided through the Web, use of strong authentication and security mechanisms for such access is recommended; however, security issues are outside the scope of this document.

The ACCESS element must contain one of the following elements:

<nonident/>: Identifiable Data is Not Used
<all/>: All Identifiable Information: access is given to all identifiable information.
<contact_and_other/>: Identifiable Contact Information and Other Identifiable Information: access is given to identifiable online and physical contact information as well as to other information linked to an identifiable person.
<ident_contact/>: Identifiable Contact Information: access is given to identifiable online and physical contact information (e.g., users can access things such as a postal address).
<other_ident/>: Other Identifiable Information: access is given to certain other information linked to an identifiable person (e.g., users can access things such as their online account charges).
<none/>: None: no access to identifiable information is given.

[22]
access

=

"<ACCESS>" access_disclosure *extension "</ACCESS>"

[23]
access-disclosure

=

"<nonident/>" | ; Identifiable Data i

[1]	p3p-header	=	`P3P: ` p3p-header-field *(`,` p3p-header-field)
[2]	p3p-header-field	=	policy-ref-field \| extension-field
[3]	policy-ref-field	=	`policyref="` URI `"`
[4]	extension-field	=	token [`=` (token \| quoted-string) ]
Here, `URI` is defined as per RFC 2396 [URI], `token` and `quoted-string` are defined by [HTTP1.1].

[5]	p3p-link-tag	=	`<link rel="P3Pv1" href="` URI `">`
Here, `URI` is defined as per RFC 2396 [URI].

[6]	prf	=	`<META xmlns="http://www.w3.org/2000/10/18/P3Pv1">` policyrefs [policies] PCDATA "</META>"
[7]	policyrefs	=	"<POLICY-REFERENCES>" [expiry] *policyref "</POLICY-REFERENCES>"
Here `PCDATA` is defined in [XML].

[8]	expiry	=	"<EXPIRY" (absdate\|reldate) "/>"
[9]	absdate	=	`date="` HTTP-date `"`
[10]	reldate	=	`max-age="` delta-seconds `"`
Here, HTTP-date is defined in section 3.3.1 of [HTTP1.1], and delta-seconds is defined in section 3.3.2 of [HTTP1.1].

[12]	include	=	"<INCLUDE>" relativeURI "</INCLUDE>"
[13]	exclude	=	"<EXCLUDE>" relativeURI "</EXCLUDE>"
Here, `relativeURI` is defined as per RFC 2396 [URI], with the addition that the '`*`' character is to be treated as a wildcard, as defined in section 2.3.2.1.2.

[16]	embedded-include	=	"<EMBEDDED-INCLUDE>" absoluteURI "</EMBEDDED-INCLUDE>"
[17]	embedded-exclude	=	"<EMBEDDED-EXCLUDE>" absoluteURI "</EMBEDDED-EXCLUDE>"
Here, `absoluteURI` is defined as per RFC 2396 [URI], with the addition that the '*' character is to be treated as a wildcard, as defined in section 2.3.2.1.2

[14]	cookie-include	=	"<COOKIE-INCLUDE>" NAME "." Domain Path "</COOKIE-INCLUDE>"
[15]	cookie-exclude	=	"<COOKIE-EXCLUDE>" NAME "." Domain Path "</COOKIE-EXCLUDE>"
Here, `NAME`, `Domain` and `Path` are defined as per RFC 2965 [STATE], with the addition that the '`*`' character is to be treated as a wildcard, as defined in section 2.3.2.1.2.

[18]	method-element	=	`<METHOD>` Method `</METHOD>`
Here, `Method` is defined in the section 5.1.1 of [HTTP1.1].

[22]	access	=	"<ACCESS>" access_disclosure *extension "</ACCESS>"
[23]	access-disclosure	=	"<nonident/>" \| ; Identifiable Data i