OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ws-caf message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Proposal for voting on issue 276


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

The issue is detailed in my previous email:
 http://www.oasis-open.org/apps/org/workgroup/ws-caf/email/archives/200509/msg00011.html

Having given this some thought my preference has changed slightly from the previous email.  I now see options two and three as variations and would like to propose a vote based on those options.  This structure is intended to be used in all circumstances whereby groups of participants are transferred.

The proposal is to change the current structure for transferring groups of participants to include the protocol information through which the endpoints are enlisted in the coordination.  The information is to be grouped within the structure but the basis for that grouping is left to the sender.  Each grouping specifies a set of protocols through which each endpoint within that grouping is enlisted.  It is permissible for protocols and/or participants to be repeated in subsequent groupings within the same structure.

The schema representation of this type would be

    <xs:complexType name="ParticipantGroupType">
        <xs:sequence>
            <xs:element name="protocol" type="xs:anyURI" maxOccurs="unbounded"/>
            <xs:element name="participant" type="ref:ServiceRefType" maxOccurs="unbounded"/>
        </xs:sequence>
    </xs:complexType>

with a change in context type to

    <xs:complexType name="RegistrationContextType">
        <xs:complexContent>
            <xs:extension base="wsctx:ContextType">
                <xs:sequence>
                    <xs:element name="registration-service" type="ref:ServiceRefType" minOccurs="1"/>
                    <xs:element name="sub-protocol" type="xs:anyURI" maxOccurs="unbounded"/>
                    <xs:element name="participants" type="tns:ParticipantGroupType" maxOccurs="unbounded"/>
                    <xs:element name="extension" type="tns:ExtensionType" minOccurs="0"/>
                </xs:sequence>
            </xs:extension>
        </xs:complexContent>
    </xs:complexType>

with participantList and any other messages being changed as follows:-

    <xs:element name="participantList">
        <xs:complexType>
            <xs:sequence>
                <xs:any namespace="##other" processContents="lax" minOccurs="0"/>
                <xs:element name="participants" type="tns:ParticipantGroupType" maxOccurs="unbounded"/>
            </xs:sequence>
            <xs:attribute ref="wsu:Id" use="optional"/>
        </xs:complexType>
    </xs:element>

	Kev

-- 
Kevin Conner
Arjuna Technologies Ltd.



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]