To the Point 1:
In SOA RM, a service is defined as a "set of technical and business elements that form a path between those with needs and those with capabilities." This sounds like those with needs are interested in capabilities.
If capabilities are resources, then aforementioned statement is ambiguous a service consumer is interested in the results of using resources RWE, not in the resources per se. Am I wrong?
I think that RM is more consistent and comprehensive about capabilities than, unfortunately, we are. Here is my proposal for the definition of Capability:
Capability: declared ability of the service in providing a real-world effect to a service consumer by utilizing underlying resource or set of resources.
Difference is that in the RM capability is the RWF, in my definition it is an ability to provide RWE using resources.
RWE - agreed
Action I do like Kens the message sender invokes the service's action. We do not define and consumer does not care what the service actions are but, in contrast with MOM, a service consumer KNOWS that a service executes its actions in respond to the invocation (in the cases of brokering intermediary a consumer might not know which service would be invoked but it is a different story)