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

W3C Working Draft 2 November 1999

This Version: http://www.w3.org/TR/1999/WD-P3P-19991102
Latest Version:: http://www.w3.org/TR/P3P
Previous Version:: http://www.w3.org/TR/1999/WD-P3P-19990826/
Editor:: Massimo Marchiori, W3C/MIT, (massimo@w3.org)
Authors:: Lorrie Cranor, AT&T; Marc Langheinrich, ETH Zurich; Massimo Marchiori, W3C/MIT; 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 is a W3C Working Draft for review by W3C members and other interested parties. This document has been produced by the P3P Specification Working Group as part of the P3P Activity. With the publication of this draft, the P3P specification enters last call. The last call period is expected to last for six months, ending April 30, 2000. The Working Group expects to issue one or more updated Working Drafts as comments are received and addressed. The working group notes that it has already received comments regarding the specific terms used in the P3P vocabulary as well as other policy-related issues. These comments have been referred to the P3P Policy Outreach Group, which is expected to review them during the last call period and advise the Specification Working Group as to how they should be addressed. A revised version of this specification is expected to advance toward W3C Recommendation status after two interoperable implementations have been demonstrated.

This Working Draft includes an extension mechanism that can be used to extend the P3P vocabulary. The working group is particularly interested in feedback on how to improve this mechanism as well as examples of extensions that people would like to propose. These examples may be useful for improving the design of the extension mechanism. In addition, the Working Group may consider incorporating some of these ideas into the P3P vocabulary so that they need not be introduced later as extensions.
The introduction to this document (Section 1) provides additional information about the status of this working draft and future versions of P3P.

While this document is in last call, it is still a draft document that may be updated, replaced, or obsoleted by other documents at any time. It is therefore inappropriate to use W3C Working Drafts as reference material or to cite them as other than "work in progress." A list of current W3C working drafts can be found at http://www.w3.org/TR/.

Please send comments to www-p3p-public-comments@w3.org (archived at http://lists.w3.org/Archives/Public/www-p3p-public-comments/).

Introduction
Referencing Policies
Policy Syntax and Semantics
Data Schemas
Appendices
Appendix 1: References (Normative)
Appendix 2: The P3P Base Data Schema Definition (Normative)
Appendix 3: ABNF Notation (Non-normative)
Appendix 4: 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 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, indicate whether or not the data will be used in an identifiable way, and make a variety of other disclosures including whether or not a site has a data retention policy, information about assuring parties, 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 declaration 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.2 P3P User Agents

P3P1.0 user agents can be built into web broswers, 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 P3P headers in HTTP responses and in P3P LINK tags embedded in HTML content. These special headers and tags 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.3 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 configuring their servers to advertise the location of the P3P policy. Automated tools can assist sites in performing this translation. Many HTTP1.1 servers can be configured to support P3P1.0 without requiring the installation of additional software. Servers may be configured to insert a P3P extension header into all HTTP responses that indicates the location of a site's P3P policy, using the HTTP Extension Framework. Alternatively, they can be configured to insert this information into HTML content as a LINK tag. 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.4 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 an Appendix. 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, and case sensitivity. In addition, note that attributes and elements may appear in any order.

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

Assuring Party: Within P3P, an assuring party is a legal entity (person or organization) that makes a statement of assurance about a policy (e.g. that practices are audited, or are in compliance with certain data collection guidelines). Assurance may come from the service itself or from an independent third party. The assuring party must identify what it is attesting to as part of the assurance statement within the policy, at a specified URI, or as part of the semantic definition of a meta-data schema.
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 "Contact Information." P3P1.0 specifies base data categories.
Data Set: A known grouping of data element, such as "user.home.postal.". A set is represented with a trailing period. P3P1.0 specifies a number of base data schemas.
Equable Practice: A practice that is very similar to another in that the purpose, recipients, and identifiable use 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.
Identifiable Use: The use of information relating to an individual that identifies that individual -- this may include linking information with personally identifiable information from other sources or combining information so as to infer a person's identity.
Personally Identifiable Data: Any information relating to an identified or identifiable individual. Note that this vocabulary uses a broader term -- Identifiable Use -- that focuses on the way information is used.
Policy: A collection of one or more privacy statements together with information asserting the identity, URI, assurances, and disclosures of the service covered by the policy.
Practice: The set of disclosures and (optional) solicitations regarding data usage, including purpose, identifiable use, 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.
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 organization 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, sets, and categories.
URI: A Uniform Resource Identifier used to identify Web resources. For definitive information on URI syntax and semantics, see [URI].
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

Whenever a resource is requested from a P3P-enabled site, the site SHOULD specify its privacy policy by either:

using the HTTP Extension Framework to reference the URI of the policy in the HTTP header of the response; or
referencing the URI of the policy using a LINK tag embedded in HTML content.

Clearly, if the requested resource is not an HTML document, the LINK tag option cannot be used.

By referencing a policy URI in a header or link tag, a site asserts that the policy at that URI is applicable to the requested resource. Note that this policy may not necessarily apply to embedded content (such as images and frames) or to the resource referenced by an HTML form's action URI. User agents MAY check for P3P policies on all embedded content and form actions before taking an action on behalf of a user. This pre-checking MAY be done by making HEAD requests referencing the relevant URIs.

Note that if an embedded LINK tag references a certain P3P policy, and a policy HTTP extension header references a different policy for the same resource, user agents MUST assume that an error has been made and treat the resource as if it has no corresponding P3P policy. Likewise, if a document contains multiple policy LINK tags or multiple policy headers that reference different policies, user agents MUST assume an error.

2.1 HTTP Extension Framework

The URI of a policy can be inserted in an HTTP header using the HTTP Extension Framework [HTTP-EXT]. P3P includes one header extension, the policy header, which may be added to any standard HTTP request. The HTTP Extension Framework requires a globally unique URI identifying the extension (the extension declaration). The P3P extension declaration is the following URI:

http://www.w3.org/2000/P3Pv1

The policy header contains the URI where the P3P policy can be fetched. This URI MUST NOT be used for any other purpose beyond identifying and referencing P3P policies (so, it MUST NOT be used to maintain user browsing state).

So, for example, a server that places its P3P policy at the URI http://coolcatalog.com/P3PPolicy1.xml could add the following two lines to all of its HTTP response headers:

Opt: "http://www.w3.org/2000/P3Pv1" ;ns=11
11-policy: http://coolcatalog.com/P3PPolicy1.xml

Note, that the HTTP Extension Framework [HTTP-EXT] requires a two-digit name space declaration for extension headers (in the example above, ns=11). Servers may select any two-digit number that does not conflict with other headers that they use.

The P3P extension declaration and policy header SHOULD be inserted whenever a P3P-enabled server responds to a relevant request, including when it responds to HEAD and OPTIONS requests.

2.2 Embedded LINK Tags

Servers may serve HTML content with embedded LINK tags that indicate the location of the relevant P3P policy. This use of P3P does not require a P3P-aware server (content may be modified to include the embedded link tags without requiring any changes to the way the server operates).

A service that uses this form of reference may declare that it will abide by a given P3P policy by embedding a LINK tag of the following form in the <HEAD> area of an HTML document:

<LINK rel="P3Pv1" href="URI">

URI indicates the location of the P3P policy and "P3Pv1" is a relation name used to distinguish this special P3P link. For example, if a policy is at http://www.privacy.org/P3PPolicy, we would use <LINK rel="P3Pv1" href="http://www.privacy.org/P3PPolicy">.

2.3 User Agent and Server Requirements

2.3.1 Immutability of Policies

An essential requirement on policies is the so-called immutability of policies: policies that can be fetched at a certain URI cannot be changed. This way, the URI of a policy acts like a unique identifier for the policy, and any new policy must therefore use a new different URI. P3P clients MAY check for immutability of policies, by comparing a cached version of a policy with the corresponding freshly retrieved policy. If a user agent discovers that a policy has changed but retains the same URI, it MUST treat the resource covered by the changed policy as if it has no P3P policy.

2.3.2 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.

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, cookies, or user agent information while requesting a P3P policy.

In addition, P3P user agents MAY issue a HEAD request to a site in order to learn the location of the relevant policy before making other requests. This is a useful way to obtain a site's policy without making a request that could result in the transmission of data.

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. In addition, servers SHOULD not use in an identifiable way any information collected while serving a policy file or responding to a HEAD request.

2.3.3 Non-discrimination of Policies

There are three important further requirements on the server side:

Suggest a policy in response to any request:: P3P-compliant servers SHOULD include a reference to a privacy policy for a web resource when a relevant policy is available.
Support HTTP HEAD requests: P3P-compliant servers SHOULD support HEAD requests.
Suggest the same policy irrespective of the HTTP method used to access the page:: P3P-compliant servers SHOULD NOT differentiate policy according to what HTTP method is used to access a specific page.

2.4 Examples

The following is a short example of how the HTTP interactions between a client and a server will typically proceed.

1. Client makes a request using GET, POST, or whatever method it pleases.

GET http://coolcatalog.com/index.html HTTP/1.1
Host: coolcatalog.com

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

HTTP/1.1 200 OK
Opt: "http://www.w3.org/2000/P3Pv1"; ns=11
11-policy: http://coolcatalog.com/P3PPolicy1.xml
. . .
Content-Type: text/html
. . .

2b. Server returns content with an embedded LINK tag pointing to the policy of the page.

HTTP/1.1 200 OK
. . .
Content-Type: text/html
. . .
<LINK rel="P3Pv1" href="http://coolcatalog.com/P3PPolicy1.xml">

3. The user agent fetches the policy at the given URI (or, uses a cached copy)...

GET http://coolcatalog.com/P3PPolicy1.xml HTTP/1.1
Host: coolcatalog.com

... and takes an appropriate action such as prompting the user, displaying a symbol, or comparing the policy with the user's privacy preferences.

This example can be applied to a variety of scenarios.

Scenario 1) Site visited for the first time

User goes to the home page of CoolCatalog for the first time.
CoolCatalog sends the URI for the policy of this page (either in the header, or in an embedded LINK tag).
The user agent fetches the policy at the given URI and takes appropriate action.
User selects the "shoes" pages in the CoolCatalog site. CoolCatalog sends the URI for the policy of this page, which is the same as before.
The user agent doesn't fetch the policy, but uses its locally stored copy, as it is the same by the immutability of policies.
User selects the "payment" page in the CoolCatalog site. CoolCatalog sends the URI for the policy of this page, which is different from the previous policy URI. This time, the user agent fetches this new policy, and takes an appropriate action such as prompting the user, displaying a symbol, or comparing the policy with the user's privacy preferences.

Scenario 2) Site visited another time, same policy

User has previously done scenario 1.
User subsequently returns to the "shoes" page of CoolCatalog. CoolCatalog sends the URI for the policy of this page, which is the same as in scenario 1.
The user agent doesn't fetch the policy, but uses its locally stored copy, as it is the same by the immutability of policy, and takes an appropriate action such as prompting the user, displaying a symbol, or comparing the policy with the user's privacy preferences.
...

Scenario 3) Site visited another time, different policy

User has previously completed scenario 1.
User subsequently returns to the "shoes" page of CoolCatalog. CoolCatalog sends the URI for the policy of this page, which this time is not the same as in scenario 1.
The user agent fetches this new policy, and takes an appropriate action such as prompting the user, displaying a symbol, or comparing the policy with the user's privacy preferences.
...

3. Policy Syntax and Semantics

We begin with an example of an English language privacy policy and a corresponding P3P policy in Section 3.1. 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.

In the sections that follow we introduce a number of XML elements. Each element is given in <> brackets, followed by a list of valid attributes. All listed attributes are optional, except when tagged as mandatory.

3.1 Example policy

3.1.1 English language policy

The following is an example of an English-language privacy policy that we would like to encode as a P3P policy.

CoolCatalog makes the following statement for the Web page at http://www.CoolCatalog.com/catalog/.
We use cookies and collect your gender, information about your clothing preferences, and (optionally) your home address to customize our entry catalog pages and for our own research and product development. We do not use this information in identifiable form.
We also maintain server logs that include information about visits to the http://www.CoolCatalog.com/catalog/ page, and the types of browsers our visitors use. We use this information in order to maintain and improve our web site. We do not use this information in an identifiable way.
We do not provide access capabilities to information we may have from you, but we do have retention and opt-out policies, which you can read more about at our privacy page http://www.CoolCatalog.com/PrivacyPractice.html. The third-party PrivacySeal.org provides assurance that we abide by this agreement.

The following is a more formal description, using the P3P element and attribute names:

Entity: CoolCatalog, Inc.
Disclosure URI: http://www.CoolCatalog.com/PrivacyPractice.html
Access to Identifiable Information: none
Assurance: PrivacySeal.org
Other disclosures: Change agreement, retention
We collect:
    dynamic.cookies (category = state)
    user.gender
    dynamic.miscdata (category = pref)
    user.home. (optional)
For purpose: Customization of the site to individuals, research and development
Identifiable use: No
Recipients: Only ourselves and our agents
Consequence: A site with clothes you would appreciate
We collect:
     dynamic.clickstream.server
     dynamic.http.useragent
For purpose: Web site and system administration, research and development
Identifiable use: No
Recipients: Only ourselves and our agents

3.1.2 XML encoding of policy

The following piece of [XML] captures the information as expressed above. 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.

<POLICY xmlns="http://www.w3.org/2000/P3Pv1"
   entity="CoolCatalog, Inc.">
  <ASSURANCE-GROUP>
     <ASSURANCE org="http://www.PrivacySeal.org" 
      description="PrivacySeal, a third-party seal provider"
      image="http://www.PrivacySeal.org/Logo.gif"/>
  </ASSURANCE-GROUP>
  <DISCLOSURE discuri="http://www.CoolCatalog.com/PrivacyPractice.html" 
   access="none" retention="yes" change_agreement="yes"/>
  <STATEMENT>
     <IDENTIFIABLE><no/></IDENTIFIABLE>
     <CONSEQUENCE-GROUP>
       <CONSEQUENCE>a site with clothes you would appreciate</CONSEQUENCE>
     <RECIPIENT><ours/>/RECIPIENT>
     <PURPOSE><custom/><develop/></PURPOSE>
     <DATA-GROUP>
       <DATA name="dynamic.cookies" category="state"/>
       <DATA name="dynamic.miscdata" category="pref"/>
       <DATA name="user.gender"/>
       <DATA name="user.home." optional="yes"/>
     </DATA-GROUP>
  </STATEMENT>
  <STATEMENT>
    <IDENTIFIABLE><no/></IDENTIFIABLE>
    <RECIPIENT><ours/></RECIPIENT>
    <PURPOSE><admin/><develop/></PURPOSE>
    <DATA-GROUP>
      <DATA name="dynamic.clickstream.server"/>
      <DATA name="dynamic.http.useragent"/>
    </DATA-GROUP>
  </STATEMENT>
</POLICY>

3.2 Policies

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

3.2.1 The `POLICY` element

The POLICY element contains a complete P3P policy. Each P3P policy MUST contain exactly one POLICY element. The policy element MUST have an entity attribute that identifies the legal entity making the representation of the privacy practices contained in the policy. In addition, the policy element MUST contain a DISCLOSURE element, at least one STATEMENT element, and optionally an ASSURANCE-GROUP element 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.
entity (mandatory attribute): The legal entity making the representation of the privacy practices contained in the policy.

[1]
policy

=

`<POLICY xmlns="http://www.w3.org/2000/P3Pv1"` " entity=" quoted-string ">" disclosure [assurance-group] 1*statement-block *extension `</POLICY>`

[2]
quoted-URI

=

`"` URI `"`

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

3.2.2 The `DISCLOSURE` element

The DISCLOSURE element contains a number of general privacy disclosures. A disclosure element MUST include a discuri attribute, which indicates the URI of a site's human-readable privacy policy, and an access attribute, which indicates whether the site provides access to various kinds of information. In addition, a disclosure element MAY include retention and change_agreement attributes, which are binary attributes that indicate whether or not a site makes certain kinds of disclosures in its human-readable privacy policy.

<DISCLOSURE>

simple disclosures regarding service access capabilities, and binary values as to whether the entity makes disclosures regarding changing the agreement (opt-out) for data already collected and how long data is retained.

discuri (mandatory attribute)

URI of the natural language privacy statement of the policy, which should include information on how to contact the service with questions or concerns.

access

the ability of the individual to view identifiable information and address questions or concerns to the service provider. Service providers may disclose one value for the access attributes. The method of access is not specified. This disclosure applies to the identifiable use disclosure. Any disclosure 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 we recommend the use of strong authentication and security mechanisms for such access, however security issues are outside the scope of this document.

There are four valid values for the access attribute:

Identifiable Data is Not Used [nonident]: [this should be consistent with the use of the identifiable qualifier].
Identifiable Contact Information [contact]: access is given to identifiable online and physical contact information (e.g., users can access things such as a postal address).
Other Identifiable Information [other_ident]: access is given to other information linked to an identifiable person (e.g., users can access things such as their online account charges).
Identifiable Contact Information and Other Identifiable Information [contact_and_other]: access is given to identifiable online and physical contact information as well as to other information linked to an identifiable person.
None [none]: no access to identifiable information is given.

retention

does the site make its policy regarding retention (how long data is retained) known at its discuri? Valid values are yes and no.

change_agreement

does the site make its policy regarding change agreement (the capability for the user to cancel, or renegotiate the existing agreement at a future time) known at its discuri? Valid values are yes and no.

[3]
disclosure

=

"<DISCLOSURE" " discuri=" quoted-URI " access=" `"` access-disclosure `"` [" retention=" `"` yesno `"`]
[" change_agreement=" `"` yesno `"`] "/>"

[4]
access-disclosure

=

"nonident" | ; Identifiable Data is Not Used "contact" | ; Identifiable Contact Information "other" | ; Other Identifiable Information
"contact_and_other" | ; Identifiable and other contact information "none" ; None

[5]
yesno

=

"yes" | "no"

Note that retention and change_agreement are optional fields: if a site wishes to signify in a policy that it makes a disclosure about change_agreement, or retention, it MAY do so. No disclosure means that the service provider makes no representation of a policy on that topic.

