gellish_expression_format
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
gellish_expression_format [2018/10/30 18:29] andries |
gellish_expression_format [2018/10/30 20:18] andries |
||
|---|---|---|---|
| Line 5: | Line 5: | ||
| |assertion|The Euromast|is located in|Rotterdam| | | | |assertion|The Euromast|is located in|Rotterdam| | | | ||
| - | The above Gellish expression table is language dependent and human readable. It can be made language independent by adding references to unique language independent identifiers (UIDs) by extending the table with columns for such UIDs as follows: | + | The above Gellish expression table contains columns that are identified by language independent column IDs (the numbers 31, 101, 3, etc.). The names of the columns as given on the second row are free text. The use of numeric column IDs makes that the columns may be arranged in any order that is convenient for the user. The content of the above table is language dependent and human readable. Its content can be made language independent by inserting columns with unique language independent identifiers (UIDs) for the concepts that are denoted by the above names. Thus by extending the table with columns for such UIDs. The additional columns with object UIDs are illustrated in the following extension of the above table: |
| ^ 1 ^ 5 ^ 2 ^ 60 ^ 15 ^ 66 ^ | ^ 1 ^ 5 ^ 2 ^ 60 ^ 15 ^ 66 ^ | ||
| ^UID of an idea^UID of an intention^UID of a left hand object^UID of a kind of relation^UID of a right hand object^UID of a unit of measure^ | ^UID of an idea^UID of an intention^UID of a left hand object^UID of a kind of relation^UID of a right hand object^UID of a unit of measure^ | ||
| Line 11: | Line 11: | ||
| Note that | Note that | ||
| - | * The UIDs shall be distinguished from the numeric UIDs that are standard in Gellish. Users can make their own UIDs by a prefix followed by a colon (:), followed by free codes. In this example Column 1 with UID therefore contains the prefix 'pr' and code '101', resulting in UID pr:101. | + | * The UIDs of new user objects shall be distinguished from the numeric UIDs that are standard in Gellish. Users can make their own UIDs by using a prefix, followed by a colon (:), followed by free codes. In this example column 3 with Column ID 2, containing the UIDs of the left hand objects therefore contains the prefix 'pr' and code '101' for The Euromast, resulting in UID pr:101 as the unique identifier of The Euromast. |
| - | * The UID of an idea is intended for being used for making statements about the expression as a whole. | + | * The UID of an idea is intended for being used for making statements about the expression as a whole. A name for the idea is usually not applicable. Therefore the column for those names is not included here. |
| * An 'assertion' is a standard kind of intention with the Gellish UID 970025. | * An 'assertion' is a standard kind of intention with the Gellish UID 970025. | ||
| * The Euromast and Rotterdam do not appear in the Gellish Dictionary (assumed), thus the user can allocate his own UIDs for those concepts. | * The Euromast and Rotterdam do not appear in the Gellish Dictionary (assumed), thus the user can allocate his own UIDs for those concepts. | ||
| Line 20: | Line 20: | ||
| === Multi language support === | === Multi language support === | ||
| - | There is a separate pair of columns available for specifying the UID and name of the language of the //name of the left hand object// on each row. This enables to use various languages in the expressions in one table, including the specification that term is a translation of another term for the same concept. | + | There is a separate pair of columns available on each row for specifying the UID and name of the language of the //name of the left hand object//. This enables the use of various languages in the expressions in one table, including the specification that term is a translation of another term for the same concept. |
| Furthermore, one or more separate columns can be inserted each of which for specifying alternative names for the left hand object in a specific language. The column ids for those columns should be the Gellish UIDs for the particular languages. For example, a table in English may include an expression in Dutch and an additional column with a name of the left hand objects in German (where applicable). This is illustrated in the following table: | Furthermore, one or more separate columns can be inserted each of which for specifying alternative names for the left hand object in a specific language. The column ids for those columns should be the Gellish UIDs for the particular languages. For example, a table in English may include an expression in Dutch and an additional column with a name of the left hand objects in German (where applicable). This is illustrated in the following table: | ||
| ^ 54 ^ 31 ^ 101 ^ 910038 ^ 3 ^ 201 ^ | ^ 54 ^ 31 ^ 101 ^ 910038 ^ 3 ^ 201 ^ | ||
| Line 29: | Line 29: | ||
| === Synonyms === | === Synonyms === | ||
| Alias names for objects, such as synonyms, abbreviations, codes, etc. can be specified by explicit statements using phrases for the kinds of relations that express the appropriate subtype of the alias relation. There is no extra column required for such expressions. Aliases are specified in a similar way as the specification of a translation in the above example. For example: | Alias names for objects, such as synonyms, abbreviations, codes, etc. can be specified by explicit statements using phrases for the kinds of relations that express the appropriate subtype of the alias relation. There is no extra column required for such expressions. Aliases are specified in a similar way as the specification of a translation in the above example. For example: | ||
| + | ^ 101 ^ 3 ^ 201^ | ||
| ^Name of left hand object ^Name of kind of relation^Name of right hand object^ | ^Name of left hand object ^Name of kind of relation^Name of right hand object^ | ||
| | PC |is an abbreviation of|personal computer| | | PC |is an abbreviation of|personal computer| | ||
| - | === Homonyms (language communities) === | + | === Homonyms === |
| - | Using the same name for different concepts, being homonym names, is enabled by distinguishing the objects by their different UIDs and by specifying different //language communities// in which those names find their home. This is supported by a special pair of columns in the expression table for the UID and the name of the language community. For example the term 'bank' in a the language community 'business' denotes an object with UID 990152, whereas the term 'bank' in the language community 'civil technology' denotes an object with UID 700140. This is illustrated in the following core table: | + | Using the same name for different concepts, being homonym names, is enabled by distinguishing the objects by their different UIDs and by specifying different //language communities// in which the homonym names find their home. This is supported by a special pair of columns in the expression table for the UID and the name of the applicable language community. For example the term 'bank' in a the language community 'business' denotes an object with UID 990152, whereas the term 'bank' in the language community 'civil technology' denotes an object with UID 700140. Their defining expressions are illustrated in the following core table: |
| ^ 16 ^ 101 ^ 3 ^ 201 ^ 4 ^ | ^ 16 ^ 101 ^ 3 ^ 201 ^ 4 ^ | ||
| ^Language community^Name of left hand object ^Name of kind of relation^Name of right hand object^Textual definition^ | ^Language community^Name of left hand object ^Name of kind of relation^Name of right hand object^Textual definition^ | ||
| Line 40: | Line 41: | ||
| === Contextual facts === | === Contextual facts === | ||
| - | Other columns are available for expression of contextual facts, such as status, date of creation, author, etc. Those columns can be added depending in the requirements of the user by selecting them from a list of available columns. The columns may be arranged in any order that is convenient for the user. Multiple tables can be combined and different tables may consist of different collections of columns. This is described in detail in the document [[http://www.gellish.net/downloads/gellish-syntax-and-contextual-facts-definition-of-universal-semantic-databases-and-data-exchange-messages.html|'The Gellish Syntax and contextual facts']] \\ | + | Other columns are available for expression of contextual facts, such as approval status (column ID 8), date-time of creation, creator, etc. Those columns can be added depending in the requirements of the user by selecting them from a list of available columns. |
| + | Multiple tables can be combined and different tables may consist of different collections of columns. This is described in detail in the document [[http://www.gellish.net/downloads/gellish-syntax-and-contextual-facts-definition-of-universal-semantic-databases-and-data-exchange-messages.html|'The Gellish Syntax and contextual facts']] \\ | ||
| === Header rows === | === Header rows === | ||
| - | The table has three header rows. The first header row contains the following fields: | + | The table has three header rows. |
| + | The first header row contains the following fields: | ||
| ^Gellish^//English//^Version^//version code//^//date of release//^//name or category of expressions//^//file name//^ | ^Gellish^//English//^Version^//version code//^//date of release//^//name or category of expressions//^//file name//^ | ||
| followed by an optional sequence of name based parameter names and values: | followed by an optional sequence of name based parameter names and values: | ||
| Line 55: | Line 58: | ||
| * The optional prefix specifies a prefix that may be used to precede a colon (:) and newly generated numeric codes for generating new UIDs for new concepts. For example, the prefix 'pre' can be used by software for generating the following sequence of UIDs within the object uid range 20-30: pre:20, pre:21, pre:22, etc. The software should first verify which is the highest current value within the range for the prefix. | * The optional prefix specifies a prefix that may be used to precede a colon (:) and newly generated numeric codes for generating new UIDs for new concepts. For example, the prefix 'pre' can be used by software for generating the following sequence of UIDs within the object uid range 20-30: pre:20, pre:21, pre:22, etc. The software should first verify which is the highest current value within the range for the prefix. | ||
| - | The columns in a table are identified by language independent column IDs in the second header row. The third header row contains free text names of the columns, corresponding with the column IDs. \\ | + | The second header row of a table contains language independent column IDs as are shown in the above tables. The third header row contains free text names of the columns, corresponding with the column IDs, also as shown above. \\ |
| Various examples of tables in Gellish Expression Format are given in the [[http://www.gellish.net/downloads|download area]]. \\ | Various examples of tables in Gellish Expression Format are given in the [[http://www.gellish.net/downloads|download area]]. \\ | ||
gellish_expression_format.txt · Last modified: 2019/09/13 16:15 by andries
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
