W3C home > Mailing lists > Public > www-i18n-comments@w3.org > June 2008

Re: [Comment on WS-I18N WD]

From: Felix Sasaki <fsasaki@w3.org>
Date: Tue, 24 Jun 2008 14:16:50 +0900
Message-ID: <48608342.5040100@w3.org>
To: Dan Chiba <dan.chiba@oracle.com>
CC: www-i18n-comments@w3.org

Hi Dan,

Dan Chiba さんは書きました:
>
> Based on the recent discussions, I revised the proposed specific i18n 
> items for explicit inclusion as follows:
>
> 1. Locale (BCP 47 | "$neutral" | "$default")
> 2. Timezone (Olson ID or RFC 822 zone offset)
> 3. Language (identifies translation language, BCP 47)
> 4. Collation (based on the IANA collation registry)
> 5. Date/Time Formats (based on LDML syntax)
> 6. Number Format (based on LDML syntax)
> 7. Currency Format (based on LDML syntax)
> 8. Calendar (based on LDML calendar type?)
>
> Changes are:
> * Locale identifier expects BCP 47 (delimiter is dash; no underscore).
> * Language is moved down to become a child of i18n:preferences. (only 
> locale and tz are immediately under i18n:international)
> * Charset is removed.
>
> Clarifications:
> * 3 - 8 are all optional.
> * Language element may be used when it is desirable to honor user's 
> locale and language preferences independently.
> * The language element is at 
> i18n:international/i18n:preferences/i18n:language. BCP 47 defines 
> valid values.
> * The collation element is at 
> i18n:international/i18n:preferences/iana:collation. Collation Registry 
> defines valid values.
> * The namespace for the collation element needs to be defined. (prefix 
> and the URI)
>
> Is this a reasonable list of the element items now?

it looks reasonable to me and I'm fine with editing the draft 
accordingly . Of course there will be other more comments like the one 
from Frank in this thread, but we have enough material to change the 
draft. I will also change the schema at
http://www.w3.org/TR/ws-i18n/ws-i18n.xsd
I'll come back to this thread after both is done.

Felix

>
> Regards,
> -Dan
>
> Dan Chiba wrote:
>>
>> Hello,
>>
>> The WS-I18N draft specifically defines locale and timezone as element 
>> information items.
>> http://www.w3.org/TR/2008/WD-ws-i18n-20080415/#sec-i18n
>>
>> Is it possible to consider defining several other commonly used 
>> elements as well?
>>
>> Here is a list of items that we think are common:
>>
>> 1. Locale (already defined)
>> 2. Timezone (already defined)
>> 3. Language (used when UI language is different from the language 
>> deduced from the UI locale. e.g. "de" for German language, "fr-CH" 
>> for Switzerland/French locale)
>> 4. Collation (based on the IANA collation registry)
>> 5. Charset (based on the IANA character set registry; for limited 
>> use, generally discouraged)
>> 6. Date/Time Formats (based on LDML syntax)
>> 7. Number Format (based on LDML syntax)
>> 8. Currency Format (based on LDML syntax)
>> 9. Calendar (based on LDML calendar type?)
>>
>> WS-I18N's defining more elements would enhance interoperability 
>> significantly. For example, they could include the followings, then 
>> it would be easier to coordinate the services and produce the desired 
>> application behavior.
>>
>> i18n:international/i18n:language?
>> i18n:international/i18n:preferences/iana:collation?
>> i18n:international/i18n:preferences/iana:charset?
>> i18n:international/i18n:preferences/ldml:dateFormat[@type="short"]?
>> <snip/>
>>
>> It would be desirable for service implementors to use standard items 
>> so that the implementations will be compatible with others.
>>
>> Regards,
>> -Dan Chiba
>> Oracle Globalization Technology
>>
>
>
Received on Tuesday, 24 June 2008 05:17:47 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 08:32:36 GMT