SEARCH by last path segment, Was: SEARCH for displayname

Hi,

the starting set is the scope without any filter. I think we have to define
whats happening when include or exclude is omitted. So I'd suggest:

include-lastpathsegment:
all files are included when omitted

exclude-lastpathsegment:
no files are excluded when omitted.


So my proposal is:

The content of DAV:include-lastpathsegment and DAV:exclude-lastpathsegment
is a literal pattern same as defined for (@see 5.15.1) Like.
When one or more child elements DAV:include-lastpathsegment are present, the
scope includes all resources, of which the last pathsegment of the uri
matches the pattern. <add> All resources are included when omitted. </add>
When one or more child elements DAV:exclude-lastpathsegment are present, the
scope excludes all resources, of which the last pathsegment of the uri
matches the pattern. <add> No resources are excluded when omitted.</add>

...


Regards,
Martin



-----Original Message-----
From: Julian Reschke [mailto:julian.reschke@gmx.de]
Sent: Montag, 17. November 2003 13:57
To: Wallmer, Martin
Cc: www-webdav-dasl@w3.org
Subject: Re: SEARCH by last path segment, Was: SEARCH for displayname


Wallmer, Martin wrote:

> Hi,
> 
> there is no processing sequence. A resource is in scope when
> 
> it is included AND is NOT excluded,
> 
> which is the same as
> 
> it is NOT excluded AND is included.
> 
> regards,
> Martin

Not convinced. You need to define the starting set, after all. When 
there are no specific directives, it includes all URIs in scope. When 
you have just "exclude", it includes everything except those excluded. 
However, when you have just "include", it includes *only* those that 
have been specifically excluded.

So please define exactly what happens when both types are present.

Julian

-- 
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760