ONS introduces multiple labels, which is problematic

[matentzn]

ONS introduces a label on a FOODON term, "shrimp":

This is problematic for various reasons. Tools assume one canonical label per class. The only possible exception is labels in other languages, clearly distinguished by different language tags..

cc @ddooley

[ddooley]

@FrancescoVit Do you need a hand addressing this one? 2ndary labels should be made into synonyms or alternate labels.

[FrancescoVit]

@ddooley eventually, how to understand which of the two labels should be mutated to synonim or alternate? should an "editor preferred label" be used?

[ddooley]

First, all this duplicate label stuff may be a result of merging updated FoodOn import files into ONS rather than the better way of keeping them as separate files referenced from within ons-edit.owl? It looks like you have the "shrimp as food source" FoodOn label from a few years ago, and then a more recent simplified "shrimp" label. This whole problem I think would be solved by using the OWL import system 100% for reference to all terms not defined by ONS. I can help revise your setup to accomplish that.

Right now the latest "shrimp" term is in this import file:

while the "shrimp as food source" is sitting permanently in your ons-edit.owl file. We need to get that out of ons-edit.owl And it would be good to have a better file name and URL specified in the "shrimp" term's import file.

[ddooley]

By the way, our latest policy around what to associate food references like "shrimp" is here: FoodOntology/foodon#133 - see the very last diagram. In other words, what should we reference when someone mentions "shrimp". (Not mentioned in that writeup is a term like shrimp doesn't have a direct taxonomic equiivalent because humans have alot of crossover in referencing prawns as shrimp and visa versa.)

[ddooley]

This should be resolved now, so can close this.