Grouping: omimFormerly, omimIncluded, & includedEntryInOMIM

[joeflack4]

Overview

Sub-tasks

• "Included" Decide if we want just want 1 property or 2
  • Update 12/16: Nico thinks 2.
• Decide implementation of omimFormerly and omimIncluded
  • a. Joe and Nico think best as synonym types
  • b. We're currently (tentatively?) using them as annotation properties.
• Remove redundant rdf:comments?
  • rdfs:comment "This term has one or more labels that end with ', INCLUDED'."

Sub-issues

• MONDO:omim_formerly mondo#8235
• "Alternative symbol" synonyms & "Formerly" - props rename omim#168
• MONDO:omim_included rename omim#167
• Rename OMIM axiom annotation properties #698

[matentzn]

Just to reiterate:

[Term]
id: NI:CO
synonym: "Big G" EXACT ["MONDO:IncludedEntryInOMIM"]

Is something very different from

[Term]
id: NI:CO
synonym: "Big G" OMIM_INCLUDED EXACT []

Do not mix these two things up! The first case is source evidence. The second case is a synonym type property!

[joeflack4]

Nico says this usage is bad, e.g.:

• TERM MONDO:omimIncluded true
• TERM MONDO:includedEntryInOMIM true

Do this:

• synonym: "Big G" EXACT ["MONDO:IncludedEntryInOMIM"]
  • Should be an oboInOwl:source property

Want to do this way (using omim repo's new functional code):

            add_triple_and_optional_annotations(graph, omim_uri, oboInOwl.hasExactSynonym, title,
                [oboInOwl.source, Literal('MONDO:includedEntryInOMIM')])

            add_triple_and_optional_annotations(graph, omim_uri, oboInOwl.hasExactSynonym, title,
                [oboInOwl.hasSynonymType, URIRef(MONDONS['omim_included'])])