-
Notifications
You must be signed in to change notification settings - Fork 41
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
AI: meaning of PresenceType in autonomyType #719
Comments
I saw it as "yes" when algorithm can perform the programmed operations without human input or guidance. |
@bennetkl I agree with that interpretation - the semantic is straightforward to the name of the field. But with that, we may need to rewrite the summary to something like this instead:
It's similar to the current summary, but written from an opposite point of view - put the autonomy concern at the center (and human involvement a secondary). |
Way forward to 3.1, we may like to consider that automation has degrees. See this table of varying degrees of automation from https://doi.org/10.3390/ijerph19063641 : |
As a note, I feel that the use of To my understanding, the type is more about presence of a metadata. Its description says:
But for 3.0.x, I don't think we can change the type. The best we can do is to put in the description, what "yes" means and what "no" means. |
This issue may resolved by #741 |
autonomyType
inAIPackage
has a type of/Core/PresenceType
./Core/PresenceType
has 3 possible values:This is a summary of
autonomyType
:If a human is involved, should
autonomyType
be "yes" or "no"?In other words, does "Yes" means:
May need a further clarification in the property description. ("Yes is..., No is ...")
Similar question for:
The text was updated successfully, but these errors were encountered: