KE-Text - Revision history

DavidWhitten at 20:21, 20 August 2021

2021-08-20T20:21:31Z

DavidWhitten: /* Special Handling for TheAssertionSentence */

2016-09-24T16:46:58Z

‎Special Handling for TheAssertionSentence

DavidWhitten: /* Special Handling for TheAssertionSentence */

2016-09-24T16:46:08Z

‎Special Handling for TheAssertionSentence

DavidWhitten: /* Special Handling for TheAssertionSentence */

2016-09-24T16:45:03Z

‎Special Handling for TheAssertionSentence

DavidWhitten: /* Special Handling for TheAssertionSentence */

2016-09-24T16:43:47Z

‎Special Handling for TheAssertionSentence

DavidWhitten: /* Special Handling for TheAssertionSentence */

2016-09-24T16:42:56Z

‎Special Handling for TheAssertionSentence

DavidWhitten: /* Special Handling for TheAssertionSentence */

2016-09-24T16:41:42Z

‎Special Handling for TheAssertionSentence

DavidWhitten: /* Special Handling for TheAssertionSentence */

2016-09-24T16:41:12Z

‎Special Handling for TheAssertionSentence

DavidWhitten: /* Strings */

2016-09-24T16:34:57Z

‎Strings

DavidWhitten: /* Constants */

2016-09-24T16:34:15Z

‎Constants

@@ Line 69: / Line 69: @@
 A complete, meaningful syntactic unit of Cyc KE text is an “expression”.
-Expressions in KE Text syntax are somewhat analogous to sentences in a natural language, or more closely, to expressions in a programming language such as [[COMPUTER LANGUAGE COMMON LISP|Lisp]] or [[COMPUTER LANGUAGE JAVA|Java]]. In [[COMPUTER LANGUAGE JAVA|Java]], the end of an expression is indicated by a semi-colon (;). In [[COMPUTER LANGUAGE COMMON LISP|Lisp]], the end of an expression is indicated by a right parenthesis that balances a corresponding left parenthesis. In KE Text syntax, each expression must end with a period (.), and the period must be outside a comment or a string. The general form of an expression in KE Text syntax is as follows:
+ Expressions in KE Text syntax are somewhat analogous to sentences in a natural language, or more closely, to expressions in a programming language such as [[COMPUTER LANGUAGE COMMON LISP|Lisp]] or [[COMPUTER LANGUAGE JAVA|Java]]. In [[COMPUTER LANGUAGE JAVA|Java]], the end of an expression is indicated by a semi-colon (;). In [[COMPUTER LANGUAGE COMMON LISP|Lisp]], the end of an expression is indicated by a right parenthesis that balances a corresponding left parenthesis. In KE Text syntax, each expression must end with a period (.), and the period must be outside a comment or a string. The general form of an expression in KE Text syntax is as follows:
 <pre> <directive>: <data-object-or-object-sequence>. </pre>
@@ Line 128: / Line 128: @@
 </pre>
-If the data object following the colon delimiter is not already known (by Cyc) to be a Cyc constant, users will be asked whether they want to create a new constant with that name.
+ If the data object following the colon delimiter is not already known (by Cyc) to be a Cyc constant, users will be asked whether they want to create a new constant with that name.
-When an expression beginning with a Constant directive is evaluated, it causes the default entry constant (the “current” constant) to be set to the named constant, the default truth value to be set to :unknown, the default direction to also be set to :unknown, and the default entry [[microtheory]] to be set to the [[BaseKB]]. The only exception to this is if the [[microtheory]] has previously been set via the Default Mt directive, in which case the use of the Constant directive leaves the microtheory unchanged. All of the settings made by the ''Constant'' directive persist until they are changed by some other (implicit or explicit) directive.
+ When an expression beginning with a Constant directive is evaluated, it causes the default entry constant (the “current” constant) to be set to the named constant, the default truth value to be set to :unknown, the default direction to also be set to :unknown, and the default entry [[microtheory]] to be set to the [[BaseKB]]. The only exception to this is if the [[microtheory]] has previously been set via the Default Mt directive, in which case the use of the Constant directive leaves the microtheory unchanged. All of the settings made by the ''Constant'' directive persist until they are changed by some other (implicit or explicit) directive.
 ===== In MT =====
@@ Line 153: / Line 153: @@
 </pre>
-When an expression beginning with a Default Mt directive is evaluated, is causes the entry/delete microtheory to be set to the named microtheory. This setting persists until the next occurrence of a Default Mt or In Mt directive, or the end of the file/text being processed. Once a directive has been overriden by another directive, the scope of the original directive is no longer valid, even if the second directive is itself overriden later. Note that this directive, unlike the In Mt directive, prevents each occurrence of a Constant directive from resetting the default microtheory to BaseKB. This directive makes it easier to process all (or most) of the expressions in a file/text segment in the same microtheory.
+ When an expression beginning with a Default Mt directive is evaluated, is causes the entry/delete microtheory to be set to the named microtheory. This setting persists until the next occurrence of a Default Mt or In Mt directive, or the end of the file/text being processed. Once a directive has been overriden by another directive, the scope of the original directive is no longer valid, even if the second directive is itself overriden later. Note that this directive, unlike the In Mt directive, prevents each occurrence of a Constant directive from resetting the default microtheory to BaseKB. This directive makes it easier to process all (or most) of the expressions in a file/text segment in the same microtheory.
@@ Line 168: / Line 168: @@
 </pre>
-It should only very rarely be necessary for a user to use a Truth Value directive. KE Text assigns truth values to entry expressions automatically. If an entry expression begins with a predicate which is an instance of [[DefaultMonotonicPredicate]] (including [[isa]] and [[genls]]), the expression is automatically assigned a truth value of :monotonic.  All other entry expressions are automatically assigned a truth value of :default. Note that the strength of “implies” is :default, by default.The only reason to use a Truth Value directive is if you want to override these built-in defaults.
+ It should only very rarely be necessary for a user to use a Truth Value directive. KE Text assigns truth values to entry expressions automatically. If an entry expression begins with a predicate which is an instance of [[DefaultMonotonicPredicate]] (including [[isa]] and [[genls]]), the expression is automatically assigned a truth value of :monotonic.  All other entry expressions are automatically assigned a truth value of :default. Note that the strength of “implies” is :default, by default.The only reason to use a Truth Value directive is if you want to override these built-in defaults.
-When an expression beginning with a Truth Value directive is evaluated, it causes the entry truth value for the following expression to be set to the indicated truth value. (Note that an expression might comprise several assertions. This will be explained more fully below). After the expression to be entered is evaluated, the setting immediately reverts to :unknown, until the next entry expression is encountered (and the truth value is automatically set to :default or :monotonic), or until another Truth Value directive is read.
+ When an expression beginning with a Truth Value directive is evaluated, it causes the entry truth value for the following expression to be set to the indicated truth value. (Note that an expression might comprise several assertions. This will be explained more fully below). After the expression to be entered is evaluated, the setting immediately reverts to :unknown, until the next entry expression is encountered (and the truth value is automatically set to :default or :monotonic), or until another Truth Value directive is read.
-When would you want to use this directive? Suppose you wanted to enter a rule with a truth value of :monotonic. Since the default setting for rules is :default, in your KE text you would want to precede the rule with this expression:
+ When would you want to use this directive? Suppose you wanted to enter a rule with a truth value of :monotonic. Since the default setting for rules is :default, in your KE text you would want to precede the rule with this expression:
 <pre>
@@ Line 313: / Line 313: @@
 comment: “Keith Goolsbey is a member of the Cycorp technical board.”.
