User Tools

Site Tools


executing_the_communicator

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
executing_the_communicator [2018/02/02 22:15]
andries preparing and reading input files clarified
executing_the_communicator [2018/02/02 22:51] (current)
andries Example of a road network introduced
Line 17: Line 17:
  
 ==== Read file ==== ==== Read file ====
-Preparing Gellish expressions shall be done in one of the Gellish formalized languages conform the methodology that is described in the book '​Semantic Modeling Methodology'​.+Preparing Gellish expressions shall be done in one of the Gellish formalized languages conform the methodology that is described in the book '​Semantic Modeling Methodology'​. ​As demonstrator,​ the user can import the '​Semantic Model of a road network-UTF-8'​ file that is available via the website, together with a descriptive document.\\  ​
 Gellish files can be imported via the option 'Read file'. Normally the program is started with the automatic import of the language definition. Thus reading files will automatically imply an addition to and integration with the existing language definition. Exceptionally,​ a manual start of the import of the (base) language definition shall be executed first via the 'DB Admin'​+ 'New network'​ option.\\  ​ Gellish files can be imported via the option 'Read file'. Normally the program is started with the automatic import of the language definition. Thus reading files will automatically imply an addition to and integration with the existing language definition. Exceptionally,​ a manual start of the import of the (base) language definition shall be executed first via the 'DB Admin'​+ 'New network'​ option.\\  ​
 A Gellish file should be compliant with the Gellish Expression Format as a CSV or JSON file and be expressed in Unicode UTF-8 encoding.\\ A Gellish file should be compliant with the Gellish Expression Format as a CSV or JSON file and be expressed in Unicode UTF-8 encoding.\\
Line 40: Line 40:
  
 === Left hand term === === Left hand term ===
-The left hand term field of the Query Window (initially filled with a question mark (?)) can be used to enter search string or a combination of strings that are separated by a blank space. The list of found candidates strings is displayed in a lower box under the header '​Select one of the following options'​. The list of candidates shows not only the candidate terms, but also the UIDs of the objects for which the strings are names, their '​Kind'​ (being a name of a classifier or a supertype of the candidate object), the '​language community'​ of the candidate terms and the language of the terms.\\+The left hand term field of the Query Window (initially filled with a question mark (?)) can be used to enter search string or a combination of strings that are separated by a blank space. The list of found candidates strings is displayed in a lower box under the header '​Select one of the following options'​. The list of candidates shows not only the candidate terms, but also the UIDs of the objects for which the strings are names, their '​Kind'​ (being a name of a classifier or a supertype of the candidate object), the '​language community'​ of the candidate terms and the language of the terms.\\
 This information enables to distinguish between homonyms (the same term with a different UID) and it also shows possible synonyms (having the same UID).\\ This information enables to distinguish between homonyms (the same term with a different UID) and it also shows possible synonyms (having the same UID).\\
 +When the '​Semantic model of a road network'​ is imported via the read file option, then it is recommended to try searching for concepts in that model, for example search for N51 or search for '​road'​.
  
 Selection of the required candidate by a **double click** will show the full name in the 'Left hand term' field, its UID in the UID field and a textual definition in the '​**Def. of left hand object**'​ field.\\ Selection of the required candidate by a **double click** will show the full name in the 'Left hand term' field, its UID in the UID field and a textual definition in the '​**Def. of left hand object**'​ field.\\
executing_the_communicator.txt ยท Last modified: 2018/02/02 22:51 by andries