# KEHOME/help/tip.txt
# Mar/1/2003
#========================#
# tips for new KE users  #
#========================#
# # begins comment
#          =======
# ; terminates proposition
#              ===========
# ? denotes question
#           ========
# do or ! begins command
#                =======

# four principal sources of input knowledge are:
#                           =====
<v_input:.=existent>Dick isa person;	# manual input (with prompt)
do read from family.ku done;		# knowledge unit file
do read from phonebook.rel done;	# relation file
do read from book.ho done;		# hierarchy file
# words are separated by blank tab comma semicolon
# quotes are used to preserve blank tab comma semicolon
# continuation to next line is automatic for any line ending with
#	, & | ~  { [ ( <
#	MKR keywords (e.g.: isa,has, if,then,else, every,do)

# output knowledge is specified by:
# ======
set hfocus = [animal,event];  # list of concepts
set hformat = ho;             # format
set debug = ALIAS;            # extra details


# knowledge processing is specified by:
#           ==========
exit; # terminates without automatic checks and writes
EOF   # automatically checks and writes all knowledge
      # EOF is usually CONTROL-Z on Windows
      # EOF is usually CONTROL-D on Linux
do check od definition done; # specific command
cat,dog  isd animal;         # differentiate existing concept: animal
organism isi animal,plant;   # integrate into new concept: organism

# knowledge searches (questions) are formed from statements by:
#           ========
Dick  has sex=male?;	# appending ?
Dick  do  ? done;	# replacing object  with ?
apple ?   orange;       # replacing verb    with ?
?     has sex=female;	# replacing subject with ?
do find od Bob* done;	# replacing part of name with "*" wildcard
# Results are stored in the variable $Sentence.

# ke self knowledge is available:
#    ==============
ke has ?;	# all attributes of ke		(parameters)
ke do ? done;	# all actions of ke		(commands)
set hformat = ?;# current attribute value	(parameters)
vfind is ?;	# definition of ke command	(purpose)

# built-in help command
#          ====
do help done;               # list of available help topics
do help od KR design done;  # knowledge representation design philosophy
do help od KE design done;  # knowledge explorer design philosophy

# many examples are located in KEHOME/knowledge subdirectories
#      ========
# examples/General		knowledge units    (isa,ise, is, has, with)
# examples/General		change units       (at,do, changes,from,to)
# examples/General		relations          (format, meaning)
# examples/General		user-defined methods
# examples/English		transliterated English
# examples/BookHierarchy	hierarchy outlines (/ name)
# examples/Logic		logic		   (if,then,else,fi, and,or,not)
# application/ExpenseRecord	  relations, iteration, variables
# application/Genealogy		  relations, methods, condtionals, iteration
# application/SemanticWeb	  RDF, OWL, RSS, etc.
# application/SemanticWeb/TAP	  Stanford TAP knowledge base
# application/SemanticWeb/OpenCyc OpenCyc knowledge base
# theory/ContextSymposium	  AAAI paper "What is Context?"
# theory/FormalConceptAnalysis	  Formal Concept Analysis
# theory/Epistemology		  concept formation  (isi,isd, measure,classify)

# KEHOME/doc		Icon Newsletter article "Knowledge Explorer"

# Knowledge Explorer Tutorial is located in
#                    ========
#   KEHOME/doc/KEtutorial.txt

# Knowledge Representation Grammar is located in
#                          =======
#   KEHOME/doc/KRgrammar.txt
#
# Knowledge Explorer User Manual is located in
#                    ===========
#   KEHOME/doc/ke.hlp	help file           (Windows winhelp command)
#   KEHOME/doc/ke.rtf	word processor file (Windows wordpad command)

# Linux users: beware of extra CarriageReturn (^M) in source files.
# ===========
# These may prevent ke from recognizing input line continuations.
# You can remove extra CRs with deletecr (KEHOME/bin/deletecr).
