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

AI: meaning of PresenceType in autonomyType #719

Open
bact opened this issue Apr 16, 2024 · 5 comments · May be fixed by #741
Open

AI: meaning of PresenceType in autonomyType #719

bact opened this issue Apr 16, 2024 · 5 comments · May be fixed by #741

Comments

@bact
Copy link
Contributor

bact commented Apr 16, 2024

autonomyType in AIPackage has a type of /Core/PresenceType.

/Core/PresenceType has 3 possible values:

  • yes: Indicates presence of the field.
  • no: Indicates absence of the field.
  • noAssertion: Makes no assertion about the field.

This is a summary of autonomyType:

States if a human is involved in the decisions of the AI software.

If a human is involved, should autonomyType be "yes" or "no"?

In other words, does "Yes" means:

  1. "Yes, there is human involved" (refer to the summary: "if a human is involved ...") or
  2. "Yes, the system is autonomous" (refer to the name of the field: "autonomyType") ?

May need a further clarification in the property description. ("Yes is..., No is ...")

Similar question for:

@bennetkl
Copy link

I saw it as "yes" when algorithm can perform the programmed operations without human input or guidance.

@bact
Copy link
Contributor Author

bact commented Apr 24, 2024

@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:

States if the system can perform decision
or action
without the involvement of a human.

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).

@bact
Copy link
Contributor Author

bact commented Apr 24, 2024

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 :

Screenshot 2024-04-24 at 13 38 35

@bact
Copy link
Contributor Author

bact commented Apr 29, 2024

As a note, I feel that the use of PresenceType here for "human presence" is a little bit of a mismatch.

To my understanding, the type is more about presence of a metadata.

Its description says:

This type is used to indicate if a given field is present or absent or unknown.

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.

@bact bact linked a pull request Apr 29, 2024 that will close this issue
@bact
Copy link
Contributor Author

bact commented Apr 29, 2024

This issue may resolved by #741

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

Successfully merging a pull request may close this issue.

2 participants