<?xml version = "1.0" encoding = "UTF-8"?>
<serviceDescriptions  xmlns="pd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="pd /C:/Documents and Settings/ytanoh/My Documents/TAVERNA/taverna-1.4-old/plugins/pedro/services/model/common.xsd">
	<serviceDescription >
		<serviceName>domainreso</serviceName>
		<organisation >
			<organisationName>European Bioinformatics Institute</organisationName>
			<organisationDescriptionText>http://www.ebi.ac.uk/</organisationDescriptionText>
			<organisationKey>EBI</organisationKey>
		</organisation>

		<locationURL>http://www.ebi.ac.uk/soaplab/emboss4/services/protein_3d_structure.domainreso</locationURL>
		<interfaceWSDL>http://www.ebi.ac.uk/soaplab/emboss4/services/protein_3d_structure.domainreso?wsdl</interfaceWSDL>
		<serviceDescriptionText>Removes low resolution domains from a DCF file(domain classification file). Detailed info about this operation can be found at the following link: http://pro.genomics.purdue.edu/cgi-bin/emboss/help/domainreso</serviceDescriptionText>
		<operations >
			<serviceOperation >
				<operationName>domainreso</operationName>
				<operationDescriptionText>Removes low resolution domains from a DCF(domain classification file) file. Detailed info about this operation can be found at the following link: http://pro.genomics.purdue.edu/cgi-bin/emboss/help/domainreso</operationDescriptionText>
				<operationInputs >
					<parameter >
						<parameterName>cpdbpath_direct_data</parameterName>
						<parameterDescription>Type: string. CCF file (clean coordinate files). A &apos;clean cordinate file&apos; contains coordinate and other data for a single PDB file or a single domain from SCOP or CATH, in CCF format (EMBL-like). The files, generated by using PDBPARSE (pdb files) or DOMAINER (domains), contain &apos;cleaned-up&apos; data that is self-consistent and error-corrected. Records for residue solvent accessibility and secondary structure are added to the file by using PDBPLUS. This is an optional parameter. Parameters &apos;cpdbpath_direct_data&apos; and &apos;cpdbpath_url&apos; are mutually exclusive. </parameterDescription>
						<transportDataType>String</transportDataType>
					</parameter>

					<parameter >
						<parameterName>cpdbpath_url</parameterName>
						<parameterDescription>Type: string. URL of CCF file (clean coordinate files). A &apos;clean cordinate file&apos; contains coordinate and other data for a single PDB file or a single domain from SCOP or CATH, in CCF format (EMBL-like). The files, generated by using PDBPARSE (pdb files) or DOMAINER (domains), contain &apos;cleaned-up&apos; data that is self-consistent and error-corrected. Records for residue solvent accessibility and secondary structure are added to the file by using PDBPLUS. This is an optional parameter. Parameters &apos;cpdbpath_direct_data&apos; and &apos;cpdbpath_direct_url&apos; are mutually exclusive.</parameterDescription>
						<defaultValue>./</defaultValue>
						<transportDataType>String</transportDataType>
					</parameter>

					<parameter >
						<parameterName>dcfinfile_direct_data</parameterName>
						<parameterDescription>Type: string. Specifies the DCF file (domain classification file). A &apos;domain classification file&apos; contains classification and other data for domains from SCOP or CATH, in DCF format (EMBL-like). The files are generated by using SCOPPARSE and CATHPARSE. Domain sequence information can be added to the file by using DOMAINSEQS. This is a mandatory parameter if the parameter &apos;dcfinfile_url&apos; is not chosen. Both parameters are mutually exclusive. 
An example of input is available here: http://pro.genomics.purdue.edu/cgi-bin/emboss/help/domainreso#input.1</parameterDescription>
						<transportDataType>String</transportDataType>
					</parameter>

					<parameter >
						<parameterName>dcfinfile_url</parameterName>
						<parameterDescription>Type: string. URL of DCF file (domain classification file) (input). A &apos;domain classification file&apos; contains classification and other data for domains from SCOP or CATH, in DCF format (EMBL-like). The files are generated by using SCOPPARSE and CATHPARSE. Domain sequence information can be added to the file by using DOMAINSEQS. This is a mandatory parameter if the parameter &apos;dcfinfile_direct_data&apos; is not chosen. Both parameters are mutually exclusive. </parameterDescription>
						<transportDataType>String</transportDataType>
					</parameter>

					<parameter >
						<parameterName>threshold</parameterName>
						<parameterDescription>Type: float. This option specifies the threshold for inclusion (Angstroms). Domains exceeding the threshold for inclusion (Angstroms) will not be given in the output file. This is an optional parameter. The default is 2.8</parameterDescription>
						<defaultValue>2.8</defaultValue>
						<transportDataType>String</transportDataType>
					</parameter>

				</operationInputs>

				<operationOutputs >
					<parameter >
						<parameterName>report</parameterName>
						<parameterDescription>Type: string. A general report for the underlying analysis job.</parameterDescription>
						<transportDataType>String</transportDataType>
					</parameter>

					<parameter >
						<parameterName>detailed_status</parameterName>
						<parameterDescription>Type: long. The exit code of the underlying analysis job, 0 means the job returned normally.</parameterDescription>
						<transportDataType>String</transportDataType>
					</parameter>

					<parameter >
						<parameterName>dcfoutfile</parameterName>
						<parameterDescription>Returns a DCF file containing the same domains excluding those whose resolution (Angstrom) of structure determination exceeds a user-defined threshold.</parameterDescription>
						<semanticType>http://www.mygrid.org.uk/ontology#protein_structure</semanticType>
						<transportDataType>String</transportDataType>
					</parameter>

				</operationOutputs>

				<operationTask>http://www.mygrid.org.uk/ontology#filtering</operationTask>
				<operationResource>http://www.mygrid.org.uk/ontology#PDB</operationResource>
			</serviceOperation>

		</operations>

		<serviceType>Soaplab service</serviceType>
	</serviceDescription>

</serviceDescriptions>
