W3C home > Mailing lists > Public > www-p3p-dev@w3.org > February 2002

FW: compact policy required attr

From: Clifford Lyon <Clifford.Lyon@cnet.com>
Date: Tue, 12 Feb 2002 10:52:28 -0800
Message-ID: <F5E5CB897FCA1A4BAC3FD38CEBA1A644021D2CCF@zdnet08.zdz.cnwk>
To: "'www-p3p-dev@w3.org'" <www-p3p-dev@w3.org>
cc'ing dev on implementation issue.

-----Original Message-----
From: Clifford Lyon 
Sent: Tuesday, February 12, 2002 1:45 PM
To: 'www-p3p-public-comments@w3.org'
Subject: compact policy required attr


Hi,

This question about compact syntax comes from using the IBM policy editor 1.9.

I noticed that if I create a policy with a "Cookies" statement, containing some elements about the use of cookies, the "i", "o", or "a" is set as expected, according the required element in the corresponding purpose in the xml policy.

However, when I add a new "group" (statement) all of the compact purpose tokens become "a", and cannot be changed. I thought the tool might be setting the required attr according to the maximum required attr for a given purpose across all statements - but it wasn't - just adding a second empty statement w/o any purpose changes all the purpose requirements to "a". The xml policy still shows "opt-in" for the purpose.

I wanted to make sure that this is a bug in the tool, and that its not the case that for policies with multiple statements, the purpose tokens in a compact policy must be required.

Regards,

Cliff Lyon
Received on Tuesday, 12 February 2002 13:52:31 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 18 June 2010 00:12:47 GMT