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

RE: generic attribute

From: Patrick C. K. Hung <cshck@cs.ust.hk>
Date: Wed, 11 Feb 2004 22:29:45 +0800
To: "'Lorrie Cranor'" <lorrie@cs.cmu.edu>, "'public-p3p-spec'" <public-p3p-spec@w3.org>
Message-ID: <00e401c3f0ab$7f49c240$5b80598f@win2k.cs.ust.hk>

Referring to what Lorrie's suggestion, one of the possible solutions to
define the companion attribute may be related to some semantic and workflow
technologies such as DAML-S or only a plain English description. If so, is
there a need to explore semantic stuff for this generic attribute?

-----Original Message-----
From: public-p3p-spec-request@w3.org [mailto:public-p3p-spec-request@w3.org]
On Behalf Of Lorrie Cranor
Sent: Wednesday, February 11, 2004 6:51 AM
To: 'public-p3p-spec'
Subject: generic attribute

I still have concerns about 2.5 The P3P Generic Attribute for XML 
The language is better than the previous draft, but I am still 
concerned about "the policy MUST describe all data collection performed 
as a result of  processing the element carrying the P3P Generic 
Attribute. The policy also MUST describe all data collection performed 
as a result of processing of all  subelements ."

The notion of binding was hairy enough when dealing with HTTP, but at 
least HTTP methods are somewhat well defined and we usually know what 
it  means for a user agent to dereference a URI (although I could 
imagine this coming back to haunt us later, but so far so good). But I 
don't think we know what it means to "process" an arbitrary XML 
element. Indeed, I think we can expect that different tools may process 
the same XML element in different ways.

Here is a hypothetical example of the problem:

Suppose I have an XML directory (name, address, phone number, fax, URI, 
etc.). Let's say I put a generic P3P tag in an element that contains a 
single directory entry. What does it mean to process this element? A 
user agent might process it by
a) displaying the entry itself in a browser.
b) dereferencing the URI in the entry and displaying it in a browser
c) dialing a phone
d) generating a form letter, putting the name and address into the form 
letter, sending the form letter to a device that prints it and puts it 
in the postal mail
e) generating a fax and sending it to the fax number

There might be no data collection associated with a. b might result in 
the collection of clickstream data. c might result in the collection of 
caller ID. d might result in collection of whatever information is put 
in the letter. e might result in whatever info is put in the fax, plus 
caller ID.

I think to solve this problem we need to add some meta data that 
explains what it means to process the XML. Perhaps we could add a 
companion attribute that would be a URI that would be used to describe 
what the P3P binding means for a particular application.

Received on Wednesday, 11 February 2004 09:33:18 UTC

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