Issue - 111 - The text for my modification of Paco's Proposal

["Yaron Y. Goland" <ygoland@bea.com>]

I think my original, unamended, proposal is best but if we are going to 
insist on putting the standard attributes and elements on the wrapper 
then I think the approach I outline below is the best one to take.

111 - Extension Activities (alternative proposal)

Proposal: Add an extensionActivity element to enable extension activities.

Introduce Section 11.9

New activities can be introduced for use in BPEL via the 
extensionActivity element.  The extensionActivity element has the same 
standard attributes and elements as any other BPEL activity. But in 
addition the extensionActivity has the extensionName attribute that is 
used to identify the semantics associated with the extension activity. 
If an extensionName is not recognized by a BPEL processor and if the 
namespace from which the extensionName is taken is not subject to a 
mustUnderstand="true" requirement from an extension declaration then the 
unrecognized extension activity MUST be treated as if it were an empty 
activity.

<extensionActivity extensionName="QName" standard-attributes>
       standard-elements
</extensionActivity>

Due to the limitations of the XML Schema processing model it is not 
possible to put new content from non-BPEL namespaces after the 
standard-elements.

For example, the following hypothetical extension activity is schema 
invalid:

<extensionActivity extensionName="the:LoggingActivity">
    <targets>
       <target linkName="foo"/>
    </targets>
    <the:LoggingConfiguration>
       <the:LogName>foo.art#1</the:LogName>
       <the:LogLevel>3</the:LogLevel>
    </the:LoggingConfiguration>
</extensionActivity>

Instead the activity would have to be specified as follows:

<extensionActivity extensionName="the:LoggingActivity">
    <the:LoggingConfiguration>
       <the:LogName>foo.art#1</the:LogName>
       <the:LogLevel>3</the:LogLevel>
    </the:LoggingConfiguration>
    <targets>
       <target linkName="foo"/>
    </targets>
</extensionActivity>

Schema:

Add to activity group:
     <element name="extensionActivity" type="bpws:tExtensionActivity"/>

Add the following definition:
     <complexType name="tExtensionActivity">
         <complexContent>
             <extension base="bpws:tActivity">
                 <attribute name="extensionName" type="QName"/>
             </extension>
         </complexContent>
     </complexType>