Agenda

Dear all, 

www.w3.org is a complicated site, because of the ACL. (Access
Control List). I have some questions on syntax and semantics of
the PRF, because it would allow me a much more fingrained
approach:

3.1. Including and excluding and re-including

I want to exclude datespace-files from public, but I want to
include some files in the datespace back into the range of the
public policy. Actually, I have first of all made an
<include>/*</include> statement. Than I excluded the datespace by
saying <exclude>/2001/*</exclude>.  Now I want to include the
file /2001/05/p3p/public.xml to the range of application of the
public policy. I could now say 
<include>/2001/05/p3p/public.xml</include>. 

But this would mean, that I have conflicting statements.
<exclude>/2001/*</exclude> means exclusion also of
/2001/05/p3p/public.xml. This is a conflict to the
<include>/2001/05/p3p/public.xml</include> - rule. Do we allow
this?

The Specification says: A very important rule of policy
references is that of non-ambiguity: For each resource at a Web
site there MUST be at most one policy active at any given time.
Thus two non-expired policy reference files on a given site MUST
NOT declare two or more different policy URIs for the same
resource.

This means, that by excluding things, I donīt run into the
ambiguity. Only by including a given URI with different policies
the non-ambiguity - rule would apply. Is this correct? 

The current definition would cover the following statement:
<include>/*</include>
<exclude>/2001/*</exclude>
<include>/2001/05/p3p/public.xml</include>

BUT, Martin said in a mail[1], that we would have to process
those rules in order. In that case, a client would have to ignore
my <include>/2001/05/p3p/public.xml</include> after having
processed. Is this correct?

[1] Message-ID: <8525693D.0050A20A.00@d54mta01.raleigh.ibm.com>

Best, 

Rigo

Received on Monday, 21 May 2001 14:28:18 UTC