-
Notifications
You must be signed in to change notification settings - Fork 26
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
Add suggested list of values for tree inference methods #226
Comments
I've been reviewing both phylont ( CDAO has a few model description terms and some potentially useful I started a google doc comparing the vocabularies I can share if Thoughts? On 3/7/14, 2:44 PM, Jim Allman wrote:
|
Thanks, @pmidford, suggestions for the method list are welcome. I can start with a simple list of inference methods on Wikipedia (http://en.wikipedia.org/wiki/Bayesian_inference_in_phylogeny, see the footer):
|
@pmidford: I see that the methods listed on BioPortal are in a more extensive hierarchy: http://bioportal.bioontology.org/ontologies/PHYLONT/?p=classes&conceptid=http%3A%2F%2Fwww.co-ode.org%2Fontologies%2Font.owl%23Assessment-of-Uncertainty I can certainly follow suit in a SELECT widget, if we want this added precision. |
@jimallman: Agree we could do this, though I suspect the tip terms are most common. Many inference methods will specify a model as well as the method (which is a different branch of the ontology). In those cases, both should be specified - one field or two? My intuition is that higher level terms might be useful for the method, but if a model is specified, it will be a tip term. |
Agree we could do this. Probably worth looking at the existing On 3/7/14, 5:01 PM, Jim Allman wrote:
|
Interesting! And now I see that there's a proposed ot:inferenceMethod for trees in the Nexson wiki page: I'm not sure if this is just a better name for ot:curatedType, or if the combination fits your model + method description. |
The intent of the ot:inferenceMethod was to capture the method, though On 3/7/14, 10:02 PM, Jim Allman wrote:
|
The property tree['^ot:curatedType'] is currently treated as a free-form text field. While we want to allow this, it's best if people choose from among a preset list of inference methods. The UI for this can include two widgets: a
SELECT
(pull-down) for suggested values, and a free-form text field that appears if the user choose 'Other' from the suggestion list.The text was updated successfully, but these errors were encountered: