Environmental Engineering Reference
In-Depth Information
domain:
The domain is the system the message is dealing with. The domain
in this case is usually “EP.”
object-type:
The type of the main object that the message refers to. This is
a level in the object hierarchy (e.g., system, subsystem, or component).
object-name:
The actual name of the object given in the user request.
object-specifiers:
Any words from the user request that give more detailed
information about which object is being referred to. This covers specifica-
tion of a number of objects that are being referred to (e.g., “number 1,”
“this,” “any”).
parameters:
Any information that adds detail about the task to be performed.
For example, when monitoring or reporting on the solar arrays, this field
would specify temperature, performance, etc.
action-start:
The date/time at which the action being referred to in the mes-
sage is to begin.
action-duration:
The length of time the action is to last.
function:
An actual function that is to be called as a result of the message. If
the
input-string
field is not empty, it contains parameters that are to be
passed to the function.
input-string:
This slot contains any data or text information required by other
slots of the message. If the function slot is populated, this slot would
contain input parameters. For a “parse” performative message, this slot
would contain the actual sentence submitted by the user.
Each ACL message format had a message header and a message body.
The message header consisted of the message attributes from
msg-id
through
result-format
. The rest of the message was the body of the message. An ex-
ample of an ACL message generated from a user's natural language input is
shown below. A user's input is the value stored in the
input-string
at the
bottom of the message. Only pertinent values of the attributes of the message
need to be included. Because the performative for this message is “parse,” the
SSA would use the information in its skill base to route the request to the nat-
ural language parser for processing. An example of a REQUEST-MESSAGE
in an ACL format is the following:
(msg-id, gen001)
(user-id, john)
(sender, umbc-ui)
(receiver, loral-coord)
(respond-to, umbc-ui)
(reply-constraint, ASAP)
(language, CLIPS)
(msg-type, request)
(performative, parse)
(recipient, john-uia)
(result-action, nil)
(result-format, nil)
