index.html 16.1 KB

Raw Blame History Permalink

<?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 lang="EN" xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html;charset=utf-8" /><title>Requirements for the Internationalization of Web Services</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-WG-NOTE.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" />Requirements for the Internationalization of Web Services</h1>
<h2><a name="w3c-doctype" id="w3c-doctype" />W3C Working Group Note 16 November 2004</h2><dl><dt>This version:</dt><dd>
    <a href="http://www.w3.org/TR/2004/NOTE-ws-i18n-req-20041116/">http://www.w3.org/TR/2004/NOTE-ws-i18n-req-20041116</a>
  </dd><dt>Latest version:</dt><dd>
    <a href="http://www.w3.org/TR/ws-i18n-req/">http://www.w3.org/TR/ws-i18n-req</a>
  </dd><dt>Previous version:</dt><dd>
     <a href="http://www.w3.org/TR/2003/WD-ws-i18n-req-20031217/">http://www.w3.org/TR/2003/WD-ws-i18n-req-20031217</a>
  </dd><dt>Editor:</dt><dd>Addison P. Phillips, webMethods, Inc.</dd></dl><p>This document is also available in these non-normative formats: <a href="Overview.xml">XML</a>.</p><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2004 <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 describes requirements for internationalizing Web services.</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 is a
     <a href="http://www.w3.org/2004/02/Process-20040205/tr.html#WGNote">W3C Working Group Note</a>, made available by the
     <a href="http://www.w3.org/International/">W3C Internationalization Working Group</a>
	  (<a href="http://www.w3.org/International/ws/">Web Services Internationalization Task Force</a>)
	  as part of the
	  <a href="http://www.w3.org/International/Activity">W3C Internationalization Activity</a>.
	  It describes requirements for the internationalization of Web services
	  and is intended for review by W3C Members and other interested parties.
	  It is also intended to serve as a basis for future work on Web service
	  internationalization.</p><p>There were only very few changes since the last publication. The main
	  change is the addition of requirement <a href="#R007">R007</a>
	  about integration with the overall Web services architecture and existing
	  technologies. The wording of the other requirements was changed to not favor
	  solutions that are still under discussion. Text has been streamlined and
	  references have been updated.</p><p>The Internationalization Working Group
	  (Web Services Internationalization Task Force) thinks that this document has
	  reached a sufficient level of maturity to be published as a Working Group Note,
	  and does not intend to issue new versions in the near future.
	  This does not exclude that the document may be updated at a later stage, after
	  more experience has been gained with the internationalization of Web services.</p><p>The Internationalization Working Group or its successor will keep track of
	  any further comments and discussion relating to this document, and invites any
	  such comments or discussion. Please send comments on this document to the
	  <a href="mailto:www-i18n-comments@w3.org">www-i18n-comments@w3.org</a>
	  mailing list (<a href="http://lists.w3.org/">public archive</a>).
	  Please use [Web Services] or [WSReq] in the subject.</p><p>At the time of publication, the Working Group believed there were no
    patent disclosures relevant to this specification. A current list of
    patent disclosures relevant to this specification may be found on the
    <a href="http://www.w3.org/International/2002/Disclosures">Working Group's patent disclosure page</a>.</p><p>Publication as a Working Group Note does not imply endorsement by the W3C,
     including the Team and Membership.</p></div><div class="toc">
<h2><a name="contents" id="contents" />Table of Contents</h2><p class="toc">1 <a href="#IDAIQUS">Introduction</a><br />
2 <a href="#IDA3QUS">Requirements</a><br />
    2.1 <a href="#R007">R007 Integrate Internationalization with Web Services Standards</a><br />
    2.2 <a href="#R001">R001 Locale Information in SOAP</a><br />
    2.3 <a href="#R002">R002 Locale Information in WSDL</a><br />
    2.4 <a href="#R003">R003 International Policies in WSDL</a><br />
    2.5 <a href="#R004">R004 International Policies in SOAP</a><br />
    2.6 <a href="#R005">R005 Locale Identifiers</a><br />
    2.7 <a href="#R006">R006 Multi-Lingual Service Discovery Requirements</a><br />
