389:
108:(OASIS). A joint coordinating committee composed of representatives from each of the two organizations led the effort. Quarterly meetings of the working groups were held between November 1999 and May 2001. At the final plenary a Memorandum of Understanding was signed by the two organizations, splitting up responsibility for the various specifications but continuing oversight by the joint coordinating committee.
215:
message. Multiple business payloads may be attached to a single message, and the format of the payloads is beyond the scope of the ebXML specifications. The information trading partners place in ebMS messages is largely dictated by the CPA agreement that defines the relationship between them. The
170:
based documents specifying a trading agreement between trading partners. Each trading partner will have their own
Collaboration Protocol Profile (CPP) document that describes their abilities in an XML format. For instance, this can include the messaging protocols they support, or the security
80:
While the ebXML standards adopted by ISO and OASIS seek to provide formal XML-enabled mechanisms that can be implemented directly, the ebXML architecture is on concepts and methodologies that can be more broadly applied to allow practitioners to better implement e-business solutions.
202:
The
Message Service Specification (ebMS) describes a communication-neutral mechanism Message Service Handlers (MSH) must implement in order to exchange business documents. ebMS3.0 is the current version of the specification. ebMS3.0 is built as an extension on top of the
171:
capabilities they support. A CPA (Collaboration
Protocol Agreement) document is the intersection of two CPP documents, and describes the formal relationship between two parties. The following information will typically be contained in a CPA document:
512:
Naujok, Klaus-Dieter; Huemer, Christian (2008), "Case Study: Designing ebXML — The Work of UN/CEFACT", in
Rebstock, Michael; Fengel, Janina; Paulheim, Heiko (eds.),
698:
283:
135:
138:(ISO) has approved the following five ebXML specifications as the ISO 15000 standard, under the general title, Electronic business eXtensible markup language:
779:
211:
message contains the meta-data required to exchange the business document in a secure and reliable manner, while the business payload is attached to the
582:
58:
658:
68:
The melding of these components began in the original ebXML work and the theoretical discussion continues today. Other work relates, such as the
628:
529:
187:
Rules to follow when acknowledgments are not received for messages, including how long to wait before resending, and how many times to resend
84:
A particular instance is the Core
Components Technical Specification (CCTS) work that continues within UN/CEFACT, whereas its cousin - UBL -
683:
723:
703:
668:
633:
134:
After completion of the 6 specifications by the two organizations, 5 parts of the work were submitted to ISO TC 154 for approval. The
603:
488:
432:
410:
794:
784:
738:
638:
46:
The ebXML architecture is a unique set of concepts; part theoretical and part implemented in the existing ebXML standards work.
733:
789:
708:
673:
88:- specification is used within OASIS that implements specific XML transactions by applying the principles of CCTS to typical
158:
OASIS technical committees and UN/CEFACT retain the responsibility for maintaining and advancing the above specifications.
774:
575:
769:
693:
131:
All work was completed based on a normative requirements document and the ebXML Technical
Architecture Specification.
85:
50:
618:
608:
175:
Identification information: the unique identifiers for each party and their roles within the trading relationship
54:
653:
613:
568:
403:
397:
69:
414:
555:
204:
592:
105:
32:
178:
Security information: for instance, are digital signatures required, and what algorithms do they use
40:
476:
111:
The original project envisioned five layers of data specification, including XML standards for:
525:
39:
whose mission is to provide an open, XML-based infrastructure that enables the global use of
517:
500:
468:
246:
ebMS is communication protocol neutral, although the most common underlying protocols are
43:
information in an interoperable, secure, and consistent manner by all trading partners.
310:
763:
678:
268:
233:
480:
181:
Communication information: the protocols that will be used when exchanging documents
728:
663:
89:
62:
743:
688:
521:
263:
455:
504:
278:
27:(pronounced ee-bee-ex-em-el, ) as it is typically referred to, is a family of
101:
36:
374:
363:
352:
341:
330:
184:
Endpoint locations: the URL, service and action messages should be sent to
273:
623:
72:
work and the OASIS BCM (Business-Centric
Methodology) standard (2006).
560:
92:
transactions such as invoice, purchase order, ship notice and so on.
472:
106:
Organization for the
Advancement of Structured Information Standards
102:
United
Nations Centre for Trade facilitation and Electronic Business
311:"UN/CEFACT Announces Successful Completion of ebXML Standards Work"
216:
following information is typically contained within ebMS messages:
49:
The ebXML work stemmed from earlier work on ooEDI (object oriented
748:
718:
142:
ISO 15000-1: ebXML Collaborative
Partner Profile Agreement (ebCPP)
648:
251:
247:
212:
208:
564:
713:
382:
239:
An indication for whether duplicate messages should be ignored
167:
28:
313:(Press release). Geneva, Switzerland: OASIS (XML Cover Pages)
100:
ebXML was started in 1999 as a joint initiative between the
145:
ISO 15000-2: ebXML Messaging Service Specification (ebMS)
151:
ISO 15000-4: ebXML Registry Services Specification (ebRS)
550:
545:
154:
ISO 15000-5: ebXML Core Components Specification (CCS)
242:
An indication for whether acknowledgments are required
229:
A conversation identifier for linking related messages
193:
Whether acknowledgments are required for all messages
148:
ISO 15000-3: ebXML Registry Information Model (ebRIM)
65:
EDI "Future Vision" work sponsored by ANSI X12 EDI.
17:
Electronic Business using eXtensible Markup Language
556:OASIS ebXML Messaging Services Technical Committee
454:
453:Lu, Eric Jui-Lin; Wu, Chang-Chuan (March 2004).
284:Universal Description Discovery and Integration
136:International Organization for Standardization
576:
166:Collaborative Partner Profile Agreements are
8:
190:Whether duplicate messages should be ignored
583:
569:
561:
491:(1998). "Introducing XML/EDI Frameworks".
433:Learn how and when to remove this message
76:Conceptual overview of ebXML architecture
396:This article includes a list of general
309:Naujok, Klaus-Dieter (21 August 2003).
301:
162:Collaborative Partner Profile Agreement
514:Ontologies-Based Business Integration
7:
516:, Berlin: Springer, pp. 79–93,
780:World Wide Web Consortium standards
402:it lacks sufficient corresponding
118:Collaboration protocol agreements,
61:, XML markup technologies and the
14:
461:Software: Practice and Experience
232:A digital signature based on the
387:
198:Messaging Service Specification
1:
31:based standards sponsored by
522:10.1007/978-3-540-75230-1_4
127:Registries and repositories
86:Universal Business Language
811:
599:
505:10.1080/10196789800000011
220:Unique message identifier
456:"A ReScUE XML/EDI model"
795:Data modeling languages
785:Technical communication
546:XML.org ebXML community
417:more precise citations.
70:Object Management Group
223:Who the message is for
790:Computer file formats
205:SOAP with Attachments
121:Core data components,
775:XML markup languages
226:Who sent the message
19:, commonly known as
770:XML-based standards
364:ISO/TS 15000-4:2004
353:ISO/TS 15000-3:2004
207:specification. The
115:Business processes,
41:electronic business
493:Electronic Markets
757:
756:
531:978-3-540-75230-1
443:
442:
435:
802:
585:
578:
571:
562:
534:
508:
484:
458:
438:
431:
427:
424:
418:
413:this article by
404:inline citations
391:
390:
383:
377:
375:ISO 15000-5:2014
372:
366:
361:
355:
350:
344:
342:ISO 15000-2:2021
339:
333:
331:ISO 15000-2:2021
328:
322:
321:
319:
318:
306:
104:(UN/CEFACT) and
810:
809:
805:
804:
803:
801:
800:
799:
760:
759:
758:
753:
595:
589:
542:
537:
532:
511:
487:
473:10.1002/spe.566
452:
448:
439:
428:
422:
419:
409:Please help to
408:
392:
388:
381:
380:
373:
369:
362:
358:
351:
347:
340:
336:
329:
325:
316:
314:
308:
307:
303:
298:
293:
260:
200:
164:
98:
78:
12:
11:
5:
808:
806:
798:
797:
792:
787:
782:
777:
772:
762:
761:
755:
754:
752:
751:
746:
741:
736:
731:
726:
721:
716:
711:
706:
701:
696:
691:
686:
681:
676:
671:
666:
661:
656:
651:
646:
641:
636:
631:
626:
621:
616:
611:
606:
600:
597:
596:
590:
588:
587:
580:
573:
565:
559:
558:
553:
548:
541:
540:External links
538:
536:
535:
530:
509:
485:
467:(3): 315–338.
449:
447:
444:
441:
440:
395:
393:
386:
379:
378:
367:
356:
345:
334:
323:
300:
299:
297:
294:
292:
289:
288:
287:
281:
276:
271:
266:
259:
256:
244:
243:
240:
237:
230:
227:
224:
221:
199:
196:
195:
194:
191:
188:
185:
182:
179:
176:
163:
160:
156:
155:
152:
149:
146:
143:
129:
128:
125:
122:
119:
116:
97:
94:
77:
74:
21:e-business XML
13:
10:
9:
6:
4:
3:
2:
807:
796:
793:
791:
788:
786:
783:
781:
778:
776:
773:
771:
768:
767:
765:
750:
747:
745:
742:
740:
737:
735:
732:
730:
727:
725:
722:
720:
717:
715:
712:
710:
707:
705:
702:
700:
697:
695:
692:
690:
687:
685:
682:
680:
679:SOAP-over-UDP
677:
675:
672:
670:
667:
665:
662:
660:
657:
655:
652:
650:
647:
645:
642:
640:
637:
635:
632:
630:
627:
625:
622:
620:
617:
615:
612:
610:
607:
605:
602:
601:
598:
594:
591:Standards of
586:
581:
579:
574:
572:
567:
566:
563:
557:
554:
552:
549:
547:
544:
543:
539:
533:
527:
523:
519:
515:
510:
506:
502:
498:
494:
490:
489:Webber, David
486:
482:
478:
474:
470:
466:
462:
457:
451:
450:
445:
437:
434:
426:
416:
412:
406:
405:
399:
394:
385:
384:
376:
371:
368:
365:
360:
357:
354:
349:
346:
343:
338:
335:
332:
327:
324:
312:
305:
302:
295:
290:
285:
282:
280:
277:
275:
272:
270:
269:ISO/IEC 11179
267:
265:
262:
261:
257:
255:
253:
249:
241:
238:
236:specification
235:
234:XML Signature
231:
228:
225:
222:
219:
218:
217:
214:
210:
206:
197:
192:
189:
186:
183:
180:
177:
174:
173:
172:
169:
161:
159:
153:
150:
147:
144:
141:
140:
139:
137:
132:
126:
123:
120:
117:
114:
113:
112:
109:
107:
103:
95:
93:
91:
87:
82:
75:
73:
71:
66:
64:
60:
56:
52:
47:
44:
42:
38:
34:
30:
26:
22:
18:
729:WS-Discovery
664:OpenDocument
643:
513:
499:(1): 38–41.
496:
492:
464:
460:
429:
423:January 2010
420:
401:
370:
359:
348:
337:
326:
315:. Retrieved
304:
245:
201:
165:
157:
133:
130:
110:
99:
90:supply chain
83:
79:
67:
48:
45:
24:
20:
16:
15:
415:introducing
264:Web service
764:Categories
398:references
317:2021-03-14
291:References
279:RosettaNet
124:Messaging,
551:ebXML.org
296:Citations
37:UN/CEFACT
481:45465182
274:Metadata
258:See also
724:WS-BPEL
624:DocBook
446:Sources
411:improve
96:History
528:
479:
400:, but
286:(UDDI)
749:XACML
719:XLIFF
689:TOSCA
644:ebXML
593:OASIS
477:S2CID
33:OASIS
25:ebXML
23:, or
739:WSRP
734:WSRF
704:WSDM
699:UDDI
684:SPML
669:SAML
659:KMIP
649:EDXL
639:DPWS
634:DSML
629:DITA
604:AMQP
526:ISBN
252:SMTP
250:and
248:HTTP
213:SOAP
209:SOAP
35:and
744:WSS
714:XDI
709:XRI
694:UBL
674:SDD
654:EML
619:DSS
614:CAP
609:CAM
518:doi
501:doi
469:doi
168:XML
63:X12
59:UMM
55:UML
53:),
51:EDI
29:XML
766::
524:,
495:.
475:.
465:34
463:.
459:.
254:.
57:/
584:e
577:t
570:v
520::
507:.
503::
497:8
483:.
471::
436:)
430:(
425:)
421:(
407:.
320:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.