This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
correct_gellish_english [2018/11/03 00:10] andries |
correct_gellish_english [2018/11/03 00:22] (current) andries |
||
---|---|---|---|
Line 2: | Line 2: | ||
====== 1. Rules for correct Gellish English ====== | ====== 1. Rules for correct Gellish English ====== | ||
- | A correct Gellish English collection of expressions is presented in a [[gellish_databases|Gellish Database]] table that satisfies at least the following rules: | + | A correct Gellish English collection of expressions is presented in a [[gellish_databases|Gellish expression format]] table that satisfies a number of rules. A few very important ones are described below. Others are implemented in the Gellish Communicator software reference application that is available on GitHub. |
- | **Rule 1: Facts shall be expressed as binary relations between things** | + | **Rule 1: Ideas shall be expressed as binary relations between things** |
- | Facts shall be expressed in Gellish English by one or more binary relations, each of which shall relate two things on a single line in a Gellish Database table. A related thing may be anything, including an individual thing or a kind of thing, a single thing or a plural thing (collection) and may be real or imaginary. Only in the case of synonyms and translations the related things (referenced by their unique identifiers) shall be the same while their names may be different. | + | Ideas, such as assertions, queries, etc. shall be expressed in Gellish as one or more binary relations, each of which shall relate two things on a single line in a Gellish expression format table. A related thing may be anything, including an individual thing or a kind of thing, a single thing or a plural thing (collection) and may be real or imaginary. Only in the case of synonyms and translations the related things (referenced by their unique identifiers) shall be the same while their names may be different. |
**Rule 2: Each thing shall be defined by an explicit classification or specialization relation** | **Rule 2: Each thing shall be defined by an explicit classification or specialization relation** | ||
This implies that each Gellish expression shall only only relate things (individual things and kinds of things or concepts) that are properly defined in one of the following three ways: \\ | This implies that each Gellish expression shall only only relate things (individual things and kinds of things or concepts) that are properly defined in one of the following three ways: \\ | ||
- | 1. It is a concept that is already defined in the [[:Gellish English Dictionary]] and is selected from that dictionary (its name or synonym and unique identifier). \\ | + | 1. It is a concept that is already defined in the [[:Gellish English Dictionary|Gellish Dictionary]] and is selected from that dictionary (its name or synonym and unique identifier). \\ |
2. It is a new concept (kind of thing) that is properly defined according to the Gellish [Proper definition of a concept|rules for proper definitions of concepts]]. This includes that the new concept is defined by the specification of an explicit specialization relation that defines it as a (proprietary) subtype of one of the concepts that already exist in the Gellish English Dictionary. | 2. It is a new concept (kind of thing) that is properly defined according to the Gellish [Proper definition of a concept|rules for proper definitions of concepts]]. This includes that the new concept is defined by the specification of an explicit specialization relation that defines it as a (proprietary) subtype of one of the concepts that already exist in the Gellish English Dictionary. | ||
Definitions of new concepts can be issued as proposals for inclusion in the Open Source Gellish English dictionary. \\ | Definitions of new concepts can be issued as proposals for inclusion in the Open Source Gellish English dictionary. \\ | ||
Line 20: | Line 20: | ||
* John Doe is classified as a man (optionally described by some characteristics). | * John Doe is classified as a man (optionally described by some characteristics). | ||
- | **Rule 3: Each relation shall be classified by a standard relation type** | + | **Rule 3: Each relation shall be classified by a standard kind of relation** |
- | Each relation shall be classified by a kind of relation (relation type) that is selected from the Gellish dictionary. Private extensions of the Gellish Dictionary with additional relation types are allowed, provided that is done \\ | + | Each relation shall be classified by a kind of relation that is selected from the Gellish dictionary. Private extensions of the Gellish Dictionary with additional kinds of relations are possible, provided that is done conform the rules for defining new concepts.\\ |
- | For example, for an electronic cataloge of fasteners it may be requirement that a bolt shall have a length. Such a fact shall be expressed by a relation that is classified by a standard relation type with unique identifier 4956 and shall have as 'name' the standard phrase 'shall have as aspect a'. So the Gellish English expression becomes: \\ | + | For example, for an electronic catalog of fasteners it may be requirement that a bolt shall have a length. Such a requirement shall be expressed by a relation that is classified by a standard kind of relation with unique identifier 4956 and shall have as 'name' the standard phrase 'shall have as aspect a'. The Gellish expression then becomes: \\ |
- | ^UID of left hand object^Name of left hand object^UID of fact^UID of relation type^Name of relation type^UID of right hand object^Name of right hand object^ | + | ^UID of left hand object^Name of left hand object^UID of idea^UID of kind of relation^Name of kind of relation^UID of right hand object^Name of right hand object^ |
| 340016 | bolt | 1 | 4956 | shall have as aspect a | 551353 | length| | | 340016 | bolt | 1 | 4956 | shall have as aspect a | 551353 | length| | ||
Line 38: | Line 38: | ||
For further information on certification please contact info@gellish.net. \\ | For further information on certification please contact info@gellish.net. \\ | ||
- | **//Continue with//** [[:Data Modeling and Database Design in Gellish English]] \\ \\ | + | **//Continue with//** [[:Data Modeling and Database Design in Gellish English|How to write Gellish enabled sofware]] \\ \\ |