Versions Compared

Version Old Version 26 New Version 27
Changes made by

WILSON Scott

WILSON Scott

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Code Block
languagexml
titleDonlonTOBTSettingServiceInformationDefinition.xsd
linenumberstrue
collapsetrue
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:don="http://www.swim.donlon-airport.com/swim-ops/gateway" targetNamespace="http://www.swim.donlon-airport.com/swim-ops/gateway" elementFormDefault="qualified" attributeFormDefault="unqualified" xml:lang="eng">

<!--SWIM-INFO-001 Need for information definitions-->
<!--This XML schema is an example of an information definition.-->

<!--SWIM-INFO-002 Information definition language-->
<!--This is given in the xs:schema element above as xml:lang="eng"-->

<!--SWIM-INFO-006 Information definition namespace-->
<!--This is given in the xs:schema element above as xmlns:don="http://www.swim.donlon-airport.com/swim-ops/gateway" targetNamespace="http://www.swim.donlon-airport.com/swim-ops/gateway"-->

<!--The following requirements are not present in this example: 
- SWIM-INFO-009 Preservation of meaning
- SWIM-INFO-010 Principles for definitions for concepts
- SWIM-INFO-011 Semantics of metadata
- SWIM-INFO-012 Use of data types
-->

<!--
====================================
information definition level 
====================================
-->
	<xs:annotation>
		<xs:documentation>
			<!--SWIM-INFO-003 Information definition identification-->
			<identification>
				<title>Donlon TOBT Setting Service Information Definition</title>
				<edition>0.93</edition>
				<referenceDate>2018-10-17</referenceDate>
			</identification>
			<!--SWIM-INFO-004 Information definition responsible party-->
			<responsibleParty>
				<responsiblePartyName>Donlon Airport Operator</responsiblePartyName>
				<contactDetails>http://www.donlon-airport.com/swim/service-request</contactDetails>
				<role>author</role>
			</responsibleParty>
			<!--SWIM-INFO-005 Information definition scope-->
			<scope>Information in support of the Donlon TOBT Setting Service. This includes the Target Off-Block Time and Flight Identification types needed for the TOBTSetting Request, TOBT Delete Request messages. It also includes the ResponseStatus type needed by the TOBT Setting Response and TOBT Delete Response messages.</scope>
		</xs:documentation>
	</xs:annotation>
	<!--
====================================
message types
===========================================
-->
	<xs:element name="TOBTSettingRequest" id="donlon002">
		<xs:complexType>
			<xs
