material classes --> ENVO

[pbuttigieg]

Based on our original design of AGRO, several classes in (e.g. liming material, note the issues with multiple inheritance) should be moved into ENVO.

[marieALaporte]

I am happy to have this class and any other material classes that are not specific to AGRO domain to ENVO.
How should I proceed?

Regarding your comment on multiple inheritance, I realize that this is common in Agro. What is the best practice to fix this issues. If I take the example of this 'liming material' class, we would like to list all (or some) of the elements that are liming materials. Should we be using subsets instead?

[pbuttigieg]

I am happy to have this class and any other material classes that are not specific to AGRO domain to ENVO. How should I proceed?

Let's create a term request in ENVO, linking to this thread. Once we have it, you can obsolete the term in AGRO and add a replaced by annotation property on it, pointing to the ENVO term (in CURIE format)

Regarding your comment on multiple inheritance, I realize that this is common in Agro. What is the best practice to fix this issues. If I take the example of this 'liming material' class, we would like to list all (or some) of the elements that are liming materials. Should we be using subsets instead?

Best to create an equivalence axiom like 'liming material' is_a 'environmental material' and 'input of' some 'lime scattering process'. That class be filled by inference, so there won't be asserted multiple inheritance.

[KrishnaTO]

Assuming you'd like to continue the plan to move terms to ENVO (requesting confirmation @pbuttigieg due to stale issue), need to determine which terms require moving.
For reference: https://www.ebi.ac.uk/ols/ontologies/agro/terms?iri=http%3A%2F%2Fpurl.obolibrary.org%2Fobo%2FENVO_00010483

• List AGRO instantiated classes within environmental material