<geographicCoverage id="" scope="document" system="">
  <geographicDescription>{1,1}</geographicDescription>
  <boundingCoordinates>{1,1}</boundingCoordinates>
  <datasetGPolygon>{0,unbounded}</datasetGPolygon>
</geographicCoverage>

<xs:element name="geographicCoverage" type="GeographicCoverage">
  <xs:annotation>
    <xs:appinfo>
      <doc:tooltip>Geographic coverage</doc:tooltip>
      <doc:summary>Geographic coverage information.</doc:summary>
      <doc:description>Geographic Coverage is a container for spatial
              information about a project, a resource, or an entity within a
              resource. It allows a bounding box for the overall coverage (in
              lat long), and also allows descriptin of arbitrary polygons with
              exclusions.</doc:description>
      <doc:example>Please see the individual sub fields for specific
              examples.</doc:example>
    </xs:appinfo>
  </xs:annotation>
</xs:element>

<xs:element name="geographicDescription" type="xs:string">
  <xs:annotation>
    <xs:appinfo>
      <doc:tooltip>Description of geographic extent</doc:tooltip>
      <doc:summary>Short description of the geographic areal domain of
              the data set.</doc:summary>
      <doc:description>A geographic extent description is especially
              important when the extent of the data set is not well described
              by the "Bounding_Rectangle_Coordinates", or in the case of data
              which are not specifically geospatial, to provide a geographic
              setting for the item being documented. Assuming the
              "Bounding_Rectangle_Coordinates" do not adequately describe the
              extent of the data set, the discrepancy can be identified and
              described in this data element. If the item being documented is
              not specifically geospatial, the "Bounding_Rectangle_Coordinates"
              can define a general polygon, such as a rectangle around a
              country, with this "Description_of_Geographic_Extent" element
              containing a disclaimer concerning the
              "Bounding_Rectangle_Coordinates" and/or further detail concerning
              the geographic area of concern for the item being documented. For
              example, a study of the diseases of salmon may not have a
              specific geographic extent associated with it, but the salmon
              involved in the study were collected in Washington and Oregon
              states, thus the "Bounding_Rectangle_Coordinates" might form a
              general rectangle around the states of Washington and Oregon, but
              the "Description_of_Geographic_Extent" might describe the fact
              that the extent within Washington and Oregon included only
              certain rivers within those states. This data element differs
              from the standard data element "Place_Keyword" in that it allows
              a free text description of the geographic extent, rather than
              just a list of words or phrases useful as an index of location
              names associated with the data set.</doc:description>
      <doc:example>Examples include, "Manistee River watershed",
              "extent of 7 1/2 minute quads containing any property belonging
              to Yellowstone National Park", or "ponds and reservoirs larger
              than 2 acres in Jefferson County, Colorado". This is especially
              important when the extent of the data set is not well described
              by the "Bounding_Rectangle_Coordinates".</doc:example>
    </xs:appinfo>
  </xs:annotation>
</xs:element>

<boundingCoordinates>
  <westBoundingCoordinate>{1,1}</westBoundingCoordinate>
  <eastBoundingCoordinate>{1,1}</eastBoundingCoordinate>
  <northBoundingCoordinate>{1,1}</northBoundingCoordinate>
  <southBoundingCoordinate>{1,1}</southBoundingCoordinate>
  <boundingAltitudes>{0,1}</boundingAltitudes>
</boundingCoordinates>

