This looks like a BioMoby service. We are working on providing better support and documentation for BioMoby services.
Click here for more info and guidance on how to use this service
About BioMoby
BioMoby is a way of making services much easier to use and work better together using an ontology-based messaging standard.
Future releases of the BioCatalogue will provide improved support for BioMoby services, including harvesting descriptions and info from the BioMoby registry.
Further documentation can be found here
Provider:
International Rice Information System (IRIS)
Location:
Los Banos, Philippines
Submitter/Source:
SeekDa (over 11 years ago)
Base URL:
http://202.123.56.214:8081/MOBYrice3/services/getGermplasmByPhenotype
WSDL Location:
http://biomoby.org/services/wsdl/www.iris.irri.org/getGermplasmByPhenotype(download last cached WSDL file)
Documentation URL(s): None Login to add a documentation URL Description(s): from provider’s description doc (over 10 years ago) phenotype, or combination of phenotypes.
The returned germplasm objects are very limited – containing just the identity attributes (simple identifiers). There are other use cases (and services implementing them) that can use these identifiers and retrieve full germplasm records.
A phenotype (used as a search filter) is defined by the GCP Domain model as a specialized Feature that contains two concepts, a “Trait” and a “TraitValue”. Both these concepts are defined by their own ontology. The Trait concept is specified as a SimpleOntologyTerm in the type of the phenotype. The TraitValue is specified as a string value of this Phenotype (later use cases may extend this to support more complex values). The above means that for this use case a Phenotype can be represented as a SimpleFeature (and not a full Feature).
For example, a phenotype we are looking for can be “Leaf color is purple”. The “Leaf color” is a term from a controlled vocabulary (ontology) of Traits, and the “purple” is a term from a controlled vocabulary of TraitValues (colors, in this case). The expected Phenotype object for such query will be:
i) getType() returning a type with ID “urn:lsid:…..:XXXXX:..”
where XXXXX is a unique identifier of the term “leaf color” in some ontology (the name of which is also part of the same LSID),
ii) getValueString() returning “purple”
where the string “purple” sits here without any knowledge where it should be looked for (the implementation must guess what would be the reasonable places – tables – to look at)..
Login to add a description ELIXIR Description(s): No info yet Login to add an elixir description License(s): No info yet Login to add license info Cost: No info yet Login to add cost info Usage conditions: No info yet Login to add usage conditions info Contact info: No info yet Login to add contact info How to cite this service: No info yet Login to add how to cite info Publications about this service: for this service (this can be in a common citation format like Bibtex, MLA or APA, a DOI, a URL, etc.) No info yet Login to add publications info Citations of this service: No info yet Login to add citations info Example workflows using this service: See all workflows on myExperiment that use this service Login to add workflows info