]> $Id: BravoAirProcess.owl,v 1.50 2005/06/09 16:19:17 martin Exp $ OWL-S Coalition: BravoAir Example for OWL-S Process Model This is the top level process for BravoAir BravoAir_Process is a composite process. It is composed of a sequence whose components are 2 atomic processes, GetDesiredFlightDetails and SelectAvailableFlight, and a composite process, BookFlight. true &concepts;#Airport &concepts;#Airport &concepts;#FlightDate &concepts;#FlightDate &concepts;#RoundTrip &concepts;#AcctName &concepts;#Password &concepts;#Confirmation &concepts;#FlightList &concepts;#FlightItinerary &concepts;#ReservationNumber BookFlight (Composite) Log into account and confirm reservation It is composed of a sequence whose components are 2 atomic processes, LogIn and ConfirmReservation. &concepts;#AcctName &concepts;#Password &concepts;#FlightItineraryList &concepts;#FlightItinerary &concepts;#ReservationNumber true CompleteReservation (Composite) Check whether the login succeeded This if-statement is used to verify whether the user is logged in. &concepts;#AcctName &concepts;#FlightItineraryList &concepts;#FlightItinerary &concepts;#ReservationNumber true LoggedIn(AcctName) This condition will be true if the previous PerformLogIn operation was succesful Get details such as airports, prefered time, roundtrip etc &concepts;#Airport &concepts;#Airport &concepts;#FlightDate &concepts;#FlightDate &concepts;#RoundTrip &concepts;#FlightList SelectAvailableFlight (ATOMIC) Get users prefered flight choice from available itineraries &concepts;#FlightList &concepts;#FlightItineraryList A simple class to indicate that the user has logged into an account. If an AcctName instance belongs to this class it means that the user has logged in to the account with the correct password. Invoking LogIn process may result in this situtation. Normally, the account would become NotLoggedIn after a period of time but it is not reflected in this simple description The complement of being logged in. If an incorrect password is supplied for an account name that account would be in the state of NotLoggedIn to indicate failure. LogIn (ATOMIC) LogIn process accepts two inputs AcctName and PassWord and returns a boolean value to indicate if the login operation succeeded or not. &concepts;#AcctName &concepts;#Password &xsd;#boolean LogIn Succeeded Result This result simply says that when the correct password has been supplied for the given account name then the service returns the xsd:boolean value true and the user is logged in to the system as the effect of invoking this service. true hasPassword(AcctName, Password) LoggedIn(AcctName) If the correct account name, password pair is supplied then the given account name will be logged in as the effect of this operation LogIn Failed Result This result simply says that when given password was not correct for the account and as a result the account is in NotLoggedIn state. Note that, there is a a result variable defined Correct_Password to stand for the correct password for the given account. The client does not need to know the exact value of the correct password to evaluate/validate the inCondition. When the service returns xsd:boolean value false, the client should infer that there exists another Password instance (this could be represented as a bnode) which is different from the given input value LogIn_Password. &concepts;#Password false NotLoggedIn(AcctName) ConfirmReservation (ATOMIC) Confirm selected reservation &concepts;#FlightItineraryList &concepts;#Confirmation &concepts;#FlightItinerary &concepts;#ReservationNumber