User Tools

Site Tools


development_of_gellish_enabled_software

Developing Gellish enabled software

1. The Gellish Dictionary as a basis

Application software developers that intend to use Gellish English should import and combine combine the various parts of the Gellish Dictionary (at least including the TOPini part) into one integrated Gellish Database, whereas lines with status 'ignore' or 'inherited' may be ignored. The columns in the Gellish Database table are defined in the wiki page Gellish Database and in the document 'The Gellish Database Definition'.

The collection of upper ontological facts (the facts in the TOPini table) defines the standard relation types of Gellish. Those relation types are used to interpret the expressions of facts in each Gellish Database table, including the facts that are expressed in the TOPini part itself. This means that the Gellish TOPini table defines the Gellish interpretation rules, whereas those rules are also the rules to interpret itself. The TOPini table itself uses only a few standard relation types: the starter set.

1.1 Relation type definitions

Each relation type has a name and is defined by a <is a specialization of> relation with its direct supertype relation(s). On separate lines it is specified for each relation type that it requires two roles: a first role and a second role. For each role it is specified in another fact which kind of thing can fulfil such a role. Nearly each relation type has also a synonym name that is a Gellish phrase and an inverse Gellish phrase. Those phrases are natural language expressions for the relation type. The synonym phrase uses a first role player at the left hand side of the phrase (in English). The inverse role uses a second role player at the left hand side of the phrase (in English). For example: the subtype-supertype relation (UID 1146) is called <specialization of class>. The synonym phrase is: <is a specialization of> requires a player of its first role (subtype) at its left hand side and a player of its second role (supertype) at its right hand side. Thus the expression: “house <is a specialization of> building” is a semantically correct Gellish expression according to the definition in TOPini. A correct inverse expression will be “building <is a generalization of> house”.

If for a relation type it is not specified which kinds of roles it requires, then the roles are inherited from the supertype of the relation type, because the relation types are arranged in a subtype-supertype hierarchy. For that reason the roles of a relation type are subtypes of the roles of the supertype of the relation type. And also a role player of a particular role is a subtype of a role player of the supertype role of that particular role.

The standard Gellish relation types are available also for users to express knowledge and information facts in Gellish English about any subject. Such user defined facts may also include expressions that define private extensions of the Gellish Dictionary or even private definitions of additional relation types.

The relation types that are defined in the TOPini table are used in the other Gellish Database tables to define concepts in the Gellish English Dictionary and they are used in various Gellish Knowledge Bases that express facts about the defined concepts. The combined other tables contains the definition of all concepts in the Gellish Dictionary. All those concepts are arranged as a taxonomy (subtype-supertype hierarchy).

2. Certification of software

Software that is able to import and interpret Gellish expressions in a correct way and is also able to create and export correct Gellish expressions can be certified by the !GellishAtWork organization. For further information about the certification process and conditions contact the site administrator.

Continue with Gellish Database

development_of_gellish_enabled_software.txt · Last modified: 2017/08/11 15:10 (external edit)