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

Re: comments on latest working draft

From: Rigo Wenning <rigo@w3.org>
Date: Thu, 10 Jun 2004 18:04:50 +0200
To: public-p3p-spec@w3.org
Cc: Lorrie Cranor <lorrie@cs.cmu.edu>
Message-Id: <200406101804.51242.rigo@w3.org>

Am Tuesday 25 May 2004 21:52 verlautbarte Lorrie Cranor :
> I read through the latest working draft
> http://www.w3.org/TR/2004/WD-P3P11-20040427/ and found a number of
> minor errors that need to be fixed:
>
> 1.1.1 The list of enhancements is incomplete. It also needs to
> include: - An optional element for declaring the jurisdiction of data
> recipients - Definitions of identified, identifiable, linked, and
> linkable data - An optional element for declaring domain
> relationships
> - A compact version of the STATEMENT element for use in compact
> policies
>
> It would also be good to list the relevant sections for all of these
> items

Done
>
> 1.3 change reference to my book to a reference in the non-normative
> references appendix
>
Done

> 1.3.1 last sentence, there is a quoted phrase at the end of the
> sentence - remove quotes and italicize instead.

Done
>
> 2.3.2.7 In first sentence of paragraph hyperlink "linked" to 1.3.4
>
Done

> 2.3.2.9
>
> The section about Domain Relationships --> This section
>
> modifications would allow --> modifications allow
>
> change hyperlink to issues to a reference in the non-normative
> references appendix

Done
>
> 2.3.2.9.1 extension element to --> extension to

Done
>
> the extension needs an xmlns (in BNF and examples)
Done

>
> 2.3.2.9.3 when only using --> when using

Done
>
> 2.5 This doesn't appear to reflect the changes I proposed in my April
> 9 email
>
Hi hi, got your first version of Draft. Should be fixed now

> 3.2.3 required. or mixed. --> required or mixed 

Pattern not found: required. or mixed 

But I think we deprecated the use of Group-Info as it is already 
included in the grouping mechanism..

>
> 3.3.2 one implementers authoring --> one implementer's authoring

Done
>
> 3.3.6.1 need xmlns attribute and long and short description in BNF
> and examples

Done

>
> 4 strike first paragraph (repeated in second paragraph)
Done
>
> 4.7 Add: See Section 6.4 for guidelines designed to reduce the chance
> that a P3P user agent will accept an invalid compact policy.

We decided to remove 4.7, no? At least this is what the Spec says at the 
moment. I think it is already said in 6.4, no?

>
> 6.2 are available at ??? --> will be posted on the W3C web site when
> they become available.

Done
>
> remove the . at the end of the money definition
Done
>
> add the CATEGORIES label to the first column of demographic
Done
>
> CATEGORIES optional -- the wording here is stated as "the data
> element" but I think "this data" would make more sense... I wasn't
> involved in this discussion

A good question to the list..
>
> Appendix 9 - add P3P 1.1 working group contributors in a new
> paragraph at the beginning

Done

>
> Changelog - spell check, I see a bunch of typos
>
>
> Also we need to add the following (basically a summary of our
> backwards compatibility guidelines documenting that we followed
> them):
>
> 1.1.7 Backwards Compatibility
>
> P3P 1.1 has been designed so that P3P 1.0 user agents can process P3P
> 1.1 policies and  policy reference files. This implies both that the
> P3P 1.1 policies and  policy reference files are fully compliant with
> the P3P 1.0 XML schema,  and that the semantics of these files will
> not be misinterpreted by a  user agent that interprets them according
> to the P3P 1.0  specification. All new syntax introduced in P3P 1.1
> has been introduced as optional extensions using the P3P 1.0
> extension mechanism. Changes to requirements or definitions
> introduced in P3P 1.1 add clarity where the P3P 1.0 specification is
> ambiguous, but do not cause a particular P3P vocabulary element to
> have different meanings in P3P 1.0 and P3P 1.1. In addition, some new
> requirements or features have been introduced in the P3P 1.1 
> specification that do not impact the ability of P3P 1.0 user agents
> to  process P3P 1.1 policies and policy reference files.
Done 

Rigo
Received on Thursday, 10 June 2004 12:10:11 EDT

This archive was generated by hypermail pre-2.1.9 : Thursday, 10 June 2004 12:10:12 EDT