Proposal for voting on issue 280

[Kevin Conner <Kevin.Conner@arjuna.com>]

This is a proposal for a vote on issue 280, the vote to be taken at the next concall. 

The addParticipant and removeParticipant messages specify a set of protocols for which the operation applies.  This is not reflected in the replaceParticipant message.

The proposal is to change the schema (and associated text) to allow the replaceParticipant to include a set of protocols for which the replace operation is to apply.  This would necessitate a change in the schema from

    <xs:element name="replaceParticipant">
        <xs:complexType>
            <xs:sequence>
                <xs:any namespace="##other" processContents="lax" minOccurs="0"/>
                <xs:element name="old-participant" type="ref:ServiceRefType"/>
                <xs:element name="new-participant" type="ref:ServiceRefType"/>
             </xs:sequence>
            <xs:attribute ref="wsu:Id" use="optional"/>
        </xs:complexType>
    </xs:element>

to

    <xs:element name="replaceParticipant">
        <xs:complexType>
            <xs:sequence>
                <xs:any namespace="##other" processContents="lax" minOccurs="0"/>
                <xs:element name="old-participant" type="ref:ServiceRefType"/>
                <xs:element name="new-participant" type="ref:ServiceRefType"/>
                <xs:element name="protocol" type="xs:anyURI" maxOccurs="unbounded"/>
             </xs:sequence>
            <xs:attribute ref="wsu:Id" use="optional"/>
        </xs:complexType>
    </xs:element>

	Kev

-- 
Kevin Conner
Arjuna Technologies Ltd.