W3C home > Mailing lists > Public > public-i18n-ws@w3.org > November 2002

RE: Editor's Draft, Use Case Document Posted

From: Martin Duerst <duerst@w3.org>
Date: Thu, 21 Nov 2002 05:39:13 +0900
Message-Id: <>
To: "Joseph Boyle" <Boyle@siebel.com>, "Addison Phillips [wM]" <aphillips@webmethods.com>, public-i18n-ws@w3.org

Hello Joseph,

At 10:28 02/11/20 -0700, Joseph Boyle wrote:
>Is there any thought of using the proposed Common XML Locale format either 
>for naming locales, or transmitting the definition of a locale?

I think things such as the Common XML Locale format will stay in
the back of our mind in some way or another.

But we are just at the stage of use cases, where we should look
at what we want/need to do, not exactly how to do it.

>Currency conversion usually has to happen at the server side because the 
>server wants to specify the exchange rate. Measurement units (inches vs. 
>cm etc.) also should not be automatically converted to local units in many 

It would be good to have use cases covering these cases, and explaining
why and in what cases this has to be done (and maybe also use cases for
the 'wrong' way of doing it, and explanations on when that's appropriate.

>In general, sending locale-independent data formats and doing 
>locale-dependent formatting at the client seems like the most reliable 
>solution. Siebel's and I think most application software does this. We 
>would not be likely to use localized representation + format of the 
>localized representation as a transmission format.
>Error messages beyond a fixed commonly known set, data language for data 
>that has multiple language copies, and collation are the examples I can 
>think of where the server would need to know locale and could not simply 
>send locale-independent representations.

In general I agree with you. Can you help us formulate that in
clear use cases?

Regards,    Martin.
Received on Wednesday, 20 November 2002 17:26:47 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:02:36 UTC