We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In LINKSET_EXACT_WIKIPATHWAYS20170929.ttl are URIs like http://cp1.pharma.openphacts.com/compounds/http_//www.wikidata.org/entity/Q27106176 an actual pattern from wikipathways? If so then need to add it to BridgeDb.
LINKSET_CLOSE_PARENT_CHILD_ISOTOPE_INSENSITIVE_PARENT_WIKIPATHWAYS20170929.ttl does not have any data - this is correct but the IMS doesn't like it.
Should we use "https" or "http" in chemistry.openphacts URIs?
DRUGBUNK in file names needs changed to DRUGBANK.
No surechembl updates.
No MESH or PDB.
https://comptox.epa.gov in LINKSET_EXACT_COMPTOX20170929.ttl needs changed to https://comptox.epa.gov/
The text was updated successfully, but these errors were encountered:
@valt, regarding point 1... What is that URI for? It's not an URI from the WikiPathways RDF...
@ianwdunlop, where can I find the VoID header for that linkset LINKSET_EXACT_WIKIPATHWAYS20170929.ttl ?
Sorry, something went wrong.
valt
YVyshnevskyi
No branches or pull requests
In LINKSET_EXACT_WIKIPATHWAYS20170929.ttl are URIs like http://cp1.pharma.openphacts.com/compounds/http_//www.wikidata.org/entity/Q27106176 an actual pattern from wikipathways? If so then need to add it to BridgeDb.
LINKSET_CLOSE_PARENT_CHILD_ISOTOPE_INSENSITIVE_PARENT_WIKIPATHWAYS20170929.ttl does not have any data - this is correct but the IMS doesn't like it.
Should we use "https" or "http" in chemistry.openphacts URIs?
DRUGBUNK in file names needs changed to DRUGBANK.
No surechembl updates.
No MESH or PDB.
https://comptox.epa.gov in LINKSET_EXACT_COMPTOX20170929.ttl needs changed to https://comptox.epa.gov/
The text was updated successfully, but these errors were encountered: