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
start [2018/11/17 20:33]
andries [2. Categories of kinds of relations (relation types)]
start [2018/12/03 12:28] (current)
andries benefits of taxonomy and uids clarified.
Line 4: Line 4:
 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.\\ 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.\\
  
-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 things, processes 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.+An advantage of the Gellish family of formalized languages is that it provides ​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. FurthermoreGellish is a //​semantic//​ modeling language, one of which advantages ​is that the expressions include the information that is required to interpret the meaning of the expressions. This implies that Gellish expressions do not need separate data models or other documentation for their interpretation. ​The various kinds of information ​that can be expressed in Gellish include ​the expression of knowledge, requirements,​ definitions,​ as well as information about any individual things, processes and documents ​and queries about all of that. The value of being a //formal// language is that the language ​is formally defined, so that computer software ​can unambiguously interpret the meaning from the expressionswhich is not (yet) possible with natural language expressions. Gellish expressions can be generated by Gellish enabled software when exporting data from databases ​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 ​implementation. Queries can be expressed in the Gellish formal languages as well, this eliminates the need for separate query languages. The structure of expressions in the Gellish ​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, 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.+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. The power of a //​taxonomic//​ dictionary is that all defined concepts inherit the knowledge about all their supertype concepts. This greatly simplifies searching and retrieval of information and it eliminates the need for re-specifying knowledge for subtypes of defined concepts. Each concept in the dictionary is identified by a natural language independent unique identifier (UID) whereas they are denoted by various terms in the formalized natural languages. The use of UIDs for representing the concepts independent of language ​causes that models and data structures become language independent. 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.
  
  
start.txt ยท Last modified: 2018/12/03 12:28 by andries