--- a/OPPL/query.xml	Mon Aug 20 11:39:56 2012 +0200
+++ b/OPPL/query.xml	Thu Sep 20 12:46:36 2012 +0200
@@ -16,7 +16,7 @@
 	
 	<!--<command>
 		java -Djava.library.path=${__tool_data_path__}/shared/jars/FaCT++-linux-v1.5.2/64bit -Xmx3000M -Xms250M -DentityExpansionLimit=1000000000 -jar ${__tool_data_path__}/shared/jars/query.jar $ontology $reasoner $answer_type $answer_format "$query" > $output 
-	</commadn>-->
+	</command>-->
 	
 
 	<inputs>
@@ -26,6 +26,7 @@
 			<option value="Pellet" selected="true">Pellet</option>
 			<option value="HermiT">HermiT</option>
 			<option value="FaCTPlusPlus">FaCT++</option>
+			<option value="Elk">Elk (Not all axioms supported)</option>
 		</param>
 		<param name="answer_type" type="select" label="Choose answer type">
 			<option value="Descendants">Descendant classes</option>
@@ -58,11 +59,19 @@
 
 **About Query-Galaxy**
 
-  Query-Galaxy can be used to execute a DL query against an OWL ontology (e.g. GO_0007049 or part_of some GO_0007049). The result is a list of entities from the target ontology. How those entities relate to the query can be chosen (A DL query is just an anonymous OWL Class).
+  Query-Galaxy can be used to execute a DL query against an OWL ontology. The result is a list of entities from the target ontology. 
 
-**Formats**
-
-  Query-Galaxy uses the OWL API, and therefore it can load any ontology format that such API is able to load: OBO flat file, OWL (RDF/XML, OWL/XML, Functional, Manchester), turtle, and KRSS. The output is a list of terms.
+**Usage**
+ 
+  An ontology is needed as input: load it with Get Data >> Upload File from your computer or redirect the output of another galaxy tool. Query-Galaxy uses the OWL API, and therefore it can load any ontology format that such API is able to load: OBO flat file, OWL (RDF/XML, OWL/XML, Functional, Manchester), turtle, and KRSS. In case the loaded ontology includes OWL imports, Query-Galaxy will try to resolve them.
+  
+  A DL query must be provided, e.g. GO_0007049 or part_of some GO_0007049.
+  
+  The reasoner can be Pellet, HermiT, FaCT++ or Elk.  
+  
+  How the retrieved entities relate to the query can be chosen: a DL query is just an anonymous OWL Class, and the retrieved entities can be descendant classes, direct sub-classes, ancestor classes, direct super-classes, equivalent classes, or member individuals.
+   
+  The returned entities can be rendered using their URI, their URI fragment, or OBO type URI fragment (e.g. GO_0000022 to GO:0000022).
 
 **Contact**