W3C home > Mailing lists > Public > www-p3p-public-comments@w3.org > February 2002

Re: [Moderator Action] re: [moderator action] mutiple policy files per site

From: Rigo Wenning <rigo@w3.org>
Date: Tue, 19 Feb 2002 11:46:17 +0100
To: "Catton, Jeff" <Jeff_Catton@AFCC.com>
Cc: "'www-p3p-public-comments@w3.org'" <www-p3p-public-comments@w3.org>
Message-ID: <20020219104617.GA18688@localhost>
Dear Jeffrey, 

the semantics of your declaration are wrong. Your declaration means,
that policy20020114_main.p3p applys to everything (/*) and that
policy20020114_email.p3p applies additionally to /us/en/*

This means, that for /us/en/* you would have to honor both policies at
the same time to avoid a false declaration (false declaration might
cause trouble). If it works technically, it doesn't mean, that it is
representing your privacy-setup.

In this case you would go for something like
<META xmlns="http://www.w3.org/2001/09/P3Pv1>
	<POLICY-REFERENCES>
		<POLICY-REF
		about="/privacy/p3p/policy20020114_main.p3p">
			<INCLUDE>/*</INCLUDE>
			<EXCLUDE>/us/en/*</EXCLUDE>
		</POLICY-REF>
		<POLICY-REF
		about="http://www.mydomain.com/privacy/p3p/policy20020114_email.p3p">
			<INCLUDE>/us/en/*</INCLUDE>
			<EXCLUDE>/us/en/images/*</EXCLUDE>
			<EXCLUDE>/us/en/xml/*</EXCLUDE>
			<EXCLUDE>/us/en/js/*</EXCLUDE>
			<EXCLUDE>/us/en/templates/*</EXCLUDE>
			<EXCLUDE>/us/en/include/*</EXCLUDE>
			<EXCLUDE>/us/en/dictionary/*</EXCLUDE>
		</POLICY-REF>
		<POLICY-REF
		about="/privacy/p3p/policy20020114_main.p3p">
      <INCLUDE>/us/en/images/*</INCLUDE>
      <INCLUDE>/us/en/xml/*</INCLUDE>
      <INCLUDE>/us/en/js/*</INCLUDE>
      <INCLUDE>/us/en/templates/*</INCLUDE>
      <INCLUDE>/us/en/include/*</INCLUDE>
      <INCLUDE>/us/en/dictionary/*</INCLUDE>
		</POLICY-REF>
	</POLICY-REFERENCES>
</META>

Best, 

Rigo 

On Mon, Feb 18, 2002 at 12:34:30PM -0500, Catton, Jeff wrote:
> Ringo,
> 
> Thanks for your response.
> 
> I reviewed what I just sent.  Sorry for not thinking of the following;
> 
> 	I rearranged the policy reference file as follows;
> 
> 	
> 				<META xmlns="http://www.w3.org/2001/09/P3Pv1
> <http://www.w3.org/2001/09/P3Pv1> ">
> 				<POLICY-REFERENCES>
> 				<POLICY-REF
> about="http://www.mydomain.com/privacy/p3p/policy20020114_email.p3p
> <http://www.mydomain.com/privacy/p3p/policy20020114_email.p3p> ">
> 				      <INCLUDE>/us/en/*</INCLUDE>
> 				      <EXCLUDE>/us/en/images/*</EXCLUDE>
> 				      <EXCLUDE>/us/en/xml/*</EXCLUDE>
> 				      <EXCLUDE>/us/en/js/*</EXCLUDE>
> 				      <EXCLUDE>/us/en/templates/*</EXCLUDE>
> 				      <EXCLUDE>/us/en/include/*</EXCLUDE>
> 				      <EXCLUDE>/us/en/dictionary/*</EXCLUDE>
> 				</POLICY-REF>
> 
> 				<POLICY-REF
> about="http://www.mydomain.com/privacy/p3p/policy20020114_main.p3p
> <http://www.mydomain.com/privacy/p3p/policy20020114_main.p3p> ">
> 				      <INCLUDE>/*</INCLUDE>
> 				</POLICY-REF>
> 
> 				</POLICY-REFERENCES>
> 				</META>
> 
> This now works!  The policy is obviously search sequentially and once an
> objects relative path is found, the search stops.  Now all of the images and
> templates in /us/en/images and /us/en/templates respectively have the
> correct policy main attached to them.  This has been tested with IE 6.0 and
> AT&T Privacy Bird.
> 
> I hope this can help others as well.
> 
> Best Regards,
> 
> Jeffery R. Catton
> CitiFinancial
> Senior Systems Consultant
> (574) 236-3104
Received on Tuesday, 19 February 2002 05:49:28 GMT

This archive was generated by hypermail 2.2.0+W3C-0.1 : Tuesday, 21 September 2004 12:14:17 GMT