Globalization and normalization features for processing business objects

• US 20020184308A1
• Filed: 10/25/2001
• Published: 12/05/2002
• Est. Priority Date: 08/23/1999
• Status: Abandoned Application

• Current Assignee: Asera, Inc. (Virtusa Corporation)
• Original Assignee: Asera, Inc. (Virtusa Corporation)
• Inventors: Sakata, Maki, Vij, Rajiv, Levy, Martin J.
• Application Number:
  US10/027,570
• Publication Number:
  US 20020184308A1
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G06F 8/38 for implementing user interfaces
• CPC Class Codes: G06F 9/454 Multi-language systems; Localisation; Internationalisation

Abstract

A globalization system for processing data in a multiple-locale or multilingual environment. A range of functionality is provided through various classes and interfaces that can be associated with subsystems running in the environment. These interfaces and classes provide for the development of subsystems (i.e., applications, servers, adapters, and so forth) that are independent of knowledge of languages and data formats of a particular locale. A locale associated with various data can be used to dynamically configure information. A normalization capability is also provided for standardizing the representation of data coming into a processing domain from various locales.

Claims

1. A globalization system for processing multi-locale information being sent to and received from a variety of external sources, the globalization system comprising:

a server domain having information objects to be processed and displayed;

at least one locale indicator associated with each information object; and

a locale-sensitive mechanism associated with processing the information objects for accessing certain locale specific information,

whereby the locale-specific information is used to uniformly process the information object according to certain requirements of the locale.

2. The globalization system of claim 1, wherein the multi-locale information includes multilingual information.

3. The globalization system of claim 1, wherein the locale-specific information includes locale-specific translated text and images.

4. The globalization system of claim 3, wherein the locale-specific information is stored in various resource files.

5. The globalization system of claim 4, wherein the resource files are external to the server domain.

6. The globalization system of claim 3, wherein the locale-specific translated text and images are used to display the information to a user, based upon the locale of the user.

7. The globalization system of claim 6, wherein the locale-specific information includes date, time, and time-zone formatting.

8. The globalization system of claim 6, wherein the locale-specific information includes currency formatting.

9. The globalization system of claim 6, wherein the locale-specific information includes numeric formatting.

10. A multi-locale processing configuration for uniformly processing multilingual information being sent to and received from a variety of external sources, the processing configuration comprising:

a processing domain for containing information objects to be processed;

at least one locale indicator associated with each information object; and

a mechanism for accessing certain locale-specific information,

whereby the locale-specific information is used for the parsing, formatting, and transformation of multilingual data in a multilingual software environment.

11. The multi-locale processing configuration of claim 10, wherein the information objects include methods and data members that can be instantiated in different ways.

12. The multi-locale processing configuration of claim 10, wherein the information objects are instantiated via programming calls to the objects.

13. The multi-locale processing configuration of claim 10, wherein the information objects are instantiated via configuration of the objects.

14. The multi-locale processing configuration of claim 10, wherein the information objects are instantiated via a combination of programming calls to the objects and configuration of the objects.

16. The multi-locale processing configuration of claim 15, wherein the configuration further includes at least one class associated with each different subsystem, the class being used to facilitate the handling of different formatting and data conventions.

17. The multi-locale processing configuration of claim 16, wherein the interface is programmatically associated with each subsystem by a developer.

18. The multi-locale processing configuration of claim 17, wherein the subsystems include applications, servers, and adapters.

20. The multi-locale processing configuration of claim 19, wherein the integration interface is configured through an interface-specific configuration file.

21. The multi-locale processing configuration of claim 20, wherein the configuration file includes configurable mapping interfaces that facilitate normalization between conventions.

22. The multi-locale processing configuration of claim 21, wherein the configuration file is stored external to the interface.

23. The multi-locale processing configuration of claim 21, wherein the mapping interfaces includes character-set encoding normalization.

24. The multi-locale processing configuration of claim 21, wherein the mapping interfaces includes vendor specific naming format normalization.

25. The multi-locale processing configuration of claim 21, wherein the mapping interfaces includes data format normalization.

26. The multi-locale processing configuration of claim 19, wherein the external system includes an end user, and the interface is a user interface that presents data in a locale-sensitive manner.

27. The multi-locale processing configuration of claim 19, wherein the normalized representation includes Universal System Format.

15. A multi-locale processing configuration for uniformly processing multi-locale information being sent to and received from a variety of subsystems, the processing configuration comprising:

a processing domain for running the variety of subsystems having a locale indicator;

at least one interface associated with each different subsystem, the interface being used to facilitate the handling of different formatting and data conventions between subsystems;

a mechanism for accessing locale-specific information based upon the locale indicator for each subsystem;

whereby the subsystems interact with each other based upon the locale-specific information, and whereby the code within the interface frees developers from needing certain detailed knowledge about any particular language.

19. A multi-locale processing configuration for performing normalization and de-normalization of data objects being used within a processing system, the configuration comprising:

a processing domain having a variety of information objects;

at least one integration interface for sending and receiving outgoing and incoming un-normalized information objects from an external system;

a normalization routine to normalize the incoming information objects to a normalized representation; and

a de-normalization routine for un-normalizing outgoing information objects from the normalized representation.