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 [2013/01/13 11:52] peterbuenk |
outline_of_gellish [2018/10/28 00:55] (current) andries [9. Gellish Documentation] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Outline of Gellish ====== | ||
| + | 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 | ||
| + | * 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 | ||
| + | * information about individual things | ||
| + | * information about documents and their relations to things that are mentioned in their content. | ||
| - | ====== 1. Information Management Method ====== | ||
| + | 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. | ||
| - | The Gellish Information Management Method covers the change management of creating, storing, updating and retrieval of data, documents and knowledge as well as the management of information exchange between various parties and systems and their harmonization and integration. The section about [[:Facility Information Models]] addresses the integration of various models with data and documents about individual objects and the processes that take place in and with those objects. The sections called [[:Document Management]] and [[:Change Management]] describe a method for storing information as well as physical document files in a Gellish database, including the storage of relations between documents and the objects about which they provide information. That part also includes a description of the method to model documents and data sets and information about them, usually called meta-data, as well as the references to physical media, such as electronic files or paper versions. | ||
| - | The Gellish Information Management Method can be applied independent of the question whether the Gellish Modeling Methodology and the Gellish language are used. However, if the latter two are used, then this greatly simplifies the management and integration of information, because of their ability to uniquely identify and manage each individual fact and because of their uniformity in storage structure of all kinds of facts and their use of a common language (common terminology). | + | ====== 1. The Semantic Modeling Methodology ====== |
| - | ====== 2. The Gellish Modeling Method ====== | + | The Semantic Modeling Methodology delivers semantic information models. Such models consist of collections of expressions in which the meaning (the semantics) of the expressions is included in the expressions themselves. Thus semantic models do not require external documentation nor data models, for their interpretation. The language definition is sufficient for an unambiguous interpretation of the expressions. For that purpose, each expression includes a kind of relation that is defined in the formal language definition. |
| + | The modeling methodology provides guidelines for modeling in at least the following five area's: | ||
| - | The Gellish Modeling Method is a powerful semantic modeling method that uses standard Gellish English for modeling in at least the following five area's: | ||
| - | - The creation of computer interpretable [[Proper definition of a concept|Domain Dictionaries-Taxonomies]], in which the defined concepts are arranged in the form of a Taxonomy (subtype - supertype hierarchy) and optionally extended with explicitly modeled definitions in the form of Definition Models. Domain Dictionaries-Taxonomies are typically created as extensions of the general purpose [[:Gellish English Dictionary|Gellish English Dictionary-Taxonomy]]. | + | - The creation of computer interpretable [[:proper_definition_of_a_concept|Taxonomic Dictionaries]] and language defining ontologies, in which the defined concepts are arranged in the form of a subtype - supertype hierarchy, which is also called a taxonomy and which includes defining relations of other kinds between concepts. Definition are basically textual expressions, although they may also be explicitly modeled in the form of Definition Models. Domain taxonomic dictionaries are typically created as extensions (or replacements of parts) of the general purpose [[:gellish_english_dictionary|taxonomic dictionary]]. |
| - | - The creation of knowledge libraries in the form of collections of [[Knowledge modeling in Gellish|Knowledge Models]] for the expression of knowledge about kinds of things in a computer interpretable form. | + | - The creation of collections of expressions of [[:knowledge_modeling_in_gellish|possibilities]] for kinds of things in a computer interpretable and reusable form. |
| - | - The expression of Requirements and Standard Specifications in the form of [[Requirements Models]] for the computer interpretable description of standard products and components and their properties and performance as in product catalogs and in general requirements as expressed in international standards and company best practice guides. | + | - The expression of [[:requirements_models|requirements]] requirements about kinds of things, whereas such requirements are only applicable in a particular context. Such requirements can be used by software to guide designs. And when both the designs as well as the deliverables are documented in the formal language, then the requirements can also be used for automated verification of designs or delivered products against the requirements. |
| - | - The creation of [[Facility Information Models]], including also Building Information Models (BIM's), that contain data and documents about individual objects, including data and documents about designs of objects as well as about realized facilities and their operation and maintenance. This includes also the integration with the Dictionary-Taxonomy (for searching and definitions) and the integration with knowledge and requirements (for reuse and verification of knowledge and requirements). | + | - The creation of [[:facility_information_models|product and process models]], including also models of complete facilities and their documentation, such as Building Information Models (BIM's), etc. Such models may integrated information models that include data as well as documents about individual objects, data and documents about designs of objects as well as about realized facilities and their operation and maintenance. |
| - | - The exchange of messages, including queries, answers and statements between Gellish enabled software, for a [[Gellish Semantic Web]]. | + | - Integrated models include also a taxonomic dictionary and language definition (which enable searching for things of specified kinds as well as definitions of those kinds) and the integration with knowledge and requirements (for reuse and verification of knowledge and requirements). |
| + | - The exchange of messages, including queries, answers and statements between Gellish enabled software, for a [[:gellish_semantic_web|Gellish based semantic data exchange (a real Semantic Web)]]. | ||
| + | ===== 1.1 Comparison with conventional data modeling ===== | ||
| + | The Gellish Modeling Methodology improves conventional data modeling methods in various respects. Conventional data modeling, for example Object-Role Modeling (ORM) or Entity-Relationship (ER) modeling, do not provide a dictionary or taxonomy, nor do they provide standardized relation types for expressing ideas or facts, nor do they provide a standard database design or data structure. As a consequence the various models that result from the application of conventional methods are implemented as different dedicated databases, so that every software supplier created its own database structure and every kind of message in data exchange between systems is designed with its own data structure. Such databases and messages are thus all mutually incompatible. And data that is stored in one database can only be transferred to other data stores by the creation of costly conversion and interfacing software. This problem can be solved by using the Gellish Modeling Methodology that is based on the application of one of the standard Gellish formalized languages and its predefined dictionary of concepts, including its standardized kinds of relations. Gellish enables the storage and exchange of knowledge and information in a standard universal data structure and format in a Gellish Database or in messages, using the generally applicable Gellish expression format. | ||
| - | The Gellish Modeling Method improves conventional data modeling methods in various respects. Conventional data modeling, for example Object-Role Modeling (ORM) or Entity-Relationship (ER) modeling, do not provide a dictionary, nor do they provide standardized relation types to express facts, nor do they provide a standard database design or data structure. As a consequence the various models that result from the application of such methods are implemented as different dedicated databases, so that every supplier created its own database structure. However, such databases are all mutually incompatible, whereas data that is stored in one database can only be transferred to other data stores by the creation of costly conversion and interfacing software. This problem can be solved by using the Gellish Modeling Method that uses the standard Gellish English Dictionary concepts, including its standardized relation types, to create knowledge and information models in a standard universal Gellish Database. When conceptual data models are expressed as knowledge models in Gellish English and when they are stored in a Gellish Database, then they can be used directly to guide the creation of information models about individual objects. Furthermore, that data can also be stored directly in a standard Gellish Database without the need to create a dedicated database. This is enabled by the fact that each Gellish Database consists of one or more of the same universally applicable standard database tables. This general applicability eliminates the need to create dedicated database designs for new applications. As a consequence it is not required anymore to convert the conceptual data models into physical data models to create a database structure. This also opens the possibility to create software that can operate on any Gellish Database or on the combined content of multiple Gellish Databases as well as on any Gellish exchange message. | + | Conceptual data models express knowledge about kinds of things. In conventional methodologies such data models are used to design and create databases with dedicated data structures. When such knowledge is expressed in a formalized language then it can be stored directly in a universal Gellish database, without the need to create dedicated database structures. And then the knowledge can be used directly to guide the creation of information models about individual objects. This is enabled by the fact that each Gellish Database consists of one or more standard database tables of the same structure, because a Gellish database table is universally applicable. This general applicability eliminates the need to create dedicated database designs for new applications. As a consequence it is not required anymore to convert the conceptual data models into physical data models for creating a database structure. This also opens the possibility to create reusable software that can operate on database independent queries on any Gellish Database or on the combined content of multiple Gellish Databases as well as on any Gellish exchange message. |
| - | ====== 3. Gellish ====== | + | ====== 2. The Gellish family ====== |
| - | Gellish is a generally applicable and formal subset of a natural language and a universal, neutral and system independent data structure. Gellish is designed to enable people and computers to express, store, exchange and integrate information, knowledge, requirements, queries and responses in and between computers without the need for costly data conversions and interfaces between systems. | + | Each formal language in the Gellish family of formalized languages is a generally applicable and a formalized subset of a natural language and uses the same universal, neutral and system independent data structure. The family of languages is designed to enable people and computers to express, store, exchange and integrate information, knowledge, requirements, queries and responses as well as the language definition itself without the need for costly data conversions for databases and interfaces between systems. |
| - | ==== 3.1 The Gellish language ==== | + | ==== 2.1 Gellish formal languages ==== |
| + | A Gellish formal language is primarily defined as a structured subset of a natural language, for English the resulting language is called Formal English. However, the formal language definitions are based on the understanding that words and phrases in natural languages are representations of concepts and things that are language independent. Therefore, each concept or thing in a formal language has a language independent unique identifier (UID) that represents the concept or the thing as such in any of the languages of the family. In addition to that, each concept or thing can be denoted by multiple terms ('names'), synonyms, codes and abbreviations in any language and language community. This enables [[:automated_translation|automated translation]] of expressions between different languages. It means that ideas that are expressed in one language do not need to be translated to other languages, as a computer is able to present such an idea in any language for which a formal dictionary is available. \\ This document primarily describes Formal English, but for any other language variant you may replace the word English by the name of that other language. So, Formal English is a formal structured subset of natural English, in the same way as the Dutch variant (Formeel Nederlands) is a subset of the Dutch language. Other formal language variants are in a similar way subsets of other natural languages. | ||
| - | The Gellish language is primarily defined as a structured subset of English, resulting in Gellish English. However, Gellish is based on the understanding that words and phrases in natural languages are representations of concepts and things that are language independent. Therefore, each concept or thing in Gellish has a language independent unique identifier (UID) that represents the concept or the thing as such. In addition to that, each concept or thing can be denoted by multiple terms ('names'), synonyms and abbreviations in any language. This enables [[:Automated Translation|automated translation]] of expressions between different languages. It means that facts that are expressed in one language do not need to be translated to other languages, as a computer is able to present such a fact in any language for which a Gellish Dictionary is available. \\ This document primarily describes Gellish English, but for any other language variant you may replace the word English by the name of that other language. So, Gellish English is a formal structured subset of natural English, in the same way as the Dutch variant (Gellish Nederlands) is a subset of the Dutch language. Other Gellish variants are in a similar way subsets of other natural languages. | + | Formalized languages are intended to facilitate standardization of data in databases and addition of general knowledge for the application of logic. This will improve 'searching and finding' by increasing the possibilities for uniform queries in multiple databases and finding more and better results. Furthermore they are intended to provide a universal data structure for data exchange and for a generally applicable database capability. As a consequence their main advantages over conventional information and knowledge modeling methods with free (undefined) languages are: |
| - | Gellish is intended to facilitate standardization of data in databases, and to provide a universal data structure for a data exchange and a generally applicable database capability. Its main advantages over conventional information and knowledge modeling methods are: | + | * Their data structure is universal and allows for extensions of their content without the need for software changes or database definition changes, whereas conventional data structures are fixed and inflexible. |
| + | * They are openlanguages in which any semantically correct information or knowledge can be expressed, whereas conventional database structures only allow for data for which the system was designed. | ||
| + | * They are defined in an extensive formal taxonomic dictionary of concepts and relation types in the form of a taxonomy and ontology. This eliminates ambiguity of terminology and has as effect that data from different sources can easily be integrated, whereas for conventional databases the concepts for their definition, as well as for their content are usually ad hoc (re)defined and not selected from a standard. | ||
| + | * They are open for extensions and are system independent, whereas most data structures and content standards are closed, application software dependent and proprietary. | ||
| + | * They have automated translation capabilities, uses normal natural language terminology and expressions and do not use a separate meta language for their definition, whereas conventional systems need ad hoc translations and require the use of a separate meta language for their definition and are usually expressed in 'programmers language'. | ||
| - | * Its data structure is universal and flexible and can be extended without software changes or database definition changes, whereas conventional data structures are fixed and inflexible. | + | The Gellish formalized languages are based on the principle that knowledge and information can be expressed as a collection of relations, whereas each related thing plays its own role in a relation. Each relation has the same structure, being two or more Relation - Role - Player combinations. Groups of elementary relations can be combined into expressions (small sentences) that are basically the same in any natural language. Each such expression has in essence the form of an object-relation-object (ORO) structure, whereas in most cases the roles can remain implicit. Examples of the core of such formal language expressions (without UID's and contextual facts) are the knowledge: |
| - | * It is an open language in which any semantically correct information or knowledge can be expressed, whereas conventional database structures only allow for data for which the system was designed. | + | |
| - | * It has an extensive standard 'smart' dictionary of concepts and relation types in the form of a taxonomy / ontology, which eliminates ambiguity and causes that data from different sources can easily be integrated, whereas conventional databases usually don't use standard concepts for their definition, nor for their content. | + | |
| - | * It is open, system independent and free available under [[http://www.opensource.org_docs_osd|Open Source]] conditions, whereas most data structures and content standards are closed, application software dependent and proprietary. | + | |
| - | * It has automated translation capabilities, uses normal English terms and expressions and does not use a separate meta language for its definition, whereas conventional systems need ad hoc translations and require the use of a separate meta language for their definition and are usually expressed in 'programmers language'. | + | |
| - | Gellish is based on the principle that knowledge and information can be regarded as a collection of elementary facts, whereas groups of elementary facts can be expressed as small computer interpretable atomic expressions (small sentences) that are basically the same in any natural language. Each such atomic expression has the form of an object-relationship-object (ORO) structure. Examples of the core of such Gellish English expressions (without UID's and auxiliary facts) are the knowledge: | + | * car <can have as part a> turbine |
| - | + | ||
| - | + | ||
| - | * turbine <can be a part of a> car | + | |
| Line 60: | Line 67: | ||
| - | and the information: | + | and by information about individual things, such as: |
| * the Eiffel tower <is located in> Paris | * the Eiffel tower <is located in> Paris | ||
| + | * John Doe <is performer of> act-1 | ||
| + | * Temperature of John Doe <has on scale a value greater than> 38 degC [on] 29-sep-2017 | ||
| + | Note that the latter expression demonstrates that more complicated expressions include also other components, such as units of measure, dates of validity, and explicit roles. | ||
| - | Such Gellish expressions use standardized phrases for relation types from the Gellish English Dictionary-Taxonomy. They also use standard terms for concepts, which shall be selected from the Gellish English Dictionary-Taxonomy or from a private or public domain extension in the form of Domain Dictionaries-Taxonomies and names of individual things. That standardization of terminology and definitions makes Gellish English a formal language that enables that Gellish expressions can be directly integrated with other Gellish expressions (without a need for conversion) and that the expressions can be interpreted by computers. \\ | + | Formal expressions use standardized phrases for the kinds of relations. Those phrases are selected from the formal taxonomic dictionary. The expressions also use standard terms for kinds of things, which shall be selected also from the taxonomic dictionary or from a private or public domain extension of that dictionary. The names of individual things are introduced and added to an ad hoc dictionary by adding classification relations, as will be discussed later. The standardization of terminology and definitions makes languages into formal languages and that enables that formal expressions can be directly integrated with other formal expressions (without a need for data conversion) and it makes that the expressions can be interpreted by computers. |
| - | The Gellish language is also capable to express questions, answers, confirmations, denials and other communicative intents. Therefore, Gellish does not need a special query language. Gellish Databases can thus be queried via Gellish Queries. This is further described in the section [[:Querying a Gellish English database]]. | + | The Gellish formalized languages are also suitable for expressing questions, answers, confirmations, denials and other communicative intents. Therefore, formal languages do not need special query languages. Databases can thus be queried via queries that are expressed in a formal language. If the queries database is not a Gellish database, then the database should be extended with a standard 'mapper module'. This is further described in the section [[:querying_a_gellish_english_database|Querying databases]]. |
| - | A Gellish Dictionary defines the concepts and terminology of the language, including also phrases that denote relation types. Each concept and each relation type is defined as a subtype of a more general concept or relation type. This means that the concepts and relation types are defined and arranged in a subtype-supertype hierarchy, also called a Taxonomy. This means that the subtypes inherit the definitions of their supertypes. A consequence of the Taxonomy structure is that Gellish expressions can be automatically verified on their consistency and grammatical correctness. | + | A formal taxonomic dictionary defines the concepts and terminology of the language, including also phrases that denote kinds of relations. Each concept and each relation type is defined as a subtype of a more general concept or relation type. This means that the concepts and relation types are defined and arranged in a subtype-supertype hierarchy, also called a Taxonomy. This implies that the subtypes inherit the definitions and relations of their supertypes. A consequence of the Taxonomy structure is that formal expressions can be automatically verified on their consistency and grammatical correctness. |
| - | The hierarchy of relation types is shown in the sheet called 'Gellish English' of the TOPini spreadsheet file of the Gellish English Dictionary. For searching for specific relation types or concepts and for viewing their hierarchy it is recommended to use a Gellish Browser (This Wiki is not suitable to represent that hierarchy, so that the Appendices only present an alphabetic flat list of relation types). | + | The taxonomic dictionary of kinds of relations can be consulted on-line via [[http://www.formalenglish.net/dictionary|the formal English dictionary of relations]]. They are extensively described in the book 'Semantic Information Modeling in a Formal Language'. For searching for specific relation types or concepts and for viewing their hierarchy it is recommended to use a Gellish Browser or Communicator (This Wiki is not suitable to represent the hierarchy of kinds of relations. Therefore the Appendices only present an alphabetic flat list of examples of kinds of relations). |
| - | ==== 3.2 The standard Gellish data structure ==== | + | ==== 2.2 The Gellish syntax, a standard data structure ==== |
| - | Gellish includes a definition of a standard universal data structure for databases and for exchange messages and queries. This means that from an information technology perspective, Gellish can be regarded as a large integrated data model that is flexible and generally applicable and can be implemented in one or more identical database tables. It is flexible, because its application scope and semantic expression capabilities can be extended without a modification of the [[:Data Modeling and Database Design in Gellish English|Gellish data structure]]. It is generally applicable, because it has generally applicable standard relation types and embedded domain specific knowledge from various discipline areas, which relation types and knowledge can be easily extended to other domain areas. \\ This means that Gellish expressions can be stored in universal Gellish Databases and can be exchanged between systems via [[:Gellish messages]] that use a standardized Gellish interface. | + | Gellish includes a definition of a standard universal data structure for databases and for exchange messages and queries. This means that from an information technology perspective, Gellish can be regarded as a large integrated data model that is flexible and generally applicable and can be implemented in one or more identical database tables. It is flexible, because its application scope and semantic expression capabilities can be extended without a modification of the [[:data_modeling_and_database_design_in_gellish_english|Gellish data structure]]. It is generally applicable, because it has generally applicable standard relation types and embedded domain specific knowledge from various discipline areas, which relation types and knowledge can be easily extended to other domain areas. \\ This means that Gellish expressions can be stored in universal Gellish Databases and can be exchanged between systems via [[:gellish_messages|Gellish Messages]] that use a standardized Gellish interface. The universal data structure is defined in the document 'Gellish Syntax and Contextual Facts', available via [[http://www.gellish.net/downloads/cat_view/2-gellish-files-english.html?start=10|the Gellish Download area]]. |
| - | The universal data structure is defined in 'Definition of Universal Databases and Messages', available via [[http://www.gellish.net/downloads/cat_view/2-gellish-files-english.html?start=10|the Gellish Download area]]. | + | |
| - | ====== 4. Gellish English ====== | + | ====== 3. Formal English ====== |
| - | ==== 4.1 Structured formal English ==== | + | ==== 3.1 Structured Formalized English ==== |
| - | Gellish English uses terminology from the 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 uses the English vocabulary that is defined in the electronic Gellish English 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 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. | ||
| - | ==== 4.2 A smart English Dictionary ==== | + | ==== 3.2 The Formal English Dictionary ==== |
| - | The smart [[:Gellish English Dictionary]] is an electronic normal English dictionary that is extended with additional knowledge. All definitions and knowledge in the dictionary is expressed as computer interpretable relationships between the concepts in the dictionary. Most of the relations are specialization relations that specify that the concepts are subtypes of their supertype concepts. This results in a subtype-supertype hierarchy, so that the concepts are arranged in a //taxonomy//. The other additional relations between concepts provide additional knowledge about the defined concepts and thus make it an //ontology//. Because the relations are computer interpretable, the Gellish dictionary becomes a //‘smart dictionary’//. \\ The Root Segment of the Gellish English dictionary includes definitions of the standard relation types. The definitions of those relation types and the definition of the related kinds of roles and kinds of role players form an upper ontology or world ontology. That section defines the semantics of the Gellish expressions. The Root Segment contains the generic concepts that are the top concepts that can be further specialized in the various domain ontologies. The Root Segment therefore acts as the integrator of the Domain Dictionaries. \\ | + | The [[:gellish_english_dictionary|Gellish Formal English Taxonomic Dictionary]] is an electronic ordinary English dictionary that is extended with additional knowledge and more specialized subtypes. All definitions and knowledge in the dictionary is expressed as computer interpretable relationships between the concepts in the dictionary. Most of the relations are specialization relations that specify that the concepts are subtypes of their supertype concepts. This results in a subtype-supertype hierarchy, so that the concepts are arranged in a //taxonomy//. The other additional relations between concepts provide additional knowledge about what is by definition the case for the defined concepts. These additional relations make that the dictionary becomes an //ontology//. Because the relations are computer interpretable, the Gellish dictionary becomes a //‘smart dictionary’// with which computer software apply logic reasoning to find things and derive conclusions. \\ The Root Segment of the Gellish English dictionary includes definitions of the standard relation types. The definitions of those relation types and the definition of the related kinds of roles and kinds of role players form an upper ontology or world ontology. That section defines the semantics of the Gellish expressions. The Root Segment contains the generic concepts that are the top concepts that can be further specialized in the various domain ontologies. The Root Segment therefore acts as the integrator of the Domain Dictionaries. |
| - | The standard Gellish English Dictionary-Taxonomy consists of a root section (or TOPini section) with a number of branch sections, called Domain Dictionaries-Taxonomies. Usage of Gellish requires the use of the TOPini root section and may use one or more standard Gellish Domain Dictionaries-Taxonomies, or may use '//proprietary// Domain Dictionaries. \\ | + | The standard Gellish English Taxonomic Dictionary consists of a root section (or upper ontology section) with a number of branch sections, called Domain Dictionaries. Usage of Gellish requires the use of the root section and may use one or more standard Gellish Domain Dictionaries, or may use '//proprietary// Domain Dictionaries. |
| - | Examples of standard Gellish Domain Dictionaries-Taxonomies are: | + | Examples of standard Gellish Domain Taxonomic Dictionaries are: |
| * **Units of Measure** | * **Units of Measure** | ||
| * **Activities, Events and Processes** | * **Activities, Events and Processes** | ||
| - | * **Physical objects** of various kinds, such as: | + | * **Physical objects** of various kinds, such as: |
| - | * **- Static equipment, civil, process units and piping** | + | * **- Static equipment, buildings, furniture, civil items, process units and piping** |
| - | * **- Electrical and Instrumentation, Control and Valves** | + | * **- Electrical and Instrumentation and Control equipment** |
| * **- Rotating equipment, Transport equipment and Solids Handling** | * **- Rotating equipment, Transport equipment and Solids Handling** | ||
| * **Aspects, Properties, Qualities and Roles** | * **Aspects, Properties, Qualities and Roles** | ||
| - | * **Materials of constructions, Fluids and Waves** | + | * **Materials of constructions, Chemicals and Waves** |
| * **Documents and Identification, Symbols and Annotation** | * **Documents and Identification, Symbols and Annotation** | ||
| - | * **Geographic objects, Lifeforms and Organizations** | + | * **Geographic objects, Organisms and Organizations** |
| - | * **Mathematics, Geometry and Shapes** | + | * **Mathematics, Geometry and Shapes** |
| - | Users and Organizations are invited to propose extensions of the Root Segment or the standard Domain Dictionaries-Taxonomies and are invited to develop Domain Dictionaries-Taxonomies for their own application domain and to propose to certify their Domain Dictionaries-Taxonomies as approved proprietary or public **Gellish Domain Dictionary-Taxonomy**. | + | |
| + | Users and Organizations are invited to propose extensions of the Root Section or the standard Domain Dictionaries and are invited to develop Domain Dictionaries for their own application domain and to propose to certify their Domain Dictionaries as approved proprietary or public **Gellish Domain Dictionary**. | ||
| - | ====== 5. Usage of Gellish ====== | ||
| + | ====== 4. Usage of formal languages ====== | ||
| - | There are basically four kinds of usage of Gellish: | ||
| - | - Usage as a Dictionary and/or Taxonomy | + | There are basically four kinds of usage of formal languages: |
| - | - Usage as a Language e.g. to create dictionaries or taxonomies, to model knowledge, to specify requirements, to describe designs or real world facilities or to manage information. | + | |
| - | - Usage as a Data Modeling language | + | |
| - | - Usage as a Query language | + | |
| - | ==== 5.1 Usage as a Dictionary ==== | + | - Usage as an Information Modeling language for data exchange and/or data storage |
| + | - Usage as a Query language | ||
| + | - Usage as a Dictionary and/or Taxonomy | ||
| + | - Usage as a Language e.g. for creating dictionaries or taxonomies, for modelling knowledge, specifying requirements, describing designs or real world objects or facilities or for managing information and documents. | ||
| - | Gellish English is defined in the electronic [[:Gellish English Dictionary]]. That dictionary can be used either in stand-alone mode via Gellish Dictionary browser software (such as the [[http://www.steplib.com|Gellish Browser]]) or by incorporating the dictionary (or a subset of it) as standard reference data in one or more application systems. | + | |
| + | ==== 4.1 Usage as a formal Language ==== | ||
| + | |||
| + | |||
| + | Gellish as a language can be used for creating Gellish based databases or data exchange between systems. This implies that the language enables the expression of various kinds of information. For example the language enables describing various kinds of information about: | ||
| + | |||
| + | |||
| + | * Individual objects, their components, properties and behavior. | ||
| + | * Designs of facilities or real world structures or to manage information about various kinds of facilities. For example Facility Information Models or a Building Information Models (BIM). | ||
| + | * Business processes, transactions and other activities, such as processes that are typically described by graphical methods such as IDEF0 and DEMO. | ||
| + | * Physical or chemical processes, including fluid or solid product streams. | ||
| + | * Definitions of concepts and relations between concepts; typically for creating smart Dictionaries, Taxonomies and Ontologies. | ||
| + | * Knowledge that can be re-used; typically for guiding designs or for verification of designs. | ||
| + | * Requirements for kinds of products or standard specifications of manufacturer's models, such as those included in product catalogs. | ||
| + | * Etc. | ||
| + | |||
| + | |||
| + | Usage of the Gellish English language for the modeling of information and knowledge implies that individual things are classified by concepts from the Gellish Dictionary, and in addition to that it implies that standard relation types are used for making expressions in Formal English. The integration of the various kinds of expressions in one integrated model is illustrated by the '**Information Architecture**' in the following figure. \\ {{ ::information_architecture.png?nolink&600 |}} | ||
| + | |||
| + | |||
| + | The figure illustrates the architecture of an Integrated Information Model and its main sections. \\ | ||
| + | 1. The left hand section of the figure illustrates the core of a model of a facility. In this example the facility is a real life LNG plant in which natural gas is liquefied and which is modeled in Gellish Formal English. The facility is decomposed in components, using part-whole relations. The components have properties and are related to each other by various kinds of relation. Furthermore the components are related to processes and activities by relations that specify the way in which the components are involved in the activities or processes. \\ | ||
| + | 2. Many pieces of equipment and other facility components are related to one or more documents. The document related expressions form a collection of document models, being the second section of the Integrated Information Model. This integration of facility data and their relations to documents enable building powerful //[[:querying_a_gellish_english_database|search engines]] // for integrated product life cycle and document management systems (PLM's and EDMS's). It enables using the structure of the facility model to find documents about the facility components and vice versa: using documents as a user interface for finding data about the objects that are represented on the documents. \\ | ||
| + | 3. Each element of the facility model and each document is also related by one or more classification relations to concepts (kinds of things or 'classes') in the Gellish Dictionary, which is the section on the right hand side of the figure. These classification relations enable the concepts in the taxonomic dictionary and the relations between those concepts for finding documents and requirements that are applicable for components that are classified by such a concept. For example, searching for information about the concept 'compressor' in the dictionary will find all compressors, including things that are classified by subtypes of compressor, as well as requirements about compressors, documents about compressors, etc. \\ | ||
| + | 4. Finally, the third section from the left in the figure illustrates the expression of knowledge about possibilities and requirements about kinds of things, in the form of relations of various kinds between concepts in the Gellish dictionary. Note: the fact that a possibility or a requirement is about a kind in the dictionary implies that the possibility or requirement is applicable to all individual things in the product and process model on the left hand side that are related to that kind via a classification relation. | ||
| + | |||
| + | |||
| + | The figure also illustrates that Gellish expressions can be seen as one integrated network of binary relations. If software selects one node in the network, it can easily retrieve all directly related objects and thus collect (and present) all available information about that node object. | ||
| + | |||
| + | |||
| + | Altogether the figure illustrates the following ways of using the Gellish language: | ||
| + | |||
| + | |||
| + | * For [[:knowledge_modeling_in_gellish|expressing knowledge]] for its storage, retrieval and for exchanging knowledge between application systems. | ||
| + | * For [[:requirements_models|expressing requirements]] and [[:standard_specification_models|standard specifications]] for types of products and processes such as in product catalogs and for the required delivery of data and documents. | ||
| + | * For modeling individual facilities and their components and products ([[:product_modeling|product modeling or product design]]) for the storage, retrieval and exchange of data and documents about them. | ||
| + | * For computer augmented [[:verification_of_designs|verification of designs]] or for verifying information about real world objects against requirements and specifications. | ||
| + | * For creating [[:facility_information_models|Intergrated Information Models]] or for expressing business transactions, measured data, or any other information about facilities and their components as an integration of information from various sources in central or decentralized distributed databases. | ||
| + | |||
| + | |||
| + | Depending on these kinds of usage a different subset of standard Gellish relation types is applicable. \\ For example: \\ Requirements specifications mainly use kinds of relations that specify <shall be ...> or <shall have...> relations between kinds of things, which are applicable for specifying relations that shall be the case. Definitions are expressed by relations that specify that something is by definition the case. Therefore, expressions in definition models include relation type phrases that begin with <has by definition…> or <is by definition…>. For example, in Gellish we can specify that a pump shall have a shaft and shall have a volumetric capacity as follows: | ||
| + | |||
| + | |||
| + | ^Name of left hand object ^Name of relation type ^Name of right hand object | | ||
| + | |pump |shall have as part a | shaft | | ||
| + | |pump |shall have as aspect a | capacity (volume flow rate) | | ||
| + | |||
| + | |||
| + | Product descriptions and operational facilities mainly use kinds of relations that specify relations between individual things and classification relations that specify that an individual thing is related to a kind of thing (a class). These kinds of relations typically start with 'is a…' or 'has a…', whereas the classification relation is expressed by the phrase 'is classified as a'. For example, the information that P-1001 is a pump that has a capacity of 5 dm3/s is described in Gellish as follows: | ||
| + | |||
| + | |||
| + | ^Name of left hand object ^Name of relation type ^Name of right hand object | | ||
| + | |P-1001 |is classified as a |pump | | ||
| + | |P-1001 |has as aspect |capacity of P-1001 | | ||
| + | |capacity of P-1001 |is classified as a |capacity (volume flow rate) | | ||
| + | |capacity of P-1001 |is quantified on scale as |5 | | ||
| + | |||
| + | |||
| + | Note that the relation types and the concepts pump, capacity (volume flow rate), 5 and dm3/s are all standard Gellish English concepts that are selected from the dictionary. The other objects, P-1001 and capacity of P-1001 are private objects that are introduced in the Gellish language by their classification relations. | ||
| + | |||
| + | |||
| + | The available kinds of relations and the various subsets are described in the book 'Semantic Information Modeling in a Formalized Language'. | ||
| + | A more extensive description of an architecture for Integrated Information Models, Building Information Models, etc. is provided in the book 'Semantic Information Modeling Methodology'. | ||
| + | |||
| + | ==== 4.2 Usage as a Query language ==== | ||
| + | |||
| + | |||
| + | Using the Gellish language for [[:querying_a_gellish_english_database|Querying]] a [[:gellish_databases|Gellish Database]] or for communicating in dialogues about transactions in which requests, promises, statements, etc. are expressed, requires that Gellish languages are suitable as a query language or as a business communication language. \\ | ||
| + | There are two main characteristics of a query language: \\ | ||
| + | 1. it requires that questions can be distinguished from statements | ||
| + | 2. it requires the use of (implicit or explicit) unknowns \\ | ||
| + | |||
| + | |||
| + | **Questions:**\\ | ||
| + | An expression of a question usually has a word sequence (grammatical structure) that differs from a statement. For example, in English the question 'is the Eiffel tower located in Paris' has a word sequence that differs from the statement 'the Eiffel tower is located in Paris'. From that word sequence a reader can infer that it is a question or a statement. 'Speech act theory' (John Searle) delivered the insight that the variation in grammatical structure of expressions in languages can be eliminated when a 'communicative intent' is added to an expression. This implies that in a formal language we can use one grammatical structure, that of statements and add an 'intention' to each expression. This implies that the expression 'question: the Eiffel tower is located in Paris' will be interpreted correctly as a question. | ||
| + | For this reason every expression in Gellish has an intention. By default the intention is 'statement'. Questions have as intention 'question', whereas the grammatical structure of statements and questions are the same. Note that this enables computer dialogues by expressing promises, denials, commands, confirmations, etc. by just adding the applicable intention to a Gellish expression. | ||
| + | |||
| + | |||
| + | **Unknowns:**\\ | ||
| + | Expressing conditions for searching unknown objects requires that the unknowns have an identity. Therefore, unknowns are allowed in Gellish questions. They are objects that have any name that does not appear in the dictionary, nor are they ad hoc used in statements. Example of names of unknowns can be just a question mark or terms such as what, which, who or what-1, what-2, etc. Software will allocate UIDs to unknown objects in a range between 1 and 100. | ||
| + | Unknowns can be used in expressions of questions in the same way as names of known things are used. Thus a question will be expressed with an expression model that uses the Gellish languages in the same way as the expression of statements. Search for answers in therefore a matter of pattern recognition: which known objects can be substituted for the unknown and thus satisfy the expressions of the query. | ||
| + | ==== 4.3 Usage as a Dictionary and/or Taxonomy ==== | ||
| + | |||
| + | |||
| + | Formal English is defined in the electronic [[:gellish_english_dictionary|Gellish Formal English Taxonomic Dictionary]]. That dictionary can be used either in stand-alone mode, for example via Gellish Dictionary browser software (such as the [[http://www.steplib.com|Gellish Browser or Communicator]] ) or by incorporating the dictionary (or a subset of it) as standard reference data in one or more application systems. | ||
| Examples of usage of the Gellish English Dictionary are: | Examples of usage of the Gellish English Dictionary are: | ||
| - | - Usage for Data Standardization and common terminology in order to harmonize data in databases in various systems in a company or in an industry. For example, standardize the classification of equipment and their properties, or to standardize document types e.g. in ERP systems, design systems, maintenance systems or document management system. | ||
| - | - Usage for the standardization of keywords in document management systems. | ||
| - | - Usage to improve search engines for retrieval of information by using the Gellish dictionary terms and synonyms (with possible private extensions) as the basis for allocation of keywords and for the keyword search, while using the taxonomy (subtype-supertype hierarchy) of kinds of things (classes) in the Gellish Taxonomy to find also information that is classified by subtypes of terms. | ||
| - | Usage of the Gellish English dictionary may include not only usage of names and textual definitions, but possibly also the usage of the subtype-supertype hierarchy relations and possible also the facts that express what is definition true for a defined concept. | + | - Usage as a classification system for standardization of data and common terminology in order to harmonize data in databases in various systems in a company or in an industry. For example, standardize the classification of equipment and their properties, or to standardize document types e.g. in ERP systems, design systems, maintenance systems or document management system. |
| + | - Usage for the standardization of keywords in document management systems. | ||
| + | - Usage for improving search engines for retrieval of information by using the Gellish dictionary terms and synonyms (with possible private extensions) as the basis for allocation of keywords and for the keyword search, while using the taxonomy (subtype-supertype hierarchy) of kinds of things (classes) in the Taxonomy to find also information that is classified by subtypes of things. | ||
| + | |||
| + | |||
| + | Usage of the Gellish English dictionary may include not only usage of names and textual definitions, but possibly also the usage of the subtype-supertype hierarchy relations and possibly also the facts that express what is by definition the case for the defined concepts. | ||
| - | Application that use only the dictionary may select from the Gellish Dictionary Database only the lines that define concepts and the lines that define synonym names for those concepts. Those lines can be recognized on the relation types which they use, because those lines contain only relation types that are indicated by the following Gellish phrases: | + | Applications that use only the dictionary may select from the Gellish Dictionary Database only the expressions that define concepts and the expressions that define synonym names for those concepts. Those expressions can be recognized on the kinds of relations which they use, because those expressions contain only relation types that are indicated by the following Gellish phrases: |
| - | * is a specialization of - Such a line defines a concept as being a subtype of another concept and provides a textual definition for the concept. | + | * is a kind of (or its synonym 'is a specialization of') - Such an expression defines a concept as being a subtype of another concept and provides a textual definition for the concept. |
| - | * is a qualification of - Such a line defines that a qualitative or quantitative aspect <is a qualification of> a conceptual aspect. For example, red <is a qualification of> color, and ASTM 317 <is a qualification of> stainless steel. | + | * is a qualitative subtype of - Such an expression defines that a qualitative or quantitative aspect <is a qualitative subtype of> a conceptual aspect. For example, red <is a qualitative subtype of> color, and ASTM 317 <is a qualitative subtype of> stainless steel. |
| * is a synonym of | * is a synonym of | ||
| * is an abbreviation of | * is an abbreviation of | ||
| - | These relation types are also some of the standard relation types that are used to extend the Dictionary with the definition of additional concepts. Guidelines for the extension of the Dictionary are given in the [[http://sourceforge.net_project_showfiles.php?group_id=28353|Gellish English Dictionary Extension Manual]]. A summary of those guidelines is provided in the [[:Rules for names of concepts|rules for proper definitions of new concepts]] and [[:Rules for names of concepts|rules for names of concepts]]. \\ If you need only a subset of the concepts in the Dictionary then it is nevertheless recommended to import the whole taxonomy, but to mark only those concepts that will be visible to users. This will simplify to upgrade to newer releases of the Gellish English Dictionary and will support the inclusion of private extensions. | + | These relation types are the main standard relation types that are used to extend the Dictionary with the definition of additional concepts. Guidelines for the extension of the Dictionary are given in the book 'Semantic Information Modeling Methodology. A summary of those guidelines is provided in this wiki on the page [[:rules_for_names_of_concepts|rules for proper definitions of new concepts]] and [[:rules_for_names_of_concepts|rules for names of concepts]]. \\ If you need only a subset of the concepts in the Dictionary then it is nevertheless recommended to import the whole taxonomy, but to mark only those concepts that will be made visible to users. This will simplify the upgrading to newer releases of the Gellish English Dictionary and will support the inclusion of private extensions. |
| - | ==== 5.2 Usage as a Language ==== | + | ==== 4.3 Usage as Data Modeling language ==== |
| - | Using Gellish as a language to create a Gellish Databases includes the usage to describe any or all of: | + | Using the Gellish English language for specification of data models, thus using it as a data modeling language implies specifying what can be the case and what shall be the case in information models in a particular domain (universe of discourse). Note that languages in general do not specify what can be the case, but only specify what are semantically correct expressions. Therefore, for a Gellish based database it is not required to specify on beforehand what data can or may be entered in the database. However in conventional databases the data models constrains what can be expressed and the validation rules of the data models prescribes what shall be expressed once something is entered. |
| + | For this reason Gellish distinguishes between a language defining ontology and possibilities and requirements expressing ontologies. | ||
| + | Modeling possibilities and requirements can be used as constraints in a particular application environment by specifying such an environment as the 'validity context'. For this reason Gellish expressions can be accompanied by a 'validity context'. | ||
| + | Thus by specifying what can or shall be the case in a particular validity context the Gellish language can be used for creating conventional data models. | ||
| + | The creation of data models is the same as modeling possibilities (knowledge) and requirements in Gellish. | ||
| - | * Individual objects, their components, properties and behavior. | + | The resulting [[:data_modeling_and_database_design_in_gellish_english|Gellish English conceptual data models]] are ordinary Gellish information models that are expressed using the kinds of relations that are standardized in Gellish and that use the concepts that are already defined in the Gellish Dictionary or their proprietary extensions where necessary. Data models expressed in Gellish have several advantages over conventional ways to express them. For example, Gellish data models are expressed in a computer interpretable form and can be integrated with other data, they are extensible and they can be directly used by software to guide the creation of data instances, without the need for the design of a physical data model or without the need for modification of the database definition or structure. |
| - | * Designs of facilities or real world structures or to manage information about a facility; typically by creating a Facility Information Model or a Building Information Model (BIM). | + | |
| - | * Business processes, transactions and other activities, such as processes that are typically described by graphical methods such as IDEF0 and DEMO. | + | |
| - | * Physical or chemical processes, including fluid or solid product streams. | + | |
| - | * Definitions of concepts and their relations to other concepts, to create smart Dictionaries, Taxonomies and Ontologies. | + | |
| - | * Knowledge by creating Knowledge Models that can be re-used to guide designs or to verify designs. | + | |
| - | * Requirements for projects or products or standard specifications of kinds of things, such as included in product catalogs. | + | |
| - | * Etc. | + | |
| - | Usage of the Gellish English language for the modeling of information and knowledge implies that individual things are classified by concepts from the Gellish Dictionary, and in addition to that it implies that standard relation types are used for making expressions of the kind Object-Relationtype-Object (ORO). This is illustrated in the figure below. \\ {{:facility_information_model_-_jul2008.gif? |}} | ||
| - | The figure illustrates the architecture of a Facility Information Model and its main sections. The left hand section of the figure illustrates a model of a facility, in this example an LNG plant. The facility is decomposed in components, using part-whole relations. The components have properties and can be related to each other. The components can also be related to processes and activities by relations that indicate the way in which they are involved. Each element in the facility model can also be related to one or more documents in a collection of document models, being the second section of the Facility Information Model. These relations in a Gellish model enable to build powerful //[[:Querying a Gellish English database|search engines]]// or product life cycle and document management systems (PLM's and EDMS's) that can use the structure of the facility model to find documents about the facility components. Each element of the facility model and each document is also related by a classification relation to a concept (a class) in the Gellish Dictionary that is the section on the right hand side of the figure. These relations enable to use the structure of the smart dictionary to find documents and requirements that are applicable for components that are classified by such a concept. Finally, the third section illustrates the expression of requirements about kinds of things, in the form of relations between concepts in the Gellish dictionary. Note that the classification relations determine which requirements are applicable to which objects in the facility model. | + | ====== 5. Universal Databases and Messages ====== |
| - | Alltogether the figure illustrates the following ways to use the full Gellish language: | + | [[:data_modeling_and_database_design_in_gellish_english|Gellish Databases]] are universal semantic databases that enable the storage of virtually any data. They can contain any number of identical database tables. Therefore Gellish Database systems have a universal table structure, which makes them generally applicable and extendable without the need to redefine their data structure (data model). All Gellish databases have as common characteristic that they enable to store any knowledge and information that can be expressed in the Gellish English language. They also have as common characteristic that they have the capability to import and integrate data that are expressed in the form of the content of other [[:gellish_databases|Gellish Expression Tables]]. |
| - | * To [[Knowledge modeling in Gellish|express knowledge]] for its storage, retrieval and for the exchange of knowledge between application systems. | + | [[:gellish_messages|Gellish Messages]] and Queries can be exchanged between computer systems, using a standard data exchange protocol, such as the [[http://www.w3.org_tr_2007_rec-soap12-part0-20070427|SOAP protocol]]. Such a message consists of an envelop, a header and a body. The body is formed by a collection of Gellish expressions, similar to rows in a Gellish Expression Table. When the SOAP protocol is used, the Gellish message or Query is exchanged in [[http://www.w3.org_tr_2006_rec-xml-20060816|XML]] format. Such messages can be sent as a query or as a response in peer to peer networks of Gellish enabled applications to query a central database or a decentralized [[:gellish_databases|distributed database]]. |
| - | * To [[Requirements Models|express requirements]] and [[Standard Specification Models|standard specifications]] for facilities and products and for the required delivery of data and documents. | + | |
| - | * To model facilities and their components and products ([[Product Modeling|product modeling or product design]]) for the storage, retrieval and exchange of data and documents about them, such as in product catalogs. | + | |
| - | * To [[Verification of designs|verify designs]] or to verify observed real world objects against requirements and specifications. | + | |
| - | * To create [[Facility Information Models]] or to express business transactions, measured data, or any other information about facilities and their components as an integration of information from various sources in a central or decentralized distributed database. | + | |
| - | Depending on these kinds of usage a different subset of standard Gellish relation types is applicable. Those subsets of the available relation types are described in the various parts of the Gellish Modeling Method. \\ For example: \\ Requirements specifications mainly use relation types that specify relations between kinds of things that specify facts that shall be the case. Such relation types are typically indicated by phrases that start with 'shall be…' or shall have…'. Definitions describe facts that are by definition the case. Therefore, definition models include relation type phrases that begin with 'has by definition…' or 'is by definition…'. For example, in Gellish we can specify that a pump shall have a shaft and shall have a volumetric capacity as follows: \\ | + | Data integration requires the use of a common language, which includes a common dictionary of concepts and relation types. Therefore it is important that users of Gellish should have the discipline to obey the rules for [[:correct_gellish_english|correct Gellish]]. You should carefully evaluate whether new concepts, especially relation types, are really needed or that existing concepts are already available in the Gellish Dictionary. If you think that a new concept is really required, then you are strongly recommended to provide feedback and to propose your extensions as enhancements of the Gellish Dictionary-Taxonomy. |
| - | ^Name of left hand object^Name of relation type^ | ||
| - | |pump |shall have as part a | | ||
| - | |pump |shall have as aspect a | | ||
| + | ====== 6. Gellish Domain Dictionaries ====== | ||
| - | Product descriptions and operational facilities mainly use relation types that specify relations between individual things and classification relations that specify that an individual thing is related to a kind of thing (a class). These kinds of relation types typically start with 'is a…' or 'has a…', whereas the classification relation is expressed by the phrase 'is classified as a'. For example, the information that P-1001 is a pump that has a capacity of 5 dm3/s is described in Gellish as follows: \\ | ||
| + | Organizations typically use their own terminology in systems and for their proprietary product types. In that way, organization form a '**language community**'. Part of the terminology of such a community will overlap with the world outside the community by using synonyms, and partly the community defined their own concepts, such as product codes for the product types that are manufactured by the organization. This is the main reason why organizations maintain their own proprietary terminology. This section describes how such concepts and terminology relate to Gellish and its taxonomic dictionary.\\ | ||
| + | Using Gellish implies that at least the base ontology section is used, because that defines the core of the Gellish language (its 'Upper Ontology'). In addition to that it may include using part or all of the other Domain Dictionaries of the full Gellish Taxonomic Dictionary, possibly extended with proprietary defined concepts or Domain Taxonomic Dictionaries. For example, parties may wish to use the Civil Engineering Domain Dictionary and the Building and Construction Domain Dictionary (in Dutch or English) and the Units of Measures Domain Dictionary or nothing at all of the remainder of the Gellish English Taxonomic Dictionary.\\ When parties want to use Gellish and want to develop and use their own (proprietary) [[:proper_definition_of_a_concept|Domain Taxonomic Dictionary]], then they need to understand how to combine their stuff with the concepts that are defined in the Gellish dictionary. \\ The Gellish Modeling Methodology provides guidelines on how to create such Gellish compliant Domain Taxonomic Dictionaries and how to manage the Unique Identifiers (UIDs). | ||
| - | ^Name of left hand object^Name of relation type^Name of right hand object^ | ||
| - | |P-1001 |is classified as a |pump | | ||
| - | |P-1001 |has as aspect |capacity of P-1001 | | ||
| - | |capacity of P-1001 |is classified as a |capacity (volume flow rate) | | ||
| - | |capacity of P-1001 |is quantified on scale as |5 | | ||
| + | The use of proprietary Gellish Domain Dictionaries is convenient and supports adoption of the methodology, because of the familiarity of its users with their own terminology. However, the use of proprietary Gellish Domain Dictionaries has two main risks: | ||
| - | Note that the relation types and the concepts pump, capacity (volume flow rate), 5 and dm3/s are all standard Gellish English concepts that are selected from the dictionary. The other objects, P-1001 and capacity of P-1001 are private objects that are introduced in the Gellish language by their classification relations. | ||
| - | A more extensive description of an architecture for Facility Information Models, Building Information Models, etc. is provided in the document [[http://shop.gellish.net/shop.html?page=shop.browse&category_id=2|Gellish Modeling Methodology, Part 1 - Architecture]]. | + | - Your Domain Dictionary may overlap or conflict with other Gellish Domain Dictionaries. This means that data integration may still be a problem when you want to communicate with systems that are not familiar with your Domain Dictionary. So you cannot simply integrate data from other parties that use a different Domain Dictionary. |
| + | - Your Domain Dictionary may contain concepts that are not subtypes of the concepts in the Gellish base ontology section. This is against one of the basic Gellish rules and causes that the correctness and consistency of the Gellish expressions cannot be verified. | ||
| - | ==== 5.3 Usage as Data Modeling language ==== | + | For example, not using the full Gellish Taxonomic Dictionary means that the power of the Gellish taxonomy is not utilized and thus that nothing is used of the benefits of the inheritance capabilities, searching on subtypes, application of logic reasoning and semantic verification possibilities), the synonyms, the definitions and the distinctions between objects and their roles, the standard units of measure and their conversions, etc. |
| - | Using the Gellish English language to specify data models, thus using it as a data modeling language. This will result in [[:Data Modeling and Database Design in Gellish English|Gellish English conceptual data models]], being data models that are expressed using the relation types that are standardized in Gellish and that use the concepts that are already defined in the Gellish Dictionary or their proprietary extending where necessary. Data models expressed in Gellish have several advantages, such as that they are documented in a database table, they are extensible and they can be directly used by software to guide the creation of data instances, without the need for the design of a physical data model. | + | To avoid these risks of overlap or isolation it is recommended to define **mapping tables** that include (only) synonym relations between your own terminology and equivalent names in the Gellish Dictionary that denote the same concepts. This is especially useful when your domain dictionary or the terminology in one or more of your systems is a subset (or translation) of the standard Gellish English Dictionary. \\ Synonyms can be defined as part of an ordinary collection of Gellish expressions that is part of your Domain Dictionary. Such a synonym table should use your Domain name as 'Language Community' and should contain subtypes of the alias kind of relation for relating your names to the names from the standard Gellish Dictionary, whereas your concepts are identified by the UIDs of the concepts in the standard Gellish Dictionary. An example of a synonym table (a mapping table) is: |
| - | ==== 5.4 Usage as a Query language ==== | + | ^Language ^Language community ^Name of left hand object ^Name of relation type ^Name of right hand object | |
| + | |English |SAP |ME_PUM |is a synonym of |pump | | ||
| + | |English |SAP |P |is an abbreviation of |pump | | ||
| + | |German |SAP |Pumpe |is a translation of |pump | | ||
| - | Using the Gellish language to [[:Querying a Gellish English database|Query]] a [[:Gellish Databases|Gellish Database]] or to communicate in dialogs about transactions with requests, promises, statements, etc., thus using Gellish English as a query language or as a business communication language. | + | It is also possible to state that a name in your context <is the same as> the same name in the general context of the standard Gellish Dictionary. \\ You can then add proprietary subtype concepts where necessary. \\ Examples of such Synonym Tables are available for the ISO 15926-4 Domain Dictionary terminology. Several companies developed such synonyms in collections of Gellish expressions. For example, synonym tables were made for terminology in various database implementations, such as equipment types and property types in various SAP implementations for maintenance and inspection. In fact in such cases the synonym expressions indicates which subset of the standard Gellish Dictionary is used in the application. \\ A possible implementation could then even use the full Gellish taxonomic dictionary at the background, while the software only shows the proprietary synonyms of the subset to the users, together with possible proprietary extensions. |
| - | ====== 6. Gellish Databases and Messages ====== | ||
| - | [[:Data Modeling and Database Design in Gellish English|Gellish English Databases]] enable the storage of virtually any data. They can contain any number of identical database tables. Therefore Gellish Database systems have a universal table structure, which makes them generally applicable and extendable without the need to redefine their data structure (data model). All Gellish databases have as common characteristic that they enable to store any knowledge and information that can be expressed in the Gellish English language. They also have as common characteristic that they have the capability to import and integrate data that are expressed in the form of the content of other [[:Gellish Databases|Gellish Database]] tables or the content of Gellish messages. | + | ====== 7. The Gellish syntax and various expression formats ====== |
| - | [[:Gellish messages]] can be exchanged between computer systems, using a standard data exchange protocol, such as the [[http://www.w3.org_tr_2007_rec-soap12-part0-20070427|SOAP protocol]]. Such a message consists of an envelop, a header and a body. The body is formed by a collection of Gellish expressions, similar to rows in a Gellish Database table. When the SOAP protocol is used, the Gellish message is exchanged in [[http://www.w3.org_tr_2006_rec-xml-20060816|XML]] format. Such messages can be sent as a query or as a response in peer to peer networks of Gellish enabled applications to query a central database or a decentralized [[:Gellish Databases|distributed database]]. | + | The structure of Gellish expressions, their syntax, distinguishes between the expression of ideas and the contextual facts about each idea. |
| + | A idea is for example the statement that Berlin is the capital of Germany. Contextual facts about this idea are among others the language of the name of a defined concept such as Berlin is a name in English, the status of the statement as being accepted, the timing since when that is the case, who created the idea, etc.\\ | ||
| - | Data integration requires the use of a common language, which includes a common dictionary of concepts and relation types. Therefore it is important that users of Gellish should have the discipline to obey the rules for [[:Correct Gellish English|correct Gellish]]. You should carefully evaluate whether new concepts, especially relation types, are really needed or that existing concepts are already available in the Gellish Dictionary. If you think that a new concept is really required, then you are strongly recommended to provide feedback and to propose your extensions as enhancements of the [[http://www.opensource.org_docs_definition.php|Open Source]] and public domain Gellish Dictionary-Taxonomy. This is in line with the conditions of the Open Source License that allows you to download and use the Gellish language definition and dictionary. | + | **Expression of an idea**\\ |
| + | An expression of any idea is based on the observation that each idea can be expressed as a collection of one or more binary relations ('basic semantic units'). For practical purposes and keeping close to natural languages, some binary relations are combined into composed expressions as will be clarified later. As a consequence expressions in Gellish consists of a number of elements: | ||
| + | - The idea itself. Note that the idea itself is language independent, because the fact that Berlin is the capitol of Germany is independent of the language in which that idea is expressed. Therefore, each idea is represented throughout all Gellish language variants by a language independent unique identifier (UID) (say 1). Usually ideas don't have a name, but sometimes in user interfaces they are denoted by a phrase. | ||
| + | - The two concepts that related in a binary relation. In the example they are denoted in English by the names Berlin and Germany . Each of them is also represented by its own UID (2 and 3). | ||
| + | - The relation between the two related concepts is classified by a kind of relation. In the example that kind of relation is denoted by the phrase 'is the capitol of', whereas that kind of relation has its own UID (4). Furthermore, it is possible that for the expression of the same idea an inverse phrase is used while inverting the sequence of the related objects. Therefore, the 'phrase type UID' (5) represents the used phrase in a natural language independent way. | ||
| + | - The roles that are played by the related objects are usually implicit, but those roles need to be explicit e.g. when constraints on objects in particular roles are applicable. Those roles have their own UIDs (6 and 7) as well as their own names. In the example, the names are 'capitol' and something like 'possessor of capital'. | ||
| + | - The kind of intention, being 'statement' in the example, also has its own UID (8). | ||
| + | - The units of measure. Sometimes an expression consists of a quantification of a physical property by a number on a scale. In those cases the relation is classified twice. The first classification is by the kind of relation between the property and the number (such as 'is equal to' or 'is greater than') this is covered by the above described kind of relation UID (4). The second classification of the relation is by the method that is used for creating the relation between the property and the number. Such a method is usually called a scale or a unit of measure. For example, a temperature may be quantified by the number 60 using the method invented by Fahrenheit, usually denoted by the scale or unit of measure 'degree F'. Such a scale has its own UID (9).\\ | ||
| - | ====== 7. Gellish Domain Dictionaries ====== | + | This causes that a full expression of any one idea in Gellish consists of maximally 9 UIDs and 8 denoting terms (names). Note that the expression can be compressed to a list of UIDs only after the terms are properly included in a dictionary that connects UIDs to terms in various contets. |
| + | In the Gellish expression format these 16 values are stored in a table of which each column has its own standardized ID. This enables to arrange the columns in any sequence that is convenient for a user and enables to use subsets of columns as and when required.\\ | ||
| + | An example of a tabular form expressions in Gellish Expression format is given in the '[[Example of a road]][[http://www.gellish.net/index.php/downloads/file/4-gellish-english-example-road-v4-xls.html]]' file in the download area of this website. | ||
| - | The use of Gellish requires at least the use of the TOPini section, which defines the core of the Gellish language (its 'Upper Ontology') and may include part or all of the other Domain Dictionaries of the full Gellish Dictionary-Taxonomy, possibly extended with proprietary defined concepts or Domain Dictionaries-Taxonomies. \\ | + | **Contextual facts** |
| - | Parties may wish to develop and use their own (proprietary) [[:Proper definition of a concept|Domain Dictionary-Taxonomy]] and combine that with the concepts that are defined in the upper ontology of Gellish (the TOPini section), and may use one or more standard Gellish English Domain Dictionaries (such as the Units of Measure Domain Dictionary) or nothing at all of the remainder of the Gellish English Dictionary-Taxonomy. \\ | + | For a correct interpretation of the meaning of an expression of an idea it is often important to know contextual facts about the expression of an idea. |
| - | The Gellish Modeling Method provides guidelines on how to create such Gellish compliant Domain Dictionaries-Taxonomies. | + | In Gellish the expression of each idea is therefore accompanied by a number of contextual facts. That is the reason why a Gellish Database table consists of a large number of standard columns, although the expression of a main fact basically only requires 3 columns. |
| - | The use of proprietary Gellish Domain Dictionaries is convenient and fast, because of the familiarity of its users with their own dictionary. However, the use of proprietary Gellish Domain Dictionaries has two main risks: \\ | + | The idea as well as all those contextual facts can be expressed on one row in the Gellish expression format. However, they can also be stored differently, for example in a triple store or in an object oriented database. |
| - | - Your Domain Dictionary may overlap or conflict with other Gellish Domain Dictionaries. This means that data integration may still be a problem when you want to communicate with systems that are not familiar with your Domain Dictionary. So you cannot simply integrate data from other parties that use a different Domain Dictionary. \\ | + | |
| - | - Your Domain Dictionary may contain concepts that are not subtypes of the concepts in the Gellish Root section (TOPini). This is against one of the basic Gellish rules and causes that the correctness and consistency of the Gellish expressions cannot be verified. \\ | + | |
| - | For example, not using the full Gellish Dictionary-Taxonomy means that the power of the Gellish taxonomy is not utilized and thus that the benefits of the inheritance capabilities, searching on subtypes and semantic verification possibilities), the synonyms, the definitions and the distinctions between objects and their roles, the standard units of measure and their conversions, etc. are not used. | + | |
| - | To avoid these risks of overlap or isolation it is recommended define synonym relations between your own terminology and equivalent names in the Gellish Dictionary that denote the same concepts. This is especially useful when your domain dictionary or the terminology in one or more of your systems is a subset (or translation) of the standard Gellish English Dictionary. \\ | ||
| - | Synonyms can be defined as part of an ordinary Gellish Database table that is part of your Domain Dictionary. Such a Synonym Table should use your Domain name as 'Language Community' and should contain synonym relation types that relate your names to the names from the standard Gellish Dictionary, whereas your concepts are identified by the UID's of the concepts in the standard Gellish Dictionary. For example: \\ | ||
| - | ^Language ^Language community ^Name of left hand object^Name of relation type^Name of right hand object^ | ||
| - | |English | SAP | ME_PUM |is a synonym of |pump | | ||
| - | |English | SAP | P |is an abbreviation of | pump | | ||
| - | |German| SAP |Pumpe |is a translation of | pump | | ||
| - | It is also possible to state that a name in your context <is the same as> the same name in the general context of the standard Gellish Dictionary. \\ | + | Users may wish to ignore some or all of the contextual facts (or even some columns for the expression of the basic semantic units) in their implementation. For that reason standard subsets of columns are defined. |
| - | You can then add proprietary subtype concepts where necessary. \\ | + | The smallest subset is a triple, which includes a left hand object name, a relation type name and a right hand object name. (In RDF those three components are called subject, property and object). Applications that do not require the implementation of the full set of auxiliary facts can use one of the subsets.\\ |
| - | Examples of such Synonym Tables are available for the ISO 15926-4 Domain Dictionary terminology. Several companies developed such Gellish Synonym Database tables. For example, Synonym tables were made for terminology in various database implementations, such as equipment types and property types in various SAP implementations for maintenance and inspection. In fact in such cases the Synonym table indicates which subset of the standard Gellish Dictionary is used in the application. \\ | + | Each subset table of the Gellish Expression format can be represented as a file in Excel xls(s) format, but the table may also be expressed e.g. in CSV or JSON. It may also be expressed in XML or RDF / Notation 3 using an XML Schema definition. A representation of “Gellish in XML” is defined in a free available [[http://www.gellikx.com/2009/ns/2.0/GellishSchema/|XML Schema]]. An XML file with data according to that Schema is recommended to have as file extension GML.\\ |
| - | A possible implementation could then even use the full Gellish dictionary/taxonomy at the background, while the software only shows the proprietary synonyms of the subset to the users, together with possible proprietary extensions. \\ | + | |
| - | Examples of Gellish Domain Dictionaries are the Civil Engineering Domain Dictionary and the Building and Construction Domain Dictionary (in Dutch and English). | + | |
| - | ====== 8. Gellish in XML and RDF / Notation 3 ====== | + | The full Gellish syntax and all contextual facts are described in detail in the document '[[http://www.gellish.net/index.php/downloads/file/1-formal-english-syntax-and-contextual-facts.html|the Gellish Syntax and Contextual Facts]]'. |
| - | In Gellish the expression of each main fact accompanied by a number of auxiliary facts. That is the reason why a Gellish Database table consists of a large number of standard columns, although the expression of a main fact basically only requires 3 columns. | + | ====== 8. Development, maintenance and support ====== |
| - | Auxiliary facts are for example, facts about the used language, the context for naming and validity, the status, the originator, the date of creation and modification of a fact, unique identifiers, etc. All those auxiliary facts can be expressed on one row in a Gellish Database or data exchange file or message. | ||
| - | A representation of “Gellish in XML” is defined in a free available [[http://www.gellikx.com/2009/ns/2.0/GellishSchema/|XML Schema]]. An XML file with data according to that Schema is recommended to have as file extension GML, whereas GMZ stands for “Gellish in XML zipped”. | + | Gellish and the various members of the family of formal languages, such as Formal English and Formal Dutch, are owned, developed and maintained as an International Industry Standard by Gellish.net. Their further development, maintenance and support is managed by Dr. Ir. Andries van Renssen, who previously developed information management standards for Shell and got his PhD on the subject at Delft University of Technology in 2005. Gellish is an improvement and extension of ISO 10303-221 and ISO 15926 and it is compliant with ISO 16354. The Gellish Taxonomic dictionary includes concepts from many international standards, and is developed by van Renssen who guided and managed a number of teams of domain experts from various international companies. Users of Gellish who want to extent the Gellish language or dictionary or who want advise are invited to submit their proposals for additions or request for advise or services to info@Gellish.net. |
| - | Users may wish to ignore some or all of the auxiliary facts in their implementation. For that reason standard subsets of columns are defined as is described in the “The Gellish Database Definition” document (see the Download area of this website). The smallest subset is a triple, which includes a left hand object name, a relation type name and a right hand object name. (In RDF those three components are called subject, property and object). Applications that do not require the implementation of the full set of auxiliary facts can use one of the subsets. Each subset table can be represented in XML or RDF / Notation 3 using a subset of the above XML Schema definition. | ||
| - | ====== 9. Development and maintenance of Gellish ====== | + | ====== 9. Gellish Documentation ====== |
| - | Gellish English is developed and maintained as an International Industry Standard by an Open Source project, headed by Dr. Ir. Andries van Renssen at Shell and at the Delft University of Technology, together with a team of domain experts from several international companies. Users of Gellish who want to extent the Gellish Dictionary of concepts and relation types are invited to submit their proposals for additions to the Gellish English dictionary or another language variant. \\ | ||
| - | Gellish is in use for a large variety of applications, including facility design, plant data integration, database content harmonization, knowledge storage and retrieval, electronic product catalogs, database prototyping and development, etc. \\ | ||
| - | Gellish English is a combination and significant extension and at the same time a simplification of the concepts defined in ISO data model standards ISO 10303-221 (AP221) and ISO 15926, especially part 2, 3 and 4 and includes enhanced concept definitions from many other standards. A project is in progress to transform Gellish into an ISO standard, thus becoming ISO 15926-11. | ||
| - | ======= 10. Gellish Documentation ======= | + | For the description of some core concepts of Gellish see the next paragraph about [[:basic_principles|Basic Principles of Gellish]]. Extensive guidance is provided in the documentation that is described below and can be provided by Gellish.net or by organizations that are authorized providers of support for application of the Gellish Modeling Methodology and the Gellish languages. Explanation of the interpretation by software of Gellish expressions is given on the section [[:development_of_gellish_enabled_software|Developing Gellish enabled software]]. |
| - | For the description of some core concepts of Gellish see the page on [[:basic principles]]. Extensive guidance is provided in the documentation that is described below and can be provided by organizations that support the use of Gellish and the Gellish Modeling Method. Explanation of the interpretation of Gellish expressions and of the standard Gellish relation types is given on the page [[:Development of Gellish enabled software|Developing Gellish enabled software]]. | ||
| The Gellish website ([[http://www.gellish.net/downloads|Downloads]] page) contains a number of documents about Gellish, arranged in three packages: | The Gellish website ([[http://www.gellish.net/downloads|Downloads]] page) contains a number of documents about Gellish, arranged in three packages: | ||
| - | **Package 1: The Gellish English Dictionary-Taxonomy - Gellish EN** | + | |
| + | **Package 1: The Gellish English Dictionary-Taxonomy - Gellish EN** | ||
| This includes | This includes | ||
| - | * The Gellish [[:Gellish English Dictionary|English Dictionary-Taxonomy]] (earlier called STEPlib). The electronic Gellish Dictionary-Taxonomy includes an advanced English Dictionary, that contains explicit relations between the defined concepts. It also includes the Gellish English language definition (its grammar) in the form of a computer interpretable table (the TOPini section). It consists of a number of Gellish Data tables presented in MS Excel files. The tables can be combined in one Gellish Database and imported in any database that is compliant with the Gellish Database definition data storage capabilities. | ||
| - | **Package 2: Examples** | + | |
| + | * The subset of the Gellish [[:gellish_english_dictionary|English Taxonomic Dictionary]]. [The full version is available for licensees only.] The electronic Gellish Taxonomic Dictionary includes an advanced English Dictionary, that contains explicit computer interpretable relations of various kinds between the defined concepts. It also includes the language definition of Gellish Formal English (its grammar) in the form of a computer interpretable table in Gellish Expression format. It consists of a number of Gellish Data tables presented as CSV files in Unicode. The tables together form one Gellish Database. It can be imported in any database that is compliant with the Gellish Database definition data storage capabilities. | ||
| + | |||
| + | |||
| + | **Package 2: Examples** | ||
| This includes | This includes | ||
| - | * An example of a Road (in English and in Dutch). - The example is described in two files: | ||
| - | 1. A document that is intended to provide a first introduction in Gellish, using the example. The document describes some knowledge about a road as well as some information about a particular road. \\ | ||
| - | 2. An Excel file that contains a Gellish Database table with the knowledge and information about the road as is described in the document. The example also illustrates as follows how Gellish enables automated translation. The English version of the database expresses the knowledge and information in Gellish English and includes a translation of the terms (the names of the concepts) to Dutch. That is sufficient for software to present the knowledge and information in Dutch as well, whereas it is not needed to express the facts in Gellish Dutch again. The inverse is the case for the Gellish Dutch version of the database. | ||
| - | * An example of Lubrication System. This [[:Gellish Databases|Gellish Database]] consists of three tables, one with knowledge, one with requirements and one with the design of a part of a particular (individual) lubrication system. | ||
| - | **Package 3. Gellish Documentation** | ||
| - | * A presentation about Gellish. | ||
| - | * Gellish Database Definition - This document defines the standard Gellish Database table and the meaning of the columns in such a table. Such tables can be implemented as database tables or can be exchanged as a computer interpretable files. | ||
| - | * The Gellish Application Manual - An extensive manual on the application of Gellish with many examples. | ||
| - | * A Guide on the extension of Gellish English - This document provides guidance on how to create your own Domain Dictionary or to extent the Gellish English Dictionary with your private terminology and how to raise proposals for the extension of the official Gellish Dictionary. See also the summary of the [[:Proper definition of a concept|rules for a proper definition of a new concept]] and [[:Rules for names of concepts|rules for names of concepts]]. | ||
| - | * Guidelines on the use of Gellish English for [[http://www.bestessays.com.au/doc_essay.php|essay writing]]- This document provides a list of guidelines that provide guidance on the usage of Gellish. It also contains rules to determine whether knowledge or information is expressed in a [[:Correct Gellish English|Gellish compliant]] way. Those rules form the basis for becoming Gellish certified, which gives the right to use the 'Gellish Powered' logo. | ||
| - | * Guidelines for the creation of product catalogs in Gellish. | ||
| - | * A PhD thesis and a summary of that thesis of the originator of Gellish. This provides a description of the fundamentals, the definition, development and application of Gellish as a universal data structure and ontology. See also the book '[[http://www.iospress.nl/loadtop/load.php?isbn=9789040725975|Gellish, a Generic Extensible Ontological Language]]' or its free available [[http://www.library.tudelft.nl/ws/search/publications/search/metadata/index.htm?docname=306185|pdf version]]. | ||
| + | * An example of a road network (in English and in Dutch). - The example is described in two files: | ||
| + | |||
| + | |||
| + | - A document that is intended to provide a first introduction in Gellish, using the example. The document describes how knowledge about a road as well as some information about a particular road is expressed in Gellish. \\ | ||
| + | - An Excel file that contains a Gellish Expression format table with the knowledge and information about the road as is described in the document. The example also illustrates how Gellish enables automated translation of expressions. The English version of the database expresses the knowledge and information in Gellish English and includes a translation of the terms (the names of the concepts) to Dutch. That is sufficient for software to present the knowledge and information in Dutch as well, whereas it is not needed to express the statements in Gellish Dutch again. The inverse is the case for the Gellish Dutch version of the database. | ||
| + | |||
| + | |||
| + | * An example of Lubrication System. This [[:gellish_databases|Gellish Database]] consists of three tables, one with knowledge, one with requirements and one with the design of a part of a particular (individual) lubrication system. | ||
| + | |||
| + | |||
| + | **Package 3. Gellish Documentation** | ||
| + | |||
| + | |||
| + | * A presentation about Gellish. | ||
| + | * Gellish Syntax and Contextual Facts - This document defines the tabular standard Gellish Expression format and the meaning of the columns in such a table. The Gellish Expression format tables can be used as database tables or can be exchanged as a computer interpretable files. | ||
| + | |||
| + | Further documentation can be found in the books: | ||
| + | * Semantic Information Modeling Methodology. This can be used as Gellish Application Manual - An extensive manual on the application of Gellish with many examples. This book also provides guidance on how to extent Gellish English as well as how to create your own Domain Dictionary or to extent the Gellish English Dictionary with your private terminology and how to raise proposals for the extension of the official Taxonomic Dictionary. | ||
| + | |||
| + | * Semantic Information Modeling in a formalized language. This is an explanation of the family of Gellish formal languages and its interpretation. as well as a guide on the extension of Gellish English - | ||
| + | * A 2nd edition of the PhD thesis Delft University of Technology, 2005) and a summary of that thesis of the originator of Gellish. This provides a description of the fundamentals, the definition, development and application of Gellish as a universal data structure and ontology. See also the book 'Formalized Natural Languages', Definition and Application of Universal Information Modeling Languages' (2014). | ||
| + | |||
| + | |||
| + | **//Continue with// ** [[:basic_principles|How to start writing Gellish]] | ||
| + | \\ | ||
| - | **//Continue with//** [[:basic principles|Basic principles]] | ||
outline_of_gellish.1358074364.txt.gz · Last modified: 2017/11/15 11:05 (external edit)
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
