6 Appendices

Appendix 1: References (Normative)

[ CHARMODEL ] M. D ¼rst, F. Yergeau (Eds.), "Character Model for the World Wide Web," World Wide Web Consortium Working Draft. 29 November 1999.

[ DOM2-Events ] T. Pixley (Ed.), "Document Object Model (DOM) Level 2 Events Specification," World Wide Web Consortium, Proposed Recommendation. 27 September 2000.

[ HTTP1.0 ] T. Berners-Lee, R. Fielding, H. Frystyk, "RFC1945 ”Hypertext Transfer Protocol ”HTTP/1.0," May 1996.

[ HTTP1.1 ] R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L. Masinter, P. Leach, T. Berners-Lee, "RFC2616 ”Hypertext Transfer Protocol ”HTTP/1.1," June 1999. [Updates RFC2068]

[ KEY ] S. Bradner. "RFC2119 ”Key words for use in RFCs to Indicate Requirement Levels." March 1997.

[ P3P-HEADER ] R. Lotenberg, M. Marchiori (Eds.), "The HTTP header for the Platform for Privacy Preferences 1.0 (P3P1.0)" (also available in HTML and XML formats), IETF Internet Draft, August 2001.

[ STATE ] Kristol, D., Montulli, L., "RFC2965 ”HTTP State Management Mechanism." October, 2000 [Obsoletes RFC2109]

[ URI ] T. Berners-Lee, R. Fielding, and L. Masinter. "RFC 2396 ”Uniform Resource Identifiers (URI): Generic Syntax and Semantics." August 1998. [Updates RFC1738]

[ UTF-8 ] F. Yergeau. "RFC2279 ”UTF-8, a transformation format of ISO 10646." January 1998.

[ XML ] T. Bray, J. Paoli, C. M. Sperberg-McQueen (Eds.). "Extensible Markup Language (XML) 1.0 Specification." World Wide Web Consortium, Recommendation. 10 February 1998.

[ XML- Name ] T. Bray, D. Hollander, A. Layman (Eds.). "Namespaces in XML." World Wide Web Consortium, Recommendation. 14 January 1999.

[ XML-Schema1 ] H. Thompson, D. Beech, M. Maloney, and N. Mendelsohn (Eds.). "XML Schema Part 1: Structures" World Wide Web Consortium Recommendation. 2 May 2001.

[ XML-Schema2 ] P. Biron, A. Malhotra (Eds.). "XML Schema Part 2: Datatypes" World Wide Web Consortium Recommendation. 2 May 2001.

Appendix 2: References (Non-Normative)

[ABNF] D. Crocker, P. Overel. "RFC2234 ”Augmented BNF for Syntax Specifications: ABNF," Internet Mail Consortium, Demon Internet Ltd., November 1997.

[APPEL] M. Langheinrich (Ed.). "A P3P Preference Exchange Language (APPEL)" World Wide Web Consortium Working Draft.

[COOKIES] "Persistent Client State ”HTTP Cookies," Preliminary Specification, Netscape, 1999.

[HTML] D. Raggett, A. Le Hors, and I. Jacobs (Eds.). "HTML 4.01 Specification" World Wide Web Consortium.

[ISO3166] "ISO3166: Codes for The Representation of Names of Countries." International Organization for Standardization.

[ISO8601] "ISO8601: Data elements and interchange formats ”Information interchange ”Representation of dates and times." International Organization for Standardization.

[RDF] O. Lassila and R. Swick (Eds.). "Resource Description Framework (RDF) Model and Syntax Specification." World Wide Web Consortium, Recommendation. 22 February 1999.

[UNICODE] Unicode Consortium. "The Unicode Standard."

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

