W3C home > Mailing lists > Public > public-device-apis@w3.org > August 2010

RE: Contacts API: ready for a review?

From: Phillips, Addison <addison@lab126.com>
Date: Mon, 30 Aug 2010 10:49:18 -0400
To: Rich Tibbett <rich.tibbett@gmail.com>
CC: "public-device-apis@w3.org" <public-device-apis@w3.org>, "public-i18n-core@w3.org" <public-i18n-core@w3.org>
Message-ID: <C7A5719F1E562149BA9171F58BEE2CA4129FAC8B59@EX-IAD6-B.ant.amazon.com>
Hi Richard,

Thanks for the response. We’ll schedule a review ASAP.

Addison

Addison Phillips
Globalization Architect (Lab126)
Chair (W3C I18N, IETF IRI WGs)

Internationalization is not a feature.
It is an architecture.

From: Rich Tibbett [mailto:rich.tibbett@gmail.com]
Sent: Monday, August 30, 2010 3:29 AM
To: Phillips, Addison
Cc: public-device-apis@w3.org; public-i18n-core@w3.org
Subject: Re: Contacts API: ready for a review?

Hi Addison,

I believe that the latest working draft of the Contacts API [3] is now feature complete and is ready for i18n review. We are still discussing some ideas around the actual format of contact data but the target is to enter LC in the coming weeks. I18N input before that would be helpful.

Thanks and look forward to your feedback.

- Richard

On Fri, Aug 27, 2010 at 11:45 PM, Phillips, Addison <addison@lab126.com<mailto:addison@lab126.com>> wrote:
Dear Device APIs WG,

I am writing on behalf of the Internationalization Core WG. In our 25 August call [1] we discussed an email [2] mentioning some internationalization issues in your new working draft [3].

I took an action item to ask if it would be appropriate for us to review the Contacts API draft now or if we should wait for a later date. Our concerns, obviously, focus on the problems that any address book faces when dealing with international data (names, postal addresses, etc.). We know that you have to deal with existing implementations and standards such as RFC2426 (vCard). It may be that the best way to address issues in this area would be via best practices. But there may also be opportunity that Contact APIs offer the opportunity to create better-internationalized implementations as well.

Please let us know how best to proceed.

Regards (for I18N),

Addison

[1] http://www.w3.org/2010/08/25-core-minutes.html

[2] http://lists.w3.org/Archives/Member/member-i18n-core/2010Aug/0007.html [MO]
[3] http://www.w3.org/TR/contacts-api/#attributes-4


Addison Phillips
Globalization Architect (Lab126)
Chair (W3C I18N, IETF IRI WGs)

Internationalization is not a feature.
It is an architecture.



Received on Monday, 30 August 2010 14:52:52 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:14:12 GMT