23:17:30 RRSAgent has joined #i18n 23:18:21 RRSAgent, please set logs world-visible 23:19:10 we need to expand the group before we have more bots listening on irc then people... 23:19:29 We need to swell attendance any way we can..... 23:19:49 like eating lots of ice cream? ;-) 23:20:03 good idea. Know where we can get any? 23:20:19 Zakim, give us ice cream 23:20:19 I don't understand 'give us ice cream', Tex 23:20:24 darn 23:23:38 --- 23:23:47 Discussion of the letter to SOAP 23:23:56 ACTION: Andrea to send the note out 23:24:29 +[IBM] 23:24:35 welcome, Mary 23:25:00 Discussion of Unicode plans 23:29:32 --- 23:29:52 Requirements document 23:30:15 TT: 2.5 locale identifiers 23:30:26 nothing about protocol around them 23:30:52 insert text about protocol and negotiation 23:31:20 locale "geographic" from locale "other stuff" 23:32:26 Unicode support: negotiation between services about subset? 23:33:30 legacy systems exposed as WS causes problems? 23:35:01 worlds most unfortunate acronym: CRPP 23:36:42 http://www.inter-locale.com/w3-ws-cc-position-i18n.html 23:37:23 comments welcome 23:40:19 - 23:41:23 need to have a "description language for i18n preferences" 23:48:09 silly requestion: WSUSI 23:48:14 (instead of WSUS) 23:48:32 WSIUS 23:48:47 WSUIS? 23:49:16 SUIWS 23:50:53 ACTION: Addison: update the document with comments. 23:51:26 MD: not one single policy per web service 23:52:05 last para in 2.1 has typo for evolution. 23:52:13 (thanks Tex) 23:55:09 Note or WD this month? 23:55:51 Tex: intro needs to say more 23:56:02 architecture necessary 23:58:11 locale model problem.... 23:58:33 work on intro statement together. 23:59:49 Now there is something mystical about how the J2EE system got the locale into the method. The Java proprietary Locale object was set in the Request object by processing the user's HTTP Accept-Language header and doing some (proprietary) mapping to Java's representation (the Locale object). The locale can then be accessed by a Java program. 23:59:49 23:59:49 Both of the examples above produce localized behavior using information maintained by the application's environment. The developer may need to do something in the body of the code to access this capability (as in the second example), but the method signature remains the same.