Business Process Project Team

1 2 3 4 5 6 ebxml Business Process Specification Schema Version 1.01 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 Business Process Project Team 1 Status of this Document 11 May 2001 This Technical Specification document has been approved by the ebxml Plenary. This material fulfills requirements of the ebxml Requirements document. The formatting for this document is based on the Internet Society s Standard RFC format. This version: www.ebxml.org/specs/ebbpss.pdf Latest version: www.ebxml.org/specs/ebbpss.pdf ebxml Business Process Specification Schema Page i of 136

29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 2 ebxml BP/CoreComponents metamodel participants We would like to recognize the following for their significant participation to the development of this document. Team Lead: Paul Levine, Telcordia Editors: Jim Clark, E2Open - previously Edifecs: (Transaction Semantics) Cory Casanave, Data Access Technologies: (UML model) Kurt Kanaskie, Lucent Technologies: (DTD and Examples) Betty Harvey, Electronic Commerce Connection: (DTD documentation) Jamie Clark, McLure-Moynihan, Inc.: (Legal aspects) Neal Smith, Chevron: (Issues Lists, and W3C schema) John Yunker, Edifecs: (Signal structures) Karsten Riemer, Sun Microsystems: (Overall Document) Participants: Antoine Lonjon, Mega J.J. Dubray, Excelon Bob Haugen, Logistical Software Bill McCarthy, Michigan State University Paul Levine, Telcordia Brian Hayes, CommerceOne Nita Sharma, Netfish David Welsh, Nordstrom Christopher Ferris, Sun Microsystems Antonio Carrasco, Data Access Technologies ebxml Business Process Specification Schema Page ii of 136

59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 3 Table of Contents 1 Status of this Document...i 2 ebxml BP/CoreComponents metamodel participants... ii 3 Table of Contents... iii 4 Introduction...v 4.1 Summary of Contents of Document... 1 4.2 Audience... 1 4.3 Related Documents... 1 4.4 Prerequisites... 2 5 Design Objectives... 2 5.1 Goals/Objectives/Requirements/Problem Description... 2 5.2 Caveats and Assumptions... 3 5.2.1 Relationship between ebxml Business Process Specification Schema and UMM3 6 System Overview... 5 6.1 Key Concepts of the ebxml Business Process Specification Schema... 10 6.2 How to use the ebxml Business Process Specification Schema... 14 6.3 How ebxml Business Process Specification Schema is used with other ebxml specifications... 14 6.4 How to design collaborations and transactions, re-using at design time... 16 6.4.1 Specify a Business Transaction and its Business Document Flow... 16 6.4.2 Specify a Binary Collaboration... 22 6.4.3 Specify a MultiParty Collaboration... 25 6.4.4 Specify a Choreography... 27 6.4.5 The whole model... 31 6.5 Core Business Transaction Semantics... 34 6.5.1 Interaction Predictability... 34 6.5.2 Creating legally binding contracts... 37 6.5.3 Non-Repudiation... 38 6.5.4 Authorization security... 39 6.5.5 Document security... 40 6.5.6 Reliability... 41 6.5.7 Parameters required for CPP/CPA... 41 6.6 Run time Business Transaction semantics... 41 6.6.1 Timeouts... 42 6.6.2 Exceptions... 44 6.7 Runtime Collaboration Semantics... 47 6.8 Where the ebxml Business Process Specification Schema May Be Implemented... 47 7 UML Element Specification... 47 7.1 Business Collaborations... 47 7.1.1 MultiPartyCollaboration... 47 7.1.2 BusinessPartnerRole... 48 7.1.3 Performs... 48 7.1.4 AuthorizedRole... 49 7.1.5 BinaryCollaboration... 50 ebxml Business Process Specification Schema Page iii of 136

103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 7.1.6 BusinessActivity... 51 7.1.7 BusinessTransactionActivity... 51 7.1.8 CollaborationActivity... 52 7.2 Business Transactions... 52 7.2.1 BusinessTransaction... 53 7.2.2 Business Action... 54 7.2.3 RequestingBusinessActivity... 55 7.2.4 RespondingBusinessActivity... 55 7.3 Document flow... 56 7.3.1 Document Security... 56 7.3.2 Document Envelope... 56 7.3.3 BusinessDocument... 58 7.3.4 Attachment... 58 7.4 Choreography within Collaborations... 59 7.4.1 BusinessState... 59 7.4.2 Transition... 59 7.4.3 Start... 60 7.4.4 CompletionState... 60 7.4.5 Success... 61 7.4.6 Failure... 61 7.4.7 Fork... 62 7.4.8 Join... 62 7.5 Definition and Scope... 63 7.6 Collaboration and transaction well-formedness rules... 63 8 ebxml Business Process Specification Schema (DTD)... 65 8.1 Documentation for the DTD... 65 8.2 XML to UML cross-reference... 94 8.3 Scoped Name Reference... 96 8.4 Substitution Sets... 97 8.5 Sample XML document against above DTD... 97 9 Business signal structures... 97 9.1.1 ReceiptAcknowledgment DTD... 98 9.1.2 AcceptanceAcknowledgement DTD... 100 9.1.3 Exception Signal DTD... 101 10 Production Rules... 103 Appendix A: Sample XML Business Process Specification... 105 Appendix B: Business Process Specification Schema DTD... 110 Appendix C: Business Process Specification Schema XML Schema... 117 11 References... 129 12 Disclaimer... 129 13 Contact Information... 130 ebxml Business Process Specification Schema Page iv of 136

145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 4 Introduction Executive Summary The ebxml Specification Schema provides a standard framework by which business systems may be configured to support execution of business collaborations consisting of business transactions. It is based upon prior UN/CEFACT work, specifically the metamodel behind the UN/CEFACT Modeling Methodology (UMM) defined in the N090R9.1 specification. The Specification Schema supports the specification of Business Transactions and the choreography of Business Transactions into Business Collaborations. Each Business Transaction can be implemented using one of many available standard patterns. These patterns determine the actual exchange of Business Documents and business signals between the partners to achieve the required electronic commerce transaction. The current version of the specification schema addresses collaborations between two parties (Binary Collaborations). It is anticipated that a subsequent version will address additional features such as the semantics of economic exchanges and contracts, more complex multi-party choreography, and context based content. ebxml Business Process Specification Schema Page v of 136

163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 4.1 Summary of Contents of Document This document describes the ebxml Specification Schema This document describes the Specification Schema, both in its UML form and in its DTD form. The document first introduces general concepts and semantics, then applies these semantics in a detail discussion of each part of the model. The document then specifies all elements in the UML form, and then in the XML form. The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this document, are to be interpreted as described in RFC 2119 [Bra97]. 4.2 Audience The primary audience is business process analysts. We define a business process analyst as someone who interviews business people and as a result documents business processes in unambiguous syntax. An additional audience is designers of business process definition tools who need to specify the conversion of user input in the tool into the XML representation of the Specification Schema. The audience is not business application developers. 4.3 Related Documents As mentioned above, other documents provide detailed definitions of some of the components of the ebxml Specification Schema and of their inter-relationship. They include ebxml Specifications on the following topics: ebxml Technical Architecture Specification, version 1.04 ebxml Core Components Dictionary, version 1.04 ebxml Naming Convention for Core Components, version 1.04 ebxml Collaboration-Protocol Profile and Agreement Specification V1.0 ebxml Business Process and Business Information Analysis Overview, version 0.7 ebxml Business Process Analysis Worksheets & Guidelines, version 0.10 ebxml E-Commerce Patterns, version 0.99 ebxml Catalog of Common Business Processes, version 0.99 ebxml Message Service Specification V0.99 Copyright ebxml 2001. All Rights Reserved.

198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 UN/CEFACT Modeling Methodology (UMM) as defined in the N090R9.1 specification 4.4 Prerequisites It is assumed that the audience will be familiar with or have knowledge of the following technologies and techniques: Business process modeling techniques and principles The UML syntax and semantics The Extensible Markup Language (XML) 5 Design Objectives 5.1 Goals/Objectives/Requirements/Problem Description Business process models describe interoperable business processes that allow business partners to collaborate. Business process models for e-business must be turned into software components that collaborate on behalf of the business partners. The goal of the ebxml Specification Schema is to provide the bridge between e- business process modeling and specification of e-business software components. The ebxml Specification Schema provides for the nominal set of specification elements necessary to specify a collaboration between business partners, and to provide configuration parameters for the partners runtime systems in order to execute that collaboration between a set of e-business software components. A specification created against the ebxml Business Process Specification Schema is referred to as an ebxml Business Process Specification. The ebxml Business Process Specification Schema is available in two standalone representations, a UML version, and an XML version. The UML version of the ebxml Business Process Specification Schema is merely a UML Class Diagram. It is not intended for the direct creation of ebxml Business Process Specifications. Rather, it is a self-contained statement of all the specification elements and relationships required to be able to create an ebxml compliant Business Process Specification. Any methodologies and/or metamodels used for the creation of ebxml compliant Business Process Specifications must at minimum support these elements and relationships. The XML version of the ebxml Business Process Specification Schema provides the specification for XML based instances of ebxml Business Process Specifications, and as a target for production rules from other representations. Both a DTD and a W3C Schema is provided. The UML and XML based versions of the ebxml Business Process Specification Schema are unambiguously mapped to each other. ebxml Business Process Specification Schema Page 2 of 136

236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 5.2 Caveats and Assumptions This specification is designed to specify the run time aspects of a business collaboration. It is not intended to incorporate a methodology, and does not directly prescribe the use of a methodology. However, if a methodology is to be used, it is recommended that it be UN/CEFACT Modeling Methodology (UMM). The ebxml Business Process Specification Schema does not by itself define Business Documents Structures. It is intended to work in conjunction with already existing Business Document definitions, and/or the document metamodel defined by the ebxml Core Components specifications. 5.2.1 Relationship between ebxml Business Process Specification Schema and UMM The UN/CEFACT Modeling Methodology (UMM) is a methodology for business process and information modeling. This section describes the relationship between UMM and the ebxml Business Process Specification Schema. The UMM Meta Model is a description of business semantics that allows Trading Partners to capture the details for a specific business scenario (a Business Process) using a consistent modeling methodology. A Business Process describes in detail how Trading Partners take on shared roles, relationships and responsibilities to facilitate interaction with other Trading Partners. The interaction between roles takes place as a choreographed set of Business Transactions. Each Business Transaction is expressed as an exchange of electronic Business Documents. The sequence of the exchange is determined by the Business Process, and by messaging and security considerations. Business Documents are composed from re-useable Business Information Objects. At a lower level, Business Processes can be composed of re-useable Common Business Processes, and Business Information Objects can be composed of re-useable Core Components. Common Business Processes and Business Information Objects reside in a UMM Business Library. The UMM Meta Model supports a set of Business Process viewpoints that provide a set of semantics (vocabulary) for each viewpoint and forms the basis of specification of the semantics and artifacts that are required to facilitate business process and information integration and interoperability. Using the UMM methodology and the UMM metamodel, the user may thus create a complete Business Process and Information Model. This model contains more information than what is required for configuring ebxml compliant software. Also the model is syntax independent and not directly interpretable by ebxml compliant software. The ebxml Business Process Specification Schema provides an additional view of the UMM metamodel. This subset is provided to support the direct specification of the nominal set of elements necessary to configure a runtime system in order to execute a set of ebxml business transactions. By drawing ebxml Business Process Specification Schema Page 3 of 136

280 281 282 283 284 285 286 287 288 289 out modeling elements from several of the other views, the ebxml Business Process Specification Schema forms a semantic subset of the UMM Meta Model. Using the ebxml Business Process Specification Schema the user may thus create a Business Process Specification that contains only the information required to configure ebxml compliant software. The ebxml Business Process Specification Schema is available in two standalone representations, a UML version, and an XML version. The XML version is intended to be interpretable by ebxml compliant software. The relationship between the UMM Meta Model and the ebxml Business Process Specification Schema is shown in Figure 1. 290 291 Figure 1. UMM Metamodel and ebxml Business Process Specification Schema 292 293 294 295 296 297 298 Using the UMM methodology, and drawing on content from the UMM Business Library a user may create complete Business Process and Information Model conforming to the UMM metamodel. Since the ebxml Business Process Specification Schema is a semantic subset of the UMM metamodel, the user may then in an automated fashion extract from the Business Process and Information Model the required set of elements and ebxml Business Process Specification Schema Page 4 of 136

299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 relationships, and transform them into an ebxml Business Process Specification conforming to the ebxml Business Process Specification Schema. Likewise, since the ebxml CC document metamodel is aligned with the UMM Metamodel, the user may then in an automated fashion extract from the Business Process and Information Model the required set of elements and relationships, and transform them into an ebxml document model conforming to ebxml Core Component specifications. The UMM methodology is not part of the formal set of ebxml specifications. Likewise, the UMM metamodel in its entirety is not part of the formal set of ebxml specifications. Only the semantic subset represented by the ebxml Business Process Specification Schema and CC are part of the formal set of ebxml specifications. The remainder of this document focuses on the ebxml Business Process Specification Schema and Business Process Specifications created against it. It is understood that proper Business Process and Information Modeling may have taken place prior to beginning the activity of creating a Business Process Specification. 6 System Overview The ebxml Business Process Specification Schema provides a standard framework for business process specification. As such, it works with the ebxml Collaboration Protocol Profile (CPP) and Collaboration Protocol Agreement (CPA) specifications to bridge the gap between Business Process Modeling and the configuration of ebxml compliant e-commerce software, e.g. an ebxml Business Service Interface, as depicted in Figure 2. ebxml Business Process Specification Schema Page 5 of 136

323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 Figure 2: Business Process Specification and Business Service Interface Configuration Using Business Process Modeling, a user may create a complete Business Process and Information Model. Based on this Business Process and Information Model and using the ebxml Business Process Specification Schema the user will then extract and format the nominal set of elements necessary to configure an ebxml runtime system in order to execute a set of ebxml business transactions. The result is an ebxml Business Process Specification. Alternatively the ebxml Business Process Specification may be created directly, without prior explicit business process modeling. An ebxml Business Process Specification contains the specification of Business Transactions and the choreography of Business Transactions into Business Collaborations. This ebxml Business Process Specification is then the input to the formation of ebxml trading partner Collaboration Protocol Profiles and Collaboration Protocol Agreements. These ebxml trading partner Collaboration Protocol Profiles and Collaboration Protocol Agreements in turn serve as configuration files for ebxml Business Service Interface software. ebxml Business Process Specification Schema Page 6 of 136

343 344 345 346 347 348 349 350 351 352 353 354 The architecture of the ebxml Business Process Specification Schema consists of the following functional components: UML version of the Business Process Specification Schema XML version of the Business Process Specification Schema Production Rules defining the mapping from the UML version of the Business Process Specification Schema to the XML version Business Signal Definitions Together these components allow you to fully specify all the run time aspects of a business process model. These components are shown (inside the dotted box)in figure 3 below. 355 356 357 358 359 360 361 Figure 3: Relationship of ebxml Business Process Specification Schema to UMM, CPP/CPA and Core Components The following provides a description of each of the components in the ebxml Business Process Specification Schema and their relationship to UMM, and ebxml CC and CPP/CPA: ebxml Business Process Specification Schema Page 7 of 136

362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 UML version of Business Process Specification Schema The UML version of the ebxml Business Process Specification Schema is a semantic subset of the metamodel behind UMM as specified in UN/CEFACT TMWG s N090R9.1 N090R9.1 is as of this writing not yet approved by UN/CEFACT. It is the intent to keep the ebxml Business Process Specification Schema and the UN/CEFACT TMWG s N090 semantically aligned. The UML version of the ebxml Business Process Specification Schema is merely a UML Class Diagram. It is not intended for the direct creation of ebxml Business Process Specifications. Rather, it is a self-contained statement of all the specification elements and relationships required to be able to create an ebxml compliant Business Process Specification. XML version of Business Process Specification Schema The XML version of the ebxml Business Process Specification Schema provides the specification for XML based instances of ebxml Business Process Specifications, and as a target for production rules from other representations. Thus, a user may either create a Business Process Specification directly as an XML document, or may chose to use some other means of specification first and then apply production rules to arrive at the XML document version. Any methodologies and/or metamodels used for the creation of ebxml compliant Business Process Specifications must at minimum support the production of the elements and relationships contained in the XML version of the ebxml Business Process Specification Schema. Both a DTD and a W3C Schema is provided. Each is an isomorphic definition of the UML version of the ebxml Business Process Specification Schema. UMM Business Process Interaction Patterns ebxml Business Service Interfaces are configured to execute the business processes specified in a Business Process Specification. They do so by exchanging ebxml messages and business signals. Each Business Transaction can be implemented using one of many available standard patterns. These patterns determine the actual exchange of messages and business signals between the partners to achieve the required electronic commerce transaction. The Business Transaction Interaction Patterns set forth in Chapter 8 of the UMM N090R9.1 document illustrate recommended permutations of message sequences as determined by the type of business transaction defined and the timing policies specified in the transactions. While the UMM patterns themselves are not part of the ebxml specifications, all the security and timing parameters required to express the pattern properties are provided as attributes of elements in the ebxml Business Process Specification Schema. ebxml Business Process Specification Schema Page 8 of 136

403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 Business Signal Definitions Business signals are application level documents that signal the current state of the business transaction. These business signals have specific business purpose and are separate from lower protocol and transport signals. However, the structures of ebxml business signals are universal and do not vary from transaction to transaction. Thus, they can be defined once and for all as part of the ebxml Business Process Specification Schema itself. The Business Process Specification Schema provides both the choreography of business signals, and the structure definition of the business payload of a business signal. The ebxml Message Service Specification signal structures provide business service state alignment infrastructure, including unique message identifiers and digests used to meet the basic process alignment requirements. The business signal payload structures provided herein are optional and normative and are intended to provide business and legal semantics to the business signals. A DTD is provided for each of the possible business signals. Production Rules A set of production rules are provided, defining the mapping from the UML version of the ebxml Business Process Specification Schema to the XML version. The primary purpose for these production rules is to govern the one-time generation of the DTD version of the ebxml Business Process Specification Schema from the UML Class Diagram version of the ebxml Business Process Specification Schema. The Class Diagram version of Business Process Specification Schema is not intended for the direct creation of ebxml Business Process Specifications. However, if a Business Process Specification was in fact (programmatically) created as an instance of this class diagram, the production rules would also apply for its conversion into a DTD conformant XML document. Separately, it is expected that a set of production rules will be constructed for the production of an XML version of an ebxml Business Process Specification from a set of UML diagrams constructed through the use of UMM. An instance of the UML Class Diagram version of the ebxml Business Process Specification Schema will through the application of its production rules produce an XML Specification Document that is analytically, semantically and functionally equivalent to one arrived at by modeling the same subset through the use of UMM and its associated production rules. Relationship to CPP/CPA A Business Process Specification is in essence the machine interpretable run time business process specification needed for an ebxml Business Service Interface. The Business Process Specification is therefore incorporated with or referenced by ebxml trading partner Collaboration Protocol Profiles (CPP) and ebxml Business Process Specification Schema Page 9 of 136

445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 Collaboration Protocol Agreements (CPA). Each CPP declares its support for one or more Roles within the Business Process Specification. Within these CPP profiles and CPA agreements are then added further technical parameters resulting in a full specification of the run-time software at each trading partner. Relationship to CC The Business Process Specification Schema does not by itself support the definiton of Business Documents. Rather, a Business Process Specification merely points to the definition of Business Documents. Such definitions may either be XML based, or as attachments may be any other structure, or completely unstructured. XML based Business Document Specifications may be based on the ebxml Core Components specifications. Relationship to ebxml Message Service Specification The Business Process Specification Schema will provide choreography of business messages and signals. The ebxml Message Service Specification provides the infrastructure for message / signal identification, typing, and integrity; as well as placing any one message in sequence with respect to other messages in the choreography. 6.1 Key Concepts of the ebxml Business Process Specification Schema The ebxml Business Process Specification Schema provides the semantics, elements, and properties necessary to define business collaborations. A business collaboration consists of a set of roles collaborating through a set of choreographed transactions by exchanging business documents. These basic semantics of a business collaboration are shown in Figure 4. ebxml Business Process Specification Schema Page 10 of 136

471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 Figure 4. Basic Semantics of a business collaboration Two or more business partners participate in the business collaboration through roles. The roles interact with each other through Business Transactions. The business transactions are sequenced relative to each other in a Choreography. Each Business Transaction consists of one or two predefined Business document flows. A Business Transaction may be additionally supported by one or more Business Signals. The following section describes the concepts of a Business Collaboration, a Business Transaction, a Business document flow, and a Choreography 1. Business Collaborations A business collaboration is a set of Business Transactions between business partners. Each partner plays one or more roles in the collaboration. The ebxml Business Process Specification Schema supports two levels of business collaborations, Binary Collaborations and Multiparty Collaborations. Binary Collaborations are between two roles only. ebxml Business Process Specification Schema Page 11 of 136

490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 Multiparty Collaborations are among more than two roles, but such Multiparty Collaborations are always synthesized from two or more Binary Collaborations. For instance if Roles A, B, and C collaborate and all parties interact with each other, there will be a separate Binary Collaboration between A and B, one between B and C, and one between A and C. The Multiparty Collaboration will be the synthesis of these three Binary Collaborations. Binary Collaborations are expressed as a set of Business Activities between the two roles. Each Business Activity reflects a state in the collaboration. The Business Activity can be a Business Transaction Activity, i.e. the activity of conducting a single Business Transaction, or a Collaboration Activity, i.e. the activity of conducting another Binary Collaboration. An example of the former is the activity of placing a purchase order. An example of the latter is the activity of negotiating a contract. In either case the activities can be choreographed relative to other activities as per below. The ability of a Binary Collaboration to have activities that in effect are executing other Binary Collaborations, is the key to recursive compositions of Binary Collaboration, and to the re-use of Binary Collaborations. In essence each Binary Collaboration is a re-useable protocol between two roles. 2. Business Transactions A Business Transaction is the atomic unit of work in a trading arrangement between two business partners. A Business Transaction is conducted between two parties playing opposite roles in the transaction. The roles are always a requesting role and a responding role. Like a Binary Collaboration, a Business Transaction is a re-useable protocol between two roles. The way it is re-used is by referencing it from a Binary Collaboration through the use of a Business Transaction Activity as per above. In a Business Transaction Activity the roles of the Binary Collaboration are assigned to the execution of the Business Transaction. Unlike a Binary Collaboration, however, the Business Transaction is atomic, it cannot be decomposed into lower level Business Transactions. A Business Transaction is a very specialized and very constrained protocol, in order to achieve very precise and enforceable transaction semantics. These semantics are expected to be enforced by the software managing the transaction, i.e. an ebxml Business Service Interface (BSI). A Business Transaction will always either succeed or fail. If it succeeds it may be designated as legally binding between the two partners, or otherwise govern their collaborative activity. If it fails it is null and void, and each partner must relinquish any mutual claim established by the transaction. This can be thought of as rolling back the Business Transaction upon failure. ebxml Business Process Specification Schema Page 12 of 136

535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 3. Business Document flows A business transaction is realized as Business Document flows between the requesting and responding roles. There is always a requesting Business Document, and optionally a responding Business Document, depending on the desired transaction semantics, e.g. one-way notification vs. two-way conversation. Actual document definition is achieved using the ebxml core component specifications, or by some methodology external to ebxml but resulting in a DTD or Schema that an ebxml Business Process Specification can point to. 4. Choreography The Business Transaction Choreography describes the ordering and transitions between business transactions or sub collaborations within a binary collaboration. In a UML tool this can be done using a UML activity diagram. The choreography is described in the ebxml Business Process Specification Schema using activity diagram concepts such as start state, completion state, activities, synchronizations, transitions between activities, and guards on the transitions. 5. Patterns The ebxml Business Process Specification Schema provides a set of unambiguous semantics within which to specify transactions and collaborations. Within these semantics the user community has flexibility to specify an infinite number of specific transactions and collaborations. The use of predefined patterns combines this flexibility with a consistency that facilitates faster design, faster implementation, and enables generic processing. A set of predefined transaction interaction patterns, defining common combinations of transaction interaction parameter settings can be found in UMM. While the UMM transaction interaction patterns themselves are not part of the ebxml specifications, all the security and timing parameters required to express the pattern properties are provided as attributes of elements in the Business Process Specification Schema. It is also anticipated that patterns for collaboration choreographies will emerge. An example of such a pattern is in the ebxml E-Commerce Patterns. Re-use, recursion, and patterns are among the key concepts of the ebxml Business Process Specification Schema. The following section will illustrate these key concepts. ebxml Business Process Specification Schema Page 13 of 136

574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 6.2 How to use the ebxml Business Process Specification Schema The ebxml Business Process Specification Schema should be used wherever ebxml compliant software is being specified to execute Business Collaborations. The generic term for such software is a Business Service Interface (BSI). The ebxml Business Process Specification Schema is used to specify the business process related configuration parameters for configuring a BSI to execute these collaborations. This section discusses How the ebxml Business Process Specification Schema fits in with other ebxml specifications. How to use the ebxml Business Process Specification Schema at design time, either for specifying brand new collaborations and transactions, or for re-using existing ones. How to specify core transaction semantics and parameters needed for a Collaboration-Protocol Profile and Agreement (CPP/CPA). Run-time transaction and collaboration semantics that the ebxml Business Process Specification Schema specifies and the Business Service Interface (BSI) is expected to manage. 6.3 How ebxml Business Process Specification Schema is used with other ebxml specifications The ebxml Business Process Specification Schema provides the semantics, elements, and properties necessary to define Business Collaborations. A collaboration consists of a set of roles collaborating through a set of choreographed transactions by exchanging Business Documents. As shown in Figure 5, Business Documents are defined at the intersection between the Business Process Specification and the ebxml Core Component specifications. A Business Process Specification will reference, but not define, a set of required Business Documents. At ebxml Business Documents are either defined by some external document specification, or assembled directly or indirectly from lower level information structures called core components. The assembly is based on a set of contexts, many of which are provided by the business processes, i.e. collaborations that use the documents in their document flows. The combination of the business process specification and the document specification become the basis against which partners can make agreements on conducting electronic business with each other. 613 ebxml Business Process Specification Schema Page 14 of 136

