Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Element URIs from ChEBI? #20

Open
smrgeoinfo opened this issue Apr 6, 2021 · 1 comment
Open

Element URIs from ChEBI? #20

smrgeoinfo opened this issue Apr 6, 2021 · 1 comment

Comments

@smrgeoinfo
Copy link
Collaborator

copied from ESIPFed/sweet#224 (comment)
Follow ups:
@smrgeoinfo : That would be a good thing. The chebi URIs are in the GSO elements module. But we don't want to import CHEBI-- it brings a lot of baggage.
@nicholascar Well I think the solution is as per QUDT: we profile CHEBI. Let’s make a vocabulary profile of CHEBI with just the chemicals needed and just the properties of those chemicals that we care about.
@smrgeoinfo I'm studying CHEBI to see what might reasonably be extracted for a profile. I'd follow the pattern we used for the GSO QUDT profile.

@smrgeoinfo
Copy link
Collaborator Author

smrgeoinfo commented Apr 9, 2021

Problem-- for mapping the CHEBI, its not clear which CHEBI concept of element matches the GSO concept of element. For instance CHEBI has gold atom, molecular gold, and elemental gold, non of which appear to precisely match the GSO concept of 'gold as aggregation of gold atoms' This does surface some interesting ontological problems w.r.t. precisely what is meant to say that e.g. copper is a constituent of cuprite. I'm sure this is a problem that has seen lots of discussion that I'm not up to speed on, so for the time being, we're going to stick with what we've got in GSO, with the URI for the 'atom' CHEBI version of an element in the gsel:chebiid property until we have a clearer picture of the landscape.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant