Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
tfrancart opened this issue Oct 13, 2023 · 0 comments

Comments

@tfrancart
Copy link
Collaborator

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant