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

Missing domain and range restrictions #582

Open
gregfowlerphd opened this issue Jan 1, 2025 · 2 comments
Open

Missing domain and range restrictions #582

gregfowlerphd opened this issue Jan 1, 2025 · 2 comments
Assignees
Labels
for 2.1 release These are changes we would like to see addressed under the 2.1 release

Comments

@gregfowlerphd
Copy link
Contributor

I was recently adding back axioms to MIREOT-ed CCO classes and object properties, and I noticed that a number of CCO object properties lack any domain and range restrictions despite such restrictions being clearly specified in their definitions:

  • "process started by" / "process starts"
  • "has agent" / "agent in"
  • "has object" / "is object of"
  • "describes condition" / "condition described by"
  • "is mention of" / "is mentioned by"
  • "is used by" / "uses"

Similarly, in the case of "has recipient" / "receives" and "has sender" / "sends", only one restriction is asserted even though both are indicated in their definitions.

It seems to me that the relevant restrictions should be added.

@neilotte
Copy link
Contributor

neilotte commented Jan 4, 2025

@gregfowlerphd -- One of our colleagues has conducted a comprehensive review of this issue and a fix is underway. @oliviahobai -- fysa.

@neilotte neilotte added the for 2.1 release These are changes we would like to see addressed under the 2.1 release label Jan 4, 2025
@gregfowlerphd
Copy link
Contributor Author

@neilotte: Thanks, Neil. I assume you're referring to Michael Rabenberg? He emailed me after seeing this issue to let me know he'd been working on it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
for 2.1 release These are changes we would like to see addressed under the 2.1 release
Projects
None yet
Development

No branches or pull requests

3 participants