-
Notifications
You must be signed in to change notification settings - Fork 3
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
Avoid example.com justification for conceptwiki #7
Comments
Used for Protein-Gene mapping - particularly for looking up labels which could be for both genes or proteins. The two lenses http://heater.cs.man.ac.uk:3004/QueryExpander/Lens?lensGroup=gene opts between http://example.com/ConceptWikiGene and http://example.com/ConceptWikiProtein Related to SQL hack for different direction? Tricky to fix properly in time for Open PHACTS 2.0 |
Maybe someone could explain what the page at http://heater.cs.man.ac.uk:3004/QueryExpander/Lens?lensGroup=gene is actually trying to tell me. Why do we have justifications which use the example.com domain? |
Excerpts from Ian Dunlop's message of 2015-10-14 13:34:27 +0100:
As far as Daniela explained, the http://example.com/ConceptWikiGene and There are two different lenses so when you ask for labels for say a uniprot There's also the related gene-to-protein but not protein-to-gene issue. Now even if we are to keep a special justification for conceptwiki, then Stian Soiland-Reyes, eScience Lab |
Thanks for that explanation but I'm not sure I could figure that out from the web page. For example, the description "The lens used to Add ConcepWiki Gene URIs into the Open PHACTS Discovery Platform" doesn't seem to tell me that if I use this ConceptWikiGene Lens then I will get the gene name rather than the protein name. As another example, what are the assumptions behind the Default Lens. Justifications using a collection of URIs are fine for machines but not so good for humans. Anyway, apologies for hijacking the thread. |
ConceptWiki void has justifications like
These should be replaced with proper justifications. Even if this remains special, terms should be minted in the bridgedb or openphacts namespace.
The text was updated successfully, but these errors were encountered: