Terminology

= Terminology =

We need a reference to communicate across groups, but don’t get hung up on the exact word. There are many different users/devs in the rocon ecosystem (e.g. robot, software, web, control, service) so the concept is more important than the exact terminology.

= Simpler Definitions =

General


 * : Rocon universal resource identifier strings are key to describing the various entities (robots, remocons), the compatible apps that run on them and allow us to shape requests for these resources as well as their allocation at a higher level.
 * e.g - rocon://concert_name/hardware_platform/name/application_framework/operating_system#rocon_app

Concert Definitions


 * : the centralised multi-robot framework pictured previously.
 * : any robot/device satisfying requirements to connect and run inside the concert.
 * : clients that can be re-tasked with different applications (usually retaskable robots).
 * : representing a human in the system via tabs/phones/web apps (sometimes referred to as interactive concert clients).
 * : usually a software process requested by a service or other concert client and allocated by the scheduler.
 * : fundamental representation and specification of 'something that delivers a certain functionality' in the system
 * e.g. a specific software launch configuration running on a robot, the software and interfaces provided by a software node executing on a virtual pc.
 * : collection of components (including a ros master) that initiates the minimum requirements of a concert.
 * : handles invitations, connections, platform info and app management on each client.
 * : handles requests for resources from services and schedules/allocates them (hopefully intelligently).
 * : the whole system should be auto-discoverable on the LAN (apple’s bonjour style).

Orchestration Definitions


 * : a loose term describing all the machinery required to facilitate orchestration of the concert (e.g. tools for connectivity, logging, introspection, databases).
 * : the ability of a concert client to introspect about whether a task it is given is feasible.
 * e.g. a robot introspecting whether it can accommodate the payload size, weight and shape for a delivery task.
 * : is a tentative term to define an invoked workflow in service. (e.g 1 order in drink delivery service)

Appable Robot Definitions


 * : a robot engineered for retaskable operation inside the concert environment.
 * : opposite end of the conductor, platform info, app installation and execution.
 * : internal layer to simplify development, installation and execution of apps.
 * : the robot specific software base (usually custom).