The data schema corresponding to the P3P base data schema follows for easy reference. The schema is also present as a separate file at the URI http://www.w3.org/TR/P3P/base.

 <DATASCHEMA xmlns="http://www.w3.org/2001/09/P3Pv1"> <!-- ********** Base Data Structures ********** --> <!-- "date" Data Structure --> <DATA-STRUCT name="date.ymd.year"     short-description="Year"/> <DATA-STRUCT name="date.ymd.month"     short-description="Month"/> <DATA-STRUCT name="date.ymd.day"     short-description="Day"/> <DATA-STRUCT name="date.hms.hour"     short-description="Hour"/> <DATA-STRUCT name="date.hms.minute"     short-description="Minute"/> <DATA-STRUCT name="date.hms.second"     short-description="Second"/> <DATA-STRUCT name="date.fractionsecond"     short-description="Fraction of Second"/> <DATA-STRUCT name="date.timezone"     short-description="Time Zone"/> <!-- "login" Data Structure --> <DATA-STRUCT name="login.id"     short-description="Login ID">     <CATEGORIES><uniqueid/></CATEGORIES> </DATA-STRUCT> <DATA-STRUCT name="login.password"     short-description="Login Password">     <CATEGORIES><uniqueid/></CATEGORIES> </DATA-STRUCT> <!-- "personname" Data Structure --> <DATA-STRUCT name="personname.prefix"     short-description="Name Prefix">     <CATEGORIES><demographic/></CATEGORIES> </DATA-STRUCT> <DATA-STRUCT name="personname.given"     short-description="Given Name (First Name)">     <CATEGORIES><physical/></CATEGORIES> </DATA-STRUCT> <DATA-STRUCT name="personname.middle"     short-description="Middle Name">     <CATEGORIES><physical/></CATEGORIES> </DATA-STRUCT> <DATA-STRUCT name="personname.family"     short-description="Family Name (Last Name)">     <CATEGORIES><physical/></CATEGORIES> </DATA-STRUCT> <DATA-STRUCT name="personname.suffix"     short-description="Name Suffix">     <CATEGORIES><demographic/></CATEGORIES> </DATA-STRUCT> <DATA-STRUCT name="personname.nickname"     short-description="Nickname">     <CATEGORIES><demographic/></CATEGORIES> </DATA-STRUCT> <!-- "certificate" Data Structure --> <DATA-STRUCT name="certificate.key"     short-description="Certificate key">     <CATEGORIES><uniqueid/></CATEGORIES> </DATA-STRUCT> <DATA-STRUCT name="certificate.format"     short-description="Certificate format">     <CATEGORIES><uniqueid/></CATEGORIES> </DATA-STRUCT> <!-- "telephonenum" Data Structure --> <DATA-STRUCT name="telephonenum.intcode"     short-description="International Telephone Code">     <CATEGORIES><physical/></CATEGORIES> </DATA-STRUCT> <DATA-STRUCT name="telephonenum.loccode"     short-description="Local Telephone Area Code">     <CATEGORIES><physical/></CATEGORIES> </DATA-STRUCT> <DATA-STRUCT name="telephonenum.number"     short-description="Telephone Number">     <CATEGORIES><physical/></CATEGORIES> </DATA-STRUCT> <DATA-STRUCT name="telephonenum.ext"     short-description="Telephone Extension">     <CATEGORIES><physical/></CATEGORIES> </DATA-STRUCT> <DATA-STRUCT name="telephonenum.comment"     short-description="Telephone Optional Comments">     <CATEGORIES><physical/></CATEGORIES> </DATA-STRUCT> <!-- "postal" Data Structure --> <DATA-STRUCT name="postal.name" structref="#personname"> </DATA-STRUCT> <DATA-STRUCT name="postal.street"     short-description="Street Address">     <CATEGORIES><physical/></CATEGORIES> </DATA-STRUCT> <DATA-STRUCT name="postal.city"     short-description="City">     <CATEGORIES><demographic/></CATEGORIES> </DATA-STRUCT> <DATA-STRUCT name="postal.stateprov"     short-description="State or Province">     <CATEGORIES><demographic/></CATEGORIES> </DATA-STRUCT> <DATA-STRUCT name="postal.postalcode"     short-description="Postal Code">     <CATEGORIES><demographic/></CATEGORIES> </DATA-STRUCT> <DATA-STRUCT name="postal.organization"     short-description="Organization Name">     <CATEGORIES><demographic/></CATEGORIES> </DATA-STRUCT> <DATA-STRUCT name="postal.country"     short-description="Country Name">     <CATEGORIES><demographic/></CATEGORIES> </DATA-STRUCT> <!-- "telecom" Data Structure --> <DATA-STRUCT name="telecom.telephone"     short-description="Telephone Number"     structref="#telephonenum">     <CATEGORIES><physical/></CATEGORIES> </DATA-STRUCT> <DATA-STRUCT name="telecom.fax"     short-description="Fax Number"     structref="#telephonenum">     <CATEGORIES><physical/></CATEGORIES> </DATA-STRUCT> <DATA-STRUCT name="telecom.mobile"     short-description="Mobile Telephone Number"     structref="#telephonenum">     <CATEGORIES><physical/></CATEGORIES> </DATA-STRUCT> <DATA-STRUCT name="telecom.pager"     short-description="Pager Number"     structref="#telephonenum">     <CATEGORIES><physical/></CATEGORIES> </DATA-STRUCT> <!-- "online" Data Structure --> <DATA-STRUCT name="online.email"     short-description="Email Address">     <CATEGORIES><online/></CATEGORIES> </DATA-STRUCT> <DATA-STRUCT name="online.uri"     short-description="Home Page Address">     <CATEGORIES><online/></CATEGORIES> </DATA-STRUCT> <!-- "contact" Data Structure --> <DATA-STRUCT name="contact.postal"     short-description="Postal Address Information"     structref="#postal"> </DATA-STRUCT> <DATA-STRUCT name="contact.telecom"     short-description="Telecommunications Information"     structref="#telecom">     <CATEGORIES><physical/></CATEGORIES> </DATA-STRUCT> <DATA-STRUCT name="contact.online"     short-description="Online Address Information"     structref="#online">     <CATEGORIES><online/></CATEGORIES> </DATA-STRUCT> <!-- "uri" Data Structure --> <DATA-STRUCT name="uri.authority"     short-description="URI Authority"/> <DATA-STRUCT name="uri.stem"     short-description="URI Stem"/> <DATA-STRUCT name="uri.querystring"     short-description="Query-string Portion of URI"/> <!-- "ipaddr" Data Structure --> <DATA-STRUCT name="ipaddr.hostname"     short-description="Complete Host and Domain Name">     <CATEGORIES><computer/></CATEGORIES> </DATA-STRUCT> <DATA-STRUCT name="ipaddr.partialhostname"     short-description="Partial Hostname">     <CATEGORIES><demographic/></CATEGORIES> </DATA-STRUCT> <DATA-STRUCT name="ipaddr.fullip"     short-description="Full IP Address">     <CATEGORIES><computer/></CATEGORIES> </DATA-STRUCT> <DATA-STRUCT name="ipaddr.partialip"     short-description="Partial IP Address">     <CATEGORIES><demographic/></CATEGORIES> </DATA-STRUCT> <!-- "loginfo" Data Structure --> <DATA-STRUCT name="loginfo.uri"     short-description="URI of Requested Resource"     structref="#uri">     <CATEGORIES><navigation/></CATEGORIES> </DATA-STRUCT> <DATA-STRUCT name="loginfo.timestamp"     short-description="Request Timestamp"     structref="#date">     <CATEGORIES><navigation/></CATEGORIES> </DATA-STRUCT> <DATA-STRUCT name="loginfo.clientip"     short-description="Client's IP Address or Hostname"     structref="#ipaddr"> </DATA-STRUCT> <DATA-STRUCT name="loginfo.other.httpmethod"     short-description="HTTP Request Method">     <CATEGORIES><navigation/></CATEGORIES> </DATA-STRUCT> <DATA-STRUCT name="loginfo.other.bytes"     short-description="Data Bytes in Response">     <CATEGORIES><navigation/></CATEGORIES> </DATA-STRUCT> <DATA-STRUCT name="loginfo.other.statuscode"     short-description="Response Status Code">     <CATEGORIES><navigation/></CATEGORIES> </DATA-STRUCT> <!-- "httpinfo" Data Structure --> <DATA-STRUCT name="httpinfo.referer"     short-description="Last URI Requested by the User"     structref="#uri">     <CATEGORIES><navigation/></CATEGORIES> </DATA-STRUCT> <DATA-STRUCT name="httpinfo.useragent"     short-description="User Agent Information">     <CATEGORIES><computer/></CATEGORIES> </DATA-STRUCT> <!-- ********** Base Data Schemas ********** --> <!-- "dynamic" Data Schema --> <DATA-DEF name="dynamic.clickstream"     short-description="Click-stream Information"     structref="#loginfo">     <CATEGORIES><navigation/><computer/><demographic/></CATEGORIES> </DATA-DEF> <DATA-DEF name="dynamic.http"     short-description="HTTP Protocol Information"     structref="#httpinfo">     <CATEGORIES><navigation/><computer/></CATEGORIES> </DATA-DEF> <DATA-DEF name="dynamic.clientevents"     short-description="User's Interaction with a Resource">     <CATEGORIES><navigation/></CATEGORIES> </DATA-DEF> <DATA-DEF name="dynamic.cookies"     short-description="Use of HTTP Cookies"/> <DATA-DEF name="dynamic.searchtext"     short-description="Search Terms">     <CATEGORIES><interactive/></CATEGORIES> </DATA-DEF> <DATA-DEF name="dynamic.interactionrecord"     short-description="Server Stores the Transaction History">     <CATEGORIES><interactive/></CATEGORIES> </DATA-DEF> <DATA-DEF name="dynamic.miscdata"     short-description="Miscellaneous Non-base Data Schema = information"/> <!-- "user" Data Schema --> <DATA-DEF name="user.name"     short-description="User's Name"     structref="#personname">     <CATEGORIES><physical/><demographic/></CATEGORIES> </DATA-DEF> <DATA-DEF name="user.bdate"     short-description="User's Birth Date"     structref="#date">     <CATEGORIES><demographic/></CATEGORIES> </DATA-DEF> <DATA-DEF name="user.login"     short-description="User's Login Information"     structref="#login">     <CATEGORIES><uniqueid/></CATEGORIES> </DATA-DEF> <DATA-DEF name="user.cert"     short-description="User's Identity Certificate"     structref="#certificate">     <CATEGORIES><uniqueid/></CATEGORIES> </DATA-DEF> <DATA-DEF name="user.gender"     short-description="User's Gender">     <CATEGORIES><demographic/></CATEGORIES> </DATA-DEF> <DATA-DEF name="user.jobtitle"     short-description="User's Job Title">     <CATEGORIES><demographic/></CATEGORIES> </DATA-DEF> <DATA-DEF name="user.home-info"     short-description="User's Home Contact Information"     structref="#contact">     <CATEGORIES><physical/><online/><demographic/></CATEGORIES> </DATA-DEF> <DATA-DEF name="user.business-info"     short-description="User's Business Contact Information"     structref="#contact">     <CATEGORIES><physical/><online/><demographic/></CATEGORIES> </DATA-DEF> <DATA-DEF name="user.employer"     short-description="Name of User's Employer">     <CATEGORIES><demographic/></CATEGORIES> </DATA-DEF> <DATA-DEF name="user.department"     short-description="Department or Division of Organization where     User is Employed">     <CATEGORIES><demographic/></CATEGORIES> </DATA-DEF> <!-- "thirdparty" Data Schema --> <DATA-DEF name="thirdparty.name"     short-description="Third Party's Name"     structref="#personname">     <CATEGORIES><physical/><demographic/></CATEGORIES> </DATA-DEF> <DATA-DEF name="thirdparty.bdate"     short-description="Third Party's Birth Date"     structref="#date">     <CATEGORIES><demographic/></CATEGORIES> </DATA-DEF> <DATA-DEF name="thirdparty.login"     short-description="Third Party's Login Information"     structref="#login">     <CATEGORIES><uniqueid/></CATEGORIES> </DATA-DEF> <DATA-DEF name="thirdparty.cert"     short-description="Third Party's Identity Certificate"     structref="#certificate">     <CATEGORIES><uniqueid/></CATEGORIES> </DATA-DEF> <DATA-DEF name="thirdparty.gender"     short-description="Third Party's Gender">     <CATEGORIES><demographic/></CATEGORIES> </DATA-DEF> <DATA-DEF name="thirdparty.jobtitle"     short-description="Third Party's Job Title">     <CATEGORIES><demographic/></CATEGORIES> </DATA-DEF> <DATA-DEF name="thirdparty.home-info"     short-description="Third Party's Home Contact Information"     structref="#contact">     <CATEGORIES><physical/><online/><demographic/></CATEGORIES> </DATA-DEF> <DATA-DEF name="thirdparty.business-info"     short-description="Third Party's Business Contact Information"     structref="#contact">     <CATEGORIES><physical/><online/><demographic/></CATEGORIES> </DATA-DEF> <DATA-DEF name="thirdparty.employer"     short-description="Name of Third Party's Employer">     <CATEGORIES><demographic/></CATEGORIES> </DATA-DEF> <DATA-DEF name="thirdparty.department"     short-description="Department or Division of Organization where     Third Party is Employed">     <CATEGORIES><demographic/></CATEGORIES> </DATA-DEF> <!-- "business" Data Schema --> <DATA-DEF name="business.name"     short-description="Organization Name">     <CATEGORIES><demographic/></CATEGORIES> </DATA-DEF> <DATA-DEF name="business.department"     short-description="Department or Division of Organization">     <CATEGORIES><demographic/></CATEGORIES> </DATA-DEF> <DATA-DEF name="business.cert"     short-description="Organization Identity certificate"     structref="#certificate">     <CATEGORIES><uniqueid/></CATEGORIES> </DATA-DEF> <DATA-DEF name="business.contact-info"     short-description="Contact Information for the Organization"     structref="#contact">     <CATEGORIES><physical/><online/><demographic/></CATEGORIES> </DATA-DEF> </DATASCHEMA> 