<xs:element name="boundingCoordinates">
  <xs:annotation>
    <xs:appinfo>
      <doc:tooltip>Bounding coordinates</doc:tooltip>
      <doc:summary>The 4 points (latitude and longitude pairs) that
              define a bounding box on the earth's surface. To define a single
              point, use the same point in both lat/lon pairs.</doc:summary>
      <doc:description>The limits of coverage of a data set expressed
              by latitude and longitude values in the order western-most,
              eastern-most, northern-most, and southern-most. For data sets
              that include a complete band of latitude around the earth, the
              West Bounding Coordinate shall be assigned the value -180.0, and
              the East Bounding Coordinate shall be assigned the value 180.0 If
              your bounding area is a single point, use the same values for
              northBoundingCoordinate and southBoundingCoordinate, as well as
              the same value for westBoundingCoordinate and
              eastBoundingCoordinate. This will define the same lat/lon pairs
              since all four are required.</doc:description>
      <doc:example>Please see the individual sub-fields for specific
              examples.</doc:example>
    </xs:appinfo>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="westBoundingCoordinate" type="xs:string">
        <xs:annotation>
          <xs:appinfo>
            <doc:tooltip>West bounding coordinate</doc:tooltip>
            <doc:summary>Western-most coordinate of the limit of
                    coverage for a bounding box, expressed in degrees of
                    longitude.</doc:summary>
            <doc:description>The west bounding coordinate field defines
                    the western-most point of the bounding box that is being
                    described. This longitude coordinate should be expressed in
                    decimal fractions of degrees. Whole degrees of longitude
                    shall be represented by a three-digit decimal number
                    ranging from 0 through 180. When a decimal fraction of a
                    degree is specified, it should be separated from the whole
                    number of degrees by a decimal point. Decimal fractions of
                    a degree may be expressed to the precision desired.
                    Longitudes east of the prime meridian shall be specified by
                    a plus sign (+), or by the absence of a minus sign (-),
                    preceding the three digits designating degrees of
                    longitude. Longitudes west of the meridian shall be
                    designated by minus sign (-) preceding the three digits
                    designating degrees. A point on the prime meridian shall be
                    assigned to the Eastern Hemisphere. A point on the 180th
                    meridian shall be assigned to the Western Hemisphere. One
                    exception to this last convention is permitted. For the
                    special condition of describing a band of latitude around
                    the earth, the East Bounding Coordinate data element shall
                    be assigned the value +180 (180) degrees.</doc:description>
            <doc:example>'-118.25', '+25', '45.247'</doc:example>
          </xs:appinfo>
        </xs:annotation>
      </xs:element>
      <xs:element name="eastBoundingCoordinate" type="xs:string">
        <xs:annotation>
          <xs:appinfo>
            <doc:tooltip>East bounding coordinate</doc:tooltip>
            <doc:summary>Eastern-most coordinate of the limit of
                    coverage of a bounding box, expressed in degrees of
                    longitude.</doc:summary>
            <doc:description>The east bounding coordinate field defines
                    the eastern-most point of the bounding box that is being
                    described. This longitude coordinate should be expressed in
                    decimal fractions of degrees. Whole degrees of longitude
                    shall be represented by a three-digit decimal number
                    ranging from 0 through 180. When a decimal fraction of a
                    degree is specified, it should be separated from the whole
                    number of degrees by a decimal point. Decimal fractions of
                    a degree may be expressed to the precision desired.
                    Longitudes east of the prime meridian shall be specified by
                    a plus sign (+), or by the absence of a minus sign (-),
                    preceding the three digits designating degrees of
                    longitude. Longitudes west of the meridian shall be
                    designated by minus sign (-) preceding the three digits
                    designating degrees. A point on the prime meridian shall be
                    assigned to the Eastern Hemisphere. A point on the 180th
                    meridian shall be assigned to the Western Hemisphere. One
                    exception to this last convention is permitted. For the
                    special condition of describing a band of latitude around
                    the earth, the East Bounding Coordinate data element shall
                    be assigned the value +180 (180) degrees.</doc:description>
            <doc:example>'-118.25', '+25', '45.247'</doc:example>
          </xs:appinfo>
        </xs:annotation>
      </xs:element>
      <xs:element name="northBoundingCoordinate" type="xs:string">
        <xs:annotation>
          <xs:appinfo>
            <doc:tooltip>North bounding coordinate</doc:tooltip>
            <doc:summary>Northern-most coordinate of the limit of
                    coverage expressed in latitude.</doc:summary>
            <doc:description>The north bounding coordinate field
                    defines the northern-most point of the bounding box that is
                    being described. This latitude coordinate should be
                    expressed in decimal fractions of degrees. Whole degrees of
                    latitude shall be represented by a two-digit decimal number
                    ranging from 0 through 90. When a decimal fraction of a
                    degree is specified, it shall be separated from the whole
                    number of degrees by a decimal point. Decimal fractions of
                    a degree may be expressed to the precision desired.
                    Latitudes north of the equator shall be specified by a plus
                    sign (+), or by the absence of a minus sign (-), preceding
                    the two digits designating degrees. Latitudes south of the
                    Equator shall be designated by a minus sign (-) preceding
                    the two digits designating degrees. A point on the Equator
                    shall be assigned to the Northern Hemisphere. Any spatial
                    address with a latitude of +90 (90) or -90 degrees will
                    specify the position at the North or South Pole,
                    respectively.</doc:description>
            <doc:example>'-18.44', '+44.35', '86'</doc:example>
          </xs:appinfo>
        </xs:annotation>
      </xs:element>
      <xs:element name="southBoundingCoordinate" type="xs:string">
        <xs:annotation>
          <xs:appinfo>
            <doc:tooltip>South bounding coordinate</doc:tooltip>
            <doc:summary>Southern-most coordinate of the limit of
                    coverage expressed in latitude.</doc:summary>
            <doc:description>The south bounding coordinate field
                    defines the southern-most point of the bounding box that is
                    being described. This latitude coordinate should be
                    expressed in decimal fractions of degrees. Whole degrees of
                    latitude shall be represented by a two-digit decimal number
                    ranging from 0 through 90. When a decimal fraction of a
                    degree is specified, it shall be separated from the whole
                    number of degrees by a decimal point. Decimal fractions of
                    a degree may be expressed to the precision desired.
                    Latitudes north of the equator shall be specified by a plus
                    sign (+), or by the absence of a minus sign (-), preceding
                    the two digits designating degrees. Latitudes south of the
                    Equator shall be designated by a minus sign (-) preceding
                    the two digits designating degrees. A point on the Equator
                    shall be assigned to the Northern Hemisphere. Any spatial
                    address with a latitude of +90 (90) or -90 degrees will
                    specify the position at the North or South Pole,
                    respectively.</doc:description>
            <doc:example>'-18.44', '+44.35', '86'</doc:example>
          </xs:appinfo>
        </xs:annotation>
      </xs:element>
      <xs:element name="boundingAltitudes" minOccurs="0">
        <xs:annotation>
          <xs:appinfo>
            <doc:tooltip>Bounding altitudes</doc:tooltip>
            <doc:summary>The limits of coverage of a data set expressed
                    by altitude.</doc:summary>
            <doc:description>The bounding altitude field is intended to
                    contain altitudinal (elevation) measurements in relation to
                    the bounding box being described. It allows for minimum and
                    maximum altitude fields, as well as a field for the units
                    of measure. The combination of these fields provide the
                    vertical extent information for the bounding box. The units
                    should refer to an accepted datum as the
                    baseline.</doc:description>
            <doc:example>Please see the individual sub-fields for
                    specific examples.</doc:example>
          </xs:appinfo>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="altitudeMinimum" type="xs:string">
              <xs:annotation>
                <xs:appinfo>
                  <doc:tooltip>Minimum altitude</doc:tooltip>
                  <doc:summary>The minimum altitude extent of
                          coverage.</doc:summary>
                  <doc:description>The minimum altitude extent of
                          coverage for the bounding box that is being
                          described. The minimum altitude should be in
                          reference to a known datum, which should be described
                          in the altitude units field.</doc:description>
                  <doc:example>'12', '100.6' (e.g meters above Mean
                          Lowest Low Water)</doc:example>
                </xs:appinfo>
              </xs:annotation>
            </xs:element>
            <xs:element name="altitudeMaximum" type="xs:string">
              <xs:annotation>
                <xs:appinfo>
                  <doc:tooltip>Maximum altitude</doc:tooltip>
                  <doc:summary>The maximum altitude extent of
                          coverage.</doc:summary>
                  <doc:description>The maximum altitude extent of
                          coverage for the bounding box that is being
                          described. The maximum altitude should be in
                          reference to a known datum, which should be described
                          in the altitude units field.</doc:description>
                  <doc:example>'12', '100.6' (e.g meters above Mean
                          Lowest Low Water)</doc:example>
                </xs:appinfo>
              </xs:annotation>
            </xs:element>
            <xs:element name="altitudeUnits" type="xs:string">
              <xs:annotation>
                <xs:appinfo>
                  <doc:tooltip>Units of altitude</doc:tooltip>
                  <doc:summary>Units in which altitude is
                          measured.</doc:summary>
                  <doc:description>Units in which altitude is measured.
                          This field should be in relation to a known datum
                          which is described in the units.</doc:description>
                  <doc:example>Meters (above Mean Lowest Low
                          Water)</doc:example>
                </xs:appinfo>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>

<xs:element name="westBoundingCoordinate" type="xs:string">
  <xs:annotation>
    <xs:appinfo>
      <doc:tooltip>West bounding coordinate</doc:tooltip>
      <doc:summary>Western-most coordinate of the limit of
                    coverage for a bounding box, expressed in degrees of
                    longitude.</doc:summary>
      <doc:description>The west bounding coordinate field defines
                    the western-most point of the bounding box that is being
                    described. This longitude coordinate should be expressed in
                    decimal fractions of degrees. Whole degrees of longitude
                    shall be represented by a three-digit decimal number
                    ranging from 0 through 180. When a decimal fraction of a
                    degree is specified, it should be separated from the whole
                    number of degrees by a decimal point. Decimal fractions of
                    a degree may be expressed to the precision desired.
                    Longitudes east of the prime meridian shall be specified by
                    a plus sign (+), or by the absence of a minus sign (-),
                    preceding the three digits designating degrees of
                    longitude. Longitudes west of the meridian shall be
                    designated by minus sign (-) preceding the three digits
                    designating degrees. A point on the prime meridian shall be
                    assigned to the Eastern Hemisphere. A point on the 180th
                    meridian shall be assigned to the Western Hemisphere. One
                    exception to this last convention is permitted. For the
                    special condition of describing a band of latitude around
                    the earth, the East Bounding Coordinate data element shall
                    be assigned the value +180 (180) degrees.</doc:description>
      <doc:example>'-118.25', '+25', '45.247'</doc:example>
    </xs:appinfo>
  </xs:annotation>
</xs:element>

