Eliminating "(whole)" from FoodOn product labels

11 views
Skip to first unread message

Damion Dooley

unread,
Apr 2, 2023, 7:32:02 PM4/2/23
to FoodOn Farm-to-Fork Food Ontology Consortium
We had started to take an approach in past of allowing ambiguity directly in classes defined within foodon such as "chicken (whole or parts)". We will keep such classes that we've already set up, but going into the future, if a biosample or other record wants to indicate ambiguity, then in addition to pointing to the animal or organ or plant or plant part that the biosample derived from, it will need to add a generic "animal (whole or parts)", "animal organ (whole or parts)" or "vegetable (whole or parts)" reference for example, to indicate ambiguity.  FoodOn will comprehensively name individual items like "apple" and "piece of apple" for convenience, and as the foundation for further processing.

In connection with that, we have existing entries such as "apple (whole)".  We will be removing the "(whole)" suffix, but ensure that the "whole" semantic is maintained both in term definition ("A pome fruit ...") and axiomatization.  This will lessen the visual disconnect between the fields talking about what the biosample derives from (was "apple (whole)", now just "apple") and statement of ambiguity ("fruit (whole or parts)").  We welcome feedback on this.

Robert Warren

unread,
Apr 4, 2023, 6:05:38 PM4/4/23
to Damion Dooley, FoodOn Farm-to-Fork Food Ontology Consortium
Damion,

I think that this is good practice. We spend most of our time talking about ontological issues but, at the end of the day, the 90% use case is the string that is going to be displayed to the end user. 

Qualifiers are programmatically easy to add if they are needed by the application, but unwieldy to remove through parsing.

-rhw 

On Sun, 2 Apr 2023 at 19:32, Damion Dooley <damion...@gmail.com> wrote:
We had started to take an approach in past of allowing ambiguity directly in classes defined within foodon such as "chicken (whole or parts)". We will keep such classes that we've already set up, but going into the future, if a biosample or other record wants to indicate ambiguity, then in addition to pointing to the animal or organ or plant or plant part that the biosample derived from, it will need to add a generic "animal (whole or parts)", "animal organ (whole or parts)" or "vegetable (whole or parts)" reference for example, to indicate ambiguity.  FoodOn will comprehensively name individual items like "apple" and "piece of apple" for convenience, and as the foundation for further processing.

In connection with that, we have existing entries such as "apple (whole)".  We will be removing the "(whole)" suffix, but ensure that the "whole" semantic is maintained both in term definition ("A pome fruit ...") and axiomatization.  This will lessen the visual disconnect between the fields talking about what the biosample derives from (was "apple (whole)", now just "apple") and statement of ambiguity ("fruit (whole or parts)").  We welcome feedback on this.

--
You received this message because you are subscribed to the Google Groups "FoodOn Farm-to-Fork Food Ontology Consortium" group.
To unsubscribe from this group and stop receiving emails from it, send an email to foodon-consort...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/foodon-consortium/5a16da5e-531b-41a9-9efd-3f87bfd02094n%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages