W3C home > Mailing lists > Public > public-p3p-spec@w3.org > September 2004

Re: Problems with the P3P Schema

From: Lorrie Cranor <lorrie+@cs.cmu.edu>
Date: Tue, 21 Sep 2004 13:47:09 -0400
Message-Id: <42A6BFE4-0BF6-11D9-B94B-000A95DA3F5A@cs.cmu.edu>
Cc: <public-p3p-spec@w3.org>
To: Massimo Marchiori <massimo@w3.org>, Giles Hogben <giles.hogben@jrc.it>


On Sep 21, 2004, at 11:20 AM, Giles Hogben wrote:

>
> Hi,
> A couple of important points arising from trying to finalize the Data 
> Schema
> Stuff
>
> 1. I would like to propose that we make the Base Data Schema 
> Definition a
> self contained section of the spec - i.e. that we move sections 3.3.7 
> and
> 3.4 to within the new Data Schema definition.

I'm not sure what you are asking... these section numbers in 
http://www.w3.org/TR/2004/WD-P3P11-20040720/ don't appear to correspond 
to sections related to the data schema.

>
> 2. In attempting to finalise the Base Data Schema using XML Schema, 
> Rigo and
> I have discovered that the P3P XML Schema (Normative :)) **appears to 
> be
> broken**.
>

Massimo, you created this schema, right? Can you take a look at this 
please?

> In particular:
>
> <!-- *********** STATEMENT ************ -->
>  <element name='STATEMENT'>
>   <complexType>
>    <sequence>
>     <element ref='p3p:EXTENSION' minOccurs='0' maxOccurs='unbounded'/>
>     <element name='CONSEQUENCE' minOccurs='0' type='string'/>
>     <choice>
>      <sequence>
>       <element ref='p3p:PURPOSE'/>
>       <element ref='p3p:RECIPIENT'/>
>       <element ref='p3p:RETENTION'/>
>    ***   <element name='DATA-GROUP' type='p3p:data-group-type'
> maxOccurs='unbounded'/>  ****
>      </sequence>
>      <sequence>
>       <element name='NON-IDENTIFIABLE'/>
>       <element ref='p3p:PURPOSE' minOccurs='0'/>
>       <element ref='p3p:RECIPIENT' minOccurs='0'/>
>       <element ref='p3p:RETENTION' minOccurs='0'/>
>       <element name='DATA-GROUP' type='p3p:data-group-type' 
> minOccurs='0'
> maxOccurs='unbounded'/>
>      </sequence>
>     </choice>
>     <element ref='p3p:EXTENSION' minOccurs='0' maxOccurs='unbounded'/>
>    </sequence>
>   </complexType>
>  </element>
>
> Data Group is defined "locally" (i.e. not globally). In doing so, it
> A. Does not define its allowed  children, and in particular no 
> extension
> element.
> B. Does not define any semantic equivalence with the data-group 
> element used
> under entity (which is also locally defined).
>
> This is a problem not only for the XML BDS but as far as I can see, it
> should mean that no real P3P policy would validate against the schema. 
> IMHO
> - it should be fixed before 1.1. esp if the schema is THE normative
> definition. We should also rationalize this with our backward 
> compatibility
> requirements.
>
> There may be other errors. We need to take a real policy and make sure 
> it
> really does validate with a schema validator (has someone already tried
> this?).
>

I don't think anyone has tried to validate with a schema validator. 
Giles, can you do this?

Let's make sure we understand the problem and then we will have to 
figure out how to deal with backwards compatibility. If your assessment 
is right then clearly we need to fix this as an errata, but we will 
need to discuss the best way to do this.

Lorrie
Received on Tuesday, 21 September 2004 17:51:59 GMT

This archive was generated by hypermail 2.2.0+W3C-0.1 : Tuesday, 21 September 2004 17:52:00 GMT