<xs:element name="eastBoundingCoordinate" type="xs:string">
  <xs:annotation>
    <xs:appinfo>
      <doc:tooltip>East bounding coordinate</doc:tooltip>
      <doc:summary>Eastern-most coordinate of the limit of
                    coverage of a bounding box, expressed in degrees of
                    longitude.</doc:summary>
      <doc:description>The east bounding coordinate field defines
                    the eastern-most point of the bounding box that is being
                    described. This longitude coordinate should be expressed in
                    decimal fractions of degrees. Whole degrees of longitude
                    shall be represented by a three-digit decimal number
                    ranging from 0 through 180. When a decimal fraction of a
                    degree is specified, it should be separated from the whole
                    number of degrees by a decimal point. Decimal fractions of
                    a degree may be expressed to the precision desired.
                    Longitudes east of the prime meridian shall be specified by
                    a plus sign (+), or by the absence of a minus sign (-),
                    preceding the three digits designating degrees of
                    longitude. Longitudes west of the meridian shall be
                    designated by minus sign (-) preceding the three digits
                    designating degrees. A point on the prime meridian shall be
                    assigned to the Eastern Hemisphere. A point on the 180th
                    meridian shall be assigned to the Western Hemisphere. One
                    exception to this last convention is permitted. For the
                    special condition of describing a band of latitude around
                    the earth, the East Bounding Coordinate data element shall
                    be assigned the value +180 (180) degrees.</doc:description>
      <doc:example>'-118.25', '+25', '45.247'</doc:example>
    </xs:appinfo>
  </xs:annotation>
</xs:element>

<xs:element name="northBoundingCoordinate" type="xs:string">
  <xs:annotation>
    <xs:appinfo>
      <doc:tooltip>North bounding coordinate</doc:tooltip>
      <doc:summary>Northern-most coordinate of the limit of
                    coverage expressed in latitude.</doc:summary>
      <doc:description>The north bounding coordinate field
                    defines the northern-most point of the bounding box that is
                    being described. This latitude coordinate should be
                    expressed in decimal fractions of degrees. Whole degrees of
                    latitude shall be represented by a two-digit decimal number
                    ranging from 0 through 90. When a decimal fraction of a
                    degree is specified, it shall be separated from the whole
                    number of degrees by a decimal point. Decimal fractions of
                    a degree may be expressed to the precision desired.
                    Latitudes north of the equator shall be specified by a plus
                    sign (+), or by the absence of a minus sign (-), preceding
                    the two digits designating degrees. Latitudes south of the
                    Equator shall be designated by a minus sign (-) preceding
                    the two digits designating degrees. A point on the Equator
                    shall be assigned to the Northern Hemisphere. Any spatial
                    address with a latitude of +90 (90) or -90 degrees will
                    specify the position at the North or South Pole,
                    respectively.</doc:description>
      <doc:example>'-18.44', '+44.35', '86'</doc:example>
    </xs:appinfo>
  </xs:annotation>
</xs:element>

<xs:element name="southBoundingCoordinate" type="xs:string">
  <xs:annotation>
    <xs:appinfo>
      <doc:tooltip>South bounding coordinate</doc:tooltip>
      <doc:summary>Southern-most coordinate of the limit of
                    coverage expressed in latitude.</doc:summary>
      <doc:description>The south bounding coordinate field
                    defines the southern-most point of the bounding box that is
                    being described. This latitude coordinate should be
                    expressed in decimal fractions of degrees. Whole degrees of
                    latitude shall be represented by a two-digit decimal number
                    ranging from 0 through 90. When a decimal fraction of a
                    degree is specified, it shall be separated from the whole
                    number of degrees by a decimal point. Decimal fractions of
                    a degree may be expressed to the precision desired.
                    Latitudes north of the equator shall be specified by a plus
                    sign (+), or by the absence of a minus sign (-), preceding
                    the two digits designating degrees. Latitudes south of the
                    Equator shall be designated by a minus sign (-) preceding
                    the two digits designating degrees. A point on the Equator
                    shall be assigned to the Northern Hemisphere. Any spatial
                    address with a latitude of +90 (90) or -90 degrees will
                    specify the position at the North or South Pole,
                    respectively.</doc:description>
      <doc:example>'-18.44', '+44.35', '86'</doc:example>
    </xs:appinfo>
  </xs:annotation>
</xs:element>

<boundingAltitudes>
  <altitudeMinimum>{1,1}</altitudeMinimum>
  <altitudeMaximum>{1,1}</altitudeMaximum>
  <altitudeUnits>{1,1}</altitudeUnits>
</boundingAltitudes>

<xs:element name="boundingAltitudes" minOccurs="0">
  <xs:annotation>
    <xs:appinfo>
      <doc:tooltip>Bounding altitudes</doc:tooltip>
      <doc:summary>The limits of coverage of a data set expressed
                    by altitude.</doc:summary>
      <doc:description>The bounding altitude field is intended to
                    contain altitudinal (elevation) measurements in relation to
                    the bounding box being described. It allows for minimum and
                    maximum altitude fields, as well as a field for the units
                    of measure. The combination of these fields provide the
                    vertical extent information for the bounding box. The units
                    should refer to an accepted datum as the
                    baseline.</doc:description>
      <doc:example>Please see the individual sub-fields for
                    specific examples.</doc:example>
    </xs:appinfo>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="altitudeMinimum" type="xs:string">
        <xs:annotation>
          <xs:appinfo>
            <doc:tooltip>Minimum altitude</doc:tooltip>
            <doc:summary>The minimum altitude extent of
                          coverage.</doc:summary>
            <doc:description>The minimum altitude extent of
                          coverage for the bounding box that is being
                          described. The minimum altitude should be in
                          reference to a known datum, which should be described
                          in the altitude units field.</doc:description>
            <doc:example>'12', '100.6' (e.g meters above Mean
                          Lowest Low Water)</doc:example>
          </xs:appinfo>
        </xs:annotation>
      </xs:element>
      <xs:element name="altitudeMaximum" type="xs:string">
        <xs:annotation>
          <xs:appinfo>
            <doc:tooltip>Maximum altitude</doc:tooltip>
            <doc:summary>The maximum altitude extent of
                          coverage.</doc:summary>
            <doc:description>The maximum altitude extent of
                          coverage for the bounding box that is being
                          described. The maximum altitude should be in
                          reference to a known datum, which should be described
                          in the altitude units field.</doc:description>
            <doc:example>'12', '100.6' (e.g meters above Mean
                          Lowest Low Water)</doc:example>
          </xs:appinfo>
        </xs:annotation>
      </xs:element>
      <xs:element name="altitudeUnits" type="xs:string">
        <xs:annotation>
          <xs:appinfo>
            <doc:tooltip>Units of altitude</doc:tooltip>
            <doc:summary>Units in which altitude is
                          measured.</doc:summary>
            <doc:description>Units in which altitude is measured.
                          This field should be in relation to a known datum
                          which is described in the units.</doc:description>
            <doc:example>Meters (above Mean Lowest Low
                          Water)</doc:example>
          </xs:appinfo>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>

<xs:element name="altitudeMinimum" type="xs:string">
  <xs:annotation>
    <xs:appinfo>
      <doc:tooltip>Minimum altitude</doc:tooltip>
      <doc:summary>The minimum altitude extent of
                          coverage.</doc:summary>
      <doc:description>The minimum altitude extent of
                          coverage for the bounding box that is being
                          described. The minimum altitude should be in
                          reference to a known datum, which should be described
                          in the altitude units field.</doc:description>
      <doc:example>'12', '100.6' (e.g meters above Mean
                          Lowest Low Water)</doc:example>
    </xs:appinfo>
  </xs:annotation>
</xs:element>

