696:
choreography specifies a protocol for peer-to-peer interactions, defining, e.g., the legal sequences of messages exchanged with the purpose of guaranteeing interoperability. Such a protocol is not directly executable, as it allows many different realizations (processes that comply with it). A choreography can be realized by writing an orchestration (e.g., in the form of a BPEL process) for each peer involved in it. The orchestration and the choreography distinctions are based on analogies: orchestration refers to the central control (by the conductor) of the behavior of a distributed system (the orchestra consisting of many players), while choreography refers to a distributed system (the dancing team) which operates according to rules (the choreography) but without centralized control.
777:(BPMN), as a graphical front-end to capture BPEL process descriptions. As an illustration of the feasibility of this approach, the BPMN specification includes an informal and partial mapping from BPMN to BPEL 1.1. A more detailed mapping of BPMN to BPEL has been implemented in a number of tools, including an open-source tool known as BPMN2BPEL. However, the development of these tools has exposed fundamental differences between BPMN and BPEL, which make it very difficult, and in some cases impossible, to generate
987:
140:
38:
79:
699:
BPEL's focus on modern business processes, plus the histories of WSFL and XLANG, led BPEL to adopt web services as its external communication mechanism. Thus BPEL's messaging facilities depend on the use of the Web
Services Description Language (WSDL) 1.1 to describe outgoing and incoming messages.
864:
specification introduces the definition of human tasks and notifications, including their properties, behavior and a set of operations used to manipulate human tasks. A coordination protocol is introduced in order to control autonomy and life cycle of service-enabled human tasks in an interoperable
654:
Define a set of Web service orchestration concepts that are meant to be used by both the external (abstract) and internal (executable) views of a business process. Such a business process defines the behavior of a single autonomous entity, typically operating in interaction with other similar peer
466:
WS-BPEL aims to model the behavior of processes, via a language for the specification of both
Executable and Abstract Business Processes. By doing so, it extends the Web Services interaction model and enables it to support business transactions. It also defines an interoperable integration model
793:
BPEL's control structures such as 'if-then-elseif-else' and 'while' as well as its variable manipulation facilities depend on the use of 'programming in the small' languages to provide logic. All BPEL implementations must support XPath 1.0 as a default language. But the design of BPEL envisages
655:
entities. It is recognized that each usage pattern (i.e., abstract view and executable view) will require a few specialized extensions, but these extensions are to be kept to a minimum and tested against requirements such as import/export and conformance checking that link the two usage patterns.
761:
There is no standard graphical notation for WS-BPEL, as the OASIS technical committee decided this was out of scope. Some vendors have invented their own notations. These notations take advantage of the fact that most constructs in BPEL are block-structured (e.g., sequence, while, pick, scope,
611:
appeared as both a 1.0 and 1.1 version, the OASIS WS-BPEL technical committee voted on 14 September 2004 to name their spec "WS-BPEL 2.0". (This change in name aligned BPEL with other web service standard naming conventions which start with "WS-" (similar to WS-Security) and took account of the
695:
language. The primary difference between orchestration and choreography is executability and control. An orchestration specifies an executable process that involves message exchanges with other systems, such that the message exchange sequences are controlled by the orchestration designer. A
454:: is a partially specified process that is not intended to be executed. Contrary to Executable Processes, an Abstract Process may hide some of the required concrete operational details. Abstract Processes serve a descriptive role, with more than one possible
876:. It defines a new type of basic activity which uses human tasks as an implementation, and allows specifying tasks local to a process or use tasks defined outside of the process definition. This extension is based on the WS-HumanTask specification.
513:
interactions of a process. BPEL refers to this concept as an
Abstract Process. A BPEL Abstract Process represents a set of publicly observable behaviors in a standardized fashion. An Abstract Process includes information such as when to wait for
668:
Support the implicit creation and termination of process instances as the basic lifecycle mechanism. Advanced lifecycle operations such as "suspend" and "resume" may be added in future releases for enhanced lifecycle
664:
Support an identification mechanism for process instances that allows the definition of instance identifiers at the application message level. Instance identifiers should be defined by partners and may
648:(WSDL) 1.1, and that manifest themselves as Web services defined using WSDL 1.1. The interactions are "abstract" in the sense that the dependence is on portType definitions, not on port definitions.
794:
extensibility so that systems builders can use other languages as well. BPELJ is an effort related to JSR 207 that may enable Java to function as a 'programming in the small' language within BPEL.
785:: generating BPEL code from BPMN diagrams and maintaining the original BPMN model and the generated BPEL code synchronized, in the sense that any modification to one is propagated to the other.
580:
which would later serve as the basis for their
Orchestrations services inside their BizTalk Server. They specifically documented that this language "is proprietary and is not fully documented."
658:
Provide both hierarchical and graph-like control regimes, and allow their use to be blended as seamlessly as possible. This should reduce the fragmentation of the process modeling space.
672:
Define a long-running transaction model that is based on proven techniques like compensation actions and scoping to support failure recovery for parts of long-running business processes.
475:
1004:
103:
51:
651:
Define business processes using an XML-based language. Do not define a graphical representation of processes or provide any particular design methodology for processes.
1520:
1120:
960:
524:, in contrast, deals with short-lived programmatic behavior, often executed as a single transaction and involving access to local logic and resources such as
1103:
1306:
1404:
467:
that should facilitate the expansion of automated process integration both within and between businesses. Its development came out of the notion that
723:
constructs including if-then-elseif-else, while, sequence (to enable executing commands in order) and flow (to enable executing commands in parallel)
1480:
57:
1051:
204:
1212:
1274:
1023:
176:
1450:
1377:
1505:
1030:
183:
502:
distinguish between two aspects of writing the type of long-running asynchronous processes that one typically sees in business processes:
1596:
1525:
935:
774:
1490:
1455:
950:
806:
in distributed business applications, the absence of human interactions was a significant gap for many real-world business processes.
584:
1037:
190:
1425:
1070:
645:
241:
223:
121:
65:
161:
154:
1560:
1460:
731:
1019:
172:
1555:
1334:
1530:
1495:
1008:
767:
439:
One can describe Web-service interactions in two ways: as executable business processes and as abstract business processes.
703:
In addition to providing facilities to enable sending and receiving messages, the BPEL programming language also supports:
1397:
888:
New activity types: repeatUntil, validate, forEach (parallel and sequential), rethrow, extensionActivity, compensateScope
1591:
661:
Provide data manipulation functions for the simple manipulation of data needed to define process data and control flow.
94:
1601:
1515:
739:
612:
significant enhancements made between BPEL4WS 1.1 and WS-BPEL 2.0.) If not discussing a specific version, the moniker
595:
and
Intalio Inc., IBM and Microsoft decided to combine these languages into a new language, BPEL4WS. In April 2003,
1440:
1430:
713:
An extensible language plug-in model to allow writing expressions and queries in multiple languages: BPEL supports
542:
515:
1100:
997:
150:
1044:
940:
810:
688:
197:
1475:
1435:
1390:
692:
678:
Build on Web services standards (approved and proposed) as much as possible in a composable and modular manner.
561:
469:
644:
Define business processes that interact with external entities through web service operations defined using
627:
and WS-HumanTask specifications, which describe how human interaction in BPEL processes can be implemented.
510:
762:
etcetera.) This feature enables a direct visual representation of BPEL process descriptions in the form of
607:
submitted BPEL4WS 1.1 to OASIS for standardization via the Web
Services BPEL Technical Committee. Although
782:
749:
720:
459:
1247:
849:
1216:
1414:
1281:
945:
420:
339:
1199:
89:
873:
837:
727:
1121:"OASIS Members Form Web Services Business Process Execution Language (WSBPEL) Technical Committee"
773:
Others have proposed to use a substantially different business process modeling language, namely
431:. Processes in BPEL export and import information by using web service interfaces exclusively.
376:
1373:
1300:
906:
XML schema variables in Web service activities (for WS-I doc/lit style service interactions)
424:
872:
specification introduces a WS-BPEL extension to address human interactions in WS-BPEL as a
1338:
1260:
1107:
894:
Termination
Handler added to scope activities to provide explicit behavior for termination
1178:
317:
909:
Locally declared messageExchange (internal correlation of receive and reply activities)
778:
735:
604:
1585:
1500:
743:
620:
525:
900:
XSLT for variable transformations (New XPath extension function bpws:doXslTransform)
1550:
1485:
1331:
576:, respectively. Microsoft even went ahead and created a scripting variant called
1565:
1510:
1156:
986:
930:
925:
803:
781:
BPEL code from BPMN models. Even more difficult is the problem of BPMN-to-BPEL
624:
596:
428:
139:
813:
of Web services alone to orchestration of role-based human activities as well.
891:
Renamed activities: switch/case renamed to if/else, terminate renamed to exit
557:
1349:
1240:"Representing business processes: conceptual model and design methodology"
955:
903:
XPath access to variable data (XPath variable syntax $ variable/location)
529:
518:, when to send messages, when to compensate for failed transactions, etc.
455:
1445:
1319:
608:
447:: models an actual behavior of a participant in a business interaction.
1134:
1382:
675:
Use Web
Services as the model for process decomposition and assembly.
600:
17:
857:
by extending BPEL with additional independent syntax and semantic.
1570:
1540:
1465:
1239:
714:
592:
546:
349:
OASIS Web
Services Business Process Execution Language (WSBPEL) TC
1101:
Business
Process Execution Language for Web Services, Version 1.1
1470:
970:
965:
1386:
1535:
980:
553:
483:
357:
133:
72:
31:
831:
takes care to delegate ownership of a task to a person only
640:
There were ten original design goals associated with BPEL:
423:
standard executable language for specifying actions within
912:
Clarification of Abstract Processes (syntax and semantics)
828:
provides means of assigning users to generic human roles
1370:
SOA for the Business Developer: Concepts, BPEL, and SCA
788:
884:
Version 2.0 introduced some changes and new features:
915:
Enable expression language overrides at each activity
821:
Within the context of a business process BPEL4People
1011:. Unsourced material may be challenged and removed.
371:
363:
353:
345:
335:
313:
295:
280:
272:
264:
1123:. OASIS WSBPEL Technical Committee. 29 April 2003.
748:Serialized scopes to control concurrent access to
809:To fill this gap, BPEL4People extended BPEL from
789:Adding 'programming in the small' support to BPEL
1135:"Cover Pages: Web Services Flow Language (WSFL)"
405:Web Services Business Process Execution Language
260:Web Services Business Process Execution Language
458:, including observable behavior and/or process
707:A property-based message correlation mechanism
1398:
486:and aims to enable programming in the large.
8:
560:had each defined their own fairly similar, "
254:
66:Learn how and when to remove these messages
1405:
1391:
1383:
623:, BEA, IBM, Oracle, and SAP published the
253:
1071:Learn how and when to remove this message
825:supports role-based interaction of people
242:Learn how and when to remove this message
224:Learn how and when to remove this message
122:Learn how and when to remove this message
1084:
479:required different types of languages.
1305:: CS1 maint: archived copy as title (
1298:
1256:
1245:
160:Please improve this article by adding
99:reihbase on refs, other issues tagged.
1200:Web Services BPEL Technical Committee
1020:"Business Process Execution Language"
173:"Business Process Execution Language"
7:
1009:adding citations to reliable sources
1238:Chinosi, Michele (1 January 2009).
936:Business Process Model and Notation
775:Business Process Model and Notation
509:generally refers to the high-level
417:Business Process Execution Language
1137:. xml.coverpages.org/. 6 June 2001
951:Web Services Conversation Language
591:and the open BPMS movement led by
583:With the advent and popularity of
541:The origins of WS-BPEL go back to
25:
646:Web Services Description Language
47:This article has multiple issues.
1215:. choreology.com. Archived from
985:
619:In June 2007, Active Endpoints,
138:
77:
36:
996:needs additional citations for
966:XML Process Definition Language
55:or discuss these issues on the
766:, in a style reminiscent of a
490:Programming in the large/small
1:
971:Yet Another Workflow Language
587:, and the growing success of
482:As such, it is serialized in
162:secondary or tertiary sources
757:Relationship of BPEL to BPMN
742:, compensation-handlers and
710:XML and WSDL typed variables
27:Computer executable language
1159:. xml.coverpages.org/. 2001
802:Despite wide acceptance of
445:executable business process
301:; 21 years ago
97:. The specific problem is:
1618:
1597:Web service specifications
1091:OASIS Standard WS-BPEL 2.0
570:Web Services Flow Language
543:Web Services Flow Language
93:to meet Knowledge (XXG)'s
1421:
941:Business Process Modeling
768:Nassi–Shneiderman diagram
452:abstract business process
259:
562:programming in the large
522:Programming in the small
507:Programming in the large
500:programming in the small
496:programming in the large
476:programming in the small
470:programming in the large
1106:3 December 2020 at the
897:Variable initialization
367:Web service integration
1255:Cite journal requires
783:round-trip engineering
721:Structured-programming
323:; 17 years ago
149:relies excessively on
834:supports scenario as
411:), commonly known as
1287:on 15 September 2012
1005:improve this article
946:List of BPEL engines
730:system to allow the
691:language, and not a
104:improve this article
1592:XML-based standards
1337:16 May 2005 at the
1219:on 27 February 2012
874:first-class citizen
256:
1602:Workflow languages
1179:"XLANG/s Language"
616:is commonly used.
599:, IBM, Microsoft,
425:business processes
321:11 April 2007
1579:
1578:
1378:978-1-58347-065-7
1364:Books on BPEL 2.0
1081:
1080:
1073:
1055:
850:chained execution
683:The BPEL language
401:
400:
252:
251:
244:
234:
233:
226:
208:
132:
131:
124:
95:quality standards
86:This article may
70:
16:(Redirected from
1609:
1407:
1400:
1393:
1384:
1352:
1347:
1341:
1329:
1323:
1317:
1311:
1310:
1304:
1296:
1294:
1292:
1286:
1280:. Archived from
1279:
1271:
1265:
1264:
1258:
1253:
1251:
1243:
1235:
1229:
1228:
1226:
1224:
1213:"choreology.com"
1209:
1203:
1197:
1191:
1190:
1188:
1186:
1175:
1169:
1168:
1166:
1164:
1153:
1147:
1146:
1144:
1142:
1131:
1125:
1124:
1117:
1111:
1098:
1092:
1089:
1076:
1069:
1065:
1062:
1056:
1054:
1013:
989:
981:
511:state transition
494:The concepts of
397:
394:
392:
390:
388:
386:
384:
382:
380:
378:
331:
329:
324:
309:
307:
302:
291:
289:
257:
247:
240:
229:
222:
218:
215:
209:
207:
166:
142:
134:
127:
120:
116:
113:
107:
81:
80:
73:
62:
40:
39:
32:
21:
1617:
1616:
1612:
1611:
1610:
1608:
1607:
1606:
1582:
1581:
1580:
1575:
1417:
1411:
1361:
1359:Further reading
1356:
1355:
1348:
1344:
1339:Wayback Machine
1330:
1326:
1318:
1314:
1297:
1290:
1288:
1284:
1277:
1275:"Archived copy"
1273:
1272:
1268:
1254:
1244:
1237:
1236:
1232:
1222:
1220:
1211:
1210:
1206:
1198:
1194:
1184:
1182:
1177:
1176:
1172:
1162:
1160:
1155:
1154:
1150:
1140:
1138:
1133:
1132:
1128:
1119:
1118:
1114:
1108:Wayback Machine
1099:
1095:
1090:
1086:
1077:
1066:
1060:
1057:
1014:
1012:
1002:
990:
979:
922:
882:
819:
800:
791:
759:
736:local variables
685:
638:
633:
539:
492:
437:
375:
327:
325:
322:
320:
305:
303:
300:
299:April 2003
296:First published
287:
285:
268:WS-BPEL or BPEL
248:
237:
236:
235:
230:
219:
213:
210:
167:
165:
159:
155:primary sources
143:
128:
117:
111:
108:
101:
82:
78:
41:
37:
28:
23:
22:
15:
12:
11:
5:
1615:
1613:
1605:
1604:
1599:
1594:
1584:
1583:
1577:
1576:
1574:
1573:
1568:
1563:
1558:
1553:
1548:
1543:
1538:
1533:
1528:
1523:
1518:
1513:
1508:
1503:
1498:
1493:
1488:
1483:
1478:
1473:
1468:
1463:
1458:
1453:
1448:
1443:
1438:
1433:
1428:
1422:
1419:
1418:
1412:
1410:
1409:
1402:
1395:
1387:
1381:
1380:
1366:
1365:
1360:
1357:
1354:
1353:
1342:
1324:
1312:
1266:
1257:|journal=
1230:
1204:
1192:
1170:
1148:
1126:
1112:
1093:
1083:
1082:
1079:
1078:
993:
991:
984:
978:
975:
974:
973:
968:
963:
958:
953:
948:
943:
938:
933:
928:
921:
918:
917:
916:
913:
910:
907:
904:
901:
898:
895:
892:
889:
881:
878:
855:
854:
853:
852:
847:
844:
841:
832:
829:
826:
818:
815:
799:
796:
790:
787:
779:human-readable
758:
755:
754:
753:
746:
744:event-handlers
734:of logic with
724:
718:
717:1.0 by default
711:
708:
684:
681:
680:
679:
676:
673:
670:
666:
662:
659:
656:
652:
649:
637:
634:
632:
629:
605:Siebel Systems
538:
535:
534:
533:
519:
491:
488:
464:
463:
448:
436:
433:
399:
398:
373:
369:
368:
365:
361:
360:
355:
354:Base standards
351:
350:
347:
343:
342:
337:
333:
332:
315:
314:Latest version
311:
310:
297:
293:
292:
282:
278:
277:
274:
270:
269:
266:
262:
261:
250:
249:
232:
231:
146:
144:
137:
130:
129:
85:
83:
76:
71:
45:
44:
42:
35:
26:
24:
14:
13:
10:
9:
6:
4:
3:
2:
1614:
1603:
1600:
1598:
1595:
1593:
1590:
1589:
1587:
1572:
1569:
1567:
1564:
1562:
1559:
1557:
1554:
1552:
1549:
1547:
1544:
1542:
1539:
1537:
1534:
1532:
1529:
1527:
1524:
1522:
1519:
1517:
1514:
1512:
1509:
1507:
1504:
1502:
1501:SOAP-over-UDP
1499:
1497:
1494:
1492:
1489:
1487:
1484:
1482:
1479:
1477:
1474:
1472:
1469:
1467:
1464:
1462:
1459:
1457:
1454:
1452:
1449:
1447:
1444:
1442:
1439:
1437:
1434:
1432:
1429:
1427:
1424:
1423:
1420:
1416:
1413:Standards of
1408:
1403:
1401:
1396:
1394:
1389:
1388:
1385:
1379:
1375:
1371:
1368:
1367:
1363:
1362:
1358:
1351:
1346:
1343:
1340:
1336:
1333:
1328:
1325:
1321:
1316:
1313:
1308:
1302:
1283:
1276:
1270:
1267:
1262:
1249:
1241:
1234:
1231:
1218:
1214:
1208:
1205:
1201:
1196:
1193:
1180:
1174:
1171:
1158:
1152:
1149:
1136:
1130:
1127:
1122:
1116:
1113:
1109:
1105:
1102:
1097:
1094:
1088:
1085:
1075:
1072:
1064:
1053:
1050:
1046:
1043:
1039:
1036:
1032:
1029:
1025:
1022: –
1021:
1017:
1016:Find sources:
1010:
1006:
1000:
999:
994:This article
992:
988:
983:
982:
976:
972:
969:
967:
964:
962:
959:
957:
954:
952:
949:
947:
944:
942:
939:
937:
934:
932:
929:
927:
924:
923:
919:
914:
911:
908:
905:
902:
899:
896:
893:
890:
887:
886:
885:
879:
877:
875:
871:
866:
863:
858:
851:
848:
845:
842:
839:
836:
835:
833:
830:
827:
824:
823:
822:
816:
814:
812:
811:orchestration
807:
805:
797:
795:
786:
784:
780:
776:
771:
769:
765:
756:
751:
747:
745:
741:
737:
733:
732:encapsulation
729:
725:
722:
719:
716:
712:
709:
706:
705:
704:
701:
697:
694:
690:
689:orchestration
682:
677:
674:
671:
667:
663:
660:
657:
653:
650:
647:
643:
642:
641:
635:
630:
628:
626:
622:
621:Adobe Systems
617:
615:
610:
606:
602:
598:
594:
590:
586:
581:
579:
575:
571:
567:
564:" languages:
563:
559:
555:
550:
548:
544:
536:
531:
527:
523:
520:
517:
512:
508:
505:
504:
503:
501:
497:
489:
487:
485:
480:
478:
477:
472:
471:
461:
457:
453:
449:
446:
442:
441:
440:
434:
432:
430:
426:
422:
418:
414:
410:
406:
396:
374:
370:
366:
362:
359:
356:
352:
348:
344:
341:
338:
334:
319:
316:
312:
298:
294:
283:
279:
275:
271:
267:
263:
258:
246:
243:
228:
225:
217:
206:
203:
199:
196:
192:
189:
185:
182:
178:
175: –
174:
170:
169:Find sources:
163:
157:
156:
152:
147:This article
145:
141:
136:
135:
126:
123:
115:
105:
100:
96:
92:
91:
84:
75:
74:
69:
67:
60:
59:
54:
53:
48:
43:
34:
33:
30:
19:
1551:WS-Discovery
1545:
1486:OpenDocument
1369:
1345:
1327:
1315:
1289:. Retrieved
1282:the original
1269:
1248:cite journal
1233:
1221:. Retrieved
1217:the original
1207:
1195:
1183:. Retrieved
1173:
1161:. Retrieved
1151:
1139:. Retrieved
1129:
1115:
1110:(5 May 2003)
1096:
1087:
1067:
1061:October 2008
1058:
1048:
1041:
1034:
1027:
1015:
1003:Please help
998:verification
995:
883:
869:
867:
862:WS-HumanTask
861:
859:
856:
820:
808:
804:Web services
801:
792:
772:
764:structograms
763:
760:
702:
698:
693:choreography
686:
639:
636:Design goals
618:
613:
588:
582:
577:
573:
569:
565:
551:
540:
532:, et cetera.
521:
506:
499:
495:
493:
481:
474:
468:
465:
451:
444:
438:
429:web services
416:
412:
408:
404:
402:
336:Organization
281:Year started
265:Abbreviation
238:
220:
214:October 2012
211:
201:
194:
187:
180:
168:
148:
118:
109:
102:Please help
98:
87:
63:
56:
50:
49:Please help
46:
29:
1181:. Microsoft
926:BPEL4People
880:WS-BPEL 2.0
870:BPEL4People
798:BPEL4People
687:BPEL is an
669:management.
625:BPEL4People
597:BEA Systems
545:(WSFL) and
379:.oasis-open
106:if you can.
1586:Categories
1031:newspapers
977:References
931:BPELscript
846:escalation
843:nomination
817:Objectives
391:/wsbpel-v2
328:2007-04-11
184:newspapers
151:references
52:improve it
1320:BPMN2BPEL
1185:9 October
1163:9 October
1141:9 October
838:four-eyes
750:variables
558:Microsoft
552:In 2001,
530:databases
419:), is an
346:Committee
276:Published
112:July 2016
58:talk page
1335:Archived
1301:cite web
1291:17 April
1223:17 April
1104:Archived
956:Workflow
920:See also
865:manner.
840:scenario
740:handlers
738:, fault-
589:BPMI.org
516:messages
460:template
456:use case
435:Overview
88:require
1546:WS-BPEL
1446:DocBook
1350:JSR 207
1157:"XLANG"
1045:scholar
728:scoping
665:change.
609:BPEL4WS
578:XLANG/s
537:History
409:WS-BPEL
383:/wsbpel
372:Website
326: (
306:2003-04
304: (
286: (
255:WS-BPEL
198:scholar
90:cleanup
1376:
1047:
1040:
1033:
1026:
1018:
961:WS-CDL
631:Topics
603:, and
572:) and
364:Domain
273:Status
200:
193:
186:
179:
171:
1571:XACML
1541:XLIFF
1511:TOSCA
1466:ebXML
1415:OASIS
1332:BPELJ
1285:(PDF)
1278:(PDF)
1052:JSTOR
1038:books
715:XPath
593:JBoss
574:Xlang
547:Xlang
526:files
427:with
421:OASIS
395:.html
393:.0-OS
340:OASIS
205:JSTOR
191:books
1561:WSRP
1556:WSRF
1526:WSDM
1521:UDDI
1506:SPML
1491:SAML
1481:KMIP
1471:EDXL
1461:DPWS
1456:DSML
1451:DITA
1426:AMQP
1374:ISBN
1307:link
1293:2013
1261:help
1225:2013
1187:2014
1165:2014
1143:2014
1024:news
868:The
860:The
614:BPEL
585:BPML
566:WSFL
556:and
498:and
473:and
413:BPEL
403:The
381:.org
377:docs
288:2001
284:2001
177:news
18:BPEL
1566:WSS
1536:XDI
1531:XRI
1516:UBL
1496:SDD
1476:EML
1441:DSS
1436:CAP
1431:CAM
1007:by
601:SAP
554:IBM
484:XML
450:An
443:An
389:/OS
358:XML
318:2.0
153:to
1588::
1372:.
1303:}}
1299:{{
1252::
1250:}}
1246:{{
770:.
726:A
549:.
528:,
387:.0
385:/2
164:.
61:.
1406:e
1399:t
1392:v
1322:.
1309:)
1295:.
1263:)
1259:(
1242:.
1227:.
1202:.
1189:.
1167:.
1145:.
1074:)
1068:(
1063:)
1059:(
1049:·
1042:·
1035:·
1028:·
1001:.
752:.
568:(
462:.
415:(
407:(
330:)
308:)
290:)
245:)
239:(
227:)
221:(
216:)
212:(
202:·
195:·
188:·
181:·
158:.
125:)
119:(
114:)
110:(
68:)
64:(
20:)
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
