Skip to content

Handling KEGG Prefixes with Identical URI Resolution #98

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

Open
jplfaria opened this issue Feb 21, 2025 · 0 comments
Open

Handling KEGG Prefixes with Identical URI Resolution #98

jplfaria opened this issue Feb 21, 2025 · 0 comments

Comments

@jplfaria
Copy link

KEGG Ontology Prefix Handling

We are currently using two KEGG prefixes:

Both of these prefixes resolve to the same base URL: https://www.kegg.jp/entry. For example:

I have been manually editing the prefix.csv files in my semsql installation to handle prefixes that are not already defined for ontologies we are currently developing. However, I'm uncertain how best to handle the KEGG prefixes given their shared resolution.

Any suggestions or guidance on a robust solution for this issue would be greatly appreciated.

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