-
Notifications
You must be signed in to change notification settings - Fork 204
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
Re-activate gaz - gaz_countries #2108
Comments
See also #2120 for a discussion about what should be required to move a non-active ontology back to active. |
I see in the OFOC notes:
I believe this is the PR that Lynn made: #2269 |
See: OBOFoundry/OBOFoundry.github.io#2108 This PR makes the GAZ countries subset resolvable via its own URL, http://purl.obolibrary.org/obo/gaz/gaz-countries.owl
If a new ID is added to |
Good point, I would say yes, they need to be kept in sync. |
Opening this ticket to request an update in the status of GAZ.
As outlined in OBO-Discuss last year, I have created a 'GAZ_ countries' to enable use of the GAZ and for revisions to be made.
Details from the email:
This work is a continuation of the Gazetteer project previously led by Michael Ashburner.
Thank you to Nico Matentzoglu for mapping the gaz country names to Wikidata, and adding in the Wikidata xrefs.
Please submit term requests:https://github.com/EnvironmentOntology/gaz/issues
Bjoern's email:
Thanks for doing this! We would like to use this file going forward for our IEDB work, but some issues come up with the modeling. Specifically it now says things like Germany is_a Europe, while we really want to say Germany located_in Europe. We had done some workarounds for our IEDB representation of GAZ countries that could be used as an alternative (basically calling the classes something like 'location in Germany', which then is_a 'location in Europe'. We could couple that with mapping to the wikidata instances via 'located in' relationships. That isn't perfect by any means either, but it would be nice to discuss on an OBO operations call?
Cheers,
Lynn
The text was updated successfully, but these errors were encountered: