Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Handling KEGG Prefixes with Identical URI Resolution #98

@jplfaria

Description

@jplfaria

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions