In this chapter the generic format was chosen to identify functions. Consider the
following two options:
1. Web services functionality format. This structure includes the following information:
service port type, operation name, message name, element name, and element data type.
It is recommended that delivered message names should include the suffix ???Request??? or
???Req.??? Conversely, returned message names should append ???Response??? or ???Res.??? The
following example illustrates the Web services functionality format.
2. Generic functionality format. Simply provide the message name, name of parameters,
and data types. Consider the following example, which illustrates functionality format for
sending and receiving messages.
Web Services Functionality Notation Format
portTypeName.operationName.messageName(elementName.elementType,. . .)
Example:
Sent Message
myPortName.getCustProfileOp.getCustProfileReq
(getCustProfileIn.custID.string)
Returned Message
myPortName.getCustProfileOp.getCustProfileRes
(getCustProfileOut.CustProf.string)
Generic Functionality Notation Format
messageName(parameter1.type, parameter2.type,. . .)
Example:
Sent Message
getAccountBalanceReq(customerID.string, startData.date, endDate.date)
Returned Message
getAccountBalanceRes(customerBalance.float)
Exhibit 14.13 illustrates two atomic services: the message originator account balance and
the market quotes message receiver.
Pages:
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511