3.2.3 The `ASSURANCE` element

Optionally, a policy MAY contain an ASSURANCE-GROUP element, which contains one or more ASSURANCE elements. These elements describe assuring parties that attest that an entity will abide by its policy, follows certain data processing guidelines, or other relevant assertions. For example, an assuring party may be a privacy seal provider, a government agency, or the service provider itself. Assurance elements can have several attributes that describe the assuring party and its logo.

<ASSURANCE>: describes a service that attests that the entity will abide by its policy, follows guidelines in the processing of data, or other relevant assertions. Assurance may come from the service provider or an independent assuring party.
service: URI of the assurance service
description: short textual description of the type of assurance service (e.g., third party, legal, etc.)
image: URI of an image logo of the assurance service
width: width in pixels of the image logo
height: height in pixels of the image logo
alt: very short textual alternative for the image logo

[6]
assurance-group

=

"<ASSURANCE-GROUP>" *assurance "</ASSURANCE-GROUP>"

[7]
assurance

=

"<ASSURANCE" " service=" quoted-URI [" description=" quoted-string] [" image=" quoted-URI [" width=" `"` number `"`] [" height=" `"` number `"`] [" alt=" quoted-string] "/>"

[8]
quoted-string

=

`"` string `"`

Here, string is defined as a [UTF-8] string (with " and & escaped)

Note that there can be multiple assurance services, specified via multiple occurrences of ASSURANCE within the ASSURANCE-GROUP element. We expect these fields can be used in a number of ways, from representing that one's privacy practices are self assured, audited by a third party, or under the jurisdiction of a regulatory authority.

3.3 Statements

Statements describe data practices that are applied to particular types of data.

3.3.1 The `STATEMENT` element

The STATEMENT element is a container that groups together an IDENTIFIABLE element, a PURPOSE element, a RECIPIENT element, a DATA-GROUP element, and optionally a CONSEQUENCE-GROUP element and one or more extensions. All of the data referenced by the data-group is handled according to the disclosures made in the other elements contained by the statement. Thus, sites may group elements that are handled the same way and create a statement for each group.

<STATEMENT>: data practices as applied to data elements.

[9]
statement-block

=

"<STATEMENT>"
identifiable [consequence-group] purpose recipient data-group *extension "</STATEMENT>"

To simplify practice declaration, service providers may aggregate any of the disclosures (purposes, recipients, and identifiable use) within a statement over data elements. Service providers MUST make such aggregations as an additive operation. For instance, a site that distributes your age to ours (ourselves and our agents), but distributes your zip code to published (unrelated third parties or public fora), MAY say they distribute your name and zip code to ours and published. Such a statement appears to distribute more data than actually happens. It is up to the service provider to determine if their disclosure deserves specificity or brevity.

Also, one must always disclose all options that apply. Consider a site with the sole purpose of collecting information for the purposes of contact (Contacting Visitors for Marketing of Services or Products). Even though this is considered to be for the current (Completion and Support of Current Activity) purpose, the site must state both contact and current purposes. Consider a site which distributes information to ours in order to redistribute it to published, the site must state both ours and published recipients.

3.3.2 The `IDENTIFIABLE` element

Each STATEMENT element MUST contain an IDENTIFIABLE element that indicates whether data referenced in that statement is used in an identifiable way.

<IDENTIFIABLE>: specifies if data used in a way that is personally identifiable (including linking it with identifiable information about you from other sources)

The IDENTIFIABLE element must contain one of the two following tags:

<yes/>: meaning data is used in a way that is personally identifiable
<no/>: meaning data is not used in a way that is personally identifiable

[10]
identifiable

=

"<IDENTIFIABLE> ("<yes/>" | "<no/>") "</IDENTIFIABLE>"

Is data used in a way that is personally identifiable -- including linking it with personally identifiable information from other sources? While some data is obviously identifiable (such as full name), other data (such as zip code, salary, or birth date) could allow a person to be identified depending on how it is used. Also, a technically astute person in some circumstances could determine the identity of a user from the IP number in a HTTP log. This requires a specific effort and is based on how that IP number is registered, whether it is used by more than one person on a computer, or if it is dynamically allocated by an internet service provider. Consequently, we refrain from defining any particular data or set of data as personally identifiable and instead focus on whether data is used in an identifiable way. Thus identifiable use applies to data commonly considered to be personally identifiable as well as other data that is used in an identifiable way.

3.3.3 The `CONSEQUENCE` element

STATEMENT elements may optionally contain a CONSEQUENCE-GROUP element that contain one or more CONSEQUENCE elements, that can be shown to a human user to provide further explanation about a site's practices.

<CONSEQUENCE>: consequences that can be shown to a human user to explain why the suggested practice may be valuable in a particular instance even if the user would not normally allow the practice.
xml:lang: the language in which the consequence is expressed

Multiple consequences can be indicated using multiple CONSEQUENCE elements, each with one of the consequences. This way, multi-lingual versions of the consequences can be encoded, using the xml:lang attribute.

[11]
consequence-group

=

"<CONSEQUENCE-GROUP>" *consequence "</CONSEQUENCE-GROUP>"

[12]
consequence

=

"<CONSEQUENCE" [" xml:lang= " LanguageID ] ">" PCDATA "</CONSEQUENCE>"

xml:lang and its value type LanguageID, as well as PCDATA, are defined in the [XML] specification.

3.3.4 The `PURPOSE` element

Each STATEMENT element MUST contain a PURPOSE element that contains one or more purposes for data collection. Sites MUST classify their data practices into one or more of the six specified purposes.

<PURPOSE>: purposes for data processing relevant to the Web.

The PURPOSE element must contain one or more among the following:

<current/>: Completion and Support of Current Activity: The use of information by the service provider to complete the activity for which it was provided, such as the provision of information, communications, or interactive services -- for example to return the results from a Web search, to forward email, or place an order.
<admin/>: Web Site and System Administration: The use of information solely for the technical support of the Web site and its computer system. This would include processing computer account information, and information used in the course of securing and maintaining the site.
<custom/>: Customization of Site to Individuals: The use of information to tailor or modify the content or design of the site to the particular individual.
<research/>: Research and Development: The use of information to enhance, evaluate, or otherwise review the site, service, product, or market. This does not include personal information used to tailor or modify the content to the specific individual nor information used to evaluate, target, profile or contact the individual.
<contact/>: Contacting Visitors for Marketing of Services or Products: The use of information to contact the individual for the promotion of a product or service. This includes notifying visitors about updates to the Web site.
<other> string </other>: Other Uses: The use of information not captured by the above definitions. (A human readable explanation should be provided in these instances.)

[13]
purpose

=

"<PURPOSE>" 1*purposevalue "</PURPOSE>"

[14]
purposevalue

=

"<current/>" | ; Completion and Support of Current Activity "<admin/>" | ; Web Site and System Administration "<custom/>" | ; Customization of the Site to Individuals "<develop/>" | ; Research and Development "<contact/>" | ; Contacting Visitors for Marketing of Services or Products "<other>" PCDATA "</other>"; Other Uses

Service providers MUST use the above elements to explain the purpose of data collection. Service providers MUST disclose all that apply. If a service provider does not disclose that a data element will be used for a given purpose, that is a representation that data will not be used for that purpose. Service providers that disclose that they use data for "other" purposes MUST provide human readable explanations of those purposes.

3.3.5 The `RECIPIENT` element

Each STATEMENT element MUST contain a RECIPIENT element that contains one or more recipients of the collected data. Sites MUST classify their recipients into one or more of the four recipients specified.

<RECIPIENT>: the organizational area, or domain, beyond the service provider and its agents where data may be distributed.

The RECIPIENT element must contain one or more among the following:

<ours/>: Ourselves and/or our agents: Ourselves and our agents. We define an agent in this instance as a third party that processes data only on behalf of the service provider for the completion of the stated purposes. (e.g., The service provider and its printing bureau which prints address labels and does nothing further with the information.)
<same/>: Organizations following our practices: Organizations who use the data on their own behalf under equable practices. (e.g., Consider a service provider that grants the user access to collected personal information, they also provide it to a partner who uses it once but discards it. Since the recipient, who has otherwise similar practices, cannot grant the user access to information that it discarded, they are considered to have equable practices.)
<other/>: Organizations following different practices: Organizations that are constrained by and accountable to the original service provider, but may use the data in a way not specified in the service provider's practices. (e.g. The service provider collects data that is shared with a partner who may use it for other purposes. However, it is in the service providers interest to ensure that the data is not used in a way that would be considered abusive to the users' and its own interests.)
<published/>: Unrelated third parties or public fora: Organizations or fora whose data usage practices are not known by the original service provider. (e.g. data is provided as part of a commercial CD-ROM directory, or it is posted on a public on-line Web directory.)

[15]
recipient

=

"<RECIPIENT>" 1*recipientvalue "</RECIPIENT>"

[16]
recipientvalue

=

"<ours/>" | ; only ourselves and our agents "<same/>" | ; organizations following our practices "<other/>" | ; organizations following different practices "<published/>" ; unrelated third parties or public forum

Service providers MUST disclose all the recipients that apply. Note that in many cases a totally accurate description cannot be provided by means of the above set of recipient elements. For instance, the issue of transaction facilitators, such as shipping or payment processors, who are necessary for the completion and support of the activity but may follow different practices was problematic. As it stands, such organizations should be represented in whichever category most accurately reflects their practices with respect to the original service provider.

3.3.6 The DATA element

Each STATEMENT element MUST contain a DATA-GROUP element that contains one or more DATA elements. DATA elements are used to describe the type of data that a site collects.

<DATA>: describes the data to be transferred or inferred
name (mandatory attribute): a string denoting the name of a data element/set. Sets and elements are syntactically distinguished by the presence of a trailing dot after the set name. For example, the trailing dot indicates that user.home. is a data set. Remember that names are case-sensitive (so, for example, user.home. is different from USER.HOME. or User.Home.). Furthermore, in names no underscore symbol ("_") can be present, and no number character can appear immediately following a dot.
dataschema: the URI of the dataschema; the default value is the P3P base data schema
optional: indicates whether or not the site requires visitors to submit this data element; "no" indicates that the data element is required, while "yes" indicates that the data element is not required. The default is "no". The optional attribute is used only in policies. Note that P3P does not include a mechanism for specifying that certain data practices are optional.
category: a string denoting the categories of a data element.

The following six attributes are only used when a new (not defined in the P3P [Base Data Schema]) data element or set is referenced.

type: a string denoting the type of a data element/set.
typeschema: a URI denoting the data schema where the type specified in the type attribute is defined.
template: specifies whether or not the corresponding data element is part of a type definition only. If set to "yes", this means that that the data element is a type definition, and is not actually representing a data element with an associated value. The default value is "no".
short: a string denoting the short display name of the data element/set, no more than 127 [UTF-8] characters.
long: a string denoting a longer description of a data element/set, no more than 1023 [UTF-8] characters.
size: denotes the maximum number of [UTF-8] characters that are needed to store the data element. The default value of 0 indicates that the data element can be arbitrarily large.

[17]
data-group

=

"<DATA-GROUP>" *data-reference "</DATA-GROUP>"

[18]
data-reference

=

"<DATA name=" quoted-string [" dataschema=" quoted-string] [" optional=" yesno] [" type=" quoted-string] [" typeschema=" quoted-string] [" template=" yesno] [" category=" category] [" short=" quoted-string] [" long=" quoted-string] [" size=" `"` number `"`] ; default is 0 (unlimited size) "/>"

Example: To reference the user's home address city, all the elements of the data set user.business. and (optionally) all the elements of the data set user.home.phone, the service would send the following references inside a P3P policy:

<DATA-GROUP>
<DATA name="user.home.city"/>
<DATA name="user.home.phone." optional="yes"/>
<DATA name="user.business."/>
</DATA-GROUP>

3.4 Categories

Categories are attributes of data elements that provide hints to users and user agents as to the intended uses of the data. Categories are vital to making P3P user agents easier to implement and use; they allow users to express more generalized preferences and rules over the exchange of their data. Categories are often included when defining a new element or when referring to data that the user is prompted to type in (as opposed to data stored in the user data repository).

In the current version of P3P, the following tokens are used to denote data categories:

Physical Contact Information [physical]: Information that allows an individual to be contacted or located in the physical world -- such as phone number or address.
Online Contact Information [online]: Information that allows an individual to be contacted or located on the Internet -- such as email. Often, this information is independent of the specific computer used to access the network. (See the category "Computer Information")
Unique Identifiers [uniqueid]: Non-financial identifiers issued for purposes of consistently identifying the individual -- such as SSN or Web site IDs.
Financial Account Identifiers [financial]: Identifiers that tie an individual to a financial instrument, account, or payment system -- such as a credit card or bank account number.
Computer Information [computer]: Information about the computer system that the individual is using to access the network -- such as the IP number, domain name, browser type or operating system.
Navigation and Click-stream Data [navigation]: Data passively generated by browsing the Web site -- such as which pages are visited, and how long users stay on each page.
Interactive Data [interactive]: Data actively generated from or reflecting explicit interactions with a service provider through its site -- such as queries to a search engine, logs of account activity, or purchases made on the Web.
Demographic and Socio-economic Data [demograph]: Data about an individual's characteristics -- such as gender, age, and income.
Preference Data [pref]: Data about an individual's likes and dislikes -- such as favorite color or musical tastes.
Content [content]: The words and expressions contained in the body of a communication -- such as the text of email, bulletin board postings, or chat room communications.
State Management Mechanisms [state]: Mechanisms for maintaining a stateful session with a user or automatically identifying users who have visited a particular site or accessed particular content previously -- such as HTTP cookies.
Other [other]: Other types of data not captured by the above definitions. (A human readable explanation should be provided in these instances.)

The Computer, Navigation, Interactive and Content categories can be distinguished as follows. The Computer category includes information about the user's computer including IP address and software configuration. Navigation data describes actual user behavior related to browsing. When an IP address is stored in a log file with information related to browsing activity, both the Computer category and the Navigation category should be used. Interactive Data is data actively solicited to provide some useful service at a site beyond browsing. Content is information exchanged on a site for the purposes of communication.

The Other category should be used only when data is requested that does not fit into any other category.

P3P uses categories to give users and user agents additional hints as to what type of information is requested from a service. While most data in the Base Data Schema is in a known category (or a set of known categories), some data elements can be in a number of different categories, depending on the situation. The former are called fixed-category data elements (or "fixed data elements" for short), the latter variable-category data elements ("variable data elements"). We will briefly describe both types of elements in the two sections below.

3.4.1 Fixed-Category Data Elements

Most of the elements in the base data schema are so called "fixed" data elements: they belong into one or at most two category classes. By assigning a category invariably to elements in the base data schema, services and users are able to refer to entire groups of elements simply by referencing the corresponding category. For example, using APPEL, the privacy preferences exchange language, users can write rules that prevent their user agent from giving out any data element in a certain category.

When creating data schemas for fixed data elements, schema creators have to explicitly enumerate the categories that these element belong to. For example:

<DATA name="postal.street.line1" type="text"
short="Street Address, Line 1" category="physical" template="yes"/>

In case of multiple categories, multiple elements referencing the same data can be used, each with a different category). For example, in case we want to declare that the data elements in user.name. have both category "physical" and "demograph" we can use:

