Changes between Version 4 and Version 5 of WebInterface/RunningSemanticQueries


Ignore:
Timestamp:
Mar 28, 2012, 2:38:59 PM (13 years ago)
Author:
manualwiki
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WebInterface/RunningSemanticQueries

    v4 v5  
    5858}}} 
    5959== Usage of skeletons == 
    60 A skeleton can be constructed by typing its body into the query construct assistant, then clicking the ’Save as skeleton’ button. The desired name of the constructed skeleton can be typed in the appearing textbox. The skeleton can be saved by clicking the ’Save’ button. If any error occurs during saving, an error message is shown. Constructed skeletons are listed under the ’Skeletons’ tab. 
     60A skeleton can be constructed by typing its body into the query construct assistant, then clicking the ’Save as skeleton’ button. The desired name of the skeleton can be typed in the appearing textbox. The skeleton can then be saved by clicking the ’Save’ button. If any error occurs during saving, an error message is shown. 
    6161 
    62 A previously saved skeleton can be evaluated by calling as a function with the actual values of the parameters. A valid actual parameter can contain nearly anything, only the {{{’}}} character is needed to avoid, because the {{{’}}} character is the delimiter of the value of an actual parameter. Auto-complete does not only offer the possible endings, but also does offer the joint skeletons. 
     62A previously saved skeleton can be evaluated like a function by filling it's actual parameter values. A valid parameter cannot contain the {{{’}}} character, because the {{{’}}} character is the delimiter of the parameter values. Auto-complete in the query textbox also offers skeleton names. 
    6363 
    64 A valid skeleton call is shown below: 
     64An example of a valid skeleton is shown below: 
    6565 
    6666{{{ 
    67 Name = skeleton_name 
    68 Body = mods.funs[$FunSubQuery$] 
     67Name: skeleton_name 
     68Body: mods.funs[$FunSubQuery$] 
    6969skeleton_name(’ (arity>0) and (name like s) ’). 
    7070}}} 
    7171 
    72 Previously saved skeletons are listed at ’Skeletons’ tab. 
     72Constructed skeletons are listed under the ’Skeletons’ tab. 
    7373 
    74 By clicking the name of the skeleton, a valid ’skeleton call’ will be placed in the query construct assistant, where the actual parameters should be written by replacing       character with the corresponding parameter value. 
     74When clicking on a skeleton, a valid ’skeleton call’ will be placed in the query construct assistant, where the actual parameters should be filled out (spaces between '' characters). 
    7575 
    76 By clicking the ? icon, the body of the skeleton and the owner of the skeleton will be shown. 
     76After a successful evaluation of a skeleton, the generated semantic query string and its result are saved in the ’Previous queries’ list, and the result of the semantic query will be shown as usual. 
    7777 
    78 After a successful evaluation of a skeleton, the generated semantic query string and its result are saved in the ’Previous queries’ list, and the result of the semantic query will be shown in the right side of the page. 
     78By clicking the ? icon, the body and owner of the corresponding skeleton will be shown. 
    7979 
    80 Only the owner of the skeleton can edit its body, or can delete it. 
    81  
    82 By clicking the corresponding ’E’ icon, the body of the skeleton will be placed into the query construct assistant. After the necessary changes had been made then the ’Update skeleton’ button has been pressed, the body of the skeleton will be updated. 
     80By clicking the corresponding ’E’ icon, you can edit the body of the skeleton in the query construct assistant. Clicking the ’Update skeleton’ button willupdate the body of the skeleton. 
    8381 
    8482By clicking the corresponding ’X’ icon, the skeleton will be deleted. 
     83 
     84Only the owner of a skeleton can edit or delete it.