Not all skill modules implement the full range of features
supported by the skill module API, and may have different ways of using the
features they do implement. We summarize characteristics of distributed skill
modules in the table below.
|
Column
|
Description
|
|
Name
|
Module name---also default
skill name.
|
|
Stage
|
Alpha and Beta indicates the general stage of
development.
Sample means it has no real intended purpose other than as
a sample for developers.
|
|
Using
|
This columns indicates which
modules the author is actually using in an application.
|
|
Link
|
Internal modules are statically linked into nb.
External modules are dynamically loaded. Modules linked
internal are also provided as external modules. This supports testing and
use of prior versions.
|
|
Utility
|
General purpose modules can be used for a wide range of
applications.
Special purpose modules are designed to collect data using a
specific protocol, or interface to a specific tool or application.
|
|
Server
|
These modules don’t get
enabled until NodeBrain enters a server mode after processing all arguments.
|
|
Assert
|
Accepts ASSERT command with Data
or Control values.
|
|
Alert
|
Accepts ALERT command with Data
or Control values. Any module that accepts ASSERT commands also
accepts ALERT commands, but most don’t make a distinction. So we only
designate this column when ALERT is treaded differently than ASSERT.
|
|
Enable
|
Accepts ENABLE and DISABLE
commands.
|
|
Command
|
Accepts expert commands “context:text”
|
|
Conditions
|
Returns values when used as
a cell expression “context(arguments)”
|
|
Asserts
|
Asserts value to the expert
context.
|
|
Alerts
|
Alerts the expert context.
|
|
Commands
|
Generates any command to the
interpreter within the expert context.
|