Skip to content

Core Communication Modules

Sean Trott edited this page May 3, 2016 · 17 revisions

(Diagram for System Architecture)

The language and action modules are bridged by shared action protocols we call n-tuples. Both the Problem Solver and Specializer have access to n-tuple templates, which are JSON structures oriented towards particular tasks, action, and information retrieval. The Specializer uses information from the SemSpec to fill in a template; the filled-in template is called an n-tuple. This is then transported over a network to the Problem Solver.

Transport

See the Transport documentation for more information.

Core Agent

The Core Agent

N-tuple Templates

N-tuple templates serve two primary functions in our system:

  1. Declarative instructions: While building an n-tuple, the templates act as declarative specifications for which aspects of the Semantic Specification the Core Specializer should extract, and give instructions on how the output should be formatted.
  2. Shared semantics: Templates are oriented towards particular tasks, and are shared between the Specializer and Problem Solver, which establishes a shared vocabulary and semantics between a human user and a robot agent (or other task).