Analyze: Source has both isObsolete and owl:deprecated

[joeflack4]

Overview

Both of these props exist in ICD11. We at Mondo consider these words interchangeable. But perhaps there is a good reason why both exist in ICD11. Do a small analysis.

Sub-tasks

• 1. Analysis @joeflack4
  • Can maybe write a SPARQL query or use OAK for the usage of each, or OAK. And see if there's an intersection.
• 2. Advise @matentzn @twhetzel

Details

Does the existence of both of these rather than just isObsolete (which is what I was expecting) indicate that it is insufficient simply to remap isObsolete to owl:deprecated? Could that cause some kind of issue?

I initially found isObsolete and was going to rename that to owl:deprecated. However, I now see that the source has both. Not sure what I intend to do yet. Perhaps there is some nuance difference between these two. I'm not sure if we care about that nuance and should do some retention of both of these properties, or if I should rename them all to owl:deprecated.

Perhaps one thing I can do is an analysis of the cases where a class is both isObsolete and owl:deprecated, and also look at classes that only have one of these properties.

---

Original post