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

Re: no extension element allowed in entity element

From: Lorrie Cranor <lorrie+@cs.cmu.edu>
Date: Wed, 29 Sep 2004 13:28:59 -0400
Message-Id: <0C2832D5-123D-11D9-B166-000A95DA3F5A@cs.cmu.edu>
Cc: 'public-p3p-spec' <public-p3p-spec@w3.org>
To: Lorrie Cranor <lorrie+@cs.cmu.edu>

An answer to my own question just occurred to me... why does the 
extension have to go inside the data group element? Why can't we put it 
in the ENTITY element itself?


On Sep 29, 2004, at 11:51 AM, Lorrie Cranor wrote:

> We're working on a few final schema-related concerns...
> Giles points out:
>> 	Currently there is no extension element allowed inside data group 
>> elements
>> in the entity element (describing business data of entity) - this is
>> according to the XML schema. Should we break the schema and allow 
>> this -
>> otherwise how can we implement the new schema - only for data 
>> elements seems
>> unworkable.
> If it doesn't break any existing user agents (I don't think it will) 
> then I would be inclined to go ahead with this. My main concern is 
> that it triggers a change in the name space, which I was trying to 
> avoid, although it may not be critical given the lack of checking done 
> by most of the existing user agents. What other options do we have?
> Lorrie
Received on Wednesday, 29 September 2004 17:29:39 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:02:19 UTC