RE: P3P and WSDL

Please check <patrick2> as follows.

-----Original Message-----
From: Philippe Le Hegaret [mailto:plh@w3.org]
Sent: Wednesday, 8 October 2003 4:23 AM
To: Patrick.Hung@csiro.au
Cc: Rigo Wenning; Hugo Haas; w3t-archive@w3.org; public-p3p-spec@w3.org
Subject: RE: P3P and WSDL


On Tue, 2003-10-07 at 06:18, Patrick.Hung@csiro.au wrote:
> Hi Philippe,
> 
> Thank you very much for your message. My response is contained in
> <patrick/>.
> 
> May I ask whether you have any suggestion for this task force? How should
> this
> task force work with the WSDL and SOAP working groups?

How about sending a note inviting them to provide feedback and even
participate if they wish? I would certainly be happy to help the P3P WG.

<patrick2>
Rigo: Do you have any idea which mailing list should I send?
</patrick2>

> 1- By reference
> 
> This is your example. The privacy element links to a P3P file. However,
> the section fails - to indicate what happens if the P3P file make
> statements on a set of URIs (using the INCLUDE element) that happens to
> differ from the location of the service (in the soap:address or
> http:address elements).
> <patrick>Would you please further explain it? It is expected to have a
> revised P3P language for describing privacy policies in the context of 
> Web services. Thus, I am not very sure what do you mean.</patrick>

Actually, I realized that section 4.3 explicitly mentions that a WSDL
description directly references a policy, not a policy reference.
Therefore, since the policy doesn't contain any reference,  it does
exclude the case I was trying to address.


> - to indicate that the statements are only applicable to the information
> going from the registrant to the registry. What happen to the
> information going from the registry to the registrant? Can't the
> registry indicates its preferences to the registry? If yes, should the
>                                  <patrick>^^^^^^^^ registrant?</patrick>

 correct s/registry/registrant/

> registry indicate its preferences using a SOAP header in the output
> messages or in the WSDL as well?
> <patrick>This is a very interesting point. At this minute, we only 
> consider uni-directional scenario. We will explore this point in the
working
> draft for next version.</patrick>

please, make sure this item is not dropped when defining the
requirements for the next version. In any case, the current version
should indicate that the statements are only applicable to the
information received by the service, and not the client interacting with
the service. What is the schedule regarding the first version of the
document btw?

<patrick2>
Hope to get more comments/suggestions by the end of Oct. And then, I would
generate another version by the end of Nov. Thanks a lot for your
contributions.
</patrick2>

Philippe

Received on Friday, 10 October 2003 11:30:40 UTC