No Description
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

xep-0056.xml 7.5KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184
  1. <?xml version='1.0' encoding='UTF-8'?>
  2. <!DOCTYPE xep SYSTEM 'xep.dtd' [
  3. <!ENTITY % ents SYSTEM "xep.ent">
  4. %ents;
  5. ]>
  6. <?xml-stylesheet type='text/xsl' href='xep.xsl'?>
  7. <xep>
  8. <header>
  9. <title>Business Data Interchange</title>
  10. <abstract>This document defines a way to transmit ebXML messages, ANSI X.11, EDIFACT/UN, and SAP iDoc over Jabber/XMPP.</abstract>
  11. &LEGALNOTICE;
  12. <number>0056</number>
  13. <status>Deferred</status>
  14. <type>Standards Track</type>
  15. <sig>Standards</sig>
  16. <dependencies/>
  17. <supersedes/>
  18. <supersededby/>
  19. <shortname>N/A</shortname>
  20. <author>
  21. <firstname>Ulrich</firstname>
  22. <surname>Staudinger</surname>
  23. <email>chicago5@gmx.de</email>
  24. <jid>uls@jabber.org</jid>
  25. </author>
  26. <revision>
  27. <version>0.3</version>
  28. <date>2002-11-18</date>
  29. <initials>uls</initials>
  30. <remark>added SAP iDoc, EDIFACT, changed from Base64 to XML aware, minor changes in wording</remark>
  31. </revision>
  32. <revision>
  33. <version>0.2</version>
  34. <date>2002-11-06</date>
  35. <initials>uls</initials>
  36. <remark>Changed namespace, improved structure, added ANSI X.12</remark>
  37. </revision>
  38. <revision>
  39. <version>0.1</version>
  40. <date>2002-11-06</date>
  41. <initials>uls</initials>
  42. <remark>Initial release.</remark>
  43. </revision>
  44. </header>
  45. <section1 topic='Introduction'>
  46. <p>
  47. ANSI X.12, EDIFACT/UN and ebXML are all standards. This document describes a fundamental approach to transmit messages that conform to these standards.
  48. </p>
  49. </section1>
  50. <section1 topic='Transmitting ebXML via XMPP'>
  51. <section2 topic='Introduction to ebXML'>
  52. <p>EbXML <note><link url='http://www.ebxml.org'>http://www.ebxml.org</link></note>, a subset of XML that is defined through OASIS.org, is quickly becoming a de-facto standard for electronic, unified, inter and intra business process communication and for business process specification. The direct adjacency to UN/CEFACT EDIFACT, especially object-oriented EDI, make the widespread use of ebXML for automatic business transaction negotiation, process definition, etc. quite likely.
  53. </p>
  54. </section2>
  55. <section2 topic='Protocol'>
  56. <p>
  57. ebXML Messages SHALL be transmitted within Jabber IQ chunks. The value of the 'type' attribute SHALL be 'set' and the chunk SHALL contain a &lt;query/&gt; child element with the namespace declaration set to 'http://jabber.org/protocol/ebxml'. The query element MUST contain the pure ebXML message. No SOAP envelope SHALL exist around the ebXML message. Reception of an ebXML iqed message must be acknowledged with an iq chunk including an empty query tag of the same namespace, the iq tag SHALL have the same ID.
  58. </p>
  59. <example caption='ebXML Envelope'><![CDATA[
  60. <iq from='a@b.c' to='d@e.f' type='set' id='some'>
  61. <query xmlns='http://jabber.org/protocol/ebxml'>
  62. [data]
  63. </query>
  64. </iq>
  65. ]]></example>
  66. <p>
  67. EbXML information is always transmitted in this envelope. No transformation of native ebXML tags into native Jabber tags is performed (e.g., ebXML reception receipt into Jabber reception receipt). The business logic, on top of Jabber transport logic, has to parse incoming IQ chunks and forward received ebXML information to the ebXML Messaging Service. The business logic has as well to pack the ebXML messages into IQ chunks and invoke the message delivery.
  68. </p>
  69. <p>
  70. Although a complex business transaction between two or more Trading Partners might require a payload that contains an array of business documents, binary images, or other related Business Information' <note>Walsh. 2002. <em>ebXML: The Technical Specifications</em>; p. 69</note>, only one ebXML message can be (at the moment) transmitted at a time in one message. However, the ebXML Message MAY contain payload in it's own payload envelope.
  71. </p>
  72. <p>It has to be noted: The karma restriction of XMPP, implied on clients, makes transmission of large amounts of payload (at the moment) to services or other clients from client side nearly impossible. However, components' karma is not restrained.
  73. </p>
  74. </section2>
  75. <section2 topic='Examples'>
  76. <example caption='ebXML Query from a client to a Gateway'><![CDATA[
  77. <iq to='ebxml.gateway.com' type='set' id='f0a0f0'>
  78. <query xmlns='http://jabber.org/protocol/ebxml'>
  79. <RegistryEntryQuery>
  80. <RegistryEntryFilter>
  81. objectType EQUAL "CPP" AND status EQUAL "Approved"
  82. </RegistryEntryFilter>
  83. <HasClassificationBranch>
  84. <ClassificationNodeFilter>
  85. id STARTSWITH "urn:urn:spsc:321118'
  86. </ClassificationNodeFilter>
  87. </HasClassificationBranch>
  88. </RegistryEntryQuery>
  89. </query>
  90. </iq>
  91. ]]></example>
  92. <p>
  93. The previous example transmits a query to a database with an ebXML interface. A requester searches for all companies dealing with 'Integrated curcuit components', here with UNSPSC code '321118'.
  94. </p>
  95. <example caption='ebXML component OK from component to client'><![CDATA[
  96. <iq to='client@server.com' from='ebxml.gateway.com' type='result' id='f0a0f0'>
  97. <query xmlns='http://jabber.org/protocol/ebxml'/>
  98. </iq>
  99. ]]></example>
  100. <p>
  101. This prior xml code is the result which every recieving unit has to send, after successfully recieving the iq chunk. Note, that this does not mean, the ebxml chunk has been accepted, parsed, or whatever, this is only on jabber level.
  102. </p>
  103. </section2>
  104. </section1>
  105. <section1 topic='Transmitting ANSI X.12 via XMPP'>
  106. <section2 topic='Introduction'>
  107. <p>ANSI X.12 is a character oriented protocol. X.12 is separated into segments. Segments are separated by an asterisk <note>Angeli, Streit, Gonfaloniere. 2000. <em>The SAP R/3 Guide to EDI and interfaces</em>; p. 133</note>.</p>
  108. </section2>
  109. <section2 topic='Protocol'>
  110. <p>ANSI X.12 messages SHALL be delivered in a query tag of an IQ chunk. The IQ chunk's type attribute SHALL be set to 'set'. The query's namespace attribute SHALL be set to 'http://jabber.org/protocol/ansi_x.12'. The query tag shall contain the ANSI X.12 message. The ANSI X.12 message SHALL NOT be Base64 encoded, but SHALL be XML aware.</p>
  111. </section2>
  112. <section2 topic='Example'>
  113. <example><![CDATA[
  114. <iq type='set' id='ANY' to='ANSI_X12Gate@way.com'>
  115. <query xmlns='http://jabber.org/protocol/ansi_x.12'>
  116. ST*850*000000101~
  117. BEG*00*NE*123456789*991125**AC~
  118. N1*BT***0111213~
  119. N1*ST***5566789~
  120. PO1*1*250*KGM*15.3*SR*EAN*MY1001~
  121. CTT*1*2~
  122. SE*7*000000101~
  123. </query>
  124. </iq>
  125. ]]></example>
  126. </section2>
  127. </section1>
  128. <section1 topic='Transmitting UN/EDIFACT via XMPP'>
  129. <section2 topic='Introduction'>
  130. <p>
  131. EDIFACT/UN is very similar to X.12 and differs only in the meaning of tags and in some syntactical details.
  132. </p>
  133. </section2>
  134. <section2 topic='Protocol'>
  135. <p>EDIFACT/UN messages SHALL be delivered in a query tag of an IQ chunk. The IQ chunk's type attribute SHALL be set to 'set'. The query's namespace attribute SHALL be set to 'http://jabber.org/protocol/edifact'. The query tag SHALL contain the UN/EDIFACT message. The UN/EDIFACT message SHALL NOT be Base64 encoded.</p>
  136. </section2>
  137. </section1>
  138. <section1 topic='Transmitting SAP iDoc via XMPP'>
  139. <section2 topic='Introduction'>
  140. <p>SAP Systems can create IDocs as receipts of transactions. These receipts can be used within other EDI systems, or within the SAP system. Of course transmission of IDocs can take place through XMPP as well.</p>
  141. </section2>
  142. <section2 topic='Protocol'>
  143. <p>SAP IDocs SHALL be transmitted in a query tag of an IQ chunk. The IQ chunk's type attribute SHALL be 'set. The query's namespace attribute SHALL be set to 'http://jabber.org/protocol/sap_idoc'. The query tag SHALL contain the iDoc, XML aware.
  144. </p>
  145. </section2>
  146. <section2 topic='Example'>
  147. <example><![CDATA[
  148. <iq type='set' id='ANY' from='sap_idoc_gate@way.com'>
  149. <query xmlns='http://jabber.org/protocol/sap_idoc'>
  150. EDI_DC0350000000000000001301230C30USDEL4111SAPI10
  151. ...
  152. </query>
  153. </iq>
  154. ]]></example>
  155. </section2>
  156. </section1>
  157. </xep>