OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-msg message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: RE: non-ebXML links


My understanding is that a value of reliableMessagingMethod="Transport"
essentially means Other.  There are other RM methods which can produce
onceandonlyonce and not be ebXML.  This is not the same as
deliverySemantics="BestEffort" which really means no RM.

David Fischer
Drummond Group.

-----Original Message-----
From: Martin W Sachs [mailto:mwsachs@us.ibm.com]
Sent: Sunday, September 16, 2001 8:43 PM
To: Dan Weinreb
Cc: dmoberg@cyclonecommerce.com; david@drummondgroup.com;
david.burdett@commerceone.com; chris.ferris@east.sun.com;
arvola@tibco.com; ebxml-msg@lists.oasis-open.org
Subject: Re: non-ebXML links



If the MS specification provides only one reliable-messaging algorithm,
then this is fully covered by the deliverySemantics attribute and there is
no need for the reliableMessagingMethod attribute.

Also, I can't find any description of the what the "Transport" value of
reliableMessagingMethod is for,  Since the word "Transport" appears in the
header of each page, it's a bit hard to search on this one, especially with
Acrobat's very primitive search function.  I assume that what is meant is
that reliability is provided, if at all, by the Transport layer.  We don't
have a binding for any transport that provides reliable messaging. I
suppose that there will be one some day for HTTPR if it becomes a standard.
In any case, reliableMessagingMethod="Transport" is exactly the same as
deliverySemantics="bestEffort".  Both mean that reliability is not provided
by ebXML; it MIGHT be provided by the transport.  So, I see no reason to
have both.

Regards,
Marty

********************************************************************************
*****

Martin W. Sachs
IBM T. J. Watson Research Center
P. O. B. 704
Yorktown Hts, NY 10598
914-784-7287;  IBM tie line 863-7287
Notes address:  Martin W Sachs/Watson/IBM
Internet address:  mwsachs @ us.ibm.com
********************************************************************************
*****



Dan Weinreb <dlw@exceloncorp.com> on 09/16/2001 09:11:50 PM

Please respond to Dan Weinreb <dlw@exceloncorp.com>

To:   Martin W Sachs/Watson/IBM@IBMUS
cc:   dmoberg@cyclonecommerce.com, david@drummondgroup.com,
      david.burdett@commerceone.com, chris.ferris@east.sun.com,
      arvola@tibco.com, ebxml-msg@lists.oasis-open.org
Subject:  Re: non-ebXML links



   Date: Sun, 16 Sep 2001 17:48:02 -0400
   From: Martin W Sachs <mwsachs@us.ibm.com>

               for the sake of everyone's sanity (including
   our own), we should eliminate all mention of non-ebXML protocols. They
   are implementer choices, not part of the ebXML-MS spec.

Just to make sure that I understand your position: Do we also feel
that we should eliminate the reliableMessagingMethod attribute,
section 8.7.4, and section 10.1.2?

----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>






[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC