<?xml version="1.0" encoding="utf-8"?>
<!-- edited with XMLSpy v2014 (x64) (http://www.altova.com) by Group IT (PostNL Groep) -->
<!--

NM, 26-06-2013: LET OP:  co1:FreightLabel toegevoegd aan lo1:FreightUnit
De impact van de wijziging moet nog afgestemd worden met PI !!!!!!


major/minor versie	:	2.2
datum aanpassing :	18-09-2012
door						:	Nelleke van der Meer; Marcel vd Voort, Peter Por/ Henk Willemse
soort aanpassing	:	sequence code toegevoegd bij stop activity en stop reason
datum productie		:	14-02-2013

major/minor versie	:	2.1
datum aanpassing :	15-06-2012
door						:	Nelleke van der Meer; op verzoek van Marcel vd Voort, Henk Willemse
soort aanpassing	:	ten behoeve van tariferen chauffeurs en co-drivers is het complextype DriverPartyType uitgebreid met co1:DriverTariffUnitPrice. 
datum productie		:	19-06-2012

major/ minor versie	:	2.0
datum aanpassing	:	23-01-2012
door						:	Nelleke van der Meer
soort aanpassing	:	1) co1:status toegevoegd als optionele component (was onterecht weggemarkeerd als comment)
								2) co1:Location binnen StopType optioneel gemaakt
								3) co1:TransportCompanyParty toegevoegd als optionele component binnen Trip
								4) fi1:TransportCompanyPartyID toegevoegd als optioneel field aan co1:DriverParty
								5) lo1:LoadTimeWindow en lo1:UnloadTimeWindow verwijderd en vervangen door lo1:StopTmeWindow.
									Dit is een major release change. Hierdoor is lo2:StopActivity aangemaakt in het nieuwe XSD
									lo2:LogisticsComponents. Dus ook een import van LogisticsComponents2 toegevoegd.
								6) choice verwijderd uit lo1:StopActivity
								7) co1:TransportOrderReference uitgebreid met co1:HeaderType
								8) co1:car toegevoegd ipv field fi1:CarNumber
								9) co1:SalesContractReference en co1:TransportContractReference toegevoegd aan lo2:StopActivity
								10) Stop is een optioneel element geworden ipv verplicht
datum productie		:	10-02-2012


major/ minor versie:	1.0
datum productie:		13-12-2011



15-09-2011    NM    tbv. Rit informatie Autobedrijf gebaseerd op OAGIS Noun CarrierRoute versie 9_5.
Versie 0.1

18-10-2011    NM
Versie 0.2

04-11-2011    NM
Versie 0.3  Opmerkingen Informatie Architect (HW) verwerkt.
                 Op 04-11-2011 Afgestemd met Quintiq en Tensing.


   Schema agency: 	Open Applications Group 
   OAGIS® Revision:    OAGIS 9_5  
   Date:               05 May 2011
   Name: /OAGi-BPI-Platform/org_openapplications_oagis/9_5/Developer/Nouns/CarrierRoute.xsd
-->
<xsd:schema xmlns:lo2="urn:postnl/mail/logisticscomponents/2" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:postnl/mail/trip/2" xmlns:lo1="urn:postnl/mail/logisticscomponents/1" xmlns:co1="urn:postnl/mail/components/1" xmlns:me1="urn:postnl/mail/meta/1" xmlns:fi1="urn:postnl/mail/fields1" targetNamespace="urn:postnl/mail/trip/2" elementFormDefault="qualified" attributeFormDefault="unqualified">
	<xsd:import namespace="urn:postnl/mail/logisticscomponents/1" schemaLocation="../../Common/OAGI/Components/LogisticsComponents1.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:import namespace="urn:postnl/mail/logisticscomponents/2" schemaLocation="../../Common/OAGI/Components/LogisticsComponents2.xsd"/>
	<xsd:element name="Trip" type="TripType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/oagis/9">Describes a scheduled journey that a particular goods transportation service provider (freight ) is requested to perform on the behalf of a shipper, customer or other transportation corrdinator. The journey may contain one or more stops.