-->
	<xs:element name="TOBTSettingRequest" id="donlon002">
		<xs:complexType>
			<xs:annotation>
				<xs:documentation>Message which provides the Target Off-Block Time value of a specific flight.</xs:documentation>
				<xs:documentation>
					<semanticCorrespondence>
						<outOfScope rationale="container"/>
					</semanticCorrespondence>
				</xs:documentation>
			</xs:annotation>
				<xs:documentation>Message which provides the Target Off-Block Time valuesequence>
				<!--SWIM-INFO-007 Information definition concepts-->
				<!--The element below (tobt) is an example of a specific flight.</xs:documentation>
				<xs:documentation>
					<semanticCorrespondence>
						<outOfScope rationale="container"/>
					</semanticCorrespondence>
				</xs:documentation>
			</xs:annotation>
			<xs:sequence> concept in XML Schema format. It contains the name of the concept (name="tobt"). The definition is captured in the xs:annotation element-->
				<!--SWIM-INFO-007008 Unique Informationidentifiers definitionfor concepts-->
				<!--The element below (tobt) ishas ana exampleunique ofidentifier arecorded concept in XMLits Schema format. It contains the name of the concept (name="tobt"). The definition is captured in the xs:annotation element-->id attribute (id="TOBTSettingRequest.tobt". -->				
				<xs:element name="tobt" type="don:TargetOffBlockTime" id="TOBTSettingRequest.tobt" minOccurs="1" maxOccurs="1">
					<xs:annotation>
						<xs:documentation>The Target Off-Block Time value to be set. TOBT is the time that an operator / handling agent estimates that an aircraft will be ready, all doors closed, boarding bridge removed, push back vehicle present, ready to start up / push back immediately upon reception of clearance from the TWR.</xs:documentation>
						<xs:documentation>
							<semanticCorrespondence>
								<mapping>
									<trace>urn:aero:airm:1.0.0:ConceptualModel:Subjects:Flight:FlightEvent:TargetOffBlockTime</trace>
									<trace>urn:aero:airm:1.0.0:LogicalModel:Subjects:Flight:FlightEvent:OffBlockReady@time</trace>
									<trace>urn:aero:airm:1.0.0:LogicalModel:Subjects:Common:Codelists:CodePlanningStatusType@TARGET</trace>
								</mapping>
							</semanticCorrespondence>
						</xs:documentation>
					</xs:annotation>
				</xs:element>
				<xs:element name="flightId" type="don:ICAOFlightIdentification" id="TOBTSettingRequest.flightId" minOccurs="1" maxOccurs="1">
					<xs:annotation>
						<xs:documentation>The ICAO identifier of the specified flight</xs:documentation>
						<xs:documentation>
							<semanticCorrespondence>
								<trace>urn:aero:ses:eurocontrol:airm:1.0.0:ConceptualModel:Subjects:Flight:FlightIdentifier:ICAOFlightID</trace>
							</semanticCorrespondence>
						</xs:documentation>
					</xs:annotation>
				</xs:element>
			</xs:sequence>
		</xs:complexType>
	</xs:element>
	<xs:element name="TOBTSettingResponse" id="donlon031">
		<xs:complexType>
			<xs:annotation>
				<xs:documentation>Message which responds the validity of a previously sent TOBTSettingRequest message.</xs:documentation>
				<xs:documentation>
					<semanticCorrespondence>
						<outOfScope rationale="container"/>
					</semanticCorrespondence>
				</xs:documentation>
			</xs:annotation>
			<xs:sequence>
				<xs:element name="responseStatus" type="don:ResponseStatus" id="TOBTSettingResponse.responseStatus" minOccurs="1" maxOccurs="1">
					<xs:annotation>
						<xs:documentation>Status of the response to the service request</xs:documentation>
						<xs:documentation>
							<semanticCorrespondence>
								<outOfScope rationale="container"/>
							</semanticCorrespondence>
						</xs:documentation>
					</xs:annotation>
				</xs:element>
			</xs:sequence>
		</xs:complexType>
	</xs:element>
	<xs:element name="TOBTDeleteRequest" id="donlon032">
		<xs:complexType>
			<xs:annotation>
				<xs:documentation>Message which requests deleting the last TOBT value of the specified flight.</xs:documentation>
				<xs:documentation>
					<semanticCorrespondence>
						<outOfScope rationale="container"/>
					</semanticCorrespondence>
				</xs:documentation>
			</xs:annotation>
			<xs:sequence>
				<xs:element name="flightId" type="don:ICAOFlightIdentification" id="TOBTDeleteRequest.flightId" minOccurs="1" maxOccurs="1">
					<xs:annotation>
						<xs:documentation>The ICAO identifier of the specified flight</xs:documentation>
						<xs:documentation>
							<semanticCorrespondence>
								<trace>urn:aero:ses:eurocontrol:airm:1.0.0:ConceptualModel:Subjects:Flight:FlightIdentifier:ICAOFlightID</trace>
							</semanticCorrespondence>
						</xs:documentation>
					</xs:annotation>
				</xs:element>
			</xs:sequence>
		</xs:complexType>
	</xs:element>
	<xs:element name="TOBTDeleteResponse" id="donlon042">
		<xs:complexType>
			<xs:annotation>
				<xs:documentation>Message which responds the validity of a previously sent TOBTDeleteRequest message.</xs:documentation>
				<xs:documentation>
					<semanticCorrespondence>
						<outOfScope rationale="container"/>
					</semanticCorrespondence>
				</xs:documentation>
			</xs:annotation>
			<xs:sequence>
				<xs:element name="responseStatus" type="don:ResponseStatus" id="TOBTDeleteResponse.responseStatus" minOccurs="1" maxOccurs="1">
					<xs:annotation>
						<xs:documentation>Status of the response to the service request</xs:documentation>
						<xs:documentation>
							<semanticCorrespondence>
								<outOfScope rationale="container"/>
							</semanticCorrespondence>
						</xs:documentation>
					</xs:annotation>
				</xs:element>
			</xs:sequence>
		</xs:complexType>
	</xs:element>
	<!--
====================================
complex types
====================================
-->
	<xs:complexType name="ICAOFlightIdentification">
		<xs:annotation>
			<xs:documentation>Flight identification structure based on usual ICAO fields present in the Flight Plan</xs:documentation>
			<xs:documentation>
				<semanticCorrespondence>
					<outOfScope rationale="container"/>
				</semanticCorrespondence>
			</xs:documentation>
		</xs:annotation>
		<xs:sequence>
			<xs:element name="aircraftIdentification" type="don:AircraftIdentification" id="ICAOFlightIdentification.aircraftIdentification" minOccurs="1" maxOccurs="1">
				<xs:annotation>
					<xs:documentation>Name used by ATS units to identify and communicate with the aircraft.</xs:documentation>
					<xs:documentation>
						<semanticCorrespondence>
							<mapping>
								<trace dataType="string">urn:aero:airm:1.0.0:LogicalModel:Subjects:Flight:FlightIdentifier:AircraftIdentification</trace>
							</mapping>
						</semanticCorrespondence>
					</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element name="estimatedOffBlockTime" type="don:EstimatedOffBlockTime" id="ICAOFlightIdentification.estimatedOffBlockTime" minOccurs="1" maxOccurs="1">
				<xs:annotation>
					<xs:documentation>Date and time at which the aircraft will off-block according to ICAO flight plan field.</xs:documentation>
					<xs:documentation>
						<semanticCorrespondence>
							<mapping>
								<trace>urn:aero:airm:1.0.0:ConceptualModel:Subjects:Flight:FlightEvent:EstimatedOffBlockTime</trace>
								<trace>urn:aero:airm:1.0.0:LogicalModel:Subjects:Flight:FlightEvent:OffBlock@time</trace>
								<trace>urn:aero:airm:1.0.0:LogicalModel:Subjects:Common:Codelists:CodePlanningStatusType@ESTIMATED</trace>
							</mapping>
						</semanticCorrespondence>
					</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element name="icaoDepartureAerodrome" type="don:ICAODepartureAerodrome" id="ICAOFlightIdentification.icaoDepartureAerodrome" minOccurs="1" maxOccurs="1">
				<xs:annotation>
					<xs:documentation>ICAO code of the scheduled departure aerodrome.</xs:documentation>
					<xs:documentation>
						<semanticCorrespondence>
							<mapping>
								<trace>urn:aero:airm:1.0.0:LogicalModel:Subjects:BaseInfrastructure:AerodromeInfrastructure:Aerodrome@locationIndicatorICAO</trace>
								<trace>urn:aero:airm:1.0.0:LogicalModel:Subjects:Flight:Flight@departureAerodrome</trace>
							</mapping>
						</semanticCorrespondence>
					</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element name="icaoArrivalAerodrome" type="don:ICAOArrivalAerodrome" id="ICAOFlightIdentification.icaoArrivalAerodrome" minOccurs="1" maxOccurs="1">
				<xs:annotation>
					<xs:documentation>ICAO code of scheduled destination aerodrome.</xs:documentation>
					<xs:documentation>
						<semanticCorrespondence>
							<mapping>
								<trace>urn:aero:airm:1.0.0:LogicalModel:Subjects:BaseInfrastructure:AerodromeInfrastructure:Aerodrome@locationIndicatorICAO</trace>
								<trace>urn:aero:airm:1.0.0:LogicalModel:Subjects:Flight:Flight@destinationAerodrome</trace>
							</mapping>
						</semanticCorrespondence>
					</xs:documentation>
				</xs:annotation>
			</xs:element>
		</xs:sequence>
	</xs:complexType>
	<xs:complexType name="ResponseStatus">
		<xs:annotation>
			<xs:documentation>Status of the response to the service request</xs:documentation>
		</xs:annotation>
		<xs:sequence>
			<xs:element name="reasonForRejection" type="don:ReasonForRejection" id="ResponseStatus.reasonForRejection" minOccurs="1" maxOccurs="1">
				<xs:annotation>
					<xs:documentation>Code or textual description on the reason for rejection.</xs:documentation>
					<xs:documentation>
						<semanticCorrespondence>
							<outOfScope rationale="messaging"/>
						</semanticCorrespondence>
					</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element name="status" type="don:Status" id="ResponseStatus.status" minOccurs="1" maxOccurs="1">
				<xs:annotation>
					<xs:documentation>Specifies whether the related request has been accepted or not. Values: ACCEPTED, REJECTED</xs:documentation>
					<xs:documentation>
						<semanticCorrespondence>
							<outOfScope rationale="messaging"/>
						</semanticCorrespondence>
					</xs:documentation>
				</xs:annotation>
			</xs:element>
		</xs:sequence>
	</xs:complexType>
	<!--
====================================
simple types
====================================
-->
	<!--SWIM-INFO-007 Information definition concepts-->
	<!--The element below (TargetOffBlockTime) is an example of a concept in XML Schema format. It contains the name of the concept (name="TargetOffBlockTime"). The definition is captured in the xs:annotation element. The type is captured in the restriction (xs:dateTime)-->
 	<xs:simpleType name="TargetOffBlockTime" id="donlon021">
		<xs:annotation>
			<xs:documentation>The time that an operator / handling agent estimates that an aircraft will be ready, all doors closed, boarding bridge removed, push back vehicle present, ready to start up / push back immediately upon reception of clearance from the TWR.</xs:documentation>
		</xs:annotation>
		<xs:restriction base="xs:dateTime"/>
	</xs:simpleType>
	<xs:simpleType name="AircraftIdentification" id="donlon022">
		<xs:annotation>
			<xs:documentation>Name used by ATS units to identify and communicate with the aircraft. String of 1 to 7 alphanumeric characters.</xs:documentation>
		</xs:annotation>
		<xs:restriction base="xs:string">
			<xs:minLength value="1"/>
			<xs:maxLength value="7"/>
		</xs:restriction>
	</xs:simpleType>
	<xs:simpleType name="EstimatedOffBlockTime" id="donlon023">
		<xs:annotation>
			<xs:documentation>Date and time at which the aircraft will off-block according to ICAO flight plan field.</xs:documentation>
		</xs:annotation>
		<xs:restriction base="xs:dateTime"/>
	</xs:simpleType>
	<xs:simpleType name="ICAOArrivalAerodrome" id="donlon024">
		<xs:annotation>
			<xs:documentation>ICAO code of scheduled destination aerodrome.</xs:documentation>
		</xs:annotation>
		<xs:restriction base="don:ICAOAerodromeLocationIndicator"/>
	</xs:simpleType>
	<xs:simpleType name="ICAODepartureAerodrome" id="donlon025">
		<xs:annotation>
			<xs:documentation>ICAO code of the scheduled departure aerodrome.</xs:documentation>
		</xs:annotation>
		<xs:restriction base="don:ICAOAerodromeLocationIndicator"/>
	</xs:simpleType>
	<xs:simpleType name="ICAOAerodromeLocationIndicator" id="donlon026">
		<xs:annotation>
			<xs:documentation>ICAO code of scheduled destination aerodrome. String of 4 alphabetic uppercase characters.</xs:documentation>
		</xs:annotation>
		<xs:restriction base="xs:string">
			<xs:length value="4"/>
		</xs:restriction>
	</xs:simpleType>
	<xs:simpleType name="ReasonForRejection" id="donlon027">
		<xs:annotation>
			<xs:documentation>Code or textual description on the reason for rejection</xs:documentation>
		</xs:annotation>
		<xs:restriction base="xs:string"/>
	</xs:simpleType>
	<xs:simpleType name="Status" id="donlon028">
		<xs:annotation>
			<xs:documentation>Specifies whether a request has been accepted or not.
Values:
    ACCEPTED
    REJECTED</xs:documentation>
		</xs:annotation>
		<xs:restriction base="xs:string">
			<xs:enumeration value="ACCEPTED"/>
			<xs:enumeration value="REJECTED"/>
		</xs:restriction>
	</xs:simpleType>
</xs:schema>

...