614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 Figure 5: ebxml Business Process Specification Schema and other ebxml S pecifications The user will extract and transform the necessary information from an existing Business Process and Information Model. Associated production rules could aid in creating an XML version of a Business Process Specification. Alternatively a user would use an XML based tool to produce the XML version directly. Production rules could then aid in converting into XMI, so that it could be loaded into a UML tool, if required. In either case, the XML version of the Business Process Specification gets stored in the ebxml repository and registered in the ebxml registry for future retrieval. The Business Process Specification would be registered using classifiers derived during its design. When implementers want to establish trading partner Collaboration Protocol Profile and Agreement the Business Process Specification XML document, or the relevant parts of it, are simply imbedded in or referenced by the CPP and CPA XML documents. ebxml CPP and CPA documents can only reference ebxml Business Process Specifications and only XML versions thereof. Guided by the CPP and CPA specifications the resulting XML document then becomes the configuration file for one or more Business Service Interfaces (BSI), ebxml Business Process Specification Schema Page 15 of 136

634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 i.e. the software that will actually manage either partner s participation in the collaboration. 6.4 How to design collaborations and transactions, re-using at design time This section describes the ebxml Business Process Specification Schema modeling relationships by building a complete Multiparty Collaboration from the bottom up, as follows: 1. Specify a Business Transaction 2. Specify the Business Document flow for a Business Transaction 3. Specify a Binary Collaboration re-using the Business Transaction 4. Specify a Choreography for the Binary Collaboration 5. Specify a higher level Binary Collaboration re-using the lower level Binary Collaboration 6. Specify a Multiparty Collaboration re-using Binary Collaborations Although this section, for purposes of introduction, discusses the specification of a collaboration from the bottom up, the ebxml Business Process Specification Schema very much is intended for specifying collaborations from the top down, re-using existing lower level content as much as possible. The constructs listed above support the specification of fairly complex multi party collaborations. However, an ebxml compliant Business Process Specificaton may be as simple as a single Binary Collaboration referencing a single Business Transaction. This involves only numbers 1 through 3 above. In other words, Higher-level Binary Collaborations, Multi-party Collaborations and choreography expressions are not required for ebxml Business Process Specification compliance. 6.4.1 Specify a Business Transaction and its Business Document Flow Figure 6 illustrates a business transaction. ebxml Business Process Specification Schema Page 16 of 136

Business Transaction name : string pattern : string isguaranteeddeliveryrequired : Boolean precondition : String postcondition : String beginswhen : String endswhen : String BusinessTransactionActivity +uses timetoperform : Time isconcurrent : Boolean +activities 1 n islegallybinding : Boolean +transaction +transaction 1 1 BusinessAction name : string isintelligiblecheckrequired : Boolean isauthorizationrequired : Boolean timetoacknowledgereceipt : Time isnonrepudiationrequired : Boolean isnonrepudiationofrecieptrequired : Boolean +requester 1 RequestingBusinessActivity timetoacknowledgeacceptance : Time 1 +responder RespondingBusinessActivity +requesting 0..1 0..1 +responding n+documentenvelope +documentenvelope1 DocumentEnvelope ispositiveresponse : Boolean 666 667 668 669 670 671 672 673 674 675 676 677 678 Figure 6. UML Diagram of a Business Transaction 6.4.1.1 Key Semantics of a Business Transaction A Business Transaction is the atomic unit of work in a trading arrangement between two business partners. A business transaction consists of a Requesting Business Activity, a Responding Business Activity, and one or two document flows between them. A Business Transaction may be additionally supported by one or more Business Signals that govern the use and meaning of acknowledgements and related matters in the transaction. ebxml Business Process Specification Schema Page 17 of 136

679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 Implicitly there is a requesting role performing the Requesting Business Activity and a responding role performing the Responding Business Activity. These roles become explicit when the transaction is used within a Business Transaction Activity within a Binary Collaboration. There is always a Request document flow. Whether a Response document is required is part of the definition of the Business Transaction. Some Business Transactions need this type of request and response, typically for the formation of a contract or agreement. Other Business Transactions are more like notifications, and have only a Request document flow. An abstract superclass, Business Action, is the holder of attributes that are common to both Requesting Business Activity and Responding Business Activity. 6.4.1.2 Sample syntax Here is a simple notification transaction with just one document flow: <BusinessTransaction name="notify of advanceshipment" <RequestingBusinessActivity name="" <DocumentEnvelope BusinessDocument name="asn"/ </RequestingBusinessActivity <RespondingBusinessActivity name="" </RespondingBusinessActivity </BusinessTransaction Associated with each document flow can be one or more business signals acknowledging the document flow. These acknowledgment signals are not modeled explicitly but parameters associated with the transaction specify whether the signals are required or not. The possible Document Flows and business signals within a Business Transaction are shown in Figure 7. 710 ebxml Business Process Specification Schema Page 18 of 136

711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 Figure 7: Possible document flows and signals and their sequence These acknowledgment signals (a.k.a. Business Signals) are application level documents that signal the current state of the business transaction. Whether a receiptacknowledgement and/or acceptanceacknowledgement signal are required is part of the pattern specified for the Business Transaction. These business signals have specific business purposes, relating to the processing and management of documents and document envelopes prior to evaluation of their business terms, and are separate from lower protocol and transport signals. The Receipt acknowledgement business signal, if used, signals that a message has been properly received. The property isintelligiblecheckrequired allows partners to agree that a message should be confirmed by a Receipt acknowledgement only if it also is legible. Legible means that it has been passed a structure/ schema validity check. Both the proper receipt and, if evaluated, the legibility of a message are reviewed (and if present acknowledged) prior to the application of any business rules or evaluation of the terms or guard expressions in the message's business documents or document envelope. ebxml Business Process Specification Schema Page 19 of 136

733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 The Acceptance Acknowledgement business signal, if used, signals that the message received has been accepted for business processing. This is the case if the contents of the message's business documents and document envelope have passed a business rule validity check. Failure to send either signal, when required (by specifying a timeout value in timetoacknowledgereceipt or timetoacknowledgeacceptance), will result in the transaction being null and void, and therefore will prevent any "success" end state that would have depended on receipt of a business document satisfying the associated timetoperform. 6.4.1.3 Sample syntax Here is a slightly more complex transaction with two document flows and three business signals. The request requires both receipt and acceptance acknowledgement, the response requires only receipt acknowledgement. P2D is a W3C Schema syntax adopted from the ISO 8601 standard and means Period=2 Days. P3D means Period=3 Days, P5D means Period=5 Days. These periods are all measured from original sending of request. <BusinessTransaction name="create Order" <RequestingBusinessActivity name="" isnonrepudiationrequired="true" timetoacknowledgereceipt= P2D" timetoacknowledgeacceptance= P3D" <DocumentEnvelope BusinessDocument="Purchase Order"/ </RequestingBusinessActivity <RespondingBusinessActivity name="" isnonrepudiationrequired="true" timetoacknowledgereceipt= P5D" <DocumentEnvelope ispositiveresponse="true" BusinessDocument="PO Acknowledgement"/ </DocumentEnvelope </RespondingBusinessActivity </BusinessTransaction 6.4.1.4 Specifying Business Document flows Request document flows and response document flows contain Business Documents that pertain to the Business Transaction. The model for this is shown in Figure 8. Business Documents have varying structures. Business signals, however always have the same structure, defined once and for all as part of the ebxml Business Process Specification Schema. ebxml Business Process Specification Schema Page 20 of 136

778 779 780 781 RequestingBusinessActivity timetoacknowledgeacceptance : Time RespondingBusinessActivity 0..1 +responding 0..1 +requesting +documentenvelope 1 n +documentenvelope DocumentEnvelope ispositiveresponse : Boolean DocSecurity isconfidential : Boolean istamperproof : Boolean isauthenticated : Boolean n 1 +documentenvelope +documentenvelope +attachment n Attachment BusinessDocument name : String name : String +attachment mimetype : String specificationlocation : URI specification : URI +businessdocument specificationelement : String n version : String 0..1 conditionexpression : Expression 1 +businessdocument 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 Figure 8: UML Diagram of document flow A document flow is not modeled directly. Rather it is modeled indirectly as a Document Envelope sent by one role and received by the other. The Document Envelope is always associated with one Requesting Business Activity and one Responding Business Activity to model the flow. Document Envelopes are named. There is always only one named Document Envelope for a Requesting Activity. There may be zero, one, or many mutually exclusive, named Document Envelopes for a Responding Activity. For example, the Response Document Envelopes for a purchase order transaction might be named PurchaseOrderAcceptance, PurchaseOrderDenial, and PartialPurchaseOrderAcceptance. In the actual execution of the purchase order transaction, however, only one of the defined possible responses will be sent. The Document Envelope represents the flow of documents between the activities. Each Document Envelope carries exactly one primary Business Document. A Document Envelope can optionally have one or more attachments, all related to the primary Business Document. The document and its attachments in essence form one transaction in the payload in the ebxml Message Service message structure. ebxml Business Process Specification Schema Page 21 of 136

