Fwd: Re: [wsrm] Proposed clarificaiton resolutions to Ferriscomments 1,2

["Mark Peel" <mpeel@novell.com>]

--- Begin Message ---

• From: "Mark Peel" <mpeel@novell.com>
• To: "Tom Rutt" <tom@coastin.com>
• Date: Thu, 15 Jul 2004 10:39:44 -0600

  I agree "manages" is overly broad, but I think "controls" carries a
wrong implication: it suggests a multi-step procedure.  "Initiates"
similarly suggests a long-running process; we don't really want to
suggest *anything* about the way the process works.  I propose
"accomplishes".  If you don't like that, "effects" also works.




Mark Peel
Web Services Infrastructure
Novell, Inc.

>>> Tom Rutt <tom@coastin.com> 7/15/2004 11:07:59 AM >>>
perhaps "initiates" rather than "manages"

However, I thing Controls is close to the correct verb.  I prefer 
controls, or initates, to manages, because managment implies many 
operations.

Tom Rutt

Abbie Barbir wrote:

> see inline,
> abbie
>  
>
>     -----Original Message-----
>     *From:* Jacques Durand [mailto:JDurand@us.fujitsu.com] 
>     *Sent:* Wednesday, July 14, 2004 8:26 PM
>     *To:* WSRM (E-mail)
>     *Subject:* [wsrm] Proposed clarificaiton resolutions to Ferris
>     comments 1,2
>
>     Tom:
>
>     inline <JD>,
>     suggested updates on your proposal responding to Chris F. (here,
>     for comments #1 and #2 only).
>
>     It also appears that our definition of "Notify" in Section 1.5
is
>     too general, as we never intended to use Notify
>     to report on successful deliveries - as Chris assumes - but only
>     on failed deliveries, as described later in the spec.
>     So I narrow it accordingly in 1.5 below.
>
>     -Jacques
>
>     -------------------------
>     From: Tom Rutt [tom@coastin.com] 
>     Sent: Wednesday, July 14, 2004 1:59 PM
>     To: wsrm
>     Subject: [wsrm] Proposed clarificaiton resolutions to Ferris
comments
>     1,2,24,5,7,9,16,19
>
>     Proposed resolutions for some of Chris Ferris comments on
>     WS-Reliability
>     ED 1.05:
>
>      SNIP
>
>      Deliver:
>
>     An abstract operation associated with a Receiving RMP. When
>     invoked, the
>     operation makes the payload of one Reliable Message available to
the
>     Consumer from the Receiving RMP. For example, in one specific
>     implementation choice, the payload is placed into a queue by the
>     Receiving RMP to be consumed by an application component.
>
>     <JD> The "associated with a Receiving RMP" might still be
>     misinterpreted.
>     I would replace 1st sentence with:
>     "An abstract operation that controls a transfer from Receiving
RMP
>     to Consumer."  
>
>     <ab> I agree , the term associated is mileading. However, I also
>     think controls is still misleading. How about, "An abstract
>     operation that  manage a transfer from ...)
>
>     Submit:
>
>     An abstract operation associated with a Sending RMP. When
invoked,
>     the
>     operation transfers payload data from the Producer to the Sending
RMP
>     (e.g., a request to the Sending RMP to take responsibility for
the
>     Reliable Message).
>
>     <JD> I would replace 1st sentence with:
>     "An abstract operation that controls a transfer from Producer to
>     Sending RMP."
>
>      <ab> same change as above
>      
>      
>
>     Respond:
>
>     An abstract operation associated with a Receiving RMP. When
>     invoked, the
>     operation transfers payload data from the Consumer to a
Receiving
>     RMP.
>
>     <JD> I would replace 1st sentence with:
>     "An abstract operation that controls a transfer from Consumer to
>     Receiving RMP."
>
>      <ab> same change as above
>
>     Notify:
>
>     An abstract operation associated with a Sending RMP. When
invoked,
>     the
>     operation makes available a response payload received by the
Sending
>     RMP, to the Producer, or makes available to the Producer the
>     status of a
>     Reliable Message (e.g., a notification that the Sending RMP
failed to
>     send a Reliable Message).
>
>     <JD> similarly,
>     "An abstract operation that controls a transfer from Sending RMP
>     to Producer."
>     plus a narrowing: replace "the status" by "the failure status".
>
>      <ab> same change as above
>
>

-- 
----------------------------------------------------
Tom Rutt	email: tom@coastin.com; trutt@us.fujitsu.com 
Tel: +1 732 801 5744          Fax: +1 732 774 5133




To unsubscribe from this mailing list (and be removed from the roster
of the OASIS TC), go to
http://www.oasis-open.org/apps/org/workgroup/wsrm/members/leave_workgroup.php.

--- End Message ---