- From: Martin Presler-Marshall <mpresler@us.ibm.com>
- Date: Wed, 13 Feb 2002 08:45:58 -0500
- To: www-p3p-public-comments@w3.org
This is indeed a bug, which I was previously unaware of. I will get a
new version sent to alphaWorks soon.
-- Martin
Martin Presler-Marshall - WebSphere Portal Server Performance & Privacy
E-mail: mpresler@us.ibm.com AIM: jhreingold
Phone: (919) 254-7819 (tie-line 444-7819) Fax: (919) 254-6430 (tie-line
444-6430)
Clifford Lyon
<Clifford.Lyon@c To: "'www-p3p-dev@w3.org'" <www-p3p-dev@w3.org>
net.com> cc:
Sent by: Subject: FW: compact policy required attr
www-p3p-dev-requ
est@w3.org
02/12/2002 01:52
PM
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 Wednesday, 13 February 2002 08:46:07 UTC