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

Hi Julian,


You are right, this is to be specified.

    <d:scope>
      <d:href>/container1/</d:href>
      <d:depth>infinity</d:depth>
      <d:include-lastpathsegment>%.pdf</d:include-lastpathsegment>
      <d:exclude-lastpathsegment>%-2001-%.pdf</d:exclude-lastpathsegment>
      <d:include-lastpathsegment>%-2001-july.pdf</d:include-lastpathsegment>
      <d:exclude-lastpathsegment>%-1999-%.pdf</d:exclude-lastpathsegment>
    </d:scope>


My interpretion is:

... WHERE ((lastpathsegment matches "%.pdf") 			// all
includes
        OR (lastpathsegment matches "%-2001-july.pdf"))  
     AND NOT 
          ((lastpathsegment matches "%-2001-%.pdf") 		// all
excludes
        OR (lastpathsegment matches "%-1999-%.pdf"))                      
                  
           
so the file "report-2001-july.pdf" IS excluded. 


   

Regards,
Martin    
 


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



Martin,

looking at your proposal 
(<http://lists.w3.org/Archives/Public/www-webdav-dasl/2003OctDec/0035.html>)

I have the following question:

When a scope includes both include-lastpathsegment and 
exclude-lastpathsegment elements, how are they processed?

For instance, in

    <d:scope>
      <d:href>/container1/</d:href>
      <d:depth>infinity</d:depth>
      <d:include-lastpathsegment>%.pdf</d:include-lastpathsegment>
      <d:exclude-lastpathsegment>%-2001-%.pdf</d:exclude-lastpathsegment>
      <d:include-lastpathsegment>chapter%.doc</d:include-lastpathsegment>
    </d:scope>

You state

"The scope of this query comprises all resources within or below 
container1, that have the postfix .pdf, all doc files starting with 
"chapter", but not the file (for example) report-2001-july.pdf"

However you do not specify a behaviour when both kinds of child elements 
are present. It seems that this may become hard because you will have to 
let it depend on document order and nesting. Does an include that 
follows an exclude pattern affect the whole filter, or just the latest 
"state"?

It seems to me that this is getting too complicated. Keep in mind that 
this also affects result truncation.

Regards, Julian

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