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