<DATA name="user.name." type="personname."
short="User's Name" category="physical" template="yes" />
<DATA name="user.name." type="personname."
short="User's Name" category="demograph" template="yes" />

Please note that the category classes of fixed data elements can not be overridden, for example by writing rules or policies that assign a different category to a known fixed base data element. User Agents MUST ignore such categories and instead use the original category (or set of categories) listed in the schema definition. User Agents MAY preferably alert the user that a fixed data element is used together with a non-standard category class.

3.4.2 Variable-Category Data Elements

Not all data elements in the base data schema belong to a pre-determined category class. Some elements can contain information from a range of categories, depending on a particular situation. Such elements are called variable-category data elements (or "variable data element" for short). Although most variable data elements in the P3P Base Data Schema are combined in the dynamic. element set, they can appear in any data set, even mixed with fixed-category data elements.

When creating a schema definition for such elements, schema authors MUST NOT list an explicit category attribute, otherwise the element becomes a fixed data element. For example when specifying the "Year" data type, which can take various categories depending on the situation (e.g. when used for a credit card expiration date vs. for a birth date), the following schema definition can be used:

<DATA name="date.year" type="number" size="6"
short="Year" template="yes"/> 

This allows new schema extensions that reference such variable-category data types to assign a specific category to derived elements, depending on their usage in that extension. For example, an E-commerce schema extension could thus define a credit card expiration date as follows:

<DATA name="Card.ExpDate." type="date."
short="Card Expiration Date" category="financial" template="yes"/>

Under these conditions, the variable data type date. is assigned a fixed category Financial Account Identifiers when being used for specifying a credit card expiration date.

Note that while user preferences can list such variable data elements without any additional category information (effectively expressing preferences over any usage of this element), services MUST always explicitly specify the categories that apply to the usage of a variable data element in their particular policy. This information has to appear as an attribute to the corresponding DATA element listed in the policy, for example as in:

<POLICY ... >
...
<DATA name="dynamic.cookies" category="uniqueid">
...
</POLICY>

where a service declares that cookies are used for identifying the user at this site (i.e. category Unique Identifiers).

3.5 Extension Mechanism

P3P provides a flexible and powerful mechanism to extend its syntax and semantics using two elements, MAN-EXTENSION and OPT-EXTENSION. The markup contained within a MAN-EXTENSION is a mandatory extension to the syntax, meaning that applications that do not understand this extension, also cannot understand the meaning of the whole policy (or dataschema). The markup contained within a OPT-EXTENSION is an optional extension to the syntax, meaning that applications that do not understand this extension can safely ignore it, and go on to process the whole policy (or dataschema) as usual.

[20]
extension

=

mandatoryext | optionalext

[21]
mandatoryext

=

"<MAN-EXTENSION>" PCDATA "</MAN-EXTENSION>"

[22]
optionalext

=

"<OPT-EXTENSION>" PCDATA "</OPT-EXTENSION>"

