EML

<?xml version="1.0"?>

<xs:schema targetNamespace="eml://ecoinformatics.org/storedProcedure-2.0.0rc1"

xmlns:xs="http://www.w3.org/2001/XMLSchema"

xmlns:con="eml://ecoinformatics.org/constraint-2.0.0rc1"

xmlns:res="eml://ecoinformatics.org/resource-2.0.0rc1"

xmlns:ent="eml://ecoinformatics.org/entity-2.0.0rc1"

xmlns:doc="eml://ecoinformatics.org/documentation-2.0.0rc1"

xmlns:att="eml://ecoinformatics.org/attribute-2.0.0rc1"

xmlns:phys="eml://ecoinformatics.org/physical-2.0.0rc1"

xmlns:prot="eml://ecoinformatics.org/protocol-2.0.0rc1"

xmlns:cov="eml://ecoinformatics.org/coverage-2.0.0rc1"

xmlns="eml://ecoinformatics.org/storedProcedure-2.0.0rc1">

  <xs:import namespace="eml://ecoinformatics.org/entity-2.0.0rc1"

  schemaLocation="eml-entity.xsd" />

  <xs:import namespace="eml://ecoinformatics.org/documentation-2.0.0rc1"

  schemaLocation="eml-documentation.xsd" />

  <xs:import namespace="eml://ecoinformatics.org/attribute-2.0.0rc1"

  schemaLocation="eml-attribute.xsd" />

  <xs:import namespace="eml://ecoinformatics.org/protocol-2.0.0rc1"

  schemaLocation="eml-protocol.xsd" />

  <xs:import namespace="eml://ecoinformatics.org/physical-2.0.0rc1"

  schemaLocation="eml-physical.xsd" />

  <xs:import namespace="eml://ecoinformatics.org/coverage-2.0.0rc1"

  schemaLocation="eml-coverage.xsd" />

  <xs:import namespace="eml://ecoinformatics.org/resource-2.0.0rc1"

  schemaLocation="eml-resource.xsd" />

  <xs:import namespace="eml://ecoinformatics.org/constraint-2.0.0rc1"

  schemaLocation="eml-constraint.xsd" />

  <xs:annotation>

    <xs:documentation>

    Copyright: 1997-2002 Regents of the University of California,

                            University of New Mexico, and

                            Arizona State University

        Sponsors: National Center for Ecological Analysis and Synthesis and

                  Partnership for Interdisciplinary Studies of Coastal Oceans,

                     University of California Santa Barbara

                  Long-Term Ecological Research Network Office,

                     University of New Mexico

                  Center for Environmental Studies, Arizona State University

   Other funding: National Science Foundation (see README for details)

                  The David and Lucile Packard Foundation

     For Details: http://knb.ecoinformatics.org/

    This program is free software; you can redistribute it and/or modify

    it under the terms of the GNU General Public License as published by

    the Free Software Foundation; either version 2 of the License, or

    (at your option) any later version.

    This program is distributed in the hope that it will be useful,

    but WITHOUT ANY WARRANTY; without even the implied warranty of

    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the

    GNU General Public License for more details.

    You should have received a copy of the GNU General Public License

    along with this program; if not, write to the Free Software

    Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA

    </xs:documentation>

    <xs:appinfo>

      <doc:moduleDocs>

        <doc:moduleName>eml-storedProcedure</doc:moduleName>

        <doc:moduleDescription>The StoredProcedure module is meant to capture

        information on procedures that produce data output in the form of a

        data table. In an RDBMS one can code complex queries and transactions

        into stored procedures and then invoke them directly from front-end

        applications. It allows the optional describtion of any parameters that

        are expected to be passed to the procedure when it is

        called.</doc:moduleDescription>

        <doc:recommendedUsage>Use the StoredProcedure module to document

        datasets that use storedProcedures to retrieve archived

        data.</doc:recommendedUsage>

        <doc:standAlone>yes</doc:standAlone>

      </doc:moduleDocs>

    </xs:appinfo>

  </xs:annotation>

  <xs:element name="storedProcedure" type="StoredProcedureType">

    <xs:annotation>

      <xs:appinfo>

        <doc:tooltip>Stored Procedure&gt;</doc:tooltip>

        <doc:summary>The storedProcedure element documents stored

        procedures.</doc:summary>

        <doc:description>The StoredProcedure element is meant to capture

        information on procedures that produce data output in the form of a

        data table. In an RDBMS one can code complex queries and transactions

        into stored procedures and then invoke them directly from front-end

        applications. This element allows the optional describtion of any

        parameters that are expected to be passed to the procedure when it is

        called.</doc:description>

        <doc:lineage>EML 2.0</doc:lineage>

      </xs:appinfo>

    </xs:annotation>

  </xs:element>

  <xs:complexType name="StoredProcedureType">

    <xs:annotation>

      <xs:appinfo>

        <doc:tooltip>Stored Procedure complex type&gt;</doc:tooltip>

        <doc:summary>Structure for documenting a stored procedure</doc:summary>

        <doc:description>The StoredProcedure complex type defines the structure

        for documenting a stored procedure.</doc:description>

        <doc:lineage>EML 2.0</doc:lineage>

      </xs:appinfo>

    </xs:annotation>

    <xs:choice>

      <xs:sequence>

        <xs:group ref="ent:EntityGroup" />

        <xs:sequence>

          <xs:element name="parameter" type="ParameterType" minOccurs="0"

          maxOccurs="unbounded">

            <xs:annotation>

              <xs:appinfo>

                <doc:tooltip>Parameter</doc:tooltip>

                <doc:summary>A parameter that is required as input to the

                stored procedure.</doc:summary>

                <doc:description>The parameter elements defines the fields that

                may be required to invoke a stored procedure.</doc:description>

                <doc:lineage>EML 2.0</doc:lineage>

              </xs:appinfo>

            </xs:annotation>

          </xs:element>

        </xs:sequence>

      </xs:sequence>

      <xs:element name="references" type="xs:string" />

    </xs:choice>

    <xs:attribute name="id" type="xs:string" use="optional" />

    <xs:attribute name="system" type="xs:string" use="optional" />

    <xs:attribute name="scope" type="res:ScopeType" use="optional"

    default="document" />

  </xs:complexType>

  <xs:complexType name="ParameterType">

    <xs:annotation>

      <xs:appinfo>

        <doc:tooltip>Parameter complex type</doc:tooltip>

        <doc:summary>The structure for defining a parameter that is required as

        input to the stored procedure.</doc:summary>

        <doc:description>The parameter complex type defines the structure for

        documenting the parameters that may be required to invoke a stored

        procedure.</doc:description>

        <doc:lineage>EML 2.0</doc:lineage>

      </xs:appinfo>

    </xs:annotation>

    <xs:sequence>

      <xs:element name="name" type="xs:string">

        <xs:annotation>

          <xs:appinfo>

            <doc:tooltip>Parameter Name</doc:tooltip>

            <doc:summary>The name of the parameter.</doc:summary>

            <doc:description>The value of the name field is the name of the

            parameter.</doc:description>

            <doc:example>SiteID</doc:example>

            <doc:lineage>EML 2.0</doc:lineage>

          </xs:appinfo>

        </xs:annotation>

      </xs:element>

      <xs:element name="datatype">

        <xs:annotation>

          <xs:appinfo>

            <doc:tooltip>Data type</doc:tooltip>

            <doc:summary>The data type for the parameter value.</doc:summary>

            <doc:description>The value of the datatype field is the data type

            of the parameter. Datatype has an attribute of typeSystem, with a

            default of "http://www.w3.org/2001/XMLSchema-datatypes". The user 

            can specify another system such as "oracle" or "sql server"

            The data type used should conform to the system type.

            </doc:description>

            <doc:example>string</doc:example>

            <doc:example>varchar2</doc:example>

            <doc:lineage>EML 2.0</doc:lineage>

          </xs:appinfo>

        </xs:annotation>

        <xs:complexType>

          <xs:simpleContent>

            <xs:extension base="xs:string">

              <xs:attribute name="typeSystem" type="xs:string" use="optional"

              default="http://www.w3.org/2001/XMLSchema-datatypes" />

            </xs:extension>

          </xs:simpleContent>

        </xs:complexType>

      </xs:element>

      <xs:element name="required" type="xs:boolean">

        <xs:annotation>

          <xs:appinfo>

            <doc:tooltip>Required</doc:tooltip>

            <doc:summary>Whether or not the parameter is

            required.</doc:summary>

            <doc:description>The required field is used to document whether

            the parameter being described is or is not required when invoking

            the stored procedure.</doc:description>

            <doc:example>true</doc:example>

            <doc:lineage>EML 2.0</doc:lineage>

          </xs:appinfo>

        </xs:annotation>

      </xs:element>

      <xs:element name="repeats" type="xs:boolean">

        <xs:annotation>

          <xs:appinfo>

            <doc:tooltip>Repeats</doc:tooltip>

            <doc:summary>Whether or not the parameter repeats.</doc:summary>

            <doc:description>The repeats field is used to document whether or ]

            not the parameter being described is repeted when invoking

            the stored procedure.</doc:description>

            <doc:example>true</doc:example>

            <doc:lineage>EML 2.0</doc:lineage>

          </xs:appinfo>

        </xs:annotation>

      </xs:element>

    </xs:sequence>

  </xs:complexType>

</xs:schema>