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
Last revision Both sides next revision
start [2018/10/31 15:44]
andries [Why Gellish]
start [2018/11/17 20:33]
andries [2. Categories of kinds of relations (relation types)]
Line 2: Line 2:
  
  
-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.\\+Information that is expressed in a Gellish formal language is computer interpretable and application system independent. It enables ​data exchange, data storage, ​data integration and systems interoperability without the need for data model harmonization or data conversion.\\
  
-The Gellish family of Formalized Languages, including Formal English, [[:​gellish_nederlands|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. An advantage of a //​semantic//​ modeling language is that it is a formalized language in which the expressions include the information that is required to interpret the meaning of the expressions,​ thus it does not need separate data model or other documentation for its interpretation. ​Furthermore, ​Gellish allows for storing any kind of information, including ​the expression of knowledge, requirements,​ definitions,​ queries as well as information about any individual things ​and processes. The value of being a //formal// language is that it is formally defined, so that computers can unambiguously interpret the meaning from the expressions which is not (yet) possible with natural language expressions. Gellish expressions can be generated by Gellish enabled software when exporting data for data exchange between systems and parties as [[:​gellish_messages|messages in Gellish]] or by using a Gellish enabled editor. It can also be imported, interpreted and stored in [[:​gellish_databases|database systems]] and files for further processing as is demonstrated in the Gellish Communicator reference application. 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|Gellish Expression Format]], which can be stored in formats such as CSV or JSON. Other formats are also possible.+An advantage of the Gellish family of formalized languages is that there is one way of expressing information in any subject area and for any available natural language, including Formal English, [[:​gellish_nederlands|Formal Dutch]] and other formal language variants. Furthermore Gellish is a semantic modeling ​language. An advantage of being a //​semantic//​ modeling language is that the expressions include the information that is required to interpret the meaning of the expressions,​ thus Gellish expressions do not need separate data models ​or other documentation for its interpretation. ​That Gellish allows for storing any kind of information ​includes ​the expression of knowledge, requirements,​ definitions,​ queries as well as information about any individual thingsprocesses ​and documents. The value of being a //formal// language is that it is formally defined, so that computers can unambiguously interpret the meaning from the expressions which is not (yet) possible with natural language expressions. Gellish expressions can be generated by Gellish enabled software when exporting data for data exchange between systems and parties as [[:​gellish_messages|messages in Gellish]] or by using a Gellish enabled editor. It can also be imported, interpreted and stored in [[:​gellish_databases|database systems]] and files for further processing as is demonstrated in the Gellish Communicator reference application. 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|Gellish Expression Format]], which can be stored in formats such as CSV or JSON. Other formats are also possible.
  
  
-Another advantage of Gellish is that its definition includes an electronic [[:​gellish_english_dictionary|Taxonomic Dictionary]] that provides the concepts and terminology of the language, ​together with natural language independent unique ​identifiers ​(UIDsfor those conceptsThose UIDs represent ​the concepts independent of language. As a consequence this enables that information that is expressed in one of the formal languages can be [[:​automated_translation|automatically translated]] by Gellish enabled software from that one formalized language to any other language. 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 or any other language and vice versa. This is possible between any languages for which formal dictionaries are available.+Another advantage of Gellish is that its definition includes an electronic [[:​gellish_english_dictionary|Taxonomic Dictionary]] that provides the concepts and terminology of the language, ​whereas the dictionary is extensible by any user. Each concept in the dictionary is identified by a natural language independent unique ​identifier ​(UID). The use of UIDs for representing ​the concepts independent of language enables that information that is expressed in one of the formal languages can be [[:​automated_translation|automatically translated]] by Gellish enabled software from that one formalized language to any other language. 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 or any other language and vice versa. This is possible between any languages for which formal dictionaries are available.
  
  
Line 22: Line 22:
  
  
-We recommend to study formalized languages ​in general and Formal English in particular ​by following the wiki pages in the sequence ​belowThe 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]]'.+We recommend to study formalized languages by following the wiki pages in the sequence ​that is given in the left hand sidebarmore in-depth treatment of how to express information in Gellish is provided in the book: '​[[Semantic Information Modeling ​Methodology]]. A more in depth treatment of the language definition ​and the content of the upper ontology in the Gellish Taxonomic Dictionary is provided in the book: '​[[Semantic Information Modeling ​in Formalized Languages]]'.
  
 Table of content of this Wiki: Table of content of this Wiki:
Line 54: Line 54:
 Note that each Wiki page has its own table of content about the details on that page. 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) ​======+====== 2. Categories of kinds of relations ======
  
  
start.txt ยท Last modified: 2018/12/03 12:28 by andries