Appendix 4: XML Schema Definition (Normative)

This appendix contains the XML schema, both for P3P policy reference files, for P3P policy documents, and for P3P data schema documents. An XML schema may be used to validate the structure and datastruct values used in an instance of the schema given as an XML document. P3P policy and data schema documents are XML documents that MUST conform to this schema. Note that this schema is based on the XML Schema specification [XML-Schema1][XML-Schema2]. The schema is also present as a separate file at the URI http://www.w3.org/2001/09/P3Pv1.xsd.

 <?xml version='1.0' encoding='UTF-8'?> <schema   xmlns='http://www.w3.org/2001/XMLSchema'   xmlns:p3p='http://www.w3.org/2001/09/P3Pv1'   targetNamespace='http://www.w3.org/2001/09/P3Pv1'   elementFormDefault='qualified'> <!-- Basic P3P Data Type -->  <simpleType name='yes_no'>   <restriction base='string'>    <enumeration value='yes'/>    <enumeration value='no'/>   </restriction>  </simpleType> <!-- *********** Policy Reference *********** --> <!-- ************** META ************** -->  <element name='META'>   <complexType mixed='true'>    <sequence>     <element ref='p3p:POLICY-REFERENCES'/>     <element ref='p3p:POLICIES' minOccurs='0'/>    </sequence>   </complexType>  </element> <!-- ******* POLICY-REFERENCES ******** -->  <element name='POLICY-REFERENCES'>   <complexType>    <sequence>     <element ref='p3p:EXPIRY' minOccurs='0'/>     <element ref='p3p:POLICY-REF' minOccurs='0' maxOccurs='unbounded'/>     <element ref='p3p:HINT' minOccurs='0' maxOccurs='unbounded'/>   </sequence>   </complexType>  </element>  <element name='POLICY-REF'>   <complexType>    <sequence>     <element name='INCLUDE'              minOccurs='0' maxOccurs='unbounded' type='anyURI'/>     <element name='EXCLUDE'              minOccurs='0' maxOccurs='unbounded' type='anyURI'/>     <element name='COOKIE-INCLUDE'              minOccurs='0' maxOccurs='unbounded'              type='p3p:cookie-element'/>     <element name='COOKIE-EXCLUDE'              minOccurs='0' maxOccurs='unbounded'              type='p3p:cookie-element'/>     <element name='METHOD'              minOccurs='0' maxOccurs='unbounded' type='anyURI'/>    </sequence>    <attribute name='about' type='anyURI' use='required'/>   </complexType>  </element>  <complexType name='cookie-element'>   <attribute name='name' type='string' use='optional'/>   <attribute name='value' type='string' use='optional'/>   <attribute name='domain' type='string' use='optional'/>   <attribute name='path' type='string' use='optional'/>  </complexType> <!-- ************* HINT ************* -->  <element name='HINT'>   <complexType>    <attribute name='domain' type='string' use='required'/>    <attribute name='path' type='string' use='required'/>   </complexType>  </element> <!-- ************* EXPIRY ************* -->  <element name='EXPIRY'>   <complexType>    <attribute name='max-age' type='nonNegativeInteger' use='optional'/>    <attribute name='date' type='string' use='optional'/>   </complexType>  </element> <!-- ************ POLICIES ************ -->  <element name='POLICIES'>   <complexType>    <sequence>     <element ref='p3p:EXPIRY' minOccurs='0'/>     <element ref='p3p:DATASCHEMA' minOccurs='0'/>     <element ref='p3p:POLICY' minOccurs='0' maxOccurs='unbounded'/>    </sequence>   </complexType>  </element> <!-- **************** Policy **************** --> <!-- ************* POLICY ************* -->  <element name='POLICY'>   <complexType>    <sequence>     <element ref='p3p:EXTENSION' minOccurs='0' maxOccurs='unbounded'/>     <element ref='p3p:TEST' minOccurs='0'/>     <element ref='p3p:ENTITY'/>     <element ref='p3p:ACCESS'/>     <element ref='p3p:DISPUTES-GROUP' minOccurs='0'/>     <element ref='p3p:STATEMENT' minOccurs='0' maxOccurs='unbounded'/>     <element ref='p3p:EXTENSION' minOccurs='0' maxOccurs='unbounded'/>    </sequence>    <attribute name='discuri' type='anyURI' use='required'/>    <attribute name='opturi' type='anyURI' use='optional'/>    <attribute name='name' type='ID' use='required'/>   </complexType>  </element> <!-- ************* TEST ************* -->  <element name='TEST'>   <complexType/>  </element> <!-- ************* ENTITY ************* -->  <element name='ENTITY'>   <complexType>    <sequence>     <element ref='p3p:EXTENSION' minOccurs='0' maxOccurs='unbounded'/>     <element ref='p3p:DATA-GROUP'/>     <element ref='p3p:EXTENSION' minOccurs='0' maxOccurs='unbounded'/>    </sequence>   </complexType>  </element> <!-- ************* ACCESS ************* -->  <element name='ACCESS'>   <complexType>    <sequence>     <choice>      <element name='nonident' type='p3p:access-value'/>      <element name='ident-contact' type='p3p:access-value'/>      <element name='other-ident' type='p3p:access-value'/>      <element name='contact-and-other' type='p3p:access-value'/>      <element name='all' type='p3p:access-value'/>      <element name='none' type='p3p:access-value'/>     </choice>     <element ref='p3p:EXTENSION' minOccurs='0' maxOccurs='unbounded'/>    </sequence>   </complexType>  </element>  <complexType name='access-value'/> <!-- ************ DISPUTES ************ -->  <element name='DISPUTES-GROUP'>   <complexType>    <sequence>     <element ref='p3p:DISPUTES' maxOccurs='unbounded'/>     <element ref='p3p:EXTENSION' minOccurs='0' maxOccurs='unbounded'/>    </sequence>   </complexType>  </element>  <element name='DISPUTES'>   <complexType>    <sequence>     <element ref='p3p:EXTENSION' minOccurs='0' maxOccurs='unbounded'/>     <choice minOccurs='0'>      <sequence>       <element ref='p3p:LONG-DESCRIPTION'/>       <element ref='p3p:IMG' minOccurs='0'/>       <element ref='p3p:REMEDIES' minOccurs='0'/>       <element ref='p3p:EXTENSION' minOccurs='0' maxOccurs='unbounded'/>      </sequence>      <sequence>       <element ref='p3p:IMG'/>       <element ref='p3p:REMEDIES' minOccurs='0'/>       <element ref='p3p:EXTENSION' minOccurs='0' maxOccurs='unbounded'/>      </sequence>      <sequence>       <element ref='p3p:REMEDIES'/>       <element ref='p3p:EXTENSION' minOccurs='0' maxOccurs='unbounded'/>      </sequence>     </choice>    </sequence>    <attribute name='resolution-type' use='required'>     <simpleType>      <restriction base='string'>       <enumeration value='service'/>       <enumeration value='independent'/>       <enumeration value='court'/>       <enumeration value='law'/>      </restriction>     </simpleType>    </attribute>    <attribute name='service' type='anyURI' use='required'/>    <attribute name='verification' type='string' use='optional'/>    <attribute name='short-description' type='string' use='optional'/>   </complexType>  </element> <!-- ******** LONG-DESCRIPTION ******** -->  <element name='LONG-DESCRIPTION'>   <simpleType>    <restriction base='string'/>   </simpleType>  </element> <!-- ************** IMG *************** -->  <element name='IMG'>   <complexType>    <attribute name='src' type='anyURI' use='required'/>    <attribute name='width' type='nonNegativeInteger' use='optional'/>    <attribute name='height' type='nonNegativeInteger' use='optional'/>    <attribute name='alt' type='string' use='required'/>   </complexType>  </element> <!-- ************ REMEDIES ************ -->  <element name='REMEDIES'>   <complexType>    <sequence>     <choice maxOccurs='unbounded'>      <element name='correct' type='p3p:remedies-value'/>      <element name='money' type='p3p:remedies-value'/>      <element name='law' type='p3p:remedies-value'/>     </choice>     <element ref='p3p:EXTENSION' minOccurs='0' maxOccurs='unbounded'/>    </sequence>   </complexType>  </element>  <complexType name='remedies-value'/> <!-- *********** STATEMENT ************ -->  <element name='STATEMENT'>   <complexType>    <sequence>     <element ref='p3p:EXTENSION' minOccurs='0' maxOccurs='unbounded'/>     <element name='CONSEQUENCE' minOccurs='0' type='string'/>     <element name='NON-IDENTIFIABLE' minOccurs='0'>      <complexType/>     </element>     <element ref='p3p:PURPOSE'/>     <element ref='p3p:RECIPIENT'/>     <element ref='p3p:RETENTION'/>     <element ref='p3p:DATA-GROUP' maxOccurs='unbounded'/>     <element ref='p3p:EXTENSION' minOccurs='0' maxOccurs='unbounded'/>    </sequence>   </complexType>  </element>  <complexType name='non-identifiable'/> <!-- ************ PURPOSE ************* -->  <element name='PURPOSE'>   <complexType>    <sequence>     <choice maxOccurs='unbounded'>      <element name='current' type='p3p:purpose-value'/>      <element name='admin' type='p3p:purpose-value'/>      <element name='develop' type='p3p:purpose-value'/>      <element name='tailoring' type='p3p:purpose-value'/>      <element name='pseudo-analysis' type='p3p:purpose-value'/>      <element name='pseudo-decision' type='p3p:purpose-value'/>      <element name='individual-analysis' type='p3p:purpose-value'/>      <element name='individual-decision' type='p3p:purpose-value'/>      <element name='contact' type='p3p:purpose-value'/>      <element name='historical' type='p3p:purpose-value'/>      <element name='telemarketing' type='p3p:purpose-value'/>      <element name='other-purpose'>       <complexType mixed='true'>        <attribute name='required' use='optional'         type='p3p:required-value'/>       </complexType>      </element>     </choice>     <element ref='p3p:EXTENSION' minOccurs='0' maxOccurs='unbounded'/>    </sequence>   </complexType>  </element>  <simpleType name='required-value'>   <restriction base='string'>    <enumeration value='always'/>    <enumeration value='opt-in'/>    <enumeration value='opt-out'/>   </restriction>  </simpleType>  <complexType name='purpose-value'>   <attribute name='required' use='optional' type='p3p:required-value'/>  </complexType> <!-- *********** RECIPIENT ************ -->  <element name='RECIPIENT'>   <complexType>    <sequence>     <choice maxOccurs='unbounded'>      <element name='ours'>       <complexType>        <sequence>         <element ref='p3p:recipient-description' minOccurs='0'          maxOccurs='unbounded'/>        </sequence>       </complexType>      </element>      <element name='same' type='p3p:recipient-value'/>      <element name='other-recipient' type='p3p:recipient-value'/>      <element name='delivery' type='p3p:recipient-value'/>      <element name='public' type='p3p:recipient-value'/>      <element name='unrelated' type='p3p:recipient-value'/>     </choice>     <element ref='p3p:EXTENSION' minOccurs='0' maxOccurs='unbounded'/>    </sequence>   </complexType>  </element>  <complexType name='recipient-value'>   <sequence>    <element ref='p3p:recipient-description' minOccurs='0'     maxOccurs='unbounded'/>   </sequence>   <attribute name='required' use='optional' type='p3p:required-value'/>  </complexType>  <element name='recipient-description'>   <complexType mixed='true'/>  </element> <!-- *********** RETENTION ************ -->  <element name='RETENTION'>   <complexType>    <sequence>     <choice>      <element name='no-retention' type='p3p:retention-value'/>      <element name='stated-purpose' type='p3p:retention-value'/>      <element name='legal-requirement' type='p3p:retention-value'/>      <element name='indefinitely' type='p3p:retention-value'/>      <element name='business-practices' type='p3p:retention-value'/>     </choice>     <element ref='p3p:EXTENSION' minOccurs='0' maxOccurs='unbounded'/>    </sequence>   </complexType>  </element>  <complexType name='retention-value'/> <!-- ************** DATA ************** -->  <element name='DATA-GROUP'>   <complexType>    <sequence>     <element ref='p3p:DATA' maxOccurs='unbounded'/>     <element ref='p3p:EXTENSION' minOccurs='0' maxOccurs='unbounded'/>    </sequence>    <attribute name='base' type='anyURI'               use='optional' default='http://www.w3.org/TR/P3P/base'/>   </complexType>  </element>  <element name='DATA'>   <complexType mixed='true'>    <sequence minOccurs='0' maxOccurs='unbounded'>     <element ref='p3p:CATEGORIES'/>    </sequence>    <attribute name='ref' type='anyURI' use='required'/>    <attribute name='optional' use='optional'     default='no' type='p3p:yes_no'/>   </complexType>  </element> <!-- ************** Data Schema ************* --> <!-- *********** DATASCHEMA *********** -->  <element name='DATASCHEMA'>   <complexType>    <choice minOccurs='0' maxOccurs='unbounded'>     <element ref='p3p:DATA-DEF'/>     <element ref='p3p:DATA-STRUCT'/>     <element ref='p3p:EXTENSION'/>    </choice>   </complexType>  </element>  <element name='DATA-DEF' type='p3p:data-def'/>  <element name='DATA-STRUCT' type='p3p:data-def'/>  <complexType name='data-def'>   <sequence>    <element ref='p3p:CATEGORIES' minOccurs='0'/>    <element ref='p3p:LONG-DESCRIPTION' minOccurs='0'/>   </sequence>   <attribute name='name' type='ID' use='required'/>   <attribute name='structref' type='anyURI' use='optional'/>   <attribute name='short-description' type='string' use='optional'/>  </complexType> <!-- *********** CATEGORIES *********** -->  <element name='CATEGORIES'>   <complexType>    <choice maxOccurs='unbounded'>     <element name='physical' type='p3p:categories-value'/>     <element name='online' type='p3p:categories-value'/>     <element name='uniqueid' type='p3p:categories-value'/>     <element name='purchase' type='p3p:categories-value'/>     <element name='financial' type='p3p:categories-value'/>     <element name='computer' type='p3p:categories-value'/>     <element name='navigation' type='p3p:categories-value'/>     <element name='interactive' type='p3p:categories-value'/>     <element name='demographic' type='p3p:categories-value'/>     <element name='content' type='p3p:categories-value'/>     <element name='state' type='p3p:categories-value'/>     <element name='political' type='p3p:categories-value'/>     <element name='health' type='p3p:categories-value'/>     <element name='preference' type='p3p:categories-value'/>     <element name='location' type='p3p:categories-value'/>     <element name='government' type='p3p:categories-value'/>     <element name='other-category' type='string'/>    </choice>   </complexType>  </element>  <complexType name='categories-value'/> <!-- *********** EXTENSION ************ -->  <element name='EXTENSION'>   <complexType mixed='true'>    <choice minOccurs='0' maxOccurs='unbounded'>     <any minOccurs='0' maxOccurs='unbounded' processContents='skip'/>    </choice>    <attribute name='optional' use='optional' default='yes'     type='p3p:yes_no'/>   </complexType>  </element> </schema> 

