RE: [ebxml-dev] ebXML Message Polling Mechanism

[David Fischer <david@drummondgroup.com>]

When we started the first UCC sponsored ebXML-MS Interoperability test, v2.0 was
already significantly taking shape (although at the time it was called v1.1) so
we decided to conform to the new spec.  Consequently, we never ran any tests on
v1.0.

The main changes in ebXML-MS from v1.0 to v2.0:

	Via - Gone
	TraceHeaderList - Gone
	DeliveryReceipt - Gone
	MessageHeader/QualityOfServiceInfo - Gone
		deliverySemantics - Gone
		messageOrderSemantics - Gone
		deliveryReceiptRequested - Gone
	MessageOrder - New top level element containing the
			SequenceNumber child element
	MessageHeader - Added DuplicateElimination child element
			to replace deliverySemantics attribute
	SyncReply - Changed to top level element
	AckRequested - Changed from Attribute to top level element
			Added Actor (nextMSH or ToPartyMSH) attribute
	Acknowledgment - Added Actor (nextMSH or ToPartyMSH) attribute
			Added RefToMessageId element
	MessageHeader/PartyId - Added Role child element
	Use of a CPA is now REQUIRED

We also did some rather major reorganizing of the spec into Core Components and
Additional Features (which are all OPTIONAL).  As you can see, these changes
make v2.0 not backward compatible.

I don't claim this is a definitive list (I am not aware that anyone has made one
yet) but it covers the salient points.

Regards,

David Fischer
Drummond Group
ebXML-MS Editor

-----Original Message-----
From: Anders Tholén [mailto:anders_tholen@yahoo.com]
Sent: Friday, March 01, 2002 1:29 AM
To: David Fischer; Anders Tholén
Cc: Beth Morrow
Subject: SV: [ebxml-dev] ebXML Message Polling Mechanism


Thank you for yor quick response.

Have similar tests been made for ebXML MS v1.0? (Which is what we're
implementing) Do you know where to find a summary of the main changes in
v2.0 and possible "v2"-considerations that should be taken into account when
making an v1.0 implementation?

With best regards

Anders Tholén

-----Ursprungligt meddelande-----
Från: David Fischer [mailto:david@drummondgroup.com]
Skickat: den 1 mars 2002 01:43
Till: Anders Tholén
Kopia: Beth Morrow
Ämne: RE: [ebxml-dev] ebXML Message Polling Mechanism


Yes, the first round of ebXML-MS v2.0 interoperability tests has just
concluded
with these four vendors completing the test.

Sybase
Sterling Commerce
Cyclone Commerce
bTrade

There will be another round this summer, date TBD.

Regards,

David Fischer
Drummond Group.

-----Original Message-----
From: Anders Tholén [mailto:anders_tholen@yahoo.com]
Sent: Thursday, February 28, 2002 6:05 PM
To: David Fischer
Subject: SV: [ebxml-dev] ebXML Message Polling Mechanism


Thank you for the information below.

I read with great interest the Edi over internet case study presented on the
Drummond Group site. We are presently implementing ebXML MS using webMethods
software (which is not yet General Availability).

What are the significant differences between ebXML and AS1/AS2? Are AS1/AS2
used in new implementations or is it/will it be gradually replaced by ebXML
MS?

Do you plan to do any interoperability tests with different vendors ebXML MS
modules?

Is it fair to say that the conclusions from the case studies are as relevant
for ebXML MS?

Thank you in advance.

With best regards

Anders Tholén

-----Ursprungligt meddelande-----
Från: David Fischer [mailto:david@drummondgroup.com]
Skickat: den 28 februari 2002 15:50
Till: Bell Stephen; ebxml-dev@lists.ebxml.org
Ämne: RE: [ebxml-dev] ebXML Message Polling Mechanism


ebXML-MS does not support PULL.

However, ebXML-MS does support multiple transfer protocols -- HTTP, SMTP,
FTP.
If your customers are overly security conscience, try using SMTP.  There are
trade-offs of course.  SMTP will be slower and will not support larger
files.

Regards,

David Fischer
Drummond Group.

-----Original Message-----
From: Bell Stephen [mailto:stephen.bell@cpgmarket.com]
Sent: Thursday, February 28, 2002 1:46 AM
To: ebxml-dev@lists.ebxml.org
Subject: [ebxml-dev] ebXML Message Polling Mechanism


Does anyone know if ebXML supports a pull mechanism in terms of polling for
messages rather than pushing messages to their intended recipients?
We are a 3rd party and are faced with the task of having to deliver messages
to
customers who have security concerns and do not want to allow direct push of
messages through their firewall.

Thanks,
Steve

----------------------------------------------------------------
The ebxml-dev list is sponsored by OASIS.
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.ebxml.org/ob/adm.pl>


----------------------------------------------------------------
The ebxml-dev list is sponsored by OASIS.
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.ebxml.org/ob/adm.pl>


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com