GO-CAM Noctua Call 2018-03-14: Difference between revisions

From GO Wiki
Jump to navigation Jump to search
Line 28: Line 28:
**Map conventional annotations to GO-CAM models  
**Map conventional annotations to GO-CAM models  
**Fit conventional annotation extensions to fit with GO-CAM representation
**Fit conventional annotation extensions to fit with GO-CAM representation
**Idea here it to work towards representing annotations to fit GO-CAM, not the other way around
**Idea here it to work towards revising conventional annotations to fit GO-CAM, not the other way around


== Simple Annoton Editor ==
== Simple Annoton Editor ==

Revision as of 11:19, 14 March 2018

Meeting URL

Agenda

Progress Towards Noctua 1.0 Release

Simple Annoton Editor

  • Review tickets on github tracker
  • Incorporating annotation rules into the SAE
    • What plans do we have for this enhancement?

Consumer Interface, Downloads

  • Any items we want to discuss at this point?

Minutes

  • On call: David H., Dustin, Edith, Harold, Jim, Karen, Kevin, Kimberly, Laurent-Phillipe, Liz, Pascale, Paul T., Rob, Sabrina, Sage, Seth, Stacia, Suzi A., Suzi L.

Progress Towards Noctua 1.0 Release

  • Some relations that are currently used in annotation extensions are not available in the editors
  • How should these be handled in Noctua?
    • For example, 'has regulation target'
      • This has a property chain in go_rel of: regulates o has_participant
      • Do these property chains need to be reviewed?
      • If we want these, do we need SWRL rules?
    • Remove these relations from the 1.0 requirements
    • Look at their usage in conventional annotations; prioritize by most commonly used
    • Map conventional annotations to GO-CAM models
    • Fit conventional annotation extensions to fit with GO-CAM representation
    • Idea here it to work towards revising conventional annotations to fit GO-CAM, not the other way around

Simple Annoton Editor

Proposal(s) for Consumer Interface, Downloads