<xs:element name="altitudeMaximum" type="xs:string">
  <xs:annotation>
    <xs:appinfo>
      <doc:tooltip>Maximum altitude</doc:tooltip>
      <doc:summary>The maximum altitude extent of
                          coverage.</doc:summary>
      <doc:description>The maximum altitude extent of
                          coverage for the bounding box that is being
                          described. The maximum altitude should be in
                          reference to a known datum, which should be described
                          in the altitude units field.</doc:description>
      <doc:example>'12', '100.6' (e.g meters above Mean
                          Lowest Low Water)</doc:example>
    </xs:appinfo>
  </xs:annotation>
</xs:element>

<xs:element name="altitudeUnits" type="xs:string">
  <xs:annotation>
    <xs:appinfo>
      <doc:tooltip>Units of altitude</doc:tooltip>
      <doc:summary>Units in which altitude is
                          measured.</doc:summary>
      <doc:description>Units in which altitude is measured.
                          This field should be in relation to a known datum
                          which is described in the units.</doc:description>
      <doc:example>Meters (above Mean Lowest Low
                          Water)</doc:example>
    </xs:appinfo>
  </xs:annotation>
</xs:element>

<datasetGPolygon>
  <datasetGPolygonOuterGRing>{1,1}</datasetGPolygonOuterGRing>
  <datasetGPolygonExclusionGRing>{0,unbounded}</datasetGPolygonExclusionGRing>
</datasetGPolygon>

<xs:element name="datasetGPolygon" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:appinfo>
      <doc:tooltip>Polygon data set</doc:tooltip>
      <doc:summary>This construct creates a spatial ring with a
              hollow center.</doc:summary>
      <doc:description>This construct creates a spatial ring with a
              hollow center.  This doughnut shape is specified by the outer
              ring (datasetGPolygonOuterRing) and the inner exclusion zone
              (datasetGPolygonExclusionGRing) which can be thought of as the
              hole in the center of a doughnut.  This is useful for defining
              areas such as the shores of a pond where you only want to specify
              the shore excluding the pond itself.</doc:description>
      <doc:example>Please see the individual sub-fields for specific
              examples.</doc:example>
    </xs:appinfo>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="datasetGPolygonOuterGRing">
        <xs:annotation>
          <xs:appinfo>
            <doc:tooltip>Outer polygon</doc:tooltip>
            <doc:summary>The outer containment loop of a datasetGPolygon.</doc:summary>
            <doc:description>The outer containment loop of a
                    datasetGPolygon.  This is the outer part of the doughnut
                    shape that encompasses the broadest area of coverage</doc:description>
          </xs:appinfo>
        </xs:annotation>
        <xs:complexType>
          <xs:choice>
            <xs:sequence>
              <xs:element name="gRingPoint" type="GRingPointType" minOccurs="3" maxOccurs="unbounded"/>
            </xs:sequence>
            <xs:element name="gRing" type="GRingPointType"/>
          </xs:choice>
        </xs:complexType>
      </xs:element>
      <xs:element name="datasetGPolygonExclusionGRing" minOccurs="0" maxOccurs="unbounded">
        <xs:annotation>
          <xs:appinfo>
            <doc:tooltip>Exclusion polygon</doc:tooltip>
            <doc:summary>Data Set G-Polygon Exclusion G-Ring, the
                    closed nonintersecting boundary of a void area (or hole in
                    an interior area).</doc:summary>
            <doc:description>Data Set G-Polygon Exclusion G-Ring, the
                    closed nonintersecting boundary of a void area (or hole in
                    an interior area).  This is the center of the doughnut
                    shape created by the datasetGPolygon.</doc:description>
          </xs:appinfo>
        </xs:annotation>
        <xs:complexType>
          <xs:choice>
            <xs:element name="gRingPoint" type="GRingPointType" maxOccurs="unbounded"/>
            <xs:element name="gRing" type="GRingPointType"/>
          </xs:choice>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>

<datasetGPolygonOuterGRing>
  <gRingPoint>{3,unbounded}</gRingPoint>
  <gRing>{1,1}</gRing>
</datasetGPolygonOuterGRing>

<xs:element name="datasetGPolygonOuterGRing">
  <xs:annotation>
    <xs:appinfo>
      <doc:tooltip>Outer polygon</doc:tooltip>
      <doc:summary>The outer containment loop of a datasetGPolygon.</doc:summary>
      <doc:description>The outer containment loop of a
                    datasetGPolygon.  This is the outer part of the doughnut
                    shape that encompasses the broadest area of coverage</doc:description>
    </xs:appinfo>
  </xs:annotation>
  <xs:complexType>
    <xs:choice>
      <xs:sequence>
        <xs:element name="gRingPoint" type="GRingPointType" minOccurs="3" maxOccurs="unbounded"/>
      </xs:sequence>
      <xs:element name="gRing" type="GRingPointType"/>
    </xs:choice>
  </xs:complexType>
</xs:element>

<gRingPoint>
  <gRingLatitude>{1,1}</gRingLatitude>
  <gRingLongitude>{1,1}</gRingLongitude>
</gRingPoint>

<xs:element name="gRingPoint" type="GRingPointType" minOccurs="3" maxOccurs="unbounded"/>

<xs:element name="gRingLatitude" type="xs:string">
  <xs:annotation>
    <xs:appinfo>
      <doc:tooltip>G-Ring Latitude</doc:tooltip>
      <doc:summary/>
      <doc:description>The latitude of a point of the
            g-ring.</doc:description>
    </xs:appinfo>
  </xs:annotation>
</xs:element>

<xs:element name="gRingLongitude" type="xs:string">
  <xs:annotation>
    <xs:appinfo>
      <doc:tooltip>G-Ring Longitude</doc:tooltip>
      <doc:summary/>
      <doc:description>The longitude of a point of the
            g-ring.</doc:description>
    </xs:appinfo>
  </xs:annotation>
</xs:element>

<gRing>
  <gRingLatitude>{1,1}</gRingLatitude>
  <gRingLongitude>{1,1}</gRingLongitude>
</gRing>

<xs:element name="gRing" type="GRingPointType"/>

<datasetGPolygonExclusionGRing>
  <gRingPoint>{1,unbounded}</gRingPoint>
  <gRing>{1,1}</gRing>
</datasetGPolygonExclusionGRing>

<xs:element name="datasetGPolygonExclusionGRing" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:appinfo>
      <doc:tooltip>Exclusion polygon</doc:tooltip>
      <doc:summary>Data Set G-Polygon Exclusion G-Ring, the
                    closed nonintersecting boundary of a void area (or hole in
                    an interior area).</doc:summary>
      <doc:description>Data Set G-Polygon Exclusion G-Ring, the
                    closed nonintersecting boundary of a void area (or hole in
                    an interior area).  This is the center of the doughnut
                    shape created by the datasetGPolygon.</doc:description>
    </xs:appinfo>
  </xs:annotation>
  <xs:complexType>
    <xs:choice>
      <xs:element name="gRingPoint" type="GRingPointType" maxOccurs="unbounded"/>
      <xs:element name="gRing" type="GRingPointType"/>
    </xs:choice>
  </xs:complexType>
</xs:element>

<gRingPoint>
  <gRingLatitude>{1,1}</gRingLatitude>
  <gRingLongitude>{1,1}</gRingLongitude>
</gRingPoint>

<xs:element name="gRingPoint" type="GRingPointType" maxOccurs="unbounded"/>

<gRing>
  <gRingLatitude>{1,1}</gRingLatitude>
  <gRingLongitude>{1,1}</gRingLongitude>
</gRing>

<xs:element name="gRing" type="GRingPointType"/>

