- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Thu, 10 Jan 2002 14:27:43 +0100
- To: "Wallmer, Martin" <Martin.Wallmer@softwareag.com>, <www-webdav-dasl@w3.org>
- Cc: "Pill, Juergen" <Juergen.Pill@softwareag.com>
Basically, what a server does with DAV:contains is completely open. So, yes, your server could use an extension like this (I'd propably define a custom function or move the path into an attribute instead, though). And no, there's nothing like this in the standard. Julian > -----Original Message----- > From: www-webdav-dasl-request@w3.org > [mailto:www-webdav-dasl-request@w3.org]On Behalf Of Wallmer, Martin > Sent: Thursday, January 10, 2002 2:18 PM > To: 'www-webdav-dasl@w3.org' > Cc: Pill, Juergen > Subject: Extend basicsearch > > > Hi, > > once again a question about extending the basicsearch, concerning content > based issues. > > Suppose the server stores XML documents, and I want to find all documents > greater than 10000 bytes and concerning the patient "Otto", I'd like to > write > > ... > <d:where> > <d:and> > <d:gt> > <d:prop> > <d:getcontentlength/> > </d:prop> > <d:literal>10000</d:literal> > </d:gt> > <d:contains> [patient/name = 'Otto'] > </d:contains> > </d:and> > </d:where> > > where the server defines, that <contains> expressions enclosed in brackets > are interpreted as xpath filter. Would that be covered by the standard? Or > would it make sense to introduce a new optional "%content_ops" > operator, say > xpathfilter, to handle this? > > Best regards, > > Martin Wallmer > Research & Development > Software AG ++49 6151 92 1831 > Uhlandstr. 12 > D 64297 Darmstadt >
Received on Thursday, 10 January 2002 08:28:17 UTC