Gellish English (as well as Gellish Dutch and possible another Gellish variant) is a semantic modeling language for the modeling of knowledge, requirements, definitions of kinds of things, as well as information about any individual things. Information that is expressed in Gellish is computer interpretable and application system independent. It can be stored in Gellish Databases or exchanged between systems and parties in Gellish Messages and queried in Gellish Queries.

Gellish English is an Open Source language. It includes an electronic Gellish English Dictionary-Taxonomy (earlier called STEPlib). Information that is expressed in Gellish includes a natural language independent version, which enables that it can be automatically translated by Gellish enabled software from one natural language to another. For example, facts that are expressed in English, can be presented to users in Dutch and vice versa. This is possible between any languages for which a Gellish Dictionary is available.

The Gellish Semantic Modeling Method is a method 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 various parts of the Gellish Modeling Method are:

• Part 1, Architecture. A part that describes an overall architecture for information and its management.
• Part 2, Creation of Domain Dictionaries-Taxonomies.
• Part 3A, Knowledge Modeling (Creation of Ontologies/Knowledge models).
• Part 3B, Requirements Modeling. About the modeling of general requirements, standard specifications and product catalogs.
• Part 4, Facility Information Management. A part that contains an introduction of the Facility Information Management Method.
• Part 5, Modeling of Activities and Processes. A part that specifies how occurrences are modeled, together with the involved parties and objects, their timing and causes.
• Part 6, Creation of Facility and Product Models. This part also covers Building Information Models (BIMs). It focuses on the creation of models with primarily 1D data and their integration with documents.
• Part 7, General Principles and Guidelines. Basics for high quality semantic modeling.
• Part 8, Product Modeling in 1D, 2D and 3D. A part about how to integrate data, schematic drawings and 3D models.
• Part 9, Modeling of Measurements and Observations.

All these parts are available via the webshop.

The <fc blue> Gellish Information Management Method </fc> is a structured method that provides guidance for organizations on a systematic approach for the management of their information and knowledge in the form of documents and data and their quality.

For information about Gellish in other languages see: Russian

Those who want to study Gellish in a systematic way are recommended to study the wiki pages in the sequence below:

1. Home (this page: Introduction)
2. Outline of Gellish
3. Basic principles
4. Gellish Modeling Method
5. Gellish English Dictionary (Gellish Dictionary)
6. Facility Information Models (FIM), Building Information Models (BIM), etc.
7. Product Modeling (Product Design)
8. Modeling of activities and processes
9. Document Management
10. Knowledge modeling in Gellish
11. Requirements Models
12. Standard Specification Models
13. Correct Gellish English
14. Data Modeling and Database Design in Gellish
15. Development of Gellish enabled software
16. Gellish Database (Gellish Table)
17. Dictionary Extension (Proper definition of a concept)
18. Rules for names of concepts
19. Gellish messages
20. Querying a Gellish English database
21. Gellish Semantic Web
22. Verification of designs
23. Automatic translation
24. Information Management
25. Change Management

Appendices: Alphabetic lists of relation types

The expression power of Gellish is largely determined by the more than 650 standard relation types that are listed in the following appendices and that are defined in the upper ontology section (TOPini) of the Gellish English Dictionary-Taxonomy. The TOPini definition table can be directly imported in Gellish enabled software to enable computer interpretation of Gellish expressions.

The appendices show that each relation type is identified by a unique identifier (Gellish UID). Furthermore, each relation type is denoted by a Gellish phrase and by an inverse Gellish phrase. For example, a part-whole relation between two individual things is denoted in Gellish English by the phrase <is a part of> or by the inverse phrase <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 <is a whole for> A'. A relation type can also be denoted by alternative synonym phrases, such as <is part 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: Dutch (Nederlands) <is een deel van>.

This Wiki has a limit on the maximum size of a page. Therefore the list of relation types is presented in several parts with preferred standard phrases and inverse phrases. At the bottom of each partial list you will find a reference to the next part. Standard synonym phrases will be added at a later stage.

1. Appendix A - part 1 List of types of relations between individual things
2. Appendix A - part 1A List of types of relations between individual things (continued)
3. Appendix A - part 2 List of types of relations between an individual thing and a kind of thing
4. Appendix A - part 3 List of types of relations between kinds of things
5. Appendix A - part 3A List of types of relations between kinds of things (continued)
6. Appendix A - part 3B List of types of relations between kinds of things (continued 2)
7. Appendix A - part 4 List of types of relations between a single thing and a plurality

For Dutch speaking people: see also Gellish Nederlands

Note that each Wiki page has its own table of content.