coos:enables should be replaced by its inverse coos:enabledBy from Activity to Capability

[tfrancart]

To represent the link between a capability and the activities it allows to perform, COOS defines the enables property.

2 alternatives here:

1. Assuming we are really talking about activities, and not activity categories : Activities are individual steps in a workflow, they are very "volatile", with a precise date, while capabilities are a controlled vocabulary of concepts defined once and relatively stable. I don't see anyone going to the capabilities controlled vocabulary and editing an entry to point to a new created activity, each time there is a new one. Just as the link between an individual and a Concept is from the individual to the Concept. In that case I suggest to replace coos:enables by an inverse property coos:enabledBy, domain coos:Activity, range coos:Capability.
2. Or what is meant is a link between capabilities and activity categories, and not activities : in that case the range of the property should be adjusted, as well as the example diagram, and the text.