There are many possible business applications in several environments that may use this capability.

A Trip is typically generated by a transportation planning system to coordinate and optimize the movement of many goods shipment to reduce overall freight cost, improve overall delivery schedules, and ensure that a carrier's equipment is utilized efficiently.

Other business systems typically interested in a Trip document include supply chain execution, supply chain visibility, warehouse management, and transportaion management systems.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="Stop" type="StopType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/oagis/9">Provides information pertaining to a particular pickup or delivery stop along the journey of a routed shipment.

Each instance of the Stop pertains to a single physical destination shipping location.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="StopReason" type="StopReasonType"/>
	<xsd:element name="RouteType" type="fi1:CodeType">
		<xsd:annotation>
			<xsd:documentation>Code type specifying the type of route.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:complexType name="TripType">
		<xsd:complexContent>
			<xsd:extension base="co1:HeaderType">
				<xsd:sequence>
					<!--<xsd:element ref="fi1:TrackingID" minOccurs="0"/>-->
					<!--<xsd:element ref="RouteType" minOccurs="0"/>-->
					<!--<xsd:element ref="fi1:ActualShipDateTime" minOccurs="0">
						<xsd:annotation>
							<xsd:documentation source="http://www.openapplications.org/oagis/9">Is the date that is used to identify the actual date and time a shipment occurs.</xsd:documentation>
							<xsd:documentation source="http://www.openapplications.org/oagis/9">Is the date that is used to identify the actual date and time a shipment occurs.</xsd:documentation>
						</xsd:annotation>
					</xsd:element>-->
					<!--<xsd:element ref="fi1:ScheduledDeliveryDateTime" minOccurs="0"/>-->
					<!--<xsd:element ref="fi1:ActualDeliveryDateTime" minOccurs="0"/>-->
					<!--<xsd:element ref="fi1:RequiredDeliveryDateTime" minOccurs="0">
						<xsd:annotation>
							<xsd:documentation source="http://www.openapplications.org/oagis/9">Is the date that the business partner is requesting delivery of goods to arrive.</xsd:documentation>
							<xsd:documentation source="http://www.openapplications.org/oagis/9">Is the date that the business partner is requesting delivery of goods to arrive.</xsd:documentation>
						</xsd:annotation>
					</xsd:element>-->
					<!--<xsd:element ref="fi1:PromisedDeliveryDateTime" minOccurs="0">
						<xsd:annotation>
							<xsd:documentation source="http://www.openapplications.org/oagis/9">Is the date that the supplier business partner promises delivery of goods</xsd:documentation>
							<xsd:documentation source="http://www.openapplications.org/oagis/9">Is the date that the business partner is supplying goods promises delivery of goods to arrive.</xsd:documentation>
						</xsd:annotation>
					</xsd:element>-->
					<!--<xsd:element ref="fi1:LoadingDateTime" minOccurs="0">
						<xsd:annotation>
							<xsd:documentation source="http://www.openapplications.org/oagis/9">Is the date that is used to mark the date and time a shipment loading process is complete.</xsd:documentation>
							<xsd:documentation source="http://www.openapplications.org/oagis/9">Is the date that is used to mark the date and time a shipment loading process is complete.</xsd:documentation>
						</xsd:annotation>
					</xsd:element>-->
					<!--<xsd:element ref="fi1:EarliestShipDateTime" minOccurs="0">
						<xsd:annotation>
							<xsd:documentation source="http://www.openapplications.org/oagis/9">This identifies the earliest possible date at which a shipment can be made.  This may be used in conjunction with the ShipPriorToDueDateInd which indicates that the item, shipping unit or delivery may be shipped early.</xsd:documentation>
							<xsd:documentation source="http://www.openapplications.org/oagis/9">This identifies the earliest possible date at which a shipment can be made.  This may be used in conjunction with the ShipPriorToDueDateInd which indicates that the item, shipping unit or delivery may be shipped early.</xsd:documentation>
						</xsd:annotation>
					</xsd:element>-->
					<!--<xsd:element ref="fi1:PromisedShipDateTime" minOccurs="0">
						<xsd:annotation>
							<xsd:documentation source="http://www.openapplications.org/oagis/9">Is the date the business partner supplying goods is promising goods to be shipped.</xsd:documentation>
						</xsd:annotation>
					</xsd:element>-->
					<!--<xsd:element ref="fi1:ScheduledShipDateTime" minOccurs="0">
						<xsd:annotation>
							<xsd:documentation source="http://www.openapplications.org/oagis/9">Identifies the date on which the goods are scheduled to be shipped.</xsd:documentation>
						</xsd:annotation>
					</xsd:element>-->
					<!--Maatwerk PostNL tbv Routeplan-->
					<xsd:element ref="co1:Status" minOccurs="0"/>
					<xsd:element ref="lo1:PlannedTripDateTimeWindow" minOccurs="0"/>
					<xsd:element ref="co1:Car" minOccurs="0"/>
					<xsd:element ref="co1:TransportCompanyParty" minOccurs="0" maxOccurs="unbounded"/>
					<xsd:element ref="co1:DriverParty" minOccurs="0"/>
					<xsd:element ref="co1:CoDriverParty" minOccurs="0"/>
					<xsd:element ref="fi1:StationCode" minOccurs="0"/>
					<xsd:element ref="co1:Process" minOccurs="0"/>
					<xsd:element ref="fi1:Area" minOccurs="0"/>
					<xsd:element ref="fi1:TransportRegion" minOccurs="0"/>
					<xsd:element ref="fi1:RouteID" minOccurs="0"/>
					<!--<xsd:element ref="fi1:TripDate" minOccurs="0"/>-->
					<!--<xsd:element ref="fi1:PointOfLoadingCode" minOccurs="0"/>-->
					<!--<xsd:element ref="fi1:PointOfShipmentCode" minOccurs="0"/>-->
					<!--<xsd:element ref="fi1:PointOfStagingCode" minOccurs="0"/>-->
					<!--<xsd:element ref="fi1:TransportationMethodCode" minOccurs="0"/>-->
					<!--<xsd:element ref="co1:TransportationTerm" minOccurs="0"/>-->
					<!--<xsd:group ref="co1:ShippingWeightAndVolumeGroup" minOccurs="0"/>-->
					<!--<xsd:element ref="lo1:Container" minOccurs="0"/>-->
					<!--<xsd:element ref="co1:Charge" minOccurs="0"/>-->
					<!--<xsd:element ref="co1:Party" minOccurs="0" maxOccurs="unbounded"/>-->
					<xsd:element ref="Stop" minOccurs="0" maxOccurs="unbounded">
						<xsd:annotation>
							<xsd:documentation>Provides information pertaining to a particular pickup or delivery stop along the journey of a routed shipment.

