In the next section, we discuss the requirements for the description of the message exchange behavior of a single web service, which can be thought of as a single role in a multi-role business protocol. The combination of services in business protocols is discussed in a subsequent section. In this section, we use a simple scenario to motivate the requirements discussion. TAWS has multiple service descriptions, one for customers and one or more for providers. The customer protocol allows access to both registered and new customers.
Registered customers can use defaults based on known profile information.
The process of making a travel plan is considered a long-running interaction. TAWS maintains the itinerary for each travel plan and provides modification and cancellation time windows and processes for each leg of travel and each service. The option of canceling the entire itinerary is always available. There may be penalties or fees applied for cancellation and modification depending on the timing. Being an internal corporate service, TAWS also allows its customers to ask for payroll advances to pay for travel.