- From: Addison Phillips [wM] <aphillips@webmethods.com>
- Date: Wed, 08 Jan 2003 09:35:27 -0800
- To: Kentaroh Noji <NOJIK@jp.ibm.com>
- CC: public-i18n-ws@w3.org
Hi Kentaroh, Thanks for your note. Some minor commentary below. Addison > > My understanding is that the list should describe 1)What is the problem, > 2) the possible solutions, 3) and the corresponded usage scenario, correct? I agree. > > >3. Discuss if we should we merge language and > >locale negotiation categories in triage table. > >General agreement that this should be done. > > I merged them in the editor's draft. Actually, I think we should leave the existing triage alone until we have something better. As I've noted, though, the categories I chose were very rough distinctions and based on past discussions. > > >4a. Discussed the categories themselves... > > On second thought, I think it is natural that current categories are > something insufficient because best practices and guidelines are a kind > of the finishing touches that require something that is not born yet. > So, I leave categories appendix as it is in the editors draft. Just I > added an editor's note of a teleconference comment. > That's better, I think. > > Addison, I think we can already make a priority for our activities for > the present. Personally, the following is my understanding about > priority. If it is incorrect, please fix it. > > 1. Isolate problems and find possible solutions for > language/locale/i18n-context negotiation based on the existent WSUS > 2. Continue to collect usage scenarios > 3. Generate requirements > 4. Flesh out the existent WSUS > Just so, although #1 includes aspects of both #2 and #3 in the specific area of interest. I think what we're saying is that, while we won't ignore other usage scenarios, we won't be actively working on them at the moment (unless there is a compelling reason to do so). As an aside, perhaps we should make a list of W3C WS recommendations in progress and each of us take one or two and review them quickly for i18n issues. So we don't have more surprises like SOAP 1.2...? Just a thought. > > Thanks, > Kentaroh > + + + > Kentaroh Noji : nojik@jp.ibm.com -- Addison P. Phillips Director, Globalization Architecture webMethods, Inc. +1 408.962.5487 mailto:aphillips@webmethods.com ------------------------------------------- Internationalization is an architecture. It is not a feature. Chair, W3C I18N WG Web Services Task Force http://www.w3.org/International/ws
Received on Wednesday, 8 January 2003 12:41:51 UTC