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

MINUTES: FRIDAY 18 June P3P Spec Call

From: Lorrie Cranor <lorrie+@cs.cmu.edu>
Date: Fri, 18 Jun 2004 13:53:58 -0400
Message-Id: <7950E401-C150-11D8-A914-000A95DA3F5A@cs.cmu.edu>
To: public-p3p-spec <public-p3p-spec@w3.org>

Brooks Dobbs
Lorrie Cranor
Rigo Wenning (scribe)
Giles Hogben
Jack Humphrey
Serge Egelman
David Stampley

1. primary purpose specification
Please review draft

Rigo suggested to put UA strings into that UA section. Lorrie wanted to 
as all should be inline.

User agent strings should go to the table and the sentence "The long
descriptions are to be used for aiding the policy authors, while the 
in bold are what is to be displayed to the end user." should be removed.

Giles critized web browsing as too general. Lorrie explained the 
Giles and Rigo said that customization is a secondary purpose. Lorrie
with use cases, but finally gave up.

Big opportunity for confusing said Giles and should have a good 
We have a mixture of primary in purpose. The idea is to expand current.
Giles adding all of purpose to ppurpose. Lorrie said, most of the 
were left out in 1.0 as we said, it is already coverd by current.

Suggestion is to expand and explain that we only expand the <current> 

Giles: login/account/register overlapping. [Discussion]
login and account management might be perceived differently by the user.
Dave and Giles and Lorrie want to merge with register. Dave said also 
account management is AM.
ACTION Lorrie: Provide new merged definition for account

Giles: bank should be something general like financial.
Suggestion <finmgt> was decided.

Giles: gambling and gaming
Brooks was origin of that, still justified.

Rigo suggested software-downloads
Dave suggested <downloads> and everybody agreed. Definition would be 
ACTION: Lorrie and Serge: Try a new definition and distribute new draft.

Next call 22 Juin at 11am EST (normal time)

2. XML schema stuff - we need more input on whether it makes
sense to make this change in P3P1.1 despite backwards compatibility

Giles has made a much nicer way of doing customized schemas, problem is
some minor backwards compatibility issues. It will only break IBM's 
Giles said it wouldn't even violate backwards compatibility guidelines.
Lorrie, view lines to change in Privacy Bird and JRC.
Giles said that research is using it.

ACTION Lorrie contact all IBM to get feedback about switching to XML 

3 Last call
After primary purpose and Schema stuff is done, we are ready for Last 
expects last call for July.
Received on Friday, 18 June 2004 13:54:24 UTC

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