Appendix 5: XML DTD Definition (Non-Normative)

This appendix contains the DTD for policy documents and for data schemas. The DTD is also present as a separate file at the URI http://www.w3.org/2001/09/P3Pv1.dtd.

 <!-- *************** Entities *************** --> <!ENTITY % URI "CDATA"> <!ENTITY % NUMBER "CDATA"> <!-- *********** Policy Reference *********** --> <!-- ************** META ************** --> <!ELEMENT META (#PCDATA  POLICY-REFERENCES  POLICIES)*> <!-- ******* POLICY-REFERENCES ******** --> <!ELEMENT POLICY-REFERENCES (EXPIRY?, POLICY-REF*, HINT*)> <!-- *********** POLICY-REF *********** --> <!ELEMENT POLICY-REF (INCLUDE*,     EXCLUDE*,     METHOD*)> <!ATTLIST POLICY-REF     about %URI; #REQUIRED > <!-- ************** HINT ************** --> <!ELEMENT HINT EMPTY> <!ATTLIST HINT     domain CDATA  #IMPLIED     path   CDATA  #IMPLIED > <!-- ************* EXPIRY ************* --> <!ELEMENT EXPIRY EMPTY> <!ATTLIST EXPIRY     max-age %NUMBER; #IMPLIED     date    CDATA    #IMPLIED > <!-- ************ POLICIES ************ --> <!ELEMENT POLICIES (EXPIRY?, DATASCHEMA?,     POLICY*)> <!-- ***** INCLUDE/EXCLUDE/METHOD ***** --> <!ELEMENT INCLUDE          (#PCDATA)> <!ELEMENT EXCLUDE          (#PCDATA)> <!ELEMENT COOKIE-INCLUDE   EMPTY> <!ATTLIST COOKIE-INCLUDE     name   CDATA  #IMPLIED     value  CDATA  #IMPLIED     domain CDATA  #IMPLIED     path   CDATA  #IMPLIED> <!ELEMENT COOKIE-EXCLUDE   EMPTY> <!ATTLIST COOKIE-EXCLUDE     name   CDATA  #IMPLIED     value  CDATA  #IMPLIED     domain CDATA  #IMPLIED     path   CDATA  #IMPLIED> <!ELEMENT METHOD           (#PCDATA)> <!-- **************** Policy **************** --> <!-- ************* POLICY ************* --> <!ELEMENT POLICY (EXTENSION*,     TEST,     ENTITY,     ACCESS,     DISPUTES-GROUP?,     STATEMENT*,     EXTENSION*)> <!ATTLIST POLICY     name    ID    #REQUIRED     discuri %URI; #REQUIRED     opturi  %URI; #IMPLIED> <!-- ******** TEST ******** --> <!ELEMENT TEST EMPTY> <!-- ************* ENTITY ************* --> <!ELEMENT ENTITY (EXTENSION*, DATA-GROUP, EXTENSION*)> <!-- ************* ACCESS ************* --> <!ELEMENT ACCESS ((nonident      all      contact-and-other      ident-contact      other-ident      none),     EXTENSION*)> <!ELEMENT nonident          EMPTY> <!ELEMENT all               EMPTY> <!ELEMENT contact-and-other EMPTY> <!ELEMENT ident-contact     EMPTY> <!ELEMENT other-ident       EMPTY> <!ELEMENT none              EMPTY> <!-- ************ DISPUTES ************ --> <!ELEMENT DISPUTES-GROUP (DISPUTES+, EXTENSION*)> <!ELEMENT DISPUTES (EXTENSION*,     ( (LONG-DESCRIPTION, IMG?, REMEDIES?, EXTENSION*)        (IMG, REMEDIES?, EXTENSION*)        (REMEDIES, EXTENSION*) )?)> <!ATTLIST DISPUTES     resolution-type   (service  independent  court  law) #REQUIRED     service           %URI;                                 #REQUIRED     verification      CDATA                                 #IMPLIED     short-description CDATA                                 #IMPLIED > <!-- ******** LONG-DESCRIPTION ******** --> <!ELEMENT LONG-DESCRIPTION (#PCDATA)> <!-- ************** IMG *************** --> <!ELEMENT IMG EMPTY> <!ATTLIST IMG     src    %URI;    #REQUIRED     width  %NUMBER; #IMPLIED     height %NUMBER; #IMPLIED     alt    CDATA    #REQUIRED > <!-- ************ REMEDIES ************ --> <!ELEMENT REMEDIES ((correct  money  law)+, EXTENSION*)> <!ELEMENT correct EMPTY> <!ELEMENT money   EMPTY> <!ELEMENT law     EMPTY> <!-- *********** STATEMENT ************ --> <!ELEMENT STATEMENT (EXTENSION*,     NON-IDENTIFIABLE?,     CONSEQUENCE?,     PURPOSE,     RECIPIENT,     RETENTION,     DATA-GROUP+,     EXTENSION*)> <!-- ********** CONSEQUENCE *********** --> <!ELEMENT CONSEQUENCE (#PCDATA)> <!-- ******** NON-IDENTIFIABLE ******** --> <!ELEMENT NON-IDENTIFIABLE (EMPTY)> <!-- ************ PURPOSE ************* --> <!ELEMENT PURPOSE ((current      admin      develop      customization      tailoring      pseudo-analysis      pseudo-decision      individual-analysis      individual-decision      contact      historical      telemarketing      other-purpose)+,     EXTENSION*)> <!ENTITY % pur_att          "required (always  opt-in  opt-out) #IMPLIED"> <!ELEMENT current             EMPTY> <!ATTLIST current             %pur_att;> <!ELEMENT admin               EMPTY> <!ATTLIST admin               %pur_att;> <!ELEMENT develop             EMPTY> <!ATTLIST develop             %pur_att;> <!ELEMENT customization       EMPTY> <!ATTLIST customization       %pur_att;> <!ELEMENT tailoring           EMPTY> <!ATTLIST tailoring           %pur_att;> <!ELEMENT pseudo-analysis     EMPTY> <!ATTLIST pseudo-analysis     %pur_att;> <!ELEMENT pseudo-decision     EMPTY> <!ATTLIST pseudo-decision     %pur_att;> <!ELEMENT individual-analysis EMPTY> <!ATTLIST individual-analysis %pur_att;> <!ELEMENT individual-decision EMPTY> <!ATTLIST individual-decision %pur_att;> <!ELEMENT contact             EMPTY> <!ATTLIST contact             %pur_att;> <!ELEMENT profiling           EMPTY> <!ATTLIST profiling           %pur_att;> <!ELEMENT historical          EMPTY> <!ATTLIST historical          %pur_att;> <!ELEMENT telemarketing       EMPTY> <!ATTLIST telemarketing       %pur_att;> <!ELEMENT other-purpose       (#PCDATA)> <!ATTLIST other-purpose       %pur_att;> <!-- *********** RECIPIENT ************ --> <!ELEMENT RECIPIENT ((ours      same      other-recipient      delivery      public      unrelated)+,     EXTENSION*)> <!ELEMENT ours                  (recipient-description*)> <!ELEMENT same                  (recipient-description*)> <!ATTLIST same                  %pur_att;> <!ELEMENT other-recipient       (recipient-description*)> <!ATTLIST other-recipient       %pur_att;> <!ELEMENT delivery              (recipient-description*)> <!ATTLIST delivery              %pur_att;> <!ELEMENT public                (recipient-description*)> <!ATTLIST public                %pur_att;> <!ELEMENT unrelated             (recipient-description*)> <!ATTLIST unrelated             %pur_att;> <!ELEMENT recipient-description (#PCDATA)> <!-- *********** RETENTION ************ --> <!ELEMENT RETENTION ((no-retention      stated-purpose      legal-requirement      indefinitely      business-practices),     EXTENSION*)> <!ELEMENT no-retention       EMPTY> <!ELEMENT stated-purpose     EMPTY> <!ELEMENT legal-requirement  EMPTY> <!ELEMENT indefinitely       EMPTY> <!ELEMENT business-practices EMPTY> <!-- ************** DATA ************** --> <!ELEMENT DATA-GROUP (DATA+, EXTENSION*)> <!ATTLIST DATA-GROUP     base     %URI;      "http://www.w3.org/TR/P3P/base" > <!ELEMENT DATA (#PCDATA  CATEGORIES)*> <!ATTLIST DATA     ref      %URI;      #REQUIRED     optional (yes  no) "no" > <!-- *********** DATA SCHEMA *********** --> <!ELEMENT DATASCHEMA (DATA-DEF  DATA-STRUCT  EXTENSION)*> <!ELEMENT DATA-DEF    (CATEGORIES?, LONG-DESCRIPTION?)> <!ATTLIST DATA-DEF     name              ID    #REQUIRED     structref         %URI; #IMPLIED     short-description CDATA #IMPLIED  > <!ELEMENT DATA-STRUCT (CATEGORIES?, LONG-DESCRIPTION?)> <!ATTLIST DATA-STRUCT     name              ID    #REQUIRED     structref         %URI; #IMPLIED     short-description CDATA #IMPLIED  > <!-- *********** CATEGORIES *********** --> <!ELEMENT CATEGORIES (physical    online    uniqueid    purchase    financial    computer    navigation    interactive    demographic    content    state    political    health    preference    location    government    other-category)+> <!ELEMENT physical    EMPTY> <!ELEMENT online      EMPTY> <!ELEMENT uniqueid    EMPTY> <!ELEMENT purchase    EMPTY> <!ELEMENT financial   EMPTY> <!ELEMENT computer    EMPTY> <!ELEMENT navigation  EMPTY> <!ELEMENT interactive EMPTY> <!ELEMENT demographic EMPTY> <!ELEMENT content     EMPTY> <!ELEMENT state       EMPTY> <!ELEMENT political   EMPTY> <!ELEMENT health      EMPTY> <!ELEMENT preference  EMPTY> <!ELEMENT location    EMPTY> <!ELEMENT government  EMPTY> <!ELEMENT other       EMPTY> <!-- *********** EXTENSION ************ --> <!ELEMENT EXTENSION (#PCDATA)> <!ATTLIST EXTENSION     optional (yes  no) "yes" > 

Appendix 6: ABNF Notation (Non-Normative)

The formal grammar of P3P is given in this specification using a slight modification of [ABNF]. The following is a simple description of the ABNF.

name = (elements)

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.


at least <a> and at most <b> occurrences of the element.

( 1*4<element> means one to four elements. )


exactly <a> occurrences of the element.

( 4<element> means exactly 4 elements. )


<a> or more elements

( 4*<element> means 4 or more elements. )


0 to <b> elements.

( *5<element> means 0 to 5 elements. )


0 or more elements.

( *<element> means 0 to infinite elements. )


optional element, equivalent to *1(element).

( [element] means 0 or 1 element. )

"string" or 'string'

matches the literal string given inside double quotes.

Other notations used in the productions are:

; or /* ... */


Appendix 7: P3P Guiding Principles (Non-Normative)

This appendix describes the intent of P3P development and recommends guidelines regarding the responsible use of P3P technology. An earlier version was published in the W3C Note "P3P Guiding Principles."

The Platform for Privacy Preferences Project (P3P) has been designed to be flexible and support a diverse set of user preferences, public policies, service provider polices, and applications. This flexibility will provide opportunities for using P3P in a wide variety of innovative ways that its designers had not imagined. The P3P Guiding Principles were created in order to: express the intentions of the members of the P3P working groups when designing this technology and suggest how P3P can be used most effectively in order to maximize privacy and user confidence and trust on the Web. In keeping with our goal of flexibility, this document does not place requirements upon any party. Rather, it makes recommendations about 1) what should be done to be consistent with the intentions of the P3P designers and 2) how to maximize user confidence in P3P implementations and Web services. P3P was intended to help protect privacy on the Web. We encourage the organizations, individuals, policy- makers and companies who use P3P to embrace the guiding principles in order to reach this goal.

