User Tools

Site Tools


This is an old revision of the document!

Why Gellish

Information that is expressed in a Gellish formal language is computer interpretable and application system independent. It enables data integration and systems interoperability without the need for data model harmonization or data conversion.
The Gellish family of Formalized Languages, including Formal English, Formal Dutch and other formal language variants, are semantic modeling languages in which information can be expressed for data exchange, data storage and data integration in any subject area. A semantic modeling language is a formalized language in which the expressions include the information that is required to interpret the meaning of the expressions, thus without the need to use a separate data model or other documentation for understanding it. Gellish is developed for the expression of knowledge, requirements, definitions, queries as well as information about any individual things and processes. The Gellish languages are called formal languages, because they are formally defined, so that computers can unambiguously interpret the meaning from the expressions and computers can store the data in structured databases, which is different from natural language expressions. Gellish expressions can be generated by software when exporting data for data exchange between systems and parties as messages in Gellish or by using a Gellish enabled editor. It can also be imported, interpreted and stored in database systems and files for further processing. Queries can be expressed in the Gellish formal languages as well. The structure of expressions in the language (its syntax) is defined in the tabular standard Gellish Expression Format, which can be stored in formats such as CSV or JSON. Other formats are also possible.

Definitions of formal languages include electronic Taxonomic Dictionaries that provide the concepts and terminology of the languages, together with natural language independent unique identifiers (UIDs) for those concepts. Those UIDs represent the concepts independent of language. Information that is expressed in one of the formal languages include those UIDs, which enable that the expressions can be automatically translated by Gellish enabled software from one formal language to another. For example, queries in Formal Dutch, can be executed on databases that are in English, and the queries as well as the results can be presented to users in Dutch and vice versa. This is possible between any languages for which formal dictionaries are available.

The Gellish Semantic Information Modeling Methodology is a methodology that provides guidance on how to express, store and exchange information, knowledge and requirements in high quality semantic models that are unambiguous, consistent and by definition integrated.
The Methodology is documented in the book: 'Semantic Information Modeling Methodology'. The book discusses general principles and guidelines for semantic modeling as well as among others the following topics: A generic information model architecture, the creation of taxonomic dictionaries and product catalogs, modeling knowledge (the creation of knowledge models), requirements modeling, the creation of facility and products as well as processes and activities, including also modeling of 2D drawings and 3D models.

The Gellish Information Management Methodology provides guidance for organizations on a systematic approach for the management, integration and quality control of their information, knowledge and requirements, including data, textual documents, drawings and 3D models.

For information about Gellish in other languages see: Russian and for Dutch speaking people see Gellish Nederlands

1. Table of content of this Wiki

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'.

Table of content of this Wiki:

  1. Home (this page): Why Gellish - A description of the power of Gellish.
  2. Outline of Gellish - An introduction.
  3. Writing Gellish - How to start.
  4. The Semantic Modeling Methodology - Providing guidance on making high quality semantic information models.
  5. The Gellish taxonomic dictionary - The vocabulary of concepts for the Gellish languages with definitions, relations and arranged as a subtype-supertype hierarchy.
  6. Integrated information (models) - An architecture for data integration. For example in Building Information Models (BIM).
  7. Product modeling - Guidance on expressing product information during design operation and maintenance.
  8. Modeling of activities and processes - Including activity planning, scheduling and resourcing.
  9. Document management - Guidance on how to integrate documents (files) into product and process information.
  10. Knowledge modeling - Modeling information about kinds of things and kinds of activities and processes and their reuse in applications.
  11. Requirements modeling - Expression of requirements that are applicable in specific contexts.
  12. Product type modeling - Guidance on expressing information about product catalogue items.
  13. Verification of Gellish expressions - Rules that can be implemented in Gellish enabled software to validate expressions.
  14. How to write Gellish enabled software - Guidance on writing Gellish enabled applications and databases.
  15. Example software - the Gellish Communicator - A reference application that demonstrates capabilities of Gellish and provides example application software.
  16. The Gellish Expression Format: - The Gellish syntax and contextual facts. Typically a tabular format in CSV or JSON.
  17. Universal semantic databases - Characteristics of Gellish enabled database systems.
  18. Dictionary Extension - Guidance on proper definitions of concepts for public or proprietary extensions of the taxonomic dictionary.
  19. Rules for names of concepts - Recommended naming conventions for concepts in the taxonomic dictionary.
  20. Gellish messages - The structure of messages for data exchange.
  21. Queries in Gellish - Using Gellish as a query language for querying Gellish enabled databases.
  22. A Gellish Semantic Web - Extending the Semantic Web with Gellish as a common language.
  23. Verification of designs - Guidance on how product design information that is expressed in Gellish can be verified automatically using requirements that are also expressed in Gellish.
  24. Automatic translation - How Gellish expressions can be presented in various languages.
  25. Change Management - About keeping track of history and modifications of Gellish expressions.

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

2. Categories of kinds of relations (relation types)

The expression power of formal languages is largely determined by the number and variety of kinds of relations that are available in the language definition. The Gellish formalized language definition includes more than 650 standard kinds of relations. They are defined in the upper ontology section of the Taxonomic Dictionary-Ontology. Their textual definitions and subtype-supertype hierarchy is documented in the book Taxonomic Dictionary of Relations and in its Dutch equivalent Taxonomisch Woordenboek van Relaties. The electronic version also includes definitions of the allowed roles and role players for those kinds of relations. Together that defines what are correct formal expressions. The electronic definitions can be licensed, and can then be directly imported in Gellish enabled databases to enable computer interpretation of formal language expressions.

Each relation type is identified by a unique identifier (Gellish UID). Furthermore, each relation type is denoted by at least one base phrase and by at least one inverse phrase. For example, a part-whole relation between two individual things is denoted in Formal English by the phrase <is a part of> and by the inverse phrases <has as part> and <is a whole for>. This means that the same fact can be expressed in either of the two ways. For example, the expression 'A <is a part of> B' has the same meaning as the expression 'B <has as part> A'. A relation type can also be denoted by alternative phrases, such as <is an assembly of>, or by phrases in other languages. Users may even define their own synonym phrases (provided that the UID remains the same) and they can indicate a 'language' and/or a 'language community' in which their phrase is preferred. For example: the Dutch (Nederlands) equivalent of the above example is: <is een deel van>.

The kinds of relations form a taxonomy (subtype-supertype hierarchy of kinds of relations) with the following branches:

  1. Kinds of relations between individual things
  2. Kinds of relations between an individual thing and a kind of thing
  3. Kinds of relations between kinds of things
  4. Kinds of relations between a single thing and a plurality
  5. Kinds of relations between pluralities

The kinds of relations include binary relations as well as higher order relations. Higher order relations include relations for modeling occurrences, such as processes, activities and events and relations to model correlations, such as for physical laws or geometric and mathematical formula.

For different application area's different kinds of relations are applicable.

Continue with: Formalized languages.

start.1540995508.txt.gz · Last modified: 2018/10/31 15:18 by andries