index.html
49.1 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en"><head><title>Web Services Internationalization (WS-I18N)</title><style type="text/css">
code { font-family: monospace; }
div.constraint,
div.issue,
div.note,
div.notice { margin-left: 2em; }
ol.enumar { list-style-type: decimal; }
ol.enumla { list-style-type: lower-alpha; }
ol.enumlr { list-style-type: lower-roman; }
ol.enumua { list-style-type: upper-alpha; }
ol.enumur { list-style-type: upper-roman; }
div.exampleInner pre { margin-left: 1em;
margin-top: 0em; margin-bottom: 0em}
div.exampleOuter {border: 4px double gray;
margin: 0em; padding: 0em}
div.exampleInner { background-color: #d5dee3;
border-top-width: 4px;
border-top-style: double;
border-top-color: #d3d3d3;
border-bottom-width: 4px;
border-bottom-style: double;
border-bottom-color: #d3d3d3;
padding: 4px; margin: 0em }
div.exampleWrapper { margin: 4px }
div.exampleHeader { font-weight: bold;
margin: 4px}
</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-WD.css"/></head><body><div class="head"><p><a href="http://www.w3.org/"><img src="http://www.w3.org/Icons/w3c_home" alt="W3C" height="48" width="72"/></a></p>
<h1><a name="title" id="title"/>Web Services Internationalization (WS-I18N)</h1>
<h2><a name="w3c-doctype" id="w3c-doctype"/>W3C Working Draft 15 April 2008</h2><dl><dt>This version:</dt><dd><a href="http://www.w3.org/TR/2008/WD-ws-i18n-20080415/">http://www.w3.org/TR/2008/WD-ws-i18n-20080415/</a></dd><dt>Latest version:</dt><dd><a href="http://www.w3.org/TR/ws-i18n">http://www.w3.org/TR/ws-i18n</a></dd><dt>Previous version:</dt><dd><a href="http://www.w3.org/TR/2005/WD-ws-i18n-20050914/">http://www.w3.org/TR/2005/WD-ws-i18n-20050914/</a></dd><dt>Editors:</dt><dd>Addison Phillips, Yahoo!, Inc.</dd><dd>Mary Trumble (until September 2005), IBM</dd><dd>Felix Sasaki, W3C</dd></dl><p>This document is also available in these non-normative formats: <a href="ws-i18n.xml">XML</a>.</p><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2008 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr/><div>
<h2><a name="abstract" id="abstract"/>Abstract</h2><p>This document (hereafter referred to as "WS-I18N") describes enhancements to SOAP messaging to provide
internationalized and localized operations using locale and international
preferences. These mechanisms can be used to accommodate a
wide variety of development models for international usage.</p><p>By itself, WS-I18N does not ensure internationalized operation or that localized operation will occur nor does it provide a complete internationalization solution. WS-I18N is a building block that is used in conjunction with other Web services and application-specific protocols, and which can accommodate a wide variety of locale and international support models. Implementing this specification does not by itself enable international functionality in a Web services interaction, but it does provide a framework for globalization that enabled products can leverage, as well as a way for enabled products to interact with systems that are not enabled.</p></div><div>
<h2><a name="status" id="status"/>Status of this Document</h2><p><em>This section describes the status of this document at the time
of its publication. Other documents may supersede this document.
A list of current W3C publications and the latest revision of
this technical report can be found in the <a href="http://www.w3.org/TR/">W3C technical reports index</a> at http://www.w3.org/TR/.</em>
</p><p>This document (hereafter referred to as "WS-I18N") describes enhancements to SOAP messaging to provide
internationalized and localized operations using locale and international
preferences. These mechanisms can be used to accommodate a
wide variety of development models for international usage.</p><p>This is an updated Working Draft of "Web Services Internationalization (WS-I18N)". This document was produced by members of the <a href="http://www.w3.org/International/core/">Internationalization Core Working Group</a>, part of the <a href="http://www.w3.org/International/Activity">W3C Internationalization Activity</a>. The Working Group intends to publish this document as a Working Group Note.</p><p>The major change in this version of the document is the adoption of <a href="#wsp">[WS Policy Framework]</a> and <a href="#wsp-attach">[WS Policy Attachment]</a> as the means to realize the functionality of Web Services Internationalization. No diff-marked version against the previous version of this document is provided, since this change resulted in a thorough restructuring of the document.</p><p>Comments should be sent to <a href="mailto:www-i18n-comments@w3.org?subject=%5BComment%20on%20WS-I18N%20WD%5D">www-i18n-comments@w3.org</a>. Use "Comment on WS-I18N WD" in the subject line of your email. The <a href="http://lists.w3.org/Archives/Public/www-i18n-comments/">archives</a> for this list are publicly available.</p><p>Publication as a Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.</p><p>This document was produced by a group operating under the
<a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5
February 2004 W3C Patent Policy</a>. The group does not expect this document to become a W3C Recommendation. W3C maintains a <a href="http://www.w3.org/2004/01/pp-impl/32113/status">public list of any
patent disclosures</a> made in connection with the deliverables of
the group; that page also includes instructions for disclosing a
patent. An individual who has actual knowledge of a patent which
the individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">
Essential Claim(s)</a> must disclose the information in accordance
with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">
section 6 of the W3C Patent Policy</a>.</p></div><div class="toc">
<h2><a name="contents" id="contents"/>Table of Contents</h2><p class="toc">1 <a href="#sec-intro">Introduction</a><br/>
1.1 <a href="#sec-i18n-patterns">Internationalization Patterns</a><br/>
1.2 <a href="#d1e171">Requirements</a><br/>
2 <a href="#sec-notation">Notation and Terminology</a><br/>
2.1 <a href="#sec-terminology">Notation and Terminology</a><br/>
2.2 <a href="#Notational_Conventions">Notational Conventions</a><br/>
2.3 <a href="#Extensibility">Extensibility</a><br/>
2.4 <a href="#sec-namespaces">Namespaces</a><br/>
2.5 <a href="#sec-implementation-requirements">Requirements on Implementations</a><br/>
3 <a href="#sec-soap-i18n">Internationalization Data Structures for SOAP Messages</a><br/>
3.1 <a href="#sec-i18n">Internationalization Information in SOAP</a><br/>
3.2 <a href="#sec-locale">Providing Locale Information</a><br/>
3.3 <a href="#sec-tz">Providing Time zone Information</a><br/>
3.4 <a href="#sec-preferences">Providing Locale Preferences</a><br/>
4 <a href="#sec-ws-i18n-policy">Indicating Use of WS-I18N</a><br/>
4.1 <a href="#sec-assertion-syntax">Assertion Syntax</a><br/>
4.2 <a href="#sec-assertion-attachment">Assertion Attachment</a><br/>
5 <a href="#sec-conformance">Conformance</a><br/>
</p>
<h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#sec-normrefs">Normative References</a><br/>
B <a href="#sec-xmlschema-documents">XML Schema Documents</a><br/>
C <a href="#sec-informrefs">Informative References</a> (Non-Normative)<br/>
D <a href="#sec-revlog">Revision Log</a> (Non-Normative)<br/>
E <a href="#sec-acknowledgements">Acknowledgements </a> (Non-Normative)<br/>
</p></div><hr/><div class="body"><div class="div1">
<h2><a name="sec-intro" id="sec-intro"/>1 Introduction</h2><p>This section is <em>informative.</em></p><p>Web services technology provides application-to-application communication over the Internet. Most programming languages and operating environments use an internationalization model that assumes that the user's preferences (generally embodied as a "locale", that is: a collection of settings associated with a specific language, country, or market) are maintained by the operating environment. This model has been extended to Web-based applications by having Web servers infer their internal locale from the user agent's Accept-Language header <a href="#RFC3282">[RFC 3282]</a> or from some form of user identity management. However, neither Accept-Language nor user identity is appropriate for the internationalization of Web services.</p><p>This specification proposes an alternative mechanism to provide locale information in a web services interaction. It provides semantics for the identification of international preferences which are as clear and platform neutral as possible, while providing for implementation specific extensions that leverage specific platform capabilities. The functionality provided by this mechanism defined in <a href="#sec-soap-i18n"><b>3 Internationalization Data Structures for SOAP Messages</b></a> is: </p><ul><li><p>identify whether a service is locale-affected;</p></li><li><p>identify the specific locale used by a provider;</p></li><li><p>accept the specific locale and language preference(s) of the requester;</p></li><li><p>optionally identify the specific locale or language preference(s) used by the provider in a response.</p></li></ul><p>In addition, this specification defines a policy assertion (see
<a href="#sec-ws-i18n-policy"><b>4 Indicating Use of WS-I18N</b></a>.) relying on <a href="#wsp">[WS Policy Framework]</a> to describe the capabilities of these functionalities for a provider or requester, and how to attach a policy with this assertion, relying on <a href="#wsp-attach">[WS Policy Attachment]</a>.</p><div class="div2">
<h3><a name="sec-i18n-patterns" id="sec-i18n-patterns"/>1.1 Internationalization Patterns</h3><p>When a Web service is deployed, there are four internationalization patterns that can be applied to the service:</p><ol class="enumar"><li><p><em>Locale Neutral. </em>Most aspects of most services are not particularly locale-affected. These services can be considered "locale neutral". For example, a service that adds two integers together is locale neutral.</p></li><li><p><em>Data Driven. </em>Aspects of the data determine how it is processed, rather than the configuration of either the requester or the provider.</p></li><li><p><em>Service Determined. </em>The service will have a particular setting built into it. As in: this service always runs in the French for France locale. Or, quite commonly, the service will run in the host's default locale. It may even be a deployment decision that controls which locale or preferences are applied to the service's operation.</p></li><li><p><em>Client Influenced. </em>The service's operation can use a locale preference provided by the end-user to affect its processing. This is called "influenced" because not every request may be honored by the service (the service may only implement behavior for certain locales or international preference combinations).</p></li></ol><p>Each of these patterns may apply to a service or an aspect of the service.</p></div><div class="div2">
<h3><a name="d1e171" id="d1e171"/>1.2 Requirements</h3><p>The goal of this specification is to enable applications to gather information about a service's capabilities; pass international preferences to Web services that the application invokes via SOAP; and understand the format and language of any messages returned.</p><p>From this goal, the following functionalities are required in SOAP messages, see <a href="#sec-soap-i18n"><b>3 Internationalization Data Structures for SOAP Messages</b></a>:</p><ol class="enumar"><li><p>indicate the locale and/or language preference of the client to the Web service and service provider;</p></li><li><p>indicate the time zone of the client;</p></li><li><p>indicate additional optional information about the client's international preferences;</p></li><li><p>provide an extensible mechanism for adding other related information to the request.</p></li></ol><p>An internationalization "policy", see <a href="#sec-ws-i18n-policy"><b>4 Indicating Use of WS-I18N</b></a>, can be used to describe the capability of these functionalities.</p></div></div><div class="div1">
<h2><a name="sec-notation" id="sec-notation"/>2 Notation and Terminology</h2><p>This section is <em>normative.</em></p><p>This section specifies the terminology used throughout.</p><div class="div2">
<h3><a name="sec-terminology" id="sec-terminology"/>2.1 Notation and Terminology</h3><p>The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in <a href="#RFC2119">[RFC 2119]</a>.</p></div><div class="div2">
<h3><a name="Notational_Conventions" id="Notational_Conventions"/>2.2 Notational Conventions</h3><p>This specification uses the following syntax within normative outlines: </p><ul><li><p>The syntax appears as an XML instance, but values in <em>italics</em>
indicate data types instead of literal values.</p></li><li><p>Characters are appended to elements and attributes to indicate
cardinality:</p><ul><li><p>"?" (0 or 1)</p></li><li><p>"*" (0 or more)</p></li><li><p>"+" (1 or more)</p></li></ul></li><li><p>The character "|" is used to indicate an exclusive choice between
alternatives.</p></li><li><p>The characters "(" and ")" are used to indicate that contained items are
to be treated as a group with respect to cardinality or choice.</p></li><li><p>This document relies on the XML Information Set <a href="#XMLInfoset">[XML Infoset]</a>. Information item properties are indicated by the style <em>infoset property</em>.</p></li><li><p>XML namespace prefixes (see <a href="#sec-namespaces"><b>2.4 Namespaces</b></a>) are used to
indicate the namespace of the element or attribute being defined.</p></li><li><p>The ellipses characters "..." are used to indicate a point of
extensibility that allows other Element or Attribute Information
Items.</p></li></ul><p>Elements and Attributes defined by this specification are referred to in the text
of this document using XPath 1.0 <a href="#xpath10">[XPath 1.0]</a> expressions. Extensibility points
are referred to using an extended version of this syntax:</p><ul><li><p>An element extensibility point is referred to using {any} in place of the
element name. This indicates that any element name can be used, from any
namespace, unless specified otherwise.</p></li><li><p>An attribute extensibility point is referred to using @{any} in place of
the attribute name. This indicates that any attribute name can be used,
from any namespace. </p></li></ul><p> Normative text within this specification takes precedence over normative
outlines, which in turn take precedence over the XML Schema <a href="#xmlschema1">[XML Schema 1]</a> descriptions. </p></div><div class="div2">
<h3><a name="Extensibility" id="Extensibility"/>2.3 Extensibility</h3><p>Within normative outlines, in this specification, ellipses (i.e., "...")
indicate a point of extensibility that allows other Element or Attribute
Information Items. Information Items <strong>MAY</strong> be added at the
indicated extension points but <strong>MUST NOT</strong> contradict the
semantics of the element information item indicated by the <em>parent</em> or <em>owner</em> property of the extension. In this context, if an Attribute
Information Item is not recognized, it <strong>SHOULD</strong> be ignored.</p></div><div class="div2">
<h3><a name="sec-namespaces" id="sec-namespaces"/>2.4 Namespaces</h3><p>This specification uses a number of namespace prefixes throughout; they are listed in Table 1. Note that the choice of any namespace prefix is arbitrary and not semantically significant.</p><a name="nsprefs" id="nsprefs"/><table summary="Namespace prefixes usage in this specification" border="1"><tbody><tr><th align="left">Prefix</th><th align="left">Namespace</th><th align="left">Specification</th></tr><tr><td>i18n</td><td>http://www.w3.org/2005/09/ws-i18n</td><td>This document, <a href="#sec-soap-i18n"><b>3 Internationalization Data Structures for SOAP Messages</b></a></td></tr><tr><td>i18np</td><td>http://www.w3.org/2008/04/ws-i18np</td><td>This document, <a href="#sec-ws-i18n-policy"><b>4 Indicating Use of WS-I18N</b></a></td></tr><tr><td>ldml</td><td>http://unicode.org/cldr/</td><td><a href="#LDML">[LDML]</a></td></tr><tr><td>S</td><td>http://www.w3.org/2003/05/soap-envelope</td><td><a href="#soap12">[SOAP 1.2]</a></td></tr><tr><td>xs</td><td>http://www.w3.org/2001/XMLSchema</td><td><a href="#xmlschema1">[XML Schema 1]</a> or <a href="#xmlschema2">[XML Schema 2]</a>, depending on the context</td></tr><tr><td>wsdl</td><td>http://www.w3.org/ns/wsdl or http://schemas.xmlsoap.org/wsdl/
, depending on context</td><td><a href="#wsdl20">[WSDL 2.0]</a> or <a href="#wsdl11">[WSDL 1.1]</a></td></tr><tr><td>wsp</td><td>http://www.w3.org/ns/ws-policy</td><td><a href="#wsp">[WS Policy Framework]</a> or <a href="#wsp-attach">[WS Policy Attachment]</a>, depending on the context</td></tr></tbody></table></div><div class="div2">
<h3><a name="sec-implementation-requirements" id="sec-implementation-requirements"/>2.5 Requirements on Implementations</h3><p>Certain aspects of this specification are described as
<b>implementation-defined</b> or
<b>implementation-dependent</b>.</p><ul><li><p>[<a name="dt-implementation-defined" id="dt-implementation-defined" title="implementation defined">Definition</a>: <b>Implementation-defined</b>
indicates an aspect that may differ between
implementations, but must be specified by the
implementor for each particular
implementation.]</p></li><li><p>
[<a name="dt-implementation-dependent" id="dt-implementation-dependent" title="implementation dependent">Definition</a>: <b>Implementation-dependent</b>
indicates an aspect that may differ between
implementations, is not specified by this or any W3C
specification, and is not required to be specified by
the implementor for any particular
implementation.]</p></li></ul></div></div><div class="div1">
<h2><a name="sec-soap-i18n" id="sec-soap-i18n"/>3 Internationalization Data Structures for SOAP Messages</h2><p>This section is <em>normative.</em></p><p>SOAP documents that need to send international preferences <strong>SHOULD</strong> include the <code>i18n:international</code> element information item in a header. When sent from the requester to a provider, the header represents the preferences of the requester or its client application. When sent in a response message from the provider, the header represents the settings that the service used to process the request. </p><div class="div2">
<h3><a name="sec-i18n" id="sec-i18n"/>3.1 Internationalization Information in SOAP</h3><p>The <code>i18n:international</code> element information item servers as a wrapper for conveying internationalization information in SOAP. Its content model is outlined below.</p><div class="exampleInner"><pre>(01) <i18n:international ... S:actor="...">
(02) <i18n:locale> <em>locale identifier</em> </i18n:locale>
(03) <i18n:timezone> <em>time zone value</em> </i18n:timezone>
(04) <i18n:preferences ...>
(05) <em>LDML-based or other locale preferences</em>
(06) </i18n:preferences>
(07) </i18n:international></pre></div><p>The following describes the element information items defined in the schema outline above:</p><dl><dt class="label">/i18n:international</dt><dd><p>This element information item encloses international preferences and contextual information, see this section for more explanation.</p></dd><dt class="label">/i18n:international/i18n:locale</dt><dd><p>This required element information item defines the locale, see <a href="#sec-locale"><b>3.2 Providing Locale Information</b></a>.</p></dd><dt class="label">i18n:international/i18n:tz?</dt><dd><p>This optional element information item defines the timezone, see <a href="#sec-tz"><b>3.3 Providing Time zone Information</b></a>.</p></dd><dt class="label">i18n:international/i18n:preferences?</dt><dd><p>This optional element information item defines the locale preferences, see <a href="#sec-preferences"><b>3.4 Providing Locale Preferences</b></a>.</p></dd><dt class="label">/i18n:international/@S:actor</dt><dd><p>This attribute information item describes the target of the international preferences. See below for more detailed explanation.</p></dd><dt class="label">i18n:international/@{any}</dt><dd><p>Additional attribute information items <strong>MAY</strong> be specified but <strong>MUST NOT</strong> contradict the semantics of the <b>owner element</b>; if an attribute is not recognized, it <strong>SHOULD</strong> be ignored.</p></dd></dl><p>The <code>i18n:international</code> element information item encloses the header block that provides a mechanism for providing international preferences and contextual information within a SOAP document targeted at a specific receiver (SOAP actor). The block can, therefore, be repeated multiple times in a SOAP message.</p><p>A message <strong>MAY</strong> have multiple <code>i18n:international</code> element information items if they are targeted for separate receivers. However, only one <code>i18n:international</code> element information item can omit the <code>S:actor</code> attribute and no two <code>i18n:international</code> element information items can have the same value for <code>S:actor</code>. International preference information targeted for different receivers <strong>MUST</strong> appear in different <code>i18n:international</code> element information items. The <code>i18n:international</code> element information item without a specified <code>S:actor</code> can be consumed by anyone, but <strong>MUST NOT</strong> be removed prior to the final destination.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>In practice, the <code>i18n:international</code> element information item is rarely repeated in a header. The main case for repeating it is when an intermediary service is forwarding a request. See <a href="http://www.w3.org/TR/ws-i18n-scenarios/#IDAGWTO">Section 4.7</a> of <a href="#I18NScenarios">[I18NScenarios]</a>.</p></div></div><div class="div2">
<h3><a name="sec-locale" id="sec-locale"/>3.2 Providing Locale Information</h3><p>The <code>i18n:locale</code> element information item <strong>MUST</strong> appear exactly one time as the first item in the <b>children</b> property of the <code>i18n:international</code> element information item.</p><div class="exampleInner"><pre>(01) <i18n:locale> (<em>locale identifier based on <a href="#LDML">[LDML]</a></em>)|
(02) "$neutral" | "$default") </i18n:locale></pre></div><p>The <code>i18n:locale</code> element information item represents the locale in the web services interaction. Its value <strong>MUST</strong> be either a valid <a href="#LDML">[LDML]</a> locale identifier or one of the values "<code>$neutral</code>" or "<code>$default</code>".</p><p>The value <code>$default</code> indicates that the service or provider should use its own runtime locale as the base setting. The value <code>$neutral</code> represents the base or root locale on the receiving system. Different systems and environments identify this setting in different ways. Examples are given below.</p><div class="exampleOuter">
<div class="exampleHeader"><a name="d1e585" id="d1e585"/>Example: Locale settings in different systems</div><table width="100%" border="1px" cellspacing="2px" cellpadding="1px"><thead><tr><th>System</th><th>Locale</th></tr></thead><tbody><tr><td>UNIX</td><td>C/POSIX</td></tr><tr><td>Java</td><td>Locale("","")</td></tr><tr><td>.NET</td><td>Invariant Culture</td></tr></tbody></table></div><p>Examples of various values for the <code>i18n:locale</code> information item are given below:</p><div class="exampleOuter">
<div class="exampleHeader"><a name="d1e616" id="d1e616"/>Example: Examples of locale values</div><div class="exampleInner"><pre>(01) <i18n:locale>en_US</i18n:locale> <!-- U.S. English -->
(02) <i18n:locale>$default</i18n:locale> <!-- default locale-->
(03) <i18n:locale>zh_Hant_HK</i18n:locale> <!-- Chinese written in
Traditional script for Hong Kong -->
</pre></div></div></div><div class="div2">
<h3><a name="sec-tz" id="sec-tz"/>3.3 Providing Time zone Information</h3><p>The <code>i18n:tz</code> element information item <strong>MAY</strong> appear at most one time in the <b>children</b> property of the <code>i18n:international</code> information item. If present, it <strong>MUST</strong> follow the <code>i18n:locale</code> element information item.</p><div class="exampleInner"><pre>(01) <i18n:tz> <em>(<a href="#RFC822">[RFC 822]</a> value) | (Olson ID <a href="#olsonid">[OLSON ID]</a>) </em></i18n:tz></pre></div><p>The <code>i18n:tz</code> element information item represents the local time zone of the requester or provider. The value of the element <strong>MUST</strong> be either RFC 822-formatted zone offset <a href="#RFC822">[RFC 822]</a> or an Olson ID <a href="#olsonid">[OLSON ID]</a> from the 'olsonid' database. Note that RFC 822 zone offsets are not complete time zone identifiers and Olson identifiers are preferred. It is <a title="implementation defined" href="#dt-implementation-defined">implementation-defined</a> whether an RFC 822-formatted zone offset or an OLson ID is given, and how a choice between these two kinds of values is indicated.</p><p>An example of the <code>i18n:tz</code> element information item using an RFC 822 zone offset is given below:</p><div class="exampleOuter">
<div class="exampleHeader"><a name="d1e674" id="d1e674"/>Example: The <code>tz</code> element information item</div><div class="exampleInner"><pre>(01) <i18n:tz>GMT-0300</i18n:tz>
(02) <i18n:tz>America/Los_Angeles</i18n:tz></pre></div></div></div><div class="div2">
<h3><a name="sec-preferences" id="sec-preferences"/>3.4 Providing Locale Preferences</h3><p>The optional <code>i18n:preferences</code> element information item <strong>MUST</strong> appear at most one time in the <b>children</b> property of the <code>i18n:international</code> element information item. If present, it <strong>MUST</strong> follow the <code>i18n:tz</code> element information item or (if <code>i18n:tz</code> is omitted) the <code>i18n:locale</code> element information item. </p><div class="exampleInner"><pre>(01) <i18n:preferences ...>...</i18n:preferences></pre></div><p>The <code>i18n:preferences</code> element information item represents a way to construct specific locale preferences and overrides. Support for the <code><i18n:preferences></code> element is <strong>OPTIONAL</strong> and specific behavior in relation to any particular preference is <a title="implementation dependent" href="#dt-implementation-dependent">implementation dependent</a>. Implementations of this specification are not required to recognize, support, or acknowledge the <code>i18n:preferences</code> element information item or any of its sub-elements. Services <strong>MUST NOT</strong> require a <code>i18n:preferences</code> element information item be sent in order to operate correctly.</p><p>An example of the usage of <code>i18n:preferences</code> is given below. It describes preferences using <a href="#LDML">[LDML]</a>.</p><div class="exampleOuter">
<div class="exampleHeader"><a name="d1e745" id="d1e745"/>Example: <code>preferences</code> element information item using <a href="#LDML">[LDML]</a></div><p>In this example, the <code>i18n:preferences</code> element information item used to convey the usage of a specific metric system.</p><div class="exampleInner"><pre>(01) <i18n:preferences>
(02) <ldml:measurementSystem type="metric" />
(03) </i18n:preferences></pre></div></div><p>The LDML <code>alias</code> element information item is demonstrated below as another example of the content of the <code>i18n:preferences</code> element information item. <code>alias</code> allows the application to specify a base locale or collection of data from the Common Locale Data Repository <a href="#CLDR">[CLDR]</a> to serve as a basis for other preferences. Thus it can be used to import a large number of settings that the remaining preferences tailor.</p><div class="exampleOuter"><p>If the following i18n header is received and the specific preferences requested are supported, then the service should be expected to obey the locale request of U.S. English ("en-US"), but uses the German ("de_DE") collation specified ("phonebook" in this case).</p><div class="exampleInner"><pre>(01) <i18n:international>
(02) <i18n:locale>en_US</i18n:locale>
(03) <i18n:preferences>
(04) <ldml:collation>
(05) <ldml:alias source="de_DE" type="phonebook"/>
(06) </ldml:collation>
(07) </i18n:preferences>
(08) </i18n:international></pre></div></div></div></div><div class="div1">
<h2><a name="sec-ws-i18n-policy" id="sec-ws-i18n-policy"/>4 Indicating Use of WS-I18N</h2><p>This section is <em>normative.</em></p><p>This section describes a domain-specific policy assertion for describing the capabilities defined in <a href="#sec-i18n"><b>3.1 Internationalization Information in SOAP</b></a> of this document. The mechanism for indicating that a requestor or provider uses the capabilities (or requires their usage) defined in this specification is through the use of the Web Services Policy - Framework <a href="#wsp">[WS Policy Framework]</a> and Web Services Policy - Attachment <a href="#wsp-attach">[WS Policy Attachment]</a> specifications. </p><p>This specification defines one policy assertion called <code>i18np:i18n</code>, reading as "Web Services Internationalization Policy". <a href="#sec-assertion-syntax"><b>4.1 Assertion Syntax</b></a> describes the syntax of this assertion, <a href="#sec-assertion-attachment"><b>4.2 Assertion Attachment</b></a> describes its relevant policy subjects and attachment points.</p><div class="div2">
<h3><a name="sec-assertion-syntax" id="sec-assertion-syntax"/>4.1 Assertion Syntax</h3><p>THe <code>i18np:i18n</code> policy assertion consists of one element information item whose structure is defined below.</p><dl><dt class="label">/i18np:i18n</dt><dd><p>The <code>i18np:i18n</code> element information item indicating the use of the mechanisms defined in <a href="#sec-soap-i18n"><b>3 Internationalization Data Structures for SOAP Messages</b></a> of this specification.</p></dd><dt class="label">/i18np:i18n/@wsp:Optional?</dt><dd><p>This attribute indicates the optionality for the support of this assertion.</p></dd><dt class="label">/i18np:i18n/@{any}</dt><dd><p>This is an extensibility mechanism to allow additional attributes to be added to the element.</p></dd></dl><p>The meaning of this assertion, when present in a policy alternative, is that the requester or provider requires the processing of web services internationalization information, as described in <a href="#sec-soap-i18n"><b>3 Internationalization Data Structures for SOAP Messages</b></a> of this document.</p><p>The <code>wsp:Optional</code> attribute, as a syntactic shortcut, can be used with the <code>i18np:i18np</code> assertion. This indicates two policy alternatives, one which contains the policy assertion, and another which does not. The <code>i18np:i18n</code> element information item MUST NOT include the <code>wsp:Ignorable</code> attribute in its <b>attributes</b> property with a value of true.</p><p>The differentiation between describing the support for this capability and the requirement is demonstrated below, using the <code>wsp:Optional</code> attribute.</p><div class="exampleOuter">
<div class="exampleHeader"><a name="d1e858" id="d1e858"/>Example: Subject supports WS-I18N</div><div class="exampleInner"><pre>(01) <wsp:Policy>
(02) <i18np:i18n wsp:Optional="true"/>
(03) </wsp:Policy></pre></div></div><div class="exampleOuter">
<div class="exampleHeader"><a name="d1e863" id="d1e863"/>Example: Subject requires WS-I18N</div><div class="exampleInner"><pre>(01) <wsp:Policy>
(02) <i18np:i18n/>
(03) </wsp:Policy></pre></div></div></div><div class="div2">
<h3><a name="sec-assertion-attachment" id="sec-assertion-attachment"/>4.2 Assertion Attachment</h3><p>Because the <code>i18np:i18n</code> assertion indicates behavior over all messages in a binding, the assertion has an endpoint policy subject. <a href="#wsp-attach">[WS Policy Attachment]</a>.</p><p><a href="#wsp-attach">[WS Policy Attachment]</a> defines three <a href="#wsdl20">[WSDL 2.0]</a> policy attachment points with endpoint policy subject:</p><ul><li><p>wsdl:interface</p></li><li><p>wsdl:binding</p></li><li><p>wsdl:endpoint</p></li></ul><p>WS-PolicyAttachment also defines three <a href="#wsdl11">[WSDL 1.1]</a> policy attachment
points with endpoint policy subject:</p><ul><li><p>wsdl:portType</p></li><li><p>wsdl:binding</p></li><li><p>wsdl:port</p></li></ul><p>A policy expression containing the <code>i18np:i18n</code> policy
assertion <strong>MUST NOT</strong> be attached to a <code>wsdl:interface</code> or <code>wsdl11:portType</code>; the <code>i18np:i18n</code> policy assertion
specifies a concrete behavior whereas the <code>wsdl:interface</code> or <code>wsdl11:portType</code> is an abstract construct.</p><p>A policy expression containing the <code>i18np:i18n</code> policy assertion MUST, if
present be attached to either a <code>wsdl:binding</code> or <code>wsdl11:binding</code>, or <code>wsdl:endpoint</code> or <code>wsdl11:port</code>.</p><p>When attached to either a <code>wsdl:binding</code> or <code>wsdl11:binding</code>, or <code>wsdl:endpoint</code> or <code>wsdl11:port</code> representing a SOAP 1.2 binding,
the assertion indicates that the designated endpoint is capable of processing the functionalities described in <a href="#sec-soap-i18n"><b>3 Internationalization Data Structures for SOAP Messages</b></a> of this specification. </p><p>The following example demonstrates the use of the <code>i18np:i18n</code> policy assertion in <a href="#wsdl20">[WSDL 2.0]</a>.</p><div class="exampleOuter">
<div class="exampleHeader"><a name="d1e971" id="d1e971"/>Example: Use of <code>i18np:i18n</code> policy assertion in WSDL 2.0</div><div class="exampleInner"><pre>1 <wsdl:description
2 targetNamespace="http://tns.example.com/"
3 xmlns:tns="http://tns.example.com/"
4 xmlns:wsdl="http://www.w3.org/ns/wsdl"
5 xmlns:wsp="http://www.w3.org/ns/ws-policy"
6 xmlns:i18np="http://www.w3.org/2008/04/ws-i18np">
7 <wsp:Policy xml:id="MyPolicy" >
8 <i18np:i18n/>
9 <!-- omitted assertions -->
10 </wsp:Policy>
11 <!-- omitted elements -->
12 <wsdl:binding name="MyBinding" type="tns:MyInterface" >
13 <wsp:PolicyReference
14 URI="#MyPolicy"
15 wsdl:required="true" />
16 <!-- omitted elements -->
17 </wsdl:binding>
18 </wsdl:description></pre></div></div><p>Lines (7-10) are a policy expression that includes an <code>i18np:i18n</code> policy assertion (Line 8)
to indicate that the functionality defined in <a href="#sec-soap-i18n"><b>3 Internationalization Data Structures for SOAP Messages</b></a> of this document may be used.</p><p>Lines (12-17) are a <a href="#wsdl20">[WSDL 2.0]</a> binding. Lines (13-14) indicate that the policy in Lines (7-10) applies to this binding, specifically indicating that the <code>i18n:international</code> element information item must be accepted over all the
messages in the binding. Line (15) indicates that this policy is a required extension.</p><div class="exampleOuter">
<div class="exampleHeader"><a name="d1e994" id="d1e994"/>Example: Use of <code>i18np:i18n</code> policy assertion in WSDL 1.1</div><div class="exampleInner"><pre>1 <wsdl:definitions
2 targetNamespace="example.com"
3 xmlns:tns="example.com"
4 xmlns:wsdl11="http://schemas.xmlsoap.org/wsdl/"
5 xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy"
6 xmlns:i18np="http://www.w3.org/2008/04/ws-i18np">
7 <wsp:Policy xml:id="MyPolicy" >
8 <i18np:i18n/>
9 <!-- omitted assertions -->
10 </wsp:Policy>
11 <!-- omitted elements -->
12 <wsdl:binding name="MyBinding" type="tns:MyPortType" >
13 <wsp:PolicyReference
14 URI="#MyPolicy"
15 wsdl11:required="true" />
16 <!-- omitted elements -->
17 </wsdl:binding>
18 </wsdl:definitions></pre></div></div><p>Lines (7-10) are a policy expression that includes an <code>i18np:i18n</code> policy assertion (Line 8)
to indicate that the functionality defined in <a href="#sec-soap-i18n"><b>3 Internationalization Data Structures for SOAP Messages</b></a> of this document may be used.</p><p>Lines (12-17) are a <a href="#wsdl11">[WSDL 1.1]</a> binding. Lines (13-14) indicate that the policy in Lines (7-10) applies to this binding, specifically indicating that the <code>i18n:international</code> element information item must be accepted over all the
messages in the binding. Line (15) indicates that this policy is a required extension.</p></div></div><div class="div1">
<h2><a name="sec-conformance" id="sec-conformance"/>5 Conformance</h2><p>This section is <em>normative.</em></p><p>An implementation is not compliant with this specification if it fails to satisfy one or more of the <strong>MUST</strong> level requirements defined herein. The XML namespace identifiers for this specification (listed in <a href="#sec-namespaces"><b>2.4 Namespaces</b></a>) <strong>MUST</strong> not be used unless they are compliant with this specification.
</p><p>Normative text within this specification takes precedence over normative outlines, which in turn takes precedence over the XML Schema <a href="#xmlschema1">[XML Schema 1]</a>, <a href="#xmlschema2">[XML Schema 2]</a> descriptions.</p></div></div><div class="back"><div class="div1">
<h2><a name="sec-normrefs" id="sec-normrefs"/>A Normative References</h2><dl><dt class="label"><a name="bcp47" id="bcp47"/>BCP 47</dt><dd>Addison Phillips, Mark Davis, editors. <a href="http://www.rfc-editor.org/rfc/bcp/bcp47.txt">Tags for the Identification of Languages</a>, September 2006. Available at <a href="http://www.rfc-editor.org/rfc/bcp/bcp47.txt">http://www.rfc-editor.org/rfc/bcp/bcp47.txt</a>.</dd><dt class="label"><a name="LDML" id="LDML"/>LDML</dt><dd>Mark Davis,
editor. <a href="http://unicode.org/reports/tr35/tr35-8.html">Locale Data Markup Language (LDML)</a>, Unicode Technical Standard #35.
Available at <a href="http://unicode.org/reports/tr35/tr35-5.html">http://unicode.org/reports/tr35/tr35-8.html</a>. The latest version of <a href="http://unicode.org/reports/tr35/">LDML</a> is available at http://unicode.org/reports/tr35/.
</dd><dt class="label"><a name="olsonid" id="olsonid"/>OLSON ID</dt><dd><a href="http://www.twinsun.com/tz/tz-link.htm">The TZID Database (aka Olson timezone database)
Timezone and daylight savings information.</a>. Available at <a href="ftp://elsie.nci.nih.gov/pub/">ftp://elsie.nci.nih.gov/pub/</a>. For general information, see <a href="http://www.twinsun.com/tz/tz-link.htm">http://www.twinsun.com/tz/tz-link.htm</a> (See ftp://elsie.nci.nih.gov/pub/.)</dd><dt class="label"><a name="RFC822" id="RFC822"/>RFC 822</dt><dd> David H. Crocker. <a href="http://www.ietf.org/rfc/rfc822.txt">Standard for the Format of Arpa Internet Text Messages</a>. Available at <a href="http://www.ietf.org/rfc/rfc822.txt">http://www.ietf.org/rfc/rfc822.txt</a>. (See http://www.ietf.org/rfc/rfc822.txt.)</dd><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd>S. Bradner. <a href="http://www.ietf.org/rfc/rfc2119.txt">Key Words for use in RFCs to Indicate Requirement Levels</a>. IETF RFC 2119. Available at <a href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a>.
(See http://www.ietf.org/rfc/rfc2119.txt.)</dd><dt class="label"><a name="soap12" id="soap12"/>SOAP 1.2</dt><dd>Martin Gudgin, Marc Hadley, Noah Mendelsohn, Jean-Jacques Moreau, Henrik Frystyk Nielsen, Anish Karmarkar, Yves Lafon, editors. <a href="http://www.w3.org/TR/2007/REC-soap12-part1-20070427/">SOAP Version 1.2 Part 1: Messaging Framework (Second Edition)</a>, W3C Recommendation 27 April 2007. Available at <a href="http://www.w3.org/TR/2007/REC-soap12-part1-20070427/">http://www.w3.org/TR/2007/REC-soap12-part1-20070427/</a>. The latest version of <a href="http://www.w3.org/TR/soap12-part1/">SOAP 1.2</a> is available at http://www.w3.org/TR/soap12-part1/ .</dd><dt class="label"><a name="wsdl11" id="wsdl11"/>WSDL 1.1</dt><dd>Erik Christensen, Francisco Curbera, Greg Meredith, Sanjiva Weerawarana, editors. <a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315">Web Services Description Language (WSDL) 1.1</a>, W3C Note 15 March 2001. Available at <a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315">http://www.w3.org/TR/2001/NOTE-wsdl-20010315</a>. The latest version of <a href="http://www.w3.org/TR/wsdl">WSDL 1.1</a> is available at http://www.w3.org/TR/wsdl .</dd><dt class="label"><a name="wsdl20" id="wsdl20"/>WSDL 2.0</dt><dd>Roberto Chinnici, Jean-Jacques Moreau, Arthur Ryman, Sanjiva Weerawarana, editors. <a href="http://www.w3.org/TR/2007/REC-wsdl20-20070626">Web Services Description Language (WSDL) Version 2.0 Part 1: Core Language</a>, W3C Recommendation 26 June 2007. Available at <a href="http://www.w3.org/TR/2007/REC-wsdl20-20070626">http://www.w3.org/TR/2007/REC-wsdl20-20070626</a>. The latest version of <a href="http://www.w3.org/TR/wsdl20">WSDL 2.0</a> is available at http://www.w3.org/TR/wsdl20 .</dd><dt class="label"><a name="wsp" id="wsp"/>WS Policy Framework</dt><dd> Asir S Vedamuthu, David Orchard, Frederick Hirsch, Maryann Hondo, Prasad Yendluri, Toufic Boubez, Ümit Yalçinalp, editors. <a href="http://www.w3.org/TR/2007/REC-ws-policy-20070904">Web Services Policy 1.5 - Framework</a>, W3C Recommendation 04 September 2007. Available at <a href="http://www.w3.org/TR/2007/REC-ws-policy-20070904">http://www.w3.org/TR/2007/REC-ws-policy-20070904</a>. The latest version of <a href="http://www.w3.org/TR/ws-policy/">WS Policy</a> is available at http://www.w3.org/TR/ws-policy/ .</dd><dt class="label"><a name="wsp-attach" id="wsp-attach"/>WS Policy Attachment</dt><dd>Asir S Vedamuthu, David Orchard, Frederick Hirsch, Maryann Hondo, Prasad Yendluri, Toufic Boubez, Ümit Yalçinalp, editors. <a href="http://www.w3.org/TR/2007/REC-ws-policy-attach-20070904">Web Services Policy 1.5 - Attachment</a>, W3C Recommendation 04 September 2007. Available at <a href="http://www.w3.org/TR/2007/REC-ws-policy-attach-20070904">http://www.w3.org/TR/2007/REC-ws-policy-attach-20070904</a>. The latest version of <a href="http://www.w3.org/TR/ws-policy-attach/">WS Policy Attachment</a> is available at http://www.w3.org/TR/ws-policy-attach/ .</dd><dt class="label"><a name="XMLInfoset" id="XMLInfoset"/>XML Infoset</dt><dd>John Cowan, Richard Tobin, editors. <a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204">XML Information Set (Second Edition)</a>, W3C Recommendation 4 February 2004. Available at <a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204">http://www.w3.org/TR/2004/REC-xml-infoset-20040204</a>. The latest version of <a href="http://www.w3.org/TR/xml-infoset/">XML Infoset</a> is available at http://www.w3.org/TR/xml-infoset/ .</dd><dt class="label"><a name="xmlschema1" id="xmlschema1"/>XML Schema 1</dt><dd>Henry S. Thompson, David Beech, Murray Maloney, Noah Mendelsohn, editors. <a href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/">XML Schema Part 1: Structures Second Edition</a>, W3C Recommendation 28 October 2004. Available at <a href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/">http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/</a>. The latest version of <a href="http://www.w3.org/TR/xmlschema-1/">XML Schema 1</a> is available at http://www.w3.org/TR/xmlschema-1/ .</dd><dt class="label"><a name="xmlschema2" id="xmlschema2"/>XML Schema 2</dt><dd>Paul V. Biron, Ashok Malhotra. <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/">XML Schema Part 2: Datatypes Second Edition</a>, W3C Recommendation 28 October 2004. Available at <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/">http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/</a>. The latest version of <a href="http://www.w3.org/TR/xmlschema-2/">XML Schema 2</a> is available at http://www.w3.org/TR/xmlschema-2/ .</dd><dt class="label"><a name="xpath10" id="xpath10"/>XPath 1.0</dt><dd>James Clark, Steve DeRose, editors. <a href="http://www.w3.org/TR/1999/REC-xpath-19991116">XML Path Language (XPath)</a>, W3C Recommendation 16 November 1999. Available at <a href="http://www.w3.org/TR/1999/REC-xpath-19991116">http://www.w3.org/TR/1999/REC-xpath-19991116</a>. The latest version of <a href="http://www.w3.org/TR/xpath">XPath 1.0</a> is available at http://www.w3.org/TR/xpath .</dd></dl></div><div class="div1">
<h2><a name="sec-xmlschema-documents" id="sec-xmlschema-documents"/>B XML Schema Documents</h2><p>This section is <em>normative</em>.</p><p>This section provides the following schemas:</p><ul><li><p><a href="ws-i18n.xsd">XML Schema document for WS-I18N</a> (see <a href="#sec-soap-i18n"><b>3 Internationalization Data Structures for SOAP Messages</b></a> of this specification)</p></li><li><p><a href="ws-i18np.xsd">XML Schema document indicating the use of WS-I18N</a> (see <a href="#sec-ws-i18n-policy"><b>4 Indicating Use of WS-I18N</b></a> of this specification)</p></li></ul></div><div class="div1">
<h2><a name="sec-informrefs" id="sec-informrefs"/>C Informative References (Non-Normative)</h2><dl><dt class="label"><a name="CLDR" id="CLDR"/>CLDR</dt><dd><a href="http://www.unicode.org/cldr/">Common Locale Data Repository</a>, Unicode Consortium. Available at <a href="http://www.unicode.org/cldr/">http://www.unicode.org/cldr/</a>.</dd><dt class="label"><a name="I18NScenarios" id="I18NScenarios"/>I18NScenarios</dt><dd>Debasish Banerjee, Martin Dürst, Mike McKenna, Addison Phillips, Takao Suzuki, Tex Texin, Andrea Vine. <a href="http://www.w3.org/TR/2004/NOTE-ws-i18n-scenarios-20040730/">Web Services Internationalization Usage Scenarios</a>. W3C Working Draft December 2003. Available at <a href="http://www.w3.org/TR/2004/NOTE-ws-i18n-scenarios-20040730/">http://www.w3.org/TR/2004/NOTE-ws-i18n-scenarios-20040730/</a>. The latest version of <a href="http://www.w3.org/TR/ws-i18n-scenarios/">ws-i18n-scenarios</a> is available at http://www.w3.org/TR/ws-i18n-scenarios/. (See http://www.w3.org/International/ws/ws-i18n-scenarios-edit/Overview.xml.)</dd><dt class="label"><a name="RFC3282" id="RFC3282"/>RFC 3282</dt><dd>Harald Alvestrand. <a href="http://www.apps.ietf.org/rfc/rfc3282.html">Content Language Headers</a>. IETF Standards track document, May 2002. Work in progress. See <a href="http://www.ietf.org/rfc/rfc3282.txt">http://www.ietf.org/rfc/rfc3282.txt</a>. (See http://www.apps.ietf.org/rfc/rfc3282.html.)</dd></dl></div><div class="div1">
<h2><a name="sec-revlog" id="sec-revlog"/>D Revision Log (Non-Normative)</h2><p>The following revision log contains changes since the <a href="http://www.w3.org/TR/2005/WD-ws-i18n-20050914/">publication from 14 September 2005.</a></p><ul><li><p>Kept the functionality of Web Services Internationalization, but realized it now relying on <a href="#wsp">[WS Policy Framework]</a> and <a href="#wsp-attach">[WS Policy Attachment]</a>. This change lead to a complete restructuring of the document.</p></li></ul></div><div class="div1">
<h2><a name="sec-acknowledgements" id="sec-acknowledgements"/>E Acknowledgements (Non-Normative)</h2><p>This document is the work of the <a href="http://www.w3.org/International/core/">W3C i18n Core Working Group</a>.</p></div></div></body></html>