<temporalCoverage id="" scope="document" system="">
  <singleDateTime>{1,unbounded}</singleDateTime>
  <rangeOfDates>{1,1}</rangeOfDates>
</temporalCoverage>

<xs:element name="temporalCoverage">
  <xs:annotation>
    <xs:appinfo>
      <doc:tooltip>Temporal coverage</doc:tooltip>
      <doc:summary>Temporal coverage information.</doc:summary>
      <doc:description>This field specifies temporal coverage, and
              allows coverages to be a single point in time, multiple points in
              time, or a range of dates. Dates can be expressed in tems of both
              calander dates and geologic dating systems.</doc:description>
      <doc:example>Please see the individual sub fields for specific
              examples.</doc:example>
    </xs:appinfo>
  </xs:annotation>
  <xs:complexType>
    <xs:complexContent>
      <xs:extension base="TemporalCoverage">
        <xs:attribute name="system" type="res:SystemType" use="optional"/>
        <xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
      </xs:extension>
    </xs:complexContent>
  </xs:complexType>
</xs:element>

<singleDateTime>
  <calendarDate>{1,1}</calendarDate>
  <time>{0,1}</time>
  <alternativeTimeScale>{1,1}</alternativeTimeScale>
</singleDateTime>

<xs:element name="singleDateTime" type="SingleDateTimeType" maxOccurs="unbounded">
  <xs:annotation>
    <xs:appinfo>
      <doc:tooltip>Single Date/Time</doc:tooltip>
      <doc:summary>Means of encoding a single date and
              time</doc:summary>
      <doc:description>The singleDateTime field is intended to
              describe a
              single date and time for an event. There is a choice between two
              options: a calendar date with a time, or a geologic
              age.</doc:description>
      <doc:example>Please see the individual sub-elements for
              example.</doc:example>
    </xs:appinfo>
  </xs:annotation>
</xs:element>

<xs:element name="calendarDate" type="res:yearDate">
  <xs:annotation>
    <xs:appinfo>
      <doc:tooltip>Calendar date</doc:tooltip>
      <doc:summary>The calendar date for an event.</doc:summary>
      <doc:description>The calendar date field is used to express a
              date, giving the year, month, and day. The format should be one
              that complies with the International Standards Organization's
              standard 8601. The recommended format for EML is YYYY-MM-DD,
              where Y is the four digit year, M is the two digit month code
              (01 - 12, where January = 01), and D is the two digit day of
              the month (01 - 31). This field can also be used to enter just 
	      the year portion of a date.</doc:description>
      <doc:example>2001-01-01</doc:example>
      <doc:example>2001-10-12</doc:example>
      <doc:example>2001</doc:example>
      <doc:example>1895</doc:example>
    </xs:appinfo>
  </xs:annotation>
</xs:element>

<xs:element name="time" type="xs:time" minOccurs="0">
  <xs:annotation>
    <xs:appinfo>
      <doc:tooltip>Time of day</doc:tooltip>
      <doc:summary>The time of day for an event.</doc:summary>
      <doc:description>The time field is used to express the hour
              (and optionally minute, or minute and second) of the day for an
              event, and should comply with the International Standards
              Organization's standard 8601. The recommended format for EML is
              hh:mm:ssTZD, where hh is the two digit hour of the day, mm is
              the two digit minute of the hour, and ss is the two digit
              second of the minute. TZD stands for Time Zone Designator which
              is used to handle time zone offsets. Times may be expressed in
              two ways: 1) UTC (Coordinated Universal Time, also known as
              Greenwich Mean Time, or GMT), with a special UTC designator
              ("Z"), 2) local time, together with a time zone offset in hours
              and minutes. A time zone offset of "+hh:mm" indicates that the
              date/time uses a local time zone which is "hh" hours and "mm"
              minutes ahead of UTC. A time zone offset of "-hh:mm" indicates
              that the date/time uses a local time zone which is "hh" hours
              and "mm" minutes behind UTC.</doc:description>
      <doc:example>1) 08:31:22Z , which means eight thirty one and 22
              seconds in the morning at Coordinated Universal Time (Greenwich
              Mean Time). 2) 14:06:09-08:00 , which means six minutes, nine
              seconds past two o'clock p.m., Pacific Standard Time (which is
              offset eight hours behind UTC)</doc:example>
    </xs:appinfo>
  </xs:annotation>
</xs:element>

<alternativeTimeScale>
  <timeScaleName>{1,1}</timeScaleName>
  <timeScaleAgeEstimate>{1,1}</timeScaleAgeEstimate>
  <timeScaleAgeUncertainty>{0,1}</timeScaleAgeUncertainty>
  <timeScaleAgeExplanation>{0,1}</timeScaleAgeExplanation>
  <timeScaleCitation id="" scope="document" system="">{0,unbounded}</timeScaleCitation>
</alternativeTimeScale>

<xs:element name="alternativeTimeScale">
  <xs:annotation>
    <xs:appinfo>
      <doc:tooltip>Alternative Time Scale</doc:tooltip>
      <doc:summary>A name, code, or date describing an event or period
            in an alternative time scale, such as one of the geologic time
            scales.</doc:summary>
      <doc:description>A name, code, or date describing an event or
            period in an alternative time scale, for instance as an absolute
            date calculated using a named dating method, or as a relative
            date that is drawn from stratigraphy or biostratigraphy.
            Calendar dates as provided in the ISO
            8601 dating system used in the standard CSDGM are not adequate to
            describe geologic time periods. Absolute geologic time is usually
            measured in millions of years before present, but may use different
            units and relative base times. Relative geologic time is measured by
            subdivisions of the earth's geology. in an order based upon relative
            age, most commonly, vertical or stratigraphic position. The actual
            dating systems used in geologic studies often tie relative times
            measured through stratigraphy or biostratigraphy to a particular
            absolute time using radioisotope dating techniques, among others. As
            these methods for absolute dating have improved, the estimates of
            the dates for strata have changed, consequently, it would be
            inaccurate to record absolute dates in situations where relative
            dates were measured.  This structure is provided as an optional
            alternative to the standard calendar dates provided by ISO 8601.</doc:description>
      <doc:example>Please see the individual sub-fields for specific
            examples.</doc:example>
    </xs:appinfo>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="timeScaleName" type="xs:string">
        <xs:annotation>
          <xs:appinfo>
            <doc:tooltip>alternative time scale</doc:tooltip>
            <doc:summary>Name of a recognized alternative time
                  scale.</doc:summary>
            <doc:description>Name of a recognized alternative time scale.
                  This includes 'Absolute' as the name of the time scale for
                  measuring geologic dates before the present and names of
                  geologic dating systems that are arrangements of symbols or
                  names in order of relative geologic time.</doc:description>
            <doc:example>'Absolute', 'Geomagnetic Polarity Time Scale',
                  'International Geological Time Scale',
                  'Oxygen-Isotope'</doc:example>
          </xs:appinfo>
        </xs:annotation>
      </xs:element>
      <xs:element name="timeScaleAgeEstimate" type="xs:string">
        <xs:annotation>
          <xs:appinfo>
            <doc:tooltip>Time scale age estimate</doc:tooltip>
            <doc:summary/>
            <doc:description>Either an absolute date or a relative age
                  name describing an event or period in an alternative time
                  scale such as the Geologic Time Scale.</doc:description>
            <doc:example>For example, '300 Ma' (300 million years before
                  present) is a Geologic_Age_Estimate based on the Absolute
                  Geologic_Time_Scale, 'C28r' is a chron name from the
                  Geomagnetic Polarity Time Scale, and 'Maastrichtian' and
                  'Jurassic' are names from the International Geological Time
                  Scale. Since different relative geologic time scales are
                  often not aligned, multiple geologic dates may need to be
                  specified. For example, the Geomagnetic Polarity Time Scale
                  chron 'C29r', at the K/T boundary lies in both the
                  'Maastrichtian' and the 'Danian' stages from the
                  International Geological Time Scale, thus if you were
                  documenting this event using the International Geological
                  Time Scale, both 'Maastrichtian' and 'Danian' should be
                  included here.</doc:example>
          </xs:appinfo>
        </xs:annotation>
      </xs:element>
      <xs:element name="timeScaleAgeUncertainty" type="xs:string" minOccurs="0">
        <xs:annotation>
          <xs:appinfo>
            <doc:tooltip>Time scale age uncertainty</doc:tooltip>
            <doc:summary>The error estimate for the alternative time
                  scale.</doc:summary>
            <doc:description>The error estimate for the alternative time.
                  This should include the units of measure, a description of
                  what the error estimate represents and how it was
                  calculated.</doc:description>
            <doc:example>+/- 5 Ma (Million Years)</doc:example>
          </xs:appinfo>
        </xs:annotation>
      </xs:element>
      <xs:element name="timeScaleAgeExplanation" type="xs:string" minOccurs="0">
        <xs:annotation>
          <xs:appinfo>
            <doc:tooltip>Time scale age explanation</doc:tooltip>
            <doc:summary>The name and/or description of the method used to
                  calculate the time scale age estimate.</doc:summary>
            <doc:description>The name and/or description of the method
                  used to calculate the age estimate. Detailed information
                  about the method may be provided through references
                  contained in the Time Scale Citation field.</doc:description>
          </xs:appinfo>
        </xs:annotation>
      </xs:element>
      <xs:element name="timeScaleCitation" type="cit:CitationType" minOccurs="0" maxOccurs="unbounded">
        <xs:annotation>
          <xs:appinfo>
            <doc:tooltip>Time Scale citation</doc:tooltip>
            <doc:summary>Citation for works providing detailed information
                  about any element of the time scale age.</doc:summary>
            <doc:description>Citation for works providing detailed
                  information about any element of the time scale
                  age.</doc:description>
            <doc:example>For example, a publication describing the
                  methodology used for carbon dating or describing the basic
                  geologic time scale in more detail could be cited
                  here.</doc:example>
          </xs:appinfo>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>

