11.3.3 I-017: Data with Additional 'Attributes'

   <?xml version='1.0' ?>
   <env:Envelope xmlns:env="http://www.w3.org/2002/06/soap-envelope">
    <env:Header>
    </env:Header>
    <env:Body>
     <c:getAvailableFlightResponse>
      <c:price c:currency="USD">123.55</c:price>
      <c:departuredate c:location="JFK">2003-05-31</c:departuredate>
      <c:departuretime c:location="JFK">13:30:00</c:departuretime>
     </c:getAvailableFlightResponse>
    </env:Body>
   </env:Envelope>

   <?xml version='1.0' ?>
   <env:Envelope xmlns:env="http://www.w3.org/2002/06/soap-envelope">
    <env:Header>
    </env:Header>
    <env:Body>
     <c:getAvailableFlightResponse>
      <c:price>
       <c:currency>USD<c:currency>
       <c:amount>123.55</c:amount>
      </c:price>
      <c:departuredate>
       <c:location>JFK</c:location>
       <c:date>2003-05-31</c:date>
      </departuredate>
      <c:departuretime>
       <c:location>JFK</c:location>
       <c:time>13:30:00</c:time>

      </departuretime>
     </c:getAvailableFlightResponse>
    </env:Body>
   </env:Envelope>

   <?xml version='1.0' ?>
   <env:Envelope xmlns:env="http://www.w3.org/2002/06/soap-envelope" >
    <env:Header>
    </env:Header>
    <env:Body>
     <c:purchase>
      <c:apple>
       <c:currency>JPY</c:currency>
       <c:amount>123.55</c:amount>
      </c:apple>
      <c:orange>
       <c:currency>USD</c:currency>
       <c:amount>325.78</c:amount>
      </c:orange>
     <c:peach>
      <c:currency>EUR</c:currency>
      <c:amount>36.55</c:amount>
     </c:peach>
    </c:purchase>
   <env:Body>
   </env:Envelope>

   <?xml version='1.0' ?>
   <env:Envelope xmlns:env="http://www.w3.org/2002/06/soap-envelope" >
    <env:Header>
     <WS-I18N:WSinternationalization xmlns:WS-I18N="http://example.org/2002/11/21/WS-I18N">
      <WS-I18N:Currency>JPY</WS-I18N:Currency>
     </WS-I18N:WSinternationalization>
    </env:Header>
   <env:Body>
    <c:purchase>
     <c:apple>
      <c:price>123.55</c:price>
     </c:apple>
     <c:orange>
      <c:price>325.78</c:price>
     </c:orange>
     <c:peach>
      <c:price>36.55</c:price>
     </c:peach>
     </c:purchase>
    </env:Body>
   </env:Envelope>

   <?xml version='1.0' ?>
   <env:Header>
    <WS-I18N:WSinternationalization
       xmlns:WS-I18N="http://example.org/2002/11/21/WS-I18N">
     <WS-I18N:dataTypePreference>
      <ja:JDate xmlns:ja="http//example.org/2003/12/3/ja">EYY-MM-DD</WS-I18N:JDate>
     </WS-I18N:dataTypePreference>
    </WS-I18N:WSinternationalization>
   </env:Header>
   <env:Body>
    <departuredate>H14-05-31</departuredate>
   </env:Body>

11.6 Finding Services

11.6.1 I-026: Searching for Web Services

Repositories and search-able meta-data (such as UDDI [UDDI]) about Web services need to provide support for multiple language searches. Transport layer issues do not allow XML data structures to be used for resolution, except by reference (e.g. the receiver must down-load a separate resource asynchronously to "decode" the preference). Tags on this layer may be necessary in place of XML data structures.

Using xml:lang and multiple entries, a Service Provider can publish text information about their service in multiple languages.  The name, description, address, and personName UDDI elements MAY be adorned with the xml:lang attribute to indicate the language in which their content is expressed.  The policyDescription element contains a description of the effect of the policy implementation.  This element can be adorned with the xml:lang attribute and can appear multiple times to allow for translations of the policy description.  Providers are encouraged to do this for target language markets that their service may support.   

Ideally, the entity names in UDDI should also provide and Alternate Name in RFC-2277 default language, readable in English.  This provides a fall back mechanism to allow a search to identify services even if the named contents may be in a script that is not readable by the entity doing the search.

(From the UDDI Spec)

The following shows an example of romanization where the primary name of the business (a Chinese flower shop) is in Chinese, and its alternative name is a romanization:

<businessEntity . . . >

  ........

  <name xml:lang="zh">黄河花店</name>

  <name xml:lang="en">Huang He Hwa Dian</name>

    .....

</businessEntity>

The following shows an example of transliteration where the primary name of the business is in Chinese, and is a transliteration of its alternative English name:

<businessEntity . . . >

  ........

  <name xml:lang="zh">康柏電腦股份有限公司</name>

  <name xml:lang="en">Compaq Computer Taiwan Limited</name>

    .....

</businessEntity>

The following example XML fragment shows an address written in two languages, English and Chinese, as indicated by the xml:lang attribute:

<address useType=”Sales office” xml:lang="en" tModelKey=”uddi:…”>

   <addressLine>7 F</addressLine>

   <addressLine>No. 245 </addressLine>

   <addressLine>Sec. 1</addressLine>

  <addressLine>Tunhua South Road</addressLine>

   <addressLine>Taipei </addressLine>

</address>

</address><address useType=”Sales office” xml:lang="zh" tModelKey=”uddi:…”>

   <addressLine> 台北市 </addressLine>

  <addressLine> 敦化南路</addressLine>

   <addressLine> 一段</addressLine>

   <addressLine> 245 號</addressLine>

   <addressLine> 7 樓</addressLine>

   …

</address>