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

RE: Issue JW17/JW24b

From: Wallmer, Martin <Martin.Wallmer@softwareag.com>
Date: Fri, 10 Jan 2003 09:07:29 +0100
Message-ID: <DFF2AC9E3583D511A21F0008C7E6210602D90785@daemsg02.software-ag.de>
To: "'Julian Reschke'" <julian.reschke@gmx.de>, www-webdav-dasl@w3.org


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.


-----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


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".


which of the two below will match?

1) <contains>&amp;</contains>
2) <contains>&amp;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.



<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Friday, 10 January 2003 03:07:33 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:22:43 UTC