For example, if www.coolcatalog.com would like to add to P3P a feature like expiration of policies, it could add a mandatory extension like this:

<MAN-EXTENSION>
   <EXPIRES xmlns="http://www.coolcatalog.com/P3P-extensions" date="September 02, 2000"/>
 </MAN-EXTENSION>

The xmlns attribute is significant since it specifies the namespace for interpreting the names of elements and attributes used in the extension.

On the other hand, if www.coolcatalog.com would like to add an extension stating what country the server is in, an optional extension might be more appropriate, such as the following:

<OPT-EXTENSION>
   <ORIGIN xmlns="http://www.coolcatalog.com/P3P-extensions" country="USA">
</OPT-EXTENSION>

The working group is particularly interested in feedback on how to improve this extension mechanism as well as examples of extensions that people would like to propose. These examples may be useful for improving the design of the extension mechanism. In addition, the Working Group may consider incorporating some of these ideas into the P3P vocabulary so that they need not be introduced later as extensions.

4. Data Schemas

P3P has the ability to define data schemas to provide a common way for services and user agents to refer to data elements. A data schema describes specific data elements, which may be grouped into hierarchical data sets.

Services may declare and use data elements by creating a data schema and referencing it in a policy using the dataschema attribute. P3P comes with a standard data schema, the P3P Base Data Schema, that besides defining a wide variety of commonly used data elements, also provides basic data types, which can be conveniently reused by other new schemas.

The format of a data schema is:

<DATASCHEMA xmlns="http://www.w3.org/2000/P3Pv1">
<DATA-GROUP>
<DATA ... />
...
<DATA ... />
</DATA-GROUP>
</DATASCHEMA>

[23]
dataschema

=

`<DATASCHEMA xmlns="http://www.w3.org/2000/P3Pv1">` *(data-reference|extension) "</DATASCHEMA>"

The <DATASCHEMA> tag contains references to the new data elements: such references can be made using the <DATA> tag and the following attributes: name, type, typeschema (which may be omitted if it has the same value as the DATA namespace), template, category, short, long, size.

For every data element, all of the attributes except long are mandatory. If any attribute is missing, it is presumed to be present with an empty string. In the case of the typeschema, the empty string value has the special meaning that the type schema coincides with the namespace of the corresponding DATA element.

For example, suppose the company HyperSpeed wants to build the following data schema:

car.model (of primitive type text)
car.color (of primitive type text)
car.built.year (of primitive type number)
car.built.where. (of basic type postal.)
car.price (of primitive type number)
bike.model (of primitive type text)
bike.color (of primitive type text)
bike.built.year (of primitive type number)
bike.built.where. (of basic type postal.)
bike.price (of primitive type number)

Then, it could place the following code at http://www.HyperSpeed.com/models-schema

<DATASCHEMA xmlns="http://www.w3.org/2000/P3Pv1">
 <DATA name="car.model" type="text" short="Model" 
   category="pref" size="63"/>
 <DATA name="car.color" type="text" short="Color" 
   category="pref" size="63"/>
 <DATA name="car.built.year" type="number" short="Construction Year" 
   category="pref" size="63"/>
 <DATA name="car.built.where." type="postal."  short="Construction Place" 
   category="pref" size="63"/>
 <DATA name="bike." type="car." 
   typeschema="http://www.HyperSpeed.com/models-schema"/>
</DATASCHEMA>

Note that every time a data schema is created, it can be implicitly used as a type, just like the car. case above.

In order to provide multilingual support for data schema files, a server can supply the right alternative based on the HTTP Accept-Language header.

Data Elements can be classified according to whether or not they are in some fixed category (using the category attribute). Schema designers can use this attribute within their schema definitions to define an invariable category for each element. Once defined, this value cannot be changed when referencing such elements from within user preferences, P3P policies, or other schema definitions. However, if left undefined, this attribute MUST be explicitly listed in each P3P policy referencing such elements. Users can have different preferences depending on different attribute-values for the same element. And in the case of undefined attributes within data types, other schema definitions can explicitly set categories in derived elements (otherwise the original definition overrides any value in the derived schema).

Note, that the data element names specified in the base data schema or in extension data schemas may be used for purposes other than P3P policies. For example, web sites may use these names to label HTML form fields. By referring to data the same way in P3P proposals and forms, automated form-filling tools can be better integrated with P3P user agents. When P3P data element names are used as HTML form field names, underscores ("_") MUST be used in place of dot notation (e.g. user.name.first must be referenced as user_name_first). This allows interoperability with client-side javascript which also uses the dot notation to access form field names and values.

4.1 Immutability of Dataschemas

Analogously to P3P policies, an essential requirement on dataschemas is the immutability of dataschemas: dataschemas that can be fetched at a certain URI cannot be changed. This way, the URI of a policy acts like a unique identifier for the policy, and any new dataschema must therefore use a new different URI. P3P clients MAY check for immutability of dataschemas, by comparing a cached version of a policy with the corresponding freshly retrieved policy.

4.2 Primitive Data Types

P3P schemas may refer to the following primitive data element types:

Primitive DataType Definition

text [UTF-8]

gender "M" or "F".

boolean "0" or "1".

binary Base64 per RFC-2045. [MIME]

number text composed with the digits "0", "1", "2", "3", "4", "5", "6", "7", "8", "9".

Country two letters country code as per [ISO3166]

uri [URI]

4.3 The Base Data Schema

All P3P-compliant user agent implementations MUST be aware of the data elements in the P3P Base Data Schema. The P3P Base Data Schema includes two element sets, user. and dynamic.. The user. set includes elements that users might provide values for, while the dynamic. set includes elements that are dynamically generated in the course of a user's browsing session. User agents may support a variety of mechanisms that allow users to provide values for the elements in the user. set, including mechanisms that support multiple personae. Users may choose not to provide values for these data elements.