Information Privacy

P3P has been designed to promote privacy and trust on the Web by enabling service providers to disclose their information practices, and enabling individuals to make informed decisions about the collection and use of their personal information. P3P user agents work on behalf of individuals to reach agreements with service providers about the collection and use of personal information. Trust is built upon the mutual understanding that each party will respect the agreement reached.

Service providers should preserve trust and protect privacy by applying relevant laws and principles of data protection and privacy to their information practices. The following is a list of privacy principles and guidelines that helped inform the development of P3P and may be useful to those who use P3P:

  • CMA Code of Ethics & Standards of Practice: Protection of Personal Privacy

  • 1981 Council of Europe Convention For the Protection of Individuals with Regard to Automatic Processing of Personal Data

  • CSA ”Q830-96 Model Code for the Protection of Personal Information

  • Directive 95/46/EC of the European Parliament and of the Council of 24 October 1995 on the protection of individuals with regard to the processing of personal data and on the free movement of such data

  • The DMA's Marketing Online Privacy Principles and Guidance and The DMA Guidelines for Ethical Business Practice

  • OECD Guidelines on the Protection of Privacy and Transborder Flows of Personal Data

  • Online Privacy Alliance Guidelines for Online Privacy Policies

In addition, service providers and P3P implementers should recognize and address the special concerns surrounding children's privacy.