<xs:element name="timeScaleName" type="xs:string">
  <xs:annotation>
    <xs:appinfo>
      <doc:tooltip>alternative time scale</doc:tooltip>
      <doc:summary>Name of a recognized alternative time
                  scale.</doc:summary>
      <doc:description>Name of a recognized alternative time scale.
                  This includes 'Absolute' as the name of the time scale for
                  measuring geologic dates before the present and names of
                  geologic dating systems that are arrangements of symbols or
                  names in order of relative geologic time.</doc:description>
      <doc:example>'Absolute', 'Geomagnetic Polarity Time Scale',
                  'International Geological Time Scale',
                  'Oxygen-Isotope'</doc:example>
    </xs:appinfo>
  </xs:annotation>
</xs:element>

<xs:element name="timeScaleAgeEstimate" type="xs:string">
  <xs:annotation>
    <xs:appinfo>
      <doc:tooltip>Time scale age estimate</doc:tooltip>
      <doc:summary/>
      <doc:description>Either an absolute date or a relative age
                  name describing an event or period in an alternative time
                  scale such as the Geologic Time Scale.</doc:description>
      <doc:example>For example, '300 Ma' (300 million years before
                  present) is a Geologic_Age_Estimate based on the Absolute
                  Geologic_Time_Scale, 'C28r' is a chron name from the
                  Geomagnetic Polarity Time Scale, and 'Maastrichtian' and
                  'Jurassic' are names from the International Geological Time
                  Scale. Since different relative geologic time scales are
                  often not aligned, multiple geologic dates may need to be
                  specified. For example, the Geomagnetic Polarity Time Scale
                  chron 'C29r', at the K/T boundary lies in both the
                  'Maastrichtian' and the 'Danian' stages from the
                  International Geological Time Scale, thus if you were
                  documenting this event using the International Geological
                  Time Scale, both 'Maastrichtian' and 'Danian' should be
                  included here.</doc:example>
    </xs:appinfo>
  </xs:annotation>
</xs:element>

<xs:element name="timeScaleAgeUncertainty" type="xs:string" minOccurs="0">
  <xs:annotation>
    <xs:appinfo>
      <doc:tooltip>Time scale age uncertainty</doc:tooltip>
      <doc:summary>The error estimate for the alternative time
                  scale.</doc:summary>
      <doc:description>The error estimate for the alternative time.
                  This should include the units of measure, a description of
                  what the error estimate represents and how it was
                  calculated.</doc:description>
      <doc:example>+/- 5 Ma (Million Years)</doc:example>
    </xs:appinfo>
  </xs:annotation>
</xs:element>

<xs:element name="timeScaleAgeExplanation" type="xs:string" minOccurs="0">
  <xs:annotation>
    <xs:appinfo>
      <doc:tooltip>Time scale age explanation</doc:tooltip>
      <doc:summary>The name and/or description of the method used to
                  calculate the time scale age estimate.</doc:summary>
      <doc:description>The name and/or description of the method
                  used to calculate the age estimate. Detailed information
                  about the method may be provided through references
                  contained in the Time Scale Citation field.</doc:description>
    </xs:appinfo>
  </xs:annotation>
</xs:element>

<timeScaleCitation id="" scope="document" system="">
  <alternateIdentifier system="">{0,unbounded}</alternateIdentifier>
  <shortName>{0,1}</shortName>
  <title>{1,unbounded}</title>
  <creator id="" scope="document" system="">{1,unbounded}</creator>
  <metadataProvider id="" scope="document" system="">{0,unbounded}</metadataProvider>
  <associatedParty id="" scope="document" system="">{0,unbounded}</associatedParty>
  <pubDate>{0,1}</pubDate>
  <language>{0,1}</language>
  <series>{0,1}</series>
  <abstract>{0,1}</abstract>
  <keywordSet>{0,unbounded}</keywordSet>
  <additionalInfo>{0,unbounded}</additionalInfo>
  <intellectualRights>{0,1}</intellectualRights>
  <distribution id="" scope="document" system="">{0,unbounded}</distribution>
  <coverage id="" scope="document" system="">{0,1}</coverage>
  <access authSystem="" id="" order="allowFirst" scope="document" system="">{0,1}</access>
</timeScaleCitation>

<xs:element name="timeScaleCitation" type="cit:CitationType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:appinfo>
      <doc:tooltip>Time Scale citation</doc:tooltip>
      <doc:summary>Citation for works providing detailed information
                  about any element of the time scale age.</doc:summary>
      <doc:description>Citation for works providing detailed
                  information about any element of the time scale
                  age.</doc:description>
      <doc:example>For example, a publication describing the
                  methodology used for carbon dating or describing the basic
                  geologic time scale in more detail could be cited
                  here.</doc:example>
    </xs:appinfo>
  </xs:annotation>
</xs:element>

<rangeOfDates>
  <beginDate>{1,1}</beginDate>
  <endDate>{1,1}</endDate>
