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

Re: Like and Case Sensitivity

From: Richard Henderson <rickh@netscape.com>
Date: Wed, 02 Feb 2000 10:27:25 -0800
Message-ID: <3898770B.1F165A77@netscape.com>
To: Kevin Wiggen <wiggs@xythos.com>
CC: Jim Davis <jrd3@alum.mit.edu>, www-webdav-dasl@w3.org
I'm not so sure all systems can turn case sensitivity on or off easily.

Some do other things than simply case sensitive or case insensitive by
default.  By default Verity is case sensitive if the query term has
mixed case and insensitive otherwise, but does have a case
operator.

Some other full text systems don't necessarily have a case
operator so they wouldn't easily be able to conform to the
standard if there is no out for being only case sensitive or  case
insensitive..

Do we need to include query discovery for control of case
sensitivity capabilities?

--Rick

Kevin Wiggen wrote:

> <case sensitive attribute on like> it's missing.  It's probably an
> oversight.  There is no reason not to allow it.
>
> Note that the default for all other casesensitive attributes is 1.
>
> 1) should the default for like be the same as the usual default?
>
> <KW> I see no reason why the default should be different.  It should be the
> same for consistency if for nothing else
> </KW>
>
> 2) should we change the usual default from 1 to 0?  (that is, comparisons
> are case insensitive unless explicitly stated otherwise?)
>
> <KW> Most systems I know of have an easier time doing case sensitive
> searches (or its less CPU cycles at least), I think we should leave the
> default where it is.  This way the default is less CPU intensive.  Its easy
> to override so it should not be a big deal
> </KW>
>
> Kevin
Received on Wednesday, 2 February 2000 13:27:44 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 22 March 2009 03:38:05 GMT