wsrm message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: RE: [wsrm] Proposed clarificaiton resolutions to Ferris comments1,2
- From: Jacques Durand <JDurand@us.fujitsu.com>
- To: "'Alan Weissberger'" <ajwdct@technologist.com>
- Date: Thu, 15 Jul 2004 17:38:04 -0700
Alan:
Although we don't want to debate more than necessary on the wording,
these
comments (#1 and #2) from C.F. need be taken seriously as they show that
the
current wording can mislead external readers into an interpretation /
implementation that is narrower than we intended.
Agree
we should conclude quickly on this.
About
initiate vs control vs manage:
I
think we may just use "transfer" instead after all, (as Doug suggests), as
long as transfer is understood as
a
transfer of control on the message (not necessarily as a physical data
transfer). (see my previous mail)
In
which case we need make that clear.
Jacques
-Can we please try not to spend too much time on wordsmithing responses to
(very) late comments.
-I prefer control or intiate, as management can imply many different
things
Alan
Alan Weissberger
1 408 863 6042 voice
1 408 863 6099 fax
----- Original Message -----
From: Tom Rutt
<TOM@COASTIN.COM>
Date: Thu, 15 Jul 2004 12:07:59 -0400
To: Abbie
Barbir
Subject: Re: [wsrm] Proposed
clarificaiton resolutions to Ferris comments1,2
> 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 ,
> > 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:
> >
&
gt; > 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.
> >
> > 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."
>
>
> > 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).
> >
> > I would
replace 1st sentence with:
> > "An abstract operation that controls
a transfer from Producer to
> > Sending RMP."
> >
>
> 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.
> >
> > I would replace 1st sentence with:
> > "An abstract operation that controls a transfer from Consumer to
> ; > Receiving RMP."
> >
> > 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).
> >
> > similarly,
> > "An
abstract operation that controls a transfer from Sending RMP
> > to
Producer."
> > plus a narrowing: replace "the status" by "the
failure status".
> >
> > same change as above
>
>
> >
>
> --
>
----------------------------------------------------
> Tom Rutt email:
tom@coastin.com; trutt@us.fujitsu.com < BR>> 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.
>
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]