- From: Giles Hogben <giles.hogben@jrc.it>
- Date: Wed, 06 Jul 2005 09:27:46 +0200
- To: "'Rigo Wenning'" <rigo@w3.org>, "'Lorrie Cranor'" <lorrie@cs.cmu.edu>
- Cc: public-p3p-spec@w3.org
I would like to propose a simplification which there is still time to put in the spec. We include categories in the Base Data Schema for backward compatibility - but we disallow them in custom schemas from now on. If you want to put in broad categories, there's nothing stopping you - you just have to make them into data elements which subsume the narrower categories. There's no need for a completely different and confusing syntax. Yes it's because of XSD. Basically because each data element takes a subset of categories from a global set, this is only possible with a custom data type (or at least that's the only way we could find to do it and we consulted some XML lists)... -----Original Message----- From: public-p3p-spec-request@w3.org [mailto:public-p3p-spec-request@w3.org] On Behalf Of Rigo Wenning Sent: Tuesday, July 05, 2005 17:13 To: Giles Hogben Cc: public-p3p-spec@w3.org Subject: Re: Trouble with data schema Am Tuesday 05 July 2005 16:17 verlautbarte Giles Hogben : > Hmmm you're right that is what the XSD says - then there is an error > with the spec examples - the problem I now remember was with XSD - how > to do a global data type which you can then specialize. Questions: 1/ Should I correct the examples? 2/ is the issue of specializing xsd a prob of xsd? Best, Rigo
Received on Wednesday, 6 July 2005 07:28:17 UTC