W3C home > Mailing lists > Public > public-i18n-core@w3.org > July to September 2011

Re: I18N-ISSUE-65: find() method case sensitivity [Contacts API]

From: Robin Berjon <robin@berjon.com>
Date: Tue, 5 Jul 2011 14:36:19 +0200
Cc: public-device-apis@w3.org
Message-Id: <3B2AAE55-57A8-4ACF-8313-1E178E42229C@berjon.com>
To: public-i18n-core@w3.org
Dear I18N WG,

this is just a personal comment.

On Jul 4, 2011, at 21:17 , Internationalization Core Working Group Issue Tracker wrote:

> Section 4.2.1
> http://dev.w3.org/2009/dap/contacts/#methods
> 
> WG Approved: Yes
> 
> It isn't clear if the find() method is case sensitive or not. Section 5, which talks about "Contact Search Processing" uses the term "match" without closely defining what constitutes a match. We think case sensitivity of the find() method and search processing in general should be defined.

I agree that this should be defined. Unfortunately, in the majority of real-world implementation cases the UA will have no control over this as it will just pass a string over to the underlying contacts DB which will perform the search on its behalf. That being said, I'm pretty sure that most if not all such backends are case-insensitive and we can probably get away with indicating that the match SHOULD be case-insensitive.


PS: Could there be a configuration problem with your tracker instance? The Reply-To that it uses completely confuses my MUA.

-- 
Robin Berjon - http://berjon.com/ - @robinberjon
Received on Tuesday, 5 July 2011 12:36:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 5 July 2011 12:36:43 GMT