</rangeOfDates>

<xs:element name="rangeOfDates">
  <xs:annotation>
    <xs:appinfo>
      <doc:tooltip>Range of dates/times</doc:tooltip>
      <doc:summary>Means of encoding a range of dates and
        times.</doc:summary>
      <doc:description>The 'RangeOfDatesType' field is intended to be used for
        describing a range of dates and/or times. It may be used multiple times
        to document multiple date ranges. It allows for two 'singleDateTime'
        fields, the first to be used as the beginning dateTime, and the second
        to be used as the ending dateTime of the range.</doc:description>
      <doc:example>Please see the examples from the 'singleDateTime'
        field for specific examples.</doc:example>
    </xs:appinfo>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="beginDate" type="SingleDateTimeType">
        <xs:annotation>
          <xs:appinfo>
            <doc:tooltip>Begin Date</doc:tooltip>
            <doc:summary>A single time stamp signifying the beginning of
              some time period</doc:summary>
            <doc:description>A single time stamp signifying the beginning of
              some time period.  There is a choice between two
              options: a calendar date with a time, or a geologic
              age.</doc:description>
            <doc:example>Please see the individual sub-elements for
              example.</doc:example>
          </xs:appinfo>
        </xs:annotation>
      </xs:element>
      <xs:element name="endDate" type="SingleDateTimeType">
        <xs:annotation>
          <xs:appinfo>
            <doc:tooltip>End Date</doc:tooltip>
            <doc:summary>A single time stamp signifying the end of
              some time period</doc:summary>
            <doc:description>A single time stamp signifying the end of
              some time period.  There is a choice between two
              options: a calendar date with a time, or a geologic
              age.</doc:description>
            <doc:example>Please see the individual sub-elements for
              example.</doc:example>
          </xs:appinfo>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>

<beginDate>
  <calendarDate>{1,1}</calendarDate>
  <time>{0,1}</time>
  <alternativeTimeScale>{1,1}</alternativeTimeScale>
</beginDate>

<xs:element name="beginDate" type="SingleDateTimeType">
  <xs:annotation>
    <xs:appinfo>
      <doc:tooltip>Begin Date</doc:tooltip>
      <doc:summary>A single time stamp signifying the beginning of
              some time period</doc:summary>
      <doc:description>A single time stamp signifying the beginning of
              some time period.  There is a choice between two
              options: a calendar date with a time, or a geologic
              age.</doc:description>
      <doc:example>Please see the individual sub-elements for
              example.</doc:example>
    </xs:appinfo>
  </xs:annotation>
</xs:element>

<endDate>
  <calendarDate>{1,1}</calendarDate>
  <time>{0,1}</time>
  <alternativeTimeScale>{1,1}</alternativeTimeScale>
</endDate>

<xs:element name="endDate" type="SingleDateTimeType">
  <xs:annotation>
    <xs:appinfo>
      <doc:tooltip>End Date</doc:tooltip>
      <doc:summary>A single time stamp signifying the end of
              some time period</doc:summary>
      <doc:description>A single time stamp signifying the end of
              some time period.  There is a choice between two
              options: a calendar date with a time, or a geologic
              age.</doc:description>
      <doc:example>Please see the individual sub-elements for
              example.</doc:example>
    </xs:appinfo>
  </xs:annotation>
</xs:element>

<taxonomicCoverage id="" scope="document" system="">
  <taxonomicSystem>{0,1}</taxonomicSystem>
  <generalTaxonomicCoverage>{0,1}</generalTaxonomicCoverage>
  <taxonomicClassification>{1,unbounded}</taxonomicClassification>
</taxonomicCoverage>

<xs:element name="taxonomicCoverage">
  <xs:annotation>
    <xs:appinfo>
      <doc:tooltip>Taxonomic coverage</doc:tooltip>
      <doc:summary>Taxonomic coverage information.</doc:summary>
      <doc:description>Taxonomic Coverage is a container for Taxonomic
              information about a project, a resource, or an entity within a
              resource. It includes a list of species names (or higher level
              ranks) from one or more classification systems.</doc:description>
      <doc:example>Please see the individual sub fields for specific
              examples.</doc:example>
    </xs:appinfo>
  </xs:annotation>
  <xs:complexType>
    <xs:complexContent>
      <xs:extension base="TaxonomicCoverage">
        <xs:attribute name="system" type="res:SystemType" use="optional"/>
        <xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
      </xs:extension>
    </xs:complexContent>
  </xs:complexType>
</xs:element>

<taxonomicSystem>
  <classificationSystem>{1,unbounded}</classificationSystem>
  <identificationReference id="" scope="document" system="">{0,unbounded}</identificationReference>
  <identifierName id="" scope="document" system="">{1,unbounded}</identifierName>
  <taxonomicProcedures>{1,1}</taxonomicProcedures>
  <taxonomicCompleteness>{0,1}</taxonomicCompleteness>
  <vouchers>{0,unbounded}</vouchers>
</taxonomicSystem>

