W3C home > Mailing lists > Public > xmlp-comments@w3.org > August 2002

Re: XMLP Issue 263 Resolution

From: Martin Duerst <duerst@w3.org>
Date: Mon, 05 Aug 2002 11:30:39 +0900
Message-Id: <>
To: Ryuji Inoue <ryuji@isl.mei.co.jp>, xmlp-comments@w3.org
Cc: w3c-i18n-ig@w3.org

Hello Ryuji,

As issue 263 was adopted by the I18N WG, I'm forwarding
your response for discussion to the I18N IG mailing list.
Misha, can you please add this to the WG's teleconf agenda?

Personally, I note that while the proposal is a step in the
right direction, there are some concerns of scalability
(increase of size of fault message with number of languages).

Also, you write "Applications could negotiate the language for
the fault text using a mechanism built using SOAP headers."
While I think this is the direction to go, has it been considered
that some underlying protocols (in particular HTTP) already have
a perfectly well working mechanism for language negotiation?

Regards,    Martin.

At 23:53 02/08/02 +0900, Ryuji Inoue wrote:
>The XML Protocol (XMLP) WG has decided to close issue 263 [1], which you
>originated, with the following resolution.
>The XMLP WG has decided to modify SOAP Reason element (5.4.2 in Part1)
>in the following manner:
>   - The Reason element information item has one or more Text element
>     information item children:
>       <env:Reason>
>           <env:Text xml:lang="en-US">wrong color</env:Text>
>           <env:Text xml:lang="en-GB">wrong colour</env:Text>
>       </env:Reason>
>   - The Text element information item has any number of character
>     information item children to explain the neture of the fault.
>   - Each Text element MUST have xml:lang attribute information item
>     (prefix of lang attribute information item MUST be "xml:").
>   - When there are multiple Text element information items, values of
>     xml:lang attribute information items MUST be unique.
>Applications can make multiple language versions of the fault text
>available using this mechanism. Applications could negotiate
>the language for the fault text using a mechanism built using SOAP headers.
>However we do not provide such a mechanism.
>We trust that this resolution satisfies your concern. If not, please
>contact the WG asap.
>[1] http://www.w3.org/2000/xp/Group/xmlp-lc-issues#x263
>Ryuji Inoue
>Matsushita Electric Industrial Co., Ltd.
Received on Sunday, 4 August 2002 22:30:55 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:16:59 UTC