Enterprise Interoperability Framework.

Abstract

Abstract. This paper aims at presenting an enterprise interoperability framework elaborated within the frame of INTEROP Network of Excellence *. The purpose of the framework is to identify the basic dimensions regarding to enterprise interoperability and to define its research domain as well as to identify and structure the knowledge of the domain. 1. Basic concepts and definitions Enterprises are not interoperable because there are barriers to interoperability. Barriers are incompatibilities of various kinds and at various enterprise levels. The incompatibilities obstruct the sharing of information and prevent from exchanging services. There exist common barriers to all enterprises whatever the sector of activities and size. Developing interoperability means to develop knowledge and solutions to remove the incompatibilities (Chen et al. 2005, 2006). The approach adopted is to: (i) define the domain of enterprise interoperability through the elaboration of an interoperability framework using barriers-driven approach; (ii) identify and structure the knowledge (solutions) of the domain using the framework. The interoperability framework proposed is elaborated on the basis of concepts developed in some existing frameworks and models (EIF, 2004), (ERISA, 2004), (IDEAS, 2002), (ATHENA, 2003), focusing on those concepts most relevant to define the research domain of enterprise interoperability. 1.1 Interoperability barriers Three categories of barriers (conceptual, technological and organisational) are identified as follows:- Conceptual barriers: They are concerned with the syntactic and semantic differences of information to be exchanged. These problems concern the modelling at the high level of abstraction (such as for example the enterprise models of a company) as well as the level of the programming (for example XML models). * This work is partly supported by the European Commission through DI (Domain of Interoperability)

Cite this work

No public copy is stored for this record, so only the metadata is cited.

Stored only when both papers are in the corpus — 65 citations exist upstream.

Papers that cite the same references — the relational fallback while embeddings are still backfilling.