<xs:element name="beginDateTime" type="xs:dateTime"/>

<xs:element name="boundingBox">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="westLongitude" type="longitudeType"/>
      <xs:element name="eastLongitude" type="longitudeType"/>
      <xs:element name="southLatitude" type="latitudeType"/>
      <xs:element name="northLatitude" type="latitudeType"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>

<xs:element name="westLongitude" type="longitudeType"/>

<xs:element name="eastLongitude" type="longitudeType"/>

<xs:element name="southLatitude" type="latitudeType"/>

<xs:element name="northLatitude" type="latitudeType"/>

<xs:element name="date" type="xs:dateTime"/>

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

<xs:element name="endDateTime" type="xs:dateTime"/>

<xs:element name="geographicIdentifier" type="xs:string">
  <xs:annotation>
    <xs:documentation>
For the DDS the geographic identifier included more complex information. It was compressed into a string to avoid for the present, the complication of including WMO or ICAO set specific encoding.
			</xs:documentation>
  </xs:annotation>
</xs:element>

<xs:element name="metadataFileIdentifier" type="xs:anyURI">
  <xs:annotation>
    <xs:documentation>
The URI is a unique identifier referring to the bulletin.
The suggested form is:
/EGRR/SYNOP/03772/2003-11-26T11:00:00
as a SYNOP bulletin disseminated by EGRR for Heathrow 03772 at the date and time.
The base for the full URI should be defined in the root document (although not done here).
From this path there should be available sufficient information that the static data in the WMO Core Profile can be added to the template of a full document by a dedicated XSLT script. 
	 		</xs:documentation>
  </xs:annotation>
</xs:element>

<xs:element name="point">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="latitude" type="latitudeType"/>
      <xs:element name="longitude" type="longitudeType"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>

<xs:element name="latitude" type="latitudeType"/>

<xs:element name="longitude" type="longitudeType"/>

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

<xs:element name="referenceDateTime" type="xs:dateTime"/>

<xs:element name="resourceIdentifier" type="xs:string">
  <xs:annotation>
    <xs:documentation>
Here the Bulletin Collection is identified as the resource from which the bulletin was extracted. This is the only plce where the AHL Abbreviated Header List is referenced.
This too is more complicated than the allowed string, and should be an XML fragment itself.
			</xs:documentation>
  </xs:annotation>
</xs:element>

<xs:element name="temporalElement">
  <xs:complexType>
    <xs:sequence>
      <xs:element ref="referenceDateTime"/>
      <xs:element ref="beginDateTime" minOccurs="0"/>
      <xs:element ref="endDateTime" minOccurs="0"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>

<xs:element name="WMOBulletinSet">
  <xs:annotation>
    <xs:documentation>The root document is a set of WMO Bulletins, each of which has a cut-down metadata tag with only the variable metadata in WMO Core Profile of the ISO19115 standard. In fact the core standard has been extended, anticipating the 4th ET-IDM meeting to include Content information comprising either coverage or feature catalogue information. In fact the full WMO Core Profile schema is not referenced directly because of validation problems.
The data tag has really only raw data in this schema, since parsed raw data requires a schema of its own comprising element sets of the named groups.  
	</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="WMOBulletin" type="WMOBulletinType" maxOccurs="unbounded"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>

<xs:element name="WMOBulletin" type="WMOBulletinType" maxOccurs="unbounded"/>

<xs:group name="coverageGeometry">
  <xs:annotation>
    <xs:documentation>
This group is a coding of the GRIB latitude-longitude grid definition translated to ISO terms
			</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="corner1Lat" type="xs:decimal"/>
    <xs:element name="corner1Lon" type="xs:decimal"/>
    <xs:element name="corner2Lat" type="xs:decimal"/>
    <xs:element name="corner2Lon" type="xs:decimal"/>
    <xs:element name="deltaLat" type="xs:decimal"/>
    <xs:element name="deltaLon" type="xs:decimal"/>
    <xs:element name="numberLatPoints" type="xs:decimal"/>
    <xs:element name="numberLonPoints" type="xs:decimal"/>
    <xs:element name="scanning" type="xs:string"/>
  </xs:sequence>
</xs:group>

<xs:element name="corner1Lat" type="xs:decimal"/>

<xs:element name="corner1Lon" type="xs:decimal"/>

<xs:element name="corner2Lat" type="xs:decimal"/>

<xs:element name="corner2Lon" type="xs:decimal"/>

<xs:element name="deltaLat" type="xs:decimal"/>

<xs:element name="deltaLon" type="xs:decimal"/>

<xs:element name="numberLatPoints" type="xs:decimal"/>

<xs:element name="numberLonPoints" type="xs:decimal"/>

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

<xs:complexType name="coverageType">
  <xs:annotation>
    <xs:documentation>
This coverage feature list is set up for WMO GRIB coverage elements.
element variableField is the parameter which varies at each point of the grid
element fixedField is the level or layer parameter foxed at every point.
For example: Temperature varying at every grid point defined at a height level of 3000m
or conversely, the lowest height variable at each grid point at which the 0C temperature is crossed, if indeed it is crossed.
group coverageGeometry is a coding of the GRIB latitude-longitude grid definition translated to ISO terms
			</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="variableField" type="xs:string"/>
    <xs:element name="fixedField" type="xs:string" maxOccurs="2"/>
    <xs:group ref="coverageGeometry" minOccurs="0"/>
  </xs:sequence>
</xs:complexType>

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

<xs:element name="fixedField" type="xs:string" maxOccurs="2"/>

<xs:complexType name="featureCatalogueType">
  <xs:annotation>
    <xs:documentation>
This is where the feature catalogue conforming tor ISO19110 is referenced. The catalogue Name should be the name of the future WMO feature catalogue repository, and the featureName is the name of the particular feature collection or feature type defind within, e.g. SYNOP. 
			</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="catalogueName" type="xs:string" minOccurs="0"/>
    <xs:element name="featureName" type="xs:string"/>
  </xs:sequence>
</xs:complexType>

<xs:element name="catalogueName" type="xs:string" minOccurs="0"/>

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

<xs:complexType name="WMOBulletinDataType">
  <xs:annotation>
    <xs:documentation>
Here the data is appended as raw data or parsed grouped data or fully parsed data
</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="rawData" type="xs:string"/>
    <xs:element name="parsedGroupedData" minOccurs="0"/>
  </xs:sequence>
</xs:complexType>

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

<xs:element name="parsedGroupedData" minOccurs="0"/>

<xs:complexType name="WMOBulletinMetadataType">
  <xs:annotation>
    <xs:documentation>
This should properly reference the WMO Core Profile of ISO 19115.
However validation problems meant that the formal reference has been remooved
</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element ref="metadataFileIdentifier"/>
    <xs:element ref="resourceIdentifier"/>
    <xs:element ref="descriptiveKeywords"/>
    <xs:element ref="date"/>
    <xs:choice>
      <xs:element ref="point"/>
      <xs:element ref="boundingBox"/>
    </xs:choice>
    <xs:element ref="geographicIdentifier" minOccurs="0"/>
    <xs:choice minOccurs="0">
      <xs:element name="featureCatalogue" type="featureCatalogueType"/>
      <xs:element name="coverage" type="coverageType"/>
    </xs:choice>
    <xs:element ref="temporalElement"/>
  </xs:sequence>
</xs:complexType>

<xs:element name="featureCatalogue" type="featureCatalogueType"/>

<xs:element name="coverage" type="coverageType"/>

<xs:complexType name="WMOBulletinType">
  <xs:sequence>
    <xs:element name="metadata" type="WMOBulletinMetadataType"/>
    <xs:element name="data" type="WMOBulletinDataType"/>
  </xs:sequence>
</xs:complexType>

<xs:element name="metadata" type="WMOBulletinMetadataType"/>

<xs:element name="data" type="WMOBulletinDataType"/>

<xs:simpleType name="latitudeRangeType">
  <xs:annotation>
    <xs:documentation>Type of a latitude value</xs:documentation>
  </xs:annotation>
  <xs:restriction base="xs:float">
    <xs:minInclusive value="-90.0"/>
    <xs:maxInclusive value="90.0"/>
  </xs:restriction>
</xs:simpleType>

<xs:simpleType name="latitudeType">
  <xs:union memberTypes="NullEnumeration latitudeRangeType"/>
</xs:simpleType>

<xs:simpleType name="longitudeRangeType">
  <xs:annotation>
    <xs:documentation>Type of a longitude value</xs:documentation>
  </xs:annotation>
  <xs:restriction base="xs:float">
    <xs:minInclusive value="-180.0"/>
    <xs:maxInclusive value="180.0"/>
  </xs:restriction>
</xs:simpleType>

<xs:simpleType name="longitudeType">
  <xs:union memberTypes="NullEnumeration longitudeRangeType"/>
</xs:simpleType>

<xs:simpleType name="NullEnumeration">
  <xs:restriction base="xs:string">
    <xs:enumeration value="inapplicable"/>
    <xs:enumeration value="missing"/>
    <xs:enumeration value="template"/>
    <xs:enumeration value="unknown"/>
    <xs:enumeration value="withheld"/>
  </xs:restriction>
</xs:simpleType>