Schema for Abstract Process Common Base for WS-BPEL 2.0 OASIS Standard 11th April, 2007 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 (i) Change the sequence for "tOnAlarmEvent" --------------------- To: --------------------- --------------------- ]]> 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. XSD Authors: The child element onAlarm needs to be a Local Element Declaration, because there is another onAlarm element defined for the pick activity. XSD Authors: The child element correlations needs to be a Local Element Declaration, because there is another correlations element defined for the invoke activity. XSD Authors: The child element correlation needs to be a Local Element Declaration, because there is another correlation element defined for the invoke activity. XSD Authors: The child element correlations needs to be a Local Element Declaration, because there is another correlations element defined for the non-invoke activities. XSD Authors: The child element correlation needs to be a Local Element Declaration, because there is another correlation element defined for the non-invoke activities. XSD Authors: The child element onAlarm needs to be a Local Element Declaration, because there is another onAlarm element defined for event handlers. XSD Authors: The child element correlations needs to be a Local Element Declaration, because there is another correlations element defined for the invoke activity. XSD Authors: The child element correlations needs to be a Local Element Declaration, 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.