Copyright 2007 The Trustees of Indiana University Licensed under an Apache-style license (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.cs.indiana.edu/dde/LICENSE-myLEAD Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. Schema for Common Elements in the myLEAD Activity Schemas Since OGSA-DAI combines all of the separate OGSA-DAI and myLEAD activity schemas, any myLEAD types that are needed in multiple activities are included in this single myLEAD types schema file. This schema file is then imported into the OGSA-DAI genera_types.xsd file. Author: Scott Jensen, scjensen@cs.indiana.edu This type is used to include selected method parameters in a fatal or nonfatal error. This type is used to communucate the details regarding a specific fatal or nonfatal error. When importing or updating, particularly in batch mode, there may be more than one error. In that case, a separate instance of this type should be included in the error summary for each error. If data was not processed (e.g., An object, attribute, or element was not processed) then the XML input for that should be included in the data element. Many of the operations write any problems to a temp table when executing stored procedures. These messages can be dumped to the response in the case of an error being encountered. If an operation encounters an error, an instance of this type should be populated for the status response with a summary of the error(s) that occurred. The two attributes indicate whether the operation had any fatal or nonfatal errors (or both). For each error, if additional details are available, an instance of the fatalError or nonFatalError should be included to provide those details. The programmer may also have included the XML of the original operation that caused the error. This is optional since the fatal and nonfatal error details may also include that fragment of the operation that caused that specific error.