I had to take a nap and read you text again to understand it, and to the degree I understand its connection to what I said, you seem to be expressing the same thing in different terms. I was kind of hoping there would be a solution to what concepts would actually be helpful in explaining the functionality to the user.A Capability is something that could be done.A Permission is whether you are allowed to do it.
Ray, what I was trying to ask was: why don't we just have Capabilities, and then express permissions implicitly. The way of using the word Permission you suggest goes against my understanding of how the word is used in English, and my brain twists!
You can say "I have a permission to do this", or even "I have a permission to use this capability". I understand (though only barely) if someone says For the Role of a Teacher, the capability of changing the short name of a course is allowed/prevented/prohibited/inherited
. I have lots of difficulties when someone comes to tell me that The Permission of the Capability to change the short name of a course for the role of a teacher is allow.
This is how you would use it, right?
Even if it was The Permission to change the short name of a course for the role of a teacher is allow.
It would still confuse someone just learning the concepts, "Wait a minute, you were just talking about capabilities, and now you're saying it's a permission?!".
The concept of a permission, then, seems just a shorthand for what is set for a particular capability in a given role
. It is not a concept of its own, it is an extraneous shorthand with lots of redundance with the concept of a capability, and it seems much easier to just spell out what you are actually saying instead of using it.
For me, the way Capability is used in the Roles system is in sync with how the word is used in English, but the way Permission is used and what it means is different and contradictory with what it means in English. A permission is no kind of a setting or a value, it is a permission. The value for a capability in a role may consequently lead in me being capable of doing it, but the value is not a permission. If it were a permission, the value could only be allow
, since otherwise it is prohibition or prevention.
I have strong wiring in my brain for what the word permission means, so every time I see the Moodle concept permission, I first have to try to unlearn the actual english concept, and it will always be difficult since it is very hard wired to my brain and I am unmotivated to learn the Moodle concept instead since the actual English expression is more useful to me in real life. So if you really want to have a separate concept for this shorthand, please call it Xigrenzedf or Herwondit, so it will not confuse my brain ;).
Chris simplified my writing in the talk page of my suggestion.
I am not quite sure what to make of it yet.