- From: Addison Phillips [wM] <aphillips@webmethods.com>
- Date: Tue, 13 Apr 2004 09:54:26 -0700
- To: <andrea.vine@Sun.COM>, "I18n WSTF" <public-i18n-ws@w3.org>
Done. Uploaded. I reworded some of the text when I moved it (to make it flow more neatly with the text above). Check out my changes, Andrea, and let me know if I got it right. (PS> Mark, if you look at the document now, you'll see that Andrea's changes put this text directly below the examples showing problems with generating lots of languages and finding a suitable message with no default.) Addison Addison P. Phillips Director, Globalization Architecture webMethods | Delivering Global Business Visibility http://www.webMethods.com Chair, W3C Internationalization (I18N) Working Group Chair, W3C-I18N-WG, Web Services Task Force http://www.w3.org/International Internationalization is an architecture. It is not a feature. > -----Original Message----- > From: public-i18n-ws-request@w3.org > [mailto:public-i18n-ws-request@w3.org]On Behalf Of A. Vine > Sent: Monday, April 12, 2004 7:07 PM > To: I18n WSTF > Subject: 4.7.5 I-008: Locale Sensitive Formated Data in SOAP Fault > Messages > > > > All, > > I think that the best arrangement of I-008, fault messages, and > I-022 would be: > > Move I-008 to be 4.3.3, or whatever it winds up being. Rename > 4.3 to something > like "Fault Handling" or "Fault Message Handling". Reword and > repunctuate 4.3.3 > slightly as follows - > > ------------------------- > > 4.3.3 I-008: Locale Sensitive Formatted Data in SOAP Fault Messages > > A service provider must substitute locale-sensitive data into > text messages when > generating faults. > > Service A is defined on Provider B. A fault is generated during > invocation, > returning a faultReason. In order to properly present values inside the > faultReason message, the locale must be known and locale > information must be > available. For example: > > * "The date provided, 12 November 2201, was too late." > * "The argument 12345.678 was too large." > * "The argument 12345,678- was too small." > > The provider should format substitutions in each message according to the > language and locale of the message, not according to the locale > of the provider > or service. In the case of Language Neutral or Service Determined > patterns, it > may not be possible to generate a message in the user's preferred > language (or > the preference may not be available). In these cases, the message > should follow > the language preference of the provider or service host. > > For more information on locale related formatting, see I-022. > > -------------------------- > > My reasoning is this: People are going to look at fault messages > separately > from SOAP messages, because they are often from different coding > components with > different people working on them. So I don't want to merge the > fault message > locale-based formatting with data formatting. But the data > formatting example > has some additional information that they might want to take a > look at to get a > better concept. > > Andrea >
Received on Tuesday, 13 April 2004 13:00:20 UTC