-In this example, the Constant directive sets the “current” constant to be Goolsbey. Goolsbey is then assumed to be the first argument to assertions formed from the three following predicate directive expressions (the expressions which begin with “isa”, “feelsTowardsObject”, and “comment”).
+ In this example, the Constant directive sets the “current” constant to be Goolsbey. Goolsbey is then assumed to be the first argument to assertions formed from the three following predicate directive expressions (the expressions which begin with “isa”, “feelsTowardsObject”, and “comment”).
-If the predicate directive is the name of a binary predicate (such as isa and comment), each of the data objects following the colon delimiter is assumed to be part of an assertion in which the predicate directive is the predicate, the default constant is the first argument, and the data object is the second argument.
+ If the predicate directive is the name of a binary predicate (such as isa and comment), each of the data objects following the colon delimiter is assumed to be part of an assertion in which the predicate directive is the predicate, the default constant is the first argument, and the data object is the second argument.
-If the predicate directive is the name of an n-ary predicate where n is greater than 2 (such as #$feelsTowardsObject), each of the data objects following the colon delimiter must be a list. The elements in the list are assumed to be part of an assertion in which the predicate directive is the predicate, the default constant is the first argument, and the elements (in listed order) are the remaining arguments. So, when evaluated and processed, the KE text fragment in the example above would result in the addition of the following six assertions to the KB:
+ If the predicate directive is the name of an n-ary predicate where n is greater than 2 (such as #$feelsTowardsObject), each of the data objects following the colon delimiter must be a list. The elements in the list are assumed to be part of an assertion in which the predicate directive is the predicate, the default constant is the first argument, and the elements (in listed order) are the remaining arguments. So, when evaluated and processed, the KE text fragment in the example above would result in the addition of the following six assertions to the KB:
 (#$isa #$Goolsbey #$HumanCyclist)
@@ Line 543: / Line 543: @@
   | {formula-directive}
@@ Line 689: / Line 688: @@
 Appendix G
 ++++++++++
+<pre>
 Common Cyc Abbreviations
@@ Line 753: / Line 752: @@
 WALES Web-Assisted Lexical Entry System
 WFF Well-formed formula; pronounced ‘woof.’ Used as an adjective to denote correctness (i.e. ‘This CycL sentence is not wff.’)
+</pre>
 Appendix L

@@ Line 371: / Line 371: @@
         ([[and]]
-               ([[termOfUnit[[ ?NART (?FUNC . ?ARGS))
+               ([[termOfUnit]] ?NART (?FUNC . ?ARGS))
                ([[argIsa]] ?FUNC ?N ?COL)

@@ Line 367: / Line 367: @@
   '''In Mt''': [[BaseKB]].
-  ''f'': ([[implies]]
+  '''f''': ([[implies]]
         ([[and]]
@@ Line 382: / Line 382: @@
     ;; assert a [[ruleTrivialForJustificationParaphrase]] [[GAF]] about the rule
-   ''f'': ([[ruleTrivialForJustificationParaphrase]] [[TheAssertionSentence]]).
+   '''In Mt''': [[BaseKB]].
    ;; assert a [[salientAssertions]] [[GAF]] about the rule (not about the
@@ Line 391: / Line 391: @@
    ;;  ruleTrivialForJustificationParaphrase GAF
-   ''In Mt'': [[BaseKB]].
+   '''In Mt''': [[BaseKB]].
-   ''f'': ([[salientAssertions]] [[argIsa]] [[TheAssertionSentence]]).
+   '''f''': ([[salientAssertions]] [[argIsa]] [[TheAssertionSentence]]).

@@ Line 363: / Line 363: @@
 For example:
-: ;; an example rule:
+ ;; an example rule:
-−
-: '''In Mt''': [[BaseKB]].
+ '''In Mt''': [[BaseKB]].
-−
   ''f'': ([[implies]]
-−
         ([[and]]
-−
                ([[termOfUnit[[ ?NART (?FUNC . ?ARGS))
-−
                ([[argIsa]] ?FUNC ?N ?COL)
                ([[argN]] ?ARGN ?N ?NART)
-−
                ([[isa]] ?ARGN [[Collection]]))
-−
     ([[isa]] ?ARGN ?COL)).
-−
     ;; assert a [[ruleTrivialForJustificationParaphrase]] [[GAF]] about the rule
- ''In Mt'': [[BaseKB]].
+  ''In Mt'': [[BaseKB]].
-−
- ''f'': ([[ruleTrivialForJustificationParaphrase]] [[TheAssertionSentence]]).
+  ''f'': ([[ruleTrivialForJustificationParaphrase]] [[TheAssertionSentence]]).
-−
- ;; assert a [[salientAssertions]] [[GAF]] about the rule (not about the
+  ;; assert a [[salientAssertions]] [[GAF]] about the rule (not about the
-−
- ;;  ruleTrivialForJustificationParaphrase GAF
+  ;;  ruleTrivialForJustificationParaphrase GAF
-−
- ''In Mt'': [[BaseKB]].
+  ''In Mt'': [[BaseKB]].
-−
- ''f'': ([[salientAssertions]] [[argIsa]] [[TheAssertionSentence]]).
+  ''f'': ([[salientAssertions]] [[argIsa]] [[TheAssertionSentence]]).
-−

@@ Line 363: / Line 363: @@
 For example:
- ;; an example rule:
+: ;; an example rule:
-−
+:
- '''In Mt''': [[BaseKB]].
+: '''In Mt''': [[BaseKB]].
   ''f'': ([[implies]]

@@ Line 359: / Line 359: @@
-The constant [[TheAssertionSentence]] has special support for referring to the previously asserted sentence, not including previous sentences that mentioned TheAssertionSentence itself.  This is useful for making meta-assertions without having to copy the [[#$ist]] assertions formula multiple times.
+The constant [[TheAssertionSentence]] has special support for referring to the previously asserted sentence, not including previous sentences that mentioned [[#$TheAssertionSentence]] itself.  This is useful for making meta-assertions without having to copy the [[#$ist]] assertions formula multiple times.
 For example:
-In Mt: BaseKB.
+ ;; an example rule:
-f: (implies
+ ''f'': ([[implies]]
-        (and
+        ([[and]]
-               (termOfUnit ?NART (?FUNC . ?ARGS))
+               ([[termOfUnit[[ ?NART (?FUNC . ?ARGS))
-               (argIsa ?FUNC ?N ?COL)
+               ([[argIsa]] ?FUNC ?N ?COL)
-               (argN ?ARGN ?N ?NART)
+               ([[argN]] ?ARGN ?N ?NART)
-               (isa ?ARGN Collection))
+               ([[isa]] ?ARGN [[Collection]]))
-    (isa ?ARGN ?COL)).
+    ([[isa]] ?ARGN ?COL)).
-    ;; assert a ruleTrivialForJustificationParaphrase GAF about the rule
+    ;; assert a [[ruleTrivialForJustificationParaphrase]] [[GAF]] about the rule
-In Mt: BaseKB.
+ ''In Mt'': [[BaseKB]].
-f: (ruleTrivialForJustificationParaphrase TheAssertionSentence).
+ ''f'': ([[ruleTrivialForJustificationParaphrase]] [[TheAssertionSentence]]).
-;; assert a salientAssertions GAF about the rule (not about the
+ ;; assert a [[salientAssertions]] [[GAF]] about the rule (not about the
-;;  ruleTrivialForJustificationParaphrase GAF
+ ;;  ruleTrivialForJustificationParaphrase GAF
-In Mt: BaseKB.
+ ''In Mt'': [[BaseKB]].
-f: (salientAssertions argIsa TheAssertionSentence).
+ ''f'': ([[salientAssertions]] [[argIsa]] [[TheAssertionSentence]]).
 Note that this support breaks the ability to make assertions about TheAssertionSentence itself using [[KE Text]].
 === Comments in KE Text ===

← Older revision		Revision as of 16:34, 24 September 2016
Line 45:		Line 45:


−	Strings referred to in KE text (such as entries on the #$comment predicate for a constant) must be delimited by double quotes (e.g., “This is a string.”), as in [[COMPUTER LANGUAGE COMMON LISP\| Common Lisp]] and [[COMPUTER LANGUAGE C\| C]].	+	Strings referred to in KE text (such as entries on the [[#$comment]] predicate for a constant) must be delimited by double quotes (e.g., “This is a string.”), as in [[COMPUTER LANGUAGE COMMON LISP\| Common Lisp]] and [[COMPUTER LANGUAGE C\| C]].

	To use double quotes inside comments, prefix them with a backslash. (e.g. “This comment \”contains\” double quotes.”)		To use double quotes inside comments, prefix them with a backslash. (e.g. “This comment \”contains\” double quotes.”)

@@ Line 40: / Line 40: @@
 ====     Constants ====
-It is not necessary to include the initial “#$” in references to known constants (i.e., constants which Cyc already knows to exist), though it is not disallowed. For example, one could use either [[#$Siegel]] or Siegel; [[#$KeithsHouse]] or KeithsHouse. Accepted practice is to write KE text without the “#$” prefix.
+It is not necessary to include the initial “#$” in references to known constants (i.e., constants which Cyc already knows to exist), though it is not disallowed. For example, one could use either [[#$Siegel]] or [[Siegel]]; [[#$KeithsHouse]] or [[KeithsHouse]]. Accepted practice is to write KE text without the “#$” prefix.
 ==== Strings ====