Notice and Communication

Service providers should provide timely and effective notices of their information practices, and user agents should provide effective tools for users to access these notices and make decisions based on them.

Service providers should:

  • Communicate explicitly about data collection and use, expressing the purpose for which personal information is collected and the extent to which it may be shared.

  • Use P3P privacy policies to communicate about all information they propose to collect through a Web interaction.

  • Prominently post clear, human-readable privacy policies.

User agents should:

  • Provide mechanisms for displaying a service's information practices to users.

  • Provide users an option that allows them to easily preview and agree to or reject each transfer of personal information that the user agent facilitates.

  • Not be configured by default to transfer personal information to a service provider without the user's consent .

  • Inform users about the privacy- related options offered by the user agent.

Choice and Control

Users should be given the ability to make meaningful choices about the collection, use, and disclosure of personal information. Users should retain control over their personal information and decide the conditions under which they will share it.

Service providers should:

  • Limit their requests to information necessary for fulfilling the level of service desired by the user. This will reduce user frustration, increase trust, and enable relationships with many users, including those who may wish to have an anonymous, pseudonymous, customized, or personalized relationship with the service.

  • Obtain informed consent prior to the collection and use of personal information.

  • Provide information about the ability to review and if appropriate correct personal information.

User agents should:

  • Include configuration tools that allow users to customize their preferences.

  • Allow users to import and customize P3P preferences from trusted parties.

  • Present configuration options to users in a way that is neutral or biased towards privacy.

  • Be usable without requiring the user to store user personal information as part of the installation or configuration process.