804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 6.4.1.5 Sample syntax This example shows a business transaction with one request and two possible responses, a success and a failure. The request has an attachment. All the the Business Documents are fully qualified with the schema name. <BusinessDocument name=" Purchase Order " specificationlocation="someplace"/ <BusinessDocument name=" PO Acknowledgement " specificationlocation="someplace"/ <BusinessDocument name=" PO Rejection " specificationlocation="someplace"/ <BusinessDocument name="delivery Instructions" specificationlocation="someplace"/ <BusinessTransaction name="create Order" <RequestingBusinessActivity name="" <DocumentEnvelope ispositiveresponse="true" ` BusinessDocument="ebXML1.0/PO Acknowledgement" <Attachment name= DeliveryNotes mimetype= XML BusinessDocument= "ebxml1.0/delivery Instructions" specification= isconfidential= true istamperproof= true isauthenticated= true </Attachment </DocumentEnvelope </RequestingBusinessActivity <RespondingBusinessActivity name="" <DocumentEnvelope ` BusinessDocument="ebXML1.0/PO Acknowledgement"/ </DocumentEnvelope <DocumentEnvelope ispositiveresponse="false" ` BusinessDocument=" ebxml1.0/po Rejection"/ </DocumentEnvelope </RespondingBusinessActivity </BusinessTransaction 6.4.2 Specify a Binary Collaboration Figure 9 illustrates a binary collaboration. ebxml Business Process Specification Schema Page 22 of 136

BinaryCollaboration +collaboration 1 name : string pattern : string timetoperform : Time precondition : String postcondition : String beginswhen : String endswhen : String 1 +uses +collaboration 1 +states n BusinessState n +role 1 AuthorizedRole name : string +from 1 isinitiator : Boolean +to n n BusinessActivity name : string Business Transaction name : string pattern : string isguaranteeddeliveryrequired : Boolean precondition : String postcondition : String beginswhen : String endswhen : String +uses 1 +activities n BusinessTransactionActivity timetoperform : Time isconcurrent : Boolean islegallybinding : Boolean +usedby n CollaborationActivity 848 849 850 Figure 9: UML Diagram of a Binary Collaboration 851 852 853 854 855 856 857 858 859 860 861 6.4.2.1 Key Semantics of a Binary Collaboration A Binary Collaboration is always between two roles. These two roles are called Authorized Roles, because they represent the actors that are authorized to participate in the collaboration. A Binary Collaboration consists of one or more Business Activities. These Business Activities are always conducted between the two Authorized Roles of the Binary Collaboration. For each activity one of two roles is assigned to be the InitiatingRole (from) and the other to be the RespondingRole (to). ebxml Business Process Specification Schema Page 23 of 136

862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 A Business Activity can be either a Business Transaction Activity or a Collaboration Activity. A Business Transaction Activity is the performance of a Business Transaction. Business Transactions are re-useable relative to Business Transaction Activity. The same Business Transaction can be performed by multiple Business Transaction Activities in different Binary Collaborations, or even by multiple Business Transaction Activities in the same Binary Collaboration. A Collaboration Activity is the performance of a Binary Collaboration, possibly within another Binary Collaboration. Binary Collaborations are reuseable relative to Collaboration Activity. The same Binary Collaboration can be performed by multiple Collaboration Activities in different Binary Collaborations, or even by multiple Collaboration Activities in the same Binary Collaboration. When performing a Binary Collaboration within a Binary Collaboration there is an implicit relationship between the roles at the two levels. Assume that Binary Collaboration X is performing Binary Collaboration Y through Collaboration Activity Q. Binary Collaboration X has Authorized roles Customer and Vendor. In Collaboration Activity Q we assign Customer to be the initiator, and Vendor to be the responder. Binary Collaboration X has Authorized roles Buyer and Seller and a Business Transaction Activity where Buyer is the initiator and Seller the responder. We have now established a role relationship between the roles Customer and Buyer because they are both initiators in activities in the related performing and performed Binary Collaborations. Since a Business Transaction is atomic in nature, the performing of a single Business Transaction through a Business Transaction Activity is also atomic in nature. If the desired semantic is not atomic, then the task should be split over multiple transactions. For instance if it is desired to model several partial acceptances of a request, then the request should be modeled as one transaction within a binary collaboration and the partial acceptance(s) as separate transactions. The CPA/CPP Specification requires that parties agree upon a Collaboration Protocol Agreement (CPA) in order to transact business. A CPA associates itself with a specific Binary Collaboration. Thus, all Business Transactions performed between two parties should be referenced through Business Transaction Activities contained within a Binary Collaboration. 6.4.2.2 Sample syntax Here is a simple Binary Collaboration using one of the Business Transactions defined above: ebxml Business Process Specification Schema Page 24 of 136

906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 <BinaryCollaboration name="firm Order timetoperform="p2d" <Documentation timetoperform = Period: 2 days from start of transaction </Documentation <InitiatingRole name="buyer"/ <RespondingRole name="seller"/ <BusinessTransactionActivity name="create Order" businesstransaction="create Order" fromauthorizedrole="buyer" toauthorizedrole="seller"/ </BinaryCollaboration Here is a slightly more complex Binary Collaboration re-using the same Business Transaction as the previous Binary Collaboration, and adding the use of another of the Business Transactions defined above: <BinaryCollaboration name="product Fulfillment" timetoperform="p5d" <Documentation timetoperform = Period: 5 days from start of transaction </Documentation <InitiatingRole name="buyer"/ <RespondingRole name="seller"/ <BusinessTransactionActivity name="create Order" businesstransaction="create Order" fromauthorizedrole="buyer" toauthorizedrole="seller" islegallybinding= true / <BusinessTransactionActivity name="notify shipment" businesstransaction="notify of advance shipment" fromauthorizedrole="buyer" toauthorizedrole="seller"/ </BinaryCollaboration 6.4.3 Specify a MultiParty Collaboration Figure 10 illustrates a multiparty collaboration ebxml Business Process Specification Schema Page 25 of 136

+ collaboration 1 MultiParty Collaboration 1 Business Partner Role +performedby Performs name : string name : string +partners +performers n n 1 n n Transition n +entering oninitiation : Boolean guardcondition : Status +exiting successexpression : Expression n +from 1 +to 1 BusinessState +states +collaboration n 1 n AuthorizedRole +performers name : string +authorizedrole 1 +torole 1 1 +collaboration 1 BinaryCollaboration name : string pattern : string timetoperform : Time precondition : String postcondition : String beginswhen : String endswhen : String 950 MultiParty Collaboration name : string n n Transition n +entering oninitiation : Boolean conditionguard : Status +exiting conditionexpression : Expression n + collaboration 1 AuthorizedRole n Business Partner Role +performedby 1 Performs +performers name : string name : string +performers 1 isinitiator : Boolean +partners n +authorizedrole n +role n 1 +from 1 BusinessState +states 1 +to +collaboration n 1 1 +collaboration 1 BinaryCollaboration name : string pattern : string timetoperform : Time precondition : String postcondition : String beginswhen : String endswhen : String 951 952 Figure 10: UML Diagram of a MultiParty Collaboration 953 954 955 956 957 958 959 960 961 962 963 964 965 966 967 968 6.4.3.1 Key Semantics of a Multiparty Collaboration A Multiparty Collaboration is a synthesis of Binary Collaborations. A Multiparty Collaboration consists of a number of Business Partner Roles. Each Business Partner Role performs one Authorized Role in one of the binary collaborations, or perhaps one Authorized Role in each of several binary collaborations. This is modeled by use of the Performs element. This Performs linkage between a Business Partner Role and an Authorized Role is the synthesis of Binary Collaborations into Multiparty Collaborations. Implicitly the Multiparty Collaboration consists of all the Binary Collaborations in which its Business Partner Roles play Authorized Roles. Each binary pair of trading partners will be subject to one or more distinct CPAs. ebxml Business Process Specification Schema Page 26 of 136

969 970 971 972 973 974 975 976 977 978 979 980 981 982 983 984 985 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 Within a Multiparty Collaboration, you may choreograph transitions between Business Transaction Activities in different Binary Collaborations, as described below. 6.4.3.2 Sample syntax Here is a simple Multiparty Collaboration using the Binary Collaborations defined above. <MultiPartyCollaboration name="dropship" <BusinessPartnerRole name="customer" <Performs initiatingrole= //binarycollaboration[@name="firm Order ] /InitiatingRole[@name= buyer ] / </BusinessPartnerRole <BusinessPartnerRole name="retailer" <Performs respondingrole= //binarycollaboration[@name="firm Order ] /RespondingRole[@name= seller ] / <Performs initiatingrole= //binarycollaboration[@name=" Product Fulfillment /InitiatingRole[@name= buyer ] / </BusinessPartnerRole <BusinessPartnerRole name="dropship Vendor" <Performs respondingrole= //binarycollaboration[@name=" Product Fulfillment /RespondingRole[@name= seller ] / </BusinessPartnerRole </MultiPartyCollaboration 6.4.4 Specify a Choreography Figure 11 illustrates a choreography. ebxml Business Process Specification Schema Page 27 of 136

<<Enumeration Status Success BusinessFailure TechnicalFailure AnyFailure Business Partner Role name : string 1 n Transition oninitiation : Boolean conditionguard : Status n conditionexpression : Expression n n in +entering +exiting out 1 +from +to 1 BusinessState +states 1 +collaboration n 1 BinaryCollaboration name : string pattern : string timetoperform : Time precondition : String postcondition : String beginswhen : String endswhen : String 1 +uses Start CompletionState guardcondition : Status Fork name : string Join name : string waitforall : Boolean BusinessActivity name : string Success Failure BusinessTransactionActivity timetoperform : Time isconcurrent : Boolean islegallybinding : Boolean +usedby n CollaborationActivity 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 Figure 11: UML Diagram of a Choreography 6.4.4.1 Key Semantics of a Choreography A Choreography is an ordering and sequencing of Business Activities within a Binary Collaboration. The choreography is specified in terms of Business States, and transitions between those Business States. A Business Activity is an abstract kind of Business State. Its two subtypes Business Transaction Activity and Collaboration Activity are concrete Business States. The purpose of a Choreography is to order and sequence Business Transaction Activity and/or Collaboration Activity within a Binary Collaboration, or across Binary Collaborations within a Multiparty Collaboration. There are a number of auxiliary kinds of Business States that facilitate the choreographing of Business Activities. These include a Start state, a Completion state (which comes in a Success and Failure flavor), a Fork state and a Synchronization state. These are all equivalent to diagramming artifacts on a UML activity chart. ebxml Business Process Specification Schema Page 28 of 136

1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 Transitions are between Business States. Transitions can be gated by Guards. Guards can refer to the status of the Document Envelope that caused the transition, the type of Document sent, the content of the document, or postconditions on the prior state. A Transition can also be used to create nested BusinessTransactionActivities. A nested BusinessTransactionActivity is one where a first transition happens after the receipt of the request in the first transaction, and then the entire second transaction is performed before returning to the first transaction to send the response back to the original requestor. The flag oninitiation in Transition is used for this purpose. Nested BusinessTransactionActivity are typically within a multiparty collaboration. In essence an Authorized Role in one Binary Collaboration receives a request, then turns around and becomes the requestor in an other Binary Collaboration before coming back and sending the response in the first Binary Collaboration. isconcurrent is a parameter that governs the flow of transactions. Unlike the security and timing parameters it does not govern the internal flow of a transaction, rather it determines whether multiple instances of that transaction type can be open at the same time as part of the same business transaction activity. IsConcurrent is the parameter that governs this. It is at the business transaction activity level. 6.4.4.2 Sample syntax Here is the same Binary Collaboration as used before, with choreography added at the end. There is a transition between the two, a start and two possible outcomes of this collaboration, success and failure: <BinaryCollaboration name="product Fulfillment" timetoperform="p5d" <Documentation timetoperform = Period: 5 days from start of transaction </Documentation <InitiatingRole name="buyer"/ <RespondingRole name="seller"/ <BusinessTransactionActivity name="create Order" businesstransaction="create Order" fromauthorizedrole="buyer" toauthorizedrole="seller"/ <BusinessTransactionActivity name="notify shipment" businesstransaction="notify of advance shipment" fromauthorizedrole="buyer" toauthorizedrole="seller"/ <Start tobusinessstate="create Order"/ <Transition ebxml Business Process Specification Schema Page 29 of 136

1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 frombusinessstate="create Order" tobusinessstate="notify shipment"/ <Success frombusinessstate="notify shipment" conditionguard="success"/ <Failure frombusinessstate="notify shipment" conditionguard="businessfailure"/ </BinaryCollaboration Here is the same Multiparty Collaboration as defined before, but with a simple choreography (transition) across two Binary Collaborations. <MultiPartyCollaboration name="dropship" <BusinessPartnerRole name="customer" <Performs initiatingrole= //binarycollaboration[@name="firm Order ] /InitiatingRole[@name= buyer ] / </BusinessPartnerRole <BusinessPartnerRole name="retailer" <Performs respondingrole= //binarycollaboration[@name="firm Order ] /RespondingRole[@name= seller ] / <Performs initiatingrole= //binarycollaboration[@name=" Product Fulfillment /initiatingrole[@name= buyer ] / <Transition frombinarycollaboration Firm Order frombusinessstate= //binarycollaboration[@name="firm Order ] /[@name="create Order"] tobusinessstate= //binarycollaboration[@name="product Fulfillment ] /[@name="create Order"] / </BusinessPartnerRole <BusinessPartnerRole name="dropship Vendor" <Performs respondingrole= //binarycollaboration[@name=" Product Fulfillment /RespondingRole[@name= seller ] / </BusinessPartnerRole </MultiPartyCollaboration ebxml Business Process Specification Schema Page 30 of 136

1120 1121 1122 1123 1124 6.4.5 The whole model Figure 12 shows the above semantics collectively as a UML class diagram. This diagram contains the whole UML version of the ebxml Business Process Specification Schema ebxml Business Process Specification Schema Page 31 of 136

1125 1126 Figure 12: Overall ebxml Business Process Specification Schema as UML class diagram ebxml Business Process Specification Schema Page 32 of 136

MultiParty + collaboration Collaboration name : string 1 +partners n +performedby Business n Partner Role 1 +performers name : string Performs n 1 +performers +authorizedrole AuthorizedRole name : string isinitiator : Boolean 1 +role n +collaboration 1 BinaryCollaboration +from 1 1 +to n n Transition oninitiation : Boolean conditionguard : Status in +entering n +from 1 +exiting out +to conditionexpression : Expression n 1 BusinessState +states 1 +collaboration n 1 name : string pattern : string timetoperform : Time precondition : String postcondition : String beginswhen : String endswhen : String 1 +uses Start CompletionState guardcondition : Status Fork name : string Join name : string waitforall : Boolean n n BusinessActivity name : string Success Failure Business Transaction name : string pattern : string isguaranteeddeliveryrequired : Boolean precondition : String postcondition : String beginswhen : String endswhen : String +uses 1 +activities n +transaction BusinessTransactionActivity timetoperform : Time isconcurrent : Boolean islegallybinding : Boolean +usedby n CollaborationActivity +transaction 1 1 BusinessAction name : string isintelligiblecheckrequired : Boolean isauthorizationrequired : Boolean timetoacknowledgereceipt : Time isnonrepudiationrequired : Boolean isnonrepudiationofrecieptrequired : Boolean <<Enumeration Status Success BusinessFailure TechnicalFailure AnyFailure +requester 1 RequestingBusinessActivity timetoacknowledgeacceptance : Time 1 +responder RespondingBusinessActivity +requesting 0..1 0..1 +responding +documentenvelope 1 n+documentenvelope DocumentEnvelope ispositiveresponse : Boolean DocSecurity isconfidential : Boolean istamperproof : Boolean isauthenticated : Boolean +documentenvelope 1 +attachment n Attachment name : String mimetype : String specification : URI version : String n +documentenvelope +businessdocument +attachment n 1 0..1 +businessdocument BusinessDocument name : String specificationlocation : URI specificationelement : String conditionexpression : Expression 1127 ebxml Business Process Specification Schema Page 33 of 136

1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 1144 1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 1157 1158 1159 1160 1161 6.5 Core Business Transaction Semantics The ebxml concept of a business transaction and the semantics behind it are central to predictable, enforceable commerce. It is expected that any Business Service Interface (BSI) will be capable of managing a transaction according to these semantics. The ebxml Business Transaction semantics allows you to specify electronic commerce transactions that provide Interaction Predictability, i.e. have clear roles, clear transaction scope, clear time bounds, clear business information semantics, clear determination of success or failure. Ability to create Legally Binding Contracts, i.e. the ability to specify that Business Transactions may be agreed to bind the parties. Nonrepudiation, i.e. may specify the keeping of artifacts to aid in legal enforceability. Authorization Security, i.e. may be specified to require athorization of parties performing roles. Document Security, i.e. may be specified to be authorized, authenticated, confidential, tamperproof. Reliability, i.e. the ability to specify reliable delivery of Business Documents and signals. Run time Business Transaction Semantics, i.e. the rules and configuration parameters required for Business Service Interface software to predictably and deterministically execute ebxml Business Transactions. Each of the above characteristics of ebxml Business Transaction semantics is discussed in detail below. 6.5.1 Interaction Predictability All Business Transactions follow a very precisely prescribed flow, or a precisely defined subset there-of. The following is an overall illustration of this flow. It can be thought of as the state machine across the two business partners. The N090R9.1 chapter on the UMM metamodel has a detail state chart for each of the business partners. ebxml Business Process Specification Schema Page 34 of 136

1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 Figure 13: Schematic of core Business Transaction semantics. In the ebxml model the business transaction always has the following semantics. 1. The Business Transaction is a unit of work. All of the interactions in a business transaction must succeed or the transaction must be rolled back to a defined state before the transaction was initiated. 2. A Business Transaction is conducted between two business partners playing opposite roles in the transaction. These roles are always the Requesting Role and the Responding Role. 3. A Business Transaction definition specifies exactly when the Requesting Activity is in control, when the Responding Activity is in control, and when control transitions from one to the other. In all Business Transactions control starts at the Requesting Activity, then transitions to the Responding Activity, and then returns to the Requesting Activity. 4. A Business Transaction always starts with a request sent out by the requesting activity. 5. The request serves to transition control to the responding role. ebxml Business Process Specification Schema Page 35 of 136

1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 1195 1196 1197 1198 1199 1200 1201 1202 1203 1204 1205 1206 1207 1208 1209 1210 1211 1212 1213 1214 1215 1216 1217 1218 1219 1220 1221 1222 1223 6. After the receipt of the Request document flow, the responding activity may send a receiptacknowledgement signal and/or an acceptanceacknowledgement signal to the requesting role. 7. The responding role then enters a responding activity. During or upon completion of the responding activity zero or one response is sent. 8. Control will be returned back to the requesting activity if either a receiptacknowledgement and/or acceptanceacknowledgement and/or a response is specified as required. A receiptacknowledgement (if required) must always occur before an acceptanceacknowledgement (if required), and an acceptanceacknowledgement must always occur before a response (if required). Control is returned to the requesting activity based on the last required of these three (if any). If none required, control stays with the responding activity. 9. All business transactions succeed or fail. Success or failure depends on: a. The receipt or non-receipt of the request, the response and/or business signals b. The occurrence of time-outs c. The occurrence of a business exception d. The occurrence of a control exception e. The interpretation of the received response and guard expressions on transitions to success or failure 10. The determination of Business Transaction success or failure is established by the requesting party based on the above success or failure factors. Once success or failure is thus established, the Business Transaction is considered closed with respect to both parties. 11. Upon receipt of a response the requesting activity may send a receiptacknowledgement signal back to the responding role. This is merely a signal and does not pass control back to the responding activity, nor does it alter the successful or failed completion of the Business Transaction that was based on the receipt of the Response. 12. Upon identifying a time-out or exception in the processing of a Business Transaction, and closing the transaction accordingly, the requesting party may send a notification of failure to the responding party. This is considered a new Business Transaction and does not alter the already established conclusion of the Business Transaction. 6.5.1.1 Transaction Interaction Patterns The business transaction specification will specify whether a requesting document requires a responding substantive document in order to achieve a "success" end state. In addition, the transaction may specify a proper nonzero time duration for timetoperform, imposing a deadline for the substantive response. ebxml Business Process Specification Schema Page 36 of 136

1224 1225 1226 1227 1228 1229 1230 1231 1232 1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256 1257 1258 1259 1260 1261 1262 1263 1264 1265 1266 1267 1268 1269 Furthermore, the specification of a business transaction may indicate, for the request whether receiptacknowledgement and/or acceptanceacknowledgement are required, and for the response whether receiptacknowledgement is required. The way to specify that a receiptacknowledgement is required is to set the parameter timetoacknowledgereceipt to any proper time duration other than zero. If this parameter has been set to a proper nonzero time duration, optionally either or both of the isintelligiblecheckrequired and isnonrepudiationofreceiptrequired parameters may also be set to Yes. The way to specify that a acceptanceacknowledgement is required is to set the parameter timetoacknowledgeacceptance to any proper time duration other than zero. So these two acknowledgement related parameters double as Boolean flags for whether the signal is required as part of the transaction, and as values for time-out of the transaction if the signal is not received. The specification of a business transaction may require each one of these signals independently of whether the other is required. If one is not required, it is actually not allowed. Therefore there is a finite set of combinations. The UMM supplies an illustrative set of patterns representing those combinations, for potential re-use. 6.5.2 Creating legally binding contracts Trading partners may wish to indicate that a Business Transaction performed as part of an ebxml arrangement is, or is not, intended to be binding. A declaration of intent to be bound is a key element in establishing the legal equivalence of an electronic message to an enforceable signed physical writing. Parties may create explicit evidence of that intent by (1) adopting the ebxml Business Process Specification Schema standard and (2) manipulating the parameter ("islegallybinding") designated by the standard to indicate that intent. In some early electronic applications, trading partners have simply used the presence, or absence, of an electronic signature (such as under the XML-DSIG standard) to indicate that intent. However, documents which rely solely on the presence of a signature may or may not be correctly interpreted, if there is semantic content indicating that a so-called contract is a draft, or nonbinding, or the like. In ebxml, the presence or absence of an electronic signature cannot indicate by itself determine legally binding assent, because XML-DSIG signatures are reserved for other uses as an assurance of sender identity and message integrity. ebxml Business Process Specification Schema Page 37 of 136

1270 1271 1272 1273 1274 1275 1276 1277 1278 1279 1280 1281 1282 1283 1284 1285 1286 1287 1288 1289 1290 1291 1292 1293 1294 1295 1296 1297 1298 1299 1300 1301 1302 1303 1304 1305 1306 1307 1308 1309 1310 1311 1312 1313 1314 1315 islegallybinding is a parameter at the BusinessTransactionActivity level, which means that the performing of a BusinessTransaction within a Binary Collaboration is either specified as legally binding or not. When operating under this standard, parties form binding agreements by exchanging binding messages that agree to terms (e.g., offer and acceptance). The "islegallybinding" parameter is Boolean, and its default value is "true." Under this standard, the exclusive manner for indicating that a Business Activity is not intended to be binding is to include a "false" value for the "islegallybinding" parameter for the transaction activity. As in EDI, the ebxml standard assumes that Business Transactions are intended by the trading parties to be binding unless otherwise indicated. As a non-normative matter, parties may wish to conduct nonbinding transactions for a variety of reasons, including testing, and the exchange of proposed offers and counteroffers on a non-committal basis so as to discover a possible agreed set of terms. When using tangible signed documents, parties often do so by withholding a manual signature, or using a "DRAFT" stamp. In ebxml, trading partners may indicate that result by use of the "islegallybinding" parameter. See the illustrative Simple Negotiation Pattern set forth in the ebxml E-Commerce Patterns. 6.5.3 Non-Repudiation Trading partners may wish to conduct legally enforceable business transactions over ebxml. A party may elect to use nonrepudiation protocols in order to generate documentation that would assist in the enforcement of the contractual obligation in court, in the case that the counterparty later attempts to repudiate its ebxml Business Documents and messages. Repudiation generally refers to the ability of a trading partner to argue at a later time, based on the persistent artifacts of a transaction, that it did not agree to the transaction. That argument might be based on assertions that a replying document was not sent, or was not sent by the proper party, or was incorrectly interpreted (under the applicable standard or the trading partners' business rules) as forming agreement. There are two kinds of non-repudiation protocol available under this document. Each protocol provides the user with some degree of additional evidentiary assurance by creating or requesting additional artifacts that would assist in a later dispute over repudiation issues. Neither is a dispositive absolute assurance. As in the paper world, trading partners are always free to invent colorful new arguments than an apparently-enforceable statement should be ignored. These parameters simply offer some opportunities to make that more difficult. ebxml Business Process Specification Schema Page 38 of 136

1316 1317 1318 1319 1320 1321 1322 1323 1324 1325 1326 1327 1328 1329 1330 1331 1332 1333 1334 1335 1336 1337 1338 1339 1340 1341 1342 1343 1344 1345 1346 1347 1348 1349 1350 1351 1352 1353 1354 One imposes a duty on each party to save copies of all Business Documents and Document Envelopes comprising the transaction, each on their own side, i.e., requestor saves his request, responder saves his response. This is the isnonrepudiationrequired parameter in the requesting or responding activity. It is logically equivalent to a request that the other trading partner maintain an audit trail. However, failure to comply with that request is not necessarily computationally detectable at run time, nor would it override the determination of a "success" or "failure" end state. The other requires the responder to send a signed copy of the receipt, which the requestor then saves. This is the isnonrepudiationofreceiptrequired parameter in the requesting business activity. NonRepudiationOfReceipt is tied to the ReceiptAcknowledgement, in that it requires the latter to be digitally signed. So NonRepudiationOfReceipt is meaningless if ReceiptAcknowledgement is not required. Failure to comply with NonRepudiation of Receipt would be computationally detectable at run time, and would override the determination of a "failure" end state. If a timetoacknowledgereceipt is imposed on a requesting message, and NonRepudiationOfReceipt is true, only a digitally signed receipt will satisfy the imposed timeout deadline. Thus, a failure to send a signed receipt within timetoacknowledgereceipt, would make the transaction null and void. Parameter isnonrepudiationrequired 6.5.4 Authorization security BSI requirement Must save audit trail of messages it sends isnonrepudiationofreceiptrequired Must digitally sign receiptacknowledgements Each request or response may be sent by a variety of individuals, representatives or automated systems associated with a business partner. There may be cases where trading partners have more than one ebxml-capable business service interface, representing different levels of authority. In such a case, the parties may establish rules regarding which interfaces or authors may be confidently relied upon as speaking for the enterprise. In order to invoke those rules, a party may specify IsAuthorizationRequired on a requesting or and responding activity accordingly, with the result that [the activity] will only be ebxml Business Process Specification Schema Page 39 of 136

1355 1356 1357 1358 1359 1360 1361 1362 1363 1364 1365 1366 1367 1368 1369 1370 1371 1372 1373 1374 1375 1376 1377 1378 processed as valid if the party interpreting it successfully matches the stated identity of the activity's [Authorized Role] to a list of allowed values previously supplied by that party. Parameter 6.5.5 Document security IsAuthorizationRequired BSI requirement Must validate identity of originator against a list of authorized originators IsAuthorizationRequired is specified on the requesting and responding activity accordingly. The following security characteristics of each Business Document being transported, even if many are collected in the same message, can be specified individually, or collectively within a Document Envelope: Parameter isconfidential. istamperproof. Delivery Channel requirement The information entity is encrypted so that unauthorized parties cannot view the information The information entity has an encrypted message digest that can be used to check if the message has been tampered with. This requires a digital signature (sender s digital certificate and encrypted message digest) associated with the document entity. isauthenticated. There is a digital certificate associated with the document entity. This provides proof of the signer s identity. The value of isconfidential, istamperproof, isauthenticated at the Document Envelope always applies to the primary Business Document. It also applies to each of the attachments unless specifically overridden at the Attachment level. When set to YES (or TRUE) these parameters assume that the corresponding security characteristic is provided in a manner providing persistence. Compliance requires that the specified character of the document survive its reception at a business service interface, and persist as the document is archived or forwarded. ebxml Business Process Specification Schema Page 40 of 136

1379 1380 1381 1382 1383 1384 1385 1386 1387 1388 1389 1390 1391 1392 1393 1394 1395 1396 1397 1398 1399 1400 1401 1402 1403 1404 1405 1406 1407 1408 1409 1410 1411 6.5.6 Reliability This parameter at the Business Transaction level states whether guaranteed delivery of the transaction's Business Documents is required. Parameter IsGuaranteedDeliveryRequired Delivery Channel requirement This means that Business Documents transferred are guaranteed (by some delivery channel or other party other than the trading partners) to be delivered This is a declaration that trading partners must employ only a delivery channel that provides a third-party delivery guarantee, to send Business Documents in the relevant transaction. 6.5.7 Parameters required for CPP/CPA The ebxml Business Process Specification Schema provides parameters that can be used to specify certain levels of security and reliability. The ebxml Business Process Specification Schema provides these parameters in general business terms. These parameters are generic requirements for the business process, but for ebxml implementations, these parameters are specifically used to instruct the CPP and CPA to require BSI and/or delivery channel capabilities to achieve the specified service levels. The CPP and CPA translate these into parameters of two kinds. One kind of parameter determines the selection of certain security and reliability parameters applicable to the transport method and techniques used by the delivery channel. Document security, and Reliability above, are determinators of delivery channel selection. The other kind of parameter determines the selection of certain service levels or capabilities of the BSI itself, in order for it to support the run time Business Transaction semantics as listed below. 6.6 Run time Business Transaction semantics The ebxml concept of a business transaction and the semantics behind it are central to predictable, enforceable commerce. It is expected that any Business Service Interface (BSI) will be capable of managing a transaction according to these semantics. ebxml Business Process Specification Schema Page 41 of 136

1412 1413 1414 1415 1416 1417 1418 1419 1420 1421 1422 1423 1424 1425 1426 1427 1428 1429 1430 1431 1432 1433 1434 1435 1436 1437 1438 1439 1440 1441 1442 1443 1444 1445 1446 1447 1448 1449 1450 1451 1452 Therefore, the Business Service Interface (BSI), or any software that implements one role in an ebxml collaboration needs at minimum to be able to support the following transaction semantics: 1. Detection of the opening of a transaction 2. Detection of transfer of control 3. Detection of successful completion of a transaction a. Application of business rules expressed as ispositiveresponse and transition conditionguard for determination of success 4. Detection of failed completion of a transaction a. Detection of time-outs b. Detection of exceptions c. Application of business rules expressed as ispositiveresponse and transition conditionguard for determination of failure 5. Notification of failure 6. Receipt of notification of failure 7. Rollback upon failure (note this is the independent responsibility of each role, it is not a co-coordinated roll-back, there are no 2-phase commits in ebxml) ebxml does not specify how these transaction semantics are implemented but it is assumed that any Business Service Interface (BSI) will be able to support these basic transaction semantics at runtime. If either party cannot provide full support, then the requirements may be relaxed as overrides in the CPP/CPA. The following sections discuss the two causes of failure: Time-outs and Exceptions. When either one happens, it is the responsibility of the two roles to do the necessary roll-back, and to exit the transaction. The responsibilities of the two roles differ slightly and are described in each of the sections below. Generally, if a failure happens at the responding role, the responding role will send an exception signal to the requesting role, and both parties will exit the current transaction. If a failure happens at the requesting role, the requesting role will exit the current transaction and in a separate transaction notify the responding role about the failure. This way the flow of control within a transaction is always unambiguous and finite. 6.6.1 Timeouts Since all business transactions must have a distinct time boundary, there are time-out parameters associated with the response, and each of the acknowledgement signals. If the time-out occurs before the corresponding response or signal arrives, the transaction is null and void. Here are the time-out parameters relative to the three response types: ebxml Business Process Specification Schema Page 42 of 136

1453 Response required Parameter Name Meaning of timeout Receipt acknowledgement timetoacknowledgereceipt The time a responding role has to acknowledge receipt of a business document. Acceptance Acknowledgement (Non-substantive) timetoacknowledgeacceptance The time a responding role has to nonsubstantively acknowledge business acceptance of a business document. Substantive Response TimeToPerform The time a responding role has to substantively acknowledge business acceptance of a business document. 1454 1455 1456 1457 1458 1459 1460 1461 1462 1463 1464 1465 A time-out parameter must be specified whenever a requesting partner expects one or more responses to a business document request. A requesting partner must not remain in an infinite wait state. The time-out value for each of the time-out parameters is absolute i.e. not relative to each other. All timers start when the initial requesting business document is sent. The timer values must comply with the well-formedness rules for timer values. A BSI needs to comply with the above parameters to detect the appropriate time outs. To preserve the atomic semantics of the Business Transaction, the requesting and responding roles take different action based on time outs. ebxml Business Process Specification Schema Page 43 of 136

1466 1467 1468 1469 1470 1471 1472 1473 1474 1475 1476 1477 1478 1479 1480 1481 1482 1483 1484 1485 1486 1487 1488 1489 1490 1491 1492 1493 1494 1495 1496 1497 1498 1499 1500 1501 1502 1503 1504 1505 1506 1507 1508 6.6.2 Exceptions A responding partner simply terminates if a timeout is thrown. This prevents responding business transactions from hanging indefinitely. A requesting partner terminates if a timeout is thrown and then sends a notification of failure to the responder as part of a separate transaction. When the time to perform an activity equals the time to acknowledge receipt or the time to acknowledge business acceptance then the highest priority time out exception must be used when the originator provides a reason for revoking their original business document offer. The time to perform exception is lower priority than both the time to acknowledge receipt and the time to acknowledge business acceptance. Under all normal circumstances the response message and/or the timeouts determine the success or failure of a business transaction. However the business processing of the transaction can go wrong at either the responding or the requesting role. 6.6.2.1 ControlException A ControlException signals an error condition in the management of a business transaction. This business signal is asynchronously returned to the initiating activity that originated the request. This exception must terminate the business transaction. These errors deal with the mechanisms of message exchange such as verification, validation, authentication and authorization and will occur up to message acceptance. Typically the rules and constraints applied to the message will have only dealt with structure, syntax and message element values. 6.6.2.2 Business Protocol Exceptions A Business Protocol Exception (or ProcessException) signals an error condition in a business activity. This business signal is asynchronously returned to the initiating role that originated the request. This exception must terminate the business transaction. These errors deal with the mechanisms that process the business transaction and will occur after message verification and validation. Typically the rules and constraints applied to the message will deal with the semantics of message elements and the validity of the request itself.the content is not valid with respect to a responding role s business rules. This type of exception is usually generated after an AcceptanceAcknowledgement has been returned. A business protocol exception terminates the business transaction. The following are business protocol exceptions. Negative acknowledgement of receipt. The structure/schema of a message is invalid. ebxml Business Process Specification Schema Page 44 of 136

1509 1510 1511 1512 1513 1514 1515 1516 1517 1518 1519 1520 1521 1522 1523 1524 1525 1526 1527 1528 1529 1530 1531 1532 1533 1534 1535 1536 1537 1538 1539 1540 1541 1542 1543 1544 1545 1546 1547 1548 1549 1550 1551 Negative acknowledgement of acceptance. The business rules are violated. Performance exceptions. The requested business action cannot be performed. Sequence exceptions. The order or type of a business document or business signal is incorrect. Syntax exceptions. There is invalid punctuation, vocabulary or grammar in the business document or business signal. Authorization exceptions. Roles are not authorized to participate in the business transaction. Business process control exceptions. Business documents are not signed for non-repudiation when required. A Business Transaction is defined in very atomic and deterministic terms. It always is initiated by the requesting role, and will always conclude at the requesting role. Upon receipt of the required response and/or signals, or time-out of same, the requesting role can unambiguously determine the success or failure of the Business Transaction. To preserve this semantics, control failures and business failures are treated differently by the requesting and responding roles as follows: A responding role that encounters a business protocol exception signals the exception back to the requesting role and then terminates the business transaction. If any business exceptions (includes negative receipt and acceptance acknowledgements) are signaled then the business transaction must terminate. A requesting role that encounters a business protocol exception terminates the transaction but does NOT send a business exception signal to the responding role. Rather, the requesting role then sends as a separate Business Transaction a notification revoking the offending business document request. This new transaction may be defined as a continuation of the current Binary Collaboration, or it may start a new Binary Collaboration specifically defined to handle this notification of failure. A BSI needs to comply specifically with the following parameters to produce the associated special exceptions. The requesting and responding roles take different action as per below. IsAuthorizationRequired If a partner role needs authorization to request a business action or to respond to a business action then the sending partner role must sign the business document exchanged and the receiving partner role must validate this business control and approve the authorizer. A responding partner must signal an authorization exception if the requesting partner role is not authorized to perform the business activity. A sending partner must send ebxml Business Process Specification Schema Page 45 of 136

1552 1553 1554 1555 1556 1557 1558 1559 1560 1561 1562 1563 1564 1565 1566 1567 1568 1569 1570 1571 1572 1573 1574 1575 1576 1577 1578 1579 1580 1581 1582 1583 1584 1585 1586 1587 1588 1589 1590 1591 1592 notification of failed authorization if a requesting partner is not authorized to perform the responding business activity. IsNonRepudiationRequired If non-repudiation of origin and content is required then the business activity must store the business document in its original form for the duration mutually agreed to in a trading partner agreement. A responding partner must signal a business control exception if the sending partner role has not properly delivered their business document. A requesting partner must send notification of failed business control if a responding partner has not properly delivered their business document. isnonrepudiationofreceiptrequired. Both partners agree to mutually verify receipt of a requesting business document and that the receipt must be non-repudiatable. A requesting partner must send notification of failed business control (possibly revoking a contractual offer) if a responding partner has not properly delivered their business document. For a further discussion of nonrepudiation of receipt, see also the ebxml E-Commerce and Simple Negotiation Patterns. Non-repudiation of receipt provides the data for the following audit controls. Verify responding role identity (authenticate) Verify the identity of the responding role (individual or organization) that received the requesting business document. Verify content integrity Verify the integrity of the original content of the business document request. ispositiveresponse An expression whose evaluation results in TRUE or FALSE. If TRUE this DocumentEnvelope is intended as a positive response to the request. The value for this parameter supplied for a DocumentEnvelope is an assertion by the sender of the DocumentEnvelope regarding its intent for the transaction to which it relates, but does not bind the recipient, or override the computation of transactional success or failure using the transaction's guard expressions. If a requesting role, upon evaluation of these expressions, determines a failure, then the requesting role will roll back the Business Transaction and send a notification of failure. ebxml Business Process Specification Schema Page 46 of 136

1593 1594 1595 1596 1597 1598 1599 1600 1601 1602 1603 1604 1605 1606 1607 1608 1609 1610 1611 1612 1613 1614 1615 1616 1617 1618 1619 1620 1621 1622 1623 1624 1625 1626 1627 1628 1629 6.7 Runtime Collaboration Semantics The ebxml collaboration semantics contain a number of relationships between multiparty collaborations and binary collaborations, between recursive layers of binary collaborations, and choreographies among transactions in binary collaborations. It is anticipated that over time BSI software will evolve to the point of monitoring and managing the state of a collaboration, similar to the way a BSI today is expected to manage the state of a transaction. For the immediate future, such capabilities are not expected and not required. 6.8 Where the ebxml Business Process Specification Schema May Be Implemented The ebxml Business Process Specification Schema should be used wherever software is being specified to perform a role in an ebxml business collaboration. Specifically, the ebxml Business Process Specification Schema is intended to provide the business process and document specification for the formation of ebxml trading partner Collaboration Protocol Profiles and Agreements. However, the ebxml Business Process Specification Schema may be used to specify any electronic commerce collaboration. It may also be used for noncommerce collaborations, for instance in defining transactional collaborations among non-profit organizations or internally in enterprises. 7 UML Element Specification In the following we will review all the specification elements in the UML version of the ebxml Business Process Specification Schema, grouped as follows: Business Collaborations o Multiparty o Binary Business Transactions Document flow Choreography 7.1 Business Collaborations 7.1.1 MultiPartyCollaboration A Multiparty Collaboration is a synthesis of Binary Collaborations. A Multiparty Collaboration consists of a number of Business Partner Roles each playing roles in binary collaborations with each other. ebxml Business Process Specification Schema Page 47 of 136

1630 1631 1632 1633 1634 Tagged Values: name. Associations: partners Defines the name of the MultiPartyCollaboration A multiparty collaboration has two or more BusinessPartnerRoles 1635 1636 1637 1638 1639 1640 1641 1642 1643 7.1.2 BusinessPartnerRole Wellformedness Rules: All multiparty collaborations must be synthesized from binary collaborations A BusinessPartnerRole is the role played by a business partner in a MultiPartyCollaboration. A BusinessPartnerRole performs at most one Authorized Role in each of the Binary Collaborations that make up the Multiparty Collaboration. 1644 1645 1646 1647 1648 1649 1650 1651 1652 1653 1654 1655 Tagged Values: name. Associations: performers. transitions collaboration Defines the name of the role played by partner in the overall multiparty business collaboration, e.g. customer or supplier. The Authorized Roles performed by a partner in the binary business collaboration. The transitions (managed by this BusinessPartnerRole) between activities across binary collaborations The Business Partner Role participates in one multi party collaboration 1656 1657 1658 1659 1660 1661 1662 1663 7.1.3 Performs Wellformedness Rules: A partner must not perform both roles in a given business activity. Performs is an explicit modeling of the relationship between a BusinessPartnerRole and the Roles it plays. This specifies the use of an Authorized Role within a multiparty collaboration. 1664 1665 1666 Tagged Values: NONE ebxml Business Process Specification Schema Page 48 of 136

1667 1668 1669 1670 1671 1672 1673 1674 1675 1676 1677 1678 1679 1680 1681 1682 1683 7.1.4 AuthorizedRole Associations: performedby An instance of Performs is performed by only one BusinessPartnerRole authorizedrole The AuthorizedRole that will be performed by the Business PartnerRole Wellformedness Rules: For every Performs performing an AuthorizedRole there must be a Performs that performs the opposing AuthorizedRole, otherwise the MultiParty Collaboration is not complete. An Authorized Role is a role that is authorized to send the request or response, e.g. the buyer is authorized to send the request for purchase order, the seller is authorized to send the acceptance of purchase order. 1684 1685 1686 1687 1688 1689 1690 1691 1692 1693 1694 1695 1696 1697 1698 1699 Tagged Values: name isinitiator Associations: performers from to collaboration Defines the name of the AuthorizedRole uniquely within the Binary Collaboration Boolean, determining whether this authorized role is the initiator of its associated binary collaboration An AuthorizedRole may be used by one or more performers, i.e. Business Partner Roles in a multiparty collaboration An AuthorizedRole may be the initiator in a business activity An AuthorizedRole may be the responder in a business activity An AuthorizedRole may be in only one BinaryCollaboration 1700 1701 1702 1703 1704 1705 Wellformedness Rules: An AuthorizedRole may not be both the requestor and the responder in a business transaction An AuthorizedRole may not be both the initiator and the responder in a binary business collaboration ebxml Business Process Specification Schema Page 49 of 136

1706 1707 1708 1709 1710 1711 1712 1713 1714 1715 1716 1717 1718 1719 1720 1721 1722 1723 1724 1725 1726 1727 1728 1729 1730 1731 1732 1733 1734 1735 7.1.5 BinaryCollaboration A Binary Collaboration defines a protocol of interaction between two authorized roles. A Binary Collaboration is a choreographed set of states among collaboration roles. The activities of performing business transactions or other collaborations are a kind of state. A Binary Collaboration choreographs one or more business transaction activities between two roles. A Binary Collaboration is not an atomic transaction and should not be used in cases where Business Transaction rollback is required. Tagged Values: name Defines the name of the BinaryCollaboration timetoperform The period of time, starting upon initiation of the first activity, within which this entire collaboration must conclude. precondition A description of a state external to this collaboration that is required before this collaboration can commence. postcondition A description of a state that does not exist before the execution of this collaboration but will exist as a result of the execution of this collaboration. beginswhen A description of an event external to the collaboration that normally causes this collaboration to commence. endswhen A description of an event external to this collaboration that normally causes this collaboration to conclude. pattern The optional reference to a pattern that this binary collaboration is based on 1736 1737 1738 1739 1740 1741 1742 1743 1744 1745 1746 1747 Associations: role states usedby transitions A binary collaboration consists of two authorized roles. One must be designated the Initiating Role, and one the Responding Role. A binary collaboration consists of one or more states, some of which are static, and some of which are action states A binary collaboration may be used within another binary collaboration via a collaboration activity The transitions between activities in this binary collaboration ebxml Business Process Specification Schema Page 50 of 136

1748 1749 1750 1751 1752 1753 1754 1755 1756 1757 1758 1759 1760 7.1.6 BusinessActivity Wellformedness Rules: NONE A business activity is an action state within a binary collaboration. It is the super type for BusinessTransactionActivity and CollaborationActivity, specifying the activity of performing a transaction or another binary collaboration respectively. Supertype of: BusinessTransactionActivity, CollaborationActivity Subtype of: BusinessState 1761 1762 1763 1764 1765 1766 1767 1768 1769 1770 1771 1772 Tagged Values: name Associations: from to Defines the name of the activity uniquely within the binary collaboration This must match one of the AuthorizedRoles in the parent binary collaboration and will become the initiator in the BinaryCollaboration performed by this activity This must match one of the AuthorizedRoles in the parent binary collaboration and will become the responder in the BinaryCollaboration performed by this activity 1773 1774 1775 1776 1777 1778 1779 1780 1781 1782 1783 1784 Wellformedness Rules: NONE 7.1.7 BusinessTransactionActivity A business transaction activity defines the use of a business transaction within a binary collaboration. A business transaction activity is a business activity that executes a specified business transaction. More than one instance of the same business transaction activity can be open at one time if the isconcurrent property is true. Subtype of: BusinessActivity ebxml Business Process Specification Schema Page 51 of 136

1785 1786 1787 1788 1789 1790 1791 1792 1793 1794 1795 1796 1797 1798 Tagged Values: timetoperform The period of time, starting upon the sending of the request, within which both partners agree to conclude the business transaction executed by this Business Transaction Activity. isconcurrent. If the BusinessTransactionActivity is concurrent then more than one instance of the associated BusinessTransaction can be performed as part of the execution of this BusinesTransactionActivity islegallybinding Defines whether the Business Transaction performed by this activity is intended by the trading parties to be binding. Default value is True. 1799 1800 1801 Associations: uses. The business transaction activity performs (uses) exactly one business transaction. 1802 1803 1804 1805 1806 1807 1808 1809 1810 1811 Wellformedness Rules: NONE 7.1.8 CollaborationActivity A collaboration activity is the activity of performing a binary collaboration within another binary collaboration. Subtype of: BusinessActivity Tagged Values: NONE (other than inherited) 1812 1813 1814 Associations: uses A collaboration activity uses exactly one binary collaboration 1815 1816 1817 1818 1819 1820 Wellformedness Rules: 7.2 Business Transactions A binary collaboration may not re-use itself ebxml Business Process Specification Schema Page 52 of 136

1821 1822 1823 1824 1825 1826 1827 1828 1829 1830 1831 1832 1833 1834 1835 1836 1837 1838 1839 1840 1841 1842 1843 1844 1845 1846 1847 1848 7.2.1 BusinessTransaction A business transaction is a set of business information and business signal exchanges amongst two commercial partners that must occur in an agreed format, sequence and time period. If any of the agreements are violated then the transaction is terminated and all business information and business signal exchanges must be discarded. Business Transactions can be formal as in the formation of on-line offer/acceptance commercial contracts and informal as in the distribution of product announcements. Tagged Values: name Defines the name of the Business Transaction. isguaranteeddeliveryrequired. Both partners must agree to use a transport that guarantees delivery precondition A description of a state external to this transaction that is required before this transaction can commence. postcondition A description of a state that does not exist before the execution of this transaction but will exist as a result of the execution of this transaction. beginswhen A description of an event external to the transaction that normally causes this transaction to commence. endswhen A description of an event external to this transaction that normally causes this transaction to conclude. pattern The optional reference to a pattern that this transaction is based on. 1849 1850 1851 1852 1853 1854 1855 Associations: activities requester responder A BusinessTransaction can be performed by many BusinessTransactionActivites A BusinessTransaction has exactly one RequestingBusinessActivity A BusinessTransaction has exactly one RespondingBusinessActivity 1856 1857 1858 1859 Wellformedness Rules: NONE ebxml Business Process Specification Schema Page 53 of 136

1860 1861 1862 1863 1864 1865 1866 1867 1868 1869 1870 1871 1872 1873 1874 1875 1876 1877 1878 1879 1880 1881 1882 1883 1884 1885 1886 1887 1888 1889 1890 1891 1892 1893 1894 1895 1896 1897 1898 1899 1900 1901 7.2.2 Business Action A Business Action is an abstract super class. Business Action, is the holder of attributes that are common to both Requesting Business Activity and Responding Business Activity. Supertype of: RequestingBusinessActivity, RespondringBusinessActivity Tagged Values: name Defines the name of the RequestingBusinessTransaction or RespondingBusinessTransaction depending on the subtype IsAuthorizationRequired Receiving party must validate identity of originator against a list of authorized originators. This parameter is specified on the sending side. (See also section on action security) IsNonRepudiationRequired Receiving party must check that a requesting document is not garbled (unreadable, unintelligible) before sending acknowledgement of receipt. This parameter is specified on the sending side. (See also section on core transaction semantics) isnonrepudiationofreceiptrequired. Requires the receiving party to return a signed receipt, and the original sender to save copy of the receipt. This parameter is specified on the sending side. (See also section on nonrepuditation) timetoacknowledgereceipt The time a receiving role has to acknowledge receipt of a business document. This parameter is specified on the sending side. (See also section on core transaction semantics) isintelligiblecheckrequired Receiving party must check that a requesting document is not garbled (unreadable, unintelligible) before sending acknowledgement of receipt. This parameter is specified on the sending side. (See also section on core transaction semantics) Associations: NONE Wellformedness Rules: NONE ebxml Business Process Specification Schema Page 54 of 136

1902 1903 1904 1905 1906 1907 1908 1909 1910 1911 1912 1913 1914 1915 1916 1917 1918 1919 1920 1921 1922 1923 1924 1925 1926 1927 1928 1929 1930 1931 1932 1933 1934 1935 1936 1937 7.2.3 RequestingBusinessActivity A RequestingBusinessActivity is a Business Action that is performed by the requesting role within a Business Transaction. It specifies the Document Envelope which will carry the request. Subtype of: BusinessAction Tagged Values: timetoacknowledgeacceptance The time a responding role has to non-substantively acknowledge business acceptance of a business document. This parameter is specified on the requesting side. (See also section on core transaction semantics) Associations: transaction A requesting activity is performed in exactly one business transaction documentenvelope A requesting activity sends exactly one Document Envelope Wellformedness Rules: NONE 7.2.4 RespondingBusinessActivity A RespondingBusinessActivity is a Business Action that is performed by the responding role within a Business Transaction. It specifies the Document Envelope which will carry the response. There may be multiple possible response Document Envelopes defined, but only one of them will be sent during an actual transaction instance. Subtype of: BusinessAction Tagged Values: NONE, except as inherited from Business Action Associations: transaction A responding activity is performed in exactly one business transaction ebxml Business Process Specification Schema Page 55 of 136

1938 1939 1940 1941 1942 1943 1944 1945 1946 1947 1948 1949 1950 1951 1952 1953 1954 1955 1956 1957 1958 1959 1960 1961 1962 1963 1964 1965 1966 1967 1968 1969 1970 1971 1972 1973 1974 1975 1976 7.3 Document flow DocumentEnvelope A responding activity may specify zero or more but sends at most one Document Envelope Wellformedness Rules: NONE 7.3.1 Document Security DocumentSecurity is an abstract super class holding the security related attributes for DocumentEnvelope and Attachment. Supertype of: DocumentEnvelope and Attachment Tagged Values: IsAuthenticated There is a digital certificate associated with the document entity. This provides proof of the signer s identity. (See also section on Document Security) IsConfidential The information entity is encrypted so that unauthorized parties cannot view the information. (See also section on Document Security) istamperproof The information entity has an encrypted message digest that can be used to check if the message has been tampered with. This requires a digital signature (sender s digital certificate and encrypted message digest) associated with the document entity. (See also section on Document Security) Associations: NONE Wellformedness Rules: NONE 7.3.2 Document Envelope A Document Envelope is what conveys business information between the two roles in a business transaction. One Document Envelope conveys the request from the requesting role to the responding role, and another Document Envelope conveys the ebxml Business Process Specification Schema Page 56 of 136

1977 1978 1979 1980 1981 1982 1983 1984 1985 1986 1987 1988 1989 1990 1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 response (if any) from the responding role back to the requesting role. Subtype of: DocumentSecurity Tagged Values: ispositiveresponse TRUE or FALSE. If TRUE this DocumentEnvelope is intended as a positive response to the request. This parameter is only relevant on the response envelope. Its value does not bind the recipient, or override the computation of transactional success or failure using the transaction's guard expressions. Associations: requesting This is a reference to the requesting activity associated with this DocumentEnvelope. This requesting activity may be the sender, or the receiver depending on whether the DocumentEnvelope represents a request or a response. responding This is a reference to the requesting activity associated with this DocumentEnvelope. This responding activity may be the sender, or the receiver depending on whether the DocumentEnvelope represents a request or a response. BusinessDocument This identifies the primary Business Document in the envelope. A Document Envelope contains exactly one primary Business Document. attachment A Document Envelope contains an optional set of attachments related to the primary document Wellformedness Rules: A Document Envelope is associated with exactly one requesting and one responding activity. IsPositiveResponse is not a relevant parameter on a DocumentEnvelope sent by a requesting activity.. ebxml Business Process Specification Schema Page 57 of 136

2019 2020 2021 2022 2023 2024 2025 2026 2027 2028 2029 2030 2031 2032 2033 2034 2035 2036 2037 2038 2039 2040 2041 2042 7.3.3 BusinessDocument 7.3.4 Attachment BusinessDocument is a generic name of a document. Tagged Values: name Defines the generic name of the Business Document as it is known within this Business Process Specification conditionexpression A Business Document may have one Condition Expression. This determines whether this is a valid business document for its envelope Associations: documentenvelope A Business Document can be in multiple Document Envelopes attachment A Business Document can serve to specify the type of many attachments Wellformedness Rules: NONE Attachment is an optional attachment to a BusinessDocument in a Document Envelope Subtype of: DocumentSecurity 2043 2044 2045 2046 2047 2048 2049 Tagged Values: name mimetype specification version Defines the name of the attachment Defines the valid MIME (Multipurpose Internet Mail Extensions) type of this Attachment A reference to an external source of description of this attachment. The version of the Attachment 2050 2051 2052 2053 2054 Associations: documentenvelope An Attachment is in exactly one Document Envelope businessdocument An Attachment can be defined by a BusinessDocument. If it is not of a defined ebxml Business Process Specification Schema Page 58 of 136

2055 2056 2057 2058 2059 2060 2061 2062 2063 2064 2065 2066 2067 2068 2069 2070 2071 2072 2073 Wellformedness Rules: NONE 7.4 Choreography within Collaborations. 7.4.1 BusinessState Business Document, the mime type and spec will be the only indication of its type. A business state is any state that a binary collaboration can be in. Start and CompletionState are a snapshot right before or right after an activity, BusinessActivity is an action states that denote the state of being in an activity. Fork and Join reflect the activity of forking to multiple activities or joining back from them. Supertype of: Start, CompletionState, Fork, Join, BusinessActivity Tagged Values: none 2074 2075 2076 2077 2078 Associations: collaboration entering exiting A business state belongs to only one binary collaboration A transition that reflects entry into this state A transition that reflects exiting from this state 2079 2080 2081 2082 2083 2084 2085 2086 7.4.2 Transition Wellformedness Rules: NONE A transition is a transition between two business states in a binary collaboration. Choreography is expressed as transitions between business states 2087 2088 2089 Tagged Values: oninitiation This specifies this is a nested BusinessTransactionActivity and that upon ebxml Business Process Specification Schema Page 59 of 136

2090 2091 2092 2093 2094 2095 2096 2097 2098 2099 receipt of the request in the associated transaction a second activity is performed before returning to the transaction to send the response back to the original requestor. conditionguard A reference to the status of the previous transaction. A fixed value of Success, BusinessFailure, TechnicalFailure, or AnyFailure conditionexpression A transition may have one Condition Expression. For a transition, this determines whether this transition should happen or not. 2100 2101 2102 Associations: in out The business state this transition is entering The business state this transition is exiting 2103 2104 2105 2106 2107 2108 2109 2110 2111 2112 2113 2114 2115 7.4.3 Start Wellformedness Rules: A transition cannot enter and exit the same state The starting state for a Binary Collaboration. A Binary Collaboration should have at least one starting activity. If none defined, then all activities are considered allowable entry points. Subtype of: BusinessState Tagged Values: NONE Associations: NONE 2116 2117 2118 2119 2120 2121 2122 2123 2124 7.4.4 CompletionState Wellformedness Rules: NONE The ending state of an binary collaboration, sub classed by success and failure Supertype of: Subtype of: Success, Failure BusinessState ebxml Business Process Specification Schema Page 60 of 136

2125 2126 2127 2128 2129 2130 2131 2132 2133 2134 2135 2136 2137 2138 2139 2140 2141 2142 2143 2144 2145 2146 2147 2148 2149 2150 2151 2152 2153 2154 2155 2156 2157 7.4.5 Success 7.4.6 Failure Tagged Values: NONE Associations: NONE Wellformedness Rules: NONE Defines the successful conclusion of a binary collaboration as a transition from an activity. Subtype of: CompletionState Tagged Values: conditionexpression A success state may have one Condition Expression for the transition. This determines whether this transition should happen or not. Associations: NONE, except as inherited Wellformedness Rules: Every activity Binary Collaboration should have at least one success A subtype of CompletionState which defines the unsuccessful conclusion of a binary collaboration as a transition from an activity. Subtype of: CompletionState Tagged Values: conditionexpression A failure state may have one Condition Expression for the transition. This determines whether this transition should happen or not. Associations: NONE, except as inherited ebxml Business Process Specification Schema Page 61 of 136

2158 2159 2160 2161 2162 2163 2164 2165 7.4.7 Fork Wellformedness Rules: Every Binary Collaboration should have at least one failure A Fork is a state with one inbound transition and multiple outbound transitions. All activities pointed to by the outbound transitions are assumed to happen in parallel. Subtype of: BusinessState 2166 2167 2168 2169 Tagged Values: Name Associations: None Defines the name of the Fork state 2170 2171 2172 2173 2174 2175 2176 2177 2178 7.4.8 Join Wellformedness Rules: None A business state where an activity is waiting for the completion of one or more other activities. Defines the point where previously forked activities join up again. Subtype of: BusinessState 2179 2180 2181 2182 2183 2184 2185 2186 Tagged Values: Name waitforall Associations: None Defines the name of the Join state Boolean value indicating if this Join state should wait for all incoming transitions to complete. If TRUE, wait for all, if False proceed on first incoming transition. 2187 2188 2189 2190 2191 Wellformedness Rules: None ebxml Business Process Specification Schema Page 62 of 136

2192 2193 2194 2195 2196 2197 2198 2199 2200 2201 2202 2203 2204 2205 2206 2207 2208 2209 2210 2211 2212 2213 2214 2215 2216 2217 2218 2219 2220 2221 2222 2223 2224 2225 2226 2227 2228 2229 7.5 Definition and Scope The ebxml Business Process Specification Schema should be used wherever software is being specified to perform a role in an ebxml binary collaboration. Specifically, the ebxml Business Process Specification Schema is intended to provide the business process and document specification for the formation of a trading partner Collaboration Protocol Profile and Agreement. A set of specification rules have been established to properly constrain the expression of a business process and information model in a way that can be directly incorporated into a trading partner Collaboration Protocol Profile and Agreement. 7.6 Collaboration and transaction well-formedness rules The following rules should be used in addition to standard parsing to properly constrain the values of the attributes of the elements in an ebxml Business Process Specification. Business Transaction [0] If non-repudiation is required then the input or returned business document must be a tamper-proofed entity. [1] If authorization is required then the input business document and business signal must be an authenticated or a tamper proofed secure entity. [2] The time to acknowledge receipt must be less than the time to acknowledge acceptance if both properties have values. timetoacknowledgereceipt < timetoacknowledgeacceptance [3] If the time to acknowledge acceptance is null then the time to perform an activity must either be equal to or greater than the time to acknowledge receipt. [4] The time to perform a transaction cannot be null if either the time to acknowledge receipt or the time to acknowledge acceptance is not null. [5] If non-repudiation of receipt is required then the time to acknowledge receipt cannot be null. [6] The time to acknowledge receipt, time to acknowledge acceptance and time to perform cannot all be zero. [7] If non-repudiation is required at the requesting business activity, then there must be a responding business document. RequestingBusinessActivity [8] There must be one input transition whose source state vertex is an initial pseudo state. ebxml Business Process Specification Schema Page 63 of 136

2230 2231 2232 2233 2234 2235 2236 2237 2238 2239 2240 2241 2242 2243 2244 2245 2246 2247 2248 2249 2250 2251 2252 [9] There must be one output transition whose target state vertex is a final state specifying the state of the machine when the activity is successfully performed. [10] There must be one output transition whose target state vertex is a final state specifying the state of the machine when the activity is NOT successfully performed due to a process control exception. [11] There must be one output transition whose target state vertex is a final state specifying the state of the machine when the activity is NOT successfully performed due to a business process exception. [12] There must be one output document flow from a requesting business activity that in turn is the input to a responding business activity. [13] There must be zero or one output document flow from a responding business activity that in turn is the input to the requesting business activity. RespondingBusinessActivity [14] There must be one input transition from a document flow that in turn has one input transition from a requesting business activity. [15] There must be zero or one output transition to an document flow that in turn has an output transition to a requesting business activity. Business Collaboration [16] A Business Partner Role cannot provide both the initiating and responding roles of the same business transaction activity. ebxml Business Process Specification Schema Page 64 of 136

2253 2254 2255 2256 2257 2258 2259 2260 2261 2262 2263 2264 2265 2266 2267 2268 2269 2270 2271 2272 2273 2274 2275 2276 2277 2278 2279 2280 2281 2282 2283 2284 2285 2286 2287 2288 2289 2290 2291 2292 2293 2294 8 ebxml Business Process Specification Schema (DTD) In this section we describe the DTD and XML Schema version of the Specification Schema. There are minimal differences between the DTD and the XML Schema, therefore the elements will only be described once, noting differences when needed. This discussion includes An example XML Business Process Specification listed in Appendix A. A listing of the DTD in Appendix B and the XML Schema in Appendix C A table listing all the elements with definitions and parent/child relationships A table listing all the attributes with definitions and parent element relationships A table listing all the elements, each with a cross reference to the corresponding class in the UML version of the specification schema Rules about namespaces and element references 8.1 Documentation for the DTD This section will document the DTD. The DTD has been derived from the UML model. The correlation between the UML classes and DTD elements will be shown separately later in this document. Overall Structure excluding attribute definitions: ProcessSpecification (Documentation*, SubstitutionSet*, (Include* BusinessDocument* ProcessSpecification* Package BinaryCollaboration BusinessTransaction MultiPartyCollaboration)*) Documentation() Include( Documentation* ) BusinessDocument (ConditionExpression Documentation)* ConditionExpression ( Documentation*) SubstitutionSet (DocumentSubstitution AttributeSubstitution Documentation)* DocumentSubstitution (ConditionExpression Documentation)* AttributeSubstitution (Documentation*) Package( Documentation*, (Package BinaryCollaboration BusinessTransaction MultiPartyCollaboration)* ) BinaryCollaboration( Documentation*, InitiatingRole, RespondingRole, (Documentation* Start Transition Success Failure BusinessTransactionActivity CollaborationActivity Fork Join)*) InitiatingRole (Documentation* ) RespondingRole( Documentation* ) Start( Documentation* ) Transition(ConditionExpression Documentation)* Success(ConditionExpression Documentation)* Failure(ConditionExpression Documentation)* ebxml Business Process Specification Schema Page 65 of 136

2295 2296 2297 2298 2299 2300 2301 2302 2303 2304 2305 2306 2307 2308 2309 2310 2311 2312 2313 2314 2315 2316 2317 2318 2319 2320 2321 2322 2323 2324 2325 2326 2327 2328 Fork( Documentation* ) Join( Documentation* ) BusinessTransactionActivity( Documentation* ) CollaborationActivity( Documentation* ) BusinessTransaction( Documentation*, RequestingBusinessActivity, RespondingBusinessActivity) RequestingBusinessActivity(Documentation*, DocumentEnvelope ) RespondingBusinessActivity(Documentation*, DocumentEnvelope* ) MultiPartyCollaboration( Documentation*, BusinessPartnerRole* ) BusinessPartnerRole(Documentation*, Performs*, Transition*) Performs( Documentation* ) Transition( Documentation* ) a. Attachment XML Element Name: Attachment DTD Declaration: <!ELEMENT Attachment (Documentation*) <!ATTLIST Attachment name CDATA #REQUIRED nameid ID #IMPLIED BusinessDocument CDATA #IMPLIED BusinessDocumentIDRef IDREF #IMPLIED mimetype CDATA #IMPLIED specification CDATA #IMPLIED version CDATA #IMPLIED isconfidential (true false) "false" istamperproof (true false) "false" isauthenticated (true false) "false" Definition: An optional attachment to a BusinessDocument in a DocumentEnvelope. Parent Elements: DocumentEnvelope ebxml Business Process Specification Schema Page 66 of 136

2328 2329 Attributes: Attribute Name Definition Default Value name Defines the name of the attachment. Required input nameid XML ID version of name Optional input businessdocument businessdocumentidr ef isauthenticated isconfidential istamperproof mimetype specification An Attachment s type can be defined by a BusinessDocument. If it is not of a defined Business Document, the mime type and spec will be the only indication of its type. The XML IDREF version of businessdocument There is a digital certificate associated with the document entity. This provides proof of the signer s identity. (See also section on Document Security) The information entity is encrypted so that unauthorized parties cannot view the information (See also section on Document Security) The information entity has an encrypted message digest that can be used to check if the message has been tampered with. This requires a digital signature (sender s digital certificate and encrypted message digest) associated with the document entity. (See also section on Document Security) Defines the valid MIME (Multipurpose Internet Mail Extensions) type of this Attachment A reference to an external source of description of this attachment. Required input Optional input false {true, false} false {true, false} false Valid values {true, false} Optional input. Example: 'application/pdf' Optional Input version The version of the Attachment Optional Input ebxml Business Process Specification Schema Page 67 of 136

2330 2331 2332 2333 2334 2335 2336 2337 2338 2339 2340 2341 2342 2343 2344 2345 2348 2349 2350 2351 2352 2353 2354 2355 2356 2357 2358 2359 2360 2361 2362 2363 2364 2365 2366 2367 2368 2369 2370 2371 b. AttributeSubstitution Element Name: AttributeSubstitution DTD Declaration: <!ELEMENT AttributeSubstitution (Documentation*) <!ATTLIST AttributeSubstitution attributename CDATA #IMPLED value CDATA #IMPLIED Definition: Attribute Substitution specifies that an attribute value should be used in place of some attribute value in an existing process specification. Parents: SubstitutionSet Attributes: Attribute Name attributena me value c. Binary Collaboration Definition The name of an attribute of any element within the scope of the substitution set. The value which shall replace the current value of the attribute. XML Element Name: BinaryCollaboration DTD Declaration: Default Value Required Input Required Input <!ELEMENT BinaryCollaboration (Documentation*, InitiatingRole, RespondingRole, (Documentation* Start Transition Success Failure BusinessTransactionActivity CollaborationActivity Fork Join)*) <!ATTLIST BinaryCollaboration name CDATA #REQUIRED nameid ID #IMPLIED pattern CDATA #IMPLIED beginswhen CDATA #IMPLIED endswhen CDATA #IMPLIED precondition CDATA #IMPLIED postcondition CDATA #IMPLIED timetoperform CDATA #IMPLIED Definition: A Binary Collaboration defines a protocol of interaction between two authorized roles. A Binary Collaboration is a choreographed set of states among collaboration roles. The activities of performing business transactions or other collaborations are a kind of state. ebxml Business Process Specification Schema Page 68 of 136

2372 2373 2374 2375 2376 2377 2378 2379 2380 A Binary Collaboration choreographs one or more business transaction activities between two roles. A Binary Collaboration is not an atomic transaction and should not be used in cases where Business Transaction rollback is required. Parents: Package Hierarchical Model: 2381 2382 2383 Attributes: Attribute Name Definition Default Value name Defines the name of the Binary Collaboration. Required Input. nameid The XML ID version of name Optional beginswhen endswhen pattern precondition A description of an event external to the collaboration that normally causes this collaboration to commence. A description of an event external to this collaboration that normally causes this collaboration to conclude. The optional reference to a pattern that this binary collaboration is based on.. In the XML Schema version the data type is xsd:anyuri A description of a state external to this collaboration that is required before this Optional Input. Optional Input. Optional Input. ebxml Business Process Specification Schema Page 69 of 136

collaboration can commence. 2384 2385 2386 2387 2388 2389 2390 2391 2392 2393 2394 2395 2396 2397 2398 2399 2400 2401 2402 2403 2404 2405 2406 postcondition timetoperform d. BusinessDocument Element Name: BusinessDocument DTD Declaration: A description of a state that does not exist before the execution of this collaboration but will exist as a result of the execution of this collaboration. The period of time, starting upon initiation of the first activity, within which this entire collaboration must conclude. <!ELEMENT BusinessDocument (ConditionExpression, Documentation*) <!ATTLIST BusinessDocument name CDATA #REQUIRED nameid ID #IMPLIED specificationlocation CDATA #IMPLIED specificationelement CDATA #IMPLIED Definition: BusinessDocument is a generic name of a document. Parents: Attachment Attributes: Attribute Name name Definition Defines the generic name of the Business Document as it is known within this Business Process Specification Optional Input.. Optional Input. Default Value Required Input nameid XML ID version of name Optional specificati onlocation specificati onelement e. Business Partner Role Element Name: BusinessPartnerRole Reference to an external source of the schema definition. In the XML Schema version the data type is xsd:anyuri Reference to the element within the schema definition that defines this document. Optional Optional ebxml Business Process Specification Schema Page 70 of 136

2407 2408 2409 2410 2411 2412 2413 2414 2415 2416 2417 2418 2419 2420 2421 DTD Declaration: <!ELEMENT BusinessPartnerRole (Documentation*, Performs*, Transition*) <!ATTLIST BusinessPartnerRole name CDATA #REQUIRED nameid ID #IMPLIED Definition: A BusinessPartnerRole is the role played by a business partner in a MultiPartyCollaboration. A BusinessPartnerRole performs at most one Authorized Role in each of the Binary Collaborations that make up the Multiparty Collaboration. Parents: MultiPartyCollaboration Hierarchical Model: 2422 2423 2424 2425 2426 2427 2428 2429 2430 2431 2432 2433 2434 2435 2436 2437 2438 2439 2440 2441 Attributes: Attribute Name Name Definition Defines the name of the role played by a partner in the overall multiparty business collaboration, e.g. customer or supplier. Default Value Required Input. nameid The XML ID version of name Optional f. Business Transaction Element Name: BusinessTransaction Content Model: <!ELEMENT BusinessTransaction (Documentation*, RequestingBusinessActivity, RespondingBusinessActivity) <!ATTLIST BusinessTransaction name CDATA #REQUIRED nameid ID #IMPLIED pattern CDATA #IMPLIED beginswhen CDATA #IMPLIED endswhen CDATA #IMPLIED isguaranteeddeliveryrequired (true false) false precondition CDATA #IMPLIED postcondition CDATA #IMPLIED Definition: ebxml Business Process Specification Schema Page 71 of 136

2442 2443 2444 2445 2446 2447 2448 2449 2450 2451 2452 2453 2454 2455 A business transaction is a set of business information and business signal exchanges amongst two commercial partners that must occur in an agreed format, sequence and time period. If any of the agreements are violated then the transaction is terminated and all business information and business signal exchanges must be discarded. Business Transactions can be formal as in the formation of on-line offer/acceptance commercial contracts and informal as in the distribution of product announcements. Parents: Package Hierarchical Model: 2456 2457 2458 2459 Attributes: Attribute Name Definition Default Value name nameid pattern beginswhen endswhen isguaranteeddeliveryrequir ed Defines the name of the Business Transaction. The XML ID version of name The optional reference to a pattern that this transaction is based on.in the XML Schema version the data type is xsd:anyuri A description of an event external to the transaction that normally causes this transaction to commence. A description of an event external to this transaction that normally causes this transaction to conclude. Both partners must agree to use a transport that guarantees delivery Required Input. Optional Optional Optional Input.. Optional Input. ebxml Business Process Specification Schema Page 72 of 136 false Valid Values:

2460 2461 2462 2463 2464 2465 2466 2467 2468 2469 2470 2471 2472 2473 2474 2475 2476 2477 2478 2479 2480 2481 2482 2483 2484 2485 precondition postcondition g. Business Transaction Activity Element Name: BusinessTransactionActivity Content Model: guarantees delivery A description of a state external to this transaction that is required before this transaction can commence. A description of a state that does not exist before the execution of this transaction but will exist as a result of the execution of this transaction. {true, false} Optional Input. Optional Input. <!ELEMENT BusinessTransactionActivity (Documentation*) <!ATTLIST BusinessTransactionActivity name CDATA #REQUIRED nameid ID #IMPLIED businesstransaction CDATA #REQUIRED businesstransactionidref IDREF #IMPLIED fromauthorizedrole CDATA #REQUIRED fromauthorizedroleidref IDREF #IMPLIED toauthorizedrole CDATA #REQUIRED toauthorizedroleidref IDREF #IMPLIED isconcurrent (true false) "false" islegallybinding (true false) "true" timetoperform CDATA #IMPLIED Definition: A business transaction activity defines the use of a business transaction within a binary collaboration. A business transaction activity is a business activity that executes a specified business transaction. More than one instance of the same business transaction activity can be open at one time if the isconcurrent property is true. Parents: BinaryCollaboration Attributes: Attribute Name Definition Default Value name Defines the name of the activity uniquely within the binary collaboration Required Input. nameid The XML ID version of name Optional Input businesstransaction A reference, by name to the Business Transaction performed by this Business Required Input. ebxml Business Process Specification Schema Page 73 of 136

Transaction Activity businesstransactionid Ref fromauthorizedrole fromauthorizedroleidr ef toauthorizedrole toauthorizedroleidref timetoperform islegallybinding The XML IDREF version of businesstransaction The name of the initiating role in Business Transaction Activity. This must match one of the AuthorizedRoles in the binary collaboration and will become the requestor in the BusinessTransaction performed by this activity The XML IDREF version of fromauthorizedrole The name of the responding role in Business Transaction Activity. This must match one of the AuthorizedRoles in the binary collaboration and will become the responder in the BusinessTransaction performed by this activity The XML IDREF version of toauthorizedrole The period of time, starting upon the sending of the request, within which both partners agree to conclude the business transaction executed by this Business Transaction Activity. Defines whether the Business Transaction performed by this activity is intended by the trading parties to be binding. Default value is True. Optional Input. Required Input. OptionalInput. Required Input. Optional Input. Optional Input. true Valid Values: {true, false} 2486 2487 2488 2489 isconcurrent h. Collaboration Activity Element Name: CollaborationActivity DTD Declaration: If the BusinessTransactionActivity is concurrent then more than one instance of the associated BusinessTransaction can be open the same time as part of the execution of this BusinesTransactionActivity false Valid Values: {true, false} ebxml Business Process Specification Schema Page 74 of 136

2490 2491 2492 2493 2494 2495 2496 2497 2498 2499 2500 2501 2502 2503 2504 2505 2506 <!ELEMENT CollaborationActivity (Documentation*) <!ATTLIST CollaborationActivity name CDATA #REQUIRED nameid ID #IMPLIED fromauthorizedrole CDATA #REQUIRED fromauthorizedroleidref CDATA #IMPLIED toauthorizedrole CDATA #REQUIRED toauthorizedroleidref CDATA #IMPLIED binarycollaboration CDATA #REQUIRED binarycollaborationidref CDATA #IMPLIED Definition: A collaboration activity is the activity of performing a binary collaboration within another binary collaboration. Parents: BinaryCollaboration Attributes: Attribute Name Definition Default Value Name fromauthorizedrole FromAuthorizedRoleIDR ef toauthorizedrole toauthorizedroleidref binarycollaboration BinaryCollaborationIDRe f Defines the name of the activity uniquely within the binary collaboration The name of the initiating role in the Collaboration Activity. This must match one of the AuthorizedRoles in the parent binary collaboration and will become the initiator in the BinaryCollaboration performed by this activity The XML IDREF version of fromauthorizedrole The name of the responding role in the Collaboration Activity. This must match one of the AuthorizedRoles in the parent binary collaboration and will become the responder in the BinaryCollaboration performed by this activity The XML IDREF version of toauthorizedrole A reference, by name, to the Binary Collaboration performed by this Collaboration Activity The XML IDREF version of binarycollaboration Required Input. Required Input OptionalInput. Required Input. Optional Input. Required Input. Optional Input. ebxml Business Process Specification Schema Page 75 of 136

2507 2508 2509 2510 2511 2512 2513 2514 2515 2516 2517 2518 2519 2520 2521 2522 2523 2524 2525 2526 2527 2528 2529 2530 2531 2532 2533 2534 2535 2536 2537 2538 2539 2540 i. Documentation Element Name: Documentation DTD Declaration: <!ELEMENT Documentation (#PCDATA) <!ATTLIST Documentation uri CDATA #IMPLIED Definition: Defines user documentation for any element. Must be the first element of its container. Documentation can be either inline PCDATA and/or a URI to where more complete documentation is to be found Parents: Attributes: AuthorizedRole BinaryCollaboration BusinessPartnerRole BusinessTransaction BusinessTransactionActivity CollaborationActivity DocumentEnvelope BusinessDocument ProcessSpecification MultiPartyCollaboration Package Performs RequestingBusinessActivity RespondingBusinessActivity Transition Attribute Name Definition Default Value uri j. DocumentEnvelope Element Name: DocumentEnvelope Content Model: Defines the URI (Uniform Resource Identifier) where external documentation is located. In the XML Schema version the data type is xsd:anyuri No Default Value. Valid URI is required. ebxml Business Process Specification Schema Page 76 of 136

2541 2542 2543 2544 2545 2546 2547 2548 2549 2550 2551 2552 2553 2554 2555 2556 2557 2558 2559 2560 2561 <!ELEMENT DocumentEnvelope (Documentation*, Attachment*) <!ATTLIST DocumentEnvelope businessdocument CDATA #REQUIRED businessdocumentidref IDREF #IMPLIED ispositiveresponse CDATA #IMPLIED isauthenticated (true false) "false" isconfidential (true false) "false" istamperproof (true false) "false" Definition: A DocumentEnvelope is what conveys business information between the two roles in a business transaction. One DocumentEnvelope conveys the request from the requesting role to the responding role, and another DocumentEnvelope conveys the response (if any) from the responding role back to the requesting role. Parents: RequestingBusinessActivity RespondingBusinessActivity Hierarchical Model: 2562 2563 2564 Attributes: Attribute Name Definition Default Value businessdocument businessdocument IDRef ispositiveresponse The name of the business document. The XML IDREF version of businessdocument TRUE or FALSE. If TRUE this DocumentEnvelope is intended as a positive response to the request. The value for this parameter supplied for a DocumentEnvelope is an assertion by the sender of the DocumentEnvelope regarding its intent for the transaction to which it relates, but does not bind the recipient, or override the computation of transactional success or failure using the transaction's guard expressions. In some situations Required Input. Optional Input. Optional Input. ebxml Business Process Specification Schema Page 77 of 136

2565 2566 2568 2570 2571 2572 2573 2574 2575 2576 2577 2578 2579 2580 2581 isauthenticated isconfidential istamperproof k. DocumentSubstitution Element Name: DocumentSubstitution DTD Declaration: this could be an XPath expression that interrogates the BusinessDocument in the envelope. IsPositiveResponse is only relevant for responses, and is ignored in requests. There is a digital certificate associated with the document entity. This provides proof of the signer s identity. (See also section on Document Security) The information entity is encrypted so that unauthorized parties cannot view the information. (See also section on Document Security) The information entity has an encrypted message digest that can be used to check if the message has been tampered with. This requires a digital signature (sender s digital certificate and encrypted message digest) associated with the document entity. (See also section on Document Security) <!ELEMENT BusinessDocument (Documentation*) <!ATTLIST DocumentSubstitution originalbusinessdocument CDATA #IMPLIED originalbusinessdocumentid IDREF #IMPLIED substitutebusinessdocument CDATA #IMPLIED substitutebusinessdocumentid IDREF #IMPLIED Definition: false Valid Values: {true, false} false Valid Values: {true, false} false Valid Values: {true, false} ebxml Business Process Specification Schema Page 78 of 136

2582 2583 2584 2585 2586 2587 2588 2589 2590 2591 2592 2593 2594 2595 2596 2597 2598 2599 2600 2601 2602 2603 2604 2605 DocumentSubstitution specifies a document that should be used in place of a document in an existing process specification. Parents: SubstitutionSet Attributes: l. Failure Attribute Name originalbu sinessdoc ument originalbu sinessdoc ument ID substitueb usinessdo cument substitueb usinessdo cumentid Element Name: Failure DTD Declaration: Definition The name of a business document within the scope of the substitution set. The ID of the business document. The document which shall replace the current document. The ID of the replacement document. Default Value Required Input Optional Required Input Optional <!ELEMENT Failure (ConditionExpression, Documentation*) <!ATTLIST Failure frombusinessstate CDATA #REQUIRED frombusinessstateidref IDREF #IMPLIED conditionguard (Success BusinessFailure TechnicalFailure AnyFailure) #IMPLIED Definition: Defines the unsuccessful conclusion of a binary collaboration as a transition from an activity. Parents: BinaryCollaboration Attributes: Attribute Name Definition Default Value frombusinessstate The name of the activity from which this indicates a transition to unsuccessful conclusion of the BusinessTransaction or BinaryCollaboration Required Input. ebxml Business Process Specification Schema Page 79 of 136

2606 2607 2608 2609 2610 2611 2612 2613 2614 2615 2616 2617 2618 2619 2620 2621 2622 2623 2624 2625 2626 2627 2628 2629 2630 2631 2632 2633 2634 2635 2636 m. Fork frombusinessstate IDRef conditionguard Element Name: Fork DTD Declaration: The XML IDREF version of frombusinessstate The condition that guards this transition <!ELEMENT Fork (Documentation*) <!ATTLIST Fork name CDATA #REQUIRED nameid ID #IMPLIED Definition: Optional Optional Valid Values: {Success, BusinessFailure, TechnicalFailure, AnyFailure} A Fork is a state with one inbound transition and multiple outbound transitions. All activities pointed to by the outbound transitions are assumed to happen in parallel. Parents: BinaryCollaboration Attributes: n. Include Attribute Name Definition Default Value name Defines the name of the Fork state Required Input nameid The XML ID version of name Optional Element Name: Include DTD Declaration: <!ELEMENT Include (Documentation*) <!ATTLIST Include name CDATA #REQUIRED version CDATA #REQUIRED uuid CDATA #REQUIRED uri CDATA #REQUIRED Definition: Includes another process specification document and merges that specification with the current specification. Any elements of the same name and in the same name scope must have exactly the same specification except that packages may have additional content. ebxml Business Process Specification Schema Page 80 of 136

2637 2638 2639 2640 2641 2642 2643 2644 2645 2646 2647 2648 2649 2650 2651 2652 2653 2654 2655 2656 2657 2658 2659 2660 2661 Documents are merged based on name scope. A name in an included package will be indistinguishable from a name in the base document. Parents: ProcessSpecification Hierarchical Model: Attributes: Attribute Name name Definition Defines the name of a model element. This name must be unique within the context of the model element and will be used to reference the element from other points in the model. Default Value Required uri Uniform Resource Indicator. In Required the XML Schema data type is xsd:anyuri uuid Universally unique identifier. Required version Version of the included specification. Required o. Initiating Role XML Element Name: InitiatingRole DTD Declaration: <!ELEMENT InitiatingRole (Documentation*) <!ATTLIST InitiatingRole name CDATA #REQUIRED nameid ID #IMPLIED Definition: An Initiating Role is a role that is authorized to send the first request, e.g. the buyer is authorized to send the request for purchase order. The Initiating Role initiates the binary collaboration. Typically this is the first role.. Parents: BinaryCollaboration Attributes: Attribute Name Definition Default Value Name Defines the name of the Initiating Role Required input. ebxml Business Process Specification Schema Page 81 of 136

2662 2663 2664 2665 2666 2667 2668 2669 2670 2671 2672 2673 2674 2675 2676 2677 2678 2679 2680 2681 2682 2683 2684 2685 2686 2687 2688 2689 2690 2691 p. Join nameid XML ID version of name Optional Element Name: Join DTD Declaration: <!ELEMENT Join (Documentation*) <!ATTLIST Join name CDATA #REQUIRED nameid ID #IMPLIED waitforall (true false) "true" Definition: A business state where an activity is waiting for the completion of one or more other activities. Defines the point where previously forked activities join up again. Parents: BinaryCollaboration Attributes: Attribute Name Definition Default Value name Defines the name of the Join state. Required Input nameid The XML ID version of name Optional waitforall q. MultiParty Collaboration Element Name: MultiPartyCollaboration DTD Declaration: Boolean value indicating if this Join state should wait for all incoming transitions to complete. If TRUE, wait for all, if False proceed on first incoming transition. true Valid Values: {true, false} <!ELEMENT MultiPartyCollaboration (Documentation*, BusinessPartnerRole+) <!ATTLIST MultiPartyCollaboration name CDATA #REQUIRED nameid ID #IMPLIED Definition: A Multiparty Collaboration is a synthesis of Binary Collaborations. A Multiparty Collaboration consists of a number of Business Partner Roles each playing roles in binary collaborations with each other. Parents: Package Hierarchical Model: ebxml Business Process Specification Schema Page 82 of 136

2692 2693 2694 2695 2696 2697 2698 2699 2700 2701 2702 2703 2704 2705 2706 2707 2708 2709 2710 2711 2712 Attributes: Attribute Name name r. Package Definition Defines the name of the MultiPartyCollaboration Default Value Required Input nameid The XML ID version of name Optional Input Element Name: Package DTD Declaration: <!ELEMENT Package (Documentation*, (Package BinaryCollaboration MultiPartyCollaboration BusinessTransaction)*) <!ATTLIST Package name CDATA #REQUIRED nameid ID #IMPLIED Definition: Defines a hierarchical name scope containing reusable elements. Parents: ProcessSpecification Package Hierarchical Model: 2713 2714 2715 Attributes: Attribute Name name Definition Defines the name of a model element. This name must be unique within the context of the model element and will be used to reference the element from other points in the Default Value Required Input ebxml Business Process Specification Schema Page 83 of 136

model. 2716 2717 2718 2719 2720 2721 2722 2723 2724 2725 2726 2727 2728 2729 2730 2731 2732 2733 2734 2735 2736 2737 2738 2739 2740 2741 2742 2743 s. Performs nameid XML ID version of name Optional Element Name: Performs DTD Declaration: <!ELEMENT Performs (Documentation*) <!ATTLIST Performs initiatingrole CDATA #REQUIRED initiatingroleidref IDREF #IMPLIED respondingrole CDATA #REQUIRED respondingroleidref IDREF #IMPLIED Definition: Performs is an explicit modeling of the relationship between a BusinessPartnerRole and the Roles it plays. This specifies the use of an Authorized Role within a multiparty collaboration. Parents: BusinessPartnerRole Attributes: Attribute Name Definition Default Value initiatingrole initiatingroleidref respondingrole respondingroleidre f t. ProcessSpecification Element Name: ProcessSpecification DTD Declaration: The InitiatingRole that will be performed by the Business PartnerRole, qualified with the name of the BinaryCollaboration The XML IDREF version of InitiatingRole The RespondingRole that will be performed by the Business PartnerRole, qualified with the name of the BinaryCollaboration The XML IDREF version of RespondingRole Required Input Optional Input Required Input Optional Input <!ELEMENT ProcessSpecification (Documentation*, SubstitutionSet*, (Include* BusinessDocument* ProcessSpecification* Package BinaryCollaboration BusinessTransaction MultiPartyCollaboration)*) ebxml Business Process Specification Schema Page 84 of 136

2744 2745 2746 2747 2748 2749 2750 2751 <!ATTLIST ProcessSpecification name ID #REQUIRED version CDATA #REQUIRED uuid CDATA #REQUIRED Definition: Root element of a process specification document that has a globally unique identity. Hierarchical Model: 2752 2753 2754 2755 2756 2757 2758 2759 2760 2761 2762 2763 2764 2765 2766 2767 Attributes: Attribute Name name Definition Defines the name of a model element. This name must be unique within the context of the model element and will be used to reference the element from other points in the model. It is defined as an XML ID. Default Value Required uuid Universally unique identifier. Required version Version of the specification. Required u. Requesting Business Activity Element Name: RequestingBusinessActivity DTD Declaration: <!ELEMENT RequestingBusinessActivity (Documentation*, DocumentEnvelope) <!ATTLIST RequestingBusinessActivity name CDATA #IMPLIED nameid ID #IMPLIED isauthorizationrequired (true false) false isintelligiblecheckrequired (true false) false isnonrepudiationreceiptrequired (true false) false isnonrepudiationrequired (true false) false ebxml Business Process Specification Schema Page 85 of 136

2768 2769 2770 2771 2772 2773 2774 2775 2776 timetoacknowledgeacceptance CDATA #IMPLIED timetoacknowledgereceipt CDATA #IMPLIED Definition: A RequestingBusinessActivity is a Business Action that is performed by the requesting role within a Business Transaction. It specifies the Document Envelope which will carry the request. Parents: BusinessTransaction ebxml Business Process Specification Schema Page 86 of 136

2776 Hierarchical Model: 2777 2778 Attributes: Attribute Name Definition Default Value name nameid isauthorizationrequired isintelligiblecheckrequired isnonrepudiationreceiptr equired isnonrepudiationrequired Defines the name of the RequestingBusinessTransa ction The XML ID version of name Receiving party must validate identity of originator against a list of authorized originators. This parameter is specified on the sending side. (See also section on action security) Receiving party must check that a requesting document is not garbled (unreadable, unintelligible) before sending acknowledgement of receipt This parameter is specified on the sending side. (See also section on core transaction semantics) Requires the receiving party to return a signed receipt, and the original sender to save copy of the receipt. This parameter is specified on the sending side. (See also section on nonrepuditation) Requires the sending parties to save copies of the transacted documents before sending them (See also section on nonrepuditation) Optional Input Optional Input false Valid Values: {true, false} false Valid Values: {true, false} false Valid Values: {true, false} false Valid Values: {true, false} ebxml Business Process Specification Schema Page 87 of 136

2779 2780 2781 2782 2783 2784 2785 2786 2787 2788 2789 2790 2791 2792 2793 2794 2795 2796 2797 2798 2799 2800 2801 2802 2803 timetoacknowledgeaccept ance timetoacknowledgereceip t v. Responding Business Activity Element Name: RespondingBusinessActivity DTD Declaration: The time a responding role has to nonsubstantively acknowledge business acceptance of a business document. This parameter is specified on the requesting side. (See also section on core transaction semantics) The time the receiving party has to acknowledge receipt of a business document. This parameter is specified on the sending side. (See also section on core transaction semantics) No default value. No default value. <!ELEMENT RespondingBusinessActivity (Documentation*, DocumentEnvelope*) <!ATTLIST RespondingBusinessActivity name CDATA #IMPLIED nameid ID #IMPLIED isauthorizationrequired (true false) false isintelligiblecheckrequired (true false) false isnonrepudiationreceiptrequired (true false) false isnonrepudiationrequired (true false) false timetoacknowledgereceipt CDATA #IMPLIED Definition: A RespondingBusinessActivity is a Business Action that is performed by the responding role within a Business Transaction. It specifies the Document Envelope which will carry the response. There may be multiple possible response Document Envelopes defined, but only one of them will be sent during an actual transaction instance. Parents: BusinessTransaction Hierarchical Model: ebxml Business Process Specification Schema Page 88 of 136

2804 2805 Attributes: Attribute Name Definition Default Value name nameid isauthorizationrequired isintelligiblecheckrequired isnonrepudiationreceiptr equired isnonrepudiationrequired timetoacknowledgereceip t Defines the name of the RespondingBusinessTrans action The XML ID version of name Receiving party must validate identity of originator against a list of authorized originators. This parameter is specified on the sending side. (See also section on action security) Receiving party must check that a requesting document is not garbled (unreadable, unintelligible) before sending acknowledgement of receipt This parameter is specified on the sending side. (See also section on core transaction semantics) Requires the receiving party to return a signed receipt, and the original sender to save copy of the receipt. This parameter is specified on the sending side. (See also section on nonrepuditation) Requires the sending parties to save copies of the transacted documents before sending them (See also section on nonrepuditation) The time the receiving party has to acknowledge receipt Optional Input Optional Input ebxml Business Process Specification Schema Page 89 of 136 false Valid Values: {true, false} false Valid Values: {true, false} false Valid Values: {true, false} false Valid Values: {true, false} No default value.

2806 2807 2808 2809 2810 2811 2812 2813 2814 2815 2816 2817 2818 2819 2820 2821 2822 2823 2824 2825 2826 2827 2828 2829 2830 2831 2832 2833 2834 2835 2836 2837 t w. Responding Role XML Element Name: RespondingRole DTD Declaration: of a business document. This parameter is specified on the sending side. (See also section on core transaction semantics) <!ELEMENT RespondingRole (Documentation*) <!ATTLIST RespondingRole name CDATA #REQUIRED nameid ID #IMPLIED Definition: value. A Responding Role is a role that is authorized to send the first response, e.g. the seller is authorized to send the acceptance of purchase order. This role is the responder in a binary collaboration.. Parents: BinaryCollaboration Attributes: x. Start Attribute Name Definition Default Value Name Defines the name of the Responding Role Required input. nameid XML ID version of name Optional Element Name: Start DTD Declaration: <!ELEMENT Start (Documentation*) <!ATTLIST Start tobusinessstate CDATA #REQUIRED tobusinessstateidref IDREF #IMPLIED Definition: The starting state for an Binary Collaboration. A Binary Collaboration should have at least one starting activity. If none defined, then all activities are considered allowable entry points. Parents: BinaryCollaboration ebxml Business Process Specification Schema Page 90 of 136

2838 2839 2840 2841 2842 2843 2844 2845 2846 2847 2848 2849 2850 2851 2852 2853 2854 2855 2856 2857 2858 2859 2860 2861 2862 2863 2864 2865 2866 2867 2868 Attributes: Attribute Name Definition Default Value tobusinessstate tobusinessstateidre f y. SubstitutionSet Element Name: SubstitutionSet DTD Declaration: The name of an activity which an allowable starting point for this for BinaryCollaboration The XML IDREF version of tobusinessstate Required Input Optional <!ELEMENT SubstitutionSet (DocumentSubstitution AttributeSubstitution, Documentation)* <!ATTLIST SubstitutionSet name CDATA #IMPLIED nameid ID #IMPLIED applytoscope CDATA #IMPLIED Definition: A Substitution Set is a container for one or more AttributeSubstitution and/or DocumentSubstitution elements. The entire SubstitutionSet specifies document or attribute values that should be used in place of some documents and attribute values in an existing process specification. Parents: ProcessSpecification Attributes: z. Success Attribute Name Definition Default Value name Name of the substitution set. Required Input nameid The ID of the substitution set. Required Input applytosc ope Element Name: Success DTD Declaration: Specifies the path to attributes or documents that are to be substituted for. Required Input <!ELEMENT Success (ConditionExpression, Documentation*) <!ATTLIST Success frombusinessstate CDATA #REQUIRED conditionguard (Success BusinessFailure ebxml Business Process Specification Schema Page 91 of 136

2869 2870 2871 2872 2873 2874 2875 2876 2877 2878 2879 2880 2881 2882 2883 2884 2885 2886 2887 2888 2889 2890 2891 Definition: TechnicalFailure AnyFailure) #IMPLIED Defines the successful conclusion of a binary collaboration as a transition from an activity. Parents: BinaryCollaboration Attributes: Attribute Name Definition Default Value frombusinessstate conditionguard aa. ConditionExpression Element Name: ConditionExpression DTD Declaration: The name of the activity from which this indicates a transition to successful conclusion of the BusinessTransaction or BinaryCollaboration The condition that guards this transition <!ELEMENT ConditionExpression (Documentation*) <!ATTLIST ConditionExpression Definition: expressionlanguage CDATA #IMPLIED expression CDATA #IMPLIED Required Input. Optional Valid Values: {Success, BusinessFailure, TechnicalFailure, AnyFailure} Condition Expression is an expression that can be evaluated to TRUE or FALSE. Parents: Attachment Attributes: Attribute Name expression Language expression Definition The language of the expression, e.g. Java. An expression whose evaluation results in TRUE or FALSE. For a transition, this determines whether this transition should happen or not. For a business document, this Default Value Required Input Optional ebxml Business Process Specification Schema Page 92 of 136

2892 2893 2894 2895 2896 2897 2898 2899 2900 2901 2902 2903 2904 2905 2906 2907 2908 2909 2910 2911 bb. Transition ELEMENT Name: Transition DTD Declaration: determines whether this is a valid business document for its envelope. The expression can refer to the name or content of the most recent DocumentEnvelope or content of documents within it. <!ELEMENT Transition (ConditionExpression, Documentation*) <!ATTLIST Transition oninitiation (true false) "false" frombusinessstate CDATA #IMPLIED frombusinessstateidref IDREF #IMPLIED tobusinessstate CDATA #IMPLIED tobusinessstateidref IDREF #IMPLIED conditionguard (Success BusinessFailure TechnicalFailure AnyFailure) #IMPLIED Definition: A transition is a transition between two business states in a binary collaboration. Choreography is expressed as transitions between business states. Parents: BinaryCollaboration BusinessPartnerRole Attributes: Attribute Name Definition Default Value oninitiation frombusinessstate frombusinessstateidr ef tobusinessstate tobusinessstateidref This specifies this is a nested BusinessTransactionActivit y and that upon receipt of the request in the associated transaction a second activity is performed before returning to the transaction to send the response back to the original requestor The name of the state transitioned from The XML IDREF version of frombusinessstate The name of the state transitioned to The XML IDREF version of tobusinessstate false Valid Values: {true, false} No default value. Optional No default value. Optional ebxml Business Process Specification Schema Page 93 of 136

2912 2913 2914 2915 conditionguard A reference to the status of the previous transaction. A fixed value of Success, BusinessFailure, TechnicalFailure, or AnyFailure Optional Valid Values: {Success, BusinessFailure, TechnicalFailure, AnyFailure} 2916 2917 2918 2919 2920 2921 2922 2923 8.2 XML to UML cross-reference The following is a table that references the XML element names in the DTD to their counterpart classes in the UML specification schema. XML Element Attachment InitiatingRole RespondingRole Binary Collaboration BusinessPartner Role Business Transaction Activity Business Transaction UML Class Attachment AuthorizedRole AuthorizedRole Binary Collaboration BusinessPartner Role Business Transaction Activity Business Transaction Responding BusinessActivity Requesting BusinessActivity Collaboration Activity DocumentEnvelo Responding BusinessActivity Requesting BusinessActivity Collaboration Activity DocumentEnvelo ebxml Business Process Specification Schema Page 94 of 136

2924 2925 2926 2927 2928 2929 2930 2931 2932 2933 2934 2935 2936 pe Documentation ebxml Process Specification Failure Include MultiParty Collaboration Package Performs Schema Fork Start Success Join Transition pe None (Should be added) (From Package model: ebxml Process Specification) Failure (From Package model: Include) MultiParty Collaboration (From Package model: Package) Performs Schema Fork Start Success Join Transition The following classes in the UML specification schema are abstract, and do not have an element equivalent in the DTD. Only their concrete subtypes are in the DTD: BusinessState CompletionState BusinessActivity BusinessAction DocumentSecurity ebxml Business Process Specification Schema Page 95 of 136

2937 2938 2939 2940 2941 2942 2943 2944 2945 2946 2947 2948 2949 2950 2951 2952 2953 2954 2955 2956 2957 2958 2959 2960 2961 2962 2963 2964 2965 2966 2967 2968 2969 2970 2971 2972 2973 2974 2975 2976 2977 2978 2979 2980 2981 8.3 Scoped Name Reference The structure of ebxml process specifications encourages re-use. An ebxmlprocessspecification can include another ebxmlprocessspecification by reference. In addition the contents of a ebxmlprocessspecification can be arranged in a recursive package structure. The ebxmlprocessspecification is a package container, so it can contain packages within it. Package in itself is also a package container, so it can contain further packages within it. Packages function as namespaces as per below. Finally a Package, at any level can have PackageContent. Types of PackageContent are BusinessTransaction, BinaryCollaboration, MultiPartyCollaboration. PackageContent are always uniquely named within a package. Lower level elements a uniquely named within their parent PackageContent. Each PackageContent type is a built-in context provider for the core components Logical Model for the Business Document definitions referenced by this ebxmlprocessspecification. Within a ebxmlprocessspecification the following applies to naming: Specification elements reference other specification elements by name through the use of attributes. The design pattern is that elements have a name attribute and other elements that reference the named elements do so through an attribute defined as the lowercamelcase version of the referenced element (e.g. AuthorizedRole has attribute name while Performs, which references AuthorizedRole, has attribute authorizedrole). Two types of attributes are provided for names and references, XML ID/IDREF based and plain text. Each named element has a required name attribute and an optional nameid attribute. Referencing elements have lowercamelcase and lowercamelcaseidref attributes for the referenced element. XML ID/IDREF functionality requires all IDs to be unique within a document and that all IDREFs point to a defined ID value. Plain text attributes do not have this capability and may result is duplicate names. To unambiguously identify a referenced element using plain text attribute in the referencing attribute it is strongly recommended that XPath syntax be used. However, this is not enforced in the DTD or Schema. The purpose of providing both solutions is to facilitate creation of Process Specification Documents directly in XML and to support future development tools that can automatically assign machine readable nameids and references. Both styles can be used simultaneously, in which case the ID and IDREF versions provide the unambiguous referencing and the plain text versions are used to provide meaningful names. Examples of named elements and references: <Package name= ebxmlordering <BinaryCollaboration name= OrderCollaboration nameid= b112 <AuthorizedRole name= buyer nameid= r224 / <AuthorizedRole name= seller nameid= r225 / </BinaryCollaboration </Package ebxml Business Process Specification Schema Page 96 of 136

2982 2983 2984 2985 2986 2987 2988 2989 2990 2991 2992 2993 2994 2995 2996 2997 2998 2999 3000 3001 3002 3003 3004 3005 3006 3007 3008 3009 3010 3011 3012 3013 3014 3015 3016 3017 3018 3019 3020 3021 <!-the XPath approach -- <Performs authorizedrole= //Package[@name= OAGOrdering ]/BinaryCollaboration[@name= OrderColla boration ]/AuthorizedRole[@name= buyer ] / <!-Combination approach -- <Performs authorizedrole= buyer authorizedroleidref= r224 / It is not required to use the full path specification as shown above, other forms of XPath expressions could be used as long as they resolve to a single reference. For example if buyer was unique to the document then the XPath could have been: <Performs authorizedrole= //AuthorizedRole[@name= buyer ] / Relative paths are also allowed for example: <BusinessTransactionActivity fromauthorizedrole=../authorizedrole[@name= buyer ]... / 8.4 Substitution Sets There is a requirement for Business specifications that are less coupled to technology and business details, such as specific document formats and structures and timing parameters. Substitution sets support the capability to take a generic business process and specialize it for a specific use. For example, an ordering process may be very generic but a specific use of that process may require specific document capabilities that go beyond the generic. A substitution set is placed in the more specific process specification and replaces or makes more explicit document definition references and attribute values. A Substitution Set is a container for one or more AttributeSubstitution and/or DocumentSubstitution elements. The entire SubstitutionSet specifies document or attribute values that should be used in place of some documents and attribute values in an existing process specification. 8.5 Sample XML document against above DTD Provided in Appendix A 9 Business signal structures The ebxml Message Service Specification signal structures provide business service state alignment infrastructure, including unique message identifiers and digests used to meet the basic process alignment ebxml Business Process Specification Schema Page 97 of 136

3022 3023 3024 3025 3026 3027 3028 3029 3030 3031 3032 3033 3034 3035 3036 3037 3038 3039 3040 3041 3042 3043 3044 3045 3046 3047 3048 3049 3050 3051 3052 3053 3054 3055 3056 3057 3058 3059 3060 3061 3062 3063 3064 3065 3066 3067 3068 3069 3070 3071 3072 3073 requirements. The business signal payload structures provided herein are optional and normative and are intended to provide business and legal semantic to the business signals. Since signals do not differ in structure from business transaction to business transaction, they are defined once and for all, and their definition is implied by the conjunction of the Business Process Specification Schema and Message Service Specification. Here are the DTD s for business signal payload for receiptacknowledgment (from the RosettaNet website, courtesy of RosettaNet, and Edifecs) and for acceptanceacknowledgement and exception. 9.1.1 ReceiptAcknowledgment DTD <!-- RosettaNet XML Message Schema. http://www.rosettanet.org RosettaNet XML Message Schema. Receipt Acknowledgement Version 1.1 -- <!ENTITY % common-attributes "id CDATA #IMPLIED" <!ELEMENT ReceiptAcknowledgement ( fromrole, NonRepudiationInformation?, receiveddocumentdatetime, receiveddocumentidentifier, thismessagedatetime, thismessageidentifier, torole ) <!ELEMENT fromrole ( PartnerRoleDescription ) <!ELEMENT PartnerRoleDescription ( ContactInformation?, GlobalPartnerRoleClassificationCode, PartnerDescription ) <!ELEMENT ContactInformation ( contactname, EmailAddress, telephonenumber ) <!ELEMENT contactname ( FreeFormText ) <!ELEMENT FreeFormText ( #PCDATA ) <!ATTLIST FreeFormText xml:lang CDATA #IMPLIED ebxml Business Process Specification Schema Page 98 of 136

3074 3075 3076 3077 3078 3079 3080 3081 3082 3083 3084 3085 3086 3087 3088 3089 3090 3091 3092 3093 3094 3095 3096 3097 3098 3099 3100 3101 3102 3103 3104 3105 3106 3107 3108 3109 3110 3111 3112 3113 3114 3115 3116 3117 3118 3119 3120 3121 3122 3123 3124 3125 3126 3127 3128 <!ELEMENT EmailAddress ( #PCDATA ) <!ELEMENT telephonenumber ( CommunicationsNumber ) <!ELEMENT CommunicationsNumber ( #PCDATA ) <!ELEMENT GlobalPartnerRoleClassificationCode ( #PCDATA ) <!ELEMENT PartnerDescription ( BusinessDescription, GlobalPartnerClassificationCode ) <!ELEMENT BusinessDescription ( GlobalBusinessIdentifier, GlobalSupplyChainCode ) <!ELEMENT GlobalBusinessIdentifier ( #PCDATA ) <!ELEMENT GlobalSupplyChainCode ( #PCDATA ) <!ELEMENT GlobalPartnerClassificationCode ( #PCDATA ) <!ELEMENT NonRepudiationInformation ( GlobalDigestAlgorithmCode, OriginalMessageDigest ) <!ELEMENT GlobalDigestAlgorithmCode ( #PCDATA ) <!ELEMENT OriginalMessageDigest ( #PCDATA ) <!ELEMENT receiveddocumentdatetime ( DateTimeStamp ) <!ELEMENT DateTimeStamp ( #PCDATA ) <!ELEMENT receiveddocumentidentifier ( ProprietaryDocumentIdentifier ) <!ELEMENT ProprietaryDocumentIdentifier ( #PCDATA ) <!ELEMENT thismessagedatetime ( DateTimeStamp ) ebxml Business Process Specification Schema Page 99 of 136

3129 3130 3131 3132 3133 3134 3135 3136 3137 3138 3139 3140 3141 3142 3143 3144 3145 3146 3147 3148 3149 3150 3151 3152 3153 3154 3155 3156 3157 3158 3159 3160 3161 3162 3163 3164 3165 3166 3167 3168 3169 3170 3171 3172 3173 3174 3175 3176 3177 3178 3179 3180 3181 3182 <!ELEMENT thismessageidentifier ( ProprietaryMessageIdentifier ) <!ELEMENT ProprietaryMessageIdentifier ( #PCDATA ) <!ELEMENT torole ( PartnerRoleDescription ) 9.1.2 AcceptanceAcknowledgement DTD <!-- RosettaNet XML Message Schema. http://www.rosettanet.org RosettaNet XML Message Schema. Acceptance Acknowledgement Exception Version 1.1 -- <!ENTITY % common-attributes "id CDATA #IMPLIED" <!ELEMENT AcceptanceAcknowledgementException ( fromrole, reason, themessagedatetime, theoffendingdocumentdatetime, theoffendingdocumentidentifier, thismessageidentifier, torole ) <!ELEMENT fromrole ( PartnerRoleDescription ) <!ELEMENT PartnerRoleDescription ( ContactInformation?, GlobalPartnerRoleClassificationCode, PartnerDescription ) <!ELEMENT ContactInformation ( contactname, EmailAddress, telephonenumber ) <!ELEMENT contactname ( FreeFormText ) <!ELEMENT FreeFormText ( #PCDATA ) <!ATTLIST FreeFormText xml:lang CDATA #IMPLIED <!ELEMENT EmailAddress ( #PCDATA ) <!ELEMENT telephonenumber ebxml Business Process Specification Schema Page 100 of 136

3183 3184 3185 3186 3187 3188 3189 3190 3191 3192 3193 3194 3195 3196 3197 3198 3199 3200 3201 3202 3203 3204 3205 3206 3207 3208 3209 3210 3211 3212 3213 3214 3215 3216 3217 3218 3219 3220 3221 3222 3223 3224 3225 3226 3227 3228 3229 3230 3231 3232 3233 3234 3235 3236 ( CommunicationsNumber ) <!ELEMENT CommunicationsNumber ( #PCDATA ) <!ELEMENT GlobalPartnerRoleClassificationCode ( #PCDATA ) <!ELEMENT PartnerDescription ( BusinessDescription, GlobalPartnerClassificationCode ) <!ELEMENT BusinessDescription ( GlobalBusinessIdentifier, GlobalSupplyChainCode ) <!ELEMENT GlobalBusinessIdentifier ( #PCDATA ) <!ELEMENT GlobalSupplyChainCode ( #PCDATA ) <!ELEMENT GlobalPartnerClassificationCode ( #PCDATA ) <!ELEMENT reason ( FreeFormText ) <!ELEMENT themessagedatetime ( DateTimeStamp ) <!ELEMENT DateTimeStamp ( #PCDATA ) <!ELEMENT theoffendingdocumentdatetime ( DateTimeStamp ) <!ELEMENT theoffendingdocumentidentifier ( ProprietaryDocumentIdentifier ) <!ELEMENT ProprietaryDocumentIdentifier ( #PCDATA ) <!ELEMENT thismessageidentifier ( ProprietaryMessageIdentifier ) <!ELEMENT ProprietaryMessageIdentifier ( #PCDATA ) <!ELEMENT torole ( PartnerRoleDescription ) 9.1.3 Exception Signal DTD ebxml Business Process Specification Schema Page 101 of 136

3237 3238 3239 3240 3241 3242 3243 3244 3245 3246 3247 3248 3249 3250 3251 3252 3253 3254 3255 3256 3257 3258 3259 3260 3261 3262 3263 3264 3265 3266 3267 3268 3269 3270 3271 3272 3273 3274 3275 3276 3277 3278 3279 3280 3281 3282 3283 3284 3285 3286 3287 3288 3289 3290 3291 <!-- RosettaNet XML Message Schema. http://www.rosettanet.org RosettaNet XML Message Schema. Exception Version 1.1 -- <!ENTITY % common-attributes "id CDATA #IMPLIED" <!ELEMENT Exception ( fromrole?, reason, themessagedatetime, theoffendingdocumentdatetime?, theoffendingdocumentidentifier?, thismessageidentifier, torole? ) <!ELEMENT fromrole ( PartnerRoleDescription ) <!ELEMENT PartnerRoleDescription ( ContactInformation?, GlobalPartnerRoleClassificationCode?, PartnerDescription? ) <!ELEMENT ContactInformation ( contactname?, EmailAddress?, telephonenumber? ) <!ELEMENT contactname ( FreeFormText ) <!ELEMENT FreeFormText ( #PCDATA ) <!ATTLIST FreeFormText xml:lang CDATA #IMPLIED <!ELEMENT EmailAddress ( #PCDATA ) <!ELEMENT telephonenumber ( CommunicationsNumber ) <!ELEMENT CommunicationsNumber ( #PCDATA ) <!ELEMENT GlobalPartnerRoleClassificationCode ( #PCDATA ) <!ELEMENT PartnerDescription ( BusinessDescription?, ebxml Business Process Specification Schema Page 102 of 136

3292 3293 3294 3295 3296 3297 3298 3299 3300 3301 3302 3303 3304 3305 3306 3307 3308 3309 3310 3311 3312 3313 3314 3315 3316 3317 3318 3319 3320 3321 3322 3323 3324 3325 3326 3327 3328 3329 3330 3331 3332 3333 3334 3335 3336 3337 3338 3339 3340 3341 GlobalPartnerClassificationCode? ) <!ELEMENT BusinessDescription ( GlobalBusinessIdentifier?, GlobalSupplyChainCode? ) <!ELEMENT GlobalBusinessIdentifier ( #PCDATA ) <!ELEMENT GlobalSupplyChainCode ( #PCDATA ) <!ELEMENT GlobalPartnerClassificationCode ( #PCDATA ) <!ELEMENT reason ( FreeFormText ) <!ELEMENT themessagedatetime ( DateTimeStamp ) <!ELEMENT DateTimeStamp ( #PCDATA ) <!ELEMENT theoffendingdocumentdatetime ( DateTimeStamp ) <!ELEMENT theoffendingdocumentidentifier ( ProprietaryDocumentIdentifier ) <!ELEMENT ProprietaryDocumentIdentifier ( #PCDATA ) <!ELEMENT thismessageidentifier ( ProprietaryMessageIdentifier ) <!ELEMENT ProprietaryMessageIdentifier ( #PCDATA ) <!ELEMENT torole ( PartnerRoleDescription ) 10 Production Rules This section provides a set of production rules, defining the mapping from the UML version of the Business Process Specification Schema to the XML version. The primary purpose for these production rules is to govern the one-time generation of the DTD version of the Business Process Specification Schema from the UML Class Diagram version of Business Process Specification Schema. ebxml Business Process Specification Schema Page 103 of 136

3342 3343 3344 3345 3346 3347 3348 3349 3350 3351 3352 3353 3354 3355 3356 3357 3358 3359 3360 3361 3362 3363 3364 3365 3366 3367 3368 3369 3370 3371 3372 3373 3374 3375 3376 3377 3378 The Class Diagram version of Business Process Specification Schema is not intended for the direct creation of ebxml Business Process Specifications. However, if a Business Process Specification was in fact (programmatically) created as an instance of this class diagram, the production rules would also provide the prescriptive definition necessary to translate a such an instance into a XML Specification Document conformant with the DTD. The production rules are defined for concrete classes, abstract classes, aggregate associations, specialization associations and unidirectional associations. 1. Classes are rendered as XML elements. 2. Class attributes are rendered as XML attributes. NOTE: occurrence requirements (required vs optional) and default values for attributes are not modeled. 3. Specialization classes (classes that inherit from another class) are rendered as XML elements including all attributes and aggregate associations from the base class. Repeated attributes are normalized to a single occurrence. 4. Abstract classes are not rendered in the XML DTD. Abstract classes are inherited from and represent a form of collection. A class that aggregates an abstract class, essentially aggregates any of each of the specialization classes. 5. An aggregate association renders the aggregated class as an XML child element with appropriate cardinality. 6. A unidirectional association defines an attribute in the originating class of the same name as the class the association points to. This type of attribute is called a reference attribute and contains the name of the class it points to. The referenced class must have a name attribute. 7. A class attribute data type, that has a class of the same name with stereotype <<Enumeration is rendered as an XML attribute enumeration. The Enumeration class does not have an explicit association. 8. A class attribute data type (e.g. Time, URI, Boolean) that has no corresponding class definition is rendered as a string in the DTD. In the XML Schema version these data types are mapped as: Time - xsd:duration URI - xsd:anyuri Boolean - xsd:boolean 9. Each class is given an optional Documentation* element which is intended for annotation of the specification instances. This is not modeled. ebxml Business Process Specification Schema Page 104 of 136

3379 3380 3381 3382 3383 3384 3385 3386 3387 3388 3389 3390 3391 3392 3393 3394 3395 3396 3397 3398 3399 3400 3401 3402 3403 3404 3405 3406 3407 3408 3409 3410 3411 3412 3413 3414 3415 3416 3417 3418 3419 3420 3421 3422 3423 3424 3425 3426 3427 3428 3429 Appendix A: Sample XML Business Process Specification <!-- edited by Kurt Kanaskie (Lucent Technologies) -- <!-- Notes from Kurt Kanaskie on 2001-04-17 Differences from 099 DTD: binarycollaboration attribute in Performs frombinarycollaboration attribute in Transition tobinarycollaboration attribute in Transition Differences from original: guard instead of guardexpression See EBXMLSpecification_2001_04_23.dtd for other changes -- <!DOCTYPE ProcessSpecification SYSTEM "ebxmlprocessspecificationv1.00.dtd" <ProcessSpecification name="simple" version="1.1" uuid="[1234-5678- 901234]" <!-- Business Documents -- <BusinessDocument name="catalog Request"/ <BusinessDocument name="catalog"/ <BusinessDocument name="purchase Order"/ <BusinessDocument name="po Acknowledgement"/ <BusinessDocument name="credit Request"/ <BusinessDocument name="credit Confirm"/ <BusinessDocument name="asn"/ <BusinessDocument name="creditadvice"/ <BusinessDocument name="debitadvice"/ <BusinessDocument name="invoice"/ <BusinessDocument name="payment"/ <BusinessDocument name="inventory Report Request"/ <BusinessDocument name="inventory Report"/ <BusinessDocument name="inventory Report"/ <Package name="ordering" <!-- First the overall MultiParty Collaboration -- <MultiPartyCollaboration name="dropship" <BusinessPartnerRole name="customer" <Performs initiatingrole="requestor"/ <Performs initiatingrole="buyer"/ <Transition frombusinessstate="catalog Request" tobusinessstate="create Order"/ </BusinessPartnerRole <BusinessPartnerRole name="retailer" <Performs respondingrole="provider"/ <Performs respondingrole="seller"/ <Performs initiatingrole="creditor"/ <Performs initiatingrole="buyer"/ <Performs initiatingrole="payee"/ <Performs respondingrole="payor"/ <Performs initiatingrole="requestor"/ <Transition frombusinessstate="create Order" tobusinessstate="check Credit"/ ebxml Business Process Specification Schema Page 105 of 136

3430 3431 3432 3433 3434 3435 3436 3437 3438 3439 3440 3441 3442 3443 3444 3445 3446 3447 3448 3449 3450 3451 3452 3453 3454 3455 3456 3457 3458 3459 3460 3461 3462 3463 3464 3465 3466 3467 3468 3469 3470 3471 3472 3473 3474 3475 3476 3477 3478 3479 3480 3481 3482 <Transition frombusinessstate="check Credit" tobusinessstate="create Order"/ </BusinessPartnerRole <BusinessPartnerRole name="dropship Vendor" <Performs respondingrole="seller"/ <Performs initiatingrole="payee"/ <Performs respondingrole="provider"/ </BusinessPartnerRole <BusinessPartnerRole name="credit Authority" <Performs respondingrole="credit service"/ <Performs respondingrole="payor"/ </BusinessPartnerRole </MultiPartyCollaboration <!-- Now the Binary Collaborations -- <BinaryCollaboration name="request Catalog" <InitiatingRole name="requestor"/ <RespondingRole name="provider"/ <BusinessTransactionActivity name="catalog Request" businesstransaction="catalog Request" fromauthorizedrole="requestor" toauthorizedrole="provider"/ </BinaryCollaboration <BinaryCollaboration name="firm Order" timetoperform="p2d" <DocumentationtimeToPerform = Period: 2 days from start of transaction</documentation <InitiatingRole name="buyer"/ <RespondingRole name="seller"/ <BusinessTransactionActivity name="create Order" businesstransaction="create Order" fromauthorizedrole="buyer" toauthorizedrole="seller"/ </BinaryCollaboration <BinaryCollaboration name="product Fulfillment" timetoperform="p5d" <DocumentationtimeToPerform = Period: 5 days from start of transaction</documentation <InitiatingRole name="buyer"/ <RespondingRole name="seller"/ <BusinessTransactionActivity name="create Order" businesstransaction="create Order" fromauthorizedrole="buyer" toauthorizedrole="seller"/ <BusinessTransactionActivity name="notify shipment" businesstransaction="notify of advance shipment" fromauthorizedrole="buyer" toauthorizedrole="seller"/ <Start tobusinessstate="create Order"/ <Transition frombusinessstate="create Order" tobusinessstate="notify shipment"/ <Success frombusinessstate="notify shipment" conditionguard="success"/ <Failure frombusinessstate="notify shipment" conditionguard="businessfailure"/ </BinaryCollaboration <BinaryCollaboration name="inventory Status" <InitiatingRole name="requestor"/ <RespondingRole name="provider"/ ebxml Business Process Specification Schema Page 106 of 136

3483 3484 3485 3486 3487 3488 3489 3490 3491 3492 3493 3494 3495 3496 3497 3498 3499 3500 3501 3502 3503 3504 3505 3506 3507 3508 3509 3510 3511 3512 3513 3514 3515 3516 3517 3518 3519 3520 3521 3522 3523 3524 3525 3526 3527 3528 3529 3530 3531 3532 3533 3534 3535 3536 <BusinessTransactionActivity name="inventory Report Request" businesstransaction="inventory Report Request" fromauthorizedrole="requestor" toauthorizedrole="provider"/ <BusinessTransactionActivity name="inventory Report" businesstransaction="inventory Report" fromauthorizedrole="provider" toauthorizedrole="requestor"/ </BinaryCollaboration <BinaryCollaboration name="credit Inquiry" <InitiatingRole name="creditor"/ <RespondingRole name="credit service"/ <BusinessTransactionActivity name="check Credit" businesstransaction="check Credit" fromauthorizedrole="creditor" toauthorizedrole="credit service"/ </BinaryCollaboration <BinaryCollaboration name="credit Payment" <InitiatingRole name="payee"/ <RespondingRole name="payor"/ <BusinessTransactionActivity name="process Credit Payment" businesstransaction="process Credit Payment" fromauthorizedrole="payee" toauthorizedrole="payor"/ </BinaryCollaboration <!-- A compound BinaryCollaboration for illustration purposes-- <BinaryCollaboration name="credit Charge" <InitiatingRole name="charger"/ <RespondingRole name="credit service"/ <CollaborationActivity name="credit Inquiry" binarycollaboration="credit Inquiry" fromauthorizedrole="charger" toauthorizedrole="credit service"/ <CollaborationActivity name="credit Payment" binarycollaboration="credit Payment" fromauthorizedrole="charger" toauthorizedrole="payor"/ <Transition frombusinessstate="credit Inquiry" tobusinessstate="credit Payment"/ </BinaryCollaboration <BinaryCollaboration name="fulfillment Payment" <InitiatingRole name="payee"/ <RespondingRole name="payor"/ <BusinessTransactionActivity name="process Payment" businesstransaction="process Payment" fromauthorizedrole="payee" toauthorizedrole="payor"/ </BinaryCollaboration <!-- Here are all the Business Transactions needed -- <BusinessTransaction name="catalog Request" <RequestingBusinessActivity name="" <DocumentEnvelope ispositiveresponse="true" businessdocument="catalog Request"/ </RequestingBusinessActivity <RespondingBusinessActivity name="" <DocumentEnvelope ispositiveresponse="true" businessdocument="catalog"/ </RespondingBusinessActivity </BusinessTransaction <BusinessTransaction name="create Order" ebxml Business Process Specification Schema Page 107 of 136

3537 3538 3539 3540 3541 3542 3543 3544 3545 3546 3547 3548 3549 3550 3551 3552 3553 3554 3555 3556 3557 3558 3559 3560 3561 3562 3563 3564 3565 3566 3567 3568 3569 3570 3571 3572 3573 3574 3575 3576 3577 3578 3579 3580 3581 3582 3583 3584 3585 3586 3587 3588 3589 3590 3591 <RequestingBusinessActivity name="" isnonrepudiationrequired="true" timetoacknowledgereceipt="p2d" timetoacknowledgeacceptance="p3d" <DocumentEnvelope ispositiveresponse="true" businessdocument="purchase Order"/ </RequestingBusinessActivity <RespondingBusinessActivity name="" isnonrepudiationrequired="true" timetoacknowledgereceipt="p5d" <DocumentEnvelope ispositiveresponse="true" businessdocument="po Acknowledgement"/ </RespondingBusinessActivity </BusinessTransaction <BusinessTransaction name="check Credit " <RequestingBusinessActivity name="" <DocumentEnvelope ispositiveresponse="true" businessdocument="credit Request"/ </RequestingBusinessActivity <RespondingBusinessActivity name="" <DocumentEnvelope ispositiveresponse="true" businessdocument="credit Confirm"/ </RespondingBusinessActivity </BusinessTransaction <BusinessTransaction name="notify of advance shipment" <RequestingBusinessActivity name="" <DocumentEnvelope ispositiveresponse="true" businessdocument="asn"/ </RequestingBusinessActivity <RespondingBusinessActivity name="" timetoacknowledgereceipt="p2d"/ </BusinessTransaction <BusinessTransaction name="process Credit Payment" <RequestingBusinessActivity name="" <DocumentEnvelope ispositiveresponse="true" businessdocument="creditadvice"/ </RequestingBusinessActivity <RespondingBusinessActivity name="" <DocumentEnvelope ispositiveresponse="true" businessdocument="debitadvice"/ </RespondingBusinessActivity </BusinessTransaction <BusinessTransaction name="process Payment" <RequestingBusinessActivity name="" <DocumentEnvelope ispositiveresponse="true" businessdocument="invoice"/ </RequestingBusinessActivity <RespondingBusinessActivity name="" <DocumentEnvelope ispositiveresponse="true" businessdocument="payment"/ </RespondingBusinessActivity </BusinessTransaction <BusinessTransaction name="request Inventory Report" <RequestingBusinessActivity name="" <DocumentEnvelope ispositiveresponse="true" businessdocument="inventory Report Request"/ </RequestingBusinessActivity ebxml Business Process Specification Schema Page 108 of 136

3592 3593 3594 3595 3596 3597 3598 3599 3600 3601 3602 3603 3604 3605 <RespondingBusinessActivity name="" <DocumentEnvelope ispositiveresponse="true" businessdocument="inventory Report"/ </RespondingBusinessActivity </BusinessTransaction <BusinessTransaction name="inventory Report" <RequestingBusinessActivity name="" <DocumentEnvelope ispositiveresponse="true" businessdocument="inventory Report"/ </RequestingBusinessActivity <RespondingBusinessActivity name=""/ </BusinessTransaction </Package </ProcessSpecification ebxml Business Process Specification Schema Page 109 of 136

3606 3607 3608 3609 3610 3611 3612 3613 3614 3615 3616 3617 3618 3619 3620 3621 3622 3623 3624 3625 3626 3627 3628 3629 3630 3631 3632 3633 3634 3635 3636 3637 3638 3639 3640 3641 3642 3643 3644 3645 3646 3647 3648 3649 3650 3651 3652 3653 3654 3655 3656 Appendix B: Business Process Specification Schema DTD <!-- =============================================================== -- <!-- Editor: Kurt Kanaskie (Lucent Technologies) -- <!-- Version: Version 1.0 -- <!-- Updated: 2001-05-10 -- <!-- -- <!-- Public Identifier: -- <!-- "-//ebxml//dtd Process Specification ver 1.0//EN" -- <!-- -- <!-- Purpose: -- <!-- The ebxml Specification DTD provides a standard -- <!-- framework by which business systems may be -- <!-- configured to support execution of business -- <!-- transactions. It is based upon prior UN/CEFACT -- <!-- work, specifically the metamodel behind the -- <!-- UN/CEFACT Unified Modeling Methodology (UMM) defined -- <!-- in the N090R9.1 specification. -- <!-- -- <!-- The Specification Schema supports the specification -- <!-- of Business Transactions and the choreography of -- <!-- Business Transactions into Business Collaborations. -- <!-- -- <!-- Notes: -- <!-- time periods are represented using ISO 8601 format -- <!-- (e.g. P2D for 2 Days, P2H30M for 2 Hours 30 Minutes -- ebxml Business Process Specification Schema Page 110 of 136

3657 3658 3659 3660 3661 3662 3663 3664 3665 3666 3667 3668 3669 3670 3671 3672 3673 3674 3675 3676 3677 3678 3679 3680 3681 3682 3683 3684 3685 3686 3687 3688 3689 3690 3691 3692 3693 3694 3695 3696 3697 3698 3699 3700 3701 3702 3703 3704 3705 3706 3707 3708 3709 3710 3711 <!-- -- <!-- Naming and reference is based on convention that an -- <!-- Element with a name attribute (e.g. AuthorizedRole) -- <!-- is refernced by an attribute in another element with -- <!-- the name in lowercamelcase (e.g. authorizedrole). -- <!-- -- <!-- frombusinessstate and tobusinessstate refer to the -- <!-- the names of a BusinessTransactionActivity, -- <!-- CollaborationActivity, Fork, and Join, all are targets for -- <!-- from/to in Transition. This deviates from the normal -- <!-- convention of lowercamelcase attribute name -- <!-- BusinessState is used as a generic term for: -- <!-- Fork, Join, Success, Failure -- <!-- -- <!-- Constraints: -- <!-- - attributes location, logicalmodel, pattern, specification -- <!-- uri, are of type xsd:anyuri -- <!-- - attributes timeto* are of type xsd:duration -- <!-- issuccess is an expression (e.g. XPath) that results -- <!-- in a boolean true or false based on document name or -- <!-- document content. -- <!-- -- <!-- =============================================================== -- <!ELEMENT ProcessSpecification (Documentation*, SubstitutionSet*, (Include* BusinessDocument* ProcessSpecification* Package BinaryCollaboration BusinessTransaction MultiPartyCollaboration)*) <!ATTLIST ProcessSpecification name ID #REQUIRED uuid CDATA #REQUIRED version CDATA #REQUIRED ebxml Business Process Specification Schema Page 111 of 136

3712 3713 3714 3715 3716 3717 3718 3719 3720 3721 3722 3723 3724 3725 3726 3727 3728 3729 3730 3731 3732 3733 3734 3735 3736 3737 3738 3739 3740 3741 3742 3743 3744 3745 3746 3747 3748 3749 3750 3751 3752 3753 3754 3755 3756 3757 3758 3759 3760 3761 3762 3763 3764 3765 3766 <!ELEMENT Documentation (#PCDATA) <!ATTLIST Documentation uri CDATA #IMPLIED <!ELEMENT Include (Documentation*) <!ATTLIST Include name CDATA #REQUIRED uuid CDATA #REQUIRED uri CDATA #REQUIRED version CDATA #REQUIRED <!ELEMENT BusinessDocument (ConditionExpression?, Documentation*) <!ATTLIST BusinessDocument name CDATA #REQUIRED nameid ID #IMPLIED specificationlocation CDATA #IMPLIED specificationelement CDATA #IMPLIED <!ELEMENT ConditionExpression (Documentation*) <!ATTLIST ConditionExpression expressionlanguage CDATA #IMPLIED expression CDATA #IMPLIED <!ELEMENT SubstitutionSet (DocumentSubstitution AttributeSubstitution Documentation)* <!ATTLIST SubstitutionSet name CDATA #IMPLIED nameid IDREF #IMPLIED applytoscope CDATA #IMPLIED <!ELEMENT DocumentSubstitution (Documentation*) <!ATTLIST DocumentSubstitution originalbusinessdocument CDATA #IMPLIED originalbusinessdocumentid IDREF #IMPLIED substitutebusinessdocument CDATA #IMPLIED substitutebusinessdocumentid IDREF #IMPLIED <!ELEMENT AttributeSubstitution (Documentation*) <!ATTLIST AttributeSubstitution attributename CDATA #IMPLIED value CDATA #IMPLIED <!ELEMENT Package (Documentation*, (Package BinaryCollaboration BusinessTransaction MultiPartyCollaboration)*) <!ATTLIST Package name CDATA #REQUIRED nameid ID #IMPLIED ebxml Business Process Specification Schema Page 112 of 136

3767 3768 3769 3770 3771 3772 3773 3774 3775 3776 3777 3778 3779 3780 3781 3782 3783 3784 3785 3786 3787 3788 3789 3790 3791 3792 3793 3794 3795 3796 3797 3798 3799 3800 3801 3802 3803 3804 3805 3806 3807 3808 3809 3810 3811 3812 3813 3814 3815 3816 3817 3818 3819 3820 3821 <!ELEMENT BinaryCollaboration (Documentation*, InitiatingRole, RespondingRole, (Documentation* Start Transition Success Failure BusinessTransactionActivity CollaborationActivity Fork Join)*) <!ATTLIST BinaryCollaboration name CDATA #REQUIRED nameid ID #IMPLIED pattern CDATA #IMPLIED beginswhen CDATA #IMPLIED endswhen CDATA #IMPLIED precondition CDATA #IMPLIED postcondition CDATA #IMPLIED timetoperform CDATA #IMPLIED <!ELEMENT MultiPartyCollaboration (Documentation*, BusinessPartnerRole*) <!ATTLIST MultiPartyCollaboration name CDATA #REQUIRED nameid ID #IMPLIED <!ELEMENT InitiatingRole (Documentation*) <!ATTLIST InitiatingRole name CDATA #REQUIRED nameid ID #IMPLIED <!ELEMENT RespondingRole(Documentation*) <!ATTLIST RespondingRole name CDATA #REQUIRED nameid ID #IMPLIED <!-- A BusinessState is one of Start, Success, Failure, Fork, Join, BusinessTransactionActivity or CollaborationActivity -- <!-- frombusinessstate and tobusinessstate are fully qualified using XPath -- <!ELEMENT Transition (ConditionExpression?, Documentation*) <!ATTLIST Transition oninitiation (true false) "false" frombusinessstate CDATA #IMPLIED frombusinessstateidref IDREF #IMPLIED tobusinessstate CDATA #IMPLIED tobusinessstateidref IDREF #IMPLIED conditionguard (Success BusinessFailure TechnicalFailure AnyFailure ) #IMPLIED <!-- Start is a special type of Transition in that it only has a destination -- <!ELEMENT Start (Documentation*) <!ATTLIST Start tobusinessstate CDATA #REQUIRED ebxml Business Process Specification Schema Page 113 of 136

3822 3823 3824 3825 3826 3827 3828 3829 3830 3831 3832 3833 3834 3835 3836 3837 3838 3839 3840 3841 3842 3843 3844 3845 3846 3847 3848 3849 3850 3851 3852 3853 3854 3855 3856 3857 3858 3859 3860 3861 3862 3863 3864 3865 3866 3867 3868 3869 3870 3871 3872 3873 3874 3875 3876 tobusinessstateidref IDREF #IMPLIED <!-- Success is a special type of Transition in that it only has a origination -- <!ELEMENT Success (ConditionExpression?, Documentation*) <!ATTLIST Success frombusinessstate CDATA #REQUIRED frombusinessstateidref IDREF #IMPLIED conditionguard (Success BusinessFailure TechnicalFailure AnyFailure ) #IMPLIED <!-- Failure is a special type of Transition in that it only has a origination -- <!ELEMENT Failure (ConditionExpression?, Documentation*) <!ATTLIST Failure frombusinessstate CDATA #REQUIRED frombusinessstateidref IDREF #IMPLIED conditionguard (Success BusinessFailure TechnicalFailure AnyFailure ) #IMPLIED <!-- Fork is a special type of BusinessState that can be transitioned to -- <!ELEMENT Fork (Documentation*) <!ATTLIST Fork name CDATA #REQUIRED nameid ID #IMPLIED <!-- Join is a special type of BusinessState that can be transitioned to -- <!ELEMENT Join (Documentation*) <!ATTLIST Join name CDATA #REQUIRED nameid ID #IMPLIED waitforall (true false) "true" <!-- fromauthorizedrole and toauthorizedrole are fully qualified using XPath -- <!-- BusinessTransactionActivity is a BusinessState that can be transitioned to -- <!ELEMENT BusinessTransactionActivity (Documentation*) <!ATTLIST BusinessTransactionActivity name CDATA #REQUIRED nameid ID #IMPLIED businesstransaction CDATA #REQUIRED businesstransactionidref IDREF #IMPLIED fromauthorizedrole CDATA #REQUIRED fromauthorizedroleidref IDREF #IMPLIED toauthorizedrole CDATA #REQUIRED toauthorizedroleidref IDREF #IMPLIED isconcurrent (true false) "true" islegallybinding (true false) "true" timetoperform CDATA #IMPLIED ebxml Business Process Specification Schema Page 114 of 136

3877 3878 3879 3880 3881 3882 3883 3884 3885 3886 3887 3888 3889 3890 3891 3892 3893 3894 3895 3896 3897 3898 3899 3900 3901 3902 3903 3904 3905 3906 3907 3908 3909 3910 3911 3912 3913 3914 3915 3916 3917 3918 3919 3920 3921 3922 3923 3924 3925 3926 3927 3928 3929 3930 3931 <!-- fromauthorizedrole and toauthorizedrole are fully qualified using XPath -- <!-- CollaborationActivity is a BusinessState that can be transitioned to -- <!ELEMENT CollaborationActivity (Documentation*) <!ATTLIST CollaborationActivity name CDATA #REQUIRED nameid ID #IMPLIED fromauthorizedrole CDATA #REQUIRED fromauthorizedroleidref IDREF #IMPLIED toauthorizedrole CDATA #REQUIRED toauthorizedroleidref IDREF #IMPLIED binarycollaboration CDATA #REQUIRED binarycollaborationidref IDREF #IMPLIED <!ELEMENT BusinessTransaction (Documentation*, RequestingBusinessActivity, RespondingBusinessActivity) <!ATTLIST BusinessTransaction name CDATA #REQUIRED nameid ID #IMPLIED pattern CDATA #IMPLIED beginswhen CDATA #IMPLIED endswhen CDATA #IMPLIED isguaranteeddeliveryrequired (true false) "false" precondition CDATA #IMPLIED postcondition CDATA #IMPLIED <!ELEMENT RequestingBusinessActivity (Documentation*, DocumentEnvelope) <!ATTLIST RequestingBusinessActivity name CDATA #IMPLIED nameid ID #IMPLIED isauthorizationrequired (true false) "false" isintelligiblecheckrequired (true false) "false" isnonrepudiationreceiptrequired (true false) "false" isnonrepudiationrequired (true false) "false" timetoacknowledgeacceptance CDATA #IMPLIED timetoacknowledgereceipt CDATA #IMPLIED <!ELEMENT RespondingBusinessActivity (Documentation*, DocumentEnvelope*) <!ATTLIST RespondingBusinessActivity name CDATA #IMPLIED nameid ID #IMPLIED isauthorizationrequired (true false) "false" isintelligiblecheckrequired (true false) "false" isnonrepudiationreceiptrequired (true false) "false" isnonrepudiationrequired (true false) "false" timetoacknowledgereceipt CDATA #IMPLIED <!ELEMENT DocumentEnvelope (Documentation*, Attachment*) <!ATTLIST DocumentEnvelope businessdocument CDATA #REQUIRED ebxml Business Process Specification Schema Page 115 of 136

3932 3933 3934 3935 3936 3937 3938 3939 3940 3941 3942 3943 3944 3945 3946 3947 3948 3949 3950 3951 3952 3953 3954 3955 3956 3957 3958 3959 3960 3961 3962 3963 3964 3965 businessdocumentidref IDREF #IMPLIED ispositiveresponse (true false) "false" isauthenticated (true false) "false" isconfidential (true false) "false" istamperproof (true false) "false" <!ELEMENT Attachment (Documentation*) <!ATTLIST Attachment name CDATA #REQUIRED nameid ID #IMPLIED businessdocument CDATA #IMPLIED businessdocumentidref IDREF #IMPLIED mimetype CDATA #REQUIRED specification CDATA #IMPLIED version CDATA #IMPLIED isauthenticated (true false) "false" isconfidential (true false) "false" istamperproof (true false) "false" <!ELEMENT BusinessPartnerRole (Documentation*, Performs*, Transition*) <!ATTLIST BusinessPartnerRole name CDATA #REQUIRED nameid ID #IMPLIED <!-- authorizedrole is fully qualified using XPath -- <!ELEMENT Performs (Documentation*) <!ATTLIST Performs initiatingrole CDATA #IMPLIED inititiatingroleidref IDREF #IMPLIED respondingrole CDATA #IMPLIED respondingroleidref IDREF #IMPLIED ebxml Business Process Specification Schema Page 116 of 136

3966 3967 3968 3969 3970 3971 3972 3973 3974 3975 3976 3977 3978 3979 3980 3981 3982 3983 3984 3985 3986 3987 3988 3989 3990 3991 3992 3993 3994 3995 3996 3997 3998 3999 4000 4001 4002 4003 4004 4005 4006 4007 4008 4009 4010 4011 4012 4013 4014 4015 4016 4017 Appendix C: Business Process Specification Schema XML Schema <?xml version="1.0" encoding="utf-8"? <!-- edited by Kurt Kanaskie (Lucent Technologies) -- <!-- Updated 2001-05-10 <!-- Kanaskie Updated 2001-04-27 Use urireference instead of anyuri Use timeduration instead of duration -- <!-- Kanaskie Changed 2001-04-27 See DTD for list of changes. Differences from DTD version: AuthorizedRole minoccurs=2 maxoccurs=2 <xsd:attribute name="pattern" type="xsd:anyuri"/ <xsd:attribute name="uri" type="xsd:anyuri" use="required"/ <xsd:attribute name="location" type="xsd:anyuri"/ <xsd:attribute name="logicalmodel" type="xsd:anyuri"/ <xsd:attribute name="specification" type="xsd:anyuri"/ <xsd:attribute name="timetoperform" type="xsd:duration"/ <xsd:attribute name="timetoperform" type="xsd:duration"/ <xsd:attribute name="timetoacknowledgeacceptance" type="xsd:duration"/ <xsd:attribute name="timetoacknowledgereceipt" type="xsd:duration"/ <xsd:attribute name="timetoacknowledgeacceptance" type="xsd:duration"/ <xsd:attribute name="timetoacknowledgereceipt" type="xsd:duration"/ <xsd:attribute name="isauthenticated" type="xsd:boolean" value="false"/ <xsd:attribute name="isconfidential" type="xsd:boolean" value="false"/ <xsd:attribute name="istamperproof" type="xsd:boolean" value="false"/ <xsd:attribute name="isguaranteeddeliveryrequired" type="xsd:boolean" value="false"/ <xsd:attribute name="isconcurrent" type="xsd:boolean" value="true"/ <xsd:attribute name="islegallybinding" type="xsd:boolean" value="true"/ <xsd:attribute name="isauthenticated" type="xsd:boolean" value="false"/ <xsd:attribute name="isconfidential" type="xsd:boolean" value="false"/ <xsd:attribute name="istamperproof" type="xsd:boolean" value="false"/ <xsd:attribute name="waitforall" type="xsd:boolean" value="true"/ <xsd:attribute name="isauthorizationrequired" type="xsd:boolean" value="false"/ <xsd:attribute name="isintelligiblecheckrequired" type="xsd:boolean" value="false"/ ebxml Business Process Specification Schema Page 117 of 136

4018 4019 4020 4021 4022 4023 4024 4025 4026 4027 4028 4029 4030 4031 4032 4033 4034 4035 4036 4037 4038 4039 4040 4041 4042 4043 4044 4045 4046 4047 4048 4049 4050 4051 4052 4053 4054 4055 4056 4057 4058 4059 4060 4061 4062 4063 4064 4065 4066 4067 4068 4069 4070 4071 4072 <xsd:attribute name="isnonrepudiationreceiptrequired" type="xsd:boolean" value="false"/ <xsd:attribute name="isnonrepudiationrequired" type="xsd:boolean" value="false"/ <xsd:attribute name="isauthorizationrequired" type="xsd:boolean" value="false"/ <xsd:attribute name="isintelligiblecheckrequired" type="xsd:boolean" value="false"/ <xsd:attribute name="isnonrepudiationreceiptrequired" type="xsd:boolean" value="false"/ <xsd:attribute name="isnonrepudiationrequired" type="xsd:boolean" value="false"/ <xsd:attribute name="oninitiation" type="xsd:boolean" value="false"/ -- <xsd:schema targetnamespace="http://www.ebxml.org/businessprocess" xmlns:xsd="http://www.w3.org/2000/10/xmlschema" xmlns="http://www.ebxml.org/businessprocess" elementformdefault="qualified" <xsd:element name="attachment" <xsd:complextype <xsd:sequence <xsd:element ref="documentation" minoccurs="0" maxoccurs="unbounded"/ </xsd:sequence <xsd:attribute name="name" type="xsd:string" use="required"/ <xsd:attribute name="nameid" type="xsd:id"/ <xsd:attribute name="businessdocument" type="xsd:string"/ <xsd:attribute name="businessdocumentidref" type="xsd:idref"/ <xsd:attribute name="specification" type="xsd:urireference"/ <xsd:attribute name="mimetype" type="xsd:string" use="required"/ <xsd:attribute name="version" type="xsd:string"/ <xsd:attribute name="isauthenticated" type="xsd:boolean" value="false"/ <xsd:attribute name="isconfidential" type="xsd:boolean" value="false"/ <xsd:attribute name="istamperproof" type="xsd:boolean" value="false"/ </xsd:complextype </xsd:element <xsd:element name="initiatingrole" <xsd:complextype <xsd:sequence <xsd:element ref="documentation" minoccurs="0" maxoccurs="unbounded"/ </xsd:sequence <xsd:attribute name="name" type="xsd:string" use="required"/ <xsd:attribute name="nameid" type="xsd:id"/ </xsd:complextype ebxml Business Process Specification Schema Page 118 of 136

4073 4074 4075 4076 4077 4078 4079 4080 4081 4082 4083 4084 4085 4086 4087 4088 4089 4090 4091 4092 4093 4094 4095 4096 4097 4098 4099 4100 4101 4102 4103 4104 4105 4106 4107 4108 4109 4110 4111 4112 4113 4114 4115 4116 4117 4118 4119 4120 4121 4122 4123 4124 4125 4126 4127 </xsd:element <xsd:element name="respondingrole" <xsd:complextype <xsd:sequence <xsd:element ref="documentation" minoccurs="0" maxoccurs="unbounded"/ </xsd:sequence <xsd:attribute name="name" type="xsd:string" use="required"/ <xsd:attribute name="nameid" type="xsd:id"/ </xsd:complextype </xsd:element <xsd:element name="binarycollaboration" <xsd:complextype <xsd:sequence <xsd:element ref="documentation" minoccurs="0" maxoccurs="unbounded"/ <xsd:element ref="initiatingrole"/ <xsd:element ref="respondingrole"/ <xsd:choice minoccurs="0" maxoccurs="unbounded" <xsd:element ref="documentation" minoccurs="0" maxoccurs="unbounded"/ <xsd:element ref="start"/ <xsd:element ref="transition"/ <xsd:element ref="success"/ <xsd:element ref="failure"/ <xsd:element ref="businesstransactionactivity"/ <xsd:element ref="collaborationactivity"/ <xsd:element ref="fork"/ <xsd:element ref="join"/ </xsd:choice </xsd:sequence <xsd:attribute name="name" type="xsd:string" use="required"/ <xsd:attribute name="nameid" type="xsd:id"/ <xsd:attribute name="pattern" type="xsd:urireference"/ <xsd:attribute name="beginswhen" type="xsd:string"/ <xsd:attribute name="endswhen" type="xsd:string"/ <xsd:attribute name="precondition" type="xsd:string"/ <xsd:attribute name="postcondition" type="xsd:string"/ <xsd:attribute name="timetoperform" type="xsd:timeduration"/ </xsd:complextype </xsd:element <xsd:element name="businessdocument" <xsd:complextype <xsd:sequence <xsd:element ref="documentation" minoccurs="0" maxoccurs="unbounded"/ ebxml Business Process Specification Schema Page 119 of 136

4128 4129 4130 4131 4132 4133 4134 4135 4136 4137 4138 4139 4140 4141 4142 4143 4144 4145 4146 4147 4148 4149 4150 4151 4152 4153 4154 4155 4156 4157 4158 4159 4160 4161 4162 4163 4164 4165 4166 4167 4168 4169 4170 4171 4172 4173 4174 4175 4176 4177 4178 4179 4180 4181 4182 <xsd:element ref="conditionexpression" minoccurs="0" maxoccurs="1"/ </xsd:sequence <xsd:attribute name="name" type="xsd:string" use="required"/ <xsd:attribute name="nameid" type="xsd:id"/ <xsd:attribute name="specificationlocation" type="xsd:string"/ <xsd:attribute name="specificationelement" type="xsd:string"/ </xsd:complextype </xsd:element <xsd:element name="substitutionset" <xsd:complextype <xsd:sequence <xsd:element ref="documentsubstitution" minoccurs="0" maxoccurs="unbounded"/ <xsd:element ref="attributesubstitution" minoccurs="0" maxoccurs="unbounded"/ <xsd:element ref="documentation" minoccurs="0" maxoccurs="unbounded"/ </xsd:sequence <xsd:attribute name="name" type="xsd:string"/ <xsd:attribute name="nameid" type="xsd:id"/ <xsd:attribute name=" applytoscope" type="xsd:string"/ </xsd:complextype </xsd:element <xsd:element name="documentsubstitution" <xsd:complextype <xsd:element ref="documentation" minoccurs="0" maxoccurs="unbounded"/ <xsd:attribute name="originalbusinessdocument" type="xsd:string"/ <xsd:attribute name="originalbusinessdocumentid" type="xsd:id"/ <xsd:attribute name="substitutebusinessdocument" type="xsd:string"/ <xsd:attribute name="substitutebusinessdocumentid" type="xsd:id"/ </xsd:complextype </xsd:element <xsd:element name="attributesubstitution" <xsd:complextype <xsd:sequence <xsd:element ref="documentation" minoccurs="0" maxoccurs="unbounded"/ </xsd:sequence <xsd:attribute name="attributename" type="xsd:string"/ <xsd:attribute name="value" type="xsd:string"/ </xsd:complextype </xsd:element <xsd:element name="conditionexpression" <xsd:complextype ebxml Business Process Specification Schema Page 120 of 136

4183 4184 4185 4186 4187 4188 4189 4190 4191 4192 4193 4194 4195 4196 4197 4198 4199 4200 4201 4202 4203 4204 4205 4206 4207 4208 4209 4210 4211 4212 4213 4214 4215 4216 4217 4218 4219 4220 4221 4222 4223 4224 4225 4226 4227 4228 4229 4230 4231 4232 4233 4234 4235 4236 4237 <xsd:sequence <xsd:element ref="documentation" minoccurs="0" maxoccurs="unbounded"/ </xsd:sequence <xsd:attribute name="expressionlanguage" type="xsd:string"/ <xsd:attribute name="expression" type="xsd:string"/ </xsd:complextype </xsd:element <xsd:element name="businesspartnerrole" <xsd:complextype <xsd:sequence <xsd:element ref="documentation" minoccurs="0" maxoccurs="unbounded"/ <xsd:element ref="performs" minoccurs="0" maxoccurs="unbounded"/ <xsd:element ref="transition" minoccurs="0" maxoccurs="unbounded"/ </xsd:sequence <xsd:attribute name="name" type="xsd:string" use="required"/ <xsd:attribute name="nameid" type="xsd:id"/ </xsd:complextype </xsd:element <xsd:element name="businesstransaction" <xsd:complextype <xsd:sequence <xsd:element ref="documentation" minoccurs="0" maxoccurs="unbounded"/ <xsd:element ref="requestingbusinessactivity"/ <xsd:element ref="respondingbusinessactivity"/ </xsd:sequence <xsd:attribute name="name" type="xsd:string" use="required"/ <xsd:attribute name="nameid" type="xsd:id"/ <xsd:attribute name="pattern" type="xsd:urireference"/ <xsd:attribute name="beginswhen" type="xsd:string"/ <xsd:attribute name="endswhen" type="xsd:string"/ <xsd:attribute name="isguaranteeddeliveryrequired" type="xsd:boolean" value="false"/ <xsd:attribute name="precondition" type="xsd:string"/ <xsd:attribute name="postcondition" type="xsd:string"/ </xsd:complextype </xsd:element <xsd:element name="businesstransactionactivity" <xsd:complextype <xsd:sequence <xsd:element ref="documentation" minoccurs="0" maxoccurs="unbounded"/ </xsd:sequence ebxml Business Process Specification Schema Page 121 of 136

4238 4239 4240 4241 4242 4243 4244 4245 4246 4247 4248 4249 4250 4251 4252 4253 4254 4255 4256 4257 4258 4259 4260 4261 4262 4263 4264 4265 4266 4267 4268 4269 4270 4271 4272 4273 4274 4275 4276 4277 4278 4279 4280 4281 4282 4283 4284 4285 4286 4287 4288 4289 4290 4291 <xsd:attribute name="name" type="xsd:string" use="required"/ <xsd:attribute name="nameid" type="xsd:id"/ <xsd:attribute name="businesstransaction" type="xsd:string" use="required"/ <xsd:attribute name="businesstransactionidref" type="xsd:idref"/ <xsd:attribute name="fromauthorizedrole" type="xsd:string" use="required"/ <xsd:attribute name="fromauthorizedroleidref" type="xsd:idref"/ <xsd:attribute name="toauthorizedrole" type="xsd:string" use="required"/ <xsd:attribute name="toauthorizedroleidref" type="xsd:idref"/ <xsd:attribute name="isconcurrent" type="xsd:boolean" value="true"/ <xsd:attribute name="islegallybinding" type="xsd:boolean" value="true"/ <xsd:attribute name="timetoperform" type="xsd:timeduration"/ </xsd:complextype </xsd:element <xsd:element name="collaborationactivity" <xsd:complextype <xsd:sequence <xsd:element ref="documentation" minoccurs="0" maxoccurs="unbounded"/ </xsd:sequence <xsd:attribute name="nameid" type="xsd:id"/ <xsd:attribute name="name" type="xsd:string" use="required"/ <xsd:attribute name="fromauthorizedrole" type="xsd:string" use="required"/ <xsd:attribute name="fromauthorizedroleidref" type="xsd:idref"/ <xsd:attribute name="toauthorizedrole" type="xsd:string" use="required"/ <xsd:attribute name="toauthorizedroleidref" type="xsd:idref"/ <xsd:attribute name="binarycollaboration" type="xsd:string" use="required"/ <xsd:attribute name="binarycollaborationidref" type="xsd:idref"/ </xsd:complextype </xsd:element <xsd:element name="documentenvelope" <xsd:complextype <xsd:sequence <xsd:element ref="documentation" minoccurs="0" maxoccurs="unbounded"/ <xsd:element ref="attachment" minoccurs="0" maxoccurs="unbounded"/ </xsd:sequence ebxml Business Process Specification Schema Page 122 of 136

4292 4293 4294 4295 4296 4297 4298 4299 4300 4301 4302 4303 4304 4305 4306 4307 4308 4309 4310 4311 4312 4313 4314 4315 4316 4317 4318 4319 4320 4321 4322 4323 4324 4325 4326 4327 4328 4329 4330 4331 4332 4333 4334 4335 4336 4337 4338 4339 4340 4341 4342 4343 4344 4345 4346 <xsd:attribute name="businessdocument" type="xsd:string" use="required"/ <xsd:attribute name="businessdocumentidref" type="xsd:idref"/ <xsd:attribute name="ispositiveresponse" type="xsd:string"/ <xsd:attribute name="isauthenticated" type="xsd:boolean" value="false"/ <xsd:attribute name="isconfidential" type="xsd:boolean" value="false"/ <xsd:attribute name="istamperproof" type="xsd:boolean" value="false"/ </xsd:complextype </xsd:element <xsd:element name="documentation" <xsd:complextype <xsd:simplecontent <xsd:restriction base="xsd:string" <xsd:attribute name="uri" type="xsd:urireference"/ </xsd:restriction </xsd:simplecontent </xsd:complextype </xsd:element <xsd:element name="failure" <xsd:complextype <xsd:sequence <xsd:element ref="documentation" minoccurs="0" maxoccurs="unbounded"/ <xsd:element ref="conditionexpression" minoccurs="0" maxoccurs="1"/ </xsd:sequence <xsd:attribute name="frombusinessstate" type="xsd:string" use="required"/ <xsd:attribute name="frombusinessstateidref" type="xsd:idref"/ <xsd:attribute name="conditionguard" <xsd:simpletype <xsd:restriction base="xsd:nmtoken" <xsd:enumeration value="success"/ <xsd:enumeration value="businessfailure"/ <xsd:enumeration value="technicalfailure"/ <xsd:enumeration value="anyfailure"/ </xsd:restriction </xsd:simpletype </xsd:attribute </xsd:complextype </xsd:element <xsd:element name="fork" <xsd:complextype <xsd:sequence ebxml Business Process Specification Schema Page 123 of 136

4347 4348 4349 4350 4351 4352 4353 4354 4355 4356 4357 4358 4359 4360 4361 4362 4363 4364 4365 4366 4367 4368 4369 4370 4371 4372 4373 4374 4375 4376 4377 4378 4379 4380 4381 4382 4383 4384 4385 4386 4387 4388 4389 4390 4391 4392 4393 4394 4395 4396 4397 4398 4399 4400 4401 <xsd:element ref="documentation" minoccurs="0" maxoccurs="unbounded"/ </xsd:sequence <xsd:attribute name="name" type="xsd:string" use="required"/ <xsd:attribute name="nameid" type="xsd:id"/ </xsd:complextype </xsd:element <xsd:element name="include" <xsd:complextype <xsd:sequence <xsd:element ref="documentation" minoccurs="0" maxoccurs="unbounded"/ </xsd:sequence <xsd:attribute name="name" type="xsd:string" use="required"/ <xsd:attribute name="uuid" type="xsd:string" use="required"/ <xsd:attribute name="uri" type="xsd:urireference" use="required"/ <xsd:attribute name="version" type="xsd:string" use="required"/ </xsd:complextype </xsd:element <xsd:element name="join" <xsd:complextype <xsd:sequence <xsd:element ref="documentation" minoccurs="0" maxoccurs="unbounded"/ </xsd:sequence <xsd:attribute name="name" type="xsd:string" use="required"/ <xsd:attribute name="nameid" type="xsd:id"/ <xsd:attribute name="waitforall" type="xsd:boolean" value="true"/ </xsd:complextype </xsd:element <xsd:element name="multipartycollaboration" <xsd:complextype <xsd:sequence <xsd:element ref="documentation" minoccurs="0" maxoccurs="unbounded"/ <xsd:element ref="businesspartnerrole" minoccurs="0" maxoccurs="unbounded"/ </xsd:sequence <xsd:attribute name="name" type="xsd:string" use="required"/ <xsd:attribute name="nameid" type="xsd:id"/ </xsd:complextype </xsd:element <xsd:element name="package" <xsd:complextype <xsd:sequence <xsd:element ref="documentation" minoccurs="0" maxoccurs="unbounded"/ ebxml Business Process Specification Schema Page 124 of 136

4402 4403 4404 4405 4406 4407 4408 4409 4410 4411 4412 4413 4414 4415 4416 4417 4418 4419 4420 4421 4422 4423 4424 4425 4426 4427 4428 4429 4430 4431 4432 4433 4434 4435 4436 4437 4438 4439 4440 4441 4442 4443 4444 4445 4446 4447 4448 4449 4450 4451 4452 4453 4454 4455 <xsd:choice minoccurs="0" maxoccurs="unbounded" <xsd:element ref="package"/ <xsd:element ref="binarycollaboration"/ <xsd:element ref="businesstransaction"/ <xsd:element ref="multipartycollaboration"/ </xsd:choice </xsd:sequence <xsd:attribute name="name" type="xsd:string" use="required"/ <xsd:attribute name="nameid" type="xsd:id"/ </xsd:complextype </xsd:element <xsd:element name="performs" <xsd:complextype <xsd:sequence <xsd:element ref="documentation" minoccurs="0" maxoccurs="unbounded"/ </xsd:sequence <xsd:attribute name="initiatingrole" type="xsd:string" use="required"/ <xsd:attribute name="initiatingroleidref" type="xsd:idref"/ <xsd:attribute name="respondingrole" type="xsd:string" use="required"/ <xsd:attribute name="respondingroleidref" type="xsd:idref"/ </xsd:complextype </xsd:element <xsd:element name="processspecification" <xsd:complextype <xsd:sequence <xsd:element ref="documentation" minoccurs="0" maxoccurs="unbounded"/ <xsd:element ref="substitutionset" minoccurs="0" maxoccurs="unbounded"/ <xsd:choice minoccurs="0" maxoccurs="unbounded" <xsd:element ref="include" minoccurs="0" maxoccurs="unbounded"/ <xsd:element ref="businessdocument" minoccurs="0" maxoccurs="unbounded"/ <xsd:element ref="processspecification" minoccurs="0" maxoccurs="unbounded"/ <xsd:element ref="package"/ <xsd:element ref="binarycollaboration"/ <xsd:element ref="businesstransaction"/ <xsd:element ref="multipartycollaboration"/ </xsd:choice </xsd:sequence <xsd:attribute name="name" type="xsd:id" use="required"/ ebxml Business Process Specification Schema Page 125 of 136

4456 4457 4458 4459 4460 4461 4462 4463 4464 4465 4466 4467 4468 4469 4470 4471 4472 4473 4474 4475 4476 4477 4478 4479 4480 4481 4482 4483 4484 4485 4486 4487 4488 4489 4490 4491 4492 4493 4494 4495 4496 4497 4498 4499 4500 4501 4502 4503 4504 4505 4506 4507 4508 4509 4510 <xsd:attribute name="uuid" type="xsd:string" use="required"/ <xsd:attribute name="version" type="xsd:string" use="required"/ </xsd:complextype </xsd:element <xsd:element name="requestingbusinessactivity" <xsd:complextype <xsd:sequence <xsd:element ref="documentation" minoccurs="0" maxoccurs="unbounded"/ <xsd:element ref="documentenvelope"/ </xsd:sequence <xsd:attribute name="name" type="xsd:string" use="required"/ <xsd:attribute name="nameid" type="xsd:id"/ <xsd:attribute name="isauthorizationrequired" type="xsd:boolean" value="false"/ <xsd:attribute name="isintelligiblecheckrequired" type="xsd:boolean" value="false"/ <xsd:attribute name="isnonrepudiationreceiptrequired" type="xsd:boolean" value="false"/ <xsd:attribute name="isnonrepudiationrequired" type="xsd:boolean" value="false"/ <xsd:attribute name="timetoacknowledgeacceptance" type="xsd:timeduration"/ <xsd:attribute name="timetoacknowledgereceipt" type="xsd:timeduration"/ </xsd:complextype </xsd:element <xsd:element name="respondingbusinessactivity" <xsd:complextype <xsd:sequence <xsd:element ref="documentation" minoccurs="0" maxoccurs="unbounded"/ <xsd:element ref="documentenvelope" minoccurs="0" maxoccurs="unbounded"/ </xsd:sequence <xsd:attribute name="name" type="xsd:string" use="required"/ <xsd:attribute name="nameid" type="xsd:id"/ <xsd:attribute name="isauthorizationrequired" type="xsd:boolean" value="false"/ <xsd:attribute name="isintelligiblecheckrequired" type="xsd:boolean" value="false"/ <xsd:attribute name="isnonrepudiationreceiptrequired" type="xsd:boolean" value="false"/ <xsd:attribute name="isnonrepudiationrequired" type="xsd:boolean" value="false"/ <xsd:attribute name="timetoacknowledgereceipt" type="xsd:timeduration"/ </xsd:complextype </xsd:element <xsd:element name="start" <xsd:complextype ebxml Business Process Specification Schema Page 126 of 136

4511 4512 4513 4514 4515 4516 4517 4518 4519 4520 4521 4522 4523 4524 4525 4526 4527 4528 4529 4530 4531 4532 4533 4534 4535 4536 4537 4538 4539 4540 4541 4542 4543 4544 4545 4546 4547 4548 4549 4550 4551 4552 4553 4554 4555 4556 4557 4558 4559 4560 4561 4562 4563 4564 4565 <xsd:sequence <xsd:element ref="documentation" minoccurs="0" maxoccurs="unbounded"/ </xsd:sequence <xsd:attribute name="tobusinessstate" type="xsd:string" use="required"/ <xsd:attribute name="tobusinessstateidref" type="xsd:idref"/ </xsd:complextype </xsd:element <xsd:element name="success" <xsd:complextype <xsd:sequence <xsd:element ref="documentation" minoccurs="0" maxoccurs="unbounded"/ <xsd:element ref="conditionexpression" minoccurs="0" maxoccurs="1"/ </xsd:sequence <xsd:attribute name="frombusinessstate" type="xsd:string" use="required"/ <xsd:attribute name="frombusinessstateidref" type="xsd:idref"/ <xsd:attribute name="conditionguard" <xsd:simpletype <xsd:restriction base="xsd:nmtoken" <xsd:enumeration value="success"/ <xsd:enumeration value="businessfailure"/ <xsd:enumeration value="technicalfailure"/ <xsd:enumeration value="anyfailure"/ </xsd:restriction </xsd:simpletype </xsd:attribute </xsd:complextype </xsd:element <xsd:element name="transition" <xsd:complextype <xsd:sequence <xsd:element ref="documentation" minoccurs="0" maxoccurs="unbounded"/ <xsd:element ref="conditionexpression" minoccurs="0" maxoccurs="1"/ </xsd:sequence <xsd:attribute name="oninitiation" type="xsd:boolean" value="false"/ <xsd:attribute name="frombusinessstate" type="xsd:string"/ <xsd:attribute name="frombusinessstateidref" type="xsd:idref"/ <xsd:attribute name="tobusinessstate" type="xsd:string"/ <xsd:attribute name="tobusinessstateidref" type="xsd:idref"/ ebxml Business Process Specification Schema Page 127 of 136

4566 4567 4568 4569 4570 4571 4572 4573 4574 4575 4576 4577 4578 4579 4580 4581 4582 4583 <xsd:attribute name="conditionguard" <xsd:simpletype <xsd:restriction base="xsd:nmtoken" <xsd:enumeration value="success"/ <xsd:enumeration value="businessfailure"/ <xsd:enumeration value="technicalfailure"/ <xsd:enumeration value="anyfailure"/ </xsd:restriction </xsd:simpletype </xsd:attribute </xsd:complextype </xsd:element </xsd:schema ebxml Business Process Specification Schema Page 128 of 136

4583 4584 4585 4586 4587 4588 4589 4590 4591 4592 4593 11 References 12 Disclaimer 1. UN/CEFACT Modelling Methodology (CEFACT/TMWG/N090R9.1 ) 2. RosettaNet Implementation Framework: Core Specification, Version: Release 2.00.00, 3 January 2001 The views and specification expressed in this document are those of the authors and are not necessarily those of their employers. The authors and their employers specifically disclaim responsibility for any problems arising from correct or incorrect implementation or use of this design. 4594 ebxml Business Process Specification Schema Page 129 of 136

4594 4595 4596 4597 4598 4599 4600 4601 4602 4603 4604 4605 4606 4607 4608 4609 4610 4611 4612 4613 4614 4615 4616 4617 4618 4619 4620 4621 4622 4623 4624 4625 4626 13 Contact Information Team Leader (Of the BP team): Paul Levine Telcordia Technologies, Inc. 45 Knightsbridge Road Piscataway, N.J. 08854 US Phone: 732-699-3042 EMail: plevine@telcordia.com Sub Team Lead (Of the context/metamodelgroup) : Karsten Riemer Sun Microsystems 1 Network Drive Burlington, MA 01803 USA Phone: 781-442-2679 EMail: karsten.riemer@sun.com Editor (of this document): Karsten Riemer Sun Microsystems 1 Network Drive Burlington, MA 01803 USA Phone: 781-442-2679 EMail: karsten.riemer@sun.com ebxml Business Process Specification Schema Page 130 of 136

4627 4628 4629 4630 4631 4632 4633 4634 4635 4636 4637 4638 4639 4640 4641 4642 4643 4644 4645 4646 4647 Copyright Statement This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to ebxml, UN/CEFACT, or OASIS, except as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by ebxml or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and ebxml DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE ebxml Business Process Specification Schema Page 131 of 136