- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Mon, 17 Nov 2003 13:21:34 +0100
- To: "Wallmer, Martin" <Martin.Wallmer@softwareag.com>
- Cc: www-webdav-dasl@w3.org
Wallmer, Martin wrote: > 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. So includes are processed before excludes? If this is the case, then it may be sufficient to rewrite the example to...: <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> which would also have the benefit of conforming to the DTD fragment. Julian -- <green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Monday, 17 November 2003 07:23:29 UTC