W3C home > Mailing lists > Public > www-ws@w3.org > April 2001

Naming of WSDL Operations

From: <Ray_Gates@manulife.com>
Date: Tue, 17 Apr 2001 13:54:35 -0400
To: www-ws@w3.org
Message-ID: <OFCD60C4FE.35921ACF-ON85256A30.007464A3@manulife.com>

The WSDL 1.1 specification names its basic operations as follows:

- One-way  --  The endpoint receives a message.
- Request-response  --  The endpoint receives a message, and sends a
correlated message.
- Solicit-response --  The endpoint sends a message, and receives a
correlated message.
- Notification  --  The endpoint sends a message.

Only the last name has an intuitive interpretation, and even that is open
to misinterpretation.

"One-way" could just as easily mean "send" as "receive".
"Notification" could just as easily mean "receive" as "send".
In standard English. "request-response" and "solicit-response" appear
synonymous.

The names of the operations should be changed so that they are clearly
distinguishable.

Some possible alternatives are given below.

- for "one way" I suggest "listener", "receiver" (as nouns) or  "listen",
"receive" (as verbs)
- for "notification" I suggest  "notifier" or "notify"
- for "request-response" I suggest "provide-response"
- "solicit-response" could remain unchanged if contrasted with "provide
response" rather than "request-response".

If we equate paired request-response messages with "service requests", and
single messages with "event notification", then:
"one way" could become "event listener"
"notification" could become "event notifier"
"request-response" could become "service provider"
"solicit-response" could become "service requester"

For your consideration.
Regards,
Ray Gates
----------------


Ray Gates
Senior Technical Advisor
Technology Architecture
Manulife Financial
Tel: +1 (416) 926-3080 Fax: +1 (416) 926-5234
Email: ray_gates@manulife.com
Received on Tuesday, 17 April 2001 13:55:50 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:25:38 GMT