Re: [comment] P3P 1.1 Well Known Location

Karl, 

this is a feature of P3P 1.0 and was not touched by the 1.1 works. Dan 
Connolly complained for the P3P 1.0 version of it. It was explained to him 
and to others that a P3P user agent will very only take into account files 
that carry the P3P namespace. So if a site has already used up /w3c/p3p.xml 
by some other format, it can't use the well-known location anymore, but has 
to use the http-headers. This was accepted in P3P 1.0.

It has to be noted nevertheless that over 90% of the sites using P3P use the 
well-known location. So as this touches on P3P 1.0, was cleared in the 
process of the P3P 1.0 Recommendation. As you are not part of the P3P Working 
Group, I don't see where the _formal_ objection should come from, but feel 
free to write down a minority view that can be attached to the Last Call 
report. 

Note perhaps that I would have expected rather a comment on the P3P generic 
attribute from you. I would be more interested in your remarks on this new 
feature that allows to address privacy metadata in any XML dialect. 

Best, 

Rigo Wenning 
Privacy Activity Lead

Am Friday 31 March 2006 05:17, sprach Karl Dubost:
> [[[
> 2.2.1 Well-Known Location
>
> Web sites using P3P MAY (and, are strongly encouraged to) place a
> policy reference file in a "well-known" location. To do this, a
> policy reference file would be made available on the site at the
> path /w3c/p3p.xml
> ]]]
>
> -- The Platform for Privacy Preferences 1.1 (P3P1.1) Specification
> http://www.w3.org/TR/2006/WD-P3P11-20060210/#Well_Known_Location
> Mon, 13 Feb 2006 15:51:33 GMT
>
> Any specification MUST not encourage to squat the URI space. To be
> reviewed with the TAG.
> Formal Objection.