INTEROP
Interoperability Research for Networked Enterprises Applications and Software
Network of Excellence - Contract no.: IST-508 011 interop-noe.org
Deliverable D10.1
INTEROPERABILITY GLOSSARY
Classification Project Responsible : Authors : Contributors Task Status : Date :
PU UPV Raul Poler Jose V. TomPaola Velardi 10.1 Final: Version 1B April 15th 2005
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
Table of contents
Executive Summary ................................................................................................................... 4 PART I ....................................................................................................................................... 5 I.1 Introduction....................................................................................................................... 5 I.1.1 Purpose of the Glossary ............................................................................................. 5 I.1.2 Coordination with other WPs..................................................................................... 6 I.2 Methods to produce the deliverable.................................................................................. 6 I.2.1 Methodology to obtain the Glossary.......................................................................... 6 I.3 Main Results ..................................................................................................................... 8 I.3.1 Glossary of terms and definitions .............................................................................. 8 I.4 Future work....................................................................................................................... 8 I.5 Conclusions..................................................................................................................... 10 PART II .................................................................................................................................... 11 II.1 Introduction ................................................................................................................... 11 II.2 Glossary Web Module ................................................................................................... 11 II.2.1 Introduction ............................................................................................................ 11 II.2.2 Glossary Web Module specifications ..................................................................... 12 II.2.3 Glossary tools analysis and selection ..................................................................... 15 II.2.4 Conclusion .............................................................................................................. 16 II.3 The OntoLearn ontology learning system ..................................................................... 17 II.3.1 Introduction ............................................................................................................ 17 II.3.2 Main steps of OntoLearn semi-automatic procedure ............................................. 18 II.3.3 Adapted OntoLearn procedure for INTEROP glossary acquisition....................... 23 Deliverable D10.1 2/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
II.3.4 Conclusion .............................................................................................................. 32 II.3.5 References .............................................................................................................. 32 II.4 INTEROP GLOSSARY ................................................................................................ 33
Deliverable D10.1
3/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
Executive Summary
The objective of this deliverable is to describe the process of creation of a Glossary in the interoperability domain. The procedures of obtaining of the Glossary are described. For the generation of the first version of the Glossary, the partners of WP10 have contributed providing documental sources to feed the procedure of semiautomatic extraction, which has been carried out by the University of Rome. Six reviewers (internal and external to the WP10) have contributed with their revision of terms and definitions. The Polytechnic University of Valencia (leader of the WP10) has defined the requirements for a glossary web environment tool and has carried out an analysis of the existent glossary tools. The final result has been 283 terms, each one of them with a definition selected as representative. The future work on the glossary will be carried out in a new WP where the relationships inter-WP will be kept in mind and the work area will be enlarged.
Deliverable D10.1
4/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
PART I
I.1 Introduction
"People can`t share knowledge if they do not speak a common language" (Davenport, 1998). Knowledge Management has been gaining significant importance within organisations and is considered an important success factor in enterprise operation. For some time, there have been many techniques to model processes and other elements of the enterprise in order to capture the explicit knowledge. Modelling in this context means creating an explicit representation, usually computable, for the purposes of understanding the basic mechanics involved. But knowledge can mean different things to different people and companies must spend some time looking for an appropriate mechanism to avoid misunderstanding in knowledge transmission. One mechanism to avoid this problem is to build a Glossary. The goal is to make accessible the organizational knowledge by unifying the language used in representing explicit knowledge. The semantic unification is a key factor for the success of the knowledge dissemination and diffusion through an organization.
I.1.1 Purpose of the Glossary
In a collaborative research project with a great number of researchers from different places in related although different research areas, the development of knowledge related to different areas that requires an interaction between researchers and the learning of the most unknown areas is an essential task. Also, to share knowledge in the area of interoperability will accelerate the advances in this domain. The INTEROP Joint Programme of Activities aims to:
integrate the knowledge in Ontology, Enterprise Modelling, and Architectures to give sustainable sense to interoperability, structure the European research community and influence organisations' programmes to achieve critical research mass, animate the community and spread industrially significant research knowledge outside the network.
Semantic unification is needed in order to facilitate the existing knowledge exchange within the Network of Excellence. The main objective is to provide a structured interoperability glossary along with the tools and methods to use this glossary within the scope of several Work-Packages in that already ascertained the need of a common set of interoperability keywords.
Deliverable D10.1
5/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
In general, a Glossary is a specialized vocabulary with corresponding annotations. The vocabulary includes terms that are unique to the subject, have special meaning in the field of interest. The annotations include descriptive comments and explanatory notes for the terms, such as definitions, synonyms, references, etc. A Glossary can be used when communicating information. In order to unify knowledge concerning Enterprise Modelling, Architecture & Platform and Ontologies, the INTEROP Glossary terms and definitions will be used consistently throughout the INTEROP documents. The objective is to extend the Glossary till nobody (researchers and PhD students) question the insertion of a new term.
I.1.2 Coordination with other WPs
During the first year of the INTEROP Project several Work-Packages ascertained the need of identifying a glossary of interoperability terms for a variety of tasks, e.g.: Building a knowledge map and classifying interoperability knowledge domains (WP1) Classifying partner's competences for the INTEROP mobility matrix (WP3) Providing a list of relevant domain concepts for educational objectives (WP10) More in general, indexing with a set of common meta-data the various deliverables, state of art, scientific papers and databases that are progressively made available on the INTEROP collaborative platform (WP2, WP4, WP7, WP8, WP9)
The glossary will be used as main information source to build an Ontology about Interoperability in cooperation with WP1 and WP3. The ontology will allow to: structure the knowledge all over the NoE facilitate the information retrieval Clustering on the collaborative platform
I.2 Methods to produce the deliverable
I.2.1 Methodology to obtain the Glossary
A general method for constructing a glossary is: collect a vocabulary, collect definitions, establish format rules, establish rules for writing definitions, examine definitions for multiple meanings, write basic definitions, review and compare for consistency of meaning, classify, select preferred words, group words, review and finalize the glossary. In practice, some of these steps are omitted, while other steps are developed to considerable depth, depending on the final objective of the glossary.
Deliverable D10.1
6/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
The complexity of detail for any phase of the glossary depends upon the scope of the glossary, the size of the vocabulary, and the number of persons participating in the project. This is understandable because a large working group reflecting a wide range of subjects, introduces more words for consideration and supplies multiple meanings relative to different backgrounds. Starting from a wide list of terms with the objective of building a whole glossary with inputs of several researchers could consume a great amount of time and effort. Therefore, a specific methodology was defined: a) to built an initial list of terms and definitions using a semiautomatic glossary acquisition and b) to complete the glossary by means of manual inputs and reviews.
I.2.1.1 Semi-automatic glossary acquisition
The first version of the INTEROP Glossary has been generated by means of a semi-automatic tool for ontology building called OntoLearn. This glossary is indeed a good starting point, but further developments are needed in order to provide an integrated set of terms that could be adequately used to: Building a knowledge map and classifying interoperability knowledge domains. Classifying partner's competences for the INTEROP mobility matrix. Providing a list of relevant domain concepts for educational objectives. More in general, indexing with a set of common meta-data the various deliverables, state of art, scientific papers and databases that are progressively made available on the INTEROP collaborative platform.
There are several benefits in creating a durable glossary facility: Semantic unification: the glossary represents an informal, but shared view of relevant interoperability concepts. This activity will let interoperability semantics emerge naturally from applications and collaborative work. Classification/ retrieval of INTEROP documents: glossary terms may be used as meta-data for indexing INTEROP documents and databases, to help manual and automatic retrieval and classification. Integration of competences from Enterprise Modelling, Ontology and Platform & Architectures, since both the creation and use of a commonly agreed set of "basic" meanings will facilitate the identification of common competences.
Therefore, the first version of the INTEROP Glossary must be addressed as a preliminary stage for the generation of the final glossary. The extension and the diffusion between the research community of the glossary are strictly required to meet the projected requirements.
I.2.1.2 Glossary extension and sharing through the GWM
Once completed the first list of terms and definitions using a semi-automatic glossary acquisition, the procedure selected to extend the glossary was the use of a Glossary Web Deliverable D10.1 7/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
Module (GWM). At the same time, this tool allows the sharing and utilization of the generated glossary. A methodology to implement the INTEROP GWM was defined: a) GWM requirements definition, b) existing Glossary Web based tools analysis, c) selection of the solution to be implemented. The GWM specification includes general, data, safety and GUI requirements. Although an analysis of existing glossary tools were performed, the requirement of integration in the INTEROP Collaborative Platform led to consider developing an ad hoc tool.
I.3 Main Results
I.3.1 Glossary of terms and definitions
The main results are: 1. The methodology for obtaining the first list of terms and definitions 2. The INTEROP Glossary
I.4 Future work
Due to the great importance of the Glossary, the inter-Work-Packages implications and the necessary extension to an Ontology, in the New Work Programme (Month 13 to 30) a new Work-Package will be proposed to continue the Glossary task. The general objective of the "Glossary-Ontology Service" work package (WPG in what follows) is to define and implement strategies to extend, exploit and allow a shared use of the glossary, eventually leading to an ontology. The following is a list of foreseen activities foreseen in year one of WPG. The foreseen tasks of this new WP are: Task 1.Glossary Extension Task 1.1. Define requirements
The acquisition of the glossary was initially foreseen only by WP10. The current version of the glossary therefore lacks of a clear view of the different needs and requirements emerging from the other WPs. A better understanding of the different requirements is therefore the first objective of WPG. The first activity foreseen in WPG will be collecting and describing the requirements from all WPs explicitly interested in the use of a glossary, namely, WP1, WP3 and WP 10, plus any other WP that might declare its interest.
Deliverable D10.1
8/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
Task 1.2.
Format and structuring
In its current version, the glossary is a "flat" list of terms and textual definitions. The source (URL or author name) of each definition is also provided. This flat structure may be inadequate for many tasks. For example, if documents/data are to be annotated with glossary terms, the annotator may find difficult and time-consuming the selection of one or more keywords from a large list. Furthermore, keyword-based search and classification has the same limitations than most search engines. A first activity can be that of structuring the terms in taxonomic order. Taxonomic structuring of keywords is a first step towards concept-based search. It is also necessary to conceive an effective way to show this structure to humans, for selection and annotation. Task 1.3. Define a procedure for extension and updating
We foresee that in INTEROP, while developing new activities and deepening our insights on enterprise interoperability issues, new concepts will emerge and new terms will be added to the glossary. In principle, all the INTEROP partners have the expertise to propose new definitions, but the methods for managing this collaborative activity must be clearly conceived to ensure consensus and consistency. In this sub-task the procedures and software tools for updating and extending the glossary will be defined. Task 2.Glossary Usages The glossary is per se an important achievement, since it will represent a partly structured representation of the semantics of an emergent field, enterprise interoperability. However, the glossary is a resource that may be useful for several INTEROP tasks, as mentioned in section 1. Some of these usages (e.g. classification of data in the knowledge map) are already foreseen, but need to be precisely specified and implemented. The purpose of this sub-task will be the specification of methods for exploiting the glossary in the work packages that already ascertained the need of a glossary. Task 3. Integration in the INTEROP platform Extending, accessing and using the glossary is a collaborative and shared activity, that needs to be supported through specific tools. This sub-task is concerned with the design and integration of glossary development, browsing and annotation tools within the INTEROP collaborative platform. This activity must be conducted in cooperation with WP 2. Task 4. Implementation of glossary-based applications in WP 1. WP3 and WP 10 New applications will be developed in WP1, WP3 and WP10 based on the glossary. This task will implement these applications. Task 5. Evaluation and assessment Finally, an evaluation will be carried out to check the consistency of the tasks developed. Deliverable D10.1 9/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
I.5 Conclusions
A first glossary of terms related with the interoperability domain has been obtained. An adaptation of a methodology of the University of Rome for the semiautomatic acquisition of terms and definitions starting from a source of documents related with the three domains of the project has been used. The requirements of a web tool to share and to permanently enlarge the glossary have been defined. An analysis of the existing glossary tools has been carried out. As conclusion an ad hoc tool will be developed. Due to the inter-Work-Packages implications and the necessary extension of the Glossary to an Ontology, a new Work-Package will be proposed to continue Glossary task in the New Work Programme (Month 13 to 30).
Deliverable D10.1
10/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
PART II
II.1 Introduction
Computer tools are widely used to give support to the process of building Ontologies and Glossaries. Focusing on glossaries, some tools are used to create glossaries by means of a set of documents used as raw materials. Other tools are used to give support to the processes of creation and diffusion of glossaries. The INTEROP Project requires the development of a new glossary on Interoperability for networked enterprises applications and software. In fact, the tasks to be performed are focussed on the creation, extension and spreading of a glossary. This glossary, following the project policies, should be supported by computer tools. Based on this and the expertise of INTEROP members, two main tools have been selected as the principal actors for the development of the INTEROP Glossary: The OntoLearn ontology learning system based on ontology building facilities aimed to provide the first version of the INTEROP Glossary. The Glossary Web Module to allow the extension and spreading of the INTEROP Glossary within the research community.
II.2 Glossary Web Module
II.2.1 Introduction
Extending, accessing and using the glossary are collaborative and sharing activities that need to be supported by specific tools. Furthermore, the spreading of the glossary requires tools that can have a wide access by the research community. Currently, web environments have proved to be a suitable solution to address interaction based applications between several actors in different locations. The main features of web environments are: Standard interfaces Ease of implementation Worldwide access Advanced interaction capabilities
These features provide the required functionality in order to allow a controlled and validated development of the future INTEROP Glossary. Deliverable D10.1 11/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
A methodology has been defined in order to facilitate the definition of the technical and operational specifications of the Glossary Module. Furthermore, this methodology is also aimed to select the software to support the INTEROP Glossary Web Module. The following figure represents the established methodology.
Define Glossary Web Module requirements
Analysis of existing Glossary Web based modules
Selection of the solution to be implemented Figure 1. Methodology to implement the INTEROP Glossary Web based Module
The stages of this methodology are: Stage 1. Define INTEROP Glossary Web Module requirements: A set of requirements will be defined related to the data and graphical user interface specifications. Stage 2. Analysis of existing Glossary Web based modules: Different existing Glossary tools will be analysed in order to check their functionalities and adaptation to the established requirements. Stage 3. Selection of the solution to be implemented: Based on the previous analysis, the software to support the INTEROP Glossary Web Module will be selected.
II.2.2 Glossary Web Module specifications
II.2.2.1 General specifications
The Glossary Web Module (GWM in what follows) developed within the INTEROP Project has the following features: The GWM is integrated within the ZOPE/CMF/PLONE platform specifically developed in the first half of 2004 by Aquitaine Valley for the INTEROP Project. Therefore, the GWM is required to be compatible with the standard PLONE approach for the content and user management. The GWM potentially interoperates with other applications developed in the platform. The GWM uses the PLONE workflow facilities to create specific stages for the creation of a term in the glossary. Deliverable D10.1 12/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
The GWM includes a glossary administration tool that is able to create several instances of the glossary object. Moreover, this administration tool allows to separately set up the main categories to group together the different terms. The GWM is aware of the way which the PLONE platform tackles the users, user groups and user roles. Therefore, different users have different access levels to the application. The GWM takes profit of the benefits of the mutual existence of a glossary and a set of resources (documents, papers, etc.) in the same Portal. For example, to link glossary definitions with words contained in any document of the platform or to provide crossreferences when a term is used in the description of another term.
II.2.2.2 Data specifications
INTEROP Glossary is made up of a group of terms related to interoperability, initially produced by a semi-automatic procedure for ontology building and later extended by the insertion of new terms by the INTEROP partners. The Glossary is available for any person that accesses the Web Portal. Glossary Module is integrated in the INTEROP Collaborative Platform in order to take profit of the available resources. Also, the glossary is initially available only in English. Further developments may include the creation of specific glossaries in different languages, specially produced for their spreading in SMEs. A glossary is made up of a group of terms. A term is comprised of a set of fields. These fields are aimed at defining, classifying and marking the term. Furthermore, one term may have different accepted definitions and belong to more than one category. The fields for each term are: Term (type: text): describes the name of the term. Category (type: text): describes the category or categories where the term may be included. For example: Enterprise modelling, Ontologies, Architectures, etc. They must be able to be set up for each glossary. Definition (type: text): includes the definition of the term. Author (type: text): author of the definition. It is a free field. May not coincide with a registered user of the portal. InsertionDate (type: date): date when the term was inserted in the glossary. RevisionDate (type: date): date when the term was revised within the glossary. PartnerOwner (type: text): INTEROP partner who inserted the term in the system. Score (type: integer): stores the score marked by the reviewer. Limited from 0 to 10.
Each term also includes three new fields related to its revision and validation The fields are: SendToRev (type: checkbox): indicates if the terms has been sent to revision. Revised (type: checkbox): indicates if the term has been revised. Validated (type: checkbox): indicates if the term has been validated and therefore published in the public section. Deliverable D10.1 13/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
II.2.2.3 Graphical User Interface specifications
INTEROP Glossary Graphical User Interface (IG-GUI in what follows) has been developed and integrated following the requirements and structure of the INTEROP Collaborative platform based on PLONE. The Web interface is made up of a public and a private section aimed at the management and visualization of the Glossary: Public section: The Web interface for the public area is able to alphabetically list the terms of the glossary, classified according to the group: Enterprise Modelling, Architecture, Platform and Ontologies, etc. Any person that accesses the Portal is able to use and visualize the Glossary, included external users. For example, in the next URL: http://www.thecorporatelibrary.com/study/glossary.asp can be seen an example of a typical glossary on the Web. Private section: the terms are inserted by the partners in this section. The term evaluation and validation are made here too. That is, each partner introduces new terms into the Glossary, which once introduced will be sent to other partners for their review. This task will be accomplished by the partner in charge of the management and administration of the glossary. Finally, each partner in charge of the revision (reviewer) will enter the Web to confirm the revision or to modify the terms. Therefore, this section will be divided in 3 well differentiated parts: o Terms insertion: Each partner of the project is invited to introduce a number of terms into the Glossary. o Terms revision: is made up of two sections: Sending terms: Each term is assigned to an INTEROP member as reviewer. Therefore, a list with all the terms with the field SendToRev set to False will appear. The GWM administrator is in charge to send to the other partners of the Project the terms to be revised. Once the email is sent, SendToRev field will be set to True for all the terms that have been sent. Those records will disappear from the "Sending Terms Section". Revising terms: shows a list of the terms with the field SendToRev set to True and the field Revised set to False. The partner, after making the review of the assigned terms, will enter this section to validate or change the term or terms. Now, the Revised field of the record will be set to True and then, the record will disappear from the list. o Terms Validation: This section shows the same appearance and functionality than "Revising terms Section", but only showing the records with the Revised field set to True and Validated set to False. The user of this section only is the GWM administrator. The working method is similar as mentioned above. The validated records are selected and then validated by the Administrator. The Validated field of each selected record will be set to True. At this moment, the validated record or records will disappear from the list and will appear in the public Glossary (because the public Glossary only shows the records with the Validated field set to True). Deliverable D10.1 14/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
The structure and level access for the GWM will be as follows:
Public section (public access) Private section o Terms insertion (only INTEROP partners) o Terms revision Sending terms (only glossary's administrator) Revising terms (only INTEROP partners) o Terms validation (only glossary's administrator)
The user roles of the GWM will be: Host (Non identified user): He is allowed to access and consult the glossary. Member (Identified user of the INTEROP Portal): He is allowed to consult the glossary. He can access the private area to check the status of each term related to the workflow. He is able to insert a new term. Reviewer: He is allowed to revise a term and to assign a score to it. Supervisor: He is allowed to validate a term and therefore to publish it. He can change the status of any term or remove it from the glossary.
Finally, a summary of the GWM operative functionalities is detailed: A Term insertion/management o Term insertion o Term elimination o Term modification o Term revision o Term publication B Term consultation o Alphabetic list of terms (general and by letter) o Alphabetic list of terms by category o Search engine facility C Management functionalities o Glossary creation o Glossary elimination o Category insertion o Category elimination
II.2.3 Glossary tools analysis and selection
Based on the general specifications stated above, the Glossary module must be integrated within the PLONE platform in order to take profit of the benefits of the mutual existence of a glossary and a set of resources (documents, papers, etc.). For example, to link glossary Deliverable D10.1 15/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
definitions with words contained in any document of the platform or to provide crossreferences when a term is used in the description of another term. In order to integrate the Glossary module in the PLONE platform, a strict requirement must be defined. The Glossary Web module must be developed following the programming requirements established in the PLONE platform, that is, the same programming environment and language. A search of glossary tools in the market has been performed. The results are stated below: There exist some glossary building tools (i.e. Babylon Builder) and some OpenSource e-learning platforms (i.e. Moodle) that provide glossary facilities, but none of them are integrated in PLONE. These solutions are discarded as stated above. There does not exist any commercial software based on PLONE to support the building of a glossary.
This fact leads to consider the possibility to develop by an external company an ad hoc software on PLONE to support the Glossary extension and spreading. An Italian company has been asked for an estimate for the development of the glossary module based on the defined specifications. This estimate has been analysed and in principle seems to match all the requirements.
II.2.4 Conclusion
New technologies represent a great advance in the development of glossaries. In our case, the GWM represents a way to interactively extend a set of terms on interoperability between a distributed researchers community. The solution to be adopted is based on an ad hoc implementation. These tools have the benefit of fully matching the requirements but the cost is higher than a commercial tool. The INTEROP project has at its disposal limited funds to acquire software applications. In many cases, European projects spend these funds in the main collaborative platform, but in our case the need of a Glossary management tool and its implications have the maximum priority of the Governing Committee.
Deliverable D10.1
16/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
II.3 The OntoLearn ontology learning system
II.3.1 Introduction
INTEROP is a Network of Excellence whose primary goal is to sustain European research on interoperability for enterprise applications and software. The originality of the project lies in the multidisciplinary approach merging different research areas which support the development of interoperable systems: architectures and platforms, enterprise modelling, and ontology. One of the most common goals of ontologies is sharing a common understanding of the structure of information among people or software agents (Musen 1992; Gruber 1993). For example, suppose several different web sites contain tourism information or provide tourism e-commerce services. If these sites share and publish the same ontology of the terms they all use, or, more realistically, they have different ontologies but provide mappings to a common upper level ontology, then computer agents can extract and aggregate information from these different resources. The agents can use this semantic information to answer user queries or as input data to other applications (Noy and Mc Guiness, 2001), e.g. automatic reservation services or trip planners. A useful and commonly adopted initial step in ontology building is to obtain a list of relevant domain terms and term definitions, i.e. a glossary. Often, natural language definitions introduce, first, the class an object belongs to (the genus) and then, the properties that characterize that object (the differentia) with respect to its class. Consider for example the first sentence of our abstract: "Enterprise Interoperability is the ability of different organizations to work together and exchange documents, data, services, best practices, etc.". Here, ability is the genus, or hyperonym (enterprise interoperability is a kind of ability, the capacity to do something) and the description of this ability, i.e. the rest of the sentence, is the differentia. Notice furthermore that we said that ability is a capacity, and therefore the definition suggests a hierarchical chain: enterprise_interoperability ability capacity In subsequent steps of the ontology building process, this hierarchy of terms can be used to populate the lower levels of a software artefact, the ontology, in which terms are replaced by concepts and informal descriptions by formal specifications expressed in some knowledge representation language, e.g. OWL, a W3C1 ontology language standard. In line with this strategy, during the first months of the INTEROP project it was decided to develop a hierarchically structured glossary of interoperability terms. The glossary is meant to provide common meta-data to annotate structured (databases) and unstructured (papers and deliverables) data produced by project work-packages dealing with the INTEROP knowledge map, researchers mobility, educational objectives, and state of the art. These data are
1
http://www.w3.org/TR/2003/CR-owl-features-20030818/
Deliverable D10.1
17/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
progressively made available on the INTEROP collaborative workspace2. The glossary will eventually evolve towards an ontology in a later stage of the project. To speed up the glossary definition, the Department of Computer Science of the University of Roma made available a battery of ontology building algorithms and tools, the OntoLearn system (Navigli and Velardi, 2004) (Navigli et al., 2003). The OntoLearn system builds a domain ontology relating domain terms to the concepts and conceptual relations of the WordNet3 lexicalised ontology. The final ontology is therefore an extended and trimmed version of WordNet. In OntoLearn, WordNet acts as a "general purpose" upper ontology, but other more specialised upper ontologies can be used, if available. Since the use of WordNet as a reference ontology is not a current choice of the INTEROP project, and since for the glossary acquisition task some additional feature was foreseen, we conceived a partly new experiment, using some of the tools and algorithms provided by the OntoLearn system, and some new feature that we developed for the purpose of the task at hand. The following chapters describe the steps and the results of this experiment, that led to the acquisition of a hierarchically structured glossary of about 380 interoperability terms, subsequently evaluated by a team of 6 domain experts selected from INTEROP partners.
II.3.2 Main steps of OntoLearn semi-automatic procedure
on-line corpora, documents, glossaries
Term Extraction
no glosses
E x t r act io n of Natural L an guage Definitions
partial glosses
Hu man Specialists In p u t
full glosses
Co mp o s it io n al In t erp ret at io n (SSI)
Glo s s Pars in g
fores t of domain trees
On t o lo g y M ap p in g
c ore ontology domain ontology
Figure 2. An outline of the ontology learning phases in the OntoLearn system.
2 3
http://interop.aquitaine-valley.fr http://www.cogsci.princeton.edu/~wn/
Deliverable D10.1
18/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
Figure 2 provides a snapshot of the OntoLearn ontology learning methodology. The following steps are performed by the system4: 1. Extract pertinent domain terminology Simple and multi-word expressions are automatically extracted from domain-related corpora, like enterprise interoperability (e.g. collaborative work), hotel descriptions (e.g. room reservation), computer network (e.g. packet switching network), art techniques (e.g. chiaroscuro). Statistical and natural language processing (NLP) tools are used for automatic extraction of terms (Navigli and Velardi, 2004). Statistical techniques are specifically aimed at simulating human consensus in accepting new domain terms. Only terms uniquely and consistently found in domain-related documents, and not found in other domains used for contrast, are selected as candidates for the domain terminology. 2. Search on the web for available natural language definitions from glossaries or documents Available natural language definitions are searched on the web using on-line glossaries or extracting definitory sentences in available documents. A context free (CF) grammar is used to extract definitory sentences. An excerpt is: S PP `,' NP SEP NP N1 KIND1 KIND1 MOD1 NOUN1 MOD1 Verb | Adj | Verb `,' MOD1 | Adj `,' MOD1 NOUN1 Noun N1 Art | Adj SEP `,' | `.' | Prep | Verb | Wh PP Prep NP In this example, S, NP and PP stand for sentence, noun phrase and prepositional phrase, respectively. KIND1 captures the portion of the sentence that identifies the kind, or genus, information in the definition. This grammar fragment identifies (and analyses) definitory sentences like e.g.: "[In a programming language]PP , [an aggregate]NP [that consists of data objects with identical attributes, each of which may be uniquely referenced by subscription]SEP", which is a definition of array in a computer network domain. The grammar is tuned for high precision, low recall. In fact, certain expressions (e.g. X is an Y) are overly general and produce mostly noise when used for sentence extraction.
Limited details on the algorithms are provided here, for obvious sake of space. The interested reader can access the referred OntoLearn bibliography.
4
Deliverable D10.1
19/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
3. IF definitions are found: 3.1. Filter out non relevant definitions Multiple definitions may be found on the internet, some of which may be not pertinent to the selected domain (e.g. in the interoperability domain federation as "the forming of a nation" rather than "a common object model, and supporting Runtime Infrastructure."). A similaritybased filtering algorithm is used to prune out "noisy" definitions, with reference to a domain. Furthermore, an extension of the CF grammar of step 2 is used to select5, when possible, "well formed" definitions. For example, definitions with genus(kind-of) and differentia (modifier), like the array example in step 2, are preferred to definitions by example, like: Bon a Tirer "When the artist is satisfied with the graphic from the finished plate, he works with his printer to pull one perfect graphic and it is marked "Bon a Tirer," meaning "good to pull". These definitions can be pruned out since they usually do not match any of the CF grammar rules. 3.2. Parse definitions to extract kind-of information The CF grammar of step 3.1 is again used to extract kind-of relations from natural language definitions. For example, in the array example reported in step 2, the same grammar rule can be used to extract the information (corresponding to the KIND1 segment in the grammar excerpt):
kind - of array aggregate
4. ELSE IF definitions are not found 4.1. IF definitions are available for term components (e.g. no definition is found for the compound integration strategy but integration and strategy have individual definitions) 4.1.1. Solve ambiguity problems In technical domains, specific unambiguous definitions are available for the component terms, e.g.: strategy: "a series of planned and sequenced tasks to achieve a goal" and integration: "the ability of applications to share information or to process independently by requesting services and satisfying service requests" (interoperability domain). In other domains, like tourism, definitions of component terms are often extracted from general purpose dictionaries (e.g. for housing list, no definitions for list are found in tourism glossaries, and in generic glossaries the word list is highly ambiguous). In these cases, a word sense disambiguation algorithm, called SSI6 (Navigli and Velardi, 2004 and 2004b), is used to select the appropriate meaning for the component terms.
5
The grammar used for analysing definitions is a superset of the grammar used to extract definitions from texts. The analysed sentences are extracted both from texts and glossaries, therefore expressions like X is an Y must now be considered. 6 The SSI algorithm (Structural Semantic Interconnections) is one of the novel and peculiar aspects of the OntoLearn system. SSI recently participated to an international challenge, Senseval-3, obtaining the second best score (very close to the first) in a word sense disambiguation task.
Deliverable D10.1
20/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
4.1.2. Create definition compositionally Once the appropriate meaning components have been identified for a multi-word expression, a generative grammar is used to create definitions. The grammar is based on the presumption (not always verified, see (Navigli et al, 2004) for a discussion) that the meaning of a multiword expression can be generated compositionally from its parts. According to this compositional view, the syntactic head of a multi-word expression represents the genus (kindof), and the other words the differentia (modifier). For example, integration strategy is a strategy for integration. Generating a definition implies, first, to identify the conceptual relations that hold between the complex term components7, and then, to compose a definition using segments of the components' definitions. For example, given the term integration strategy, the selected underlying conceptual relation is purpose:
pur ose strategy p int egration
and the grammar rule for generating a definition in this case is: (1)
:: = a kind of
,
, for
,
where: MWE is the complex term H is the syntactic head HDEF is the main sentence of the selected definition for H M is the modifier of the complex term MDEF is the main sentence of the selected definition for M
For example, given the previous definitions for strategy and integration, the following definition is generated by the rule (1): integration strategy: a kind of strategy, a series of planned and sequenced tasks to achieve a goal, for integration, the ability of applications to share information or to process independently by requesting services and satisfying service requests. As better discussed in (Navigli et al., 2004) this definition is quite verbose, but has the advantage of showing explicitly the sense choices operated by the sense disambiguation algorithm. A human supervisor can easily verify sense choices and reformulate the definition in a more compact way.
7
Machine learning techniques are used to assign appropriate conceptual relations, see referenced papers for details.
Deliverable D10.1
21/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
4.2. ELSE ask expert If it is impossible to find even partial definitions for a multi-word expression, the term is submitted to human specialists, who are in charge of producing an appropriate and agreed definition. 5. Arrange terms in hierarchical trees Terms are arranged in forests of trees, according to the information extracted in steps 3.2 and 4.1.1. Figure 3 shows examples from a computer domain. 6. Link sub-hierarchies to the concepts of a Core Ontology. The semantic disambiguation algorithm SSI (mentioned in step 4.1.1) is used to append subtrees under the appropriate node of a Core Ontology. In our work, we use a general purpose wide-coverage ontology, WordNet. This is motivated by the fact that sufficiently rich domain ontologies are currently available only in few domains (e.g. medicine). With reference to Figure 3, the root artificial language has a monosemous correspondent in WordNet, but temporary or permanent termination has no direct correspondent. The node is then linked to termination, but first, a disambiguation problem must be solved, since termination in WordNet has two senses: "end of a time span", and "expiration of a contract", therefore disambiguation is necessary.
artificial_language programming_language, c omputer_language failure temporary_or_ permanent_termination
algorithmic _language
c obol
pl/i
low -level_language, c omputer-oriented_language
dropout#2 dis engagement_failure
bloc king#2
bloc k_trans fer_failure
as s embly_language, c omputer-dependent_language
Figure 3. Examples of taxonomic trees of terms (computer domain).
7. Provide output to domain specialists for evaluation and refinement. The outcome of the ontology learning process is then submitted to experts for corrections, extensions, and refinement. In the current version of OntoLearn, the output of the system is a taxonomy, not an ontology, since the only information provided is the kind-of relation. However, extensions are in progress, aimed at extracting other types of relations from definitions and on-line lexical resources.
Deliverable D10.1
22/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
II.3.3 Adapted OntoLearn procedure for INTEROP glossary acquisition
II.3.3.1 The INTEROP experiment
For the purpose of the INTEROP glossary acquisition task, step 6 above has been omitted, since an interoperability Core Ontology was not available, and the adoption of an available reference ontology (like WordNet) is not agreed in the project. The preliminary objective in this phase of INTEROP was to obtain a sort of partially structured glossary, rather than an ontology, i.e. a forest of term trees, where, for each term, the following information has to be provided: definition of the term, source of the definition (domain specialist or web site), kind-of relation, e.g.: interoperability: The ability of information systems to operate in conjunction with each other encompassing communication protocols, hardware software, application, and data compatibility layers. source: www.ichnet.org/glossary.htm kind-of: ability Step 1: Term extraction The first step of the INTEROP glossary procedure was to derive an initial list of terms using the evidence provided by interoperability-related documents. The INTEROP collaborative workspace was used to collect from all partners the relevant documents, among which, the proceedings of INTEROP workshops and deliverables, highly referenced scientific papers, partners' papers, tutorials, etc. The OntoLearn TermExtractor module (Navigli and Velardi, 2004) extracted from these documents 517 terms. A generic computer science glossary was used to remove overly general technical terms (e.g. computer network), and the list was then quickly reviewed manually to delete clearly identifiable spurious terms. The final list included 376 terms. Step 2: Generation of definitions Given the list of terms, we activated step 2 of the automatic glossary acquisition procedure. During this step, 28 definitions were not found, 22 were generated compositionally, and the remaining terms were extracted either from glossaries or from available documents. For each definition, we kept track of the source (URL of the web page). For some term, more than one definition survived the well-formedness and domain similarity criteria (step 3.1 of section 2), therefore the total number of definitions submitted to the experts for revision was 358.
Deliverable D10.1
23/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
Step 3: Evaluation by experts Six domain experts8 in INTEROP were asked to review and refine the glossary. Each expert could review (rev), reject (rej), accept (ok) or ignore (blank) a definition, acting on a shared database. The experts added new definitions for brand-new terms, but they also added new definitions for terms that may have more than one sense in the domain. There have been a total of 67 added definitions, 33 substantial reviews, and 26 small reviews (only few words changed or added). Some term (especially the more generic ones, e.g. business domain, agent, data model) was reviewed by more than one expert who proposed different judgements (e.g. ok and rev) or different revised definitions. In order to harmonise the results, a first pass was conducted automatically, according to the following strategy: If a judgement is shared by the majority of voters, then select that judgement and ignore the others (e.g. if a definition receives two ok and one rev, then, ignore rev and accept the definition as it is). If the only judgement is rej(ect), then delete the definition If a definition has a rej and one (or more) reviewed versions, then, ignore the reject and keep the reviews. This step led to a final glossary including 425 definitions, 23 of which with a surviving ambiguity that could not be automatically conciliated. Therefore a second, short manual pass was necessary, involving this time only three reviewers. After resolving ambiguity, one definition (the most representative) per term was selected. Final glossary has 283 terms and definitions (see II.4 INTEROP GLOSSARY). Step 4: Speed-up factors The objective of the procedure describe in section 2 is to speed-up the task of building a glossary by a team of experts. Evaluating whether this objective has been met is difficult, since no studies are available for a comparison. We consulted several sources, finally obtaining the opinion of a very experienced professional lexicographer9 who has worked for many important publishers. He outlined a three-steps procedure for glossary acquisition including: i) internet search of terms, ii) production of definitions, and iii) harmonization of definitions style. He evaluated the average time spent in each step in terms of 6 minutes, 10 min. and 6 min. per definition, respectively. He also pointed out that conducting this process with a team of experts could be rather risky in terms of time10, however he admits that in very new fields the support of experts could be necessary.
The experts have been chosen according to their expertise in the three INTEROP domains: ontology, architecture and enterprise modelling, but also to include representatives or leaders of the project work-packages that will actually use the glossary. 9 We thank Orin Hargraves for his very valuable comments. 10 To cite his words: "no commercial publisher would subject definitions to a committee for fear of never seeing them in recognizable form again"
8
Deliverable D10.1
24/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
Though the comparison is not fully possible, the procedure described in this paper has three phases in which man-power is requested: After term extraction (step 1), to prune non-terminological and non-domain relevant strings. This requires 0.5 minutes per term. After the extraction of definitions (step 2), to evaluate and refine definitions. We asked each expert to declare the time spent on this task, and we came out with an average of 4 minutes per definition. Since some definition was examined by more than one expert, this amount must be increased to 6 min. approximately. In a second-pass review, to agree on the conflicting judgements. This depends on the number of conflicts, that in our case was less than 10%, mostly solved automatically (section 3.3). Overestimating, we may still add 1 minute per definition. The total time is then 7.5 minutes per definition, against the 16 declared by the lexicographer for steps 1 and 2 of his procedure. In this comparison we exclude the stylistic harmonisation (step 3 of the lexicographer), which is indeed necessary to obtain a good quality glossary, but has not been conducted in the case of the INTEROP experiments. However, since this phase would be necessarily manual in both cases, it does not influence the computation of the speed-up factor. The above evaluation is admittedly very questionable, because on one side we have an experienced lexicographer, on the other side we have a team of people that are certainly experts of a very specific domain, but have no lexicographic skills. Our intention here was only to provide a very rough estimate of the manpower involved, given that no better data are available in literature. Apparently, a significant speed-up is indeed obtained by our procedure.
II.3.3.2 Generation of domain sub-trees
As remarked in the introduction, the glossary terms must have some kind of hierarchical ordering, leading eventually to a formal ontology. A hierarchical structure simplifies the task of document annotation, and is a basis for further developments such as automatic clustering of data (e.g. for document classification), identification of similarities (e.g. for researchers mobility), etc. In other words, it is a first step towards semantic annotation. To arrange terms in term trees, we used the procedure described in steps 3.2 and 4.1.1 of section Erreur ! Source du renvoi introuvable.. The definitions have been parsed and the word, or complex term, representing the hyperonym (genus) has been identified. Given the limited number of definitions, we verified this task manually, obtaining a figure of 91.76% precision, in line with previous evaluations that we did on other domains (computer networks, tourism, economy). Contrary to the standard OntoLearn algorithm, we did not attached subtrees to WordNet, as motivated in previous sections. Overall, the definitions were grouped in 125 sub-trees, of which 39 including only 2 nodes, 43 with 3 nodes, and the other with >3 nodes. Examples of two term trees are shown in figure 4. Deliverable D10.1 25/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
c omponent
interac ting c omponent s ys tem artific ial intelligenc e s ys tem c omputer-bas ed s ys tem
applic ation c omponent
c omputer s ys tem
c ommunic ation s ys tem
netw ork know ledge bas e, KB bus ines s applic ation agent expert s ys tem enterpris e-w ide open systems netw ork netw ork
capability
s oftw are c apability s oftw are requirement
func tionality
bus ines s c apability
c ompetenc y
c onc eptual func tionality s ervic e
bus ines s s ervic e bus ines s objec t fac ility (BOF) s ec urity service b2b connectivity
Figure 4. Sub-trees extracted from the Interoperability domain.
In figure 4 (tree on top), the collocation of the term system might seem inappropriate, since this term has a very generic meaning. However, the definition of system in the interoperability glossary is quite specific: "a set of interacting components for achieving common objectives", which justifies its collocation in the tree. A similar consideration applies to service in the bottom tree. An interesting paper (Ide and Vnis, 1993) provides an analysis of typical problems found when attempting to extract (manually or automatically) hyperonymy relations from natural language definitions, e.g. attachments too high in the hierarchy, unclear choices for more general terms, or-conjoined heads, absence of hyperonym, circularity, etc. These problems are more or less evident especially over-generality when analysing the term trees forest extracted from the glossary. However, our purpose here is not to overcome problems that are inherent with the task of building a domain concept hierarchy: rather, we wish to automatically extract, with high precision, hyperonymy relations embedded in glossary definitions, just as they are: possibly over-general, circular, or-conjoined. The target is, again, to speed up the task of ontology building and population, extracting and formalizing domain knowledge expressed by human specialists in an unstructured way. Discrepancies and inconsistencies can be corrected later by the human specialists, who will verify and rearrange the nodes of the forest. The study of automatic methods to rearrange trees and reduce these discrepancies is one of our on-going research streams. Deliverable D10.1 26/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
II.3.3.3 Documents used
The following list summarizes the documents used to perform the first step of the methodology: the term extraction.
Document number
1
Document title
The DaQuinCIS Broker: Querying Data and Their Quality in Cooperative Information Systems An E-service-Based Framework for Inter-administration Cooperation Managing Data Quality in Cooperative Information Systems
Authors
Massimo Mecella, Monica Scannapieco, Antonino Virgillito, Roberto Baldoni, Tiziana Catarci and Carlo Batini Mariangela Contenti, Alessandro Termini, Massimo Mecella and Roberto Baldoni Massimo Mecella, Monica Scannapieco, Antonino Virgillito, Roberto Baldoni, Tiziana Catarci and Carlo Batini Luca De Santis, Diego Milano, Gabriele Palmieri, Monica Scannapieco and Tiziana Catarci Arne-J Berre Daniela Berardi, Diego Calvanese, Giuseppe De Giacomo, Maurizio Lenzerini and Massimo Mecella Daniela Berardi, Diego Calvanese, Giuseppe De Giacomo and Massimo Mecella Daniela Berardi, Diego Calvanese, Giuseppe De Giacomo, Maurizio Lenzerini, and Massimo Mecella Daniela Berardi, Diego Calvanese, Giuseppe De Giacomo, Maurizio Lenzerini, and Massimo Mecella D. Berardi, D. Calvanese, G. De Giacomo, M. Lenzerini and M. Mecella Daniela Berardi, Diego Calvanese, Giuseppe De Giacomo, Maurizio Lenzerini, and Massimo Mecella Daniela Berardi, Diego Calvanese, Giuseppe De Giacomo, Maurizio Lenzerini, and Massimo Mecella Luca De Santis, Monica Scannapieco and Tiziana Catarci Andrea CalDiego Calvanese, Giuseppe De Giacomo and Maurizio Lenzerini Andrea CalDiego Calvanese, Giuseppe De Giacomo and Maurizio Lenzerini Andrea CalDiego Calvanese, Giuseppe De Giacomo and Maurizio Lenzerini Andrea CalDiego Calvanese, Giuseppe De Giacomo and Maurizio Lenzerini Andrea Calnd Diego Calvanese Andrea CalDiego Calvanese, Giuseppe De Giacomo, Maurizio Lenzerini, Paolo Naggar and Fabio Vernacotola
Domain
Architectures
2 3
Architectures Architectures
4 5 6
Data Quality Improvement in the DaQuinCIS System The Principles and Evolution of Architecture & Platforms Synthesis of Underspecified Composite e-Services based on Automated Reasoning Reasoning about Actions for e-Service Composition e-Service Composition by Description Logics Based Reasoning Automatic Composition of e-Services that Export their Behaviour
Architectures Architectures Architectures
7 8
Architectures Architectures
9
Architectures
10 11
Synthesis of Composite e-Services based on Automated Reasoning A Foundational Framework for e-Services
Architectures Architectures
12
Automatic Composition of e-Services
Architectures
13 14 15 16 17 18 19
Trusting Data Quality in Cooperative Information Systems On the Expressive Power of Data Integration Systems On the Role of Integrity Constraints in Data Integration Data Integration under Integrity Constraints Accessing Data Integration Systems through Conceptual Schemas Optimized Querying of Integrated Data over the Web BIS: Data Integration at Work
Architectures Architectures Architectures Architectures Architectures Architectures Architectures
Deliverable D10.1
27/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
20
Semantic Data Integration in P2P Systems
21
Hyper: A Framework for Peer-to-Peer Data Integration on Grids
22
What to Ask to a Peer: Ontology-based Query Reformulation
23 24
DAQUINCIS. DL1.B: Description of the General Reference Scenario Cooperative Processes and Information Quality Control: the SICS Case Study DaQuinCIS. DL4.A: Design and Definition of the Cooperative Architecture Supporting Data Quality
Diego Calvanese, Elio Damaggio, Giuseppe De Giacomo, Maurizio Lenzerini and Riccardo Rosati Diego Calvanese, Giuseppe De Giacomo, Maurizio Lenzerini, Riccardo Rosati and Guido Vetere Diego Calvanese, Giuseppe De Giacomo, Domenico Lembo, Maurizio Lenzerini and Riccardo Rosati Carlo Batini and Paolo Missier Roberto Baldoni, Cinzia Cappiello, Chiara Francalanci, Barbara Pernici, Pierluigi Plebani, Monica Scannapieco, Sara Tucci Piergiovanni and Antonino Virgillito Cinzia Cappiello, Chiara Francalanci and Barbara Pernici Diego Milano, Gabrieli Oalmieri, Monica Scannapieco and Antonino Virgillito Paolo Missier and Carlo Batini
Architectures
Architectures
Architectures
Architectures Architectures
25 26 27
DaQuinCIS. Process-based methods for improving data-quality DaQuinCIS Arquitecture DaQuinCIS. A General Framework and Case Study for Information Quality Management in Cooperative Information Systems Enhancing Application Interoperability and Enabling B2B Transactions over the Internet for Small and Medium Enterprises: The PRAXIS Project Moda-ML: Building a collaborative sectoral framework based on ebXML Virtual Engineering Team for the Industrial Engineering
Architectures Architectures Architectures
28 29 30
Yannis Charalabidis and Stelios Pantelopoulos Nicola Gessa, Piero De Sabbata, Massimo Marzocchi and Fabio Vitali N.Perry, A.Bernard, A.Candlot, S.A.Khodja, Y.Keraron, M. Shahrokhi, M.Pouliquen and M.Mauchand FG Intelligent Distributed Systems Marco Bertoletti, Paolo Missier, Monica Scannapieco, Pietro Aimetti and Carlo Batini Monica Scannapieco, Valeria Mirabella, Massimo Mecella and Carlo Batini Diego Milano, Monica Scannapieco and Tiziana Catarci Diego Milano, Monica Scannapieco and Tiziana Catarci Barbara Pernici and Monica Scannapieco Luca De Santis, Diego Milano, Gabriele Palmieri, Monica Scannapieco and Tiziana Catarci EXTERNAL Project (Editor: John Krogstie) Christian Huemer Popkin Software Enrico Franconi
Architectures Architectures Architectures
31 32 33 34 35 36 37 38 39 40 41
Introduction to iVS - Intelligent Distributed Systems The Service to Businesses Project: Improving Government-to-Business Relationships in Italy Data Quality in e-Business Applications A Peer-to-Peer Service Supporting Data Quality: Design and Implementation Issues Quality-Driven Query Processing of XQuery Queries Data Quality in Web Information Systems Data Quality improvement in the DaQuinCIS Systems EXTERNAL Project Glossary terms ebXML: An Emerging B2B Framework Building an Enterprise Architecture: The Popkin Process Description Logics for Interoperability
Architectures Architectures Architectures Architectures Architectures Architectures Architectures Architectures and Enterprise Modelling Architectures and Enterprise Modelling Architectures and Enterprise Modelling Architectures, Enterprise Modelling and Ontologies
Deliverable D10.1
28/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
42
IDEAS Thematic Network: Deliverable 5.1
IDEAS Project (Editors: Ricardo Olavo and Ricardo Gonves) IDEAS Project (Editors: UNINOVA, COMPUTAS AS, AIDIMA, BAAN, CRF, EADS, Formula Research, Graisoft, Intracom, LEKS, SAP and TXT e-Solutions) IDEAS Project (Editor: Maria Anastasiou) IDEAS Project (Editor: Maria Anastasiou) Lutz Heuser
43
IDEAS Thematic Network: Deliverable 5.2
Architectures, Enterprise Modelling and Ontologies Architectures, Enterprise Modelling and Ontologies Architectures, Enterprise Modelling and Ontologies Architectures, Enterprise Modelling and Ontologies Architectures, Enterprise Modelling and Ontologies Architectures and Ontologies Architectures and Ontologies Architectures and Ontologies Architectures and Ontologies Architectures and Ontologies Architectures and Ontologies Architectures and Ontologies Architectures and Ontologies Enterprise Modelling and Ontologies Enterprise Modelling and Ontologies Enterprise Modelling and Ontologies Enterprise Modelling and Ontologies Enterprise Modelling and Ontologies Enterprise Modelling and Ontologies Enterprise Modelling and Ontologies Enterprise Modelling and Ontologies Ontologies Ontologies Ontologies Ontologies
44
IDEAS Thematic Network: Deliverable 1.1
45
IDEAS Thematic Network: Deliverable 1.2
46
The future of collaborative Business Processes
47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66
A Framework for Ontology Integration What to Ask to a Peer: Ontology-based Query Reformulation Query Reformulation over Ontology-based Peers Ontology-based Interoperability for Interorganizational Applications Ranked Matching for Service Descriptions using DAML-S A Model-based Ontology of the Software Interoperability Problem: Preliminary Results Using Ontologies to Compose Transformations of XML Schema Based Documents Adding trust to ontology based peer-to-peer networks A knowledge management scheme for meta-data: an information structure graph Supporting Enterprise Integration through a Unified Enterprise Modelling Language A Configurable Reference Modelling Language Process Models and Business Models a Unified Framework A Unified Foundational Ontology and some Applications of it in Business Modelling Setting up an ontology of business models UML for Ontology Modelling and interoperability Metadata as a knowledge management tool: supporting intelligent agent and end user access to spatial data Ontologies for Analysis and Improvement of Business Process Quality in a Virtual Enterprise On the use of WordNet for semantic interoperability: towards "cognitive computing" A knowledge-based approach to ontology learning and semantic annotation A Step Towards Context Insensitive Quality Control for Ontology
Diego Calvanese, Giuseppe De Giacomo and Maurizio Lenzerini Diego Calvanese, Giuseppe De Giacomo, Domenico Lembo, Maurizio Lenzerini and R. Rosati Diego Calvanese, Giuseppe De Giacomo, Domenico Lembo, Maurizio Lenzerini and R. Rosati D. Bianchini, V. De Antonellis and M. Melchiori Michael C. Jaeger and Stefan Tang Vincent Rosener, Thibaud Latour and Eric Dubois Johann Eder, Christian Koncilia, Marek Lehmann and H. Pichler Axel Hahn, Sven Abels Choon Yeul Lee Giuseppe Berio, Vor Anaya and gel Ortiz M. Rosemanna and W.M.P. van der Aalstb Maria Bergholtz, Prasad Jayaweera, Paul Johannesson and Petia Wohed Giancarlo Guizzardi and Gerd Wagner Alexander Osterwalder, Christine Parent and Yves Pigneur Vandana Kabilan and Paul Johannesson Lawrence A. West Jr. and Traci J. Hess Alexandra Galatescu and Taisia Greceanu Csaba Veres Roberto Navigli and Paola Velardi Sari Hakkarainen, Raimundas
Deliverable D10.1
29/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
Building Methodologies 67 68 69 Towards Ontology-Driven Institutional IS Engineering Methods and Techniques for Ontology-based Semantic Interoperability in Networked Enterprise Contexts Modelling and realizing interoperability
70 71 72 73 74 75 76 77
Ontology Driven Business Processes Integration a Position Paper Ontology of Enterprise Competencies Why we understand each other: the role of the context The PARADIGMA Project: an Ontology-based Approach for Cooperative Work in the Medical Domain A Patient Centred Process Ontology for Information Visualisation in Health Care Ontologies in the CRP Henri Tudor projects Ontology-based semantic infrastructure for service interoperability COEUR-SW: Concepts On Enriching, Understanding, and Retrieving the Semantics on the Web Complement Concept and Capability Discover Enriching Ontology Languages Adequacy for eBusiness Domain Using the WordNet ontology for interpreting Medical Records Towards Semantic Service Specification and Discovery Ontology for Characterising Architecture Frameworks Special Track on Business and Enterprise Ontologies: Systems, Methods and Experiences Tutorial on Ontologies Knowledge Representation with Ontologies Description Logics for Conceptual Design, Information Access, and Ontology Integration: Research Trends Basic Principles of Ontologies Tutorial on Ontologies Ontology Interoperability Ontology Representation and Reasoning ISO/TC 184/SC 5 Overview. Enterprise-reference architectures, Application integration frameworks and Interoperability profiles BPMN and Business Process Management - Introduction to the New Business Process Modelling Standard Love Affair With Web Services Warning? Enterprise Modelling: a Vision Inferred from a Study of the State of the Art An Enterprise Modelling And Analysis Toolkit The evolution of business processes from description to data to smart executable code is this the future of systems integration and collaborative commerce? BPM is Not About People, Culture and Change It's About Technology Business Process Fusion Is Inevitable Workflow Management within the ARIS Framework A Taxonomy Of A Living Model Of The Enterprise Reasoning on UML Class Diagrams Reasoning on UML Class Diagrams is EXPTIME-hard Business Process Management: The Third Wave
78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102
Matulevis, D. Strasunskas, Xiaomeng Su and G. Sindre Slim Turki, Christine Anidis, A. Khadraoui and M. Lard S. Castano, A. Ferrara and S. Montanelli M. A. Jeusfeld , Willem-J. van den Heuvel, J. Hoppenbrouwers, K. Leune, M. Papazoglou, H. Weigand and Jian Yang Per Backlund, Benkt Wangler, Eva SstrA. Toms, RoseMahrie lfeldt and A. Persson Mounira Harzallah G.Andrighetto and P. Assogna A. Di Leva, D. Occhetti and C. Reyneri Prasad Jayaweera and Paul Johannesson Jean-Sstien Brunner and Thibaud Latour D. Bianchini, V. De Antonellis and M. Melchiori S. Hakkarainen, A. Srg, T. Brasethvik, Y. Lin, J. Sampson, G. Sindre, D. Strasunskas, X. Su and C. Veres N. Boudjlida and Cheng Dong M. Missikoff And F. Schiappelli J. Espen Ingvaldsen and C. Veres S.Pokraev, Roel J. Wieringa and Maarten W.A. Steen Oddrun Pauline Ohren Coordinator: M.Missikoff Oleg Rokhlenko C Brewster and K. O'hara Enrico Franconi M. Missikoff, M.Lenzerini, F. Schiappelli M. Missikoff and F. Schiappelli M.Lenzerini Em delaHostria Martin Owen and Jog Raj Howard Smith and Peter Fingar MichaPetit Dursun Denle and Perakath C. Benjamin Doug Neal, Howard Smith and David Butler Howard Smith and Peter Fingar Howard Smith and Peter Fingar Theodore J. Williams Larry Whitman, Kartik Ramachandran and V. Ketkar D. Berardi, A. CalD. Calvanese and Giuseppe De Giacomo D. Berardi, Diego Calvanese, and Giuseppe De Giacomo Howard Smith and Peter Fingar
Ontologies Ontologies Ontologies
Ontologies Ontologies Ontologies Ontologies Ontologies Ontologies Ontologies Ontologies
Ontologies Ontologies Ontologies Ontologies Ontologies Ontologies Ontologies Ontologies Ontologies Ontologies Ontologies Ontologies Enterprise Modelling Enterprise Modelling Enterprise Modelling Enterprise Modelling Enterprise Modelling Enterprise Modelling Enterprise Modelling Enterprise Modelling Enterprise Modelling Enterprise Modelling Enterprise Modelling Enterprise Modelling Enterprise Modelling
Deliverable D10.1
30/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137
The Emergence of Business Process Management The Third Wave of Business Process Management Workflow is just a Pi process Value Chain Integration: The Next Frontier Business Process Modelling Language Business Process Modelling Notation Design Principles for Application Integration ENV 12204 Advanced Manufacturing Technology Systems Architecture Constructs For Enterprise Modelling Standardisation on Enterprise Integration & Engineering / Achievements, On-going Works and Future Perspectives From CIMOSA Architecture to CimOsa/rg Methodology CIMOSA Glossary Comparison of Modelling Methodologies Application and Process Integration Enterprise Modelling Glossary Enterprise Modelling and Integration: Myth or Reality? Achieving Enterprise Model Interoperability through the Model Based Architecture Framework for Enterprises Perspectives on the scope and definition process of the Unified Enterprise Modelling Language Using Business Network Models in web Pilarcos Enterprise Interoperability: A Standardisation View Enterprise Modelling and Integration : Towards Agile Manufacturing Systems Enterprise Modelling and the UML: (sometimes) a conflict without a case Enterprise Modelling Languages Comparison and Evaluation framework: A Proposal for the UEML Project Enterprise Models & Methodologies Enterprise Modelling: Issues, Problems & Approaches What is an Enterprise Model? Explanatory capability of enterprise models Taxonomy of AKM and EE/VO Services and Solutions External Ontology Process-Oriented Architecture Platforms First Tutorial on Enterprise Modelling GERAM: Generalised Enterprise Reference Architecture and Methodology Version 1.6.3 Glossary UEML Project Enterprise Modelling Languages Toward a new landscape of systems management in an autonomic computing environment Using Meta-Model Technologies to Organize Functionalities for
CSC'S Research Services Howard Smith Howard Smith and Peter Fingar Jeanne Baker, Peter Fingar And Howard Smith Assaf Arkin Business Process Management Initiative (BPMI) Paul Johannesson and Erik Perjons David Chen and Frans Vernadat CIMOSA Association CIMOSA Association K. Kosanke Benkt Wangler and Paul Johannesson Integrated Manufacturing Technology Initiative F.B. Vernadat Hrd D. Jsen and Oddrun P. Ohren MichaPetit and Patrick Heymans Lea Kutvonen David Chen and Frans Vernadat R H Weston G. Berio and M. Petit MichaPetit Pera Home Page. http://www.pera.net Peter Eirich Pera Home Page. http://www.pera.net Marite Kirikova Frank Lillehagen EXTERNAL Project Shone Sadler Raler and Jos. TomIFIPIFAC Task Force on Architectures for Enterprise Integration UEML Project (Editor: Raler) F.B. Vernadat G. Lanfranchi, P. Della Peruta, A. Perrone and D. Calvanese Erwan Breton and Jean Bvin
Enterprise Modelling Enterprise Modelling Enterprise Modelling Enterprise Modelling Enterprise Modelling Enterprise Modelling Enterprise Modelling Enterprise Modelling Enterprise Modelling Enterprise Modelling Enterprise Modelling Enterprise Modelling Enterprise Modelling Enterprise Modelling Enterprise Modelling Enterprise Modelling Enterprise Modelling Enterprise Modelling Enterprise Modelling Enterprise Modelling Enterprise Modelling Enterprise Modelling Enterprise Modelling Enterprise Modelling Enterprise Modelling Enterprise Modelling Enterprise Modelling Enterprise Modelling Enterprise Modelling Enterprise Modelling Enterprise Modelling Enterprise Modelling Enterprise Modelling Enterprise Modelling Enterprise
Deliverable D10.1
31/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
138 139 140 141 142 143 144
Active System Schemes Pera And Geram - Enterprise Reference Architectures In Enterprise Integration Unified Process Specification Language: Requirements for Modelling Process Research in Enterprise Modelling and Integration Some Methodological Clues for Defining a Unified Enterprise Modelling Language The Split Personality of BPM UEML Project WP1 Enterprise Modelling State of the Art Qualitative Analysis Of Enterprise Processes With Autonomous Petri Nets
Theodore J. Williams Craig Schlenoff, Amy Knutilla and Steven Ray Taner BilgiichaPetit Derek Miers and Enix Consulting UEML Project (Editor: MichaPetit) Christine Cov Didier Crestani and Frans Prunet
Modelling Enterprise Modelling Enterprise Modelling Enterprise Modelling Enterprise Modelling Enterprise Modelling Enterprise Modelling Enterprise Modelling
II.3.4 Conclusion
As already remarked, the glossary provides a first set of shared terms to be used as metadata for annotating documents and data in the INTEROP platform. Several features/improvements are foreseen to improve this initial result, both on the interface/architecture and the methodological side. For example, annotation tools must be defined and integrated in the INTEROP platform. The taxonomic structuring of the glossary must be manually reviewed in the light of a core ontology to be defined, and methods to include new terms must be provided. Finally, the use of terms (and later, of ontology concepts) for document access, clustering and retrieval must be implemented and evaluated.
II.3.5 References
Gruber, T.R. (1993). A Translation Approach to Portable Ontology Specification. Knowledge Acquisition 5, pp. 199-220. Ide N. and Vnis J. (1993). Refining Taxonomies extracted from machine readable Dictionaries, In Hockey, S., Ide, N. Research in Humanities Computing, 2, Oxford University Press. Musen, M.A. (1992). Dimensions of knowledge sharing and reuse. Computers and Biomedical Research 25, pp. 435-467. Navigli R., Velardi P and Gangemi A. (2003). Ontology Learning and its Application to Automated Terminology Translation. IEEE Intelligent Systems, vol. 18, pp. 22-31 Navigli R. and Velardi P. (2004). Learning Domain Ontologies from Document Warehouses and Dedicated Web Sites. Computational Linguistics, vol. 50 (2). Navigli R. and Velardi P. (2004b). Structural Semantic Interconnection: a knowledge-based approach to Word Sense Disambiguation, Proc. 3rd Workshop on Sense Evaluation, Barcelona. Navigli R., Velardi P., Cucchiarelli A. and Neri F. (2004). Quantitative and Qualitative Evaluation of the OntoLearn Ontology Learning System. Proc. 20th COLING 2004, Geneva. Noy N. F. and D. L. McGuinness (2001). Ontology Development 101: A Guide to Creating Your First Ontology. Stanford Knowledge Systems Laboratory Technical Report KSL-01-05 and Stanford Medical Informatics Technical Report SMI-2001-0880, March 2001.
Deliverable D10.1
32/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
II.4 INTEROP GLOSSARY
A
access protocol A set of specific procedures that enable a user to obtain services from a telephone company or network.
specific_procedure (set-of) Google define:
acquisition logistics Technical and management activities conducted to ensure supportability implications are considered early and throughout the acquisition process to minimize support costs and to provide the user with the resources to sustain the system in the field.
technical_and_management_activity (kind-of) http://www.eitoolkit.com/Tools/appendix/ei_glossary.html
activity A named process, function or task performed over time by humans or agents using up assigned resources to produce products and services. An activity is a sequence of internal actions and external events that causes an object to be in a particular state; activities are combined to form business processes.
named_process (kind-of) http://www.eitoolkit.com/Tools/appendix/ei_glossary.html
activity diagram An activity diagram is a special case of a state diagram in which all (or at least most) of the states are action or subactivity states and in which all (or at least most) of the transitions are triggered by completion of the actions or subactivities in the source states.
UML 1.5 specification: http://www.omg.org/docs/formal/03-03-01.pdf
advanced planning & scheduling (APS) The functionality to provide seamless execution of optimized plans. An enterprise application or module which allows to provide optimized plans with finite capacity from the tactical to the operational decision levels.
() http://www.eitoolkit.com/Tools/appendix/ei_glossary.html
agent an agent is a computer system, situated in some environment, that is capable of flexible autonomous action in order to meet its design objectives. There are thus three key concepts in our definition: situatedness, autonomy, and flexibility.
http://www.ecs.soton.ac.uk/~nrj/download-files/roadmap.pdf
Deliverable D10.1
33/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
agent communication Agent communication is the exchange of information between agents, transferred by the integration infrastructure, according to specific agent communication protocols or
exchange (kind-of) www.lips.utexas.edu/infrastructure/infra_overview.html
application interoperability The characteristic demonstrated by two (or more) independent application components of exhibiting predefined behaviours in a consistent manner, e.g. user interface interoperability, data instance sharing interoperability, etc.
characteristic (kind-of) www.posc.org/InteropRelease/ Interoperability/InteropIntro/int_appa.html
architecture An organized framework consisting of principles, rules, conventions, and standards that serves to guide development and construction activities such that all components of the intended structure will work together to satisfy the ultimate objective of the structure.
organized_framework (kind-of) http://www.eitoolkit.com/Tools/appendix/ei_glossary.html
architecture framework An architecture framework is a tool. It should describe a method for designing an information system in terms of a set of building blocks, and for showing how the building blocks fit together. It should contain a set of tools and provide a common vocabulary. It should also include a list of recommended standards and compliant products that can be used to implement the building blocks.
tool (kind-of) www.opengroup.org/architecture/togaf8-doc/arch/p1/togaf_faq.htm
B
best practice (or leading practice) Strategies, activities, or approaches which have been shown through benchmarking of research and performance evaluation to be the most effective.
strategy (kind-of) http://www.eitoolkit.com/Tools/appendix/ei_glossary.html
boundary The border around a market area or a modelling domain that is being studied.
border (kind-of) https://www.quirks.com/resources/glossary.asp
BPR methodology The Business Process Reengineering Methodology is a structured sequence of activities
Deliverable D10.1
34/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
and a set of working groups that constitutes the typical BPR Project.
() http://www.eitoolkit.com/Tools/appendix/ei_glossary.html
business activity An individual activity or unit of work performed in the business. An activity can be either continuous in nature (function) or discontinuous (process). A business activity performs a transformation with adding value to the product or service.
individual_activity (kind-of) www.cio.gov.bc.ca/other/daf/IRM_Glossary.htm
business analyst A business analyst is a key person involved in the complete cycle of a project. The essential responsibility of a Business Analyst is to be the primary systems requirements
key_person (kind-of) www.indiangaming.org/info/employment/bus-analyst.shtml
business application A computer-based system that processes business information in support of a specific business function or business process such as purchasing, accounting, or logistics
computer-based_system (kind-of) http://www.eitoolkit.com/Tools/appendix/ei_glossary.html
business case A structured proposal for business improvement that functions as a decision package for organizational decision-makers. A business case includes an analysis of business process performance and associated needs or problems, proposed alternative solutions, assumptions, constraints, and a risk-adjusted cost-benefit analysis.
structured_proposal (kind-of) www.ichnet.org/glossary.htm
business domain A collection of related business modelling constructs that it is normally practical to use together. UML Class diagrams is a domain in this sense. A set of activities that are typical for a specific business. For instance, the mechanical industry is a business domain.
domain (kind_of) comp
business entity 1) An organization that possesses a separate existence for tax purposes. Some types of business entities include corporations and limited liability companies. 2) A person, place, or thing that is tracked by your business. For example, a business entity can be an account, a customer, or a part. An instance of a business domain.
Deliverable D10.1
35/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
organization (kind-of) Google define:
business function Group of business activities which together completely support one aspect of furthering the mission of the organization describing what is done within the organization independently from the organization structure.
group (kind-of) Google define:
business functionality Set of capabilities of the system which provide some business service to the user.
functionality (kind_of) comp
business goal What the business needs or wants to achieve in response to the business drivers. The strategic objectives to reach at a long term level.
() www.andrews.edu/ITS/AS/dw/Andrews/dictionary.html
business model a model of the business in terms of the terminology of the domain experts and users without regard to any specific system or software application. The main objectives of a business model are to formally represent the business in terms of the essential business objects and how they collaborate to perform the major business processes. The business model forms the basis for understanding and engineering (or reengineering) the business and its processes. The business model typically consists of a business-level use case model and associated object model. The business model is composed of a set of business activities
model (kind-of) www.donald-firesmith.com/Glossary
business object A representation of a thing active in the business domain, including at least its business name and definition, attributes, behavior, relationship and constraints.
representation (kind-of) http://www.posc.org/InteropRelease/Interoperability/InteropIntro/int_appa.html
business object facility (BOF) A collection of services that facilitate the definition and use of business objects.
service (collection-of) http://www.posc.org/InteropRelease/Interoperability/InteropIntro/int_appa.html
business objective
Deliverable D10.1
36/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
A business objective is something the business is aiming toward or a strategic position it is working to attain.
() management.about.com/cs/generalmanagement/g/objective.htm
business operations the activity consisting of the cohesive collection of all tasks that are primarily performed to keep a business operating after it has been deployed for use by the user organizations.
operations (kind_of) comp
business practice knowledge of how something is usually done in business.
practice (kind_of) comp
business process A collection of activities that work together to produce a defined set of products and
activity (collection-of) http://www.eitoolkit.com/Tools/appendix/ei_glossary.html
business process improvement A philosophy and practice of looking for incremental ways to improve organizational processes, on an ongoing basis.
philosophy (kind-of) Google define:
business process integration Business Process Integration is the tying together of automated (not only automated) business processes with legacy or custom systems.
tying_together (kind-of) www.dewpoint.com/web_services/2_1_2_integration.html
business process management Business Process Management is the definition, analysis, execution, monitoring and administration of a company's business processes.
definition (kind-of) www.brightstar.com/page31.htm
business process model A graphic and descriptive representation of business processes or value chains that cut across functions and organizations. The model may be expressed in different levels of detail, including decomposition into successive lower levels of activities.
graphic_and_descriptive_representation (kind-of) www.cio.gov.bc.ca/other/daf/IRM_Glossary.htm
Deliverable D10.1
37/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
business process modelling Business process modelling is the process of building and maintaining BP models.
process (kind-of) www.cbt.es/mediat-sme/Doc/carsfof-mediat-cr2.pdf
business process reengineering (BPR) A methodology that examines, rethinks, and redesigns mission, products, and services within the political, social, and economic environment of the organization.
methodology (kind-of) http://www.eitoolkit.com/Tools/appendix/ei_glossary.html
business relationship a component of a business that models one of its relationships to another organization.
business (part-of) www.donald-firesmith.com/Glossary
business requirement any mandatory, externally-observable, and validatable (e.g., testable) behaviour, datum, characteristic, or interface of a business enterprise, application, application domain, framework, or component.
requirement (kind_of) comp
business semantics The explicit model of business semantics is the corporal knowledge and important parts of software assets.
explicit_model (kind-of) www.starlab.vub.ac.be/research/projects/poirot/STAR-2004-09.pdf
business services Services such as repairs and maintenance, consulting and professional advice, installation, equipment leasing, marketing research, advertising, temporary office personnel and caretaking services.
service (kind-of) Google define:
business transaction A unit of work acted upon by a data capture system to create, modify, or delete business data. Each transaction represents a single valued fact describing a single business event.
unit (kind-of) Google define:
business user The business user is the most valuable customer of the service provider.
Deliverable D10.1
38/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
most_valuable_customer (kind-of) www.huawei.com/solutions/infodetail1.jsp?solutionID=136&kind=network&farentID=32
C
capability and interoperability analysis Analyze models and architectures in terms of their support to joint concepts, identify capability needs, and determine the operational and support-related performance attributes of a system(s) that provide the capabilities required.
() www.opengroup.org/architecture/togaf8-doc/arch/p1/togaf_faq.htm
class diagram A class diagram consists of a group of classes and interfaces reflecting important entities of the business domain of the system being modeled, and the relationships between these classes and interfaces.
diagram (kind-of) http://www.omg.org/
class hierarchy It is a set of classes related by generalization/specialization relationships. In a hierarchy, a class can be a specialization (sub-class) of another one (super-class) when it represents a more specific element in the modelled domain with respect to that represented by the superclass. A sub-class inherits the properties describing its super-class.
http://www.omg.org/
class( model ) It is the specification of a set of objects of the same kind. These objects are called the members of the class.
model (kind_of) http://www.omg.org/
classification scheme A set of target classes organized into a hierarchy. The classification is the act of placing an object or concept into the scheme. At the top of this structure is a single classification the root node that applies to all objects. Nodes below this root are more specific classifications that apply to subsets of the total set of classified objects.
target_classe (set-of) Google define:
collaboration Relationships that involve working with several business partners to jointly solve business problems. These relationships include collaborative planning for supply, maintenance, transportation, and related services.
Deliverable D10.1
39/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
relationship (kind_of) http://www.eitoolkit.com/Tools/appendix/ei_glossary.html
collaboration systems Systems and software that enable group participation in a problem or process. Collaboration systems supply methods for group definition, common technology, interaction and follow-up, and present a common situation view to all participants while
system (kind-of) www.bridgefieldgroup.com/glos2.htm
collaborative filtering Collaborative filtering is the process of filtering documents by determining what documents other users with similar interests and/or needs find relevant.
process (kind-of) km.aifb.uni-karlsruhe.de/projects/ swap/public/Publications/swap-d3.1.pdf
collaborative work, computer supported collaborative work computer supported collaborative work is the use of a computer as an intermediary in human interactions.
() www.cs.wustl.edu/~kjg/CS333_SP97/spreadsheet.html
common object request broker architecture A specification developed by the Object Management Group in 1992 in which pieces of programs (objects) communicate with other objects in other programs, even if the two programs are written in different programming languages and are running on different platforms. A program makes its request for objects through an object request broker, or ORB, and thus does not need to know the structure of the program from where the object comes. CORBA is designed to work in object-oriented environments.
specification (kind-of) http://iishelp.web.cern.ch/IISHelp/iis/htm/core/iigloss.htm
common vocabulary A set of words about an observed portion of reality at different levels of abstraction with related definitions given in a specific language that are accepted by a set of enterprises, systems or humans that want to communicate. A common vocabulary is the basis of all
Google define:
common-shared conceptualisation A conceptualization that is accepted and shared by more parties that wish to collaborate.
conceptualisation (kind-of) Google define:
communication infrastructure
Deliverable D10.1
40/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
The computer and communication hardware, software, databases, people, and policies supporting the enterprise's communication functions.
infrastructure (kind_of) comp
communication protocol The method by which two computers coordinate their communications.
method (kind-of) Google define:
competency capabilities of an individual, group, organisational unit and organisation component interface A set of methods supported by a component, and type definitions for the data used for arguments to those methods. An interface itself is a type and can be an argument for a
methods_supported (set-of) Google define:
conceptual model An abstract representation of an object or phenomenon that provides a common
abstract_representation (kind-of) www.pera.net/Tools/Glossary/ Enterprise_Integration/Glossary.html
conceptual schema It is an abstract representation of the domain of interest characterized by concepts or their formation without a dependency of implementation terminology or rules.
Google define:
conceptual structure A Conceptual Structure is a model meant to represent the domain knowledge of an
model (kind-of) www-clips.imag.fr/calie04/actes/Pecheanu_final.pdf
conceptualization Conceptualization is the representation of reality as perceived by human mind, independently of the vocabulary used or the actual occurrence of a specific situation, performed by means of concepts (or classes) to describe the modelled elements.
elaborated_concept (kind-of) http://www-db.stanford.edu/pub/gio/1994/vocabulary.html
conflict an incompatibility of actions or goals.
incompatibility (kind-of) missing
Deliverable D10.1
41/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
constraint A semantic condition or restriction, obtained by expressing logical relations among several variables used to model the domain of interest, each taking a value in a given domain. A constraint thus restricts the possible values that variables can take.
semantic_condition (kind-of) http://www.omg.org/
constraint language A formal logical language used to express constraints.
formal_language (kind-of) http://www.omg.org/
cross-platform A software application that can run under more than one operating system.
software_application (kind-of) www.y2k.gov/got.html
D
data analysis The process of systematically applying statistical and logical techniques to describe, summarize, and compare data. Topic areas:Accountability and Evaluation.
process (kind-of) Google define:
data exchange, data interchange Flow of data among unrelated data sources and multiple applications.
process (kind-of) www.microsoft.com/technet/prodtechnol/sql/70/evaluate/sqldifaq.mspx
data integration Process of blending data from multiple, often heterogeneous sources by resolving conflicts and differences in representing them to create an homogeneous, unified view on the overall set of original data sources.
process (kind-of) http://www-db.stanford.edu/pub/gio/1994/vocabulary.html
data interoperability Data interoperability is the sharing of data between unrelated data sources and multiple applications.
sharing (kind-of) www.microsoft.com/technet/prodtechnol/sql/70/evaluate/sqldifaq.mspx
data management The activities of strategic data planning, data element standardization, information
Deliverable D10.1
42/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
management control, data synchronization, data sharing, and database development. Active data management increases system effectiveness and improves the accuracy and timeliness of data to derive maximum business benefit. (Core Policy Manual (Ch. 12): 12.3.2 iii Data
activity (kind-of) www.cio.gov.bc.ca/other/daf/IRM_Glossary.htm
data model A graphical and/or textual representation of the business data deemed of interest to an organization. It is a representation of data objects that can be shared and reused across application systems, organizational boundaries, and different functional areas. Examples of data models are and Entity relationship diagram (ERD), a class diagram or a data dictionary. See also Entity Relationship Diagram.
graphical_and_textual_representation (kind-of) www.cio.gov.bc.ca/other/daf/IRM_Glossary.htm
data translation Data translation is the process of cleaning and reformatting data when moving it from one representation (form and syntax) to another.
process (kind-of) http://www-db.stanford.edu/pub/gio/1994/vocabulary.html
data type An attribute of a data element or field that specifies the DBMS type of physical values, such as numeric, alphanumeric.
attribute (kind-of) www.cio.gov.bc.ca/other/daf/IRM_Glossary.htm
data warehouse A subject-oriented, integrated, non-volatile, time-variant, enterprise wide collection of data organized to support management needs. A single, complete and consistent store of data obtained from a variety of sources and made available to end users in a way they can understand and use in a business context.
() www.andrews.edu/ITS/AS/dw/Andrews/dictionary.html
data warehousing The process of extracting data from a variety of data sources and channelling it into a specific data warehouse for analysis.
process (kind-of) http://www.eitoolkit.com/Tools/appendix/ei_glossary.html
database A software system containing data.
Deliverable D10.1
43/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
database application A software application that uses a database management system. The following are examples of database applications: computerized library systems automated teller machines flight reservation systems computerized parts inventory systems MGI. database integration Database Integration is the process of integrating systems at the database level.
process (kind-of) c2.com/cgi/wiki?DatabaseIntegration
database management system A collection of computer programs that allow storage, modification, and extraction of information from a database. There are many different types of DBMSs, ranging from small systems that run on personal computers to huge systems that run on mainframes.
computer_program (collection-of) Google define:
database model A model of a database. It is made of at least a data model which describes the general logical structure in which data (records) is stored. It may also contain a model of other aspects of the database such as a description of updating and querying activities.
general_logical_structure (kind-of) courses.nnu.edu/bu512bm/ch07.ppt
decision maker someone who administers a business. A person who acts on the decision variables to reach the objectives.
person (kind-of) Google define:
decision support software Use of computers to supply and process information needed to make decisions. Term is typically applied to business applications.
use (kind-of) Google define:
decision-making A procedure for making logical decisions on the basis of sample data.
procedure (kind-of) www.uvm.edu/~dhowell/StatPages/Fundamentals/Glossary.html
deployment The process of placing an application in a distributed environment and making the application available for use. Deployment can include such tasks as installation,
Deliverable D10.1
44/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
configuration, and administration of various parts of the application.
process (kind-of) edocs.bea.com/wle/tuxedo/glossary/glossary.htm
deployment diagram A graphical representation of a concrete software architecture and its relationships with the software components
UML
description logic Description Logic is a subfield of knowledge representation and as such aims to provide a vehicle for expressing structured information and for reasoning.
subfield (kind-of) www.daml.org/2000/10/daml-oil
design pattern Repeated fragment of information processing that can serve as a guide to software design and as a test of the completeness and correctness of the definitions of shared services and
repeated_fragment (kind-of) http://www.posc.org/InteropRelease/Interoperability/InteropIntro/int_appa.html
design phase the third phase of a project after the modelling and the diagnosis of the existing system. design process A systematic problem-solving strategy, with criteria and constraints, used to develop many possible solutions to solve a problem or satisfy human needs and wants and to winnow (narrow) down the possible solutions to one final choice.
systematic_problem-solving_strategy (kind-of) Google define:
developer A person with programming skills whom creates tools to be used by other developers or by end-users.
person (kind-of) http://www.posc.org/InteropRelease/Interoperability/InteropIntro/int_appa.html
development process a project-specific process for delivering an application or other work products to a
project-specific_process (kind-of) docs.sun.com/db/doc/805-4368/6j450e60h
distributed application An application that runs on two or more networked computers.
application (kind-of)
Deliverable D10.1
45/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
www.liebert.com/support/glossary/net_gloss.asp
distributed environment A configuration of hardware and software that is physically and geographically dispersed but networked together for communication.
configuration (kind-of) Google define:
distributed object technology Object technology with the ability to distribute objects across heterogeneous computing environments. With distributed object technology, the servers and clients can be in different address spaces or in different processors that may be distributed across a network (e.g. an Intranet or the Internet).
object_technology (kind-of) http://www.posc.org/InteropRelease/Interoperability/InteropIntro/int_appa.html
domain expert A domain expert contains the raw knowledge that a knowledge engineer uses to structure the knowledge to fuse and formulate the rule base. [DEC]. One whole is well versed on all aspects of a domain of knowledge.
() www.pera.net/Tools/Glossary/ Enterprise_Integration/Glossary.html
domain knowledge Knowledge about a particular domain, as distinct from task, method or application
knowledge (kind-of) Google define:
domain model In the traditional software engineering perspective, a precise representation of specification and implementation concepts that define a class of existing systems (i.e. a domain). Produced through domain analysis. In a constructionist perspective, a domain model is the set of objects and behaviors contained in a domain-oriented system. In this perspective, the domain model evolves over time as users modify system to meet changing requirements.
precise_representation (kind-of) Google define:
domain ontology An explicit formal specification of how to represent the objects, concepts and other entities that are assumed to exist in some specific area of interest and the relationships that hold
ontology (kind_of) comp
E Deliverable D10.1 46/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
electronic business (EB) The buying and selling of goods and services on the Internet
buying (kind-of) http://www.eitoolkit.com/Tools/appendix/ei_glossary.html
electronic commerce (EC) The interchange and processing of information using electronic techniques for accomplishing transactions based upon the application of commercial standards and
interchange (kind-of) http://www.eitoolkit.com/Tools/appendix/ei_glossary.html
electronic commerce infrastructure (ECI) ECI is a combination of software, hardware, and communication media components that support Electronic Commerce.
combination (kind-of) http://www.eitoolkit.com/Tools/appendix/ei_glossary.html
electronic data interchange The computer-to-computer exchange of business data in a standardized format between entities.
computer-to-computer_exchange (kind-of) http://www.eitoolkit.com/Tools/appendix/ei_glossary.html
enterprise An enterprise is defined as the aggregate of all functional elements participating in a business process improvement action regardless of the organizational structure housing those functional elements.
aggregate (kind_of) http://www.eitoolkit.com/Tools/appendix/ei_glossary.html
enterprise activity a set of partially ardered basic operations executed to perform the things to be done within an enterprise. Activities are performed by functional entities of the enterprise and transform an input state into an output state.
Enterprise Modelling and Integration, Frans Vernadat, Chapman & Hall, 1996
enterprise architecture The explicit description and documentation of the current and desired relationships among business and management processes and information
() technology.sunset.usc.edu/gsaw/gsaw2004/s10b/kreitman.pdf
enterprise information integration Enterprise Information Integration is the process ofintegrating structured data from any
Deliverable D10.1
47/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
relevant source for the purpose of presenting an intelligent, real-time view of the business to a business analyst or an operational application.
process_ofintegrating (kind-of) www.sagent.com/products/pdf/EII.pdf
enterprise integration Enterprise Integration is concerned with facilitating information, control and material flows accross organisational boundaries by connecting all the necessary functions and heterogeneous functional entities in order to improve communication, cooperation and coordination within the enterprise so that the enterprise behaves as an integrated whole, therefore enhancing, its overall productivity, flexibility and capacity for management of change. Heterogeneous functional entities to be integrated are information systems,
Enterprise Modelling and Integration, Frans Vernadat, Chapman & Hall, 1996
enterprise model One representation of a perception of the enterprise. It can be made of several submodels including (but not limited to) process models, data models, resource models and organisational models. The contents of an enterprise model is whatever the enterprise considers important for its operations.
Enterprise Modelling and Integration, Frans Vernadat, Chapman & Hall, 1996
enterprise modelling The process of building models of whole or part of the enterprise (e.g. process models, data models, resource models, new ontologies, etc.) from knowledge about the enterprise, previous models, and/or reference models as well as domain ontologies and model representation languages.
Enterprise Modelling and Integration, Frans Vernadat, Chapman & Hall, 1996
enterprise ontology The Enterprise Ontology is a collection of terms and definitions relevant to business
term (collection-of) www.aiai.ed.ac.uk/project/enterprise/enterprise/ontology.html
enterprise reference architecture An enterprise reference architecture is the enterprise technology equivalent of a master blueprint for an enterprise's current and future technology.
enterprise_technology_equivalent (kind-of) www.doculabs.com/research/event_erawebsem.html
enterprise resource Enterprise Resource is the means for an enterprise to create value.
mean (kind-of) www.imm.dtu.dk/pubdb/views/edoc_download.php/2537/ps/imm2537.ps
Deliverable D10.1
48/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
enterprise resource planning (ERP) The predominant commercial Enterprise Integration solution. ERP is a family of computer programs that instantly access and update information shared among business functions typically including manufacturing logistics, procurement, finance, and human resources.
predominant_commercial_enterprise_integration_solution (kind-of) http://www.eitoolkit.com/Tools/appendix/ei_glossary.html
enterprise software Software that solves an Enterprise Problem (rather than a departmental one) and that is written with an Enterprise Software Architecture
software (kind-of) www.officevision.com/pub/p5ee/definitions.html
enterprise system Enterprise Software running on an Enterprise Platform (which, by implication, has the Attributes of an Enterprise System as defined below)
enterprise_software (kind-of) www.officevision.com/pub/p5ee/definitions.html
enterprise-wide network (EWN) A network that serves an entire organization. Implies interoperability of disparate computing platforms, such as MS-DOS, UNIX, OS/2, and Macintosh.
network (kind-of) www.liebert.com/support/glossary/net_gloss.asp
expert system A computer system that embodies the specialized knowledge of one or more human experts and uses that knowledge to solve problems. [DEC].
computer_system (kind-of) www.pera.net/Tools/Glossary/ Enterprise_Integration/Glossary.html
extended enterprise An extended enterprise is a dynamic networked organisation, being developed ad-hoc to reach a certain goal based on the resources of several existing co-operating enterprises. An EE is extended both in physical location and knowledge representation,
dynamic_networked_organisation (kind-of) Interop WP10 Glossary
F
federation A named set of interacting federates, a common federation object model, and supporting runtime infrastructure, that are used as a whole to achieve some specific objective
interacting_federates (set-of)
Deliverable D10.1
49/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
www.semb.co.uk/reference/glossary.htm
formal description 1) A description expressed in a formal language with well-defined syntax and semantics. 2) a formal description is a concrete or abstract representation of an intended behavior.
concreteor_abstract_representation (kind -of) ists.w3.org/Archives/Public/www-qa-wg/2002Nov/0017.html
formal language A language equipped with a formal syntax and/or a formal semantics. Formal means defined so precisely that it leaves no (or very few) place for ambiguity or freedom.
languages_people (kind-of) Google define:
formal ontology A terminological ontology whose categories are distinguished by axioms and definitions stated in logic or in some computer-oriented language that could be automatically translated to logic. There is no restriction on the complexity of the logic that may be used to state the axioms and definitions. The distinction between terminological and formal ontologies is one of degree rather than kind. Formal ontologies tend to be smaller than terminological ontologies, but their axioms and definitions can support more complex inferences and computations. The two major contributors to the development of formal ontology are the philosophers Charles Sanders Peirce and Edmund Husserl. Examples of formal ontologies include theories in science and mathematics, the collections of rules and frames in an expert system, and specification of a database schema in SQL.
terminological_ontology (kind-of) www.jfsowa.com/ontology/gloss.htm
function 1) A function is something that associates each element of a set with an element of another set (which may or may not be the same as the first set). The concept of function appears quite often even in nontechnical contexts. For example, a social security number uniquely identifies the person, the income tax rate varies depending on the income, the final letter grade for a course is often determined by test and exam scores, homeworks and projects, and so on. 2) the appropriate or assigned duties, responsibilities, missions, or tasks of an
appropriate_duty (kind_of) http://www.cs.odu.edu/~toida/nerzic/content/function/definitions.html, http://www.eitoolkit.com/Tools/appendix/ei_glossary.html
functional entity An active resource inside or outside of an enterprise capable of executing basic functional operations of an activity and playing a given role in the course of a process. A similar term
Deliverable D10.1
50/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
used in artificial intelligence is agent.
Enterprise Modelling and Integration, Frans Vernadat, Chapman & Hall, 1996
functional requirement A requirement that specifies a function that a system or system component must be able to perform, i.e. the services provided for the users and for other systems
() IEEE
functionality Set of capabilities of the system which provide some service to the user.
capability (kind-of) www.worldofdave.ca/web/451/glossary.html
G
global view A global representation of an enterprise or a part of the enterprise based on the concepts of system theory. graphical user interface A type of environment that represents programs, files, and options by means of icons, menus, and dialog boxes on the screen. The user can select and activate these options by pointing and clicking with a mouse or, often, with a keyboard.
environment (kind-of) http://iishelp.web.cern.ch/IISHelp/iis/htm/core/iigloss.htm
H
human factors A body of information about human abilities, human limitations, and other human characteristics from a physical and psychological perspective that are relevant to the design, operations, and maintenance of complex systems.
body (kind-of) www.northropgrummanit.com/set/glossary.html
I
inference engine 1) A program that infers new facts from known facts using inference rules. 2) The part of a rule-based system that selects and executes rules. The conclusion that an inference engine will draw from a given set of facts is not known in advance. [DEC].
rule-based_system (part-of) www.pera.net/Tools/Glossary/ Enterprise_Integration/Glossary.html
information exchange information exchange is the electronic exchange of data and supporting information
Deliverable D10.1
51/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
electronic_exchange (kind-of) www.jhuapl.edu/.../guides/safety_v1/msword/Safety_02_What%20is%20Safety%20Info%20Exch%20R1%20DONE.doc
information extraction Information Extraction is the process of extracting user-specified text from a set of documents. The extracted text can range from a list of names to a database of event
process (kind-of) Google define:
information infrastructure the information infrastructure is the combination of public and private networks, computers and electronics that connects people with people, and people with computers.
combination (kind-of) www.innovation.cc/awards/gii.htm
information management The function of managing information as an enterprise resource, including planning, organizing and staffing, leading and directing, and controlling information. Information management includes managing data as the enterprise knowledge infrastructure and information technology as the enterprise information technical infrastructure, and managing applications across business value chains.
function (kind-of) www.cio.gov.bc.ca/other/daf/IRM_Glossary.htm
information model A high-level graphical representation of the information resource requirements of an organization showing the information classes and their relationships.
high-level_graphical_representation (kind-of) www.cio.gov.bc.ca/other/daf/IRM_Glossary.htm
information modelling information modelling is the core of conceptualisation, system structuring, and justification for information system design.
core (kind-of) www.pori.tut.fi/ejc/ejc-book-2001-proc-XIII.html
information need Information need is the individual's conception of what information he needs to satisfy a more basic need of his.
individual (kind-of) informationr.net/ir/4-2/isic/kari.html
information requirement An information requirement is a report from which an office or organization draws part or all
Deliverable D10.1
52/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
of the data required for another report.
report (kind-of) www.tpub.com/content/administration/14260/css/14260_72.htm
information resource Any entity, electronic or otherwise, capable of conveying or supporting intelligence or knowledge; e.g. a book, a letter, a picture, a sculpture, a database, a person. See also DLO.
entity (kind-of) Google define:
information services Programs that provide for the collection, classification, storage, retrieval and dissemination of recorded knowledge for the community. Included are computer bulletin boards, information and referral programs, information lines, library services, media services, public awareness/education, campaigns, research data and rumor control activities.
program (kind-of) Google define:
information source An information source is a source alphabet together with probabilities.
source_alphabet (kind-of) www.dcs.st-and.ac.uk/~sal/ school/CS3010/Lectures/forhtml/node2.html
information technology Includes all matters concerned with the furtherance of computer science and technology and with the design, development, installation, and implementation of information systems and applications.
development (kind-of) www.ichnet.org/glossary.htm
infrastructure The basic framework or features of a system or organization.
basic_framework (kind-of) www.iteawww.org/TAA/Glossary.htm
integrated system 1) an integrated system is a complete or a unified system, although it will generally have subordinated components. 2) A system in which separate programs perform separate functions with communication and data-passing between functional programs performing standardized I/O routines and a common data-base. Such systems allow flexibility in addition/revision/deletion of various processing functions without disrupting the entire
system (kind-of) www.pera.net/Tools/Glossary/ Enterprise_Integration/Glossary.html; http://www.dundee.ac.uk/crsem/TEF/proceed.htm
Deliverable D10.1
53/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
integration 1) The merging or combining of one or more components, parts, or configuration items into a higher level system for ensuring that the logical and physical interfaces can be satisfied, and the integrated system satisfies its intended purpose. 2) In systems design, the process that allows separate functions to use a common technology and database, pass data and information without requiring translation, reformatting or duplicate entry, and enable crossfunctional views and management.
process (kind-of) Enterprise Modelling and Integration, Frans Vernadat, Chapman & Hall, 1996
integration platform A hardware and software environment providing a set of services to enable systems interoperability and integration (i.e. communications, cooperation and coordination).
Enterprise Modelling and Integration, Frans Vernadat, Chapman & Hall, 1996
integration process The process of combining intermediate contents from multiple, often heterogeneous
elaboration (kind-of) http://www-db.stanford.edu/pub/gio/1994/vocabulary.html#Sec2
integration technique A well-defined procedure used to accomplish integration
technique (kind_of) comp
integrity constraint Integrity constraints are the constraints that we wish to impose in order to protect the database from becoming inconsistent.
constraint (kind-of) www.sci.usq.edu.au/courses/CSC3400/resources/StudyBook/m11.pdf
intellectual property refers to the intangible or intellectual nature of works or creations and the body of laws governing such property; areas of intellectual property are patents, trademarks, industrial designs, confidential information, copyright, etc.
intangible_or_intellectual_nature (kind-of) www.nrcan-rncan.gc.ca/cfs-scf/ science/prodserv/kmglossary_e.html
intelligent agent A program that automates the task of finding information on the internet, perhaps delivering a list of news stories on a particular topic on the desktop every morning.
program (kind-of) Google define:
Deliverable D10.1
54/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
interaction A behavioral specification that comprises a set of message exchanges among a set of objects within a particular context to accomplish a specific purpose.
behavioural_specification (kind-of) swiki.hfbk-hamburg.de:8888/MusicTechnology/24
interface A recognized and definable crossover point between two systems.
recognized_crossover (kind_of) http://www.eitoolkit.com/Tools/appendix/ei_glossary.html
interoperability The ability of information systems to operate in conjunction with each other encompassing communication protocols, hardware software, application, and data compatibility layers
ability (kind-of) www.ichnet.org/glossary.htm
interoperability problem 1) The problem of bringing together heterogeneous and distributed information resources and services 2) interoperability problem is the absence of a state-of-the-art, standardized model representation. The solution to this interoperability problem is the creation of a system of standard interface specifications.
absence (kind-of) www.ercim.org/publication/Ercim_News/enw32/ernst.html
K
knowledge information evaluated and organised in the human mind so that it can be used purposefully
information (kind-of) www.aslib.co.uk/info/glossary.html
knowledge acquisition The process of extracting knowledge. It can be derived from many sources: an expert, documents, books, manuals, forms, etc.
process (kind-of) www.pera.net/Tools/Glossary/ Enterprise_Integration/Glossary.html
knowledge base The part of an artificial intelligence system that contains structured, codified knowledge and heuristics used to solve problems. [DEC].
artificial_intelligence_system (part-of) www.pera.net/Tools/Glossary/ Enterprise_Integration/Glossary.html
knowledge base interoperability
Deliverable D10.1
55/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
The ability of knowledge bases on multiple machines to communicate.
interoperability (kind_of) comp
knowledge engineer A person who implements an expert system. A knowledge engineer interviews experts to utilize the raw knowledge from which to structure the knowledge base and formulate the rule base. [DEC].
person (kind-of) www.pera.net/Tools/Glossary/ Enterprise_Integration/Glossary.html
knowledge integration combining separate knowledge management programs into a more complete whole, coupled with adapting diverse groups into a coordinated knowledge-sharing culture.
combining_separate_knowledge_management_program (kind-of) www.nrcan-rncan.gc.ca/cfs-scf/ science/prodserv/kmglossary_e.html
knowledge management The process of capturing value, knowledge and understanding of corporate information, using IT systems, in order to maintain, re-use and re-deploy that knowledge.
process (kind-of) www.documentmanagement.org.uk/pages/glossary.htm
knowledge management infrastructure A knowledge management infrastructure is an infrastructure that identifies the components involved in capturing, organising, accessing and managing knowledge content.
infrastructure (kind-of) csweb.rau.ac.za/staff/labuschagne/research/articles/transforming.pdf
knowledge model A knowledge model is a specification of a domain or problem solving behaviour, which abstracts from implementation-cantered considerations.
specification (kind-of) kmi.open.ac.uk/software/downloads-text.cfm
knowledge repository A knowledge repository is an online information resource that is: comprehensive, accurate and up-to-date.
online_information_resource (kind-of) www.steptwo.com.au/papers/kmc_callcentre/
knowledge representation Knowledge representation is the application of logic and ontology to the task of constructing computable models for some domain.
Deliverable D10.1
56/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
application (kind-of) www.jfsowa.com/krbook/krpref.htm
knowledge representation Knowledge representation is the application of logic and ontology to the task of constructing computable models for some domain.
application (kind-of) www.pera.net/Tools/Glossary/ Enterprise_Integration/Glossary.html
knowledge representation language A knowledge representation language is a set of abstractions and conceptualizations about how to formulate knowledge; it is a language for capturing knowledge.
abstraction (kind-of) www.swi.psy.uva.nl/usr/bert/pdf/thesis/03vHoof.pdf
knowledge representation system A knowledge representation system is a way of encoding propositions or facts as finite data structures in a digital computer.
way (kind-of) www.rbjones.com/rbjpub/rbjcv/papers/wp32.htm
knowledge source Knowledge source is the person, document, non-print source, or place that is the origin or prime cause of knowledge
person (kind-of) home.earthlink.net/~ddstuhlman/defin1.htm
knowledge-based system A system that uses stored knowledge to solve problems in a specific domain.
system (kind-of) Google define:
L
language A set of characters, conventions, and rules, that is used for conveying information. The three aspects of language are pragmatics, semantics, and syntax.
character (set-of) www.daube.ch/share/nla13.html
language specification A document that describes the major technical requirements for a language
specification (kind_of) comp
legacy application
Deliverable D10.1
57/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
An application that executes on older generation systems, or that has been used for a considerable period of time in an organization. It often refers to mainframe and minicomputer applications.
application (kind-of) Google define:
legacy system Those systems in existence and either deployed or under development at the start of a modernization program. All legacy systems will be affected by modernization to a greater or lesser extent. Some systems will become transition systems before they are retired. Other systems will simply be retired as their functions are assumed by modernization systems. Still others will be abandoned when they become obsolete. [Treasury Enterprise Architecture
system (kind-of) www.ichnet.org/glossary.htm
M
management The process of planning, organizing, executing, coordinating, monitoring, forecasting and exercising control.
process (kind-of) www.projectauditors.com/Dictionary/M.html
management system A system intended to provide information needed to make effective decisions on the use of limited resources to improve the efficiency of, and protect the investment in, the nation's existing and future infrastructure at all levels of jurisdictional control. ISTEA originally required the implementation of six management systems: congestion, intermodal, public transportation, pavement, bridges, and safety. These systems are no longer federally mandated, except that the congestion management system is required as part of the conformity determinations in Transportation Management Areas.
() Google define:
market boundary The border around a market area that is being studied.
border (kind-of) https://www.quirks.com/resources/glossary.asp
material flow The progressive movement of material, parts or products toward the completion of a production process between work stations, storage areas, machines, departments, etc.
progressive_movement (kind-of)
Deliverable D10.1
58/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
www.pera.net/Tools/Glossary/ Enterprise_Integration/Glossary.html
message exchange The basic unit of communication between cooperating applications.
basic_unit (kind-of) www.kenamea.com/prd_glossary.html
method A well-defined procedure used to accomplish a specific activity or task. More than one technique may be available for accomplishing a specific activity or task. Selection of the technique should be based on project approach, available tools, etc.
well-defined_procedure (kind-of) www.portal-step.com/90.1Glossary.htm
methodology A set of compatible and coherent methods having different application objectives and having the same fundations model element An element that is an abstraction drawn from the system being modeled.
element (kind-of) Google define:
modelling construct A primitive of a modelling of a modelling language, the syntax and semantics of which must be precisely defined.
Enterprise Modelling and Integration, Frans Vernadat, Chapman & Hall, 1996
modelling framework A collection of modelling principles, methods and tools relevant for a given domain of application.
Enterprise Modelling and Integration, Frans Vernadat, Chapman & Hall, 1996
modelling process The set of activities to be followed for creating one or more models of something (defined by its universe of discourse) for the purpose of representation, communication, analysis, design or synthesis, decision-making, or control.
Enterprise Modelling and Integration, Frans Vernadat, Chapman & Hall, 1996
N
network A communication system made up of computers which are connected. This arrangement allows information transfer from one computer to another in "real time". (See also Local Area Network (LAN); Wide Area Network (WAN)).
communication_system (kind-of)
Deliverable D10.1
59/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
www.lib.purdue.edu/rguides/studentinstruction/glossary.html
network connectivity The physical (wired or wireless) and logical (protocol) connection of a computer network or an individual device to a network, such as the Internet or a LAN.
physical_and_logical_connection (kind-of) www.axis.com/corporate/corp/glossary_general.htm
network management The processes of managing, monitoring, and controlling a communications network. Modern Network Management systems also include the ability to re-configure network elements remotely.
processe (kind-of) www.interoute.com/glossary/
network service An application available on a network, for example, file storage.
application (kind-of) homepages.bw.edu/~kweiss/glossary/n.html
O
object class A set of objects that share a common structure and a common behavior.
object (set-of) Google define:
object model A representation of a set objects and their relationships.
representation (kind-of) www.posc.org/InteropRelease/ Interoperability/InteropIntro/int_appa.html
object request broker Object Request Broker is the middleware that handles the communication details between the objects.
middleware (kind-of) www.theindianprogrammer.com/resources/corba/
object role Defined characteristics in the functionality of an object, e.g. entity or data for objects carrying and providing data, process for objects that carry out algorithms, and presentation for objects that cause information to be displayed for users.
defined_characteristic (kind-of) http://www.posc.org/InteropRelease/Interoperability/InteropIntro/int_appa.html
object technology
Deliverable D10.1
60/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
The set of techniques and tools based on the concept of object.
technique (set-of) www.posc.org/InteropRelease/ Interoperability/InteropIntro/int_appa.html
ontology 1) the specification of a conceptualization, i.e., the set of terms and relationships used in a domain, denoting concepts and objects 2)an explicit formal specification of how to represent the objects, concepts and other entities that are assumed to exist in some area of interest and the relationships that hold among them. The
framework produced such an ontology, which has been further developed and forms the basis of the (DOI) TermSet
explicit_formal_specification (kind-of) http://www-db.stanford.edu/pub/gio/1994/vocabulary.html#Sec2, www.doi.org/handbook_2000/glossary.html
ontology alignment Ontology alignment is the automated resolution of semantic correspondences between the representational elements of heterogenous sytems.
automated_resolution (kind-of) www.atl.external.lmco.com/projects/ontology/
ontology class A class provides an abstraction mechanism for grouping resources with similar
class (kind_of) http://www.w3.org/TR/2004/REC-owl-ref-20040210/
ontology construction Ontology construction is usually a manual, iterative process consisting of at least 3 steps: (1) selection of concepts to be included in the ontology; (2 establishment of properties for the concepts and relationships between concepts in the ontology; (3 maintenance of the
iterative_process (kind-of) mia.ece.uic.edu/~papers/MediaBot/pdf00002.pdf
ontology development, ontology creation, ontology construction ontology development is the definition of the domain and scope of the ontology itself.
definition (kind-of) www.isi.edu/~stefan/SemPGRID/proceedings/9.pdf
ontology engineer the role that is played when a person performs engineering tasks on an ontology
engineer (kind_of) comp
ontology integration ontology integration is the process of building an ontology in one subject reusing one or more ontologies in different subjects
Deliverable D10.1
61/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
process (kind-of) portal.acm.org/ft_gateway.cfm?id=500759&type=pdf&coll=portal&dl=ACM&CFID=11111111&CFT
ontology language Languages to describe ontology contents, such as semantic markup languages, - DAML: DARPA Agent Markup Language - OWL: Web Ontology Language is the successor of
markup_languages_, (kind-of) db-www.aist-nara.ac.jp/dasfaa2003/file/mohania.pdf
ontology specification Ontology specification is the description of the ontology structure using a formal
description (kind-of) www.biu.ac.il/cgkm/hadas.html
ontology structure 1) An ontology structure is a set of concepts, their properties, and relationships among them 2) An ontology structure is a tuple consisting of classes, properties and a hierarchy.
tuple (kind-of) km.aifb.uni-karlsruhe.de/projects/ swap/public/Publications/swap-d3.1.pdf
open source Any software whose code is available for users to look at and modify freely. Linux is the best-known example; others include Apache, the dominant software for servers that dish out corporate web pages.
software (kind-of) Google define:
open systems network A network comprised of equipment that conforms to industry standards of interoperability between different operating systems
network (kind-of) http://www.raidstorage.uk.com/glossary.html
organisational structure Organizational structure is the set of arrangements by which the resources of an organization, human and others, are connected through relationships.
organizational_structure (kind-of) www.ibissoft.se/bpmds04/sprice.pdf
organization chart the management work product consisting of a diagram that documents the composition of the either the development organization or the project team in terms of its component teams and the aggregation relationships between them.
management_work_product (kind-of) www.donald-firesmith.com/Glossary
Deliverable D10.1
62/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
organizational structure The arrangement of activities and possibly lines of responsibility within the entity.
arrangement (kind-of) Google define:
P
platform The hardware and software that makes a computer function.
hardware (kind-of) www.congressonlineproject.org/glossary.html
process A set of related activities that takes one or more kinds of input and creates an output that is of value to the customer. The activities are linked through inputs, outputs, controls and
related_activity (set-of) http://www.eitoolkit.com/Tools/appendix/ei_glossary.html
process analysis Analytical examination of a process for the purpose of documenting and understanding the phenomena which occur in/within the process.
analytical_examination (kind-of) www.pera.net/Tools/Glossary/ Enterprise_Integration/Glossary.html
process description 1) Process description is a detailed characterization of what it does and how to use it. 2) Process description is the high level business view.
highlevel_business_view (kind-of) con-cern.org/modeller/development.html
process design 1) Methodological phase devoted to produce a formal process description. 2) The design of a process, which may be either a management process as required in corporate management, or technical as in commercial or industrial engineering.
design (kind-of) Google define:
process integration 1) Sharing of processes among different functions or organizations 2) Process Integration is the application of methodologies developed for System-oriented and Integrated approaches to industrial process.
application (kind_of) comp
process management
Deliverable D10.1
63/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
A set of functions supporting the definition of inter-related process steps and the management of their execution across a variety of hardware and software platforms
function (set-of) www.andrews.edu/ITS/AS/dw/Andrews/dictionary.html
process model The graphical representation of processes, including a hierarchy of relationships between them. Process models capture the essence of the system being configured and developed. A given process may be used in the delivery of more that one function
graphical_representation (kind-of) www.cio.gov.bc.ca/other/daf/IRM_Glossary.htm
process modelling The task in which process models are developed. Usually both the IT people and the system users from the business work jointly on this task. This ensures that the users perception and needs are appropriately understood and accounted for within the process
task (kind-of) www.cio.gov.bc.ca/other/daf/IRM_Glossary.htm
project management May be used in a project manufacturing environment for production scheduling or in a variety of one off projects throughout all types of organisation.
() www.homercomputer.com.au/ homer_software_guide/glossary.htm
protocol A set of formal rules describing how to transmit data, especially across a network.
formal_rule (set-of) webmaster.info.aol.com/glossary.html
Q
quality management Measuring quality conformance by comparing the actual with a standard and acting on the difference. Software in this category may provide Statistical Process Control functions or be concerned with the documentation issues of quality management.
measuring_quality_conformance (kind-of) www.homercomputer.com.au/ homer_software_guide/glossary.htm
R
real-time electronic data interchange (edi) Data interchange in which transaction sets are sent and received on-line and entire transactions can be completed in a single session. Presently, most EDI transactions are still in the store-and-retrieve or store-and-forward mode. Also known and Interactive EDI.
Deliverable D10.1
64/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
data_interchange (kind-of) http://www.eitoolkit.com/Tools/appendix/ei_glossary.html
reference architecture A reference architecture for a given domain is a generic architecture from which other architectures can be compared or derived.
Enterprise Modelling and Integration, Frans Vernadat, Chapman & Hall, 1996
reference model A (partial) model which can be used as a basis for particular model development or for evaluation of particular models. relational model A database model that organizes data logically in tables.
database_model (kind-of) Google define:
representation The encoding of information for interchange.
encoding (kind-of) www.w3.org/MarkUp/html3/terms.html
representation formalism A graphical representation based on rules of constructions, of analysis, of design. requirement (1) A condition or capability needed by a user to solve a problem or achieve an objective. (2) A condition or capability that must be met or possessed by a system or system component to satisfy a contract, standard, specification, or other formally imposed documents. (3) A documented representation of a condition or capability as in (1) or (2). See: design requirement, functional requirement, implementation requirement, interface requirement, performance requirement, physical requirement.
(IEEE)
resource A resource is an entity (human or technical) whihc can play a role in the realisation of a certain class of tasks, when it is available. Thus, a resource is mainly characterized by two essential facts: (i) it is able to perform a given set of tasks (or jobs), as long as its capacity is not exceeded; (ii) it might not be available all the time.
Enterprise Modelling and Integration, Frans Vernadat, Chapman & Hall, 1996
resource description framework The basic language for writing metadata; a foundation which provides a robust flexible architecture for processing metadata on the Internet. RDF will retain the capability to exchange metadata between application communities, while allowing each community to
Deliverable D10.1
65/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
define and use the metadata that best serves their needs. For more information see
basic_language (kind-of) Google define:
resource management the project management task that ensures that adequate resources are allocated to the
project_management_task (kind-of) www.donald-firesmith.com/Glossary
reusability The ability of a package or subprogram to be used again without modification as a building block in a different program from the one it was originally written for.
ability (kind-of) www.it.bton.ac.uk/staff/je/adacraft/glossary.htm
S
schema integration Schema integration is the process of combining database schemas into a coherent global
process (kind-of) www.cs.uiowa.edu/~rlawrenc/research/Presentations/TRLabs_SI.ppt
search engine A utility capable of returning references to relevant information resources in response to a query.
utility (kind-of) library.csun.edu/mwoodley/dublincoreglossary.html
security services Services provided by a set of security frameworks and performed by means of certain security mechanisms. Such services include, but are not limited to, access control, data confidentiality, and data integrity.
service (kind-of) Google define:
semantic description A semantic description is a description of the meaning of a term.
() http://www-db.stanford.edu/pub/gio/1994/vocabulary.html#Sec2
semantic heterogeneity Semantic heterogeneity is caused by differences in the meaning, interpretation or use of the same or related data.
interpretation (kind-of) ontogeo.ntua.gr/publications/esdi-dublin.pdf
Deliverable D10.1
66/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
semantic relationship, semantic correspondence, semantic link A semantic link is a typed link where the type carries some semantics. That is, it does not simply describe a characteristic of the link, but describes some external relationship or issue. An example of a semantic link would be (any syntax expressing) ""a is-mother-of b"". some other relations like ""b is-child-of a"" may be implied by it.
relation (kind-of) http://en.wikipedia.org/wiki/Semantic_link
semantic web A term coined by Tim Berners-Lee which views the future Web as a web of data, like a global database. The infrastructure of the Semantic Web would allow machines as well as humans to make deductions and organize information. The architectural components include semantics (meaning of the elements), structure (organization of the elements), and syntax (communication). http://www.w3.org/DesignIssues/Semantic.html
()
semantics A semantic definition for a language L, or simply a semantics, consists of two parts: a semantic domain which we denote generically by SL or simply S when there is no confusion, and a semantic mapping from the syntax to the semantic domain denoted by ML or simply
http://www4.in.tum.de/publ/papers/HR00.pdf
service Conceptual functionality provided by an application for a customer directly or indirectly..
module (kind-of) http://www-db.stanford.edu/pub/gio/1994/vocabulary.html
service description A service description is a set of documents that describe the interface to and semantics of a service.
summary (kind-of) http://www.w3.org/TR/ws-gloss/
service provider A person or organization that provides services and subscriptions to users.
company (kind-of) http://www.w3.org/TR/ws-gloss/
simple object access protocol Simple Object Access Protocol is the message protocol that allows Web services to talk.
message_protocol (kind-of) www.nwfusion.com/buzz2001/popup_mainframe.html
software application
Deliverable D10.1
67/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
a program that gives a computer instructions that provide the user with tools to accomplish a task.
program (kind-of) www.cogsci.princeton.edu/cgi-bin/webwn
software architecture the architecture of a software application in terms of its type architecture, package architecture, and concurrency architecture. Contrast with business architecture and system
architecture (kind-of) www.donald-firesmith.com/Glossary/GlossaryS.html
software component Discrete piece of software. Software systems are composed of components.
discrete_piece (kind-of) http://www.posc.org/InteropRelease/Interoperability/InteropIntro/int_appa.html
software development process a project-specific process for delivering a software application or other work products to a customer.
project-specific_process (kind-of) docs.sun.com/db/doc/805-4368/6j450e60h
software engineer A person who designs, builds, tests, debugs, and maintains computer programs.
person (kind-of) Google define:
software product The set of computer programs, procedures, and possibly associated documentation and
computer_program (set-of) Google define:
software requirement a Software Requirement is a software capability that must be met or possessed by a software component in order to satisfy a contract or standard.
software_capability (kind-of) sern.ucalgary.ca/courses/seng/621/W97/johnf/reqeng.htm
software reusability The ability of a package or subprogram to be used again without modification as a building block in a different program from the one it was originally written for.
ability (kind-of) www.it.bton.ac.uk/staff/je/adacraft/glossary.htm
standards body Internationally, the key standards body is the International Organisation for
Deliverable D10.1
68/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
Standardisation (ISO). The second major standards body is the America National Standards Institute (ANSI), whose recommendations are followed throughout North America.
international_organisation (kind-of) www.flexiblelearning.net.au/ interop/standardsdifference.htm
sub-process Logical collection of lower level activities which are grouped to execute a specific business function within a process.
logical_collection (kind-of) http://www.eitoolkit.com/Tools/appendix/ei_glossary.html
support system a network of facilities and people who interact and remain in informal communication for mutual assistance; a network that enables you to live in a certain style.
network (kind-of) Google define:
system a set of interacting components for achieving common objectives system integration The process of connecting systems, devices, and programs together in a common architecture so as to share and exchange data.
process (kind-of) Google define:
systems analysis Work that involves applying analytical processes to the planning, design and implementation of new and improved information systems to meet the business requirements of customer organizations.
work (kind-of) Google define:
systems integration process by which different computing systems and software applications are linked
process (kind-of) Google define:
systems integrator An organization responsible for making diverse IT components (such as COTS) work together and delivering secure and interoperable Enterprise Solutions.
organization (kind-of) http://www.eitoolkit.com/Tools/appendix/ei_glossary.html
T Deliverable D10.1 69/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
target domain A target domain is a semantic domain that is structured and understood metaphorically in terms of another domain.
semantic_domain (kind-of) www.sil.org/linguistics/GlossaryOfLinguisticTerms/WhatIsATargetDomain.htm
technique A well-defined procedure used to accomplish a specific activity or task.
well-defined_procedure (kind-of) www.portal-step.com/90.1Glossary.htm
technology transfer the transfer of knowledge or equipment to enable the manufacture of a product, the application of a process, or the rendering of a service.
transfer (kind-of) Google define:
template Annotated outline of information suitable for the content of a type of definition.
annotated_outile (kind-of) http://www.posc.org/InteropRelease/Interoperability/InteropIntro/int_appa.html
trading partner A trading partner is an organization or individual with whom information or data is accessed or exchanged.
organization (kind-of) http://www.eitoolkit.com/Tools/appendix/ei_glossary.html
U
unified modeling language The Unified Modelling Language is the industry-standard language for specifying, visualising, constructing, and documenting the artefacts of software systems. It simplifies the complex process of software design, making a "blueprint" for construction.
unified_modelling_language (kind-of) www.canri.nsw.gov.au/glossary.html
usage scenario Description of a specific business activity, especially as used to describe the requirements to be met by a system solution; also known as Use Case.
description (kind-of) http://www.posc.org/InteropRelease/Interoperability/InteropIntro/int_appa.html
user Any person who uses a computer or a particular software or hardware system. More
Deliverable D10.1
70/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
specifically, user is sometimes used to refer to the user's computer identification tag, used as an address for electronic mail. Its form depends on individual computer center conventions.
person (kind-of) www.uic.edu/depts/accc/inform/v106t.html
user group A voluntary group of users of a specific computer or software package, who meet to share tips and listen to industry experts.
voluntary_group (kind-of) Google define:
user interface The part of a computer program that displays on the screen for the user to see. Also used to describe how humans interact with what they see on the computer screen. A good user interface makes it easy for users to do what they want to do. See also graphical user
computer_program (part-of) Google define:
user need User need is the principal consideration in developing/executing business strategies for agent-enabled products.
principal_consideration (kind-of) www.hermans.org/agents/h23.htm
user requirement A user requirement is a requirement that a user needs to see implemented in order to be satisfied with the finished product.
requirement (kind-of) www.threesl.com/pages/reference/requirements/definitions.php
V
virtual organization An organization that is not limited by the constraints of legal definition. Virtual organizations may be formed in an informal manner through alliances of independent organizations, or by assembling members of various legally independent organizations into a single virtual organization with specified business goals and powers delegated by their respective legal organizations.
organization (kind-of) Google define:
W
web application A software program that uses HTTP for its core communication protocol and delivers Web-
Deliverable D10.1
71/72
INTEROP
Interoperability Research for Networked Enterprises Applications and Software
based information to the user in the HTML language. Also called a Web-based application.
software_program (kind-of) http://iishelp.web.cern.ch/IISHelp/iis/htm/core/iigloss.htm
web community A Web community is a virtual meeting place for interacting, sharing information and experiences or doing business regardless of organizational, geographical national or cultural boundaries and time zones.
virtual_meeting_place (kind-of) www.teamware.com/communities/
web resource A web resource is a general term used to describe a physical device or software data structure that can only be accessed through the web.
resource (kind_of) comp
web service A Web service is a software system designed to support interoperable machine-to-machine interaction over a network
automated_resource (kind-of) http://www.w3.org/TR/ws-gloss/
web technology Web Technology is the amalgamation of Web related software, tools and research.
amalgamation (kind-of) kakadu.ics.mq.edu.au:8080/SemanticWeb/listParticipantsAction.do?areaCode=2
world wide web consortium Founded in 1994 to develop common standards for the World Wide Web, the W3C is an international industry consortium jointly hosted by the Massachusetts Institute of Technology Laboratory for Computer Science (MIT/LCS) in North America, by the Institut National de Recherche en Informatique et en Automatique (INRIA) in Europe, and by the Keio University Shonan Fujisawa Campus in Asia. Initially, the W3C was established in collaboration with CERN, where the Web originated, with support from DARPA and the European Commission. For more information, see http://www.w3.org/.
international_industry_consortium (kind-of) http://iishelp.web.cern.ch/IISHelp/iis/htm/core/iigloss.htm
Deliverable D10.1
72/72
Close