[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [ubl-dev] UBL Implementation based on SOAP with attachments
Hi Sacha, Thanks for this input. I'm not sure if I can introduce ebXML right now, since I am not the person who can decide this in this case. The other party has laid out the requirements for that. But it is for sure a very interesting technology to keep an eye on. The best thing I take away from your reply is that SOAP with attachments is actually considered a viable means of transportation of the business documents. I was a little bit worried about that, since I cannot find a lot of information about it. Do you have any experience with potential interoperability issues? One problem I still need to solve right now, is how to archive the XML messages. One of the requirements is that the order information should be accessible and regenerated for a period of 7 years. Of course it is not very difficult to store the XML files on disk, but I also would like to see from the filename which XML files belong together. The ebXML idea of having a correlation ID appeals to me. Another solution is to use the BuyersID. On the other hand I realized that one invoice could aggregate multiple orders, so 1 ID does not seem sufficient. I'll have to ponder about that a little bit more, I guess. Cheers, Franck -----Original Message----- From: Sacha Schlegel [mailto:sschlegel@cyclonecommerce.com] Sent: donderdag 5 januari 2006 19:36 To: Franck de Bruijn Cc: ubl-dev@lists.oasis-open.org Subject: Re: [ubl-dev] UBL Implementation based on SOAP with attachments Hi Franck Some more information about ebXML Messaging that might be of interest to you. ebXML Messaging 2.0 uses Soap with Attachments. The Soap header got an extension, the ebXML Message header. The ebXML message header includes the sender, the receiver, the name of the service, the name of the action, the message ID, a conversation ID for message correlation (eg all messages that belong to one instance of a collaborative business process). As Soap Body an ebXML manifest is present. The ebXML manifest references the business documents, that are the actual attachments to the SOAP message. This way the business documents must not be XML documents but can also be EDI or PNG binary documents. For encryption, W3C XML Encryption is used. For signature, W3C XML Digital Signature is used. The upcoming ebXML Messaging version 3.0 will be even more based on Web Services, and use appropriate WS-* components. Eg for security WS-Security will be used, for reliable messaging, either or both OASIS WS-RX and OASIS WS-Reliability will be used. The OASIS ebXML messaging Technical Committee can be found at http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ebxml-msg Regards Sacha On Thu, 2006-01-05 at 11:15 -0700, Sacha Schlegel wrote: > Hi Franck > > One possibility is to use parts of the ebXML framework (ebXML stands for > electronic business XML) [1] for your task. > > ebXML messaging allows you to transport business documents, such as UBL > documents, in a > > a) secure > b) reliable > c) standardised (ISO standard 15000-2:2004 [2]) and > d) interoperable > > way. > > There are commercial and even Open Source implementations available. > http://www.freebxml.org is a good place to find Open Source ebXML > component implementations ;) > > There are additional ebXML framework components that might be of > interest to you. > > ebXML Collaboration Protocol Profile and Agreement: > > An ebXML Collaboration Protocol Agreement for example is used as the > agreement between the parties how to "technically" exchange the business > documents. In an ebXML Collaboration Protocol Agreement for example, you > can define which transport protocol to use (HTTP or SMTP), you can list > the actual endpoints of the parties (HTTP address or email address), > whether to use security, whether to use reliablity, and if these are > used their technical parameters, the selection of the encryption > algorithm, digital signature algorithms, the public certificates used > for digital encryption, digital signature, SSL server certficates, SSL > client authentication, and many more. A cool thing, such a CPA XML file > can be used to configure an ebXML Messaging system. > > ebXML Business Processes: > > ebXML Business Processes can be used to specify the choreography, eg in > which order the business documents are supposed to be exchanged. The > ebXML Business Processes also allow you to make use of business signals, > which are used to align the current "collaboration" state between > trading partners. Such a signals indicate, that the receiving backend > application successfully received the business document and that it > could parse the business document sucessfully, another business signal > indicates that the backend application successfully processed the > business document or some business signals are used to indicate the > opposite, eg that there was a problem, a failure of some sort. > > ebXML Registry/Repository: > > A place to store (and share) and query all the different ebXML > artifacts. > > Hope this helps. > > Regards > > Sacha > > > [1] http://www.ebxml.org > [2] > http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=39973 &ICS1=35&ICS2=40&ICS3= > [3] http://www.freebxml.org > > On Thu, 2006-01-05 at 18:45 +0100, Franck de Bruijn wrote: > > Hi again! > > > > We will have to implement an UBL scheme based on webservices and more > > specifically using SOAP with attachments. > > > > Today I got a prototype working based on Java, Apache AXIS and JAXB and I'm > > actually very impressed how nice it all works together. > > > > The other party will work with SAP. > > > > I'm still a little bit worried, however, about interoperability issues. Does > > anyone have experience with this way of interchanging the XML files? What > > are your findings/thoughts on this? > > > > Thanks in advance, > > Franck > > > > > > --------------------------------------------------------------------- > > This publicly archived list supports open discussion on implementing the UBL OASIS Standard. To minimize spam in the > > archives, you must subscribe before posting. > > > > [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/ > > Alternately, using email: list-[un]subscribe@lists.oasis-open.org > > List archives: http://lists.oasis-open.org/archives/ubl-dev/ > > Committee homepage: http://www.oasis-open.org/committees/ubl/ > > List Guidelines: http://www.oasis-open.org/maillists/guidelines.php > > Join OASIS: http://www.oasis-open.org/join/ > > > > > --------------------------------------------------------------------- > This publicly archived list supports open discussion on implementing the UBL OASIS Standard. To minimize spam in the > archives, you must subscribe before posting. > > [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/ > Alternately, using email: list-[un]subscribe@lists.oasis-open.org > List archives: http://lists.oasis-open.org/archives/ubl-dev/ > Committee homepage: http://www.oasis-open.org/committees/ubl/ > List Guidelines: http://www.oasis-open.org/maillists/guidelines.php > Join OASIS: http://www.oasis-open.org/join/ > --------------------------------------------------------------------- This publicly archived list supports open discussion on implementing the UBL OASIS Standard. To minimize spam in the archives, you must subscribe before posting. [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/ Alternately, using email: list-[un]subscribe@lists.oasis-open.org List archives: http://lists.oasis-open.org/archives/ubl-dev/ Committee homepage: http://www.oasis-open.org/committees/ubl/ List Guidelines: http://www.oasis-open.org/maillists/guidelines.php Join OASIS: http://www.oasis-open.org/join/
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]