add located_in and is_active_in to allowed list of relations fixes #385

[sierra-moxon]

No description provided.

[sierra-moxon]

@balhoff - reopened as PR on dev instead of master.

[dustine32]

@sierra-moxon Yeah, I bet this would work. Thanks!

[balhoff]

@vanaukenk @ukemi could you please also sign off on this? Asking because adding these has been pending for quite a long time and I'm not sure what has been holding it up, besides inertia.

[balhoff]

Looks good technically but I asked Kimberly and David to approve.

[sierra-moxon]

thanks so much @ukemi and @vanaukenk for taking a look. As per @dustine32's great debugging, I hope this issue will help bring in the remaining noctua annotations to ZFIN (the testing revealed that they are getting left behind on roundtrip from ZFIN->noctua(one time import)->ZFIN. :)

[ukemi]

@balhoff do we have the right property chains in place? enables o occurs_in -> is_active_in ? I think we need that, if not for the imports then for hand-curated models. You diff looks good to me.

[vanaukenk]

Thanks @balhoff
I think I just have the same question as David about the property chain for the GPAD exports: enables o occurs_in -> is_active_in

[balhoff]

• enables o occurs_in -> is_active_in => this is in RO
• There are some other axiom changes proposed in enables_o_occurs_in -> is_active_in ? #179 that we should review. I don't think that should hold this change up.