[Fwd: [ebxml-dev] Ebusinesswatch report on ebXML]

[Monica J Martin <Monica.Martin@Sun.COM>]

As provided by Pim. Thanks.

--- Begin Message ---

• From: Pim van der Eijk <lists@sonnenglanz.net>
• To: ebxml-dev@lists.ebxml.org
• Date: Wed, 02 Nov 2005 12:40:42 +0100

I got an email that pointed to the "sectoral e-business advisory",
ebusiness-watch.org.  
There is a recent document that provides some interesting comments:

"Systems such as ebXML have reached a point where they are now ready for
full deployment".

"If, as some contend, the market for Web Services has peaked, and Grid
Services are already the next big venture ... it is advisable for SME
managers to be very cautious before risking their business ... ebXML
represents a far safer and more viable option at this time".

"the investment in ebXML will continue to pay dividends for the foreseeable
future".

URL
http://www.ebusiness-watch.org/resources/documents/TR03_Interoperability_200
5_web.pdf 

-----Original Message-----
From: Pim van der Eijk [mailto:lists@sonnenglanz.net] 
Sent: 07 April 2005 20:51
To: 'Bryan Rasmussen'; ebxml-dev@lists.ebxml.org
Subject: RE: [ebxml-dev] messageID globally unique


Bryan,

The MessageId string format has to conform to the RFC 2822 production rules,
which specifies a.o. there has to be a "@" symbol in the middle of the
msg-id string value.  An implementation that just reuses a MIME library
function may report syntax error faults for ebXML messages without "@" in
their MessageIds.  The algorithm suggested to get a unique value is just an
example. In the case of UBL you could probably generate a syntax valid
unique MessageId by concatenating the UBL Invoice "ID" or "GUID" element
value, the "@" symbol and some string value derived from IdentifierType
subelements. 

Pim van der Eijk

-----Original Message-----
From: Bryan Rasmussen [mailto:brs@itst.dk]
Sent: 07 April 2005 15:21
To: 'ebxml-dev@lists.ebxml.org'
Subject: [ebxml-dev] messageID globally unique

Hi
from 3.1.6.1 of the ebxml Messaging services spec:

The REQUIRED element MessageId is a globally unique identifier for each
message conforming to MessageID[RFC2822]

By this is it just meant that MessageId must be globally unique and it is up
to the application to make sure that it is or is it meant that MessageId
must be generated using the recommended algorithm from RFC 2822 as follows:
   
	"The message identifier (msg-id) itself MUST be a globally unique
identifier for a message. The generator of the message identifier MUST
guarantee that the msg-id is unique. There are several algorithms that can
be used to accomplish this. Since the msg-id has a similar syntax to
angle-addr (identical except that comments and folding white space are not
allowed), a good method is to put the domain name (or a domain literal IP
address) of the host on which the message identifier was created on the
right hand side of the "@", and put a combination of the current absolute
date and time along with some other currently unique (perhaps sequential)
identifier available on the system (for example, a process id number) on the
left hand side. Using a date on the left hand side and a domain name or
domain literal on the right hand side makes it possible to guarantee
uniqueness since no two hosts use the same domain name or IP address at the
same time. Though other algorithms will work, it is RECOMMENDED that the
right hand side contain some domain identifier (either of the host itself or
otherwise) such that the generator of the message identifier can guarantee
the uniqueness of the left hand side within the scope of that domain. "

I would hope for the first one (and am supposing it is the first one but
this kind of confusion can arise when moving across specs) as I have my own
globally unique id that would make more sense for our application. 

--- End Message ---