The formal XML definition of the P3P Base Data Schema is given in Appendix 2. In the following sections, we explain one by one the base data elements and sets. The members of this working group expect that in the future, there will be demand for the creation of other data sets and elements. Obvious applications include catalogue, payment, and agent/system attribute schemas. (An extensive set of system elements is provided for example in http://www.w3.org/TR/NOTE-agent-attributes.)

Each table below specifies a set, the elements within the set, the category associated with the element, its type, and the display name shown to users. More than one category may be associated with a fixed data element. However, we have tried to assign each base data element to only one category whenever possible. We recommend that data schema designers do the same. background color.

4.3.1 User Data

The user. data set includes general information about the user.

user. Category Type Short display name

name. Physical Contact Information, Demographic and SocioEconomic Data personname. User's Name

bdate. Demographic and SocioEconomic Data date. User's Birth Date

cert. Unique Identifiers certificate User's Identity certificate

gender Demographic and SocioEconomic Data gender User's gender

employer Demographic and SocioEconomic Data text User's Employer

department Demographic and SocioEconomic Data text Department or division of organization where user is employed

jobtitle Demographic and SocioEconomic Data text User's Job Title

home. Physical Contact Information,
Online Contact Information, Demographic and SocioEconomic Data contact. User's Home Contact Information

business. Physical Contact Information,
Online Contact Information, Demographic and SocioEconomic Data contact. User's Business Contact Information

Note, that this data set includes elements that are actually sets of data themselves. These sets are defined in the data types subsection of this document. The short display name for an individual element contained within a data set is defined as the concatenation of the short display names that have been defined for the set and the element, separated by commas. For example, the short display name for user.home.postal.postalcode would be "User's Home Contact Information, Postal Address Information, Postal code". User agent implementations may prefer to develop their own short display names rather than using the concatenated names when prompting users for information.

4.3.2 Dynamic Data

In some cases, there is a need to specify data elements that do not have fixed values that a user might type in or store in a repository. In the P3P Base Data Schema, all such elements are grouped under the dynamic. data set. Sites may refer to the types of data they collect using the dynamic data set only, rather than enumerating all of the specific data elements.

dynamic. Category Type Short display name

clickstream.client Navigation and Click-stream Data text Click-stream collected on the client

clickstream.server Navigation and Click-stream Data text Click-stream collected on the server

cookies (variable-category) text Cookies are processed (read/write)

http.useragent Computer Information text User Agent information

http.referrer Navigation and Click-stream Data uri Last URI requested by the user

miscdata (variable-category) text Miscellaneous non-base data schema information

searchtext Interactive Data text Search terms

interactionrecord Interactive Data text Server stores the transaction history

These elements are often implicit in navigation or Web interactions. They should be used with categories to describe the type of information collected through these methods. A brief description of each element follows.

"clickstream.client" should be used when the server accesses off-line browsing information that has been collected by the user's client. Some versions (e.g. 5.0) of Microsoft's Internet Explorer are known to support such behavior.

"clickstream.server" will probably apply to almost all sites on the Web today. It must be used whenever page access data is kept on the server side. Almost all known Web server implementations today will by default create such an access log, often including origin of the request (IP address or DNS name), time, requested resource, HTTP return code and transferred bytes. Any combination of resource name and originating address should be considered clickstream data (i.e. it allows the reconstruction of a visitors movements through the site) and should be declared.

Please note that the logging of referer or user agent information (included in the headers of the HTTP request by many browsers) should explicitly by declared using the http.useragent and http.referrer data elements.

"cookies" should be used whenever information is placed on a user's machine using the HTTP cookie mechanism in order to be "solicited" (i.e. automatically sent) later. Please note that "cookies" is a variable data element and requires the explicit declaration of usage categories in a policy.

"http.useragent" indicates that the server stores additional information about the user agent in its logs, such as operating system, browser software and version.

"http.referrer" indicates that the server stores additional information about the page the user viewed previously, as indicated by the HTTP_REFERER header.

The "miscdata" element references information collected by the service that is not described by any element in the currently available (base) data element schemas. Sites MUST reference a separate miscdata element in their policies for each category of miscdata they collect.

"searchtext" is a specific type of solicitation used for searching and indexing sites. For example, if the only fields on a search engine page are search fields, the site only needs to disclose that data element.

The "interactionrecord" element should be used if the server is keeping track of the interaction it has with the user (i.e. information other than clickstream data, for example account transactions, etc). This element is only meant to inform the user that such information will be retained, but does not indicate how long such data will be kept.

Policies that contain one or more of the Variable Data Elements above explicitly declare the category of the information they solicit, for example:

<POLICY ... >
...
<DATA:REF name="dynamic.miscdata" category="online">
...
</POLICY>

when asking for a user's IRC name (which would be in category Online Contact Information).

4.4 Basic Data Types

4.4.1 Dates

The date. type is a structured type that specifies a date. Since date information can be used in different ways, depending on the context, all date. information is tagged as being of "variable" category. Schema definitions have to explicitly set the corresponding category in the element referencing this data type. For example, soliciting the birthday of a user might be "Demographic and SocioEconomic Data", while the expiration date of a credit card belongs to the "Financial Account Identifiers" category.

date. Category Type Short display name

ymd.year (variable-category) number Year

ymd.month (variable-category) number Month

ymd.day (variable-category) number Day

hms.hour (variable-category) number Hour

hms.minute (variable-category) number Minute

hms.second (variable-category) number Second

fractionsecond (variable-category) number Fraction of Second

timezone (variable-category) text Time Zone

All the fields in the datetime. type correspond to those in the most informative profile of the time standard ISO8601. Note that "day.ymd." and "day.hms." can be used to fast reference the year/month/day and hour/minutes/seconds blocks respectively.

4.4.2 Names

The personname. type is a structured type that specifies information about the naming of a person.

personname. Category Type Short display name

prefix Demographic and SocioEconomic Data text Name Prefix

first Physical Contact Information text First Name

last Physical Contact Information text Last Name

middle Physical Contact Information text Middle Name

suffix Demographic and SocioEconomic Data text Name Suffix

formatted Physical Contact Information, Demographic and SocioEconomic Data text formatted Name

nickname Demographic and SocioEconomic Data text Nickname

4.4.3 Certificates

The certificate. type is a structured type to specify identity certificates (like, for example, X.509).

certificate. Category Type Short display name

key Unique Identifiers binary Certificate Key

format Unique Identifiers text Certificate Format

The "format" field is an IANA registered public key or authentication certificate format, while the "key" field contains the corresponding certificate key.

4.4.4 Telephones

The phonenum. type is a structured type that specifies the characteristics of a phone number.

phonenum. Category Type Short display name

intcode Physical Contact Information number International Phone code

loccode Physical Contact Information number Local Phone Area code

number Physical Contact Information number Phone Number

ext Physical Contact Information number Phone Extension

comment Physical Contact Information text Phone Optional Comments

4.3.5 Contact Information

The contact. type is a structured, redirected, type to other types. This is done so that services can specify precisely which set of data they need.

contact. Category Type Short display name

postal. Physical Contact Information, Demographic and SocioEconomic Data postal. Postal Address Information

telecom. Physical Contact Information telecom. Telecommunications Information

online. Online Contact Information online. Online Address Information

4.4.5.1 Postal

The postal. type is a structured type that specifies a postal mailing address.

postal. Category Type Short display name

name. Physical Contact Information, Demographic and SocioEconomic Data personname. Name

street.line1 Physical Contact Information text Street Address 1

street.line2 Physical Contact Information text Street Address 2

street.line3 Physical Contact Information text Street Address 3

city Physical Contact Information text City

stateprov Physical Contact Information text State or Province

postalcode Demographic and SocioEconomic Data text Postal code

countrycode Demographic and SocioEconomic Data Country Country code

country Demographic and SocioEconomic Data text Country Name

organization Physical Contact Information, Demographic and SocioEconomic Data text Organization Name

formatted Demographic and SocioEconomic Data text formatted Postal Address

Using three distinct fields for the street information allows service providers and user agents to split long addresses into multiple lines during solicitation. However, since all fields share the common street. prefix, this shorthand form can be used to reference all three fields at once.

The "formatted" field is used to specify the formatted text corresponding to the delivery address, as it could for example be printed on a label.

4.4.5.2 Telecommunication

The telecom. type is a structured type that specifies telecommunication information about a person.

telecom. Category Type Short display name

phone. Physical Contact Information phonenum. Phone number

fax. Physical Contact Information phonenum. Fax number

mobile. Physical Contact Information phonenum. Mobile Phone number

pager. Physical Contact Information phonenum. Pager number

4.3.5.3 Online

The online. type is a structured type that specifies online information about a person.

online. Category Type Short display name

email Online Contact Information text Email Address

uri Online Contact Information uri Home Page Address

5. Appendices

Appendix 1: References (Normative)

[APPEL]: M. Langheinrich (Ed.). "A P3P Preference Exchange Language (APPEL)" World Wide Web Consortium.
[DSIG]: Y. Chu, P. DesAutels, B. LaMacchia, P. Lipp. "PICS Signed Labels (DSig) 1.0 Specification," World Wide Web Consortium Recommendation 27 May 1998.
[HTTP1.0]: T. Berners-Lee, R. Fielding, H. Frystyk Nielsen, "RFC1945 -- Hypertext Transfer Protocol -- HTTP/1.0," W3C/MIT, UC Irvine, W3C/MIT, May 1996.
[HTTP1.1]: R. Fielding, J. Gettys, J.C. Mogul, H. Frystyk, T. Berners-Lee, "RFC2068 -- Hypertext Transfer Protocol -- HTTP/1.1," UC Irvine, Digital Equipment Corporation, MIT.
[HTTP-EXT]: H. Frystyk, P. Leach, S. Lawrence. "IETF Internet Draft -- HTTP Extensions", W3C, Microsoft, Agranat Systems, March 1999.
[ISO3166]: "ISO3166: Codes for The Representation of Names of Countries." International Organization for Standardization.
[KEY]: S. Bradner. "RFC2119 -- Key words for use in RFCs to Indicate Requirement Levels." March 1997.
[MIME]: N. Freed, N. Borenstein. "MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies." November 1996.
[SSL]: A. Freier, P. Karlton, P. Kocher. "SSL 3.0 Specification."
[URI]: T. Berners-Lee, R. Fielding, and L. Masinter. "Uniform Resource Identifiers (URI): Generic Syntax and Semantics." August 1998. RFC 2396. [Updates RFC1738]
[UTF-8]: F. Yergeau. "RFC2279 -- UTF-8, a transformation format of ISO 10646." January 1998.
[VCARD]: F. Dawson, T. Howes. "RFC 2426 -- vCard MIME Directory Profile", Lotus Decelopment Corporation, Netscape Communications, September 1998.
[XML]: T. Bray, J. Paoli, C. M. Sperberg-McQueen. "Extensible Markup Language (XML) 1.0 Specification." World Wide Web Consortium, Recommendation. 10 February 1998.
[XML-Data]: A. Layman et al. "XML-Data." World Wide Web Consortium, Note. 5 January 1998.
[XML-Name]: T. Bray, D. Hollander, A. Layman. "Namespaces in XML." World Wide Web Consortium, Working Draft. 16 September 1998.

Appendix 2: The P3P Base Data Schema Definition (Normative)

The data schema corresponding to the P3P base data schema follows. In order to improve legibility, we have indented and aligned the code along various attribute names.

<DATASCHEMA xmlns="http://www.w3.org/2000/P3Pv1">



<DATA:REF name="date.ymd.year"
          short="Year"
                          type="number" size="6"
                          template="yes"/> 
<DATA:REF name="date.ymd.month"
          short="Month"
                          type="number" size="2"
                          template="yes"/> 
<DATA:REF name="date.ymd.day"
          short="Day"
                          type="number" size="2"
                          template="yes"/> 
<DATA:REF name="date.hms.hour"
          short="Hour"
                          type="number" size="2"
                          template="yes"/> 
<DATA:REF name="date.hms.minute"
          short="Minutes"
                          type="number" size="2"
                          template="yes"/> 
<DATA:REF name="date.hms.second"
          short="Second"
                          type="number" size="2"
                          template="yes"/> 
<DATA:REF name="date.fractionsecond"
          short="Fraction of Second"
                          type="number" size="6"
                          template="yes"/> 
<DATA:REF name="date.timezone"
          short="Time Zone"
                          type="text"   size="10"
                          template="yes"/> 


<DATA:REF name="personname.Prefix"
          short="Name Prefix"
                          type="text"
                          category="demograph" template="yes"/>
<DATA:REF name="personname.first"
          short="First Name"
                          type="text"
                          category="physical" template="yes"/>
<DATA:REF name="personname.last"
          short="Last Name"
                          type="text"
                          category="physical" template="yes"/>
<DATA:REF name="personname.middle"
          short="Middle Name"
                          type="text"
                          category="physical" template="yes"/>
<DATA:REF name="personname.suffix"
          short="Name Suffix"
                          type="text"
                          category="demograph" template="yes"/>
<DATA:REF name="personname.formatted"
          short="formatted Name"
                          type="text"
                          category="physical" template="yes"/>
<DATA:REF name="personname.formatted"
          short="formatted Name"
                          type="text"
                          category="demograph" template="yes"/>
<DATA:REF name="personname.nickname"
          short="Nickname"
                          type="text"
                          category="demograph" template="yes"/>


<DATA:REF name="certificate.key"
          short="Certificate Key"
                          type="binary" size="0"
                          category="uniqueid" template="yes"/>
<DATA:REF name="certificate.format"
          short="Certificate format"
                          type="number" size="128"
                          category="uniqueid" template="yes"/>


<DATA:REF name="phonenum.intcode"
          short="International Phone Code"
                          type="number" size="11"
                          category="physical" template="yes"/>
<DATA:REF name="phonenum.loccode"
          short="Local Phone Area Code"
                          type="number" size="11"
                          category="physical" template="yes"/>
<DATA:REF name="phonenum.number"
          short="Phone Number"
                          type="number" size="30"
                          category="physical" template="yes"/>
<DATA:REF name="phonenum.ext"
          short="Phone Extension"
                          type="number" size="11"
                          category="physical" template="yes"/>
<DATA:REF name="phonenum.comment"
          short="Phone Optional Comments"
                          type="text"
                          category="physical" template="yes"/>


<DATA:REF name="contact.postal."
          short="Postal Address Information"
                          type="postal."
                          category="physical" template="yes"/>
<DATA:REF name="contact.postal."
          short="Postal Address Information"
                          type="postal."
                          category="demograph" template="yes"/>
<DATA:REF name="contact.telecom."
          short="Telecommunications Information"
                          type="telecom."
                          category="physical" template="yes"/>
<DATA:REF name="contact.online."
          short="Online Address Information"
                          type="online."
                          category="online" template="yes"/>


<DATA:REF name="postal.name."
          short="Name"
                          type="personname."
                          category="physical" template="yes"/>
<DATA:REF name="postal.name."
          short="Name"
                          type="personname."
                          category="demograph" template="yes"/>
<DATA:REF name="postal.street.line1"
          short="Street Address, Line 1"
                          type="text"
                          category="physical" template="yes"/>
<DATA:REF name="postal.street.line2"
          short="Street Address, Line 2"
                          type="text"
                          category="physical" template="yes"/>
<DATA:REF name="postal.street.line3"
          short="Street Address, Line 3"
                          type="text"
                          category="physical" template="yes"/>
<DATA:REF name="postal.city"
          short="City"
                          type="text"
                          category="physical" template="yes"/>
<DATA:REF name="postal.stateprov"
          short="State or Province"
                          type="text"
                          category="physical" template="yes"/>
<DATA:REF name="postal.postalcode"
          short="Postal Code"
                          type="text"
                          category="demograph" template="yes"/>
<DATA:REF name="postal.organization"
          short="Organization Name"
                          type="text"
                          category="physical" template="yes"/>
<DATA:REF name="postal.organization"
          short="Organization Name"
                          type="text"
                          category="demograph" template="yes"/>
<DATA:REF name="postal.formatted"
          short="Formatted Postal Address"
                          type="text"
                          category="physical" template="yes"/>
<DATA:REF name="postal.formatted"
          short="Formatted Postal Address"
                          type="text"
                          category="demograph" template="yes"/>
<DATA:REF name="postal.country"
          short="Country Name"
                          type="text"
                          category="demograph" template="yes"/>
<DATA:REF name="postal.countrycode"
          short="Country Code"
                          type="Country" size="2"
                          category="demograph" template="yes"/>


<DATA:REF name="telecom.phone."
          short="Phone Number"
                          type="phonenum."
                          category="physical" template="yes"/>
<DATA:REF name="telecom.fax."
          short="Fax Number"
                          type="phonenum."
                          category="physical" template="yes"/>
<DATA:REF name="telecom.mobile."
          short="Mobile Phone Number"
                          type="phonenum."
                          category="physical" template="yes"/>
<DATA:REF name="telecom.pager."
          short="Pager Number"
                          type="phonenum."
                          category="physical" template="yes"/>


<DATA:REF name="online.email"
          short="Email Address"
                          type="text"
                          category="online" template="yes"/>
<DATA:REF name="online.uri"
          short="Home Page Address"
                          type="uri"
                          category="online" template="yes"/>


<DATA:REF name="dynamic.clickstream.client"
          short="Click-stream collected on the client"
                          type="text" source="service"
                          category="navigation"/>
<DATA:REF name="dynamic.clickstream.server"
          short="Click-stream collected on the server"
                          type="text" source="service"
                          category="navigation"/>
<DATA:REF name="dynamic.cookies"
          short="cookies are processed (read/write)"
                          type="text" source="service"
                          template="yes"/> 
<DATA:REF name="dynamic.http.useragent"
          short="User Agent information"
                          type="text" source="service"
                          category="navigation"/>
<DATA:REF name="dynamic.http.referrer"
          short="Last URI requested by the user"
                          type="uri" source="service"
                          category="navigation"/>
<DATA:REF name="dynamic.miscdata"
          short="Miscellaneous non base data schema information"
                          type="text" source="service"
                          template="yes"/> 
<DATA:REF name="dynamic.searchtext"
          short="Search terms"
                          type="text" source="service"
                          category="interactive"/>
<DATA:REF name="dynamic.interactionrecord"
          short="server stores the transaction history"
                          type="text" source="service"
                          category="interactive"/>


<DATA:REF name="user.name."
          short="User's Name"
                          type="personname."
                          category="physical"/>
<DATA:REF name="user.name."
          short="User's Name"
                          type="personname."
                          category="demograph"/>
<DATA:REF name="user.bdate."
          short="User's Birth Date"
                          type="date."
                          category="demographic"/>
<DATA:REF name="user.cert."
          short="User's Identity certificate"
                          type="certificate."
                          category="uniqueid"/>
<DATA:REF name="user.gender"
          short="User's gender"
                          type="gender"
                          category="demograph"/>
<DATA:REF name="user.jobtitle"
          short="User's Job Title"
                          type="text"
                          category="demograph"/>
<DATA:REF name="user.home."
          short="User's Home Contact Information"
                          type="contact."
                          category="physical"/>
<DATA:REF name="user.business."
          short="User's Business Contact Information"
                          type="contact."
                          category="physical"/>
<DATA:REF name="user.employer"
          short="Name of User's Employer"
                          type="text"
                          category="demograph"/>
<DATA:REF name="user.department"
          short="Department or division of organization where user is employed"
                          type="text"
                          category="demograph"/>
</DATASCHEMA>

Appendix 3: ABNF Notation (Non-normative)

The formal grammar of P3P is given in this specification using a slight modification of the ABNF defined in http://info.internet.4.3.5.3isi.edu/in-notes/rfc/files/rfc2234.txt . The following is a simple description of the ABNF.

name = (element): where <name> is the name of the rule, <elements> is one or more rule names or terminals combined through the operands provided below. Rule names are case-insensitive.
(element1 element2): elements enclosed in parentheses are treated as a single element, whose contents are strictly ordered.
<a>*<b>element: at least <a> and at most <b> occurrences of the element.; (1*4<element> means one to four elements.)
<a>element: exactly <a> occurrences of the element.; (4<element> means exactly 4 elements.)
<a>*element: <a> or more elements; (4*<element> means 4 or more elements.)
*<b>element: 0 to <b> elements.; (*5<element> means 0 to 5 elements.)
*element: 0 or more elements.; (*<element> means 0 to infinite elements.)
[element]: optional element, equivalent to *1(element).; ([element] means 0 or 1 element.)
"string" or 'string': matches a literal string matching that given inside the double quotes.

Other notations used in the productions are:

; or /* ... */: comment.

Appendix 4: Working Group Contributors (Non-normative)

This specification was produced by the P3P Specification Working Group. The following individuals participated in the P3P Specification Working Group, chaired by Lorrie Cranor (AT&T): Mark Ackerman (University of California, Irvine), Margareta Björksten (Nokia), Joe Coco (Microsoft), Daniel LaLiberte (W3C), Marc Langheinrich (NEC/UTH Zurich), Daniel Lim (PrivacyBank), Massimo Marchiori (W3C/MIT), Christine McKenna (Phone.com, Inc.), Paul Perry (Microsoft), Martin Presler-Marshall (IBM), Dave Remy (Geotrust), Ari Schwartz (CDT), Betty Whitaker (NCR), Sam Yen (Citigroup), Alan Zausner (American Express).

The P3P Specification Working Group inherited a large part of the specification from previous P3P working groups. The Working Group would like to acknowledge the contributions of the members of these previous groups (affiliations shown are the members' affiliations at the time of their participation in each working group).

The P3P Implementation and Deployment Working Group, chaired by Rolf Nelson (W3C) and Marc Langheinrich (ETH Zurich): Mark Ackerman (University of California, Irvine), Rob Barrett (IBM), Joe Coco (Microsoft), Lorrie Cranor (AT&T), Massimo Marchiori (W3C/MIT), Gabe Montero (IBM), Stephen Morse (Netscape), Paul Perry (Microsoft), Ari Schwartz (CDT), Gabriel Speyer (Citibank), Betty Whitaker (NCR).

The P3P Syntax Working Group, chaired by Steve Lucas (Matchlogic): Lorrie Cranor (AT&T), Melissa Dunn (Microsoft), Daniel Jaye (Engage Technologies), Massimo Marchiori (W3C/MIT), Maclen Marvit (Narrowline), Max Metral (Firefly), Paul Perry (Firefly), Martin Presler-Marshall (IBM), Drummond Reed (Intermind), Joseph Reagle (W3C).

The P3P Vocabulary Harmonization Working Group, chaired by Joseph Reagle (W3C): Liz Blumenfeld (America Online), Ann Cavoukian (Information and Privacy Commission/Ontario), Scott Chalfant (Matchlogic), Lorrie Cranor (AT&T), Jim Crowe (Direct Marketing Association), Josef Dietl (W3C), David Duncan (Information and Privacy Commission/Ontario), Melissa Dunn (Microsoft), Patricica Faley (Direct Marketing Association), Marit Köhntopp (Privacy Commissioner of Schleswig-Holstein, Germany), Tony Lam (Hong Kong Privacy Commissioner's Office), Tara Lemmey (Narrowline), Jill Lesser (America Online), Steve Lucas (Matchlogic), Deirdre Mulligan (Center for Democracy and Technology), Nick Platten (Data Protection Consultant, formerly of DG XV, European Commission), Ari Schwartz (Center for Democracy and Technology), Jonathan Stark (TRUSTe).

The P3P Protocols and Data Transport Working Group, chaired by Yves Leroux (Digital): Lorrie Cranor (AT&T), Philip DesAutels (Matchlogic), Melissa Dunn (Microsoft), Peter Heymann (Intermind), Tatsuo Itabashi (Sony), Dan Jaye (Engage), Steve Lucas (Matchlogic), Jim Miller (W3C), Michael Myers (VeriSign), Paul Perry (FireFly), Martin Presler-Marshall (IBM), Joseph Reagle (W3C), Drummond Reed (Intermind), Craig Vodnik (Pencom Web Worlds).

The P3P Vocabulary Working Group, chaired by Lorrie Cranor (AT&T): Mark Ackerman (W3C), Philip DesAutels (W3C), Melissa Dunn (Microsoft), Joseph Reagle (W3C), Upendra Shardanand (Firefly).

The P3P Architecture Working Group, chaired by Martin Presler-Marshall (IBM): Mark Ackerman (W3C), Lorrie Cranor (AT&T), Philip DesAutels (W3C), Melissa Dunn (Microsoft), Joseph Reagle (W3C).

[1]	`policy`	=	`<POLICY xmlns="http://www.w3.org/2000/P3Pv1"` " entity=" quoted-string ">" disclosure [assurance-group] 1statement-block extension `</POLICY>`
[2]	quoted-URI	=	`"` URI `"`
Here, URI is defined as per RFC 2396 [URI]

[6]	assurance-group	=	"<ASSURANCE-GROUP>" *assurance "</ASSURANCE-GROUP>"
[7]	assurance	=	"<ASSURANCE" " service=" quoted-URI [" description=" quoted-string] [" image=" quoted-URI [" width=" `"` number `"`] [" height=" `"` number `"`] [" alt=" quoted-string] "/>"
[8]	quoted-string	=	`"` string `"`
Here, string is defined as a [UTF-8] string (with " and & escaped)

[11]	consequence-group	=	"<CONSEQUENCE-GROUP>" *consequence "</CONSEQUENCE-GROUP>"
[12]	consequence	=	"<CONSEQUENCE" [" xml:lang= " LanguageID ] ">" PCDATA "</CONSEQUENCE>"
`xml:lang` and its value type `LanguageID`, as well as `PCDATA`, are defined in the [XML] specification.

[20]	extension	=	mandatoryext \| optionalext
[21]	mandatoryext	=	"<MAN-EXTENSION>" PCDATA "</MAN-EXTENSION>"
[22]	optionalext	=	"<OPT-EXTENSION>" PCDATA "</OPT-EXTENSION>"

Primitive DataType	Definition
text	[UTF-8]
gender	"M" or "F".
boolean	"0" or "1".
binary	Base64 per RFC-2045. [MIME]
number	text composed with the digits "0", "1", "2", "3", "4", "5", "6", "7", "8", "9".
Country	two letters country code as per [ISO3166]
uri	[URI]

user.	Category	Type	Short display name
name.	Physical Contact Information, Demographic and SocioEconomic Data	personname.	User's Name
bdate.	Demographic and SocioEconomic Data	date.	User's Birth Date
cert.	Unique Identifiers	certificate	User's Identity certificate
gender	Demographic and SocioEconomic Data	gender	User's gender
employer	Demographic and SocioEconomic Data	text	User's Employer
department	Demographic and SocioEconomic Data	text	Department or division of organization where user is employed
jobtitle	Demographic and SocioEconomic Data	text	User's Job Title
home.	Physical Contact Information, Online Contact Information, Demographic and SocioEconomic Data	contact.	User's Home Contact Information
business.	Physical Contact Information, Online Contact Information, Demographic and SocioEconomic Data	contact.	User's Business Contact Information

dynamic.	Category	Type	Short display name
clickstream.client	Navigation and Click-stream Data	text	Click-stream collected on the client
clickstream.server	Navigation and Click-stream Data	text	Click-stream collected on the server
cookies	(variable-category)	text	Cookies are processed (read/write)
http.useragent	Computer Information	text	User Agent information
http.referrer	Navigation and Click-stream Data	uri	Last URI requested by the user
miscdata	(variable-category)	text	Miscellaneous non-base data schema information
searchtext	Interactive Data	text	Search terms
interactionrecord	Interactive Data	text	Server stores the transaction history

date.	Category	Type	Short display name
ymd.year	(variable-category)	number	Year
ymd.month	(variable-category)	number	Month
ymd.day	(variable-category)	number	Day
hms.hour	(variable-category)	number	Hour
hms.minute	(variable-category)	number	Minute
hms.second	(variable-category)	number	Second
fractionsecond	(variable-category)	number	Fraction of Second
timezone	(variable-category)	text	Time Zone

personname.	Category	Type	Short display name
prefix	Demographic and SocioEconomic Data	text	Name Prefix
first	Physical Contact Information	text	First Name
last	Physical Contact Information	text	Last Name
middle	Physical Contact Information	text	Middle Name
suffix	Demographic and SocioEconomic Data	text	Name Suffix
formatted	Physical Contact Information, Demographic and SocioEconomic Data	text	formatted Name
nickname	Demographic and SocioEconomic Data	text	Nickname

certificate.	Category	Type	Short display name
key	Unique Identifiers	binary	Certificate Key
format	Unique Identifiers	text	Certificate Format

phonenum.	Category	Type	Short display name
intcode	Physical Contact Information	number	International Phone code
loccode	Physical Contact Information	number	Local Phone Area code
number	Physical Contact Information	number	Phone Number
ext	Physical Contact Information	number	Phone Extension
comment	Physical Contact Information	text	Phone Optional Comments

contact.	Category	Type	Short display name
postal.	Physical Contact Information, Demographic and SocioEconomic Data	postal.	Postal Address Information
telecom.	Physical Contact Information	telecom.	Telecommunications Information
online.	Online Contact Information	online.	Online Address Information

postal.	Category	Type	Short display name
name.	Physical Contact Information, Demographic and SocioEconomic Data	personname.	Name
street.line1	Physical Contact Information	text	Street Address 1
street.line2	Physical Contact Information	text	Street Address 2
street.line3	Physical Contact Information	text	Street Address 3
city	Physical Contact Information	text	City
stateprov	Physical Contact Information	text	State or Province
postalcode	Demographic and SocioEconomic Data	text	Postal code
countrycode	Demographic and SocioEconomic Data	Country	Country code
country	Demographic and SocioEconomic Data	text	Country Name
organization	Physical Contact Information, Demographic and SocioEconomic Data	text	Organization Name
formatted	Demographic and SocioEconomic Data	text	formatted Postal Address

telecom.	Category	Type	Short display name
phone.	Physical Contact Information	phonenum.	Phone number
fax.	Physical Contact Information	phonenum.	Fax number
mobile.	Physical Contact Information	phonenum.	Mobile Phone number
pager.	Physical Contact Information	phonenum.	Pager number

online.	Category	Type	Short display name
email	Online Contact Information	text	Email Address
uri	Online Contact Information	uri	Home Page Address