</p>
<h3><a name="appendices" id="appendices" />Appendices</h3><p class="toc">A <a href="#IDAUUUS">References</a> (Non-Normative)<br />
B <a href="#IDAZVUS">Acknowledgements</a> (Non-Normative)<br />
</p></div><hr /><div class="body"><div class="div1">
<h2><a name="IDAIQUS" id="IDAIQUS" />1 Introduction</h2><p>A Web Service is a software application identified by a URI <a href="#RFC2396">[RFC2396]</a>,
whose interfaces and binding are capable of being defined, described and discovered by XML
artifacts, and which supports direct interactions with other software applications using XML-based
messages via Internet-based protocols. The full range of application functionality can be
exposed in a Web service. </p><p>The W3C Internationalization Working Group, Web Services Task Force,
was chartered to examine Web Services for internationalization issues.
The result of this work is the Web Services Internationalization Usage Scenarios document
<a href="#WSIUS">[WSIUS]</a>. Some of the scenarios in that document
demonstrate that, in order to achieve worldwide usability, internationalization
options must be exposed in a consistent way in the definitions, descriptions,
messages, and discovery mechanisms that make up Web services.</p><p>The following is a list of the requirements to address these issues.</p></div><div class="div1">
<h2><a name="IDA3QUS" id="IDA3QUS" />2 Requirements</h2><div class="div2">
<h3><a name="R007" id="R007" />2.1 R007 Integrate Internationalization with Web Services Standards</h3><p><em>Problem Statement:</em> Internationalization should be integrated with
the architecture and general evolution of Web services and should not represent
a departure in design from existing solutions. </p><p><em>Requirement:</em> Specifications and formats developed for the
internationalization of Web services should be composable with other
quality-of-service type standards, such as those related to security,
reliable messaging, or addressing.</p></div><div class="div2">
<h3><a name="R001" id="R001" />2.2 R001 Locale Information in SOAP</h3><p><em>Problem Statement:</em> Service providers and services need information
about the locale, language preference, time zone, or other international preferences
(such as currency, collation, etc.) of the requester.</p><p><em>Requirement:</em>
A Specification or Specifications for a SOAP header or data structure (possibly a SOAP Feature, see <a href="#SOAPpart2">[SOAP-Feature]</a>,
<a href="http://www.w3.org/TR/2003/REC-soap12-part2-20030624/#soapfeatspec">Section 5: A Convention for Describing Features and Bindings</a>)
to send the Web service provider international context information
(such as locale, language, or other culturally linked preferences)
about the requester and which the provider can use to tailor the language, invocation,
or operation of services or the operation of the provider
(such as language selection in the generation of Faults and so forth).</p></div><div class="div2">
<h3><a name="R002" id="R002" />2.3 R002 Locale Information in WSDL</h3><p><em>Problem Statement:</em> Service providers need to indicate that the SOAP headers or data structures
described in R001 are available for a specific service or collection of services. The specific "international preference" information of use to the service or aspects of the service must be described so that properly formatted data can be interchanged, enabling internationalized operation.</p><p><em>Requirement:</em> A specification or specifications for WSDL data structures that can be use in Web service descriptions to indicate  that the headers or data structures described in R001 are available for a particular service and describe the binding and invocation requirements related to this.</p></div><div class="div2">
<h3><a name="R003" id="R003" />2.4 R003 International Policies in WSDL</h3><p><em>Problem Statement:</em> Service providers need a way to provide information
about how a specific instance of a locale-affected Web service will execute or to differentiate
instances of the same service. </p><p><em>Examples:</em>   For service 'Z', binding 'A' executes in French, binding 'B' executes
in Japanese, and binding 'C' attempts to match the user's preferences.</p><p><em>Requirement:</em> A specification or specifications for WSDL data structures that allow a service to describe a "locale
execution policy" for a service or a binding of a service, including any additional derived
information of interest to users of the service (allowing users to select the service and
binding that most closely matches their needs or to tailor the operation of the service via
header information). The specification(s) must allow services to describe one or more languages or
locales available for a specific service and allow for a runtime user choice (language/locale
negotiation) when that is appropriate. They must also provide a way to indicate that a specific
service always executes using specific international settings or returns data in a specific
language.</p></div><div class="div2">
<h3><a name="R004" id="R004" />2.5 R004 International Policies in SOAP</h3><p><em>Problem Statement:</em> Given the WSDL features in R003, requesters must be able to
indicate their preferences (when choices exist) when invoking a service and providers must be able to indicate which choice was
applied when the service actually executed (as in a response).</p><p><em>Requirement:</em> A specification or specifications for SOAP headers or data structures  that describe the locale preferences the
requester wishes to have applied to a service (in a request) or which were actually
applied to a service by the provider (in a response) as described in the Web service
description defined in R003. This mechanism may be the same as in R001.</p></div><div class="div2">
<h3><a name="R005" id="R005" />2.6 R005 Locale Identifiers</h3><p><em>Problem Statement:</em> Although there exist standards for identifying languages
and language preferences on the Web, there are no standards for identifying locales or certain
other international preferences. These data structures are of interest in enabling Web services
and other Web applications for multi-lingual or global operation.</p><p><em>Requirement:</em> A standard for identifying platform neutral international
preferences (that is, locale identifiers). This should include the protocol for matching requests with actual values (locale negotiation), along with guidelines for implementation. Possible mechanisms for this might be a standard
extension to the proposed extension <a href="#ID-langtags">[ID-langtags]</a> of
RFC 3066 <a href="#RFC3066">[RFC3066]</a> that describes international preferences or the use of URIs to refer to locale data or identifiers on the Web.</p></div><div class="div2">
<h3><a name="R006" id="R006" />2.7 R006 Multi-Lingual Service Discovery Requirements</h3><p><em>Problem Statement:</em> Web service discovery needs to allow
users to find the same service in multiple languages and to find services that will meet
their specific language or locale requirements.</p><p><em>Requirement:</em> Document best practices and approaches  for the discovery of Web services,
including via non-W3C standards such as UDDI.</p><p><em>Requirement:</em> Liaise with appropriate standards organizations working on Web service discovery.</p></div></div></div><div class="back"><div class="div1">
<h2><a name="IDAUUUS" id="IDAUUUS" />A References (Non-Normative)</h2><dl><dt class="label"><a name="RFC3066" id="RFC3066" />[RFC3066]</dt><dd>"Tags for the Identification of Languages",
Harald Alvestrand,
January 2001.  (See http://www.ietf.org/rfc/rfc3066.txt.)</dd><dt class="label"><a name="ID-langtags" id="ID-langtags" />[ID-langtags]</dt><dd>"Tags for the Identification of Languages",
Addison Phillips and Mark Davis,
Internet-Draft draft-phillips-langtags-08, 9 November 2004, work in progress (this document is intended as a replacement for RFC3066).  (See http://www.ietf.org/internet-drafts/draft-phillips-langtags-07.txt.)</dd><dt class="label"><a name="WSIUS" id="WSIUS" />[WSIUS]</dt><dd>"Web Services Internationalization Usage Scenarios",
    Debasish Banerjee, Martin J. Dürst,
    Mike McKenna, Addison Phillips, Takao Suzuki, Tex Texin, Mary Trumble, Andrea Vine, Kentaroh Noji, W3C Working Group Note, 30 July 2004.  (See http://www.w3.org/TR/ws-i18n-scenarios/.)</dd><dt class="label"><a name="RFC2396" id="RFC2396" />[RFC2396]</dt><dd>"Uniform Resource Identifiers (URI): Generic Syntax",
Tim Berners-Lee, Roy Fielding, and Larry Masinter,
August 1998.  (See http://www.ietf.org/rfc/rfc2396.txt.)</dd><dt class="label"><a name="SOAPpart2" id="SOAPpart2" />[SOAP-Feature]</dt><dd>"SOAP Version 1.2, Part 2 (Adjuncts)",
Martin Gudgin, Marc Hadley, Noah Mendelsohn, Jean-Jacques Moreau, and Henrik Frystyk Nielsen,
W3C Recommendation 24 June 2003.  (See http://www.w3.org/TR/2003/REC-soap12-part2-20030624/#soapfeatspec.)</dd></dl></div><div class="div1">
<h2><a name="IDAZVUS" id="IDAZVUS" />B Acknowledgements (Non-Normative)</h2><p>This document is the work of the Web Services Task Force
 of the W3C Internationalization Working Group. The participants in this task force contributing to the development of these requirements and the content of this document are: Debasish Banerjee (IBM), Martin Dürst (W3C), Mike McKenna (University of California), Takao Suzuki (Microsoft), Tex Texin (Xencraft), Mary Trumble (IBM), Andrea Vine (Sun Microsystems)</p></div></div></body></html>