Updated API to include multiple service support and added some missing elements.

@@ -62,6 +62,12 @@
       <elem name="returnFilteredData" multiplicity ="1" type="bool" default ="false">
       <elem name="returnFilteredData" multiplicity ="1" type="bool" default ="false">
         <comment>Optional boolean, determines if filtered data should be returned to caller for future testing and analysis.</comment>
         <comment>Optional boolean, determines if filtered data should be returned to caller for future testing and analysis.</comment>
       </elem>
       </elem>
+      <elem name="uriServices" multiplicity = "1..*" type="Tensor.uri">
+          <comment>One or more services to use to process the specified data sets.   Analysis can comprise multiple services 
+          processing the datasets and producing reports that provide a comparative performance. Check the API documentation for
+          querying a list of available service URIs (e.g. ILPS, etc.).
+          </comment>
+      </elem>      
     </struct>
     </struct>
 
 
     <!-- 
     <!-- 
@@ -84,6 +90,9 @@
         <comment>Optional contact information.</comment>
         <comment>Optional contact information.</comment>
       </elem>
       </elem>
 
 
+      <elem name="datasets" multiplicity="0..*" type="DataSet">
+        <comment>Dataset specifications to process.</comment>
+      </elem>
     </struct>
     </struct>
 
 
     <!-- 
     <!-- 
@@ -167,6 +176,13 @@
         <comment>Confidence for the result records. Typically this will be .6872, but will report the confidence specified by the input.</comment>
         <comment>Confidence for the result records. Typically this will be .6872, but will report the confidence specified by the input.</comment>
       </elem>
       </elem>
 
 
+      <elem name="uriService" multiplicity = "1" type="Tensor.uri">
+          <comment>URI of the service used  process the specified datasets.   This is one of the services specified in DataSet/uriServices field.
+          Analysis can comprise multiple services processing the datasets and producing reports that provide a comparative performance. Check the API documentation for
+          querying a list of available service URIs (e.g. ILPS, etc.).
+          </comment>
+      </elem>   
+
     </struct>
     </struct>
 
 
     <!-- 
     <!-- 
@@ -190,8 +206,8 @@
         <comment>Duration of the execution time in milliseconds.</comment>
         <comment>Duration of the execution time in milliseconds.</comment>
       </elem>
       </elem>
 
 
-      <elem name="uriSource" type="string" multiplicity="1">
-        <comment>Source of results.</comment>
+      <elem name="resultsets" multiplicity="0..*" type="ResultSet">
+        <comment>Results processed by a specified service.</comment>
       </elem>
       </elem>
     </struct>
     </struct>
 
 
@@ -222,6 +238,19 @@
             <comment>Optional, publishes the results for additional downstream processing.</comment>
             <comment>Optional, publishes the results for additional downstream processing.</comment>
           </elem>
           </elem>
           
           
+          <elem name="maxBatch" multiplicity ="1" type="uint16" default ="1">
+            <tag name="unit" value="records"/> 
+            <comment>The maximum batch of records that may be processed at one time.  The default is 1, only one record may be processed at a time.
+            The system may place limits on the batch size and interval so as maximum throughput limit is not exceeded for any particular service.</comment>
+          </elem>          
+
+          <elem name="msecInterval" multiplicity ="1" type="uint32" default ="100">
+            <tag name="unit" value="msec"/>              
+            <comment>The minimum processing interval in msec units.  This specifies the interval between batches.  For development systems these values should be set relatively
+            high (e.g. 100 msec) to minimize operational overhead on services.  The default is 100 msec. The system may place limits on the batch size and interval so as maximum 
+            throughput limit is not exceeded for any particular service.</comment>
+          </elem>          
+
           <elem name="spec" multiplicity="1" type="Specification">
           <elem name="spec" multiplicity="1" type="Specification">
             <comment>The test specification to execute.</comment>
             <comment>The test specification to execute.</comment>
           </elem>
           </elem>