Abstract:
Described herein is a method for Global Data Type (GDT) ontology generation that involves parsing GDTs in order to define their basic components and building hierarchical structures for each GDT basic component. Each hierarchical structure is created by breaking down the corresponding GDT basic component into semantic elements and defining a relation between the elements, allowing easier navigation through the structure. New semantically compliant GDTs can be composed by combining already existing elements from the defined hierarchical structures. The GDT ontology eases GDT searching and simplifies the process of creating new GDTs.

Description:
FIELD OF THE INVENTION 
       [0001]    The field of invention relates generally to software, and particularly but not exclusively, relates to generation of hierarchical structures over a flat collection of data types. 
       BACKGROUND OF THE INVENTION 
       [0002]    A Global Data Type (GDT) represents a string comprising a concatenation of various elements having specific business semantics. The existing software products using GDTs usually have access to a plurality of already defined GDTs stored in a flat collection, and an option for the user to list the collection in order to find and use a specific GDT. Defining a new GDT involves a thorough analysis and approval of the new GDT proposal in order to verify semantic compliance with already existing GDTs, which makes GDT defining process time consuming and expensive. 
         [0003]    A new GDT structure is required in order to guarantee effective searching and easy addition of new GDTs. A semantic structure of GDTs enriched with additional relations between the GDT elements would provide means for navigation, thus simplifying GDT searching. In such an ontology, new GDTs can be defined with respect to already existing GDT elements, thus accelerating the approval process. 
       SUMMARY OF THE INVENTION 
       [0004]    Described herein is a method for Global Data Type (GDT) ontology generation that involves parsing GDTs in order to define their basic components and building hierarchical structures for each GDT basic component. Each hierarchical structure is created by breaking down the corresponding GDT basic component into semantic elements and defining a relation between the elements, allowing easier navigation through the structure. New semantically compliant GDTs can be composed by combining already existing elements from the defined hierarchical structures. The GDT ontology eases GDT searching and simplifies the process of creating new GDTs. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0005]    A better understanding of the present invention can be obtained from the following detailed description in conjunction with the following drawings, in which: 
           [0006]      FIG. 1  is an example of a Global Data Type (GDT) and its basic components, in accordance with an embodiment of the present invention. 
           [0007]      FIG. 2  is a flow diagram of a process generating a hierarchical structure from the Object Classes of a flat collection of GDTs, in accordance with an embodiment of the present invention. 
           [0008]      FIG. 3A  is an example of a flat collection of GDTs in accordance with an embodiment of the present invention. 
           [0009]      FIG. 3B  is an example of a GDT business ontology generated from the flat collection shown on  FIG. 3A , using the process described in reference to  FIG. 2  below, in accordance with an embodiment of the present invention. 
           [0010]      FIG. 3C  is an example of defining new ontology elements using the already existing elements and adding them to the ontology, in accordance with an embodiment of the present invention. 
           [0011]      FIG. 4  is a block diagram of a system for GDT ontology generation, in accordance with an embodiment of the present invention. 
       
    
    
     DETAILED DESCRIPTION 
       [0012]    Embodiments of a method and machine readable medium for Global Data Type (GDT) business ontology generation are described herein. In the following description, numerous specific details are set forth to provide a thorough understanding of embodiments of the invention. One skilled in the relevant art will recognize, however, that the invention can be practiced without one or more of the specific details, or with other methods, components, materials, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the invention. 
         [0013]    Reference throughout this specification to “one embodiment” or “this embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, the appearances of the phrases “in one embodiment” or “in this embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. 
         [0014]      FIG. 1  is an example of a Global Data Type (GDT) and its basic components. In this embodiment, the GDT comprises three basic components: Object Class, Property, and Representation. The Object Class represents the main business semantic of the GDT. It is a set of ideas, abstractions, or things in the real world that can be identified with explicit boundaries and meaning and whose properties and behavior follow the same rules. Object Classes are the things about which we wish to collect and store data. Examples of Object Classes are cars, persons, households, employees, orders, etc. The Property is a characteristic feature shared by all the instances of an Object Class. Properties are used to distinguish or describe objects. Examples of Properties are color, model, sex, age, income, address, price, etc. Object Classes and Properties may need to be described using multiple words, depending on the natural language in use. In this case, they are further classified as qualifiers and terms. The terms represent a basic concept, while the qualifiers help to define and render the concept unique. The Representation describes how the data is represented, i.e. the data type and its value range. In this embodiment, the Representation is based on core data types, for example, Code, Name, Description, ID, etc. 
         [0015]      FIG. 2  is a flow diagram of a process generating a hierarchical structure from the Object Classes of a flat collection of GDTs. At block  210 , all Object Classes terms and qualifiers are added as elements to the hierarchical structure. At block  220 , all concatenations of each Object Class term and each qualifier are added as elements to the hierarchical structure. At block  230 , Object Classes are defined as a super class for each one of their concatenations, thus defining a higher level of hierarchy. At block  240 , a check is performed for each element of the hierarchical structure if it is a concatenation of already existing hierarchical structure element and a new element that is not present in the hierarchical structure. If there is such an element, the existing element is split off the new element at block  250  and the new element is added to the hierarchical structure. The check at block  240  is repeated until there are no more new elements to add. At block  260 , for each element ‘X’ all elements ‘Y’ which are concatenations of the element ‘X’ and element ‘Z’ are located and the element ‘X’ is defined as a super class of all elements ‘Y’, thus defining new levels of hierarchy. The result is a hierarchy of elements by generalization of semantics. 
         [0016]    Following the process described above, similar hierarchical structures are generated for the other GDT basic components. In this embodiment, the process produces Web Ontology Language (OWL) ontology, adhering to the OWL Lite World Wide Web Consortium (W3C) recommendation. The ontology represents a Resource Description Framework (RDF) graph which can be even more efficiently processed than the pure description logic that has become a cornerstone of the W3C Semantic Web for its use in the design of ontologies. OWL Lite also allows modeling of relations, their ranges, and domains to define the detailed relations between Objects Classes, Properties, and Representations. In addition, OWL Lite allows relations for integrating the GDTs into the ontology. In this extended business ontology, the GDTs are leafs whose semantics derives from the combined semantics of the related Object Class, Property, and Representation. 
         [0017]      FIG. 3A  is an example of a flat collection of GDTs. A result of applying the process described above on this flat collection is the GDT business ontology shown on  FIG. 3B . The Object Classes of the GDTs from the flat list are: TransportationChargesPaymentArrangement, ProcurementArrangement, ProductProcurementArrangement, and SalesArrangement. At blocks  210  and  220  from  FIG. 2  described above, these Object Classes will be added to the Object Class hierarchical structure along with the Object Class term Arrangement. At block  230 , the element Arrangement will be defined as a super class of all elements and the element ProcurementArrangement will be defined as a super class for the element ProductProcurementArrangement. At blocks  240  and  250  from  FIG. 2  described above, the following new elements will be split off the existing elements and added to the hierarchical structure: ChargesPaymentArrangement and PaymentArrangement. At block  260 , ChargesPaymentArrangement will be defined as a super class of TransportationChargesPaymentArrangement, PaymentArrangement will be defined as a super class of ChargesPaymentArrangement and Arrangement will be defined as a super class of PaymentArrangement. 
         [0018]    The ontology from  FIG. 3B  allows new elements to be defined with respect to already existing more general elements.  FIG. 3C  is an example of defining new ontology elements using the already existing elements and adding them to the ontology. The new Class Objects are: ProductSalesArrangement, which is defined as a subclass of the existing Object Class SalesArrangement, MerchandiseandAssortmentProductProcurementArrangement, and MerchandiseandAssortmentPlanningProductProcurementArrangement, defined as subclasses of ProductProcurementArrangement. Each newly added Object Class appears as a leaf in the hierarchical structure which guarantees semantic compliance with the already existing GDTs. 
         [0019]      FIG. 4  is a block diagram of a system for GDT ontology generation. The Basic Component Identifier  420  parses the GDTs from the Flat Collection of GDTs  410  to identify GDT Object Class, Property, and Representation elements. Once basic components are identified, they are passed to the Hierarchical Structure Generator (HSG)  430 . Within the HSG  430 , the Object Class HSG  431  generates an Object Class hierarchical structure, the Property HSG  432  generates a Property hierarchical structure, and the Representation HSG  433  generates a Representation hierarchical structure. All hierarchical structures are generated following the process described in reference to  FIG. 2  above. HSG  430  further separates each GDT basic component into a term and a qualifier. All terms, qualifiers, and their concatenations are added as elements to the respective hierarchical structure. HSGs  431 ,  432 , and  433  further define relations between the elements and their concatenations to produce the RDF graph described in reference to  FIG. 3B  above. The Ontology Generator  440  generates GDT ontology from the hierarchical structures, generated by the HSG  430 . In this ontology, the GDTs are leafs whose semantics derives from the combined semantics of the related Object Class, Property, and Representation. 
         [0020]    The above description of illustrated embodiments of the invention, including what is described in the Abstract, is not intended to be exhaustive or to limit the invention to the precise forms disclosed. While specific embodiments of, and examples for the invention are described herein for illustrative purposes, various equivalent modifications are possible within the scope of the invention, as those skilled in the relevant art will recognize. 
         [0021]    These modifications can be made to the invention in light of the above detailed description. The terms used in the following claims should not be construed to limit the invention to the specific embodiments disclosed in the specification and the claims. Rather, the scope of the invention is to be determined entirely by the following claims, which are to be construed in accordance with established doctrines of claim interpretation.