Hello,
I would like to learn more about component "capabilities*".
Key questions are:
1. how does an ODA component "exposes its capabilities" (by what means)?
2. what are the practical benefits of a having a "catalog" of capabilities?
3. what's the relation between an ODA capability/function and an TMF Open API capability/function.
They obviously intersect, both have "capabilities", both needs these capabilities to be registered in a catalogue.
I understand 2 things so far:
1. the component capabilities must be registered in a "catalog" of capabilities.
2. The "catalog" makes all capabilities "discoverable" to other components.
IG1171 says "The functions offered by an ODA component are exposed via "operations and notifications". I assume function = capability.
Component anatomy doesn't have "operations and notifications" but has "Management Function" and "Reporting Function". Are both used to register a capability?
*
"Capability" can have different meaning in different ODA documents. For this post I consider this definition:
A component expose its capabilities. A capability means the ability to carry out a business process.
source: ODA training, component module.
#OpenDigitalArchitecture------------------------------
Matthieu Hattab
Altibox AS
------------------------------