- From: Wallmer, Martin <Martin.Wallmer@softwareag.com>
- Date: Fri, 10 Jan 2003 09:07:29 +0100
- To: "'Julian Reschke'" <julian.reschke@gmx.de>, www-webdav-dasl@w3.org
Hi, following chapter 5.14, verse 147, ... The DAV:contains operator is intentionally not overly constrained, in order to allow the server to do the best job it can in performing the search. ... I would suggest not to make constraints about character sets. Regards, Martin -----Original Message----- From: Julian Reschke [mailto:julian.reschke@gmx.de] Sent: Donnerstag, 9. Januar 2003 18:24 To: www-webdav-dasl@w3.org Subject: RE: Issue JW17/JW24b Hi, this issue is on the relation between DAV:contains and character sets. "5.13 should discuss handling of queries when character set differs. Some text on handling character sets would be helpful." Some observations: a) the character set for the query condition is well known (due to the fact that we're using XML) -- basically the query processor just has a sequence of Unicode characters. b) even text files may be difficult -- the server may not need their encoding -- even if he does, it's unclear how matching will work -- for instance take a file of mime type "text/xml; charset=ISO8859-1". <foo>&</foo> which of the two below will match? 1) <contains>&</contains> 2) <contains>&amp;</contains> (in one case the raw text file is searched, in the other case the XML Infoset after parsing). Conclusion: it's hard to define, and very hard to mandate a specific behaviour. IMHO, the spec should be silent on this issue. Julian [1] <http://greenbytes.de/tech/webdav/draft-reschke-webdav-search-latest.html#rf c.issue.JW17/JW24b> -- <green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Friday, 10 January 2003 03:07:33 UTC