Fairness and Integrity

Service providers should treat users and their personal information with fairness and integrity. This is essential for protecting privacy and promoting trust.

Service providers should:

  • Accurately represent their information practices in a clear and unambiguous manner ”never with the intention of misleading users.

  • Use information only for the stated purpose and retain it only as long as necessary.

  • Ensure that information is accurate, complete, and up-to-date.

  • Disclose accountability and means for recourse.

  • For as long as information is retained, continue to treat information according to the policy in effect when the information was collected, unless users give their informed consent to a new policy.

User agents should:

  • Act only on behalf of the user according to the preferences specified by the user.

  • Accurately represent the practices of the service provider.


While P3P itself does not include security mechanisms, it is intended to be used in conjunction with security tools. Users' personal information should always be protected with reasonable security safeguards in keeping with the sensitivity of the information.

Service providers should:

  • Provide mechanisms for protecting any personal information they collect.

  • Use appropriate trusted protocols for the secure transmission of data.

User agents should:

  • Provide mechanisms for protecting the personal information that users store in any data repositories maintained by the agent.

  • Use appropriate trusted protocols for the secure transmission of data.

  • Warn users when an insecure transport mechanism is being used.

Appendix 8: 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), Eric Brunner (Engage), Joe Coco (Microsoft), Brooks Dobbs (DoubleClick), Rajeev Dujari (Microsoft), Matthias Enzmann (GMD), Patrick Feng (RPI), Aaron Goldfeder (Microsoft), Dan Jaye (Engage), Marit Koehntopp (Privacy Commission of Land Schleswig-Holstein, Germany), Yuichi Koike (NEC/W3C), Yusuke Koizumi (ENC), Daniel LaLiberte (Crystaliz), Marc Langheinrich (NEC/ETH Zurich), Daniel Lim (PrivacyBank), Ran Lotenberg (IDcide), Massimo Marchiori (W3C/MIT/UNIVE), Christine McKenna (Phone.com, Inc.), Mark Nottingham (Akamai), Paul Perry (Microsoft), Jules Polonetsky (DoubleClick), Martin Presler-Marshall (IBM), Joel Reidenberg (Fordham Law School), Dave Remy (Geotrust), Ari Schwartz (CDT), Noboru Shimizu (ENC), Rob Smibert (Jotter Technologies Inc.), Tri Tran (AvenueA), Mark Uhrmacher (DoubleClick), Danny Weitzner (W3C), Michael Wallent (Microsoft), Rigo Wenning (W3C), Betty Whitaker (NCR), Allen Wyke (Engage), Kevin Yen (Netscape), 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 (NEC/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 Mar chiori (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).

Finally, Appendix 7 is drawn from the W3C Note "P3P Guiding Principles," whose signatories are: Azer Bestavros (Bowne Internet Solutions), Ann Cavoukian (Information and Privacy Commission Ontario Canada), Lorrie Faith Cranor (AT&T Labs-Research), Josef Dietl (W3C), Daniel Jaye (Engage Technologies), Marit K hntopp (Land Schleswig-Holstein), Tara Lemmey (Narrowline; TRUSTe), Steven Lucas (MatchLogic), Massimo Marchiori (W3C/MIT), Dave Marvit (Fujitsu Labs), Maclen Marvit (Narrowline Inc.), Yossi Matias (Tel Aviv University), James S. Miller (MIT), Deirdre Mulligan (Center for Democracy and Technology), Joseph Reagle (W3C), Drummond Reed (Intermind), Lawrence C. Stewart (Open Market, Inc.).

Change log from the 15 December 2000 Candidate Recommendation:

  • Fixed errors in examples and typos throughout

  • Made many minor (non-substantive) wording changes

  • Added 2.4.7 Absence of Policy Reference File

  • Added paragraph to intro to 3.2 to explain requirements for handling policies containing errors

  • Changed categories of some of the elements of the postal structure and the dynamic.clickstream.clientip element in the base data schema

  • Changed 3.3.3 to clarify how the NON-IDENTIFIABLE element is aggregated across statements

  • Added language to 4.2 to clarify user agent behavior when encountering duplicate or unknown tokens in compact policies

  • Added section 2.4.8 Asynchronous Evaluation

  • Change other-purpose token from OPT to OTP in 4.2 Compact Policies

  • Added language to 2.4.1 to clarify the precedence of multiple policy reference files and make section more clear generally

  • Added definitions of data structure and data schema to 1.3 Terminology

  • Added new data element user.login to base data schema

  • Many wording changes throughout related to the term "identifiable"

  • Changed language in to state that policy reference files are applied relative to the DNS hosts that reference them

  • Changed the intro to 4 to clarify compact policy scope

  • Changed definition of the current purpose in 3.3.4 and removed the required attribute from the current purpose

  • Removed the customization purpose in 3.3.4

  • Changed the definition of the tailoring purpose in 3.3.4

  • The use of HTTP headers for determining policy and policy reference file expiry was eliminated

  • EXPIRY element moved to child of POLICIES element (instead of child of POLICY element)

  • was changed to clarify expiry rules for cookie policies

  • Syntax of COOKIE-INCLUDE and COOKIE-EXCLUDE changed

  • POLICY elements must now be contained within a POLICIES element and must have a name attribute

  • Changes to 2.4.3 to clarify the meaning of the safezone

  • New section 2.2.4 HTTP ports and other protocols


  • New section Policy Reference Hints

  • Added language to 2.2.2 and 2.2.3 to clarify that when the policyref attribute is a relative URI, that URI is interpreted relative to the request URI

  • Added language to to clarify the significance of order in policy reference files

  • Added language to and to clarify the use of the METHOD element

  • An embedded DATASCHEMA is now child of POLICIES rather than of POLICY

Mobile Location Servies(c) The Definitive Guide
Software Project Management in Practice
ISBN: 0201737213
EAN: 2147483647
Year: 2005
Pages: 150
Authors: Pankaj Jalote

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net