- From: Mark Davis <mark.davis@jtcsv.com>
- Date: Mon, 12 Apr 2004 19:10:44 -0700
- To: <andrea.vine@Sun.COM>, "I18n WSTF" <public-i18n-ws@w3.org>
I disagree with this assessment. We all agree that the error message -- when presented to the reader -- should be localized. Thus the user should see: > * "The date provided, 12 November 2201, was too late." > * "The argument 12345.678 was too large." > * "The argument 12345,678- was too small." However, *where* the localization should be done is not so simple. It should be closest point to the user where enough information is available to formulate the message. Thus Service A (where the error is generated) may not actually have any locale information available. It might then simply send back something like: "Use MessageFormat string associated with someFault, plus data (in unlocalized form, e.g. XMLSchema datatypes): ... <error>someFault</error> <date>2004-04-14</date> <numberOfPages>1400</numberOfPages> ... This message hops from Service to Service until it gets to one that knows (a) what the end recipient's locale is, and (b) what the MessageFormat string associated with someFault for that locale is. For more info, see http://oss.software.ibm.com/cvs/icu/~checkout~/icuhtml/design/jit_localization.html Mark __________________________________ http://www.macchiato.com ► शिष्यादिच्छेत्पराजयम् ◄ ----- Original Message ----- From: "A. Vine" <andrea.vine@Sun.COM> To: "I18n WSTF" <public-i18n-ws@w3.org> Sent: Mon, 2004 Apr 12 19:06 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 Monday, 12 April 2004 22:10:46 UTC