outline_of_gellish
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
outline_of_gellish [2017/11/15 11:15] 127.0.0.1 external edit |
outline_of_gellish [2018/10/28 00:55] (current) andries [9. Gellish Documentation] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Architecture ====== | + | ====== Outline of Gellish ====== |
| - | The Gellish semantic modeling methodology is based on an integrated information architecture, which means that it is about the integration of | + | The Gellish semantic modeling methodology is based on an integrated information architecture, which means that it covers the integration of |
| * a taxonomy and ontology that contains a definition of the Gellish formal language with its syntax and semantics about concepts and kinds of relations and expressions | * a taxonomy and ontology that contains a definition of the Gellish formal language with its syntax and semantics about concepts and kinds of relations and expressions | ||
| * dictionaries with natural language specific terminology and textual definitions which define natural language specific variants of the Gellish family of formalized languages | * dictionaries with natural language specific terminology and textual definitions which define natural language specific variants of the Gellish family of formalized languages | ||
| * knowledge about about kinds of things | * knowledge about about kinds of things | ||
| * information about individual things | * information about individual things | ||
| - | * information about documents and their relations to things that appear in their content. | + | * information about documents and their relations to things that are mentioned in their content. |
| - | Thus, the vocabulary of each formal language in the family is defined in a taxonomic dictionary (which is also a language defining ontology). In that dictionary the defined concepts are related to each other such that they define a natural language independent taxonomy and ontology. The dictionary also includes natural language specific terminology and textual definitions for the concepts. This makes that the taxonomic dictionaries define formalized natural language specific variants of the Gellish family. All dictionaries in the family use the same unique identifiers (UIDs) to represent the defined concepts. This enables that the expressions can be machine transformed into any other formal natural language variant for which a formal dictionary is available. Thus Gellish Formal English, Formal Dutch (Formeel Nederlands), etc. are all formally defined with their own natural language terms, but share the defined concepts. | + | The vocabulary of each formal language in the family is defined in a taxonomic dictionary (which is also a language defining ontology). In that Gellish dictionary the defined concepts are related to each other in such a way that they define a natural language independent taxonomy and ontology. The basic language definition is available free of charge. It can be used in combination with your proprietary vocabulary and dictionary and/or in combination with one or more sections of the Gellish taxonomic dictionary. The Gellish dictionary includes natural language specific terminology and textual definitions for the concepts. This makes that the taxonomic dictionaries define formalized natural language specific variants of the Gellish family. All dictionaries in the family use the same unique identifiers (UIDs) to represent the defined concepts. The option for using prefixes to UIDs allows for using externally defined concepts and identifiers. The use of language independent UIDs for concepts enables that the expressions can be machine transformed into and presented in any other formal natural language variant for which a formal dictionary is available. Thus Gellish Formal English, Formal Dutch (Formeel Nederlands), etc. are all formally defined with their own natural language terms, but share the defined concepts. |
| Line 39: | Line 39: | ||
| - | ==== 2.1 Formal languages ==== | + | ==== 2.1 Gellish formal languages ==== |
| Line 100: | Line 100: | ||
| - | Gellish English uses terminology from natural English, nevertheless Gellish may also be called a [[http://en.wikipedia.org_wiki_formal_language|formal language]] that is computer interpretable, because it limits the language to a formally defined, and computer interpretable subset of a natural language. However, Gellish English does not define its own vocabulary, but select from the English vocabulary as is defined in the electronic Gellish English Taxonomic Dictionary or in user defined Domain Dictionaries. Thus the Gellish English Dictionary provides standardized terminology that can be used as a 'common language' in application systems. Typically it can be used to enhance conventional databases by standardizing their content and thus simplifying data integration and data exchange between systems. For example, the standard terminology and concept definitions can be and is used for standardizing the content of multiple implementations of systems, such as ERP, PLM and EDMS systems, that need to share or exchange data.\\ | + | Gellish Formal English uses terminology from natural English, nevertheless Gellish limits the language to a formally defined, and computer interpretable subset of a natural language. Therefore, it is called a [[http://en.wikipedia.org_wiki_formal_language|formal language]] that is computer interpretable. This does not mean that Gellish English defines its own vocabulary, because its terms are selected from the English vocabulary and included in the electronic Gellish English Taxonomic Dictionary or can be added via user defined Domain Dictionaries. Thus the Gellish English Dictionary provides standardized terminology that can be used as a 'common language' in application systems. Typically it can be used to enhance conventional databases by standardizing their content and thus simplifying data integration and data exchange between systems. For example, the standard terminology and concept definitions can be and is used for standardizing the content of multiple implementations of systems, such as ERP, PLM and EDMS systems, that need to share or exchange data.\\ |
| The formalization implies a simplification, for example through elimination on the need for using plural terms, replacement of the variety of tenses such as past and future tense by the use of explicit times when required, elimination of the variety of word sequences between statements and questions by addition of intentions, etc. | The formalization implies a simplification, for example through elimination on the need for using plural terms, replacement of the variety of tenses such as past and future tense by the use of explicit times when required, elimination of the variety of word sequences between statements and questions by addition of intentions, etc. | ||
| Line 392: | Line 392: | ||
| - | **//Continue with// ** [[:basic_principles|Basic principles]] | + | **//Continue with// ** [[:basic_principles|How to start writing Gellish]] |
| \\ | \\ | ||
outline_of_gellish.1510740946.txt.gz ยท Last modified: 2017/11/15 11:15 by 127.0.0.1
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
