User Tools

Site Tools


start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
start [2018/02/15 12:29]
127.0.0.1 external edit
start [2019/11/29 12:07] (current)
andries
Line 1: Line 1:
-====== ​Why Gellish ======+====== ​The Gellish ​Communicator software ​====== 
 +The Gellish Communicator application is a [[https://​en.wikipedia.org/​wiki/​Reference_implementation|reference implementation]] for information that is expressed in any of the Gellish family of formalized languages. For guidance on expressing information in Gellish see the [[http://​wiki.gellish.net/​|Gellish Wiki]]. Users of the software can query the language definition and its taxonomic dictionary or supply files with expressions of knowledge, products and processes as well as documents. Such files will be verified on correctness and consistency and the integrated database is available for searching and retrieval of information and knowledge. The software can also be used for consulting the definitions of the formal languages of the family, such as Formal English or Formeel Nederlands and their taxonomic dictionary and ontology.
  
 +The open source software code in stand-alone version using Tkinter is available on [[https://​github.com/​AndriesSHP/​Gellish|GitHub]] together with [[https://​github.com/​AndriesSHP/​Communicator-Web_version-|a web-version]] that uses REMI for interaction with web browsers as user interface. The software is accompanied by data that includes a subset of the source of the language definition and dictionary. The full language definition, taxonomy and ontology ​ and a professional version of the software can be licensed from Gellish.net.
  
-The Gellish family of Formalized Languages, including Formal English, [[:​gellish_nederlands|Formal Dutch]] ​and other formal language variants) are [[http://​www.gellish.net/​index.php/​semantic-modeling.html|semantic modeling languages]] ​for data exchange, data storage ​and data integration in any subject area. It is developed ​for the modeling ​of knowledge, requirements,​ definitions,​ queries as well as information about any individual things and individual processesThe languages are called formal languages, because they are formally defined, so that computers can unambiguously interpret the meaning from the expressions, which is not the case with natural languagesInformation that is expressed in a Gellish formal language is thus computer interpretable ​and application system independent. It can be generated when exporting ​data from systems for data exchanged between systems ​and parties in [[:​gellish_messages|Gellish Messages]] ​and can be imported, interpreted ​and stored in [[:​gellish_databases|Database systems]] and files. Queries can also be expressed in formal languages. The structure of expressions in the language (its syntax) is defined in the native standard Gellish Expression Format, which can be stored in formats such as CSV or JSON. Other formats are also possible.+The Communicator can also be used as  
 +  * A Taxonomic Dictionary-Ontology - by consulting the definitions ​and knowledge models. 
 +  * A Document Management System ​that uses product and process models ​for finding documents 
 +  * A Knowledge Database - by viewing ​and retrieving knowledge and documents about concepts with an option ​for direct export ​of knowledge ​for inclusion in other applications. 
 +  * A Verifier of the quality of expressions. 
 +  * A Database for user defined product ​and process ​data - which enables searching ​and retrieving of information about user defined products ​and processes ​and documents 
  
 +The source code of the basic version is under Open Source license conditions available via [[https://​github.com/​AndriesSHP/​Gellish|GitHub]]. It is written in Python and is a source for code that can be reused and modified by software developers for integration in their own applications. The code facilitates ​
 +  * reading and interpreting Gellish expressions
 +  * searching in Gellish enabled data stores
 +  * generic presentation views (e.g. universal data sheets)
 +  * converting (mapping) data to and from other data structures
 +  * writing Gellish expressions
  
-Definitions of formal languages include electronic ​[[:​gellish_english_dictionary|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 [[:​automated_translation|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. +[[installing_the_communicator|Next]]
- +
- +
-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: [[http://​www.lulu.com/​shop/​andries-van-renssen/​semantic-information-modeling-methodology/​paperback/​product-22457361.html|'​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: [[http://​praxos.ru/​index.php/​Gellish|Russian]] and for Dutch speaking people see [[:​gellish_nederlands|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: +
-    - Home (this page: Introduction) +
-    - [[:​outline_of_gellish|Outline of Gellish]]  +
-    - [[:​basic_principles|Basic principles]]  +
-    - [[:​gellish_modeling_method|Gellish Modeling Method]] ology +
-    - [[:​gellish_english_dictionary|Gellish English Dictionary]] -Taxonomy (Gellish Dictionary) +
-    - [[:​facility_information_models|Facility Information Models]] (FIM), Building Information Models (BIM), etc. +
-    - [[:​product_modeling|Product Modeling]] (Product Design) +
-    - [[:​modeling_of_activities_and_processes|Modeling of activities and processes]]  +
-    - [[:​document_management|Document Management]]  +
-    - [[:​knowledge_modeling_in_gellish|Knowledge modeling in Gellish]]  +
-    - [[:​requirements_models|Requirements Models]]  +
-    - [[:​standard_specification_models|Standard Specification Models]]  +
-    - [[:​correct_gellish_english|Correct Gellish English]]  +
-    - [[:​data_modeling_and_database_design_in_gellish_english|Data Modeling and Database Design in Gellish]]  +
-    - [[:​development_of_gellish_enabled_software|Development of Gellish enabled software]]  +
-    - [[:​gellish_databases|Universal Databases]] (Gellish Expression Tables) +
-    - [[:​dictionary_extension|Dictionary Extension]] (Proper definition of a concept) +
-    - [[:​rules_for_names_of_concepts|Rules for names of concepts]]  +
-    - [[:​gellish_messages|Gellish messages]] for data exchange +
-    - [[:​querying_a_gellish_english_database|Querying Gellish databases]]  +
-    - [[:​gellish_semantic_web|Gellish Semantic Web]]  +
-    - [[:​verification_of_designs|Verification of designs]]  +
-    - [[:​automated_translation|Automatic translation]]  +
-    - [[:​change_management|Change Management]]  +
- +
- +
-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 [[http://​www.lulu.com/​shop/​andries-van-renssen/​taxonomic-dictionary-of-relations/​paperback/​product-22534783.html|Taxonomic Dictionary of Relations]] and in its Dutch equivalent [[http://​www.lulu.com/​shop/​andries-van-renssen/​taxonomisch-woordenboek-van-relaties/​paperback/​product-22534768.html|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: +
- +
- +
-    - Kinds of relations between individual things +
-    - Kinds of relations between an individual thing and a kind of thing +
-    - Kinds of relations between kinds of things +
-    - Kinds of relations between a single thing and a plurality +
-    - 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. +
start.1518694195.txt.gz · Last modified: 2018/02/15 12:29 by 127.0.0.1