This page is a first draft, and needs to be properly reviewed.
A capability (of a party) is the (named) combination of
- the means of a specific party to get something done - in other words the means to ensure that certain results are realized (typically associated with an objective of that party);
- the party's governance process that ensures that its (business) policies for getting that something done are being created and maintained, and
- the party's management process that creates and maintains the (operational) policies, such that every employee that has a task in getting this something done can find and interpret a policy and use it as it executes actions in such tasks..
The name of a capability typically refers to a (set of) function(s) that stakeholders (e.g. architects, domain experts, business people, developers) can easily relate to. In SSI contexts, names such as 'issuer capability', 'revocation capability' might appear.
The description of a capability (of a party) should specify
- its name;
- its scope, i.e.
- the functions that define the 'getting something done';
- the (other) capabilities that are expected to be in place, and that the party relies on to function as specified;
- the parties (e.g. service providers) that (operationally) supply the capabilities that the party itself relies on;
- employees that are tasked with the creation and operational maintenance of the means that the party needs to dispose of (and that may rely on other capabilities) in order to have this capability.
- the expectations that this party has towards employees that are tasked with the operational execution of (some of) these functions1.
We need a set of references towards good examples of capability-descriptions.