- From: Wallmer, Martin <Martin.Wallmer@softwareag.com>
- Date: Wed, 26 Nov 2003 08:21:04 +0100
- To: "'Julian Reschke'" <julian.reschke@gmx.de>, Lisa Dusseault <lisa@xythos.com>
- Cc: www-webdav-dasl@w3.org
- Message-ID: <DFF2AC9E3583D511A21F0008C7E62106063A9162@daemsg02.software-ag.de>
Hi, <julian> ... So one low-cost suggestion I made was to require servers that do support DAV:basicsearch to perform matching on DAV:getcontentlength after normalizing whitespace in the attribute value. I think in practice this is what servers do anyway. Feedback appreciated. </julian> ours does <julian> If we can make this operator reasonably simple, would there be support for adding it as mandatory operator? </julian> media type is often used in queries. Having an operator for getting it in an easy way helps the client. From my point of view it is not hard to implement, so +1 for media-type-match from me. Martin -----Original Message----- From: Julian Reschke [mailto:julian.reschke@gmx.de] Sent: Dienstag, 25. November 2003 19:26 To: Lisa Dusseault Cc: www-webdav-dasl@w3.org Subject: Re: Format of DAV:get* properties Lisa Dusseault wrote: > This hasn't been a problem in the WFS implementation. The unusual > formatting is rare, and so users can generally search on "contains > 'text/plain'" and get all the results they need. Sometimes it's > not worth dealing with edge cases in a spec, beyond noting that > they exist and noting that servers can easily normalize the value > to reduce the existence of edge cases. Right. So one low-cost suggestion I made was to require servers that do support DAV:basicsearch to perform matching on DAV:getcontentlength after normalizing whitespace in the attribute value. I think in practice this is what servers do anyway. Feedback appreciated. > However, I'm not sure how much of an edge case it is. If it's been > a problem in practice, the 'media-type-match' syntax seems to be an > elegant and effective way to deal with it. That would be the alternative. At least it makes it clear what the client wants, and doesn't require "or"ing three conditions just to make sure that it will work in any case. If we can make this operator reasonably simple, would there be support for adding it as mandatory operator? Julian (removed webdav wg from distr. list) -- <green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Wednesday, 26 November 2003 02:22:36 UTC