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

 


Help: OASIS Mailing Lists Help | MarkMail Help

provision message

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


Subject: [provision] Extended Request/Response Proposal..


In order to move things along, I would like to make a proposal for the extended request/response operations. I propose that an extended request contain:

 

An identified operator

An optional PSO ID

An optional list of attribute value(s) pairs

 

And that the response should contain:

 

An optional PSO ID

An optional list of attribute value(s) pairs

 

The Spml:Identifier could be reused to identify the operation type. I believe that this will cover the desired functionality we discussed at the F2F.

 

Using this model, an example extended request representing an employee promotion would look like:

 

<spml:extendedRequest>

            <spml:operationIdentifier identifierType = "urn:oasis:names:tc:SPML:1.0:core#URN">

                        <spml:id>urn:com:acme:operations:promote</spml:id>

            </spml:operationIdentifier>

            <spml:identifier identifierType = "urn:oasis:names:tc:SPML:1.0:core#EMailAddress">

                        <spml:id>jdoe@acme.com</spml:id>

            </spml:identifier>

            <attr name="title">

                        <value>Manager</value>

            </attr>

</spml:extendedRequest>

 

And the response would look like:

 

</spml:extendedResponse>

            <resultCode code="0" descr="success"/>

            <attr name="title">

                        <value>VP</value>

            </attr>

</spml:extendedResponse>

 

 

The schema for this would be as follows:

 

<xsd:complexType name="ExtendedRequest">

            <xsd:complexContent>

                        <xsd:extension base="spml:SpmlRequest">

                                    <xsd:sequence>

                                                <xsd:element name="operationIdentifier" type="spml:Identifier" />

                                                <xsd:element name="identifier" type="spml:Identifier" />

                                                <xsd:element name="attr" type="dsml:DsmlAttr" minOccurs="0" maxOccurs="unbounded"/>

                                    </xsd:sequence>

                        </xsd:extension>

            </xsd:complexContent>

</xsd:complexType> 

 

<xsd:complexType name="ExtendedResponse">

            <xsd:complexContent>

                        <xsd:extension base="spml:SpmlResponse">

                                    <xsd:sequence>

                                                <xsd:element name="attr" type="dsml:DsmlAttr" minOccurs="0" maxOccurs="unbounded"/>

                                    </xsd:sequence>

                        </xsd:extension>

            </xsd:complexContent>

</xsd:complexType>

 

Also to better support using the Spml:Identifier to identify operations, I would like to add OID to our list of supported identifier types.

 

I would like to put this proposal to the list for consideration. I would welcome others to present other proposals, but one way or the other we should try to reach a consensus by or at the next telecon.

 

Jeff Bohren

Product Architect

OpenNetwork Technologies, Inc

 

 



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


Powered by eList eXpress LLC