<xs:element name="taxonomicSystem" minOccurs="0">
  <xs:annotation>
    <xs:appinfo>
      <doc:tooltip>Taxonomic system</doc:tooltip>
      <doc:summary>Documentation of taxonomic sources, procedures, and
              treatments.</doc:summary>
      <doc:description>Documentation of taxonomic sources, procedures,
              and treatments.</doc:description>
    </xs:appinfo>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="classificationSystem" maxOccurs="unbounded">
        <xs:annotation>
          <xs:appinfo>
            <doc:tooltip>Classification system/authority</doc:tooltip>
            <doc:summary>Information about the classification system or
                    authority used.</doc:summary>
            <doc:description>Information about the classification
                    system or authority used.</doc:description>
            <doc:example>Flora of North America</doc:example>
          </xs:appinfo>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="classificationSystemCitation" type="cit:CitationType">
              <xs:annotation>
                <xs:appinfo>
                  <doc:tooltip>Taxonomic citation</doc:tooltip>
                  <doc:summary/>
                  <doc:description>Relevant literature for documenting
                          the used classification system.</doc:description>
                </xs:appinfo>
              </xs:annotation>
            </xs:element>
            <xs:element name="classificationSystemModifications" type="xs:string" minOccurs="0">
              <xs:annotation>
                <xs:appinfo>
                  <doc:tooltip>Classification system
                          modification</doc:tooltip>
                  <doc:summary/>
                  <doc:description>A description of any modifications
                          or exceptions made to the classification system or
                          authority used.</doc:description>
                </xs:appinfo>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="identificationReference" type="cit:CitationType" minOccurs="0" maxOccurs="unbounded">
        <xs:annotation>
          <xs:appinfo>
            <doc:tooltip>Non-authoritative citation</doc:tooltip>
            <doc:summary/>
            <doc:description>Information on any nonauthoritative
                    materials (e.g. field guides) useful for reconstructing the
                    actual identification process.</doc:description>
          </xs:appinfo>
        </xs:annotation>
      </xs:element>
      <xs:element name="identifierName" type="rp:ResponsibleParty" maxOccurs="unbounded">
        <xs:annotation>
          <xs:appinfo>
            <doc:tooltip>Identifier's Name</doc:tooltip>
            <doc:summary/>
            <doc:description>Information about the individual(s)
                    responsible for the identification(s) of the specimens or
                    sightings, etc.</doc:description>
          </xs:appinfo>
        </xs:annotation>
      </xs:element>
      <xs:element name="taxonomicProcedures" type="xs:string">
        <xs:annotation>
          <xs:appinfo>
            <doc:tooltip>Taxonomic procedures</doc:tooltip>
            <doc:summary/>
            <doc:description>Description of the methods used for the
                    taxonomic identification.</doc:description>
            <doc:example>specimen processing, comparison with museum
                    materials, keys and key characters, chemical or genetic
                    analyses</doc:example>
          </xs:appinfo>
        </xs:annotation>
      </xs:element>
      <xs:element name="taxonomicCompleteness" type="xs:string" minOccurs="0">
        <xs:annotation>
          <xs:appinfo>
            <doc:tooltip>Taxonomic completeness</doc:tooltip>
            <doc:summary/>
            <doc:description>Information concerning the proportions and
                    treatment of unidentified materials ; estimates of the
                    importance, and identities of misidentifications, uncertain
                    determinations, synonyms or other incorrect usages; taxa
                    not well treated or requiring further work; and expertise
                    of field workers.</doc:description>
            <doc:example>materials sent to experts, and not yet
                    determined</doc:example>
          </xs:appinfo>
        </xs:annotation>
      </xs:element>
      <xs:element name="vouchers" minOccurs="0" maxOccurs="unbounded">
        <xs:annotation>
          <xs:appinfo>
            <doc:tooltip>Specimen information</doc:tooltip>
            <doc:summary/>
            <doc:description>Information on the types of specimen, the
                    repository, and the individuals who identified the
                    vouchers.</doc:description>
          </xs:appinfo>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="specimen" type="xs:string">
              <xs:annotation>
                <xs:appinfo>
                  <doc:tooltip>Specimen type</doc:tooltip>
                  <doc:summary/>
                  <doc:description>A word or phrase describing the type
                          of specimen collected.</doc:description>
                  <doc:example>herbarium specimens, blood samples,
                          photographs, individuals, or batches</doc:example>
                </xs:appinfo>
              </xs:annotation>
            </xs:element>
            <xs:element name="repository">
              <xs:annotation>
                <xs:appinfo>
                  <doc:tooltip>Storage location of
                          specimen</doc:tooltip>
                  <doc:summary/>
                  <doc:description>Information about the curator or
                          contact person and/or agency responsible for the
                          specimens.</doc:description>
                </xs:appinfo>
              </xs:annotation>
              <xs:complexType>
                <xs:sequence>
                  <xs:element name="originator" type="rp:ResponsibleParty" maxOccurs="unbounded">
                    <xs:annotation>
                      <xs:appinfo>
                        <doc:tooltip>Originator</doc:tooltip>
                        <doc:summary>A person or organization asociated
                                with this resource.</doc:summary>
                        <doc:description>The 'originator' element
                                provides the full name of the person,
                                organization, or position associated with the
                                resource. Typically, the originator role is set
                                to "owner" to indicate the list of parties who
                                "own" the resource, but other roles such as
                                "principal investigator", "author", and
                                "editor" are provided.</doc:description>
                        <doc:example>Please see the examples within the
                                sub fields for the responsible
                                party.</doc:example>
                      </xs:appinfo>
                    </xs:annotation>
                  </xs:element>
                </xs:sequence>
              </xs:complexType>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>

<classificationSystem>
  <classificationSystemCitation id="" scope="document" system="">{1,1}</classificationSystemCitation>
  <classificationSystemModifications>{0,1}</classificationSystemModifications>
</classificationSystem>

<xs:element name="classificationSystem" maxOccurs="unbounded">
  <xs:annotation>
    <xs:appinfo>
      <doc:tooltip>Classification system/authority</doc:tooltip>
      <doc:summary>Information about the classification system or
                    authority used.</doc:summary>
      <doc:description>Information about the classification
                    system or authority used.</doc:description>
      <doc:example>Flora of North America</doc:example>
    </xs:appinfo>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="classificationSystemCitation" type="cit:CitationType">
        <xs:annotation>
          <xs:appinfo>
            <doc:tooltip>Taxonomic citation</doc:tooltip>
            <doc:summary/>
            <doc:description>Relevant literature for documenting
                          the used classification system.</doc:description>
          </xs:appinfo>
        </xs:annotation>
      </xs:element>
      <xs:element name="classificationSystemModifications" type="xs:string" minOccurs="0">
        <xs:annotation>
          <xs:appinfo>
            <doc:tooltip>Classification system
                          modification</doc:tooltip>
            <doc:summary/>
            <doc:description>A description of any modifications
                          or exceptions made to the classification system or
                          authority used.</doc:description>
          </xs:appinfo>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>

<classificationSystemCitation id="" scope="document" system="">
  <alternateIdentifier system="">{0,unbounded}</alternateIdentifier>
  <shortName>{0,1}</shortName>
  <title>{1,unbounded}</title>
  <creator id="" scope="document" system="">{1,unbounded}</creator>
  <metadataProvider id="" scope="document" system="">{0,unbounded}</metadataProvider>
  <associatedParty id="" scope="document" system="">{0,unbounded}</associatedParty>
  <pubDate>{0,1}</pubDate>
  <language>{0,1}</language>
  <series>{0,1}</series>
  <abstract>{0,1}</abstract>
  <keywordSet>{0,unbounded}</keywordSet>
  <additionalInfo>{0,unbounded}</additionalInfo>
  <intellectualRights>{0,1}</intellectualRights>
  <distribution id="" scope="document" system="">{0,unbounded}</distribution>
  <coverage id="" scope="document" system="">{0,1}</coverage>
  <access authSystem="" id="" order="allowFirst" scope="document" system="">{0,1}</access>
</classificationSystemCitation>

<xs:element name="classificationSystemCitation" type="cit:CitationType">
  <xs:annotation>
    <xs:appinfo>
      <doc:tooltip>Taxonomic citation</doc:tooltip>
      <doc:summary/>
      <doc:description>Relevant literature for documenting
                          the used classification system.</doc:description>
    </xs:appinfo>
  </xs:annotation>
</xs:element>

<xs:element name="classificationSystemModifications" type="xs:string" minOccurs="0">
  <xs:annotation>
    <xs:appinfo>
      <doc:tooltip>Classification system
                          modification</doc:tooltip>
      <doc:summary/>
      <doc:description>A description of any modifications
                          or exceptions made to the classification system or
                          authority used.</doc:description>
    </xs:appinfo>
  </xs:annotation>
</xs:element>

<identificationReference id="" scope="document" system="">
  <alternateIdentifier system="">{0,unbounded}</alternateIdentifier>
  <shortName>{0,1}</shortName>
  <title>{1,unbounded}</title>
  <creator id="" scope="document" system="">{1,unbounded}</creator>
  <metadataProvider id="" scope="document" system="">{0,unbounded}</metadataProvider>
  <associatedParty id="" scope="document" system="">{0,unbounded}</associatedParty>
  <pubDate>{0,1}</pubDate>
  <language>{0,1}</language>
  <series>{0,1}</series>
  <abstract>{0,1}</abstract>
  <keywordSet>{0,unbounded}</keywordSet>
  <additionalInfo>{0,unbounded}</additionalInfo>
  <intellectualRights>{0,1}</intellectualRights>
  <distribution id="" scope="document" system="">{0,unbounded}</distribution>
  <coverage id="" scope="document" system="">{0,1}</coverage>
  <access authSystem="" id="" order="allowFirst" scope="document" system="">{0,1}</access>
</identificationReference>