Commit 1a69d3e5 authored by Markus Klinik's avatar Markus Klinik
Browse files

terminology: capabilities

parent b7f940af
......@@ -76,7 +76,14 @@ For simplicity we focus entirely on reusable resources in this paper.
The connection between tasks and resources are made with \emph{capabilities}.
Resources have one or more capabilities, and tasks have one or more \emph{capability requirements}.
For example, Bob can have the capabilities Operator, Medic, and Commander.
The task Perform rescue can require a Transport and an Operator.
From a technical standpoint, capabilities are just labels that the scheduler uses to match resources and tasks.
Because the scheduler does not care what capabilities actually stand for, they can be used in different ways.
For example, capabilities can represent professions, completed trainings, military ranks, or identify individual resources.
In the scheduling literature capabilities are often called \emph{skills}.
We chose not to use this word, because it suggests that resources can only be people.
We want to emphasize that resources can be anything from machines to people to tools, so we chose a more general term.
\todo{use consistently}
We chose to avoid this word because it suggests that resources are people.
We want to emphasize that resources can be anything including machines, people, and tools, so we chose a more general term.
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment