Open matentzn opened 5 years ago
This is an edge case for located_in.
Actually - I think there's a simpler solution: substitute SO terms for GO chromatin region terms (& leave the job of bridging to SO to GO developers)
@mah11 Do you think this would be an option for you?
Probably. FYPO already uses a lot of the GO chromatin region terms. Of the four logical defs using located_in, two can change to existing GO CC terms. I can request terms to replace the other two, and use them if GO adds them. Watch this space in case they reject one or both.
Note to self: FYPO:0005923 -> GO:1990421 FYPO:0004846 -> GO:0000781 FYPO:0004820 -> GO:new FYPO:0005924 -> GO:new
ticket opened; we'll see what they make of it
Also see https://github.com/geneontology/go-ontology/issues/19178 - GO may second-guess the newest of these terms. In the meantime, FYPO logical defs haven't changed.
FYPO uses some EQs using RO:0001025, located in, in conjunction with SO terms such as
These are the classes:
@dosumis can you figure out, together with @mah11, whether the relation is used approporiately, and if so, whether you can derive a general pattern here? Thanks!