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 [2017/11/16 13:53]
andries Formats clarified
start [2018/12/03 12:28] (current)
andries benefits of taxonomy and uids clarified.
Line 2: Line 2:
  
  
-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 processes. The 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 languages. ​Information 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 importedinterpreted ​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.+Information that is expressed in a Gellish formal language is computer interpretable and application system independent. It enables ​data exchange, ​data storagedata 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 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. Furthermore,​ Gellish 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 expressions,​ which 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.
  
-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. 
  
 +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.
  
-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 creation of Gellish expressions is supported by the Gellish **Semantic Information Modeling Methodology**. This is a consistent ​methodology that provides guidance on how to express, store and exchange information,​ knowledge and requirements ​as collections of high quality semantic ​expressions ​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 topics ​such as: A generic ​integrated ​information architecture,​ the creation of taxonomic dictionaries and product catalogs, ​the expression of knowledge (the modeling ​of possibilities), the expression of requirements,​ the creation of information models, such as models of facilities ​and products as well as processes and activities, including also modeling of 2D drawings and the shapes of 3D objects.
  
  
Line 20: 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:
-    - Home (this page: Introduction+    - Home (this page): Why Gellish - A description of the power of Gellish. 
-    - [[:​outline_of_gellish|Outline of Gellish]]  +    - [[:​outline_of_gellish|Outline of Gellish]] ​- An introduction. 
-    - [[:​basic_principles|Basic principles]]  +    - [[:​basic_principles|Writing Gellish]] - How to start. 
-    - [[:​gellish_modeling_method|Gellish ​Modeling ​Method]] ology +    - [[:​gellish_modeling_method|The Semantic ​Modeling ​Methodology]] - Providing guidance on making high quality semantic information models. 
-    - [[:​gellish_english_dictionary|Gellish ​English Dictionary]] -Taxonomy (Gellish ​Dictionary) +    - [[:​gellish_english_dictionary|The Gellish ​taxonomic dictionary]] - The vocabulary of concepts for the Gellish ​languages with definitions,​ relations and arranged as a subtype-supertype hierarchy. 
-    - [[:​facility_information_models|Facility Information Models]] ​(FIM)Building Information Models (BIM), etc+    - [[:​facility_information_models|Integrated information ​(models)]] - An architecture for data integration. For example in Building Information Models (BIM).  
-    - [[:​product_modeling|Product ​Modeling]] (Product Design) +    - [[:​product_modeling|Product ​modeling]] - Guidance on expressing product information during design operation and maintenance. 
-    - [[:​modeling_of_activities_and_processes|Modeling of activities and processes]]  +    - [[:​modeling_of_activities_and_processes|Modeling of activities and processes]] ​- Including activity planning, scheduling and resourcing. 
-    - [[:​document_management|Document ​Management]]  +    - [[:​document_management|Document ​management]] - Guidance on how to integrate documents (files) into product and process information. 
-    - [[:​knowledge_modeling_in_gellish|Knowledge modeling ​in Gellish]]  +    - [[:​knowledge_modeling_in_gellish|Knowledge modeling]] ​- Modeling information about kinds of things and kinds of activities and processes and their reuse in applications. 
-    - [[:​requirements_models|Requirements ​Models]]  +    - [[:​requirements_models|Requirements ​modeling]] - Expression of requirements that are applicable in specific contexts. 
-    - [[:​standard_specification_models|Standard Specification Models]]  +    - [[:​standard_specification_models|Product type modeling]] - Guidance on expressing information about product catalogue items. 
-    - [[:​correct_gellish_english|Correct ​Gellish ​English]]  +    - [[:​correct_gellish_english|Verification of Gellish ​expressions]] - Rules that can be implemented in Gellish enabled software to validate expressions. 
-    - [[:​data_modeling_and_database_design_in_gellish_english|Data Modeling and Database Design in Gellish]]  +    - [[:​data_modeling_and_database_design_in_gellish_english|How to write Gellish ​enabled software]] - Guidance on writing Gellish enabled applications and databases. 
-    - [[:​development_of_gellish_enabled_software|Development ​of Gellish ​enabled ​software]]  +    - [[:​development_of_gellish_enabled_software|Example software - the Gellish Communicator]] - A reference application that demonstrates capabilities ​of Gellish ​and provides example application ​software
-    - [[:​gellish_databases|Universal ​Databases]] (Gellish ​Expression Tables) +    - [[:​gellish_expression_format|The Gellish Expression Format:]] - The Gellish syntax and contextual facts. Typically a tabular format in CSV or JSON. 
-    - [[:​dictionary_extension|Dictionary Extension]] ​(Proper definition ​of a concept) +    - [[:​gellish_databases|Universal ​semantic databases]] - Characteristics of Gellish ​enabled database systems. 
-    - [[:​rules_for_names_of_concepts|Rules for names of concepts]]  +    - [[:​dictionary_extension|Dictionary Extension]] ​- Guidance on proper definitions ​of concepts for public or proprietary extensions of the taxonomic dictionary. 
-    - [[:​gellish_messages|Gellish messages]] for data exchange +    - [[:​rules_for_names_of_concepts|Rules for names of concepts]] ​- Recommended naming conventions for concepts in the taxonomic dictionary. ​ 
-    - [[:​querying_a_gellish_english_database|Querying ​Gellish ​databases]]  +    - [[:​gellish_messages|Gellish messages]] ​- The structure of messages ​for data exchange. 
-    - [[:​gellish_semantic_web|Gellish Semantic Web]]  +    - [[:​querying_a_gellish_english_database|Queries in Gellish]] ​- Using Gellish as a query language for querying Gellish enabled databases. 
-    - [[:​verification_of_designs|Verification of designs]]  +    - [[:​gellish_semantic_web|Gellish Semantic Web]] - Extending the Semantic Web with Gellish as a common language. 
-    - [[:​automated_translation|Automatic translation]]  +    - [[:​verification_of_designs|Verification of designs]] ​- Guidance on how product design information that is expressed in Gellish can be verified automatically using requirements that are also expressed in Gellish. 
-    - [[:​change_management|Change Management]] ​+    - [[:​automated_translation|Automatic translation]] ​- How Gellish expressions can be presented in various languages. ​ 
 +    - [[:​change_management|Change Management]] ​- About keeping track of history and modifications of Gellish expressions.
  
  
 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 ======
  
  
Line 71: Line 74:
  
 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. 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. For different application area's different kinds of relations are applicable.
 +
 +//Continue with:// [[formalized_languages|Formalized languages]].
 +
  
start.1510836800.txt.gz · Last modified: 2017/11/16 13:53 by andries