RE: SEARCH by last path segment, Was: SEARCH for displayname


I'd be happy to see an example :-)


-----Original Message-----
From: Elias Sinderson []
Sent: Donnerstag, 20. November 2003 11:51
Subject: Re: SEARCH by last path segment, Was: SEARCH for displayname

What needs to be clarified is the relative ordering of evaluating 
include and exclude elements of a DASL request. Whereas AND operations 
are generally unaffected by the order of their evaluation, this fails to 
hold when you AND together set operations (union, intersection, and the 
like). If you would like me to provide an example of why this is the 
case, I'd be happy to...


Julian Reschke wrote:

> Wallmer, Martin wrote:
>> Hi,
>> the starting set is always "ALL", which is defined by href and depth.
>> 1) res = all
>> 2) res = all AND NOT excluded
>> 3) res = all AND included
>> 4) res = all AND included AND NOT excluded
>> Does this make it clear? Any suggestion to add it to the the proposal?
> I think we should have a format explanation in there. Either your's 
> (using query syntax) or mine (using set arithmetics)...
> Julian

Received on Thursday, 20 November 2003 06:45:12 UTC