P3P 1.1 wants to be backwards compatible. Therefore the P3P Specification Working Group used the Extension-mechanism in P3P 1.0 to define the new features of P3P 1.1.
In order to understand the P3P 1.1 Application, you will need this XML Schema and the XML Schema of P3P 1.0. A XML version of this file can be found at http://www.w3.org/2004/02/P3Pv11.xsd.
Last update by $Author: rigo $ $Date: 2004/02/10 13:05:05 $
<?xml version='1.0' encoding='UTF-8'?> <schema xmlns='http://www.w3.org/2001/XMLSchema' xmlns:p3p='http://www.w3.org/2004/02/P3Pv11' targetNamespace='http://www.w3.org/2004/02/P3Pv11' elementFormDefault='qualified'> <!-- p3p attribute --> <attribute name='p3p' type='anyURI'> <annotation> <documentation> <div xmlns='http://www.w3.org/1999/xhtml'> <p>The P3P-generic attribute takes a URI as its value.</p> <p>The meaning is that a P3P document describing the privacy policy relevant to this element may be found at the URI given.</p> </div> </documentation> </annotation> </attribute> <simpleType name='consent_value'> <restriction base='string'> <enumeration value='opt-in'/> <enumeration value='opt-out'/> <enumeration value='always'/> <enumeration value='mixed'/> </restriction> </simpleType> <element name='STATEMENT-GROUP-DEF'> <complexType> <attribute name='id' type='ID' use='required'/> <attribute name='short-description' type='p3p:consent_value' use='optional'/> </complexType> </element> <element name='STATEMENT-GROUP'> <complexType> <attribute name='id' type='IDREF' use='required'/> <attribute name='name' type='string' use='required'/> <attribute name='short-description ' type='string' use='optional'/> </complexType> </element> </schema>