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

BioPAX Pathway URIs #1258

Open
IgorRodchenkov opened this issue May 25, 2024 · 1 comment
Open

BioPAX Pathway URIs #1258

IgorRodchenkov opened this issue May 25, 2024 · 1 comment

Comments

@IgorRodchenkov
Copy link
Member

I just discovered that Biofactoid is already included in bioregistry.io registry and can resolve links.
See http://bioregistry.io/biofactoid

So why don't you use those resolvable/linkable URIs for the Biofactoid Pathways in the BioPAX model and output file?

Can we use e.g. "http://bioregistry.io/biofactoid:3e4476c1-e3ec-4635-969b-6a02de4e581a" URI instead of current "3e4476c1-e3ec-4635-969b-6a02de4e581a" (or use whatever ID resolves to the right thing)?

In the BioPAX file it looks like this:

<bp:Pathway rdf:about="3e4476c1-e3ec-4635-969b-6a02de4e581a">

but likely should look like this

<bp:Pathway rdf:about="http://bioregistry.io/biofactoid:3e4476c1-e3ec-4635-969b-6a02de4e581a">

PS: (more importantly)
By the way, the examle ID above is from a biopax data file (0a49a0c9-1cb4-4f67-b78f-eaa5cc5f0ebf.owl) from the archive that I downloaded from https://biofactoid.org/api/document/zip/biopax?idMapping=true on 13 May 2024.

Why the Pathway ID/URI there is "3e4476c1-e3ec-4635-969b-6a02de4e581a" instead of that from the file name: "0a49a0c9-1cb4-4f67-b78f-eaa5cc5f0ebf", which is in fact perfectly resolvable: http://bioregistry.io/biofactoid:0a49a0c9-1cb4-4f67-b78f-eaa5cc5f0ebf?

Also, the example from the bioregistry.io/biofactoid page also works (gets resolved): http://bioregistry.io/biofactoid:fdb8a927-45c3-48b7-9743-cbb5e16837fa

@IgorRodchenkov
Copy link
Member Author

On the second thought.., as I understand, Biofactoid stable IDs are document IDs, not bioentity IDs... A document can have more than one Pathway or interactions or no pathways.
So likely not using the document ID for any of the bioentities was a good decision indeed. So ignore my suggestion then.

Though, it would be great to make sure you generate the same ID/URIs for the same Things (bioentities and refs inside the BioPAX files) every time one calls: https://biofactoid.org/api/document/zip/biopax?idMapping=true

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