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

Inverses of mixin predicates don't establish an is_a path to a "root" mixin #1480

Open
sierra-moxon opened this issue Mar 21, 2024 · 0 comments

Comments

@sierra-moxon
Copy link
Member

From @colleenXu :

Some of the new "treats"-related predicates are mixins that the other predicates are mapped to: promotes condition, treats, treats or applied or studied to treat. I thought their inverses would be the same (and just map to the equivalent inverse predicates), but: -

  • condition promoted by isn't a mixin
  • treated by and subject of treatment application or study for treatment by are set as mixins, but other predicates aren't mapped to them
  • At the moment, I don't think it'll be a breaking problem. But I do think our team will need to be aware/account for it during the ARA implementation of "treats refactor", by explicitly including all "treats"-related predicates in a template that we want used.

Ex: if we flip treats or applied or studied to treat to subject of treatment application or study for treatment by for execution, the predicate isn't a mixin that'll expand to all "treats-related" predicates the same way the canonical predicate will.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants