<?xml version="1.0" encoding="UTF-8"?>
<!-- edited with XMLSpy v2016 rel. 2 sp1 (x64) (http://www.altova.com) by PostNL IT (PostNL Holding B.V.) -->
<!--org/2001/XMLSchema-->
<!--
Major/Minor versie:    1.0
datum productie			6 juli 2018
aanpassing door		NM in overleg met Manon Havinga en Henk Willemse

details:						Observation3 (gebaseerd op het XSD Observation & Measurements van de Open Geospatial Consortium standaard) zonder verdere aanpassingen geschikt gemaakt voor observaties afkomstig van sensoren.




  	
   -->
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:postnl/mail/observationsensor/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/observationsensor/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/meta/1" schemaLocation="../../Common/OAGI/Components/Meta1.xsd"/>
	<xsd:import namespace="urn:postnl/mail/fields1" schemaLocation="../../Common/OAGI/Components/Fields1.xsd"/>
	<xsd:element name="ObservationSensor" type="ObservationSensorType">
		<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.So, it is an act of measuring or otherwise determining the value of a property.

An observation is an act associated with a discrete time instant or period through which a number, term or other symbol is assigned to a phenomenon [2]. It involves application of a specified procedure, such as a sensor, instrument, algorithm or process chain. The procedure may be applied in-situ, remotely, or ex-situ with respect to the sampling location. The result of an observation is an estimate of the value of a property of some
feature. Use of a common model allows observation data using different procedures to be combined
unambiguously.
</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:complexType name="ObservationSensorType">
		<xsd:sequence>
			<xsd:element ref="ObservationSensorHeader" minOccurs="0">
				<xsd:annotation>
					<xsd:documentation>Information that generally describes the ObservationSensor. </xsd:documentation>
				</xsd:annotation>
			</xsd:element>
			<xsd:element ref="ObservationSensorResult" minOccurs="0" maxOccurs="unbounded">
				<xsd:annotation>
					<xsd:documentation>The ObservationSensorResult 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="ObservationSensorHeader" type="ObservationSensorHeaderType">
		<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="ObservationSensorHeaderType">
		<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="ObservationSensorResult" type="ObservationSensorResultType">
		<xsd:annotation>
			<xsd:documentation>The ObservationSensorResult 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="ObservationSensorResultType">
		<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 ref="ma3:ResultProcedure" 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:schema>
