W3C home > Mailing lists > Public > www-webdav-dasl@w3.org > October to December 2003

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

From: Julian Reschke <julian.reschke@gmx.de>
Date: Sun, 16 Nov 2003 19:35:30 +0100
Message-ID: <3FB7C372.4070603@gmx.de>
To: www-webdav-dasl@w3.org
Cc: "Wallmer, Martin" <Martin.Wallmer@softwareag.com>

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
Received on Sunday, 16 November 2003 13:36:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 22 March 2009 03:38:09 GMT