Each instance of the Stop pertains to a single physical destination shipping location.</xsd:documentation>
						</xsd:annotation>
					</xsd:element>
					<!--<xsd:element ref="fi1:UserArea" minOccurs="0"/>-->
				</xsd:sequence>
			</xsd:extension>
		</xsd:complexContent>
	</xsd:complexType>
	<xsd:complexType name="StopType">
		<xsd:sequence>
			<xsd:element ref="fi1:ID" minOccurs="0"/>
			<xsd:element ref="fi1:SequenceCode" minOccurs="0"/>
			<!--<xsd:element ref="lo1:PlannedStopTimeWindow" minOccurs="0"/>-->
			<xsd:element ref="fi1:PlannedStopTime" minOccurs="0"/>
			<xsd:element ref="co1:Location" minOccurs="0"/>
			<!--<xsd:element ref="fi1:ShipmentReferenceID" minOccurs="0"/>-->
			<!--<xsd:element ref="fi1:ShipUnitReferenceID" minOccurs="0"/>-->
			<!--<xsd:element ref="fi1:Type" minOccurs="0">
				<xsd:annotation>
					<xsd:documentation source="http://www.openapplications.org/oagis/9">Code type specifing the type of route stop.</xsd:documentation>
				</xsd:annotation>
			</xsd:element>-->
			<!--Maatwerk PostNL aanpassingen-->
			<!--<xsd:element ref="lo1:LoadTimeWindow" minOccurs="0"/>
			<xsd:element ref="lo1:UnloadTimeWindow" minOccurs="0"/>
			<xsd:element ref="lo1:FreightUnits" minOccurs="0" maxOccurs="unbounded"/>
			<xsd:element name="SpecialHandling" type="lo1:SpecialHandlingType" minOccurs="0" maxOccurs="unbounded"/>-->
			<!--<xsd:element ref="co1:StopParty" minOccurs="0" maxOccurs="unbounded"/>-->
			<!--<xsd:element ref="fi1:TrackingID" minOccurs="0"/>
			<xsd:element ref="fi1:ContainerID" minOccurs="0" maxOccurs="unbounded"/>-->
			<!--<xsd:group ref="me1:FreeFormTextGroup" minOccurs="0"/>-->
			<!--<xsd:group ref="co1:ShippingWeightAndVolumeGroup" minOccurs="0"/>-->
			<!--<xsd:element ref="co1:HazardousMaterial" minOccurs="0" maxOccurs="unbounded"/>-->
			<!--<xsd:element ref="co1:Charge" minOccurs="0" maxOccurs="unbounded"/>-->
			<!--<xsd:element ref="co1:Party" minOccurs="0" maxOccurs="unbounded"/>-->
			<!--<xsd:element ref="co1:DocumentReference" minOccurs="0" maxOccurs="unbounded"/>-->
			<xsd:element ref="StopReason" minOccurs="0" maxOccurs="unbounded">
				<xsd:annotation>
					<xsd:documentation>The reason the driver has to stop during the trip (nb. element alleen tbv structuur en ordening XSD.</xsd:documentation>
				</xsd:annotation>
			</xsd:element>
			<!--<xsd:element ref="StopActivity" minOccurs="0" maxOccurs="unbounded"/>-->
			<!--<xsd:element ref="fi1:UserArea" minOccurs="0"/>-->
		</xsd:sequence>
		<!--<xsd:attribute name="type" type="fi1:NormalizedStringType"/>-->
	</xsd:complexType>
	<xsd:complexType name="StopReasonType">
		<xsd:sequence>
			<!--<xsd:element ref="fi1:BillOfLadingID" minOccurs="0"/>-->
			<!--<xsd:element ref="fi1:ContainerID" minOccurs="0" maxOccurs="unbounded"/>-->
			<!--<xsd:group ref="me1:FreeFormTextGroup" minOccurs="0"/>-->
			<!--<xsd:element ref="fi1:TrackingID" minOccurs="0"/>-->
			<xsd:element ref="fi1:SequenceCode" minOccurs="0"/>
			<xsd:element ref="co1:StopParty" minOccurs="0"/>
			<xsd:element ref="lo2:StopActivity" minOccurs="0" maxOccurs="unbounded"/>
			<!--<xsd:element ref="co1:ShipToParty" minOccurs="0"/>-->
			<!--<xsd:element ref="co1:Party" minOccurs="0" maxOccurs="unbounded"/>-->
			<!--<xsd:element ref="co1:ShipUnitReference" minOccurs="0" maxOccurs="unbounded"/>
			<xsd:element ref="co1:ShipmentReference" minOccurs="0" maxOccurs="unbounded"/>-->
			<!--<xsd:group ref="co1:ReferencesGroup" minOccurs="0"/>-->
			<!--<xsd:element ref="co1:BillOfLadingReference" minOccurs="0"/>-->
			<!--<xsd:element ref="fi1:UserArea" minOccurs="0"/>-->
		</xsd:sequence>
	</xsd:complexType>
</xsd:schema>
