Abstract: A framework for accomplishing vocabulary-based data transformations, for interfacing systems of disparate data formats. The framework is layered to separate the terms of documents form the underlying concepts corresponding thereto. The layers include an ontology layer for defining concepts, a vocabulary layer for labeling the concepts, a specification layer that specifies the concepts and labels, and a representation layer for encoding data in conformance with the specification layer. The separation enables the relationships between existing transformations to be automatically leveraged for minimizing user input for creating new transformations.

Abstract: An integrated modeling environment for creating integration models of computer architecture for executing business processes. The models include components having ports defining standard interfaces. The components can represent business process models for executing business processes. Connection information is stored in a repository so that binding of communication protocols can occur during deployment after creation of the model and can be looked up during runtime.

Abstract: A computer architecture for sharing information between plural applications having disparate data structures. An application integration platform includes logic for exchanging information between the plural applications. At least one common object definition specifies common objects to be used for exchanging data between the applications. The common object definition includes a canonical object defining elements of a standard object that are common between data structures of the applications. The comon object also includes at least one extension defining application specific or user specific elements. The canonical object is exposed to all of the applications through the application integration platform and the extensions are being exposed only to selected applications.

Abstract: A model driven environment for creating collaborative applications for executing collaborative business processes. Interrelated models are configured to define the application. A business process model defines steps and rules of the business process. A vocabulary model defines document flows corresponding to the business process. A service model exposes external events of the business process to other parties in the form of specifications. Trading partners can subscribe to the specifications to collaborate.

Abstract: A framework for accomplishing vocabulary-based data transformations, for interfacing systems of disparate data formats. The framework is layered to separate the terms of documents form the underlying concepts corresponding thereto. The layers include an ontology layer for defining concepts, a vocabulary layer for labeling the concepts, a specification layer that specifies the concepts and labels, and a representation layer for encoding data in conformance with the specification layer. The separation enables the relationships between existing transformations to be automatically leveraged for minimizing user input for creating new transformations.

Abstract: An integrated modeling environment for creating integration models of computer architecture for executing business processes. The models include components having ports defining standard interfaces. The components can represent business process models for executing business processes. Connection information is stored in a repository so that binding of communication protocols can occur during deployment after creation of the model and can be looked up during runtime.

Abstract: A communication interface for decoupling one software application from another software application such communications between applications are facilitated and applications may be developed in modularized fashion. The communication interface is comprised of two libraries of programs. One library manages self-describing forms which contain actual data to be exchanged as well as type information regarding data format and class definition that contain semantic information. Another library manages communications and includes a subject mapper to receive subscription requests regarding a particular subject and map them to particular communication disciplines and to particular services supplying this information. A number of communication disciplines also cooperate with the subject mapper or directly with client applications to manage communications with various other applications using the communication protocols used by those other applications.