ONLY ANSWER IF YOU'RE WILLING TO ELABORATE! In your answer include "WHAT PROGRAMS" were used and "HOW" you did it. I will need to learn this and I will need to make edit and must know which application were used. Briefly explain your answer so I may understand. I will complain and I will cancel my membership if only an answer is provided. Thanks! **IMPORTANT: Provide a 2 part answer so that I can TELL THE DIFFERENCE! I AM NEW TO THIS AND WANT TO LEARN.
Part1A: Define a schema for a flight availability request application that requests flight availability for a city pair on a specific date for a specific number and type of passengers. Also include: time or time window, connecting cities, client preferences, e.g., airlines, flight types, etc. the request can be narrowed to request availability for a specific airline, specific flight, or specific booking class on a specific flight. LET ME KNOW WHAT YOU USED TO DO THIS? EG. Notepad++ AND HOW YOU DID THIS?
Part1B: Write a simple SOAP program that returns information about commercial flights from the XML Schema of Exercise 3.4 (practical part of Problem Set 1). You are expected to use an Integrated Development Environment (IDE) to code, debug, compile, and test your programs for both the client and the server side of the application. The application can be tested on a single host, or two remote hosts on the Internet. You submission should include the following components. 1) Source code of the application; 2) Executables and instructions how to run the application; 3) A brief report that discusses your design, your implementation (e.g., platform of development, programming language, etc), and test cases. LET ME KNOW LANGUAGE USED IF APPLICABLE AND HOW YOU DID THIS.
<xs:schema xmlns="http://www.opentravel.org/OTA/2003/05"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://www.opentravel.org/OTA/2003/05"
elementFormDefault="qualified" version="2.007" id="OTA2007A">
<xs:include schemaLocation="OTA_AirCommonTypes.xsd"/>
<xs:include schemaLocation="OTA_AirPreferences.xsd"/>
<xs:element name="OTA_AirLowFareSearchRQ">
<xs:annotation>
<xs:documentation xml:lang="en">
The Low Fare Search Request message requests priced itinerary options for
flights between specific city pairs on specific dates for specific numbers and
types of passengers. Optional request information can include:
- Time / Time Window
- Connecting cities.
- Client Preferences (airlines, cabin, flight types etc.)
The Low Fare Search request contains similar information to a Low Fare Search
entry on an airline CRS or GDS.
</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="POS" type="POS_Type">
<xs:annotation>
<xs:documentation xml:lang="en">Point of sale object.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="ProcessingInfo" minOccurs="0">
<xs:annotation>
<xs:documentation xml:lang="en">A collection of information that
specifies how the message processing should occur or how the data
should be returned.</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:attributeGroup ref="AirProcessingInfoGroup"/>
</xs:complexType>
</xs:element>
<xs:element name="OriginDestinationInformation" maxOccurs="10">
<xs:annotation>
<xs:documentation xml:lang="en">Origin and Destination location,
and time information for the Air Low Fare Search request.
</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:complexContent>
<xs:extension base="OriginDestinationInformationType">
<xs:sequence>
<xs:element name="AlternateLocationInfo" minOccurs="0">
...
<xs:complexType>
<xs:attribute name="OriginLocation"
type="ListOfStringLength1to8" use="optional">
...
</xs:attribute>
<xs:attribute name="DestinationLocation"
type="ListOfStringLength1to8" use="optional">
...
</xs:attribute>
</xs:complexType>
</xs:element>
<xs:element ref="TPA_Extensions" minOccurs="0"/>
</xs:sequence>
<xs:attribute name="RPH" type="RPH_Type" use="optional">
...
</xs:attribute>
<xs:attribute name="RefNumber" type="Numeric1to99"
use="optional">
...
</xs:attribute>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
<xs:element name="SpecificFlightInfo" type="SpecificFlightInfoType"
minOccurs="0">
...
</xs:element>
<xs:element name="TravelPreferences" minOccurs="0" maxOccurs="10">
...
<xs:complexType>
<xs:complexContent>
<xs:extension base="AirSearchPrefsType">
<xs:attribute name="FlexDatePref" use="optional">
...
</xs:attribute>
...
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
<xs:element name="TravelerInfoSummary">
...
<xs:complexType>
<xs:complexContent>
<xs:extension base="TravelerInfoSummaryType">
<xs:attribute name="TicketingCountryCode" type="ISO3166"
use="optional">
...
</xs:attribute>
<xs:attribute name="SpecificPTC_Indicator" type="xs:boolean"
use="optional">
...
</xs:attribute>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attributeGroup ref="OTA_PayloadStdAttributes"/>
<xs:attributeGroup ref="MaxResponsesGroup"/>
<xs:attribute name="DirectFlightsOnly" type="xs:boolean" use="optional"
default="false">
...
</xs:attribute>
<xs:attribute name="AvailableFlightsOnly" type="xs:boolean"
use="optional">
...
</xs:attribute>
</xs:complexType>
</xs:element>
</xs:schema>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns="http://www.opentravel.org/OTA/2003/05"
targetNamespace="http://www.opentravel.org/OTA/2003/05"
elementFormDefault="qualified" version="5.000" id="OTA2007A">
<xs:include schemaLocation="OTA_AirCommonTypes.xsd"/>
...
<xs:element name="OTA_AirLowFareSearchRS">
<xs:annotation>
<xs:documentation xml:lang="en">
The Low Fare Search Response message contains a number of 'Priced Itinerary'
options. Each includes:
- A set of available flights matching the client's request.
- Pricing information including taxes and full fare breakdown for each
passenger type
- Ticketing information
- Fare Basis Codes and the information necessary to make a rules entry.
This message contains similar information to a standard airline CRS or GDS Low
Fare Search Response message.
</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:choice>
<xs:sequence>
<xs:element name="Success" type="SuccessType">
<xs:annotation>
<xs:documentation xml:lang="en">Success
Standard way to indicate successful processing of an OTA message. Returning an
empty element of this type indicates success.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="Warnings" type="WarningsType" minOccurs="0">
<xs:annotation>
<xs:documentation xml:lang="en"> Standard way to indicate
successful processing of an OTA message, but one in which warnings are generated.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="PricedItineraries" type="PricedItinerariesType">
<xs:annotation>
<xs:documentation xml:lang="en">Successfull Low Fare priced
itineraries in response to a Low Fare Search request.
</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
<xs:element name="Errors" type="ErrorsType">
<xs:annotation>
<xs:documentation xml:lang="en"> A collection of errors that
occurred during the processing of a message.</xs:documentation>
</xs:annotation>
</xs:element>
</xs:choice>
</xs:sequence>
<xs:attributeGroup ref="OTA_PayloadStdAttributes">
<xs:annotation>
<xs:documentation xml:lang="en"> The OTA_PayloadStdAttributes
defines the standard attributes that appear on the root element for all
OTA payloads.</xs:documentation>
</xs:annotation>
</xs:attributeGroup>
</xs:complexType>
Get Answers For Free
Most questions answered within 1 hours.