171 2003-03-10 21:41:00 +0000 standardize STATEMENT name attribute based on IBM extension 2008-12-02 22:41:08 +0000 1 1 1 Unclassified P3P Vocabulary extensions unspecified Other other RESOLVED FIXED P2 normal P3P1.1 1 lorrie rigo zzz oldest_to_newest 407 0 lorrie 2003-03-10 21:41:00 +0000 The IBM P3P Policy Editor defines a P3P extension to assign a name attribute to the STATEMENT element. This is useful for the editor itself, but it has also proven useful for user agents when they display policy summaries to users. We should consider making this extension an "official" part of the P3P specification -- probably by referencing the extension in v1.1 and turning it into a regular attribute (without using the extension mechanism ) in future versions. 471 1 lorrie 2003-05-07 13:01:33 +0000 At the 7 May P3P specification working group conference call we agreed to adopt this extension as a P3P 1.1 extension. The editor is assigned to incorporate this into the P3P1.1 working draft. 1271 2 rigo 2004-02-04 03:52:58 +0000 While editing the Specification and getting the remarks from Matthias Schunter at http://lists.w3.org/Archives/Member/w3c-p3p-specification/2004Feb/0001.html I realized that this was superseded finally by the consent choices draft. So I re-open this bug for the 4 feb call. 1693 3 rigo 2004-04-19 11:00:03 +0000 http://lists.w3.org/Archives/Public/public-p3p-spec/2004Apr/0000.html =================================================================== On March 30th call we were trying to sort out the status of bug 171. Looking at section 3.3.2 in the 10 February working draft http://www.w3.org/TR/P3P11 it appears that this has already been solved. The STATEMENT-GROUP element takes a name attribute, and we explain that this is equivalent to the IBM extension. Is there something else here I'm missing. If so, please set me straight. If not, I'm going to close this bug. Lorrie =================================================================== Having received no remark, I have closed the bug on 19 April Rigo