DR058: Interaction patterns

• From: Alex Ceponkus <aceponkus@bowstreet.com>
• Date: Wed, 6 Dec 2000 14:19:07 -0500
• To: xml-dist-app@w3.org
• Message-ID: <27D6DE55E78ED411872100B0D049008D2E01D5@bst-mail01.pnh.bowstreet.com>

DR058 currently reads as follows:
"Shall support multiple interaction patterns (e.g. request/response, RPC,
point-to-point, publish/subscribe)."

It overlaps with DR067 "other interaction patterns." from the 'other
requirements' section, so I suggest we drop DR067.

There is a small amount of overlap with DR304 that lists the following
interaction patterns: "one-way or event, synchronous, or two-way request
response".

Also, RPC is already converted in great detail.

We might want to consider changing DR058 from an open ended requirement to a
specific list:
- request/response  (Is this the same as synchronous ??)
- point-to-point  (same as one way & events ??)
- publish/subscribe
- store and forward

I suggest, we change "shall support" to "shall not preclude".  Depending on
the underlying transport, not all interaction patterns will be readily
available.

Any comments?

Alex

Received on Wednesday, 6 December 2000 14:23:39 UTC