You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When SSSOM was originally introduced, the hope was that if you just give people a standard model for mapping metadata, they would magically produce better mappings. 2 years and many litres of tears later, it is clear that there is not even a remotely shared understanding of what it means for two entities (terms, classes, codes, etc) to be "the same".
I would like to try to provide you with a general mental framework for determining "sameness" for your own use cases, and "curation rules" that allow use to clearly document the assumptions by which a "sameness" decision was made.
Concretely, my hope is to help people become more confident about the distinctions of "exact", "broad", "narrow", "close" and "related" matches (see https://mapping-commons.github.io/sssom/mapping-predicates/) when they determine a mapping, and more explicit in documenting the rules by which they arrive at a decision.
The text was updated successfully, but these errors were encountered:
This would be extremely helpful for my work and I would love to be able to link to this Tutorial in the context of the NFDI working group ontology harmonization and mapping.
When SSSOM was originally introduced, the hope was that if you just give people a standard model for mapping metadata, they would magically produce better mappings. 2 years and many litres of tears later, it is clear that there is not even a remotely shared understanding of what it means for two entities (terms, classes, codes, etc) to be "the same".
I would like to try to provide you with a general mental framework for determining "sameness" for your own use cases, and "curation rules" that allow use to clearly document the assumptions by which a "sameness" decision was made.
Concretely, my hope is to help people become more confident about the distinctions of "exact", "broad", "narrow", "close" and "related" matches (see https://mapping-commons.github.io/sssom/mapping-predicates/) when they determine a mapping, and more explicit in documenting the rules by which they arrive at a decision.
The text was updated successfully, but these errors were encountered: