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

Re: Problems with the P3P Schema

From: Yuichi Koike <koike@ay.jp.nec.com>
Date: Wed, 22 Sep 2004 17:02:01 +0900
Message-ID: <005b01c4a07a$70e7cbf0$3a95380a@MYCAL>
To: "Giles Hogben" <giles.hogben@jrc.it>, <public-p3p-spec@w3.org>
Cc: "'Lorrie Cranor'" <lorrie@cs.cmu.edu>, "'Rigo Wenning'" <rigo@w3.org>

Hello,

> OK sorry - we missed the type reference.
> There still seems to be a problem with the entity element however.
> In the DTD, it allows for an extension child, but in the schema, it does
> not.
> 
> This could be a problem for the XSD data schema, because if it is going to
> be useful, it would need to be applied also within the entity element...
> Do you think we could add the possibility of an extension here?

In the P3P specification document, there are three ways 
to define the element. ABNF (embedded in the document), 
XML schema (normative appendix), DTD (informative appendix).

DTD, ABNF, and XML schema allow extension child
in <DATA-GROUP> element in <STATEMENT>.

ABNF and XML schema do NOT allow extension child
in <DATA-GROUP> element in <ENTITY>.
However, DTD allows.

This is because ability of DTD is limited.
DTD cannot give different definitions to 
DATA-GROUP in ENTITY and DATA-GROUP in STATEMENT, 
while ABNF and XML schema can.

I think the intention of the P3P specification working group is 
closer to what ABNF and XML schema say.

Thanks,

--
Yuichi Koike ( koike@ay.jp.nec.com )
NEC Corporation
Internet System Laboratory


> Thanks
> 
> Giles
> 
> >**-----Original Message-----
> >**From: Yuichi Koike [mailto:koike@ay.jp.nec.com] 
> >**Sent: 22 September 2004 04:00
> >**To: Giles Hogben; public-p3p-spec@w3.org
> >**Subject: Re: Problems with the P3P Schema
> >**
> >**
> >**Hello,
> >**
> >**
> >**>    ***   <element name='DATA-GROUP' type='p3p:data-group-type'
> >**>  maxOccurs='unbounded'/>  ****
> >**
> >**The above lines says:
> >**"The element type of <DATA-GROP> is 'p3p:data-group-type' ".
> >**
> >**The 'data-group-type' is defined in other part of the schema.
> >**
> >** <complexType name='data-group-type'>
> >**  <sequence>
> >**   <element ref='p3p:EXTENSION' minOccurs='0' maxOccurs='unbounded'/>
> >**   <element name='DATA' type='p3p:data-in-statement' 
> >**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>
> >**
> >**It says that <DATA-GROUP> element has
> >**    - 0 or more EXTENSION elements,
> >**    - one or more than one DATA elements,
> >**    - 0 or more EXTENSION elements 
> >**as its children.
> >**
> >**> 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?).
> >**
> >**P3P validator uses XSV (XML Schema Validator) as 
> >**sub module. I think it is working well.
> >**
> >**http://www.w3.org/2001/03/webdata/xsv?docAddrs=http%3A%2F%2Fw
> >**ww.att.com%2Fprivacy%2Fp3p2.xml&warnings=on&style=xsl
> >**
> >**Regards,
> >**
> >**--
> >**Yuichi Koike ( koike@ay.jp.nec.com )
> >**NEC Corporation
> >**Internet System Laboratory
> >**
> >**
> 
Received on Wednesday, 22 September 2004 08:02:38 GMT

This archive was generated by hypermail 2.2.0+W3C-0.1 : Wednesday, 22 September 2004 08:02:38 GMT