Schema for Abstract Process Common Base for WS-BPEL 2.0 Last modified date: 17th August, 2006 NOTE: Here is the changes path from Exec BPEL XSD to this XSD: (a) have a global replace from minOccurs=1 to minOccurs=0 for element declaration (b) have a global replace from use=required to use=optional for attribute declaration (c) change "xsd-derived" from XSD NS to this Abstract BPEL NS and define the corresponding simple types (d) adding "##opaque" to BPELVariableName, tInitiate, tPattern, tRoles, tBoolean (e) add abstractProcessProfile to tProcess (f) add opaqueActivity (g) add tOpaqueBoolean type and add opaque attribute tExpression, tQuery, tFrom, tTo (h) add opaqueFrom element and introduce fromGroup 2006-08-07: Rev 1.1: Alex Yiu Branching off from wsbpel_main.xsd of Rev 1.48: by changing targetNamespace and changing prefix "simple" to "xsd-derived" and its corresponding namespace 2006-08-08: Rev 1.2: Alex Yiu Minor cosmetic change 2006-08-09: Rev 1.3: Alex Yiu A minor update and clarification in comments and documentation 2006-08-16: Rev 1.4: Thomas Schulze Minor formatting changes. Apply AI 151: change the defaults of queryLanguage and expressionLanguage from "urn:oasis:names:tc:ws2.0:sublang:xpath1.0" to "urn:oasis:names:tc:wsbpel:2.0:sublang:xpath1.0". Apply AI 152: change the targetNamespace from "http://docs.oasis-open.org/ws-bpel/2.0/process/abstract" to "http://docs.oasis-open.org/wsbpel/2.0/process/abstract". Apply the two friendly amendments made in today's call. That are: 1) make the QName list non empty (simpleType QNames) 2) make fromParts, fromPart, toParts, toPart extensible Add a copyright statement. 2006-08-17: Rev 1.5: Alex Yiu Adding last modified date and small reformatting for copyright statement This is the root element for a WS-BPEL 2.0 process. This type is extended by other component types to allow elements and attributes from other namespaces to be added at the modeled places. All standard WS-BPEL 2.0 activities in alphabetical order. Basic activities and structured activities. Addtional constraints: - rethrow activity can be used ONLY within a fault handler (i.e. "catch" and "catchAll" element) - compensate or compensateScope activity can be used ONLY within a fault handler, a compensation handler or a termination handler This element can contain all activities including the activities compensate, compensateScope and rethrow. This element can contain all activities including the activities compensate, compensateScope and rethrow. Child element onAlarm needs to be a LED, because there is another onAlarm element defined for the pick activity. Child element correlations needs to be a LED, because there is another correlations element defined for the invoke activity. Child element correlation needs to be a LED, because there is another correlation element defined for the invoke activity. Child element correlations needs to be a LED, because there is another correlations element defined for the non-invoke activities. Child element correlation needs to be a LED, because there is another correlation element defined for the non-invoke activities. Child element onAlarm needs to be a LED, because there is another onAlarm element defined for event handlers. Child element correlations needs to be a LED, because there is another correlations element defined for the invoke activity. Child element correlations needs to be a LED, because there is another correlations element defined for the invoke activity. There is no schema-level default for "exitOnStandardFault" at "scope". Because, it will inherit default from enclosing scope or process. This element can contain all activities including the activities compensate and compensateScope. This element can contain all activities including the activities compensate and compensateScope.