<?xml version="1.0" encoding="UTF-8"?>
<!-- edited with XMLSpy v2014 (x64) (http://www.altova.com) by Group IT (PostNL Groep) -->
<!--org/2001/XMLSchema-->
<!--
Major/Minor versie:    3.0
datum productie			oktober 2017
aanpassing door		NM
Major/Minor versie:    3.0
datum productie		
aanpassing door		NM
details:						Herijking met standaard Open Geospatial Consortium.


Major/Minor versie:		1.2
datum productie			06-07-2012
aanpassing door		PS
details:						ma1:CFCStatistics toegevoegd

major/ minor versie: 	1.1
datum aanpassing:	13-01-2012
aanpassing door:		NM
doelgroep:				    alle gebruikers van Observation
details						optionele ref naar co1:HeaderType toegevoegd 
								FeatureOfInterest is uitgebreid met optioneel PictureType
								Ten behoeve van integratie met MDM is in ma1:ResultProcess ma1:LocationType vervangen door ma1:WorkLocationType 
								en is ma1:ProcessOrganizationType vervangen door  ma1:OrganizationEntityType
								In ma1:InductionStationStatistics zijn alle velden met quantity in de naam gekoppeld aan QuantityType. Dit is geen major release wijziging omdat dit ook SAPPI wordt gedaan.
								


major/ minor versie:	1.0
datum productie:		13-12-2011
gemaakt door			PS
doelgroep					PostNL

  	
   -->
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:postnl/mail/observationsensorml/1" xmlns:ma1="urn:postnl/mail/manufacturingcomponents/1" xmlns:co1="urn:postnl/mail/components/1" xmlns:me1="urn:postnl/mail/meta/1" xmlns:fi1="urn:postnl/mail/fields1" xmlns:lo1="urn:postnl/mail/logisticscomponents/1" xmlns:ma2="urn:postnl/mail/manufacturingcomponents/2" xmlns:co2="urn:postnl/mail/components/2" xmlns:co3="urn:postnl/mail/components/3" xmlns:ma3="urn:postnl/mail/manufacturingcomponents/3" targetNamespace="urn:postnl/mail/observationsensorml/1" elementFormDefault="qualified" attributeFormDefault="unqualified">
	<xsd:import namespace="urn:postnl/mail/manufacturingcomponents/1" schemaLocation="../../Common/OAGI/Components/ManufacturingComponents1.xsd"/>
	<xsd:import namespace="urn:postnl/mail/manufacturingcomponents/2" schemaLocation="../../Common/OAGI/Components/ManufacturingComponents2.xsd"/>
	<xsd:import namespace="urn:postnl/mail/manufacturingcomponents/3" schemaLocation="../../Common/OAGI/Components/ManufacturingComponents3.xsd"/>
	<xsd:import namespace="urn:postnl/mail/components/1" schemaLocation="../../Common/OAGI/Components/Components1.xsd"/>
	<xsd:import namespace="urn:postnl/mail/components/2" schemaLocation="../../Common/OAGI/Components/Components2.xsd"/>
	<xsd:import namespace="urn:postnl/mail/components/3" schemaLocation="../../Common/OAGI/Components/Components3.xsd"/>
	<xsd:import namespace="urn:postnl/mail/meta/1" schemaLocation="../../Common/OAGI/Components/Meta1.xsd"/>
	<xsd:import namespace="urn:postnl/mail/fields1" schemaLocation="../../Common/OAGI/Components/Fields1.xsd"/>
	<xsd:element name="ObservationSensorML" type="ObservationSensorMLType">
		<xsd:annotation>
			<xsd:documentation>Observation is an act ("event"), whose result is an estimate of the value of a property of the feature of interest. 
Deze Observation is de basisversie ten behoeve van de observatie van een sensorML meting. 
De koppeling tussen SensorML en Observation is te vinden in de elementen:
1. The result of a SensorML process is typically considered to be an observation result if it is measuring or deriving some value of a physical property or phenomenon .
Thus, the output values described in SensorML and resulting from a sensor or process may be packaged in an OM Observation object, or provided as a SWE Common DataStream.
2. Inversely, the procedure property within an Observation instance may reference a SensorML description of the measurement process.

</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:complexType name="ObservationSensorMLType">
		<xsd:sequence>
			<xsd:element ref="ObservationSensorMLHeader" minOccurs="0">
				<xsd:annotation>
					<xsd:documentation>Information that generally describes the Observation. </xsd:documentation>
				</xsd:annotation>
			</xsd:element>
			<xsd:element ref="ObservationSensorMLResult" minOccurs="0" maxOccurs="unbounded">
				<xsd:annotation>
					<xsd:documentation>The ObservationResult contains the value of the Observation, as well as the inforrnation about the context of the observation.

An observation results in a value being assigned to a phenomenon. The phenomenon is a property of a feature, the latter being the feature-of-interest of the observation. The observation uses a procedure, which is
often an instrument or sensor , but may be a process chain, human observer, an algorithm, a computation 
or simulator. The key idea is that the observation result is an estimate of the value of some property of the
feature-of-interest, and the other observation properties provide context or metadata to support evaluation,
interpretation and use of the result.
The relationship between the properties of an observatio and those of its feature-of-interest is key to the semantics of the model.</xsd:documentation>
				</xsd:annotation>
			</xsd:element>
		</xsd:sequence>
	</xsd:complexType>
	<xsd:element name="ObservationSensorMLHeader" type="ObservationSensorMLHeaderType">
		<xsd:annotation>
			<xsd:documentation>Information that generally describes the Observation and the context of the Observation.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:complexType name="ObservationSensorMLHeaderType">
		<xsd:complexContent>
			<xsd:extension base="co1:StatusEnabledHeaderType">
				<xsd:sequence>
					<xsd:element ref="ma2:ObservationClass" minOccurs="0"/>
					<xsd:element ref="ma1:ResultReleaseTime" minOccurs="0"/>
					<xsd:element ref="ma1:ResultReceivedTime" minOccurs="0"/>
					<xsd:element ref="ma1:Metadata" minOccurs="0" maxOccurs="unbounded"/>
				</xsd:sequence>
			</xsd:extension>
		</xsd:complexContent>
	</xsd:complexType>
	<xsd:element name="ObservationSensorMLResult" type="ObservationSensorMLResultType">
		<xsd:annotation>
			<xsd:documentation>The ObservationResult contains the value of the Observation, as well as the inforrnation about the context of the observation.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:complexType name="ObservationSensorMLResultType">
		<xsd:sequence>
			<xsd:element ref="ma1:RelatedObservation" minOccurs="0" maxOccurs="unbounded"/>
			<xsd:element name="PhenomenonTime" type="co1:TimePeriodType" minOccurs="0">
				<xsd:annotation>
					<xsd:documentation>
					PhenomenonTime shall describe the time that the result applies to the property of the feature-of-interest. This is often the time of interaction by a sampling procedure or observation procedure with a real-world feature.
					</xsd:documentation>
				</xsd:annotation>
			</xsd:element>
			<xsd:element name="ResultTime" type="co1:TimePeriodType" minOccurs="0">
				<xsd:annotation>
					<xsd:documentation> Result time is the time when the result became available, typically when the procedure associated with the observation was completed For some observations this is identical to the samplingTime. However, there are important cases where they
differ. </xsd:documentation>
				</xsd:annotation>
			</xsd:element>
			<xsd:element name="ValidTime" type="co1:TimePeriodType" minOccurs="0">
				<xsd:annotation>
					<xsd:documentation>If present, the attribute validTime shall describe the
time period during which the result is intended to be used. </xsd:documentation>
				</xsd:annotation>
			</xsd:element>
			<xsd:element name="Procedure" type="ProcedureType" minOccurs="0"/>
			<!--	<xsd:element ref="ma2:ResultSource" minOccurs="0"/>-->
			<xsd:element ref="fi1:EventParameter" minOccurs="0" maxOccurs="unbounded"/>
			<xsd:element ref="ma1:PropertyObserved" minOccurs="0"/>
			<xsd:element ref="ma2:FeatureOfInterest" minOccurs="0"/>
			<xsd:element ref="ma2:ResultQuality" minOccurs="0" maxOccurs="unbounded"/>
			<xsd:element ref="ResultValue" minOccurs="0" maxOccurs="unbounded">
				<xsd:annotation>
					<xsd:documentation>The ResultValue contains the values of the Observation of the feature of interest.</xsd:documentation>
				</xsd:annotation>
			</xsd:element>
		</xsd:sequence>
	</xsd:complexType>
	<xsd:element name="ResultValue" type="ResultValueType"/>
	<xsd:complexType name="ResultValueType">
		<xsd:sequence>
			<xsd:element name="ResultValueCharacteristics" type="co1:CharacteristicType" minOccurs="0" maxOccurs="unbounded">
				<xsd:annotation>
					<xsd:documentation>De naam en inhoud van het resultaat van de observatie.</xsd:documentation>
				</xsd:annotation>
			</xsd:element>
		</xsd:sequence>
	</xsd:complexType>
	<xsd:complexType name="ProcedureType">
		<xsd:sequence>
			<xsd:element name="identification" type="ma1:SMLIdentificationType" minOccurs="0" maxOccurs="unbounded">
				<xsd:annotation>
					<xsd:documentation>Identifiers useful for discovery of the process (e.g. short name, mission id, wing id, serial number, etc.)</xsd:documentation>
				</xsd:annotation>
			</xsd:element>
			<xsd:element name="classification" type="ma1:SMLClassificationType" minOccurs="0" maxOccurs="unbounded">
				<xsd:annotation>
					<xsd:documentation>Classifiers useful for discovery of the process (e.g. process type, sensor type, intended application, etc.)</xsd:documentation>
				</xsd:annotation>
			</xsd:element>
			<xsd:element name="localreferenceframe" type="ma1:SpatialFrameType" minOccurs="0" maxOccurs="unbounded">
				<xsd:annotation>
					<xsd:documentation>A spatial reference frame of the physical component itself; this reference frame is absolute and defines the relationship of the reference frame to the physical body of the component; position of the component relates this reference frame to some external reference frame. Note that units are specified in the position so they are not specified as part of the SpatialFrame.</xsd:documentation>
				</xsd:annotation>
			</xsd:element>
			<xsd:element name="localtimeframe" type="ma1:TemporalFrameType" minOccurs="0" maxOccurs="unbounded"/>
			<xsd:element name="position" type="co1:GeoCoordinateType" minOccurs="0" maxOccurs="unbounded">
				<xsd:annotation>
					<xsd:documentation>Provides positional information relating the component's spatial reference frame to an external spatial reference frame. Positional information can be given by location, by full body state, by a time-tagged trajectory, or by a measuring or computational process.</xsd:documentation>
				</xsd:annotation>
			</xsd:element>
			<xsd:element name="timeposition" type="fi1:DateTimeType" minOccurs="0" maxOccurs="unbounded">
				<xsd:annotation>
					<xsd:documentation>Provides Time positions typically reference a local time frame to an external time frame. For example, a timer-start-time might be given relative to an "absolute" GPS time.</xsd:documentation>
				</xsd:annotation>
			</xsd:element>
		</xsd:sequence>
	</xsd:complexType>
</xsd:schema>
