Constraints on part of

[dosumis]

Objects can only be part of objects
Processes can only be part of processes

We can't add this constraint using local domain and range or owl domain and range.

We could add constraints constraints using OWL. But showing these in Protein2GO will require on a suitable web-service infrastructure at Berkeley.

Alternatively, we could restrict AEs to two subrelations for occurrent and continuant part_of. These are already in RO, but need nicer names. Curators suggest: part_of_process and part_of_object. With this in place we can use OWL and local domain and range as normal.

[cmungall]

These should be encoded in RO as allValuesFrom axioms. The noctua reasoner which will run on the client side does a closed-world check on these.

(as well as the complete reasoning that will also happen on the server side)

cc @balhoff @kltm

[dosumis]

Protein2GO users would like these checks to be available to them. What are the chances that these checks (& reasoning more generally) could be rolled into a web-service that P2GO can access?

CC @tonysawfordebi @rachhuntley @RLovering