Table of content:
Note that each Wiki page has its own table of content about the details on that page.
Table of content:
Note that each Wiki page has its own table of content about the details on that page.
This is an old revision of the document!
A taxonomy is a hierarchical network of concepts, in which each concept is related to one or more other concepts that are its supertype concepts. The top of the total hierarchy is the concept 'anything'. A domain taxonomy is a taxonomy for a particular domain that has one or more top level concepts that are subtype-concepts of anything. A subtype-supertype relation is also called a specialization-generalization relation and can be denoted by the phrase <is a kind of> or synonymous phrases. Examples of subtype-supertype relations are:
In Gellish, the concepts are represented by language independent unique identifiers that enable that each concepts is denoted by one or more names, synonyms, codes, abbreviations and translations.
A taxonomic dictionary is a dictionary of which each lemma represents a name of a concept, whereas the concepts are explicitly defined and related to each other as in a taxonomy.
An ontology is a taxonomic dictionary that is extended with relations of other kinds between concepts, whereas those relations represent knowledge about the related concepts.
A Gellish taxonomic dictionary, such as the dictionary of Formal English, is an electronic 'smart' dictionary that is also a taxonomy and an ontology. This means that it contains definitions of concepts, each of which is identified by a unique identifier (UID) and can be referenced by one or more 'names' (terms, including synonyms, abbreviations and codes) and includes relations between concepts, among others subtype-supertype relations. The vocabulary of the formal language, being the names of concepts, are mainly ordinary natural language terms, many of them can also be found in ordinary English dictionaries. All definitions satisfy the rules for proper definitions of concepts in Gellish. This means among others that every concept has a textual definition that refers to its supertype concept(s), and it also means that they have at least one explicit relation with its supertype concept. Thus together the concepts form a consistent subtype-supertype hierarchy of concepts or taxonomy. The Gellish Modeling Methodology provides guidelines for the extension of the taxonomic dictionary and for the creation of domain taxonomic dictionaries or just vocabularies in other languages. Such extensions or modifications may lead to separate domain dictionaries for specialized application areas. As long as the common unique identifiers are used, the availability of vocabularies in various languages enable automated translation of Gellish expressions and their presentations in a generalized user interface.
The Gellish basic language definition in the taxonomic dictionary of Formal English is free of charge available under Open Source conditions (through an Open Source License) via this website. Extended editions and various knowledge models are available for licensees or can be purchased via the webshop.
The most important concepts in the Gellish taxonomic dictionary are kinds of relations. They determine the semantic expression power of the language. Each kind of relation is identified by a UID and is denoted by a name, which may be a short expression, such as 'being manager of an organization'. Such a name is accompanied by a base phrase, such as 'is a manager of' and an inverse phrase, such as 'has as manager. A separate relation denotes which kind of thing should play the first role in the relation (in this example the role 'manager' and the role player 'person') and which kind or thing should play the second role (the role 'managed' and the role player 'organization'). A base phrase requires that the player of the first role is located at the left hand of the phrase according to the normal English grammar and the player of the second role is at its right hand side. For an inverse phrase this is the other way around.
When searching for kinds of relations for expressing information users (and supporting systems) should be aware that kinds of relations are typically denoted in expressions by 'phrases'; thus kinds of relations have phrases as their 'names'. The phrases that denote the kinds of relations obey to a logical pattern. The following patterns can be recognized and should be helpful in searching for the proper kinds of relations:
Name of left hand object | Name of kind of relation | Name of right hand object |
---|---|---|
pump | can have as part a | bearing |
bearing | can be a part of a | pump |
All those kinds of relations are defined in the taxonomic dictionary. The phrases can be used in Gellish for making formalized expressions close to natural language. Note that Gellish dictionary does not provide definitions of the separate words, such as is, a, part and of, but it gives definitions of the whole phrases, because the whole phrases represent kind of relation concepts: ways of being related. The definitions of the standard kinds of relations of the Gellish languages is given in the base ontology section of the Gellish taxonomic dictionary. The kinds of relations currently have 'names' and 'Gellish phrases' in English and in Dutch (Nederlands) and some in German and French. That base ontology section also contains definitions (and names) of the kinds of the roles that are played by objects in relations of those kinds and it contains definitions of the kinds of things that can play such roles. The definitions of kinds of relations also satisfy the rules for proper definitions of concepts in Gellish and thus form a consistent subtype-supertype hierarchy of kinds of relations. As all concepts in the dictionary, including the kinds of relations, roles and other kinds of things, are arranged in a subtype-supertype hierarchy of concepts, the Gellish dictionary is also a taxonomy. The collection of expressions that form the base ontology in the dictionary composes the top of that subtype-supertype hierarchy of concepts. All other concepts in the dictionary are subtypes of those generic concepts. The data in the Gellish dictionary are stored in a Gellish database or collection of files in Gellish Expression Format. For further information about that format see the Gellish Expression Format and its definition in the document 'The Gellish syntax and contextual facts'.
The Gellish taxonomic dictionary defines concepts by expressing computer interpretable expressions of ideas about the concepts. The prime expressions have the form of specialization relations or qualification relations. The expressions are grouped in collections of expressions that define domain related subsets of the dictionary. In the current Gellish dictionary collections of expressions can be distinguished about the following domains:
Every concept is a subtype of a more generic concept, up to the top concept, called anything.
Lower in the hierarchy you will find the more specialized concepts as defined in engineering standards and in proprietary standards. Further specialized concepts, such as catalog items and manufacturer's models are again subtypes of more generalized concepts.
A smart dictionary has a number of characteristics in addition to ordinary dictionaries.
The Gellish taxonomic dictionary is an electronic smart dictionary because it satisfies the following rules:
The Gellish Dictionary itself defines the Gellish languages: it is a language defining ontology.
The Gellish dictionary contains a special collection of facts that specify how expressions of knowledge can be used to create expressions of real facts about individual things.
These are <can be realized by a> relations. Each relation of that kind relates two kinds of relations:
with
An example of such a relation is the expression of the fact that:
The collection of such relations in the Gellish smart dictionary specify which kind of relation type should be used when knowledge or requirements are used to create facts about individual things in an imaginary or real world. This is typically used when knowledge or requirements are turned into designs.
The following example illustrates the basic principles of knowledge-based design using Gellish. Assume that a requirement expresses that
The above-mentioned Gellish language relations define how to apply that knowledge to create bearings for individual pumps. For example, assume that P-101 is classified as a pump, then software that is powered with Gellish can conclude that
whereas
Such software can also derive from the Gellish dictionary what kinds of bearings there are and from a knowledge model in Gellish it can derive which characteristics such components normally have.
Continue with Integrated information