internationalization and service capabilities n.
Skip this Video
Loading SlideShow in 5 Seconds..
Internationalization and Service Capabilities PowerPoint Presentation
Download Presentation
Internationalization and Service Capabilities

Loading in 2 Seconds...

play fullscreen
1 / 15

Internationalization and Service Capabilities - PowerPoint PPT Presentation

  • Uploaded on

Web Services:. Internationalization and Service Capabilities. Constraints and Capabilities Workshop Presented by Addison P. Phillips Director, Globalization Architecture webMethods, Inc. About This Presentation.

I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
Download Presentation

PowerPoint Slideshow about 'Internationalization and Service Capabilities' - kaelem

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
internationalization and service capabilities

Web Services:

Internationalization andService Capabilities

Constraints and Capabilities Workshop

Presented by Addison P. Phillips

Director, Globalization Architecture

webMethods, Inc.

about this presentation
About This Presentation
  • Web service constraints and capabilities: Internationalization makes a good use case.
    • The classic internationalization model
    • Applying the internationalization model to Web services
    • Why constraints? Why capabilities?
w3c internationalization working group
W3C Internationalization Working Group
  • Web Services Internationalization Usage Scenarios
  • Web Services Internationalization Requirements
  • (draft) Internationalization Core WG charter
web services and internationalization
Web Services and Internationalization
  • So Web Services are internationalized, right?
    • Locale-neutral representation (XML Schema)
    • No user interface (machine-to-machine)
    • Inherits XML’s rich support for Unicode, language tags, and so forth
    • “Internationalization is the problem of the service author, not the provider.”
programming paradigms the classic i18n model
Programming Paradigms: the classic I18N model
  • Desktop
    • Locales in the environment
  • Web Application
    • Locale-related APIs and state mechanisms
  • Web Service?
    • Uh…
the importance of composition and ws
The Importance of Composition and WS*
  • Web Services (SOAP, WSDL) allow you to use “features” and “properties” to add capabilities.
    • Use different features together to get different results.
  • WS-* standardization provides:
    • Quality-of-Service
    • Execution State
international patterns what are they
International Patterns: What are they?
  • Four Patterns:
    • Locale Neutral
    • Service Determined
    • Client Influenced
    • Data/Resource Driven
what does that service do
What does that service do?
  • Services generally run in the locale of the server where they are installed
    • May not be the same as the WS Provider
    • May not give the results the user expects
    • No way for the user to control it
  • Developers must program services to provide international capabilities
    • Provide locale model
    • Provide localization model and capabilities
    • Define multiple endpoints for different locales
    • “Providers” do nothing for you.
web service descriptions
Web Service Descriptions
  • Exchange a locale that is explicitly in the service signature.
    • No standards exist for doing this
    • Strong platform and programming language dependency
  • Exchange a locale that is implied in the service’s operation.
    • Web service descriptions don’t convey this information.
  • Describe how a particular endpoint will work.
    • There may be multiple endpoints in multiple geographies.
  • Language negotiation
    • Services still need human readable messages.
    • Faults (exceptions) need human readable messages.
    • Service may retrieve, process, store, or otherwise access text.
  • Locale negotiation
    • Making the service do what the user wants.
      • Collation, calendar, text processing, currency, routing, addressing, formatting, business rules, tax authority, legal requirements, etc.
basic conclusions
Basic Conclusions
  • Web services need “international preferences”
    • Personally: these are “locales”
  • Web service descriptions need to describe “policies”
    • “This service runs in the fr-FR locale.”
    • “The requester can tell me what locale to use.”
    • “If you request a locale I don’t support, I return a Fault message.”
  • Locale identifiers are needed.
    • You can tell me what locale to run in… if we can agree on what the identifier means.
  • Web service discovery needs more internationalization.
constraints and capabilities
Constraints and Capabilities
  • Internationalization model describes capabilities:
    • Policy? Runtime locale? Etc.
  • Internationalization model describe constraints:
    • Available locales
    • Available resources
    • Available language content
    • Runtime restrictions
  • Internationalization is an excellent example of the kinds of Web service constraints and capabilities that need to be communicated.
  • Standardization is necessary to ensure interoperability.
  • It won’t happen by magic.
  • Plays well with others?