User Tools

Site Tools


start

1. Introduction

Data exchange between systems and integration of data from various sources usually requires the dedicated design of interface messages and the costly development of data conversion software for each interface between systems. This is caused by the fact that each system design is based on its own dedicated 'data model' or 'ontology'. Furthermore, the data that is or can be entered into systems, as 'instances' of the data models, is usually not standardized across systems of different organizations, but usually also not within companies. Thus each system uses its own data structure, terminology and corresponding software for storing its data and for searching and reporting. The root cause is the lack of availability of a common formalized language for data storage and data exchange. Therefore it is common practice that software developers are educated in developing their own data models or ontologies and thus inventing their own dedicated 'sub-language'. As a consequence systems data exchange and data integration is a continuing problem area. A common language for data exchange would enable writing only one import and export module that can read and write any message in the common language and would thus enable interoperability of systems. This long standing issue can now be solved by applying a formal language from the Gellish family of formalized languages as a common language.

For example, nowadays product catalogues are usually made searchable via the websites of the suppliers. However, it is currently not possible to express one universal query that searches for product types in systems of multiple suppliers and that the results are combined in one report. Neither is it possible to integrate selected resulting models directly in someones own models, such as in designs. Such data integration also needs a formalized common language.
Universal search, combined reporting and direct integration of product type models in users models, becomes possible by modeling product types in a Gellish formal language. This is demonstrated as documented in the description of the Gellish Communicator software.

2. Table of content of this Wiki

This Wiki provides information and guidance on

  • the definition of the Gellish family of formalized languages,
  • the application of formal languages for creating databases, queries and messages,
  • the semantic information modeling methodology that uses those formalized languages.

We recommend to study formalized languages in general and Formal English in particular by following the wiki pages in the sequence below. The language and application methodology can be studies more in depth by reading the books: 'Semantic Information Modeling in Formalized Languages' and 'Semantic Information Modeling Methodology'. The first book describes the language definition, the second book describes its application.

Table of content of this Wiki:

  1. Home (this page: Introduction)
  2. Integrated Information Models, Building Information Models (BIM), etc.
  3. Universal Databases (Gellish Expression format)
  4. Dictionary Extension (Proper definitions of concepts)

Note that each Wiki page has its own table of content about the details on that page.

start.txt · Last modified: 2017/10/10 13:34 by andries